cancel
Showing results for 
Search instead for 
Did you mean: 

ECC 6.0 installation error - DB2/ AIX

Former Member
0 Kudos

Hello,

I am installing ECC 6.0 using DB2 database Version 8 Fixpak 12 on AIX system in HACMP clustering envt.

I have insatlled DB2 & Central Instance in Node A and DB2 and Dialog Instance in Node B.

But now while starting DB2 in node B by command "startsap db" I am getting below error. Pls help me ASAP........

***********************************

SQL1063N DB2START processing was successful.

Database Manager started

SQL30081N A communication error has been detected. Communication protocol

being used: "TCP/IP". Communication API being used: "SOCKETS". Location

where the error was detected: "192.168.213.41". Communication function

detecting the error: "connect". Protocol specific error code(s): "79",

"*",

"*". SQLSTATE=08001

Activate database failed

**************

Pls help me ASAP..........i am stuck up in installation.

Thanks,

Gautam.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

please check the following too .

I suppose you perform IP-Address Takeover .

(Move Virtual IP-Address 192.168.213.41 of Node A to Node B)

Did you flush the ARP Cache on Node B ?

Please check , when this error occurs , to which MAC Address IP Address 192.168.213.41 points in node B's Arp Cache .

 
***********************************
SQL1063N DB2START processing was successful.
Database Manager started
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "192.168.213.41". Communication function
detecting the error: "connect". Protocol specific error code(s): "79",
"*",
"*". SQLSTATE=08001
Activate database failed

**************

Furthermore check , that TCP/IP Listening is started properly on Node B via netstat .

If there is no listening on node B check db2diag.log for Error's regarding starting

TCPIP processing .

If there are Error's in db2diag.log regarding TCP/IP processing , please provide .

Hth + Best regards

dirk

Former Member
0 Kudos

Dear Dirk,

Yes I have performed IP-Address takeover. How will i flush the ARP Cache on Node B ? And how shd i trace to which MAC Address IP Address 192.168.213.41 points in node B's Arp Cache .

Pls find below the other reqd things:

*************NETSTAT Output *****************

Active Internet connections

Proto Recv-Q Send-Q Local Address Foreign Address (state)

tcp4 0 2 gipapp_pers.telnet 192.168.213.21.4talk ESTABLISHED

tcp4 0 0 loopback.smux loopback.filenet- ESTABLISHED

tcp4 0 0 loopback.filenet- loopback.smux ESTABLISHED

tcp4 0 0 loopback.smux loopback.32778 ESTABLISHED

tcp4 0 0 loopback.32778 loopback.smux ESTABLISHED

tcp4 0 0 gipapp_pers.32821 gipdb.trap-dae CLOSE_WAIT

tcp4 0 0 gipapp.32844 gipdb.trap-dae CLOSE_WAIT

tcp4 0 0 gipapp.filenet- gipapp.32775 ESTABLISHED

tcp4 0 0 gipapp.32775 gipapp.filenet- ESTABLISHED

tcp4 0 0 gipapp.filenet- gipapp.32776 ESTABLISHED

tcp4 0 0 gipapp.32776 gipapp.filenet- ESTABLISHED

tcp4 0 0 gipapp.filenet- gipapp.32777 ESTABLISHED

tcp4 0 0 gipapp.32777 gipapp.filenet- ESTABLISHED

udp4 0 0 192.168.0.255.topsvcs .

udp4 0 0 gipapp_boot.topsvcs .

udp4 0 0 192.167.0.255.topsvcs .

udp4 0 0 gipapp_stby.topsvcs .

udp4 0 0 loopback.32823 loopback.tick-por

udp4 0 0 loopback.32831 loopback.cpq-task

Active UNIX domain sockets

SADR/PCB Type Recv-Q Send-Q Inode Conn Refs Nextref Addr

f10006000316e008 stream 0 0 f100010032a807f8 f100060003178880 0 0 /var/ha/soc/grpsvcs.clients.gipcluster/u463020

f10006000276af00

f1000600004a7408 dgram 0 0 f100010032a7fff8 0 0 0 /dev/.SRC-unix/SRCxhAbam

f1000600004a1880

f1000600002b5408 stream 0 0 f10001003281e3f8 0 0 0 /tmp/dpi_socket

f1000600002afc80

f10006000311d808 stream 0 0 f1000100327fdff8 0 0 0 /var/ct/IW/soc/mc/RMIBM.ServiceRM.0

f10006000039c680

f1000600004a0008 stream 0 0 f1000100328013f8 0 0 0 /usr/es/sbin/cluster/ha_ipc

f1000600004a1000

f10006000311dc08 stream 0 0 0 f10006000276a480 0 0 /var/ct/IW/soc/mc/RMIBM.ServiceRM.0

f10006000276a500

f10006000057a808 stream 0 0 0 f10006000276a500 0 0

f10006000276a480

f100060001a6ec08 dgram 0 0 f1000100327ce7f8 0 0 0 /dev/.SRC-unix/SRC1pAbaf

f100060000575c80

f10006000311b408 dgram 0 0 f10001003282fbf8 0 0 0 /dev/.SRC-unix/SRC2CAbah

f10006000276a900

f10006000057ac08 stream 0 0 0 f10006000276a780 0 0

f10006000276a600

f1000600002a2808 stream 0 0 0 f1000600002aff80 0 0

f1000600002aff00

f1000600002a2408 stream 0 0 f1000100327acbf8 0 0 0 /var/ct/IW/soc/mc/RMIBM.CSMAgentRM.0

f1000600002afe80

f1000600004be408 dgram 0 0 f1000100328017f8 0 0 0 /usr/es/sbin/cluster/HacmpClstrmgrSrvr

f1000600004a1200

f100060000576008 dgram 0 0 f1000100327a8ff8 0 0 0 /dev/.SRC-unix/SRCwhAbae

f10006000276a280

f1000600002fa808 stream 0 0 0 f1000600004b6100 0 0

f1000600004a1800

f1000600004a9808 stream 0 0 0 f1000600004a1c80 0 0

f1000600004b6180

f1000600002b5c08 dgram 0 0 f100010032310ff8 0 0 0 /dev/.SRC-unix/SRCs6Abac

f1000600002b8800

f1000600004b7c08 stream 0 0 0 f1000600004b6680 0 0

f1000600004a1b00

f100060003116c08 stream 0 0 0 f10006000276ac80 0 0 /var/ha/soc/topsvcs/server_socket.gipcluster

f100060003178900

f10006000057a408 dgram 0 0 f100010032340bf8 0 0 0 /dev/SRC

f10006000039c700

f100060003177808 stream 0 0 0 f100060003178600 0 0

f10006000276ab80

f100060001a6e008 dgram 0 0 f1000100323fbff8 0 0 0 /dev/.SRC-unix/SRCdxAbaa

f100060000575d80

f100060003177c08 stream 0 0 0 f10006000276ae80 0 0 /var/ha/soc/em.clsrv.gipcluster

f100060003178d00

f100060003136008 stream 0 0 0 f100060003178b80 0 0

f10006000276ae00

f100060003117408 stream 0 0 f1000100329bcff8 0 0 0 /var/ha/soc/grpsvcsdsocket.gipcluster

f10006000276ad80

f10006000317bc08 dgram 0 0 f100010032bbb7f8 0 0 0 /dev/.SRC-unix/SRCWgAbav

f100060003178280

f100060002767808 stream 0 0 f1000100327a7bf8 0 0 0 /var/ct/IW/soc/mc/clsrv

f10006000276a380

f1000600002fa008 dgram 0 0 f100010032aa07f8 0 0 0 /dev/.SRC-unix/SRC2SAban

f1000600004a1500

f1000600002fa408 stream 0 0 0 f1000600004b6180 0 0 /var/ha/soc/topsvcs/server_socket.gipcluster

f1000600004a1c80

f100060002767c08 dgram 0 0 f1000100323433f8 0 f1000600004b6000 0 /dev/log

f10006000276a180

f10006000311d008 stream 0 0 f1000100327ebbf8 0 0 0 /var/ct/IW/soc/mc/rmsrv

f10006000276a200

f1000600004b9408 stream 0 0 f100010032a6dff8 0 0 0 /var/ha/soc/topsvcs/server_socket.gipcluster

f1000600004a1600

f100060002768008 dgram 0 0 f10001003231bbf8 0 0 0 /dev/.SRC-unix/SRCm_Abab

f10006000039c600

f100060003125408 dgram 0 0 f100010032aa73f8 0 0 0 /dev/.SRC-unix/SRCvhAbat

f100060003178b00

f10006000057a008 stream 0 0 f10001003078b3f8 0 0 0 /tmp/.X11-unix/X0

f10006000039c780

f1000600002bc808 stream 0 0 f1000100327deff8 0 0 0 /usr/es/sbin/cluster/etc/ha_sec

f1000600002b8880

f1000600004a5808 dgram 0 0 f100010032ab6ff8 0 0 0 /dev/.SRC-unix/SRCuKAbar

f1000600004a1580

f1000600002b4408 dgram 0 0 f1000100327db3f8 0 0 0 /dev/.SRC-unix/SRCvxAbad

f1000600002b8900

f100060002765008 stream 0 0 0 f10006000276a680 0 0 /var/ct/IW/soc/mc/clsrv

f10006000276a700

f1000600002bcc08 stream 0 0 f1000100327cf7f8 0 0 0 /var/ct/IW/soc/mc/RMIBM.ERRM.0

f1000600002afb80

f10006000311b808 dgram 0 0 f1000100328103f8 0 0 0 /dev/.SRC-unix/SRC3wAbai

f10006000276a980

f1000600004a0408 stream 0 0 f1000100328213f8 0 0 0 /usr/es/sbin/cluster/ha_vt_ipc

f1000600004a1080

f1000600002a2c08 stream 0 0 0 f1000600002aff00 0 0 /var/ct/IW/soc/mc/RMIBM.CSMAgentRM.0

f1000600002aff80

f100060002768c08 dgram 0 0 f100010032840bf8 0 0 0 /dev/.SRC-unix/SRC6oAbaj

f10006000276a400

f100060003112c08 stream 0 0 0 f100060003178480 0 0 /var/ha/soc/em.rmsrv.gipcluster

f100060003178500

f1000600002fac08 stream 0 0 0 f1000600004a1800 0 0 /var/ha/soc/haem/em.RMaixos.0.gipcluster

f1000600004b6100

f10006000316f008 stream 29 0 0 f100060003178200 0 0

f100060003178780

f100060000576808 stream 0 0 f10001003283f7f8 f10006000276a700 0 0 /tmp/.ct_mc_393300_sec60054145d02cc43a325315

f10006000276a680

f1000600002a7408 dgram 0 0 f1000100327cf3f8 0 0 0 /dev/.SRC-unix/SRC1SAbag

f1000600002afc00

f1000600002a7808 stream 0 0 0 f1000600002afd80 0 0

f1000600002afd00

f1000600002a7c08 stream 0 0 0 f1000600002afd00 0 0 /var/ct/IW/soc/mc/RMIBM.ERRM.0

f1000600002afd80

f100060002765808 stream 0 0 0 f10006000276a600 0 0 /var/ct/IW/soc/mc/RMIBM.AuditRM.0

f10006000276a780

f1000600002a2008 stream 0 0 f10001003281fff8 0 0 0 /var/ct/IW/soc/mc/RMIBM.AuditRM.0

f1000600002afe00

f1000600004a0c08 dgram 0 0 f1000100327ad7f8 0 0 0 /usr/es/sbin/cluster/hacmprd.stat

f1000600004a1100

f1000600004bec08 dgram 0 0 f1000100328317f8 0 0 0 /usr/es/sbin/cluster/clresmgrd.stat

f1000600004a1300

f1000600004bc408 dgram 0 0 f1000100327e1bf8 0 0 0 /usr/es/sbin/cluster/hats_to_cm

f1000600004a1400

f1000600004be008 dgram 0 0 f1000100327e17f8 0 0 0 /usr/es/sbin/cluster/vtapi_event.stat

f1000600004a1180

f1000600004bc008 dgram 0 0 f1000100327adbf8 0 0 0 /usr/es/sbin/cluster/hacmprd.extev

f1000600004a1380

f1000600004be808 dgram 0 0 0 0 0 0

f1000600004a1280

f1000600005ff408 dgram 2904 0 f1000100328f87f8 0 0 0 /usr/es/sbin/cluster/HacmpRgRmClnt

f1000600004a1d80

f10006000316f408 dgram 0 0 f100010032ac23f8 0 0 0 /dev/.SRC-unix/SRCGCAbap

f100060003178a00

f1000600002fcc08 dgram 0 0 f100010032a773f8 0 0 0 /dev/.SRC-unix/SRCu_Abas

f1000600004b6480

f1000600002fb408 dgram 0 0 f100010032501ff8 0 0 0 /dev/.SRC-unix/SRC0KAbao

f1000600004a1b80

f100060003123808 stream 0 0 0 f100060003178900 0 0

f10006000276ac80

f1000600004bc808 dgram 0 0 f100010032aaebf8 0 0 0 /dev/.SRC-unix/SRCsoAbal

f1000600004a1900

f1000600002fe808 stream 0 0 f100010032aa1bf8 0 0 0 /var/ha/soc/em.rmsrv.gipcluster

f1000600004a1f00

f10006000316e408 stream 0 0 0 f10006000276af00 0 0 /var/ha/soc/grpsvcsdsocket.gipcluster

f100060003178880

f1000600005fe808 stream 0 0 f1000100329be3f8 0 0 0 /var/ha/soc/haem/em.RMaixos.0.gipcluster

f1000600004b6280

f1000600004a6808 stream 0 0 0 f1000600004a1b00 0 0 /var/ha/soc/topsvcs/hats_nim.663676

f1000600004b6680

f1000600004bcc08 stream 0 0 f100010032a91bf8 0 0 0 /var/ha/soc/em.clsrv.gipcluster

f1000600004b6080

f100060003107408 dgram 0 0 f1000100329a13f8 0 0 0

f100060003178680

f100060003107808 stream 0 0 f100010032a823f8 f100060003178380 0 0 /var/ha/soc/grpsvcs.clients.gipcluster/u495618

f100060003178180

f1000600005fe408 stream 0 0 0 f1000600004b6400 0 0 /var/ha/soc/topsvcs/hats_scsi_nim.594076

f1000600004b6200

f100060000359008 stream 0 0 f100010032aeabf8 0 0 0 /tmp/.sapstream50113

f10006000035f880

f1000600004aa408 stream 0 0 0 f1000600004b6200 0 0

f1000600004b6400

f1000600002fb808 stream 0 0 f100010032bbbbf8 0 0 0 /var/ct/IW/soc/mc/RMIBM.HostRM.0

f1000600004a1f80

f100060003174408 stream 0 0 0 f10006000276ab80 0 0 /var/ha/soc/topsvcs/hats_nim.491568

f100060003178600

f100060003175408 dgram 0 0 0 f10006000276a180 0 0

f10006000276ad00

f100060003174008 dgram 0 0 f100010032a8bbf8 0 0 0 /dev/.SRC-unix/SRCnxAbak

f10006000276af80

f100060003175008 stream 0 0 f100010032bccff8 0 0 0 /tmp/.sapstream50013

f10006000276ab00

f1000600030e0408 stream 0 0 0 f10006000276ae00 0 0 /var/ct/IW/soc/mc/RMIBM.HostRM.0

f100060003178b80

f100060003112808 stream 0 0 0 f100060003178780 0 0 /var/ha/soc/em.clsrv.gipcluster

f100060003178200

f100060003123c08 stream 0 0 0 f100060003178500 0 0

f100060003178480

f10006000316f808 stream 0 0 f1000100329c03f8 f100060003178700 0 0 /tmp/.ct_mc_495618_sec79002145d02dd108ac6da6

f100060003178080

f10006000316fc08 stream 0 0 0 f100060003178080 0 0 /var/ct/IW/soc/mc/clsrv

f100060003178700

f1000600002fbc08 dgram 0 0 f100010032a86ff8 0 0 0 /dev/.SRC-unix/SRCuDAbaq

f1000600004a1a00

f100060003107c08 stream 0 0 0 f100060003178180 0 0 /var/ha/soc/grpsvcsdsocket.gipcluster

f100060003178380

f1000600002fb008 dgram 0 0 0 f10006000276a180 0 f10006000276ad00

f1000600004b6000

f10006000316ec08 dgram 0 0 f100010032a997f8 0 0 0 /dev/.SRC-unix/SRCz_Abau

f100060003178000

f10006000313a808 stream 0 0 0 f100060003178d00 0 0

f10006000276ae80

*************NETSTAT Output *****************

*************db2diag.log Yesterday's LOG *****************

sqlePrintFinalMessage, probe:10

RETCODE : ZRC=0xFFFFFBFF=-1025

2007-02-12-02.42.44.891105-360 I41780851A293 LEVEL: Event

PID : 589924 TID : 1 PROC : db2flacc

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30

CHANGE : CFG DBM: "Svcename" From: "" To: "sapdb2PRD"

2007-02-12-02.43.05.558265-360 I41781145A305 LEVEL: Error

PID : 577556 TID : 1 PROC : R3trans

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110

MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="79".

2007-02-12-02.43.05.671468-360 I41781451A1630 LEVEL: Event

PID : 647380 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-02.43.05.832661-360 E41783082A920 LEVEL: Warning

PID : 577574 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, LicCheckProcessors, probe:20

MESSAGE : ADM12017E The number of processors on this machine exceeds the

defined entitlement of "1" for the product "DB2 Enterprise Server

Edition". The number of processors on this machine is "2". You should

purchase additional processor based entitlements from your IBM

representative or authorized dealer and update your license using the

License Center or the db2licm command line utility. For more

information on updating processor based licenses, refer to the Quick

Beginnings manual for your platform. For more information on the

db2licm utility, refer to the DB2 Command Reference.

2007-02-12-02.43.07.045789-360 E41784003A1027 LEVEL: Event

PID : 577574 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911

MESSAGE : ADM7513W Database manager has started.

START : DB2 DBM

DATA #1 : Build Level, 144 bytes

Instance "db2prd" uses "64" bits and DB2 code release "SQL08025"

with level identifier "03060106".

Informational tokens are "DB2 v8.1.1.112", "s060429", "U807381", FixPak "12".

DATA #2 : System Info, 224 bytes

System: AIX gipapp 3 5 0003F54ED700

CPU: total:4 online:4 Threading degree per core:2

Physical Memory(MB): total:7936 free:5677

Virtual Memory(MB): total:38656 free:36390

Swap Memory(MB): total:30720 free:30713

Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304

shmMax:68719476736 shmMin:1 shmIDs:131072

shmSegments:68719476736 semIDs:131072 semNumPerID:65535

semOps:1024 semMaxVal:32767 semAdjustOnExit:16384

2007-02-12-02.43.15.651519-360 I41785031A282 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.43.15.656995-360 E41785314A421 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.43.15.658771-360 I41785736A386 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.43.22.503247-360 I41786123A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.43.22.507915-360 E41786406A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.43.22.509308-360 I41786828A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.43.49.140930-360 I41787215A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.43.49.142013-360 E41787498A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.43.49.142206-360 I41787920A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.43.49.550152-360 I41788307A1630 LEVEL: Event

PID : 589840 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-02.43.57.058173-360 I41789938A282 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.43.57.060029-360 E41790221A421 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.43.57.060262-360 I41790643A386 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.44.05.352154-360 I41791030A282 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.44.05.353829-360 E41791313A421 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.44.05.354061-360 I41791735A386 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.44.51.772136-360 I41792122A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.44.51.773633-360 E41792405A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.44.51.773850-360 I41792827A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.46.57.416377-360 I41793214A282 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.46.57.417652-360 E41793497A421 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.46.57.417855-360 I41793919A386 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.46.57.697529-360 I41794306A300 LEVEL: Warning

PID : 1884344 TID : 1 PROC : db2bp

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150

RETCODE : ZRC=0x8037006D=-2143879059=SQLJR_CABLT "CA BUILT"

2007-02-12-02.48.05.634981-360 I41794607A282 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.48.05.636417-360 E41794890A421 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.48.05.636630-360 I41795312A386 LEVEL: Error

PID : 757960 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.52.00.771459-360 I41795699A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.52.00.773060-360 E41795982A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.52.00.773281-360 I41796404A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.53.59.143179-360 I41796791A1630 LEVEL: Event

PID : 1896668 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA430 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA440 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA450 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA490 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA500 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA510 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA520 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-02.54.17.316458-360 I41798422A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.54.17.317648-360 E41798705A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.54.17.317847-360 I41799127A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.54.17.712817-360 I41799514A1630 LEVEL: Event

PID : 2289784 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-02.54.25.176344-360 I41801145A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.54.25.178082-360 E41801428A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.54.25.178309-360 I41801850A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.54.33.666929-360 I41802237A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.54.33.668600-360 E41802520A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.54.33.668822-360 I41802942A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-02.55.40.600227-360 I41803329A282 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-02.55.40.601702-360 E41803612A421 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-02.55.40.601928-360 I41804034A386 LEVEL: Error

PID : 741486 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-03.06.37.038989-360 I41804421A1630 LEVEL: Event

PID : 884978 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-03.06.37.556213-360 E41806052A920 LEVEL: Warning

PID : 553066 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, LicCheckProcessors, probe:20

MESSAGE : ADM12017E The number of processors on this machine exceeds the

defined entitlement of "1" for the product "DB2 Enterprise Server

Edition". The number of processors on this machine is "2". You should

purchase additional processor based entitlements from your IBM

representative or authorized dealer and update your license using the

License Center or the db2licm command line utility. For more

information on updating processor based licenses, refer to the Quick

Beginnings manual for your platform. For more information on the

db2licm utility, refer to the DB2 Command Reference.

2007-02-12-03.06.39.165763-360 E41806973A1026 LEVEL: Event

PID : 553066 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911

MESSAGE : ADM7513W Database manager has started.

START : DB2 DBM

DATA #1 : Build Level, 144 bytes

Instance "db2prd" uses "64" bits and DB2 code release "SQL08025"

with level identifier "03060106".

Informational tokens are "DB2 v8.1.1.112", "s060429", "U807381", FixPak "12".

DATA #2 : System Info, 224 bytes

System: AIX gipdb 3 5 0003F4FAD700

CPU: total:4 online:4 Threading degree per core:2

Physical Memory(MB): total:7936 free:6692

Virtual Memory(MB): total:38656 free:37406

Swap Memory(MB): total:30720 free:30714

Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304

shmMax:68719476736 shmMin:1 shmIDs:131072

shmSegments:68719476736 semIDs:131072 semNumPerID:65535

semOps:1024 semMaxVal:32767 semAdjustOnExit:16384

2007-02-12-03.06.41.237476-360 I41808000A360 LEVEL: Warning

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30

MESSAGE : Crash Recovery is needed.

2007-02-12-03.06.42.534793-360 I41808361A368 LEVEL: Warning

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, relation data serv, sqlrr_db_init, probe:100

MESSAGE : DB2_IMPLICIT_UNICODE enabled

2007-02-12-03.06.42.601134-360 I41808730A423 LEVEL: Warning

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410

MESSAGE : Crash recovery started. LowtranLSN 000000048D86D7FC MinbuffLSN

000000048D6CC00C

2007-02-12-03.06.42.645830-360 I41809154A405 LEVEL: Warning

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:2000

MESSAGE : Using parallel recovery with 5 agents 34 QSets 136 queues and 64 chunks

2007-02-12-03.06.43.879438-360 I41809560A433 LEVEL: Warning

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4000

MESSAGE : DIA2051W Forward phase of crash recovery has completed. Next LSN is

"000000048D9CE2A3".

2007-02-12-03.06.43.915853-360 I41809994A388 LEVEL: Warning

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3170

MESSAGE : Crash recovery completed. Next LSN is 000000048D9CE2A3

2007-02-12-03.10.47.172908-360 I41810383A411 LEVEL: Severe

PID : 852158 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-36 APPID: *LOCAL.db2prd.070212091047

FUNCTION: DB2 UDB, base sys utilities, sqleserl, probe:911

RETCODE : ZRC=0x00000001=1

DIA8000C An unexpected end of file was reached "".

2007-02-12-03.10.47.311281-360 I41810795A1629 LEVEL: Event

PID : 712896 TID : 1 PROC : db2stop

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2stop2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA380 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA390 : 6962 2F61 646D 2F64 6232 7374 6F70 3200 ib/adm/db2stop2.

0x0FFFFFFFFFFFA3A0 : 4E4F 4D53 4700 534E 0000 0000 0000 0000 NOMSG.SN........

0x0FFFFFFFFFFFA3B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-03.10.47.335338-360 I41812425A375 LEVEL: Error

PID : 856134 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:504

MESSAGE : Active Db:[PRD ] [RetCode=-1025] [Reason=1] [AppGrpCnt=9]

[QsAttemptCnt=0] [DbActivated=1] [UseCnt=8] [DbQuiesced=0]

2007-02-12-03.10.47.337807-360 I41812801A272 LEVEL: Error

PID : 712896 TID : 1 PROC : db2stop

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqlePrintFinalMessage, probe:10

RETCODE : ZRC=0xFFFFFBFF=-1025

2007-02-12-03.11.00.682446-360 I41813074A1629 LEVEL: Event

PID : 1044714 TID : 1 PROC : db2stop

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2stop2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA430 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA440 : 6962 2F61 646D 2F64 6232 7374 6F70 3200 ib/adm/db2stop2.

0x0FFFFFFFFFFFA450 : 4E4F 4D53 4700 534E 0000 0000 0000 0000 NOMSG.SN........

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA490 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA500 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA510 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA520 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-03.11.00.705875-360 I41814704A376 LEVEL: Error

PID : 876766 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:504

MESSAGE : Active Db:[PRD ] [RetCode=-1025] [Reason=1] [AppGrpCnt=10]

[QsAttemptCnt=0] [DbActivated=1] [UseCnt=9] [DbQuiesced=0]

2007-02-12-03.11.00.708628-360 I41815081A272 LEVEL: Error

PID : 1044714 TID : 1 PROC : db2stop

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqlePrintFinalMessage, probe:10

RETCODE : ZRC=0xFFFFFBFF=-1025

2007-02-12-03.11.09.443296-360 I41815354A1629 LEVEL: Event

PID : 1044718 TID : 1 PROC : db2stop

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2stop2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA420 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA430 : 6962 2F61 646D 2F64 6232 7374 6F70 3200 ib/adm/db2stop2.

0x0FFFFFFFFFFFA440 : 4E4F 4D53 4700 464F 5243 4500 534E 0000 NOMSG.FORCE.SN..

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA490 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA500 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA510 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-03.11.09.467050-360 I41816984A383 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:104

DATA #1 : String, 26 bytes

Force phase is in progress

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE40 : 0000 0000 ....

2007-02-12-03.11.09.469688-360 I41817368A454 LEVEL: Error

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, catalog services, sqlrlrci_all_rt, probe:100

RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT DETECTED"

DIA8003C The interrupt has been received.

2007-02-12-03.11.09.505744-360 I41817823A452 LEVEL: Warning

PID : 737428 TID : 1 PROC : db2agent (PRD) 0

INSTANCE: db2prd NODE : 000 DB : PRD

APPHDL : 0-7 APPID: *LOCAL.db2prd.070212090640

FUNCTION: DB2 UDB, catalog services, sqlrlrci_all, probe:10

RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT DETECTED"

DIA8003C The interrupt has been received.

2007-02-12-03.11.09.506521-360 I41818276A308 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:108

DATA #1 : String, 47 bytes

Force phase is completed and preparing to stop.

2007-02-12-03.11.09.506671-360 I41818585A387 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:65

DATA #1 : String, 31 bytes

Deactivate phase is in progress

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE3C : 0000 0001 ....

2007-02-12-03.11.11.974500-360 I41818973A406 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:230

DATA #1 : String, 49 bytes

Deactivate phase is completed, preparing to stop.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE3C : 0000 0001 ....

2007-02-12-03.11.11.974733-360 I41819380A287 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240

DATA #1 : String, 26 bytes

Stop phase is in progress.

2007-02-12-03.11.11.974857-360 I41819668A302 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250

DATA #1 : String, 41 bytes

Requesting system controller termination.

2007-02-12-03.11.12.017024-360 I41819971A403 LEVEL: Warning

PID : 524492 TID : 1 PROC : db2sysc 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5

MESSAGE : Bringing down all db2fmp processes as part of db2stop

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFFE2B0 : 0000 0000 ....

2007-02-12-03.11.12.037639-360 I41820375A288 LEVEL: Severe

PID : 999576 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.037671-360 I41820664A288 LEVEL: Severe

PID : 970796 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038016-360 I41820953A288 LEVEL: Severe

PID : 995366 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038349-360 I41821242A288 LEVEL: Severe

PID : 962794 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038450-360 I41821531A288 LEVEL: Severe

PID : 807162 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.045904-360 I41821820A304 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260

DATA #1 : String, 43 bytes

System controller termination is completed.

2007-02-12-03.11.12.546108-360 I41822125A381 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280

DATA #1 : String, 24 bytes

There is no active EDUs.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE6C : 0000 0000 ....

2007-02-12-03.11.12.037791-360 I41822507A288 LEVEL: Severe

PID : 933900 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038125-360 I41822796A288 LEVEL: Severe

PID : 925894 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038126-360 I41823085A288 LEVEL: Severe

PID : 655448 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038349-360 I41823374A288 LEVEL: Severe

PID : 909500 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.037840-360 I41823663A288 LEVEL: Severe

PID : 1007626 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038140-360 I41823952A288 LEVEL: Severe

PID : 913600 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038237-360 I41824241A288 LEVEL: Severe

PID : 929992 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038241-360 I41824530A288 LEVEL: Severe

PID : 958684 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.037905-360 I41824819A288 LEVEL: Severe

PID : 380968 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.14.480236-360 E41825108A301 LEVEL: Event

PID : 1011914 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911

MESSAGE : ADM7514W Database manager has stopped.

STOP : DB2 DBM

2007-02-12-03.11.12.037903-360 I41825410A288 LEVEL: Severe

PID : 966878 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.037943-360 I41825699A288 LEVEL: Severe

PID : 1040636 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038016-360 I41825988A288 LEVEL: Severe

PID : 917698 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.11.12.038042-360 I41826277A288 LEVEL: Severe

PID : 1003520 TID : 1 PROC : db2fmp (idle) 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:3

RETCODE : ZRC=0x83000024=-2097151964

2007-02-12-03.13.52.664866-360 I41826566A305 LEVEL: Error

PID : 766080 TID : 1 PROC : R3trans

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110

MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="79".

2007-02-12-03.13.54.309598-360 I41826872A1630 LEVEL: Event

PID : 598196 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-03.13.54.805820-360 E41828503A920 LEVEL: Warning

PID : 729118 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, LicCheckProcessors, probe:20

MESSAGE : ADM12017E The number of processors on this machine exceeds the

defined entitlement of "1" for the product "DB2 Enterprise Server

Edition". The number of processors on this machine is "2". You should

purchase additional processor based entitlements from your IBM

representative or authorized dealer and update your license using the

License Center or the db2licm command line utility. For more

information on updating processor based licenses, refer to the Quick

Beginnings manual for your platform. For more information on the

db2licm utility, refer to the DB2 Command Reference.

2007-02-12-03.13.56.366393-360 E41829424A1027 LEVEL: Event

PID : 729118 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911

MESSAGE : ADM7513W Database manager has started.

START : DB2 DBM

DATA #1 : Build Level, 144 bytes

Instance "db2prd" uses "64" bits and DB2 code release "SQL08025"

with level identifier "03060106".

Informational tokens are "DB2 v8.1.1.112", "s060429", "U807381", FixPak "12".

DATA #2 : System Info, 224 bytes

System: AIX gipapp 3 5 0003F54ED700

CPU: total:4 online:4 Threading degree per core:2

Physical Memory(MB): total:7936 free:5943

Virtual Memory(MB): total:38656 free:36656

Swap Memory(MB): total:30720 free:30713

Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304

shmMax:68719476736 shmMin:1 shmIDs:131072

shmSegments:68719476736 semIDs:131072 semNumPerID:65535

semOps:1024 semMaxVal:32767 semAdjustOnExit:16384

2007-02-12-03.14.05.543646-360 I41830452A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-03.14.05.547756-360 E41830735A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-03.14.05.549088-360 I41831157A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-03.14.12.643286-360 I41831544A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-03.14.12.645438-360 E41831827A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-03.14.12.645680-360 I41832249A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-03.16.06.155233-360 I41832636A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-03.16.06.156943-360 E41832919A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-03.16.06.157212-360 I41833341A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-03.16.06.697794-360 I41833728A1630 LEVEL: Event

PID : 2072576 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA380 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA390 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3A0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-03.16.14.216018-360 I41835359A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-03.16.14.217777-360 E41835642A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-03.16.14.218009-360 I41836064A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-03.16.20.967417-360 I41836451A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-03.16.20.969666-360 E41836734A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-03.16.20.969967-360 I41837156A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.01.48.956481-360 I41837543A282 LEVEL: Error

PID : 647268 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.01.48.961075-360 E41837826A421 LEVEL: Error

PID : 647268 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.01.48.962460-360 I41838248A386 LEVEL: Error

PID : 647268 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.01.49.480838-360 I41838635A1630 LEVEL: Event

PID : 2408676 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-05.01.56.990153-360 I41840266A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.01.56.992058-360 E41840549A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.01.56.992303-360 I41840971A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.02.04.128577-360 I41841358A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.02.04.130348-360 E41841641A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.02.04.130580-360 I41842063A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.02.15.502658-360 I41842450A282 LEVEL: Error

PID : 647268 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.02.15.628097-360 E41842733A421 LEVEL: Error

PID : 647268 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.02.15.628391-360 I41843155A386 LEVEL: Error

PID : 647268 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.02.34.804865-360 I41843542A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.02.34.806770-360 E41843825A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.02.34.807046-360 I41844247A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.02.35.305548-360 I41844634A1630 LEVEL: Event

PID : 725146 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-05.02.43.814029-360 I41846265A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.02.43.815725-360 E41846548A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.02.43.815942-360 I41846970A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.02.52.390444-360 I41847357A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.02.52.392339-360 E41847640A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.02.52.392618-360 I41848062A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.29.13.982112-360 I41848449A282 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-05.29.13.983947-360 E41848732A421 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-05.29.13.984235-360 I41849154A386 LEVEL: Error

PID : 618596 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-05.29.30.961086-360 I41849541A1629 LEVEL: Event

PID : 2339046 TID : 1 PROC : db2stop

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2stop2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA420 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA430 : 6962 2F61 646D 2F64 6232 7374 6F70 3200 ib/adm/db2stop2.

0x0FFFFFFFFFFFA440 : 4E4F 4D53 4700 464F 5243 4500 534E 0000 NOMSG.FORCE.SN..

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA490 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA500 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA510 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-05.29.30.985738-360 I41851171A383 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:104

DATA #1 : String, 26 bytes

Force phase is in progress

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE40 : 0000 0000 ....

2007-02-12-05.29.31.007904-360 I41851555A308 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:108

DATA #1 : String, 47 bytes

Force phase is completed and preparing to stop.

2007-02-12-05.29.31.008058-360 I41851864A386 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:210

DATA #1 : String, 29 bytes

Deactivate phase is bypassed.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE3C : 0000 0001 ....

2007-02-12-05.29.31.008183-360 I41852251A406 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:230

DATA #1 : String, 49 bytes

Deactivate phase is completed, preparing to stop.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE3C : 0000 0001 ....

2007-02-12-05.29.31.008306-360 I41852658A287 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240

DATA #1 : String, 26 bytes

Stop phase is in progress.

2007-02-12-05.29.31.008437-360 I41852946A302 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250

DATA #1 : String, 41 bytes

Requesting system controller termination.

2007-02-12-05.29.31.311130-360 I41853249A403 LEVEL: Warning

PID : 745544 TID : 1 PROC : db2sysc 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5

MESSAGE : Bringing down all db2fmp processes as part of db2stop

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFFE2B0 : 0000 0000 ....

2007-02-12-05.29.31.326804-360 I41853653A304 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260

DATA #1 : String, 43 bytes

System controller termination is completed.

2007-02-12-05.29.31.326973-360 I41853958A381 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280

DATA #1 : String, 24 bytes

There is no active EDUs.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE6C : 0000 0000 ....

2007-02-12-05.29.32.436409-360 E41854340A301 LEVEL: Event

PID : 1945852 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911

MESSAGE : ADM7514W Database manager has stopped.

STOP : DB2 DBM

2007-02-12-06.59.53.421464-360 I41854642A305 LEVEL: Error

PID : 1413358 TID : 1 PROC : R3trans

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110

MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="22".

2007-02-12-06.59.53.536073-360 I41854948A1630 LEVEL: Event

PID : 1429752 TID : 1 PROC : db2start

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2star2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA390 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA3A0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.

0x0FFFFFFFFFFFA3B0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........

0x0FFFFFFFFFFFA3C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA3F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA400 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA410 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA420 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA430 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA440 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-06.59.53.687635-360 E41856579A920 LEVEL: Warning

PID : 1380524 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, LicCheckProcessors, probe:20

MESSAGE : ADM12017E The number of processors on this machine exceeds the

defined entitlement of "1" for the product "DB2 Enterprise Server

Edition". The number of processors on this machine is "2". You should

purchase additional processor based entitlements from your IBM

representative or authorized dealer and update your license using the

License Center or the db2licm command line utility. For more

information on updating processor based licenses, refer to the Quick

Beginnings manual for your platform. For more information on the

db2licm utility, refer to the DB2 Command Reference.

2007-02-12-06.59.54.884406-360 E41857500A1027 LEVEL: Event

PID : 1380524 TID : 1 PROC : db2star2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911

MESSAGE : ADM7513W Database manager has started.

START : DB2 DBM

DATA #1 : Build Level, 144 bytes

Instance "db2prd" uses "64" bits and DB2 code release "SQL08025"

with level identifier "03060106".

Informational tokens are "DB2 v8.1.1.112", "s060429", "U807381", FixPak "12".

DATA #2 : System Info, 224 bytes

System: AIX gipapp 3 5 0003F54ED700

CPU: total:4 online:4 Threading degree per core:2

Physical Memory(MB): total:7936 free:5860

Virtual Memory(MB): total:38656 free:36573

Swap Memory(MB): total:30720 free:30713

Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304

shmMax:68719476736 shmMin:1 shmIDs:131072

shmSegments:68719476736 semIDs:131072 semNumPerID:65535

semOps:1024 semMaxVal:32767 semAdjustOnExit:16384

2007-02-12-07.00.03.475795-360 I41858528A282 LEVEL: Error

PID : 1175616 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-07.00.03.480769-360 E41858811A421 LEVEL: Error

PID : 1175616 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-07.00.03.482437-360 I41859233A386 LEVEL: Error

PID : 1175616 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-07.00.10.413144-360 I41859620A282 LEVEL: Error

PID : 1146930 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2007-02-12-07.00.10.416880-360 E41859903A421 LEVEL: Error

PID : 1146930 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125

MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.

A possible cause is that the maximum number of agents has been

exceeded.

2007-02-12-07.00.10.417980-360 I41860325A386 LEVEL: Error

PID : 1146930 TID : 1 PROC : db2tcpcm 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFF6614 : FFFF FB36 ...6

2007-02-12-07.00.23.359208-360 I41860712A1629 LEVEL: Event

PID : 1822910 TID : 1 PROC : db2stop

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130

DATA #1 : String, 31 bytes

/db2/db2prd/sqllib/adm/db2stop2

DATA #2 : Hexdump, 256 bytes

0x0FFFFFFFFFFFA420 : 2F64 6232 2F64 6232 7072 642F 7371 6C6C /db2/db2prd/sqll

0x0FFFFFFFFFFFA430 : 6962 2F61 646D 2F64 6232 7374 6F70 3200 ib/adm/db2stop2.

0x0FFFFFFFFFFFA440 : 4E4F 4D53 4700 464F 5243 4500 534E 0000 NOMSG.FORCE.SN..

0x0FFFFFFFFFFFA450 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA460 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA470 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA480 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA490 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4A0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4B0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4C0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4D0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4E0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA4F0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA500 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

0x0FFFFFFFFFFFA510 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2007-02-12-07.00.23.383194-360 I41862342A383 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:104

DATA #1 : String, 26 bytes

Force phase is in progress

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE40 : 0000 0000 ....

2007-02-12-07.00.23.383492-360 I41862726A308 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:108

DATA #1 : String, 47 bytes

Force phase is completed and preparing to stop.

2007-02-12-07.00.23.383619-360 I41863035A386 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:210

DATA #1 : String, 29 bytes

Deactivate phase is bypassed.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE3C : 0000 0001 ....

2007-02-12-07.00.23.383749-360 I41863422A406 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:230

DATA #1 : String, 49 bytes

Deactivate phase is completed, preparing to stop.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE3C : 0000 0001 ....

2007-02-12-07.00.23.383872-360 I41863829A287 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240

DATA #1 : String, 26 bytes

Stop phase is in progress.

2007-02-12-07.00.23.383993-360 I41864117A302 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250

DATA #1 : String, 41 bytes

Requesting system controller termination.

2007-02-12-07.00.23.561695-360 I41864420A403 LEVEL: Warning

PID : 1306752 TID : 1 PROC : db2sysc 0

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5

MESSAGE : Bringing down all db2fmp processes as part of db2stop

DATA #1 : Hexdump, 4 bytes

0x0FFFFFFFFFFFE2B0 : 0000 0000 ....

2007-02-12-07.00.23.573306-360 I41864824A304 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260

DATA #1 : String, 43 bytes

System controller termination is completed.

2007-02-12-07.00.23.573579-360 I41865129A381 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280

DATA #1 : String, 24 bytes

There is no active EDUs.

DATA #2 : Hexdump, 4 bytes

0x0FFFFFFFFFFFDE6C : 0000 0000 ....

2007-02-12-07.00.24.668811-360 E41865511A301 LEVEL: Event

PID : 1327274 TID : 1 PROC : db2stop2

INSTANCE: db2prd NODE : 000

FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911

MESSAGE : ADM7514W Database manager has stopped.

STOP : DB2 DBM

*************db2diag.log Yesterday's log *****************

Thanks & Waiting for your response...

Gautam

Former Member
0 Kudos

Hello Dirk,

I am getting this after executing ARP command in gipapp

  1. arp gipapp

0821-237 arp: Entry gipapp (192.168.213.42) was not found in local arp table.

  1. arp gipdb

gipdb (192.168.213.41) at 0:14:5e:c5:55:16 [ethernet]

This is in gipdb :

  1. arp gipdb

gipdb (192.168.213.41) at 0:14:5e:c5:55:16 [ethernet]

  1. arp gipapp

0821-237 arp: Entry gipapp (192.168.213.42) was not found in local arp table.

Former Member
0 Kudos

Dear Dirk,

Please help me in solving a similar kind of issue on AIX DB2 HACMP Cluster.

Please reply to the thread - [;

Expecting your reply at the earliest.

Regards,

Vineeth Damodar

Answers (8)

Answers (8)

Former Member
0 Kudos

Hi all

I have installed ASCS, SCS, Database Instance and CI at node A (sappbi-lpar), with virtual name for SAP resource sappbi and db2pbi as database resource virtual name. I have created pbiadm and db2pbi users at node B (sappbiha-lpar). In node A, all works correctly. So I have moved all filesystem and resources to node B. In node B I have this error communication message

db2 => list node directory

Node Directory

Number of entries in the directory = 1

Node 1 entry:

Node name = PBI

Comment =

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = db2pbi

Service name = sapdb2PBI

db2 => list database directory

System Database Directory

Number of entries in the directory = 1

Database 1 entry:

Database alias = PBI

Database name = PBI

Node name = PBI

Database release level = c.00

Comment =

Directory entry type = Remote

Catalog database partition number = -1

Alternate server hostname =

Alternate server port number =

db2 => connect

SQL30081N A communication error has been detected. Communication protocol

being used: "TCP/IP". Communication API being used: "SOCKETS". Location

where the error was detected: "10.xx.xx.xxx". Communication function

detecting the error: "connect". Protocol specific error code(s): "79", "*",

"*". SQLSTATE=08001

I hope your help

Thanks in advanced

Former Member
0 Kudos

Hi

The error you get is correct , because DB2 does not find PRDL on node A .

Now lets finalize the configuration and configure node A to be in sync with node B .

Issue the following Commands on <b>Node A</b>


db2 'uncatalog database PRD'
db2 'catalog tcpip node NODEPRD remote gipdb SERVER sapdb2PRD'
db2 'catalog Database PRD  as PRDL on /db2/PRD'
db2 'catalog database PRDL as PRD  at node NODEPRD'

Hth + best regards

dirk

Former Member
0 Kudos

Dear Dirk,

I have done this in Node A but now gettring problems in STMS config. While doing Transport Check Tool it says "Connect to PRD fails".

In Node A - CI + DB are running but "db2 connect to PRD " is failing.

db2 => connect to prd

SQL30082N Attempt to establish connection failed with security reason "3"

("PASSWORD MISSING"). SQLSTATE=08001

How to resolve this error now??

Regards,

Gautam.

Former Member
0 Kudos

Hi

First I recommend to open an new thread , because this one will get somehow unhandily

because of it's length and the question is marked as answered .

db2 => connect to prd

SQL30082N Attempt to establish connection failed with security reason "3"

("PASSWORD MISSING"). SQLSTATE=08001

This does not work with this setup because Database is now network cataloged .

For connect you need to specify user + password .

You need to connect like this

connect to prd user db2prd

Surely there is an developer trace with the error you get , when tp tries to connect to the database .

Please post this error + output of

disp+work -v

Please check that your kernel and dbsl is on current maintenance .

Hth + best regards

dirk

Former Member
0 Kudos

Hello,

This is log file of R3trans -d :

******************************************

telnet (gipapp)

AIX Version 5

(C) Copyrights by IBM and by others 1982, 2006.

login: root

root's Password:

*******************************************************************************

  • *

  • *

  • Welcome to AIX Version 5.3! *

  • *

  • *

gipapp:prdadm 6> R3trans -d

This is R3trans version 6.14 (release 700 - 20.07.06 - 17:34:00).

unicode enabled version

2EETW169 no connect possible: "DBMS = DB6 --- DB2DB

DFT = 'PRD'"

R3trans finished (0012).

gipapp:prdadm 7> cat trans.log

4 ETW000 R3trans version 6.14 (release 700 - 20.07.06 - 17:34:00).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time : 14.02.2007 - 07:35:24

4 ETW000 control file: <no ctrlfile>

4 ETW000 R3trans was called as follows: R3trans -d

4 ETW000 trace at level 2 opened for a given file pointer

4 ETW000 [dev trc ,00000] Wed Feb 14 07:35:24 2007

55 0.000055

4 ETW000 [dev trc ,00000] db_con_init called

20 0.000075

4 ETW000 [dev trc ,00000] create_con (con_name=R/3)

35 0.000110

4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/PRD/SYS/exe/run/dbd

b6slib.o' ...

4 ETW000

48 0.000158

4 ETW000 [dev trc ,00000] load shared library (/usr/sap/PRD/SYS/exe/run/db

db6slib.o), hdl 0

4 ETW000

529 0.000687

4 ETW000 [dev trc ,00000] Library '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o' l

oaded

4 ETW000

29 0.000716

4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sa

p/PRD/SYS/exe/run/dbdb6slib.o

4 ETW000

31 0.000747

4 ETW000 [dev trc ,00000] Version of '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o

' is "700.08", patchlevel (0.52)

4 ETW000

141 0.000888

4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/s

ap/PRD/SYS/exe/run/dbdb6slib.o

4 ETW000

31 0.000919

4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/

sap/PRD/SYS/exe/run/dbdb6slib.o

4 ETW000

30 0.000949

4 ETW000 [dev trc ,00000] New connection 0 created

24 0.000973

4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCO

NNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, oc

c = NO

4 ETW000

35 0.001008

4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3)

33 0.001041

4 ETW000 [dev trc ,00000] find_con_by_name found the following connection

for reuse:

4 ETW000

29 0.001070

4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCON

NECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ

= NO

4 ETW000

33 0.001103

4 ETW000 [dev trc ,00000] DB6 (DB2 UDB) UNICODE database interface 700.08

[opt]

4 ETW000

311 0.001414

4 ETW000 [dev trc ,00000] DB6 shared library (dbdb6slib) patchlevels

19 0.001433

4 ETW000 [dev trc ,00000] (0.8) DB6: V8.2.2 optguidelines in OPEN SQL (n

ote 150037)

4 ETW000

30 0.001463

4 ETW000 [dev trc ,00000] (0.8) Support of SDBUPDEXCL (note 847616)

20 0.001483

4 ETW000 [dev trc ,00000] (0.9) DB6: use export file for dbdb6slib (note

835135)

4 ETW000

29 0.001512

4 ETW000 [dev trc ,00000] (0.9) DB6: Core in getAndBindSQLDA (note 83318

3)

4 ETW000

29 0.001541

4 ETW000 [dev trc ,00000] (0.10) DB6: link dbdb6slib.dll on windows with

libdb6.obj (note 761159)

4 ETW000

30 0.001571

4 ETW000 [dev trc ,00000] (0.10) DB6: DUPLICATE_KEY on MERGE -> repeat (

note 851474)

4 ETW000

37 0.001608

4 ETW000 [dev trc ,00000] (0.15) DB6: wrong CAST for short string ABAP t

ype (note 861905)

4 ETW000

30 0.001638

4 ETW000 [dev trc ,00000] (0.17) DB6: special characters in sidadm passw

d (note 865839)

4 ETW000

29 0.001667

4 ETW000 [dev trc ,00000] (0.21) DB6: no SAP_INFO comments (note 873889)

4 ETW000

29 0.001696

4 ETW000 [dev trc ,00000] (0.22) DB6: hints: get correlation names from

view texts (note 868888)

4 ETW000

30 0.001726

4 ETW000 [dev trc ,00000] (0.23) DB6: hints: get correlation names from

view texts (note 868888)

4 ETW000

29 0.001755

4 ETW000 [dev trc ,00000] (0.26) DB6: DB6_DBSL_CLP_COMMAND STRING_BAD_RE

F (note 883402)

4 ETW000

29 0.001784

4 ETW000 [dev trc ,00000] (0.27) DB6: activate value compression (note 8

86231)

4 ETW000

30 0.001814

4 ETW000 [dev trc ,00000] (0.28) DB6: optimization guidelines on views p

art 2 (note 868888)

4 ETW000

29 0.001843

4 ETW000 [dev trc ,00000] (0.30) DB6: no SQL trace for SQLCancel (note 8

92111)

4 ETW000

29 0.001872

4 ETW000 [dev trc ,00000] (0.33) DB6: append SAP_TA comment (note 873889

)

4 ETW000

29 0.001901

4 ETW000 [dev trc ,00000] (0.34) DB6: activate value compression with qu

oted names (note 886231)

4 ETW000

30 0.001931

4 ETW000 [dev trc ,00000] (0.36) DB6: Repeat isolated DDL statements aft

er SQL0911 (note 901338)

4 ETW000

29 0.001960

4 ETW000 [dev trc ,00000] (0.41) DB6: add V9 to list of supported DB2 re

leases (note 912386)

4 ETW000

30 0.001990

4 ETW000 [dev trc ,00000] (0.50) DB6: reread passwords for secondary con

nections (note 931742)

4 ETW000

29 0.002019

4 ETW000 [dev trc ,00000] (0.52) DB6: double quote table names in optgui

delines (note 868888)

4 ETW000

30 0.002049

4 ETW000 [dev trc ,00000] Supported features:

18 0.002067

4 ETW000 [dev trc ,00000] - CLI LOAD for INSERT ... FULLSELECT

19 0.002086

4 ETW000 [dev trc ,00000] ..retrieving configuration parameters

18 0.002104

4 ETW000 [dev trc ,00000] ..done

91 0.002195

4 ETW000 [dev trc ,00000] Running with UTF-8 Unicode

18 0.002213

4 ETW000 [dev trc ,00000] DB2 library /db2/db2prd/sqllib/lib64/libdb2.a(sh

r_64.o) successfully loaded

4 ETW000

9497 0.011710

4 ETW000 [dev trc ,00000] Wed Feb 14 07:35:26 2007

1490336 1.502046

4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (BEGIN)

27 1.502073

4 ETW000 [dev trc ,00000] &+ DbSlConnectDB6( SQLConnect 😞 [IBM][CLI D

river] SQL1040N The maximum number of applications is already connected

4 ETW000

43 1.502116

4 ETW000 [dev trc ,00000] &+ to the database. SQLSTATE=57030

4 ETW000

32 1.502148

4 ETW000 [dev trc ,00000] &+

4 ETW000

32 1.502180

4 ETW000 [dev trc ,00000] &+

4 ETW000

32 1.502212

4 ETW000 [dev trc ,00000] &+

4 ETW000

31 1.502243

4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (END)

20 1.502263

4 ETW000 [dbdb6.c ,00000] *** ERROR => DbSlConnect to 'PRD' as 'sapprd' fa

iled

4 ETW000

54 1.502317

2EETW169 no connect possible: "DBMS = DB6 --- DB2DB

DFT = 'PRD'"

gipapp:prdadm 8>

*******************************************

gipapp:prdadm 8> disp+work -V|more

-


disp+work information

-


kernel release 700

kernel make variant 700_REL

DBMS client library DB6_81

DBSL shared library version 700.08

compiled on AIX 2 5 005DD9CD4C00

compiled for 64 BIT

compilation mode UNICODE

compile time Apr 2 2006 20:44:50

update level 0

patch number 52

Standard input

Please help me ASAP

Former Member
0 Kudos

Hello,

I am getting this error while executing this db2 connect to prd user db2prd

gipdb:prdadm 1> db2 connect to prd

SQL30082N Attempt to establish connection failed with security reason "3"

("PASSWORD MISSING"). SQLSTATE=08001

gipdb:prdadm 2> db2 connect to prd user db2prd

Enter current password for db2prd:

SQL1040N The maximum number of applications is already connected to the

database. SQLSTATE=57030

Former Member
0 Kudos

Hello,

I have raised the issue in this node "STMS error in ECC 6.0 - DB2 /AIX "

Please help me ASAP

Thanks

Gautam

Former Member
0 Kudos

Hi

As you see , you have an asynchronous setup of DB+Node directory on Node A and Node B .

First you need to recatalog your database for high availability and cross-takeover of DI and CI+DB <b>on Node B</b>.


db2 'uncatalog database PRD'
db2 'catalog Database PRD  as PRDL on /db2/PRD'
db2 'catalog database PRDL as PRD  at node NODEPRD'

Then you could try an takeover of CI+DB to Node B .

With this setup then just the takeover of DI to Node a will not work , but this we will discuss in a next step .

Hth + Best regards

dirk

Former Member
0 Kudos

Dear Dirk,

THANKS A LOT!!!

After the execution of commands given by you its working fine in Node B.

And as you said that this setup will not work when DI is moved to Node A. Actually i donot need this .

According to my config i plan that when Node A (CI + DB) will fail then it will move to Node B (DI ) and Node B will startup with CI + DB + DI and which is now successful after your help!!

Thanks again....

Regards & Thanks,

Gautam.

Former Member
0 Kudos

Dear Dirk,

I got stuck up again...

Dialog Instance is not started in node B while DB + CI is running in node A. After executing the below commands.

SAP is working fine only when all CI + DB + DI are in Node B. But earlier it was fine with DB + CI in Node A and DI in B, then why is it failing now. Pls help.

TRANS.LOG details are as below:

******************

gipapp:prdadm 1> more trans.log

4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time : 14.02.2007 - 01:12:35

4 ETW000 control file: <no ctrlfile>

4 ETW000 R3trans was called as follows: R3trans -d

4 ETW000 trace at level 2 opened for a given file pointer

4 ETW000 [dev trc ,00000] Wed Feb 14 01:12:35 2007

64 0.000064

4 ETW000 [dev trc ,00000] db_con_init called

19 0.000083

4 ETW000 [dev trc ,00000] create_con (con_name=R/3)

41 0.000124

4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/PRD/SYS/exe/run/dbd

b6slib.o' ...

4 ETW000

39 0.000163

4 ETW000 [dev trc ,00000] load shared library (/usr/sap/PRD/SYS/exe/run/db

db6slib.o), hdl 0

4 ETW000

771 0.000934

4 ETW000 [dev trc ,00000] Library '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o' l

oaded

4 ETW000

29 0.000963

4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sa

p/PRD/SYS/exe/run/dbdb6slib.o

4 ETW000

31 0.000994

4 ETW000 [dev trc ,00000] Version of '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o

' is "700.08", patchlevel (0.52)

4 ETW000

146 0.001140

4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/s

ap/PRD/SYS/exe/run/dbdb6slib.o

4 ETW000

31 0.001171

4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/

sap/PRD/SYS/exe/run/dbdb6slib.o

4 ETW000

31 0.001202

4 ETW000 [dev trc ,00000] New connection 0 created

23 0.001225

4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCO

NNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, oc

c = NO

36 0.001261

4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3)

37 0.001298

4 ETW000 [dev trc ,00000] find_con_by_name found the following connection

for reuse:

4 ETW000

29 0.001327

4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCON

NECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ

= NO

4 ETW000

33 0.001360

4 ETW000 [dev trc ,00000] DB6 (DB2 UDB) UNICODE database interface 700.08

[opt]

4 ETW000

582 0.001942

4 ETW000 [dev trc ,00000] DB6 shared library (dbdb6slib) patchlevels

19 0.001961

4 ETW000 [dev trc ,00000] (0.8) DB6: V8.2.2 optguidelines in OPEN SQL (n

ote 150037)

4 ETW000

29 0.001990

4 ETW000 [dev trc ,00000] (0.8) Support of SDBUPDEXCL (note 847616)

20 0.002010

4 ETW000 [dev trc ,00000] (0.9) DB6: use export file for dbdb6slib (note

835135)

4 ETW000

29 0.002039

4 ETW000 [dev trc ,00000] (0.9) DB6: Core in getAndBindSQLDA (note 83318

3)

4 ETW000

28 0.002067

4 ETW000 [dev trc ,00000] (0.10) DB6: link dbdb6slib.dll on windows with

libdb6.obj (note 761159)

4 ETW000

30 0.002097

4 ETW000 [dev trc ,00000] (0.10) DB6: DUPLICATE_KEY on MERGE -> repeat (

note 851474)

4 ETW000

37 0.002134

4 ETW000 [dev trc ,00000] (0.15) DB6: wrong CAST for short string ABAP t

ype (note 861905)

4 ETW000

1021 0.003155

4 ETW000 [dev trc ,00000] (0.17) DB6: special characters in sidadm passw

d (note 865839)

4 ETW000

29 0.003184

4 ETW000 [dev trc ,00000] (0.21) DB6: no SAP_INFO comments (note 873889)

4 ETW000

29 0.003213

4 ETW000 [dev trc ,00000] (0.22) DB6: hints: get correlation names from

view texts (note 868888)

4 ETW000

29 0.003242

4 ETW000 [dev trc ,00000] (0.23) DB6: hints: get correlation names from

view texts (note 868888)

4 ETW000

29 0.003271

4 ETW000 [dev trc ,00000] (0.26) DB6: DB6_DBSL_CLP_COMMAND STRING_BAD_RE

F (note 883402)

4 ETW000

29 0.003300

4 ETW000 [dev trc ,00000] (0.27) DB6: activate value compression (note 8

86231)

4 ETW000

29 0.003329

4 ETW000 [dev trc ,00000] (0.28) DB6: optimization guidelines on views p

art 2 (note 868888)

4 ETW000

29 0.003358

92111)

4 ETW000

29 0.003387

4 ETW000 [dev trc ,00000] (0.33) DB6: append SAP_TA comment (note 873889

)

4 ETW000

29 0.003416

4 ETW000 [dev trc ,00000] (0.34) DB6: activate value compression with qu

oted names (note 886231)

4 ETW000

29 0.003445

4 ETW000 [dev trc ,00000] (0.36) DB6: Repeat isolated DDL statements aft

er SQL0911 (note 901338)

4 ETW000

29 0.003474

4 ETW000 [dev trc ,00000] (0.41) DB6: add V9 to list of supported DB2 re

leases (note 912386)

4 ETW000

29 0.003503

4 ETW000 [dev trc ,00000] (0.50) DB6: reread passwords for secondary con

nections (note 931742)

4 ETW000

30 0.003533

delines (note 868888)

4 ETW000

29 0.003562

4 ETW000 [dev trc ,00000] Supported features:

18 0.003580

4 ETW000 [dev trc ,00000] - CLI LOAD for INSERT ... FULLSELECT

18 0.003598

4 ETW000 [dev trc ,00000] ..retrieving configuration parameters

19 0.003617

4 ETW000 [dev trc ,00000] ..done

95 0.003712

4 ETW000 [dev trc ,00000] Running with UTF-8 Unicode

19 0.003731

4 ETW000 [dev trc ,00000] DB2 library /db2/db2prd/sqllib/lib64/libdb2.a(sh

r_64.o) successfully loaded

4 ETW000

12566 0.016297

4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (BEGIN)

78186 0.094483

4 ETW000 [dev trc ,00000] &+ DbSlConnectDB6( SQLConnect 😞 [IBM][CLI D

river] SQL30061N The database alias or database name "PRDL

4 ETW000

48 0.094531

TATE=08004

4 ETW000

32 0.094563

4 ETW000 [dev trc ,00000] &+

4 ETW000

31 0.094594

4 ETW000 [dev trc ,00000] &+

4 ETW000

32 0.094626

4 ETW000 [dev trc ,00000] &+

4 ETW000

31 0.094657

4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (END)

20 0.094677

4 ETW000 [dbdb6.c ,00000] *** ERROR => DbSlConnect to 'PRD' as 'sapprd' fa

iled

4 ETW000

50 0.094727

2EETW169 no connect possible: "DBMS = DB6 --- DB2DB

DFT = 'PRD'"

******************

Regards,

Gautam.

Former Member
0 Kudos

Hi

First lets leave that ARP issues behind .

the Error you get


>>>snip<<<
2007-02-12-02.54.25.178082-360 E41801428A421 LEVEL: Error
PID : 741486 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.
A possible cause is that the maximum number of agents has been
exceeded.

2007-02-12-02.54.25.178309-360 I41801850A386 LEVEL: Error
PID : 741486 TID : 1 PROC : db2tcpcm 0
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
MESSAGE : Return code from sqleGetAgent =
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFF6614 : FFFF FB36 ...6
>>>unsnip<<<

You get only on Node B .

I suppose you have an different Database+Node Directory on Node A and Node B

[Due to different Installation Types on Node A [CI+DB] and Node B[DI]]

Please give us an

list database directory 
list node directory

from <b>Node A</b>

This Error is caused by an incorrect Database cataloging on Node B and the connect to database PRD works only , if Hostname gipdb is not local due to remote cataloging .

So first let us know , how your DB is cataloged on node A

[list db+node directory ] to provide further assistance .

Hth+Best regards

dirk

Former Member
0 Kudos

Hello,

List Database Directory of Node A :

gipdb:db2prd 2> db2 list database directory

System Database Directory

Number of entries in the directory = 1

Database 1 entry:

Database alias = PRD

Database name = PRD

Local database directory = /db2/PRD

Database release level = a.00

Comment = SAP database PRD

Directory entry type = Indirect

Catalog database partition number = 0

Alternate server hostname =

Alternate server port number =

list db node directory of Node A :

gipdb:db2prd 7> db2 list node directory

SQL1027N The node directory cannot be found.

I am also giving these of Node B

gipapp:prdadm 4> db2 list node directory

Node Directory

Number of entries in the directory = 2

Node 1 entry:

Node name = GIPAPP

Comment =

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = gipdb

Service name = sapdb2PRD

Node 2 entry:

Node name = NODEPRD

Comment = TCPIP Node for database PRD

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = gipdb

Service name = sapdb2PRD

gipapp:prdadm 5> db2 list db directory

System Database Directory

This catalog has been created by SAP in Node B

Please help me ASAP

Thanks

Gautam

Number of entries in the directory = 1

Database 1 entry:

Database alias = PRD

Database name = PRD

Node name = NODEPRD

Database release level = a.00

Comment = Remote database PRD

Directory entry type = Remote

Catalog database partition number = -1

Alternate server hostname =

Alternate server port number =

gipapp:prdadm 6>

Frank-Martin
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Gautam,

it is not supprising that R3trans and startdb fail if you can not connect to the database.

As you can see from the db and node directory, your database is cataloged remotely pointing to a database on gipdb. You did not state on which node you have executed the commands. I guess you did it on the dialog instance. Please do the same on the db server gipdb.

The DB2 instance on gipdb has to contain a local database with name PRD.

After takeover of the db server to the other node the catalog entry of the local database has to be taken over to the new DB server.

As far as I know HACMP is script based and your HACMP scripts have to perform the catalog changes.

Regards

Frank

Former Member
0 Kudos

Hello Frank,

In my case "gipdb" is virtual host name where i have installed CI + DB. All is working fine in this node ie. gipdb.

I have installed DB + CI on one virtual host ie. gipdb. I am trying to startup CI + DB in Node B ie. gipapp. Dialog Instance not running in Node B "gipapp" when I try to startup database & CI.

Thanks,

Gautam.

Former Member
0 Kudos

Dear Frank,

Thanks for your reply. But please reply below this.

Now what will I do? Can I reconfigured the HACMP Clustering software? I have also doubt about the clustering software HACMP. I have told also to IBM but they were not agreed.

All the users are created with the Virtual hostname but I know it should be with the local server name ( here gipdb_pers and gipapp_pers ). Here when I connect with the user ID prdadm, it is showing gipdb:prdadm> and gipapp:prdadm> and other users. I think it should be gipdb_pers:prdadm> and gipapp_pers:prdadm>. What is your idea about this?

I have worked in HACMP clustering environment under Oracle 10g and SAP ECC 6.0 (SR1). This is working fine.

Here Host file entries are like that:

192.168.213.41 gipdb_svc gipdb (Virtaul IP) - Node A

192.168.213.42 gipapp_svc gipapp (Virtaul IP) Node B

192.168.213.43 gipdb_pers (Actual IP ) Node A

192.168.213.44 gipapp_pers (Actual IP ) Node B

What will I do now? I have to complete the Installation ASAP and I have

to take a decision regarding this. Please help me ASAP about this.

Another thing is that, when Database and SAP Central system in Node A, SAP is working fine and Dialog instance is working in Node B. So, DB2 client is working to connect the DB2 Database which is in Node A. I think DB2 Client in Node B is working fine.

My SAP Installation is ok or not?

Please guide me what will I do? Will I reconfigure HACMP Clustering software or not?

Thanks

Gautam Poddar

PricewaterhouseCoopers India

Frank-Martin
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Gautam,

I would first try some tests with DB2 CLP commands.

You should execute the following commands on both sides before and after the take over.

db2 list db directory

db2 list node directory

db2 connect to DB user <user> using <pwd>

I guess that your database is cataloged remotely on your dialog instance and locally on your db server before that take over. I am not sure what happens during the take over in your HACMP scripts.

The HACMP scripts will have to adjust the catalog entries during take over.

Regards

Frank

Former Member
0 Kudos

Dear Frank,

I have executed all the commands as below: DB2START is now successful but STARTSAP db is still failing. Pls suggest me what should i do now??

gipapp:prdadm 1> db2 list db directory

System Database Directory

Number of entries in the directory = 1

Database 1 entry:

Database alias = PRD

Database name = PRD

Node name = NODEPRD

Database release level = a.00

Comment = Remote database PRD

Directory entry type = Remote

Catalog database partition number = -1

Alternate server hostname =

Alternate server port number =

gipapp:prdadm 2> db2 list node directory

Node Directory

Number of entries in the directory = 2

Node 1 entry:

Node name = GIPAPP

Comment =

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = gipdb

Service name = sapdb2PRD

Node 2 entry:

Node name = NODEPRD

Comment = TCPIP Node for database PRD

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = gipdb

Service name = sapdb2PRD

gipapp:prdadm 3> db2 connect to PRD user prdadm using admin123

SQL30081N A communication error has been detected. Communication protoco

being used: "TCP/IP". Communication API being used: "SOCKETS". Location

where the error was detected: "192.168.213.41". Communication function

detecting the error: "recv". Protocol specific error code(s): "", "", "

SQLSTATE=08001

gipapp:prdadm 4> db2start

02/12/2007 02:53:59 0 0 SQL1026N The database manager is already activ

.

SQL1026N The database manager is already active.

gipapp:prdadm 5> startsap db

Checking db6 db Database

-


ABAP Database is not available via R3trans

Starting SAP-Collector Daemon

-


***********************************************************************

  • This is Saposcol Version COLL 20.89 700 - AIX v6.55 5L-64 bit 060323

  • Usage: saposcol -l: Start OS Collector

  • saposcol -k: Stop OS Collector

  • saposcol -d: OS Collector Dialog Mode

  • saposcol -s: OS Collector Status

  • The OS Collector (PID 594080) is already running .....

************************************************************************

saposcol already running

Running /usr/sap/PRD/SYS/exe/run/startdb

02/12/2007 02:54:17 0 0 SQL1026N The database manager is already activ

.

SQL1026N The database manager is already active.

Activate database failed

R3trans connect failed

DB startup failed

gipapp:prdadm 6>

Regards & Thanks,

Gautam.

Former Member
0 Kudos

Hi

pls check that the DB2 Ports are the same in /etc/services on Node A and Node B

Check for Port's named
sapdb2<DBSID>

DB2_db2<dbsid>
DB2_db2<dbsid>_1   
DB2_db2<dbsid>_2
DB2_db2<dbsid>_...
...
DB2_db2<dbsid>_END 

and that no other product is using your communication port's on host B .

Hth + best regards

dirk

Former Member
0 Kudos

Hello Dirk,

I have installed the DB2 software locally into both the Nodes Node A and Node B and FixPak 12 also. After that I have installed the Central System ( which is included CI + Database + ASCS) in Node A into the shared mont Points and Virtual name and IP. Actually it is like a single package clustering. When I down the Node A, CI and DB also moved from Node A to Node B. I am trying to start the SAP in Node B. But I am unable to startup the SAP Central System. I have also installed the dialog instance in Node B locally.

What will I do for this case. Which parameter will be set for this to start the DB2 Database?

db2set -all in Node B :

  1. su - db2prd

gipapp:db2prd 1> db2set -all

[e] DB2CODEPAGE=819

[e] DB2COMM=TCPIP

[e] DB2COUNTRY=1

[e] DB2DBDFT=PRD

<i> DB2TCPCONNMGRS=1

<i> DB2CONNECT_IN_APP_PROCESS=NO

<i> DB2COMM=TCPIP

[g] DB2SYSTEM=gipapp

[g] DB2ADMINSERVER=dasusr1

gipapp:db2prd 2>

db2 get dbm cfg in Node B

gipapp:db2prd 2> db2 get dbm cfg

Database Manager Configuration

Node type = Client

Database manager configuration release level = 0x0a00

Federated Database System Support (FEDERATED) = NO

Transaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT_ACCOUNT_STR) =

Java Development Kit installation path (JDK_PATH) = /usr/java14_64

Diagnostic error capture level (DIAGLEVEL) = 3

Notify Level (NOTIFYLEVEL) = 3

Diagnostic data directory path (DIAGPATH) = /db2/db2prd/sqllib/d

2dump

SYSADM group name (SYSADM_GROUP) = DBPRDADM

SYSCTRL group name (SYSCTRL_GROUP) = DBPRDCTL

SYSMAINT group name (SYSMAINT_GROUP) = DBPRDMNT

SYSMON group name (SYSMON_GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =

Client Kerberos Plugin (CLNT_KRB_PLUGIN) =

Group Plugin (GROUP_PLUGIN) =

GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =

Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED

Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =

Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =

Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED

Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT

Cataloging allowed without authority (CATALOG_NOAUTH) = NO

Bypass federated authentication (FED_NOAUTH) = NO

Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048

Directory cache support (DIR_CACHE) = YES

Max requester I/O block size (bytes) (RQRIOBLK) = 32767

Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10

Transaction manager database name (TM_DATABASE) = 1ST_CONN

Discovery mode (DISCOVER) = SEARCH

gipapp:db2prd 3>

./db2ilist value is db2prd

I have tried to execute this command also

./db2iupdt db2prd but it is not accepting in Node B.

I have also copied all the port no.( DB2 related ) from the service file of Node A to Node B.

How will I create the catalog? How will I check the catalog is moved or not from Node A to Node B?

Please help me ASAP

Thanks

Gautam

0 Kudos

Hi Gautam,

you said you installed DB2 on both nodes A & B and additional SAP instances. So I assume you installed the DB2 software on both machines and you installed the DB2 instance and the database on a shared disk.

I just want to ask you some questions you can check:

- Did you cataloge the database on your central instance as a remote database?

- Is the setting for db2comm the same on the second node?

- Is the entry in /etc/services for SVCENAME on the second node available?

One additional question according to your setup: do you shutdown the dialog instance to move the central instance as well in case of an failover?

Regards,

Steffen

Former Member
0 Kudos

Hello Stefen,

I have installed DB2 locally on both the nodes. Central Instancce on Node A and then Dialog instance on node B. After that i wanted to test manual failover so i first stopped DB2, dialog and central instance. Then i moved CI and all other mount points to node B to test Manual Failover but in Node B, I am not able start DB2 using following command ---

***********

gipapp:prdadm 7> startsap db

Checking db6 db Database

-


ABAP Database is not available via R3trans

Starting SAP-Collector Daemon

-


***********************************************************************

  • This is Saposcol Version COLL 20.89 700 - AIX v6.55 5L-64 bit 060323

  • Usage: saposcol -l: Start OS Collector

  • saposcol -k: Stop OS Collector

  • saposcol -d: OS Collector Dialog Mode

  • saposcol -s: OS Collector Status

  • The OS Collector (PID 704652) is already running .....

************************************************************************

saposcol already running

Running /usr/sap/PRD/SYS/exe/run/startdb

SQL1063N DB2START processing was successful.

Activate database failed

R3trans connect failed

DB startup failed

*********************

I did not cataloge the database.

And yes the settings for db2comm and SVCENAME are done.

What shouls i do now??

Thanks,

Gautam.

0 Kudos

Hi Gautam,

is your database cataloged correctly after the fail over? Can you just do a db2 list db directory?

BTW: Do you have a use case for just let the CI stay at node A and move DB2 instance to node B? In this case you have to recatalog the database in the db directory of CI to use the virtual hostname.

Are there any additional messages in /db2/PRD/db2dump/db2diag.log?

Regards,

Steffen

Former Member
0 Kudos

Hello Steffen,

I have installed the DB2 software locally into both the Nodes Node A and Node B and FixPak 12 also. After that I have installed the Central System ( which is included CI + Database + ASCS) in Node A into the shared mont Points and Virtual name and IP. Actually it is like a single package clustering. When I down the Node A, CI and DB also moved from Node A to Node B. I am trying to start the SAP in Node B. But I am unable to startup the SAP Central System. I have also installed the dialog instance in Node B locally.

What will I do for this case. Which parameter will be set for this to start the DB2 Database?

db2set -all in Node B :

  1. su - db2prd

gipapp:db2prd 1> db2set -all

[e] DB2CODEPAGE=819

[e] DB2COMM=TCPIP

[e] DB2COUNTRY=1

[e] DB2DBDFT=PRD

<i> DB2TCPCONNMGRS=1

<i> DB2CONNECT_IN_APP_PROCESS=NO

<i> DB2COMM=TCPIP

[g] DB2SYSTEM=gipapp

[g] DB2ADMINSERVER=dasusr1

gipapp:db2prd 2>

db2 get dbm cfg in Node B

gipapp:db2prd 2> db2 get dbm cfg

Database Manager Configuration

Node type = Client

Database manager configuration release level = 0x0a00

Federated Database System Support (FEDERATED) = NO

Transaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT_ACCOUNT_STR) =

Java Development Kit installation path (JDK_PATH) = /usr/java14_64

Diagnostic error capture level (DIAGLEVEL) = 3

Notify Level (NOTIFYLEVEL) = 3

Diagnostic data directory path (DIAGPATH) = /db2/db2prd/sqllib/d

2dump

SYSADM group name (SYSADM_GROUP) = DBPRDADM

SYSCTRL group name (SYSCTRL_GROUP) = DBPRDCTL

SYSMAINT group name (SYSMAINT_GROUP) = DBPRDMNT

SYSMON group name (SYSMON_GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =

Client Kerberos Plugin (CLNT_KRB_PLUGIN) =

Group Plugin (GROUP_PLUGIN) =

GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =

Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED

Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =

Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =

Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED

Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT

Cataloging allowed without authority (CATALOG_NOAUTH) = NO

Bypass federated authentication (FED_NOAUTH) = NO

Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048

Directory cache support (DIR_CACHE) = YES

Max requester I/O block size (bytes) (RQRIOBLK) = 32767

Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10

Transaction manager database name (TM_DATABASE) = 1ST_CONN

Discovery mode (DISCOVER) = SEARCH

gipapp:db2prd 3>

./db2ilist value is db2prd

I have tried to execute this command also

./db2iupdt db2prd but it is not accepting in Node B.

I have also copied all the port no.( DB2 related ) from the service file of Node A to Node B.

How will I create the catalog? How will I check the catalog is moved or not from Node A to Node B?

Please help me ASAP

Thanks

Gautam

0 Kudos

Hi Gautam,

is the output of db2set -all the same as on node A? It seems your workload is not set to SAP: <i> DB2_WORKLOAD=SAP

In your setup scenario you might not need to recatalog the database for your CI since you always move both CI and DB. You can check this by issuing "db2 list db directory" and db2 "list node directory" on node B and check if your PRD database is registered. I just thought you installed the CI and the DB each on a virtual hostname. So you could have moved DB2 without restarting the application servers. One possible scenario could have been you need more perfromance for the database so you could have moved DB2 to the second node and shutdown the DI to get more memory ...

Have you checked that no other application uses your ports on node B like Dirk already mentioned? Are there any additional messages in /db2/db2prd/sqllib/d2dump?

Regards,

Steffen

Former Member
0 Kudos

Dear Steffen,

Thanks for your reply.

Parameter DB2_WORKLOAD=SAP is set correctly. Pls check below output.

We have isnatlled DB + CI on one virtual host ie. gipdb. We are trying to startup CI + DB in NOde B ie. gipapp. Dialaog Instance not running in Node B "gipapp" when we try to startup database & CI. And no other application uses ports on node B?

There are 3 files in /db2/db2prd/sqllib -- db2diag.log, db2eventlog.000 and db2prd.nfy

I have executed all the commands as told by you: DB2START is now successful but STARTSAP db is still failing. Pls suggest me what should i do??

gipapp:prdadm 1> db2set -all

[e] DB2CODEPAGE=819

[e] DB2COMM=TCPIP

[e] DB2COUNTRY=1

[e] DB2DBDFT=PRD

<i> DB2_WORKLOAD=SAP

<i> DB2_TRUNCATE_REUSESTORAGE=IMPORT [DB2_WORKLOAD]

<i> DB2_MDC_ROLLOUT=YES [DB2_WORKLOAD]

<i> DB2_SKIPINSERTED=YES [DB2_WORKLOAD]

<i> DB2_VIEW_REOPT_VALUES=YES [DB2_WORKLOAD]

<i> DB2_OBJECT_TABLE_ENTRIES=65532 [DB2_WORKLOAD]

<i> DB2_OPTPROFILE=YES [DB2_WORKLOAD]

<i> DB2_IMPLICIT_UNICODE=YES [DB2_WORKLOAD]

<i> DB2_INLIST_TO_NLJN=YES [DB2_WORKLOAD]

<i> DB2_MINIMIZE_LISTPREFETCH=YES [DB2_WORKLOAD]

<i> DB2_UPDATE_PART_KEY=YES [DB2_WORKLOAD]

<i> DB2_REDUCED_OPTIMIZATION=4,INDEX,JOIN [DB2_WORKLOAD]

<i> DB2NOTIFYVERBOSE=YES [DB2_WORKLOAD]

<i> DB2_INTERESTING_KEYS=YES [DB2_WORKLOAD]

<i> DB2_EVALUNCOMMITTED=YES_DEFERISCANFETCH [DB2_WORKLOAD]

<i> DB2_ANTIJOIN=EXTEND [DB2_WORKLOAD]

<i> DB2MEMMAXFREE=2000000 [DB2_WORKLOAD]

<i> DB2ENVLIST=INSTHOME SAPSYSTEMNAME dbs_db6_schema DIR_LIBRARY LIBPATH

<i> DB2_RR_TO_RS=YES [DB2_WORKLOAD]

<i> DB2_FORCE_FCM_BP=YES [DB2_WORKLOAD]

<i> DB2COUNTRY=1

<i> DB2COMM=TCPIP [O]

[g] DB2SYSTEM=gipapp

[g] DB2ADMINSERVER=dasusr1

gipapp:prdadm 1> db2 list db directory

System Database Directory

Number of entries in the directory = 1

Database 1 entry:

Database alias = PRD

Database name = PRD

Node name = NODEPRD

Database release level = a.00

Comment = Remote database PRD

Directory entry type = Remote

Catalog database partition number = -1

Alternate server hostname =

Alternate server port number =

gipapp:prdadm 2> db2 list node directory

Node Directory

Number of entries in the directory = 2

Node 1 entry:

Node name = GIPAPP

Comment =

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = gipdb

Service name = sapdb2PRD

Node 2 entry:

Node name = NODEPRD

Comment = TCPIP Node for database PRD

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = gipdb

Service name = sapdb2PRD

gipapp:prdadm 3> db2 connect to PRD user prdadm using admin123

SQL30081N A communication error has been detected. Communication protoco

being used: "TCP/IP". Communication API being used: "SOCKETS". Location

where the error was detected: "192.168.213.41". Communication function

detecting the error: "recv". Protocol specific error code(s): "", "", "

SQLSTATE=08001

gipapp:prdadm 4> db2start

02/12/2007 02:53:59 0 0 SQL1026N The database manager is already activ

.

SQL1026N The database manager is already active.

gipapp:prdadm 5> startsap db

Checking db6 db Database

-


ABAP Database is not available via R3trans

Starting SAP-Collector Daemon

-


***********************************************************************

  • This is Saposcol Version COLL 20.89 700 - AIX v6.55 5L-64 bit 060323

  • Usage: saposcol -l: Start OS Collector

  • saposcol -k: Stop OS Collector

  • saposcol -d: OS Collector Dialog Mode

  • saposcol -s: OS Collector Status

  • The OS Collector (PID 594080) is already running .....

************************************************************************

saposcol already running

Running /usr/sap/PRD/SYS/exe/run/startdb

02/12/2007 02:54:17 0 0 SQL1026N The database manager is already activ

.

SQL1026N The database manager is already active.

Activate database failed

R3trans connect failed

DB startup failed

gipapp:prdadm 2> db2 get dbm cfg

Database Manager Configuration

Node type = Enterprise Server Edition with local and remote clients

Database manager configuration release level = 0x0a00

CPU speed (millisec/instruction) (CPUSPEED) = 4.000000e-05

Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.250000e+00

Max number of concurrently active databases (NUMDB) = 8

Data Links support (DATALINKS) = NO

Federated Database System Support (FEDERATED) = NO

Transaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT_ACCOUNT_STR) =

Java Development Kit installation path (JDK_PATH) = /usr/java14_64

Diagnostic error capture level (DIAGLEVEL) = 3

Notify Level (NOTIFYLEVEL) = 3

Diagnostic data directory path (DIAGPATH) = /db2/PRD/db2dump

Default database monitor switches

Buffer pool (DFT_MON_BUFPOOL) = OFF

Lock (DFT_MON_LOCK) = OFF

Sort (DFT_MON_SORT) = OFF

Statement (DFT_MON_STMT) = OFF

Table (DFT_MON_TABLE) = OFF

Timestamp (DFT_MON_TIMESTAMP) = ON

Unit of work (DFT_MON_UOW) = OFF

Monitor health of instance and databases (HEALTH_MON) = ON

SYSADM group name (SYSADM_GROUP) = DBPRDADM

SYSCTRL group name (SYSCTRL_GROUP) = DBPRDCTL

SYSMAINT group name (SYSMAINT_GROUP) = DBPRDMNT

SYSMON group name (SYSMON_GROUP) =

Client Userid-Password Plugin (CLNT_PW_PLUGIN) =

Client Kerberos Plugin (CLNT_KRB_PLUGIN) =

Group Plugin (GROUP_PLUGIN) =

GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =

Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED

Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =

Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =

Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED

Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT

Cataloging allowed without authority (CATALOG_NOAUTH) = NO

Trust all clients (TRUST_ALLCLNTS) = YES

Trusted client authentication (TRUST_CLNTAUTH) = CLIENT

Bypass federated authentication (FED_NOAUTH) = NO

Default database path (DFTDBPATH) = /db2/PRD

Database monitor heap size (4KB) (MON_HEAP_SZ) = 90

Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048

Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0

Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC

Backup buffer default size (4KB) (BACKBUFSZ) = 1024

Restore buffer default size (4KB) (RESTBUFSZ) = 1024

Sort heap threshold (4KB) (SHEAPTHRES) = 20000

Directory cache support (DIR_CACHE) = YES

Application support layer heap size (4KB) (ASLHEAPSZ) = 15

Max requester I/O block size (bytes) (RQRIOBLK) = 32767

Query heap size (4KB) (QUERY_HEAP_SZ) = 1000

Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10

Priority of agents (AGENTPRI) = SYSTEM

Max number of existing agents (MAXAGENTS) = 400

Agent pool size (NUM_POOLAGENTS) = 200(calculated)

Initial number of agents in pool (NUM_INITAGENTS) = 0

Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS - NUM_INI

AGENTS)

Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS

Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS

Keep fenced process (KEEPFENCED) = YES

Number of pooled fenced processes (FENCED_POOL) = MAX_COORDAGENTS

Initial number of fenced processes (NUM_INITFENCED) = 0

Index re-creation time and redo index build (INDEXREC) = RESTART

Transaction manager database name (TM_DATABASE) = 1ST_CONN

Transaction resync interval (sec) (RESYNC_INTERVAL) = 180

SPM name (SPM_NAME) =

SPM log size (SPM_LOG_FILE_SZ) = 256

SPM resync agent limit (SPM_MAX_RESYNC) = 20

SPM log path (SPM_LOG_PATH) =

TCP/IP Service name (SVCENAME) = sapdb2PRD

Discovery mode (DISCOVER) = SEARCH

Discover server instance (DISCOVER_INST) = ENABLE

Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY

Enable intra-partition parallelism (INTRA_PARALLEL) = NO

No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 4096

Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATIC

Number of FCM connection entries (FCM_NUM_CONNECT) = AUTOMATIC

Number of FCM message anchors (FCM_NUM_ANCHORS) = AUTOMATIC

Node connection elapse time (sec) (CONN_ELAPSE) = 10

Max number of node connection retries (MAX_CONNRETRIES) = 5

Max time difference between nodes (min) (MAX_TIME_DIFF) = 60

db2start/db2stop timeout (min) (START_STOP_TIME) = 10

Pls suggest me how to resolve this issue?

Regards & Thanks,

Gautam.

Former Member
0 Kudos

Dear Steffen,

I am going to uninstall all these and and reconfigure from HACMP Clustering. Can you check all these and confirm me these are ok or not?

These are the mount points whcih will be configured with HACMP.

1. /db2 - This is in Shared drive

2. /db2/PRD - This is in Shared drive

3. /db2/PRD/db2dump - This is in Shared drive

4. /db2/PRD/log_dir - This is in Shared drive

5. /db2/PRD/sapdata1 - This is in Shared drive

6. /db2/PRD/saptemp1 - This is in Shared drive

7. /export/sapPRD - This is in Shared drive

8. /export/sapmnt - This is in Shared drive

9. /export/saptrans - This is in Shared drive

Node A and Node B :

/usr/opt/db2_08_01 - Locally

Node B :

/usr/sap/PRD/D01 - Locally in Node B

We are going to configure HACMP for single package. Either Node A will be working or Node B will be working.

Intially CI and DB will be working in Node A and Dialog Instance will be working in Node A. If node A fails, CI and DB will be working in Node B and Dialoglog Instance. Here it will be not possible to configure two package clustering because there is small no. HD in storage box. For that reason I can not try to install the SAP High Availabily option.

So I want to install the DB2 Database software will be installed Locallyin Node A and Node B. After that I will install the SAP Central system in Node A with the Virtual host name with Virual IP. So, if Node A fails, Virtual name and Virtual IP will be moved from Node A to Node B. So I will start the CI and Database in Node B. After successfull , I will Install the dialog instance in Node B Locally.

Please confim this.

Thanks

Gautam

0 Kudos

Hi Gautam,

first of all I do not understand why you want to uninstall everything. Do you plan to change your setup during reinstall?

Are there any helpfull messages at the end of db2diag.log? Have you already confirmed the move of the virtual IP address succeeded?

Your shared disk setup looks strange: Why do you mount /db2 as a shared disk? How many shared disk do you have? Are these different physical disks?

In case you have only one physical disk or raid setup you only have to put /db2/PRD and /db2/db2prd on the shared disk. For your SAP file systems you have to ensure the second node exports the file systems using the same configuration as node A. Otherwise the DI cannot mount the NFS shares.

In case of an failover do you still have enough resources on node B to run 2 SAP application servers and the database instance? I would rather shutdown DI and run DB and CI only.

FYI: In case you would use DB2 9 rather than V8 FP12 you could install DB2 on the shared disk as well. So you only have to apply FixPacks once.

FYI: In the home directories of the users prdadm and db2prd there are some environment scripts. Some of them have the real hostname of node A in their name. So on node A the scripts with the hostname A are taken on node B the ones without the hostnames will setup your environment. For your setup you should ensure you use the same environment scripts on both nodes.

Regards,

Steffen

Former Member
0 Kudos

Dear steffen,

Thanks for your reply. I thougt my installtion and filesystems are wrong. I have no plan to change the installation.

How will I confirmed the virtual IP successfully moved?

My current file system ls like that :

1. /db2 - This is in Local dive of Node A and Node B

2. /db2/PRD - This is in Shared drive

3. /db2/PRD/db2dump - This is in Shared drive

4. /db2/PRD/log_dir - This is in Shared drive

5. /db2/PRD/sapdata1 - This is in Shared drive

6. /db2/PRD/saptemp1 - This is in Shared drive

7. /export/sapPRD - This is in Shared drive

8. /export/sapmnt - This is in Shared drive

9. /export/saptrans - This is in Shared drive

Home directory of the db2prd is created in /db2. So I thought if i will create this mount point in share drive, it will be automatically available in Node B after moving the virtual IP from Node A to Node. That is my reason to change the file system /db2 from Local to share drive.

Another thing if I will create the mount point /db2/db2prd in share drive, there is no requirement to create the /db2 mount point. What is your idea.

I have already copied the .dbenv_gipdb.csh and .dbenv_gipdb.sh of /home/prdadm and /db2/db2prd from Node A to Node B and I have changed these files .dbenv_gipapp.csh and .dbenv_gipapp.sh.

Yes, there is so much resource to run CI + DB + Dialog in Node B.

What will I do? Can I move to reinstall or not?

I am getting this out put after executing the netstat command in Node B.

***********************************************************************************

Active Internet connections

Proto Recv-Q Send-Q Local Address Foreign Address (state)

tcp4 0 2 gipapp_pers.telnet 192.168.213.21.4talk ESTABLISHED

tcp4 0 0 loopback.smux loopback.filenet- ESTABLISHED

tcp4 0 0 loopback.filenet- loopback.smux ESTABLISHED

tcp4 0 0 loopback.smux loopback.32778 ESTABLISHED

tcp4 0 0 loopback.32778 loopback.smux ESTABLISHED

tcp4 0 0 gipapp_pers.32821 gipdb.trap-dae CLOSE_WAIT

tcp4 0 0 gipapp.32844 gipdb.trap-dae CLOSE_WAIT

tcp4 0 0 gipapp.filenet- gipapp.32775 ESTABLISHED

tcp4 0 0 gipapp.32775 gipapp.filenet- ESTABLISHED

tcp4 0 0 gipapp.filenet- gipapp.32776 ESTABLISHED

tcp4 0 0 gipapp.32776 gipapp.filenet- ESTABLISHED

tcp4 0 0 gipapp.filenet- gipapp.32777 ESTABLISHED

tcp4 0 0 gipapp.32777 gipapp.filenet- ESTABLISHED

udp4 0 0 192.168.0.255.topsvcs .

udp4 0 0 gipapp_boot.topsvcs .

udp4 0 0 192.167.0.255.topsvcs .

udp4 0 0 gipapp_stby.topsvcs .

udp4 0 0 loopback.32823 loopback.tick-por

udp4 0 0 loopback.32831 loopback.cpq-task

***********************************************************************************

Actually my douubts are for reinstallation :

All the users are created with the Virtual hostname but I kanow it should be with the local server name ( here gipdb_pers and gipapp_pers ). Here when I connect with the user ID prdadm, it is showing <gipdb>prdadm> and <gipapp>prdadm> and other users. I think it should be <gipdb_pers>prdadm> and <gipapp_pers>prdadm. What is your idea about this?

I have worked in HACMP clustering environment under Oracle 10g and SAP ECC 6.0 (SR1). This was working fine.

Here Host file entries are like that:

192.168.213.41 gipdb_svc gipdb (Virtaul IP) - Node A

192.168.213.42 gipapp_svc gipapp (Virtaul IP) Node B

192.168.213.43 gipdb_pers (Actual IP ) Node A

192.168.213.44 gipapp_pers (Actual IP ) Node B

*****************************************************************************

Please help me ASAP.

Thanks

Gautan