Infradmins

Configuring HADR 1. db2level should be same on both the server. Primary: DB21085I  This instance or install (instance name, where applicable: "db2inst2") uses "64" bits and DB2 code release "SQL10014" with level identifier "0205010E". Informational tokens are "DB2 v10.1.0.4", "s140509", "IP23584", and Fix Pack "4". Product is installed at "/opt/IBM/DB2". Standby: DB21085I  This instance or install (instance name, where applicable:"db2inst2") uses "64" bits and DB2 code release "SQL10014" with level identifier "0205010E". Informational tokens are "DB2 v10.1.0.4", "s140509", "IP23584", and Fix Pack "4". Product is installed at "/opt/IBM/DB2". 2. Create database on Primary Create a sample database or restore db from any offline backup 3. Enable  Archive logging mode db2 "update db cfg using LOGARCHMETH1 ...

1. Get the ddl from linux system by using the following command.         This ddl contains the table structures and associated indexes and sequesenses for a perticular            Schema.      db2look -d <db_name> -z <schema_name> -e |tee <Filename>.ddl 2. Export the data from the Database for a perticular schema using the following command.            db2move <DB_NAME> export -sn <schema_Name>             -- This will generate one .lst file and multiple .ixf,.msg files 3. Transfer the files generated in the above step to the windows system. 4. create the Database,bufferpool,tablespaces and schema manually in the windows machine using the following commands.        1. create db <DB_NAME>;     ...

If the following error comes when trying to connect to DB2 database Action Taken : 2009-05-07-16.43.36.788014-240 I2378630885A584 LEVEL: Error (OS) PID : 2502884 TID : 1 PROC : db2ipccm 0 INSTANCE: db2ist1 NODE : 000 FUNCTION: DB2 UDB, SQO Mnemory Management, sqloMemSetPageSize, probe:100 MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid memory addr" DIA8561C A invalid memory block was encountered. CALLED : OS, -, shmctl OSERR : EINVAL (22) "Invalid argument" DATA #1 : String, 44 bytes Failure enabling specified memory page size. DATA #2 : Logical page size, PD_TYPE_MEM_PAGE_SIZE, 8 bytes 65536 Just set the below parameter db2set DB2_MEDIUM_PAGE_SUPPORT=OFF and restart the db2

Creating VG Verify new disks 1)    Take the output of lspv before scanning the disk. #lspv 2) Check for the new disk For scanning #cfgmgr -v Identify the new disk that detected by comparing the old lspv output. 3) Cross verify the LUN Number matching with the given number from Storage #powermt display dev=<hdiskpower#> |grep -i LUN Eg: root@NIMmaster /root # powermt display dev=hdiskpower5 |grep -i LUN Logical device ID=6006016020672A008820B177987CE011 [LUN 125] If the disk not displaying under powerpath use following command to identify the Uniq ID, which can be matched from storage end also. #lscfg -vpl hdiskpower5 |grep -i "(UI)" Eg: root@NIMmaster /root # lscfg -vpl hdiskpower5 |grep -i "(UI)"   Device Specific.(UI)........6006016020672A008820B177987CE011 4) Verify the size of the disk #bootinfo –s <disk> If it’s under powerpath use hdiskpower. Eg: root@NIMmaster /root # bootinfo -s hdiskpow...

Given procedure helpful for applying Firmware and OS patches for Solaris 9 Before starting the patching Ensure all system files have up to date backup. I.  Installation of OBP patches: 1. Verify system hardware level.    # uname  -a    SunOS LABSEVER 5.9 Generic_118558-39 sun4u sparc SUNW, Sun-Fire-V440 2. Copy the appropriate OBP patches to the server under /var/tmp/OBPpatches. 3. Unzip the OBP patches    #unzip <patch-id.zip> 4. Verify the server for existing OBP level    #prtdiag  -v |grep –i OBP And compare the patch level with the new OBP patch level info available in /var/tmp/OBPpatches/<patch number>/README.<patch number>.   If the existing level is lower than the update available, update the server with OBP   patches. Otherwise you can skip the OBP patches. 5. It is good practice to apply any OS/OBP patches in Single user mode (need console logi...

Topic : Installation procedure for WebSphere Liberty Profile. Procedure: Install a Java SDK. If you already have a Java 6 or Java 7 SDK then you can skip this step.   To install a Java 7 SDK ,simply unzip the file   ibm-java-sdk-70-win-i386.zip . Install the WebSphere Application Server Developer Tools for Eclipse V8.5.5. From the command prompt type   java -jar WDT-8.5.5-win.jar   and follow the prompts to install Eclipse 4.2.2 and the developer tools to the directory of your choice. Install the IBM WebSphere Application Server V8.5.5 Liberty Profile. From the   command prompt   type   java -jar wlp-developers-runtime-8.5.5.0.jar and follow the prompts to install the Liberty profile to a directory of your choice. If you want to use JMS, Web services or MongoDB you should also install the extended programming models. This can be done by running   java -jar wlp-developers-extended-8.5.5.0.jar   and following the prompts. Optional: ...

Topic:  Programming Models Supported: Java Servlet 3.0 JavaServer Faces (JSF) 2.0 JavaServer Pages (JSP) 2.2 Java Expression Language 2.2 Standard Tag Library for JavaServer Pages (JSTL) 1.2 Bean Validation 1.0 Java Persistence API (JPA) 2.0 Java Transaction API (JTA) 1.1 Java Database Connectivity (JDBC) 4.0 Java API for RESTful Web Services (JAX-RS) 1.1 In WAS 8.5.5 version  it supports the below Contexts and Dependency Injection for Java (Web Beans 1.0) Dependency Injection for Java 1.0 Enterprise JavaBeans 3.1 (includes Interceptors 1.1) - EJB Lite subset In other editions, such as WebSphere Application Server and WebSphere Application Server Network Deployment, the Liberty profile supports the following technologies in addition to those contained in Liberty Core: Java API for XML-Based Web Services (JAX-WS) 2.2 Java Architecture for XML Binding (JAXB) 2.2 SOAP with Attachments API for Java (SAAJ) 1.3 Java Message Service...

Topic : What is liberty Profile in WAS? and its features Explanation: The Liberty profile is a lightweight, simple to use, yet powerful, application server for lightweight web production server , OSGi, and mobile applications. Extremely fast restart times coupled with its small size and ease of use make the Liberty profile a great option for building web apps that do not require the full Java EE environment of traditional enterprise application server profiles. Features: 1.Simple Configuration (only one simple config file server.xml for all configurations) 2. Rapid Server Restart (less then 5 seconds) 3. It supports integrated  tools like(Maven/Eclipse). 4. dynamically extendible. 5. Supports light weight Cluster Management. 6. Fidelity to traditional WAS.  7. Web Profile Certified. 8. Memory foot print is < 60 MB 9. Profile is dynamic (switch parts of the server on and off with out restart) 10. Be installed and managed separately from a...

Issue: Circular Log is deleted by the user by mistake which causes the queue manager not able to start Solution: Restore the log file from back up and start the qmgr. it should work WorkAround: If there is no backup the workaround to get the queue manager running is 1. backup /var/mqm/log/<ORI_QMGR> 2. create the dummy qmgr with the similar log description as in the <ORI_QMGR>for this refer the /var/mqm/qmgrs/<ORI_QMGR>/qm.ini 3. crtmqm <DUMMY_QMGR> -lp 3 -ls 2 -lp 1024 -lc 4. copy /var/mqm/log/<DUMMY_QMGR>/active and amqhlct.ifh to /var/mqm/log/<ORI_QMGR>        cp  /var/mqm/log/<DUMMY_QMGR>/* /var/mqm/log/<ORI_QMGR>/ 5. ensure all semphores for <ORI_DMGR> are cleared 6.strmqm <ORI_QMGR> 7. you can remove <DUMMY_QMGR> if not required.

Issue: AMQ8041 Error Unable to restart the QueueManager Solution :  Remove the MQ semaphores by using this command /usr/mqm/bin/amqiclen -m <QM_NAME> -v -h -x -F