db2 connect to sales db2 update db cfg using sortheap 1000 db2 get db cfg instfix -vik IY76255backup vg to tape $savevg -f /dev/rmt0 appsvg backup vg to another folder $mount nimtsm:/backup /mnt $savevg -f /mnt/siviewt/savevg_appsvg_170707 appsvg Deleve files in batch $find . -name "spc.log.*" - exec rm {} \; mount SSA5TSMP2:/backup /mnt Scheduler client connection 1. run cmd line 2. \program files\ibm siview\schclient -option SiView Compiliation 1. Make clean $HOME/superpos/src/csppt/source/src/posppt/make clean 2. If small tx is changed, bohhelper need to make $HOME/superpos/src/csppt/source/src/posppt/pptmgr/factory/make -f makefile bos_c lean $HOME/superpos/src/csppt/source/src/posppt/pptmgr/factory/make -f makefile mkbos 3. Make all $HOME/superpos/src/csppt/source/src/posppt/make all 4. Make lib $HOME/superpos/src/csppt/source/src/posppt/mkso 5. Make clean mmserver $HOME/superpos/src/csclass/make -f mkcsmain.mak clean $HOME/superpos/src/csclass/make -f mkcsmain.mak all 6. copy module and bind into runtime $HOME/superpos/src/csppt/source/src/posppt/copymod.ksh siviewd to resync the current setting on lv. $synclvodm -v -P mms1vg change schd client setting $schedulerclient.exe -option DSL access 1. WEP Key: 8b791e4934f28e6b25e5c8d5f6 DB2 Instance # db2icrt -p edatinst -s ESE -w 64 -u edatinst edatinst DB2 Fixpack installation #installFixPak -y to display filesystem is mirrored or not #lsvg -l edat1vg note: if PVs is 2 means two physical volumes db2 export data command 1. db2move MMDB EXPORT -tn * 2. db2move MMDB IMPORT LOAD check HADR status #login as db2instance # db2 get snapshot for all on dbname DB2 Export #db2 export to awards.ixf of ixf message msgs.txt select * from staff where dept =20 db2 export to xxep_events_data.ixf of ixf select * from xxep.xxep_events_data wh ere event_id <=16706 db2 "export to xxep_siview_events_data.ixf of ixf select * from oraerp.xxep_sivi ew_events_data where event_id=32684" db2 "import from xxep_siview_events_data.ixf of ixf allow write access commitcou nt 1 insert into oraerp.xxep_siview_events_data" db2 "export to fbusergrp_m.ixf of ixf select smallint(0), d_thesystemKey, usergr p_id, usergrp_type,desc, timestamp(current timestamp), 'replica' from siview.fbu sergrp_m" DB2 Import # db2 import from myfile.ixf of ixf message msg.txt insert into staff #db2 "import from fbusergrp_m.ixf of ixf insert into siview.usergrp" DB2 query SQL message #db2 ? SQLnnnn Export db2 -x " select ' export to '||rtrim(name)||'.ixf of ixf select * from '||rtrim( creator)||'.'||ltrim(name)||';' from sysibm.systables where creator = 'SIVIEWT' and type = 'T' " > export_mmdb.sql db2 -tvf export_mmdb.sql -z export_mmdb.log I plan to run this script to import the data db2 -x " select ' import from '||rtrim(name)||'.ixf of ixf replace_create into s chema1'||ltrim(name)||' in '||rtrim(tbspace)||' index in '||rtrim(INDEX_TBSPACE) ||';' from sysibm.systables where creator = 'SIVIEW' and type = 'T' " > import_m mdb.sql db2 -tvf import_mmdb.sql -z import_mmdb.log DB2 rollforward #db2 rollforward database spcdb to xxxxx and stop perform this on the DB2 client side in order to test the HADR features? #UPDATE ALTERNATE SERVER FOR DATABASE database-alias USING HOSTNAME hostname POR T port-number check db configuration #db2 get db cfg for <database_name> | grep HADR db2 back/restore #cd <temp_backup_directory> db2 backup db <database_name> #db2 restore db <database_name> from <temp_restore_directory> replace history fi le remove ^M character from the file #tr -d "\015\032" < oldfile > newfile add more spaces for Rep 1. create rawdevices on standby 2. assign to standby instance owner 3. create rawdevices on primary 4. assign to primary instance owner create sample database #db2sampl check cluster status #lssrc -g cluster #clRGinfo # clstat #smitty clstop #smitty clstart #smitty hacmp reboot the machine #reboot -q To start and stop the hadr process, use the db2 instance owner userid. To start primary hadr database process, execute: db2 start hadr on database SMDB as primary To start standby hadr database process, execute: db2 start hadr on database SMDB as standby To stop primary hadr database process, execute: db2 stop hadr on database databa se-alias To stop standby hadr database process, execute: db2 stop hadr on database databa se-alias Deactivate database #db2 deactivate database database-alias Stop rollforward #db2 rollforward database database-alias to end of logs and stop check Listen Port cat 1078873 Sep 25 11:21 mmserver .bnd cs00008.so libcs_pptsvrlib.bnd $HOME/mm/msg -rw-r--r-. Upgrade from prod version to customized version $HOME/mm/lib -rwxr-xr-x -rwxr-xr-x -rwxr-xr-x -rwxr-xr-x -rwxr-xr-x -rwxr-xr-x $HOME/mm/bnd -rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r--rw-r--r-1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd siviewd db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 db2iadm1 2010519 7811434 833017 2247753 1280630 6388018 2089 10821 13729 9050 16067 7057 15363 3736 3724 1556 Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep 26 26 26 26 26 26 25 25 25 25 25 25 25 25 25 25 09:53 09:53 09:53 09:53 09:53 09:53 19:17 19:35 19:36 19:37 19:38 19:39 19:39 19:40 19:41 19:42 libcs_pptbossp_fw.out Kill all process # | grep -v grep | grep siview|grep -v 'kill' | awk '{print$1}' or #ps -u shemond -o pid | grep -v PID | xargs -i kill -9 {} check the files with most space taken #du -sm * | sort -n | pg Generate IOR To generate the ior using genIOR utility in mm/bin.so libcs_pptmgri.23 DB2 get snapshop for hadr #db2 get snapshot for all on hadr | grep "HADR Status" #hdrsnap check hacmp failover log #tail -f /tmp/hacmp. the server is UUID if you pointing to server directly.bnd cs00002.bnd cs00010. If y ou point to dispatcher any number with 32 characters is fine. systax: genIOR host port server marker interface orb example: genIOR siviewt 16000 88888888888888888888888888888888 thePPTServiceManagerObject Factory CS_PPTServiceManagerObjectFactory EBROKER For EBROKER version.bnd cs00006.1 siviewd db2iadm1 $HOME/mm/bin -rwxr-xr-x 1 siviewd db2iadm1 Then call 6328 Sep 26 00:25 cs_pptmsg.so libcs_txmethods.so libcs_srvlibs.bnd cs00004.bnd cs00005.so cs00001. The port refer to dispatcher port.bnd cs00003.so libcs_svcclt. or server port (direct connection).bnd cs00007.#netstat -Aan | grep *.bnd cs00009. ..ManagedObjectImplName=PPTServiceManager_i [CS_PPTManager] ManagedObjectIDLName=CS_PPTManager ManagedObjectImplName=CS_PPTManager_i [BRSVariableInfoIMizedMgrBO] ManagedObjectIDLName=BRSVariableInfoIMizedMgr ManagedObjectImplName=BRSVariableInfoIMizedMgr_i . common to common1 2. Bind the database.. bindmm.. 3. Overwrite the mm1A content with files in folder in SSA5SMSD1:root:/package/up grade_1A_release_1/mm.ksh lbmmdb Change $HOME/mm/bin/startmm.. [ln -s /home/siview/mm1 mm] 5. Please make sure in startmm. 6.[PPTServiceManagerBO] . please copy the /package/upg rade_1A_release_1/mm/bin/mmserver to mmserver01.ksh. CLP is included in mm1/mig/clp [Please confirm with J ian Der the appropriate table space]. create the new tables.ksh. new parameter is added: export IFLIB_PATH=$HOME/ifadapter/lib . Import the predefined data.ini PPTServiceManager thePPTServiceManagerObjectFactory:802000001111111111111111 11111111:28200:EBROKER SSA5SMSD1 PPTManager P25/#CS_PPTManager#F25#PPTManager:8020000011111111111111111111111 1:28200:EBROKER SSA5SMSD1 PPTServiceManagerObjectFactory PPTServiceManagerObjectFactory:80200000111111 111111111111111111:28200:EBROKER SSA5SMSD1 PPTManagerObjectFactory CS_PPTManagerObjectFactory:8020000011111111111111111 1111111:28200:EBROKER SSA5SMSD1 1..ManagedObjectIDLName=PPTServiceManager .ini [F25] ManagedObjectEntries=CS_PPTManager . 4. [Upg rade step attached in excel sheet] 7. RAS Support section (service) / ManagedObjectEntries=CS_PPTManager Change $HOME/mm/etc/mmserver.. mmserver02.ksh. Depend on how many mmsever insetance is running.bindmm.ksh #Add SD100027 export CS_MM_CATALOG_FILE=$HOME/mm/msg/cs_pptmsg.. Predefined data is available at mm1/mig/pre. 8. bindcs. create the softlink from at /home/siview/mm to mm1.cat #D100027 Add start export CS_DERIVEDDATA_FORMULA_ENABLED=1 #D100027 add end Change $HOME/mm/etc/mmimconfig.DCR4000022 Remove Inheritance of IM object from PPTServiceManager . copy existing mm folder to become mm1 in modules folder. 2@localhost:30000/SiViewIFDispatcher export CS_MM_CATALOG_FILE=$HOME/mm/msg/cs_pptmsg. 2.. create a new folder ifadapter1 in modules folder.NODE0000.fr The followings are Good Database Backup image for mmdb and smdb: > su .001 SSA5DBP1:mminst:/db2instance/db2home/mminst/dbbackup> . export SP_CARRIER_CAPACITY=25 export SP_CARRIER_NOMINALSIZE=12 export SP_FPC_ADAPTATION_FLAG=1 #D100027 Add start export CS_DERIVEDDATA_FORMULA_ENABLED=1 Step to upgrade Interface Adapter: 1.mminst SSA5DBP1:mminst:/db2instance/db2home/mminst/dbbackup> db2 backup db mmdb to /db2instance/db2home/mminst/dbbackup Backup successful. drwxrwxr-x 14 mminst mmiadm 4096 Oct 23 12:34 . -rw-r----.mminst. The timestamp for this backup image is : 20071023155652 SSA5DBP1:mminst:/db2instance/db2home/mminst/dbbackup>ls -al total 1844456 drwxr-xr-x 2 mminst mmiadm 256 Oct 23 16:06 .Please confirm if this sha re folder has been created export SP_CARRIER_ADMINISTRATOR=MM <--Please make sure it is set in SM too. overwrite ifadapter1 content with SSA5SMSD1:root:/package/upgrade_1A_release_ 1/ifadapter 3. CATN0000.20071023155652.# LIBPATH export LIBPATH=.0.cat export SP_EBROKERTCS_SAMBAPATH=/home/smb/smartTCS <-. check Database integrity #db2dart check volume group mount #fsck /dev/lv_moudules #lsvg -l rep1vg #mount /home/siview/modules Query TSM backup history #db2adutl query db MMDB Refresh sendmail #refresh -s sendmail frederic. [ln -s /home/siview/ifada pter1 ifadapter] Addition upgrade on IF Adapter will be provided by this week once Naveen has com pleted his changes on IF. create the softlink at /home/siview to ifadapter1.1 mminst mmiadm 944353280 Oct 23 15:57 MMDB.oh@soitec.:$LIBPATH:$IFLIB_PATH #Interface Adapter fs export IFSERVER_NAME=SiViewIFDispatcher export IFSERVER_URL=corbaloc:iiop:1. If the database is ready for backup. > db2 list application If there are.NODE0000.001 I have not done it for spcdb. su . Could you do a backup of the database? Steps: 1.spcinst 2..20071023161121. check pp size by using lsvg rootvg (max available ps: #bootinfo -r) b. smitty chps Remove Paging Space #smitty swapoff #smitty rmps Restart sendmail # stopsrc -s sendmail . issue: db2 force application all 3.sminst SSA5DBP1:sminst:/db2instance/db2home/sminst/dbbackup> db2 backup db smdb use tsm Backup successful. The timestamp for this backup image is : 20071023161121 SSA5DBP1:sminst:/db2instance/db2home/sminst/dbbackup>ls -al total 1572136 drwxr-xr-x 2 sminst smiadm 256 Oct 23 16:11 . CATN0000. -rw-r--r-. Do a offine backup to tsm db2 backup db spcdb use tsm Take note of the timestamp for the backup image.sminst. Do a offline backup to local disk.1 sminst smiadm 804921344 Oct 23 16:11 SMDB.0. The timestamp for this backup image is : 20071023160747 db2 backup db smdb to /db2instance/db2home/sminst/dbbackup Backup successful. Check top resources used by application #topas Check paging space #lsps Change Page size a. db2 backup db spcdb to /db2instance/db2home/spcinst/dbbackup Take note of the timestamp for the backup image.1 sminst smiadm 1072 Oct 23 16:09 DART.db2 backup db mmdb use tsm Backup successful. drwxrwxr-x 8 sminst smiadm 4096 Oct 22 21:31 . Ensure that there is no connections.INF -rw-r----. 4. The timestamp for this backup image is : 20071023160135 > su . set proper rights and owner for filesysetm.# startsrc -s sendmail -a"-bd -q30m" If you only need to refresh the configuration you can also run: #kill -1 pid # refresh -s sendmail Refresh clinfoES #stopsrc -s clinfoES #startsrc -s clinfoES #lssrc -s clinfoES #clstat if above not working for refreshing clinfoES then #stopsrc -s clinfoES #stopsrc -s snmpd #startsrc -s snmpd #startsrc -s clinfoES wait about 10 seconds then #clstat Print System configuration info #prtconf | more check file sizing and sorting #du -sk * | sort -n -r | pg DB2 restoring a. create instance account and instance c. #db2 restore db schdb from /home/tstinst/backup taken at 20071101141915 to /home /schdb replace history file #db2 restore db spcdb from /home/tstinst/backup taken at 20071101143035 to /home /spcdb replace history file #db2 restore db smdb from /home/tstinst/backup taken at 20071101141617 to /home/ smdb replace history file #db2 restore db mmdb from /home/tstinst/backup taken at 20071101141043 to /home/ mmdb replace history file do roll forwarding (copy lastet log files over). create filesystem b. shutdown corba service: #txtsaoclt SSA5SMS:27500 xmserver ShutDown 2 txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt ssa5mmsp1:27201 ssa5mmsp1:27202 ssa5mmsp1:27203 ssa5mmsp1:27204 ssa5mmsp1:27205 ssa5mmsp1:27206 ssa5mmsp1:27207 ssa5mmsp1:27208 ssa5mmsp1:27209 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown 2 2 2 2 2 2 2 2 2 . repinst db2 deactivate database su .repinst -c 'db2start' .edainst -c 'db2start' su .schinst db2 deactivate database su .sminst -c 'db2start' su . P1 start instance on P2 su .schinst -c 'db2start' su .mminst -c 'db2start' su .txtsaoclt ssa5mmsp1:27210 mmserver01 ShutDown 2 txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt txtsaoclt ssa5mmsp2:27201 ssa5mmsp2:27202 ssa5mmsp2:27203 ssa5mmsp2:27204 ssa5mmsp2:27205 ssa5mmsp2:27206 ssa5mmsp2:27207 ssa5mmsp2:27208 ssa5mmsp2:27209 ssa5mmsp2:27210 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 mmserver01 ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown ShutDown 2 2 2 2 2 2 2 2 2 2 1.spcinst db2 deactivate database su .sminst db2 deactivate database su .pmsinst -c 'db2start' su . P1 start P2. deactivate DB on P2 su .edainst db2 deactivate database stop su su su su su su su stop su su su su su su su - MMDB SMDB SPCDB SCHDB MMRDB EMNTDB EDATDB hadr on P2 schinst -c 'db2stop' spcinst -c 'db2stop' edainst -c 'db2stop' sminst -c 'db2stop' mminst -c 'db2stop' pmsinst -c 'db2stop' repinst -c 'db2stop' hadr on P1 schinst -c 'db2stop' spcinst -c 'db2stop' edainst -c 'db2stop' sminst -c 'db2stop' mminst -c 'db2stop' pmsinst -c 'db2stop' repinst -c 'db2stop' shutdown P2.mminst db2 deactivate database su .spcinst -c 'db2start' su .pmsinst db2 deactivate database su . 1.schinst -c 'db2start' su . For emntdb: Run db2 "ALTER TABLESPACE TSASNAA RESIZE (ALL 25000)" #Update DB config parameter 1. execute: db2 stop hadr on db emntdb db2stop db2start 3. as pmsinst. On primary server.pmsinst -c 'db2 start hadr on database emntdb as standby' su . For smdb: Run db2 "ALTER TABLESPACE TSASNUOW RESIZE (ALL 4900)" #2.edainst -c 'db2start' su . execute: db2 deactivate db emntdb db2 stop hadr on db emntdb db2stop db2start 2. db2 update db cfg for emntdb using locklist 500 maxlocks 60 locktimeout 60 2. On standby server.mminst -c 'db2start' su . as pmsinst. 3. as pmsinst.2.edainst -c 'db2 start hadr on database edatdb as standby' su .schinst -c 'db2 start hadr on database schdb as standby' su .edainst -c 'db2 start hadr on database edatdb as primary' su .start hadr on P2 su . Stop HADR processes for emntdb on both database servers.repinst -c 'db2 start hadr on database mmrdb as primary' Update tablespaces #1. as pmsinst.spcinst -c 'db2 start hadr on database spcdb as standby' su .mminst -c 'db2 start hadr on database mmdb as standby' su .sminst -c 'db2start' su .2. Run the following on both servers using the instance userid(pmsinst). 2.mminst -c 'db2 start hadr on database mmdb as primary' su .pmsinst -c 'db2 start hadr on database emntdb as primary' su . Start HADR Processes on both database servers.spcinst -c 'db2 start hadr on database spcdb as primary' su . execute: db2 start hadr on db emntdb as standby 3.sminst -c 'db2 start hadr on database smdb as primary' su .repinst -c 'db2 start hadr on database mmrdb as standby' start instance on P1 su . On Primary server.schinst -c 'db2 start hadr on database schdb as primary' su .1 On Standby server.repinst -c 'db2start' start hadr on P1 su . execute: db2start hadr on db emntdb as primary .pmsinst -c 'db2start' su .sminst -c 'db2 start hadr on database smdb as standby' su .spcinst -c 'db2start' su . DROP TABLE SIVIEW. #SYNC 10. NULL. NULL. NULL. NULL. #SYNC 40. NULL. CREATE TABLE SIVIEW.ixf OF IXF MODIFIED BY COMPOUND=5 NOCHECKLENGTHS COMM ITCOUNT 1000 INSERT INTO SIVIEW.FHCDATAHS" NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NULL. NULL. #SYNC 30. NULL. NULL. NULL. NULL.FHCDATAHS LOCKSIZE ROW APPEND OFF NOT VOLATILE. NULL.FHCDATAHS". NULL.FHCDATAHS. NULL.ixf OF IXF SELECT * FROM SIVIEW. NULL. NULL. NULL. NULL. NULL. db2 "IMPORT FROM FHCDATAHS.FHCDATAHS (MEAS_LOT_ID VARCHAR(64) MEAS_LOT_TYPE VARCHAR(64) MEAS_PRODSPEC_ID VARCHAR(64) MEAS_PRODGRP_ID VARCHAR(64) MEAS_TECH_ID VARCHAR(64) MONITOR_GRP_ID VARCHAR(64) MEAS_MAINPD_ID VARCHAR(64) MEAS_OPE_NO VARCHAR(64) MEAS_PD_ID VARCHAR(64) MEAS_PD_TYPE VARCHAR(20) MEAS_PASS_COUNT INTEGER MEAS_PD_NAME VARCHAR(64) MEAS_AREA_ID VARCHAR(64) MEAS_EQP_ID VARCHAR(64) MEAS_EQP_NAME VARCHAR(64) MEAS_LC_RECIPE_ID VARCHAR(64) MEAS_RECIPE_ID VARCHAR(64) MEAS_PH_RECIPE_ID VARCHAR(64) CLAIM_TIME TIMESTAMP CLAIM_SHOP_DATE DOUBLE CLAIM_USER_ID VARCHAR(64) MEAS_DCDEF_ID VARCHAR(64) MEAS_DC_TYPE VARCHAR(12) MEAS_DCSPEC_ID VARCHAR(64) MEAS_WFRHS_TIME TIMESTAMP STORE_TIME TIMESTAMP EVENT_CREATE_TIME TIMESTAMP ) DATA CAPTURE NONE IN MM_TBSPACE1 INDEX IN MM_IDXSPACE2. NULL. NULL. #SYNC 20. NULL. NULL . NULL. NULL. NULL.list tablespace container #db2 list tablespace containers for tbsid analyze replication #asnqanalyze -db proddb1 proddb2 -la detailed Move index tablespace to different one db2 "EXPORT TO FHCDATAHS. NULL. ALTER TABLE SIVIEW. Start Appply program Stop All running Queue Managers # endmqm . Start Capture program 6.FHCDATAHS AND INDEXES ALL SHRLEVEL REFERENCE. #SYNC 70.FHCDATAHS (MEAS_LOT_ID ASC.Add new Replication Tables 1. DB2 Catalog #db2 catalog tcpip node mmdb remote <IP-ADR> server <DB-PORT> #db2 catalog db mmdb at node mmdb as <alias> authentication SERVER SQL Replication . use the same tablespace as original table . add Index tablespace information for table creatio n. Stop Apply program 3. may hav e different schema) 4. Add Apply Member . From Replication Center Register new capture tables . CREATE UNIQUE INDEX SIVIEW.For CD table. . #SYNC 60.For CD table.IXFHCDATAHS ON SIVIEW.For the running script.Set target table name . Table space resizing #ALTER TABLESPACE TSCDFBPRIVGRP_M RESIZE (File '/home/smdb/sminst/NODE0000/SQL00001/CDFBPRIVGRP_M' 2048 ) ON DBPARTITIONNUM (0). CLAIM_TIME ASC.Change tablespace (same as MMDB) .sh) 2. MEAS_OPE_NO ASC. RUNSTATS ON TABLE SIVIEW. STORE_TIME ASC ) PCTFREE 10 DISALLOW REVERSE SCANS. Stop Capture program (extract the script from /HAapps/hacmp/stopDBServer.#SYNC 50. use 'siview' as the schema (note for different usage. MEAS_MAINPD_ID ASC. MEAS_PASS_COUNT ASC.Change Target Load Option to 'ASNLOAD using the Export and Import Utilitie s" 5. MEAS_DCDEF_ID ASC. ensure that the HADR host name or IP address maps to the intended one. Th ese cannot be the same as the ports allocated to the instance.queue) # cd /usr/mqm/samp/bin # .Stop listeners associated with a Queue Managers # endmqlsr -m QMgrName Create a Queue Manager # crtmqm -q venus. To use the CLP to initialize HADR on your system for the first time: Determine the host name.QUEUE # . If a host has multiple network interfaces. host IP address. the BACKUP DATABASE and RESTORE DATABASE commands are used to initialize database SOCKS as a standby database. based on the existing database that is to be the primary./amqsget ORANGE. In the following example. an NFS mounted file system is accessible at both sites. In this case. Note: The instance names for the primary and standby databases do not have to be the same. HADR can be initialized through the command line processor (CLP)./amqsput ORANGE. Create the standby database by restoring a backup image or by initializing a spl it mirror. and the service name or port number fo r each of the HADR databases. You need to allocate separate HADR ports in /etc/services for each protected database. or by calling the db2HADRStart API.QUEUE Delete a Queue Manager #dltmqm QMgrName export MYTEMPQM=TESTQM export MYPORT=1600 export MQCHLLIB=/var/mqm/ crtmqm $MYTEMPQM strmqm $MYTEMPQM runmqlsr -m $MYTEMPQM runmqsc $MYTEMPQM << EOF DEFINE CHANNEL(NTLM) DEFINE CHANNEL(NTLM) ALTER CHANNEL(NTLM) DEFINE QLOCAL(TESTQ) EOF amqsputc TESTQ $MYTEMPQM hello world EOF endmqm -i $MYTEMPQM Initializing high availability disaster recovery (HADR) Use the following procedure to set up and initialize the primary and standby dat abases for DB2 High Availability Disaster Recovery (HADR).queue. The host name can only map to one IP address. the Set Up Hig h Availability Disaster Recovery (HADR) wizard in the Control Center.manager # strmqm # runmqsc # define qlocal (orange. Issue the following command at the primary database: backup db socks to /nfs1/backups/db2/socks Issue the following command at the standby database: restore db socks from /nfs1/backups/db2/socks replace history file The following example illustrates how to use the db2inidb utility to initialize the standby database using a split mirror . com hadr_service host2. You can specify the RELOCATE USING option to change one or more of the following configuration attributes: instance name. you must ensure that the standby remains in rollforward mode.ibm.com hadr_service host1.com hadr_service dbinst1 120 NEARSYNC 120 . This procedure is an alternative to the backup and rest ore procedure illustrated above. On the primary: HADR_LOCAL_HOST HADR_LOCAL_SVC HADR_REMOTE_HOST HADR_REMOTE_SVC HADR_REMOTE_INST HADR_TIMEOUT HADR_SYNCMODE HADR_PEER_WINDOW On the standby: HADR_LOCAL_HOST HADR_LOCAL_SVC HADR_REMOTE_HOST HADR_REMOTE_SVC HADR_REMOTE_INST HADR_TIMEOUT HADR_SYNCMODE HADR_PEER_WINDOW host1. Issue the following command at the standby database: db2inidb socks as standby Note: The database names for the primary and standby databases must be the same. Set the HADR configuration parameters on the primary and standby databases.of the primary database.ibm. REDIRECT. Note: It is very important that you set the following configuration parameters a fter the standby databases has been created: HADR_LOCAL_HOST HADR_LOCAL_SVC HADR_REMOTE_HOST HADR_REMOTE_SVC HADR_REMOTE_INST The following sample configuration is for the primary and standby databases. When using the RESTORE DATABASE command. However. issuing the START HADR command with the AS STANDBY option will fail. The following RESTORE DATABASE command options should be avoided when setting up the standby database: TABLESPACE. and database path. it is recommended that the REPLACE HIST ORY FILE option is used. It is recommended that you do not issue the ROLLFORWARD DATABASE command on the standby database after the restore operation or split mirror initialization.ibm. When creating the standby database using the RESTORE DATABASE command. If the databases are not identical.com hadr_service dbinst2 120 NEARSYNC 120 host2. When setting up the standby database using the db2inidb utility. An error will be returned if the START HADR command with the AS STANDBY option is attempted on the database after rollforward is stopped. INTO.ibm. you must not change the database name or the table s pace container paths. do not use the SNAPSHOT or MIRROR options. log path. and WITHOUT ROLLING FORWARD. This means that you cannot issue the ROLLFORWARD DATABASE comm and with either the COMPLETE option or the STOP option. The results of using a rollforward operation mi ght differ slightly from replaying the logs using HADR on the standby database. the standby database is started first. Click Start HADR. To open the Set Up High Availability Disaster Recovery (HADR) Databases wizard: From the Control Center expand the object tree until you find the database for w hich you want to configure HADR. or you can just use the wizard to initialize HADR. If you start the primary d atabase first. the settings on the stan dby database will reflect what is set on the primary database. expand the object tree until you find the database for which you want to manage HADR. The Manage High Availability Disaster Recovery window opens. Additional information is provided through the contextual help facility within t he Control Center. Connect to the standby instance and start HADR on the standby database. Right-click the database and click High Availability Disaster Recovery?Manage i n the pop-up menu. The Start HADR window opens. Creating Source and Target Q Manager # crtmqm SRC_QM # crtmqm TGT_QM # strmqm sRC_QM # strmqm TGT_QM 2.If they are set prior to creating the standby database. Note: You can start HADR within the Set Up High Availability Disaster Recovery D atabases wizard. as in th e following example: START HADR ON DB SOCKS AS PRIMARY HADR is now started on the primary and standby databases. as in th e following example: START HADR ON DB SOCKS AS STANDBY Note: Usually. Creating Sourece Queue # runmqsc SRC_QM # DEFINE QLOCAL ('ADMINQ') DEFPSIST(YES) # DEFINE QLOCAL ('RESTARTQ') DEFPSIST(YES) # DEFINE QLOCAL('TGT_QM') USAGE(XMITQ) DEFPSIST(YES) # DEFINE QREMOTE('SENDQ') RNAME('RECVQ') RQMNAME('TGT_QM') XMITQ('TGT_QM') DEFP SIST(YES) 3. this startup procedure will fail if the standby database is not started within the time period specifie d by the HADR_TIMEOUT database configuration parameter. Connect to the primary instance and start HADR on the primary database. # # # Creating Target Queue runmqsc TGT_QM DEFINE QLOCAL('RECVQ') DEFPSIST(YES) DEFINE QLOCAL('SRC_QM') USAGE(XMITQ) DEFPSIST(YES) . To open the Start HADR window: From the Control Center. then start it at another time. Right-click the database and click High Availability Disaster Recovery ? Set Up in the pop-up menu. DB2 Check Backup Integrity #db2ckbkp Setting up Q Replication 1. The Set Up High Availability Disaster Recovery Databases wizard opens. accept the default Q Capture schema of ASN. Creating Sourece and Target control tables Create the Q Capture control tables. On the Enter Queues page. click Programs > IBM DB2 > General Administration Tools > Replication Center. and click Next. click the Q replication icon. including its set of control tables.SPILL.TGT_QM') CHLTYPE(SDR) TRPTYPE(TCP) CONNAME ('IP_addres s(port)') XMITQ('TGT_QM') DISCINT(0) Important: Replace IP_address with the IP address of your computer and replace p ort with 1450 or the alternate port that you determined earlier.TO.SRC_QM') CHLTYPE(RCVR) TRPTYPE(TCP) # runmqsc TGT_QM # DEFINE CHL ('TGT_QM.MODELQ') DEFSOPT(SHARED) MSGDLVSQ(FIFO) DEFTYPE( PERMDYN) 4.TGT_QM') CHLTYPE(RCVR) TRPTYPE(TCP) 5.TGT_QM) end runmqlsr -t tcp -m TGT_QM -p 1450 runmqsc TGT_QM start channel (TGT_QM.TO. Click the buttons next to the Adminis tration queue and Restart queue fields to select the ADMINQ and RESTARTQ queues that you previously created. # # # # # # # # # # Starting Up MQ strmqm SRC_QM strmqm TGT_QM runmqlsr -t tcp -m SRC_QM -p 1451 runmqsc SRC_QM start channel (SRC_QM. Schema refers to an instance of the Q Capture or Q Apply program. Figure 1. UNIX®. o r from the Windows® Start menu. and Windows. Click the Create Q Capture Control Tables button.# DEFINE QREMOTE('ADMINQ') RNAME('ADMINQ') RQMNAME('SRC_QM') XMITQ('SRC_QM') DE FPSIST(YES) # DEFINE QMODEL('IBMQREP.SRC_QM') CHLTYPE(SDR) TRPTYPE(TCP) CONNAME('IP_address (port)') XMITQ('SRC_QM') DISCINT(0) Important: Replace IP_address with the IP address or host name of your computer and replace port with 1451 or the alternate port that you determined earlier. On the Replication Center Launchpad. You can use the db2rc command on all platforms. Figure 2.TO. . Click the button next to the Queue manager field to select the SRC_QM queue manager. Entering server information in the Create Q Capture Control Tables wiz ard The term server in the Replication Center refers to a DB2® database on Linux®. accept the defa ult choice of Typical.SRC_QM) end Setting up Q Replication 1. You can have multiple schemas on a server. administration queue. # DEFINE CHL ('TGT_QM. and click Next. Creating MQ Channels # runmqsc SRC_QM # DEFINE CHL ('SRC_QM. and r estart queue for the source system. On the Server page. Launch the Replication Center. Type a valid user ID and password for connecting to th e database.TO.TO. On the Start page of the Create Q Capture Control Tables wizard.TO. and to a DB2 subsystem on z/OS®. specify the queue manager. and se lect the SAMPLE database. # DEFINE CHL ('SRC_QM. click the button next to the Q Capture server field. Specifying names for the queue manager and queues Optional: Click the Validate WebSphere MQ objects link to test if your WebSphere® MQ objects can communicate properly. Type a valid user ID and password for connecting to th e database. You should see a confirmation messa ge that the scripts ran successfully. which shows the suggested naming convention . Create the Q Apply control tables. and sele ct the TARGETDB database. click OK. The Create Repl ication Queue Map window opens. Note: The backup process can take several minutes. On the General page. If the Launchpad is no longer on your screen. Enabling the source database for replication To turn on archive logging at the SAMPLE database: Close the Replication Center Launchpad. On the Run Now or Save SQL window. The Replication Center does the following tasks: Forces all applications off the SAMPLE database Turns on archive logging (which puts the database in a backup pending state) Backs up the database to the default DB2 installation directory Deletes the backup. 3. accept the default Q Apply schema of ASN. If you want to save the backup. click Replication Center > Launchpad. Creating Replication Queue Map To create a replication queue map: In the Replication Center object tree. 2. and in the Replication center object tre e use the icons to expand the folders in the following order:Q replication > De finitions > Q Capture Servers > SAMPLE Right-click the SAMPLE icon and choose Enable database for replication. from the Replication Center menu. click OK. Figure 3. Figure 1. Replication Center object tree opened to display Replication Queue Map s folder Right-click the Replication Queue Maps folder. and click Create. On the Start page of the Create Q Apply Control Tables wizard. use the icons to open folders in the fol lowing order: Q replication > Definitions > Q Capture Servers > SAMPLE > Q Captu re Schemas > ASN. Selecting and validating the queue manager on the Queue Manager page Click Next. On the Server page. select Use Configure Logging wizard to launch th e DB2 wizard that lets you specify backup options. and click Next. you will create the replication queue map. Optional: Click the Validate queue manager link to test the settings of your que ue manager. Click Finish to generate the SQL script for creating the control tab les.Click Next. click the button next to the Q Apply server field. Click Create Q Apply Control Tables. Click Finish to generate the SQL script for creating the control tab les. click the button next to the Queue manager field and select the TGT_QM queue manager. On the Run Now or Save SQL window. accept the defaul t choice of Typical. In the Turn on Archive Logging window. click OK. Figure 4. click the button next to the Q Apply server field and sele ct the TARGETDB server. Next. You should see a confirmation messa ge that the scripts ran successfully. Entering server information in the Create Q Apply Control Tables wizar d On the Enter Queues page. The Replication Queue Map Name field is filled in with t he value SAMPLE_ASN_TO_TARGETDB_ASN. and click Next. You defined the mapping between the EMPLOYEE table at the SAMPLE database and th e newly created EMPLOYEE table at the TARGET database. On the Loading Target Tables page. If the Repli cation Center Launchpad is not visible. and click Next. On the Servers page. Figure 1. On the Unexpected Conditions page of the wizard. This mapping was automati cally named EMPLOYEE0001 and is the name of the Q subscription. If any of these values are missing. cli ck the buttons next to the appropriate field to select the object. Enter or select your queues. Y ou are almost ready to replicate data. Figure 2. A ccept the default replication type of Unidirectional. You also defined the queue pathway that will be used to replicate data between the two tables. cha nge the Table name field to EMPLOYEE. review your choices. accept the default setting of Use a table and New table. click Next to open the Replication page. cli ck Retrieve. Entry fields on the Create Replication Queue Map notebook Optional: Click the Validate queues link to validate the queues and send test me ssages between the queues. and attributes. To create a Q subscription: On the Replication Center Launchpad. and click OK. click Next. On the Source Tables page. verify that the SAMPLE and TARGETDB databases appear in the Server fields and that the SAMPLE_ASN_TO_TARGETDB_ASN replication queue map app ears in the Replication queue map field. click Create a Q Subscription. On the Create Q Subscriptions wizard. On the Run Now or Save SQL window. Click the button next to the Send queue field and select the SENDQ queue that y ou previously created. Click the button next to the Receive queue field and select the RECVQ queue tha t you previously created. accept the default values and c lick Next. Summary page On the Run Now or Save SQL window. and click Next.. The Select Source Table window will open in front of the Source Tables page. Select the EMPLOYEE table from the list and click OK. and click Finish. DB2 Memory Track #db2mtrk -i -d DB2 monitoring parameters: Buffer pool size Dynamic cache size Heap sizes Locklist and maxlocks sizes Lock mode and isolation issues Disorganized table spaces . click OK. click Replication Center > Launchpad. accept the defaults and click Next. On the Target page. The Review Q Subscriptions page showing a valid Q subscription Click Next to get to the Summary page. Figure 2. click OK. data types. Click the button next to the Administration queue field and select the ADMINQ q ueue that you previously created. The Replication Center aut omatically creates the target table for you and handles all of the mappings betw een columns. Accept the other defaults on the Options page. 4. On the Rows and Columns page. accept the defaults and click Next. log 2> /db2instance/db2home/pmsinst/adm/ stopCaptureSMDB.repinst -c 'cd /db2instance/db2home/repinst/apply.err' #su .sh > sta rtCaptureSMDB.sh > /db2instance /db2home/repinst/apply/stop_apply.sh > /db2inst ance/db2home/spcinst/capture/stop_capture.sh > st art_apply. start_capture.sh > start_ apply. startCaptureSMDB.log 2> start_catpure. start_capture.err' #### stop PMS replication process echo "stoping PMS replication process\n" su .Outdated runstats Long running SQL Log and table space utilization #### Start PMS replication process echo "starting PMS replication process\n" #su . start_apply.log 2> start_apply.log 2> /db2instance/db2home/mminst/captur e/stop_capture.sh > /db2instan ce/db2home/sminst/capture/stop_capture.sh > /db2instanc e/db2home/pmsinst/adm/stopApplySMDB.sh > /db2inst ance/db2home/repinst/apply_spc/stop_apply.err' su .sh > star t_capture.err' #su .err' #su .log 2> start_catpure.spcinst -c '/db2instance/db2home/spcinst/capture/stop_capture.pmsinst -c 'cd /db2instance/db2home/pmsinst/adm.mminst -c 'cd /db2instance/db2home/mminst/capture. start_capture.err' su .err' #su .sh > st art_capture.pmsinst -c '/db2instance/db2home/pmsinst/adm/stopApplySMDB.sh > /db2insta nce/db2home/pmsinst/adm/stopCaptureSMDB.log 2> /db2instance/db2home/sminst/captur e/stop_capture.mminst -c '/db2instance/db2home/mminst/capture/stop_capture.repinst -c 'cd /db2instance/db2home/repinst/apply_spc.log 2> /db2instance/db2home/repinst/ apply_smdb/stop_apply.log 2> /db2instance/db2home/repinst/apply/stop _apply.err' .err' #su .sh > star t_capture. start_apply.log 2> /db2instance/db2home/repinst/ap ply_spc/stop_apply.sh > s tart_apply.repinst -c 'cd /db2instance/db2home/repinst/apply_smdb.repinst -c '/db2instance/db2home/repinst/apply/stop_apply.err' su .log 2> /db2instance/db2home/sminst/cap ture/stop_capture.log 2> start_apply.err' su .log 2> start_catpure.sminst -c '/db2instance/db2home/sminst/capture/stop_capture. startApplySMDB.err' #su .sh > start ApplySMDB.sh > /db2ins tance/db2home/repinst/apply_smdb/stop_apply.sminst -c 'cd /db2instance/db2home/sminst/capture.log 2> startApplySMDB.pmsinst -c '/db2instance/db2home/pmsinst/adm/stopCaptureSMDB.repinst -c '/db2instance/db2home/repinst/apply_smdb/stop_apply.log 2> /db2instance/db2home/pmsinst/adm/stop ApplySMDB. start_apply.log 2> startCatpureSMDB.err' #### Start local Reporting Replication Process echo "starting local reporting replication process\n" #su .err' su .pmsinst -c 'cd /db2instance/db2home/pmsinst/adm.err' su .sh > /db2instan ce/db2home/mminst/capture/stop_capture.log 2> start_apply.spcinst -c 'cd /db2instance/db2home/spcinst/capture.err' #### stop local reporting replication process echo "stoping local reporting replication process\n" su .repinst -c '/db2instance/db2home/repinst/apply_spc/stop_apply. Create another folder call /home/udb/. Set the rights of ~/.sql asnqacmd apply_server=FDB_PROD apply_schema= QAPROD startq=" SYSB. cat /id_rsa.ssh 3.sql smdb -a -e -l -x -f -o db2look_smdb_20080212./ssh/*. Restart the SSH services Problem Determination Steps 1.This means the home folder rights must only be 755 2.pub >> .pub >> . In the remote host. Set the rights /home/udb 755 /home/udb/. Call by: db2 stvf <scriptname> .ssh/* 600 5.ssh/authorized_keys 3.ssh/authorized_keys 4. But the home directory for udb (/kla-tencor/udb) for some reasons is configur ed as 777 drwxrwxrwx 18 udb udb 1024 Feb 1 12:05 udb Solution 1.ssh/* to 600 cd .sql schdb -a -e -l -x -f -o db2look_schdb_20080212. Copy the authorized_keys in /home/udb/. generate the private/public keys ssh-keygen -t rsa ssh-keygen -t dsa ssh-keygen -t rsa1 2. Copy the public keys to the remote host scp .sql edatdb -a -e -l -x -f -o db2look_edatdb_20080212. Feb 1 12:07:52 sscm1pa sshd[3275]: Authentication refused: bad ownership o r modes for directory /home/udb #iostat -a 2 5 # # # # # # # db2look db2look db2look db2look db2look db2look db2look -d -d -d -d -d -d -d mmdb -a -e -l -x -f -o db2look_mmdb_20080212. Give ownership of /home/udb to user udb 4. Configure the /etc/opt/ssh/sshd_config AuthorizedKeysFile /home/udb/.ssh/authorized_keys cat /identity./.pub user@remote_host:/$HOME/.sql mmrdb -a -e -l -x -f -o db2look_mmrdb_20080212. In the local host.sql emntdb -a -e -l -x -f -o db2look_emntdb_20080212.ssh 700 /home/udb/. See the logs /var/adm/syslog/syslog E.ssh/authorized_keys 6./ssh chmod 700 . so that SiView Interface Adapter can call Klari ty SendEvent executable/script Steps to setup password-less SSH Access 1. The sshd_config is configured as StrictModes yes .QPRODTATAQ" These scripts generate the Q subscriptions.ssh 2.g./. chmod 600 * Where it did not work for UDB user 1. append.pub >> .sql spcdb -a -e -l -x -f -o db2look_spcdb_20080212.ssh to 700 and ~/.ssh/authorized_keys cat /id_dsa./.Requirement Enable Password-less SSH Access. first of all check if all MQ objects are available and runnin g. $ nsu 3. and if Stop Capture was define d as error action in the Queue Map. If problems occur. In this case. description = '' WH ERE repqmapname = 'MMRDB_QCPROD_TO_FDB_PROD_QAPROD'".ddl This section contains some troubleshooting hints and tips. two reasons cause Apply to detect missing messages and wait: Messages went to the DEAD LETTER queue Messages were cleared from a queue How to re-activate an inactive data queue? asnqacmd apply_server=server_name apply_schema=schema startq=receive_queue_name For example: asnqacmd apply_server=FDB_DEV apply_schema=QFDBDEV1 startq="SYSB.QMRDEVTATAQ" #rmdev -dl proc2 # cfgmgr -v # lsdev -Cc processor temp root passwd 1. or investigate why Apply does not fetch the messages from the queue. you increase the maximum number of messages allowed.IBMQREP_RECVQUEUES SET memory_limit = 64. SSA5DBP2:root:/>vmo -a maxfree minfree SSA5DBP2:root:/>vmo -a maxperm maxperm% minperm minperm% strict_maxperm SSA5DBP2:root:/>vmo -p Setting maxperm% to 90 | grep free = 6528 = 5760 | grep perm = 5507607 = 80 = 1376899 = 20 = 0 -o maxperm%=90 in nextboot file . passwd: 63223asEWQ db2 "UPDATE QAPROD. hprrolim/63223ASewg 2. If Capture cannot put messages into the send queue.db2 connect to mmdbdev user <userid> using <password> db2 stvf full_refresh. A reason could be that the queue already contains the maximum number of messages allowed (CURDEPTH = MAXDEPTH). Do use tools like the Websphere MQ Explorer (Windows only) or MQSC commands (like DISPLAY QUEUE) to display the numb er of messages in a queue. Runtime problems are most often caused by unavailable MQ objects. The MQ objects are Queue Manager(s) (local and remote setup) Channels (remote setup only) Listeners (remote setup only) If all objects are up and running but is does not replicate. the Capture stops. check the MQ messag es. Apply detects missing messages automatically and only continues to process and r eplicate changed data when the missing messages reoccur. Mainly. 015970 2008-01-23-20.12.12. CALL SYSPROC.NULL.449128 2008-01-23-20.?).12.21.0.240450 2008-01-23-20.11.'FRCODE'. vmo vmo vmo Let vmo vmo vmo vmo -p -o minperm%=3 -p -o maxperm%=90 -p -o maxclient%=90 strict_maxperm and strict_maxclient default -p -o minfree=960 (960= minimum.34.389532 2008-01-23-20.11.11.NULL. CONNECT RESET.11. Warning: changes will take effect only at next reboot CONNECT TO FDB_PROD USER "db2inst2".'SIVIEW'.149171 2008-01-23-20.903142 2008-01-23-20.43.297157 2008-01-23-20.NULL.07.686821 2008-01-23-20.476099 2008-01-23-20. multiply by x number of mempools) -p -o maxfree=1088 (1088= minimum.IBMQREP_DONEMSG WITH DISTRIBUTION" Run bosboot now? y bosboot: Boot image is 25202 512 byte blocks.11.multiply by x number of mempools) -p -o lru_file_repage=0 -p -o lru_poll_interval=10 amqsputc SYSB.12.27.175648 2008-01-23-20.Setting maxperm% to 90 SSA5DBP2:root:/>vmo -p -o minperm%=3 Setting minperm% to 3 in nextboot file Setting minperm% to 3 SSA5DBP2:root:/>vmo -a | grep lru lru_file_repage = 1 lru_poll_interval = 10 lrubucket = 131072 SSA5DBP2:root:/>vmo -p -o lru_file_repage=0 Setting lru_file_repage to 0 in nextboot file Setting lru_file_repage to 0 SSA5DBP2:root:/>vmo -a | grep maxcl maxclient% = 80 strict_maxclient = 1 SSA5DBP2:root:/>vmo -p -o maxclient%=90 Setting maxclient% to 90 in nextboot file Setting maxclient% to 90 SSA5DBP2:root:/>vmo -a | grep page_st page_steal_method = 0 SSA5DBP2:root:/>vmo -r -o page_steal_method=1 Setting page_steal_method to 1 in nextboot file Warning: some changes will take effect only after a bosboot and a reboot IBMQREP_APPLYENQ IBMQREP_APPLYMON IBMQREP_APPLYPARMS IBMQREP_APPLYTRACE IBMQREP_DONEMSG IBMQREP_EXCEPTIONS IBMQREP_RECVQUEUES IBMQREP_SAVERI IBMQREP_SPILLEDROW IBMQREP_SPILLQS IBMQREP_TARGETS IBMQREP_TRG_COLS QAPROD QAPROD QAPROD QAPROD QAPROD QAPROD QAPROD QAPROD QAPROD QAPROD QAPROD QAPROD T T T T N N N N N N N N 2008-01-23-20.12.NNSTAT('FBSIVBID'.38.34.34.817854 db2 "runstats on table QAPROD.32.460750 2008-01-23-20.12.34.15.QMRDEVERPTATAQ QMRERPDEV .48.12. In the r emote host./ssh/*. Copy the public keys to the remote host scp . Set the rights of ~/.ssh 2.set MQSERVER=QMRDEVERP.pub >> .pub >> .This means the home folder rights must only be 755 2.QMRDEVERPTATAQ asnqanalyze -db FDB_ERP -la detailed Requirement Enable Password-less SSH Access. Create another folder call /home/udb/.g. chmod 600 * Where it did not work for UDB user 1.ssh/* to 600 cd . generate the private/public keys ssh-keygen -t rsa ssh-keygen -t dsa ssh-keygen -t rsa1 2. See the logs /var/adm/syslog/syslog E.QMRDEVERPTATAQ asnqacmd apply_server=FDB_ERP apply_schema=QAERP startq=SYSB.ssh/authorized_keys cat /identity./.ssh/authorized_keys 6. In the local host. Copy the authorized_keys in /home/udb/.40.204(1434)' asnqacmd apply_server=FDB_ERP apply_schema=QAERP stopq=SYSB. Feb 1 12:07:52 sscm1pa sshd[3275]: Authentication refused: bad ownership o r modes for directory /home/udb SSA5DBP1:spcinst:/db2instance/db2home/spcinst>db2 update db cfg using LOGPRIMARY 5 .pub user@remote_host:/$HOME/.ssh/* 600 5.pub >> . Set the rights /home/udb 755 /home/udb/. The sshd_config is configured as StrictModes yes ./ssh chmod 700 .SYSACHNL/TCP/'10./.ssh/authorized_keys 3. But the home directory for udb (/kla-tencor/udb) for some reasons is configur ed as 777 drwxrwxrwx 18 udb udb 1024 Feb 1 12:05 udb Solution 1.ssh/authorized_keys 4.ssh 3. so that SiView Interface Adapter can call Klari ty SendEvent executable/script Steps to setup password-less SSH Access 1.ssh 700 /home/udb/. cat /id_rsa. append.24.ssh to 700 and ~/. Configure the /etc/opt/ssh/sshd_config AuthorizedKeysFile /home/udb/. Restart the SSH services Problem Determination Steps 1.ssh/authorized_keys cat /id_dsa. Give ownership of /home/udb to user udb 4./. and the reason code is "". db2flsn 019CACC03524 db2flsn 0001FCDC3F62 . Create a mount_klarityresults.IBMSNAP_RESTART Result may look something like this: MIN_INFLIGHTSEQ ----------------------x'00000000019CACC03524' x'000000000001FCDC3F62' 2.35.714074 <logrd::readTheLog> ASN0005E CAPTURE "ASN" : "WorkerThread". === These errors indicate that the log file Capture needs is unavailable.54. all applications must disconnect from this database before the changes become effective.54. #ipclean Why is Capture failing with ASN0005E/SQL2656N messages? Answer The messages in the Capture log file may look similar to these messages: === 2007-07-23-07. SELECT MIN_INFLIGHTSEQ from ASN. The instructions below should resolve the problem: === 1. the highest log sequence number of a successfully captured log record is "469F:ED0C:0000:000D:0000" and the lowest log sequence number of a record still to be committed is "0000:0000:004D:E01B:FFB3". For example.33.714025 <logrd8::readTheLog> ASN8041D "Capture" : "ASN" : "WorkerThread" : db2LogRead API is sending us backwards in the DB2 Log: First LSN is "0000:0000:004d:e01b:ffb3" while Next Start LSN is "0000:0000:0000:0000:0000" 2007-07-23-07.212\klarityresults /user:siview siview Then put this batch file in the Start > Programs > Startup. SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically.54. 2007-07-23-07. The log sequence number is "0000:0000:004D: E01B:FFB3". the SQLCODE is "-2656".DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.33.714201 <CWorkerMain> ASN0123I CAPTURE "ASN" : "WorkerThread". For these configuration parameters. Run db2flsn to determine which log file Capture needs.33.40. At program termination.714074 <logrd::readTheLog> ASN8999D "Capture" : "ASN" : "WorkerThread" : 2007-07-23-07.54. The Capture program encountered an error when reading the DB2 log.54. 2007-07-23-07.bat batch file with the following command net use z: \\10.714145 <CWorkerMain> ASN0589I "Capture" : "ASN" : "WorkerThread" The program received an unexpected return code "910" from routine "logtxrdr::getTrans".33.33. 110. Copy this log file and subsequent files back into active log directory.LOG.0. db2pd -alldbs -hadr 2:43:55 PM: [email protected] route add 10.com .0 10.0.0 mask 255.0 192. Restart Capture.40.0.0.40.db2flsn 005DD6CF8828 Note: Either copy SQLOGCTL.168. UNIX.0.40. LSN) = S0000001. This manual can be found at #asnanalyze -db mmrdb -la detailed # asnqacmd apply_server=fdb_erp apply_schema=QAERP startq="SYSB.0 10. Windows.0. z/OS)" in Chapter 14 of the "SQL Replication Guide and Reference V8.0 mask 255.0 mask 255.1 route add 80.ibm.65.255.Chaitali Nandan/India/IBM: this will giv e you : Primary log position(file. page. === The section titled "Retaining log data (Linux.0.110.QMRDEVERPTATAQ" route add 0. db2 get sn apshot for all on <dbname> 2:44:17 PM: chaitalinandan@in. The LSN must be 12-bytes.0 mask 0. 0000000000BB800 .QMRDEVRESTART QMRDEV asnqcap capture_server=mmdb capture_schema=QCDEV LSN=0000:0000:0005:71aa:b75c MA XCMTSEQ=48a2:fd4c:0000:0005:0000 asnqcap capture_server=mmrdb capture_schema=QCERP LSN=0000:0000:001C:0383:C862 M AXCMTSEQ=48A9:55E7:0000:0003:0000 asntrc -help asntrc on -db mmdb -app -qualifier MIXQUAL -b 5M "asncap capture_server=sourcedb capture_schema=ASN debug=y logstdout > cap.0. 4. 0. 3.40.0. 2.com .ibm.0.110.255.1 asnqmfmt SYSA.Chaitali Nandan/India/IBM: 3.0 10.255.2" is helpful to understand ho w long to keep DB2 logs.40.LFH (log header control file) into current directory or cd into the directory where this resides before running db2flsn.1.1 route add 10. check the active and paths on primary and standby to check whether logs are being shipped correctly.trc" db2 uncatalog db SPCDB db2 catalog tcpip node MMRDBSRV remote SSA5DB server 58010 # db2 catalog db MMRDB as MMRDB at node MMRDBSRV authentication server db2 catalog db SPCDB as SPCDB on path '/home/tstinst/SPCDB' authentication serve r db2 catalog db MMDB as MMDB on path '/home/tstinst/MMDB' authentication server 1. fnt package.LOG.LOG 1 0x000 0007D123E0000 check IPC key #ipcs | grep xxxx remove IPC key #ipcrm -q ID #db2 bind @udbubind.ibm.lst datetime ISO blocking all grant public need to do to /home/db2inst1/sqllib/bnd #list wmb components running mqsilist # create broker db mqsicreatedb BRKDB1 -i userid -a password -e dbtype #create configuration manager mqsicreateconfigmgr CONFIG_MANAGER -i userid -a password -q queuename #start configuration manager mqsistart CONFIG_MANAGER #start broker mqsistart BROKER1 #change configuration manager mqsichangeconfigmgr -a <ServicePassword> -i <ServiceUserID> -j <MaxJVMHeapSize> To verify all files that comprise the X11.fnt To verify the symbolic links of all software products whose names begin with X11 .com . page. enter: #lppchk -c X11.Chaitali Nandan/India/IBM: in the optio n 2 above . values to observe : PrimaryFile PrimaryPg PrimaryLSN StandByFile Stan dByPg StandByLSN S0000001. enter: #lppchk -l 'X11*' To verify that all filesets have all required requisites and are completely inst alled. 00000000007D123E 2:44:56 PM: chaitalinandan@in. LSN) = S0000000. enter: #lppchk -v Determine which filesets are missing using the command #oslevel -rl 5100-05 An alternative to oslevel -r : You can use instfix to determine the missing filesets as shown in the following example : #instfix -ciqv | grep 5200-02_AIX_ML | grep :-: #lsvg -p rootvg (lists physical partition allocation for each section) #lsvg rootvg (lists rootvg information) .LOG 0 0x000000BB80000000 S0000000. 1.0 Standby log position(file. Physical Volume Commands #pvcreate Initialize a disk as a Physical Volume. This can be done to recognize hot pluggable drives that were added after the system was up. or can be used to recognize devices such as external tape or disk drives that were not powered on when the system was booted up. #cfgmgr Re-scan the system for devices that were not available at system start u p. #extendvg Add PVs to a volume group. #reducevg Remove unused PVs from a volume group. it can give detailed information about a particular VG.#lsvg -l rootvg #bootlist -m normal -o (this will list the normal boot list) #unmirrorvg rootvg hdiskx If there are remaining LVs on the alternate disk. or can be used when moving a disk or disks from one syst . This must be done prior to add ing a disk to a volume group. #chvg Change volume group characteristics. the "migratepv" command can be used to move the LV o nto another disk in the VG provided there is enough space to do so. #lspv Display the Physical Volumes on a system. it lis ts all volume groups on the system. Volume Group Commands #lsvg List information about logical volumes. When given a PV name as a parame ter. This can be used o n removable disks such as optical disks or Iomega Jaz drives prior to removing t he drive from a system. it gives detailed information about that PV. migrate logical volumes using: # migratepv -l lv_name source_disk target_disk #shutdown -Fr #lppchk -v #oslevel -r #instfix -I | grep ML or TL #errpt | more #bootlist -m normal -o (the disk with rootvg must be the first on the list) List VG details: lsvg <vgname> List LVs within VG: lsvg -l <vgname> List PV within VG: lsvg -p <vgname> Lists physical group names: lspv List PV details: lspv hdiskN List LVs within PV: lspv -l hdiskN List PP within PV: lspv -p hdiskN Lists LV names: lsvg -l <vgname> List LV details: lslv <lvname> List LVs within PV: lslv -l <lvname> List PP within PV: lslv -p <pvname> Show mirrored LV: lslv -m <lvname> Device Commands #lsdev The "lsdev -Cc disk" command can be used to display the what disks are re cognized by the system. This will display disks whether they have been initializ ed as PVs or not. When given parameters. When given with parameters. If logical volumes currently re side on the PV in question. This is done to remove the device configuration when a faulty disk is replaced. or if a disk is moved to a nother system. #rmdev Remove a device from the system configuration. #mkvg Create a volume group. #exportvg Remove knowledge of a volume group from the Kernel. including information about what logical volu mes are in that volume group. In order to list information about all logical volumes. Set the Capture RETENTION_LIMIT and LAG_LIMIT values to their maximum. #importvg Re-initializes kernel knowledge of a volume group that had been previo usly exported. as shown in the following SQL statement: UPDATE ASN. and then use "lsvg -l <vgname>" on each volume group. CCD_OLD_SYNCHPOINT=x'00000006F5638E600000' WHERE GLOBAL_RECORD='N'. A logical volume name must be spe cified.55. #mirrorvg Creates mirror volumes for all volumes in a volume group. CD.43. #extendlv Increase the size of a logical volume. and becomes accessible once it has been imported.IBMSNAP_SUBS_SET SET .43. #rmlv Delete a logical volume.316970 is the timestamp from which you send the Capture program back to start reading the log. This allows for RAID-1 in software. #mklv Create a logical volume.data file (generated by the mkszfile command) to a tape device named /dev/rmt0. #unmirrorvg Removes a mirror from each volume in a volume group. Logical Volume Commands #lslv Lists information about logical volumes. 00000006F5638E60000 is the log sequence number and 2009-09-05-09. you would need t o use "lsvg" to list all volume groups.55. its associated logical volume.LAG_LIMIT=99999. In the following example. IBMSNAP_REGISTER. UPDATE ASN. and its entry in /etc/ filesystems. This command can be used to create a file system on an existing logical volume. enter: #mksysb -i /dev/rmt0 Create a boot image on the newly added disk #bosboot -ad /dev/hdiskx Starting the Capture program from a known point in the DB2 log Stop the Capture and Apply programs. File System Commands #crfs Create a file system.em to another. This can be used to increase the size of a file system. or it can be used as an all in one command to create both a logical volume and file system at once. #chfs Change file system characteristics.IBMSNAP_CAPPARMS SET RETENTION_LIMIT=99999. #rmlvcopy Removes a mirror copy of a logical volume. SYNCHTIME=TIMESTAMP('2009-05-05-09. You could then use "lslv <lvname>" to list the detailed informatio n about each logical volume found. use SQ L to set the value to the point from which you want to start recapturing transac tions. Paging Space Commands #lsps Lists information about paging space volumes. #chlv Change the characteristics of a logical volume. #mklvcopy Mirror a logical volume.316970'). The data in the VG is left intact. The existing logical volume names are used unless they confl ict with logical volumes currently in use on the system. and IBMSNAP_PRUNCNTL t ables are higher than the LSN value from which you want to start Capture. #rmfs Remove a filesystem. The data on the VG is left intact.IBMSNAP_REGISTER SET CD_OLD_SYNCHPOINT=x'00000006F5638E600000'. CD_NEW_SYNCHPOINT=x'00000006F5638E600000'.IBMSNAP_REGISTER SET SYNCHPOINT = x'00000006F5638E600000. UPDATE ASN. If the SY NCHPOINT values in the IBMSNAP_UOW. UPDATE ASN. To generate a system backup and create an /image. SYNCHTIME=TIMESTAMP('2009-05-05-09.x'00000006F5638E600000'.TBSPACE.00. db2 export to FHWCPHS.00.1.55.TBSPACEID=TB.000000'" db2 export to FHWLTHS.00.IBMSNAP_RESTART (MAX_COMMITSEQ. db2 restore db mmrdb use tsm taken at 20100405204018 to /home/mmrdb without prom pting db2 rollforward db mmrdb to end of logs and complete db2 "SELECT SUBSTR(TBS.00.43.00. SYSCAT.24) AS TABNAME.43.log file #db2instance\db2home\repinst\sqllib\db2dump STEP 1: connect to SSA5DB.ixf of ixf commitcount 20000 "INSERT INTO FHWLTHS" db2 terminate. db2diag.1.00.IBMSNAP_PRUNE_SET SET SYNCHPOINT =x'00000006F5638E600000'. MIN_INFLIGHTSEQ.TABNAM E.CURR_COMMIT_TIME.316970').IBMSNAP_UOW.000000'" db2 import from FHWCPHS.43.43. LASTSUCCESS=TIMESTAMP('2009-05-05-09.1. SUBSTR(TB.43. DELETE FROM ASN.316970').55.316970') WHERE WHOS_ON_FIRST='S' AND SET_NAME='BACK1'.TBSPACE IN ('U SERSPACE1'.000000' and CLAIM_TIME < '2010-04-05-15. SUBSTR(TB. SYNCHTIME=TIMESTAMP('2009-05-05-09.00.000000' and CLA IM_TIME < '2010-04-05-15.43.out Please run the following: db2pd -db MMRDB -tablespaces -alldbp >db2pd-tablespaces.TBSPACEID.00.TBSPACEID AND TBS.LASTRUN=TIMESTAMP('2009-09-05-09.55.24) AS TABSCHEMA FROM SYSCAT.316970').000000'" db2 terminate.000000'" db2 "DELETE FROM FHWLTHS WHERE CLAIM_TIME > '2010-04-04-09. UPDATE ASN.00.00.00.00.TABLESPAC ES TBS. TBS.00.ixf of ixf "SELECT * FROM FHWCPHS WHERE CLAIM_TIME > '2010 -04-04-09.43.00.316970'.00. log in using mminst db2 connect to MMDB user siview using siview.55.TABSCHEMA. db2 "DELETE FROM FHWCPHS WHERE CLAIM_TIME > '2010-04-04-09. STEP 2: connect to SSA5DB.TABLES TB WHERE TBS.ixf of ixf "SELECT * FROM FHWLTHS WHERE CLAIM_TIME > '2010 -04-04-09. SYNCHPOINT=x'00000006F5638E600000'.000000' and CLA IM_TIME < '2010-04-05-15.'QASNTBSP')" >tables_tablespaces.IBMSNAP_PRUNCNTL SET SYNCHPOINT =x'00000006F5638E600000'.316970').55.55. MAX_COMMIT_TIME. UPDATE ASN.24) AS TBSPACE. SYNCHTIME=TIMESTAMP('2009-05-05-09.out db2adutl query db MMRDB VERIFY HEADERONLY TAKEN AT 20100405204018 db2adutl query db MMRDB VERIFY TABLESPACESONLY TAKEN AT 20100405204018 . log in using repinst db2 connect to MMRDB user siview using siview.CAPTURE_FIRST_SEQ) values (x'00000006F5638E600000'.00.316970'.ixf of ixf commitcount 20000 "INSERT INTO FHWCPHS" db2 import from FHWLTHS. x'00000006F5638E600000').'2009-05-05-09.000000' and CLAIM_TIME < '2010-04-05-15. '2009-05-05-09.55. INSERT INTO ASN. TABLESPACES AS TBSPACES WHERE TABLES.db2adutl VERIFY HEADERONLY TAKEN AT 20100405204018 DATABASE MMRDB WITHOUT PROMPT ING > verify1.TABSCHEMA. determine tablespace from table name #db2 "SELECT TABLES. and applications. TBSPACES.vmdk Importing a virtual disk inside VMware ESX Server 2: vmkfstools -i /vmfolder/vmdiskfile.TBSPACE FROM SYSCAT.logs date >> restore_again.TABNAME.sql Exporting a virtual disk from VMware ESX Server 1: vmkfstools -e /vmfolder/exportvmdiskkfilename.logs db2adutl QUERY FULL DATABASE MMRDB > query1.50 and complete 2>> restore_again.logs db2adutl VERIFY TABLESPACESONLY TAKEN AT 20100405204018 DATABASE MMRDB WITHOUT PRO MPTING > verify2.TBSPACE ID AND TABNAME = 'SALES'" #db2mtrk -d -v db2mtrk orts. -d mmrdb -c -g -s # db2look -d mmrdb -a -e -l -x -f -o db2look_mmrdb.l ogs 1>> restore_again. SYSCAT. you can register virtual machin e using: vmware-cmd -s register <config_file_path>. agents.logs db2adutl QUERY TABLESPACE DATABASE MMRDB > query2. databases. This command outputs the following memory pool allocation information: Current size Maximum size (hard limit) Largest size (high water mark) Type (identifier indicating function for which memory will be used) Agent who allocated pool (only if the pool is private) Application Part 1 : i d v and db2pd dbptnmem output are two different rep .TBSPACEID = TBSPACES.17.TABL ES AS TABLES. all areas.logs # db2support .vmdk Once the VMDK file copying over to ESX Server 2. not just actual system memory usage db2mtrk .logs #rollforward to a point in time before crash db2 rollforward db mmrdb to 2010-04-05-22. TABLES.Memory tracker command Provides complete report of memory status.vmdk /vmfs/vmserver1.vmdk /vmfs/vmdiskfile. for monitoring Instance Memory usage includes allowance for configuration. for instances. db2pd -dbptnmem High-level. tgz file # tar -zxvf ibm-java-sdk-6.rw.kudzu.rw.flw and X.tgz .Part 2 : set db2diag level to 4 db2diag -A to start a new db2diag.owner.run db2dart /DB of db2dbmon .users.user 0 0 /dev/sda1 /mnt/usb_flash vfat noauto. and send the dart report Part 3 : db2trc on -f X.4.fmt show and sort directory size $ du -k | sort -nr | more restart send queue $asnqacmd apply_server=FDB_ERP apply_schema=QAERP startq=SYSB.flw db2trc fmt X.dmp db2 backup db db2dbmon and get the error db2trc off db2trc flw X.iso9660 noauto.mode=620 0 0 LABEL=/home /home ext3 defaults 1 2 LABEL=/opt /opt ext3 defaults 1 2 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 LABEL=/tmp /tmp ext3 defaults 1 2 LABEL=/usr /usr ext3 defaults 1 2 LABEL=/usr/local /usr/local ext3 defaults 1 2 LABEL=/var /var ext3 defaults 1 2 /dev/hda8 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom udf.umask=0 0 0 install from .umask=0 0 0 Then as root do this: [ mount -a ] This is what my /etc/fstab looks like on my system which is 2.QMRDEVERPTATAQ log file in ERP $cd APPLCSF/$LOG To access a usb flash drive you can modify your /etc/fstab file like this: /dev/sda1 /mnt/usb_flash vfat noauto.0-5.log db2 backup db db2dbmon revert to diaglevel 4 send the latest db2diag.owner.dmp X.kudzu 0 0 /dev/sda /mnt/cam vfat noauto.0-linux-<arch>.users.dmp X.20-6 ( Red Hat 9 ) LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5.fmt send X.r o 0 0 /dev/fd0 /mnt/floppy auto noauto.log . dmp trace.64:5901 Deactivate all the Q subscriptions that feed the receive queue.QMRDEVERPTATAQ #asnqacmd apply_server=FDB_ERP apply_schema=QAERP stopq=SYSB. 'CAPSTOP'.dmp -s ese -u eposint eposinst trace. signal_subtype.XX EP_SIVIEW_EVENTS_DATA" is ready to be loaded from source table "XXEP. Note for insert loaddone # db2 "INSERT INTO QCERP.flw truss -aelf -o db2icrt.out /opt/IBM/db2/V9. signal_input_in) VALUES ('CMD'.QMRDEVERPTATAQ Activate all the Q subscriptions # db2 "INSERT INTO QCERP.install from rpm file # rpm -ivh TIVsm-API-x.IBMQREP_SIGNAL (signal_type. signal_subtype.rpm start vnc server #vncserver :1 remote connect to vncserver #vncviewer 10. 'XXEP_EVENTS_DATA_QREP')" Note: May consider cold start if not working or stop the QManager.XXEP_EVENTS_DATA" for publication or Q su bscription "XXEP_EVENTS_DATA_QREP".IBMQREP_SIGNAL (signal_type.dmp trace. db2trc on db2icrt -d db2trc off db2trc fmt db2trc flw f trace. 'LOADDONE'. if see following message then clear the target table ASN7017I "Q Capture" : "QCERP" : "WorkerThread" : The target table "ORAERP. signal_input_in) VALUES ('CMD'.5/instance/db2icrt -d -s ese -u eposi nt eposinst truss -aelf -o db2ilist. # db2 "INSERT INTO QCERP.5/instance/db2ilist . 'XXEP_EVENTS_DATA_QREP')" Check capture log.0.fmt trace. signal_subtype. 'XXEP_EVENTS_DATA_QREP')" Stop QCapture Delete all message from all the send queues and the receive queue that were invo lved in the invalid setup.7.IBMQREP_SIGNAL (signal_type.x. signal_input_in) VALUES ('CMD'. #clear qlocal (SYSB.out /opt/IBM/db2/V9. 'CAPSTART'.QMRDEVERPTATAQ) Start QCapture Issue the startq command so that the Q Apply program starts reading from the rec eive queue again #asnqacmd apply_server=FDB_ERP apply_schema=QAERP startq=SYSB.x. look for "TCB Index Stats:" header and the "Scans" column.mm. #select firstkeycard.ldapdb2 db2 connect to ldapdb2 db2 reorgchk update statistics on table all db2 terminate show valude of table log index build db2cat -d <db name> -n <table name> -s <schema name> -o <output file> db2pd -dbptnmem db2pd -db TEST -logs Instance Level UPDATE DATABASE MANAGER CONFIGURATION USING dft_mon_bufpool ON dft_mon_lock ON dft_mon_sort ON dft_mon_stmt ON dft_mon_table ON dft_mon_uow ON IMMEDIATE Turning switches on for session #UPDATE MONITOR SWITCHES USING bufferpool ON db2 get snapshot # db2 GET SNAPSHOT FOR ALL BUFFERPOOLS # db2 GET SNAPSHOT FOR BUFFERPOOLS ON database_name # . db2 snapshot to get locks $db2 get snapshot for locks for application agentid appwtfrlocksid $db2 get snapshot for locks on database_name default timestamp format yyyy-MM-dd-HH.indexes where indname='FX1' find unused index $db2pd -db db-name -tcbstats index from the result.'B') find cardinality of indexes. if t he count in Scans is 0 that means "it is not used". first2keycard from syscat.#dismq -x # db2 force application all | db2 backup database eposdb to . # db2 force application all | db2 restore database eposdb Find out table statistics is recently updated.ffffff su .tables where tabname in ('A'. #select stats_time from syscat.ss. n e .