For some reason, DB2 is taking a long time to start archiving the
logs. Pls, do you know what could be causing it?
I see the following msgs on db2diag.log


2008-09-04-00.36.24.414103+000 I415281A322 LEVEL: Warning
PID : 1585198 TID : 1 PROC : db2loggr
(SGPPBWG2) 0
INSTANCE: ucsdb2 NODE : 000 DB : SGPPBWG2
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
MESSAGE : DB2 is waiting for log files to be archived.

2008-09-04-00.37.24.412810+000 I415604A429 LEVEL: Warning
PID : 1585198 TID : 1 PROC : db2loggr
(SGPPBWG2) 0
INSTANCE: ucsdb2 NODE : 000 DB : SGPPBWG2
FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1800
DATA #1 : String, 133 bytes
DB2 was unable to confirm logs were archived.
Return code -2029059911, FirstArchNum 2875, FirstArchNum2 4294967295,
HeadExtentID 2911

2008-09-04-00.42.26.590835+000 I416034A333 LEVEL: Warning
PID : 1093740 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: ucsdb2 NODE : 000 DB : SGPPBWG2
APPHDL : 0-788
FUNCTION: DB2 UDB, data protection, sqlpterm, probe:2330
MESSAGE : Some daemon is taking too long to shut down

2008-09-04-00.47.28.826324+000 I416368A333 LEVEL: Warning
PID : 1093740 TID : 1 PROC : db2agent
(idle) 0
INSTANCE: ucsdb2 NODE : 000 DB : SGPPBWG2
APPHDL : 0-788
FUNCTION: DB2 UDB, data protection, sqlpterm, probe:2330
MESSAGE : Some daemon is taking too long to shut down

..... (after many hours)

2008-09-04-03.21.41.642148+000 I428342A379 LEVEL: Warning
PID : 606318 TID : 1 PROC : db2logmgr
(SGPPBWG2) 0
INSTANCE: ucsdb2 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3170
MESSAGE : Completed archive for log file S0002875.LOG to USEREXIT from
/db2/fs13/sgppbwg2/ucsdb2/logs/NODE0000/.

Thanks.

During the issue above, it's not able to connect to database. It hangs.

On Sep 4, 5:51 pm, eliane <elian...@hotmail.comwrote:

During the issue above, it's not able to connect to database. It hangs.

Have you checked the userexit program?

On 4 set, 16:59, w.l.fisc...@googlemail.com wrote:

On Sep 4, 5:51 pm, eliane <elian...@hotmail.comwrote:
>

>
Have you checked the userexit program?

Yes, the userexit program is working fine.

Hi ,
when your archive exit program fail ,
DB2 fall in waiting status until that archive finished .
If you're exit is TSM , have look what it happened at that time .

What is you "failarchpath" configuration ?
if you configure "failarchpath " ,
DB2 can keep processing even if TSM archive fail .

Hope this help

Myoungsoo