DB2 database hangs when archive logs cannot be written to NetBackup
I have an issue with a new NB set up. We are running DB2 v9.7 on Netbackup 7.1 - AIX 6.1.
I have encoutnered an issue with the config, where the DB2 database hangs/refuses connections when it is unable to write its archive log to netbackup when using userexit and arcfunc save. When the media server is available, this has all looked spot on, backups complete fine and the restore process has been tested successfully.
I am however reluctant to roll this out to the production DB's until i know how to prevent the DB hanging if the media or master servers are unavailable.
2012-01-17-126.96.36.1997114-360 I6347562A374 LEVEL: Info
PID : 15466644 TID : 3636 PROC : db2sysc 0
INSTANCE: xxxx NODE : 000 DB : XXXX
EDUID : 3636 EDUNAME: db2loggr (QHPI04) 0
FUNCTION: DB2 UDB, data protection services, sqlpghck, probe:1780
MESSAGE : DB2 is waiting for log files to be archived.
When these archive log processes are queued up due to the media server not being available to archive the logs, the DB becomes unavailable until the processes either complete or are killed off.Any ideas how to prevent this other than having a workaround whereby we use arcfunc copy, to write the archive logs to local disk and then archive the entire directory off to netbackup?