Closed as program error.
If customer has a split mirrored db that was put into standby mode using db2inidb, and a parallel offline backup is taken using db2_all, this can cause certain non-catalog nodes to fail the backup. If APAR is not applied, parallel backup of a split mirrored db in standby mode using db2_all will fail on some non-catalog nodes. In the db2diag.log you will see a message similar to the following: 2008-03-04-22.214.171.124703-300 E12827A463 LEVEL: Error PID : 291742 TID : 1 PROC : db2agent (DB8) 0 INSTANCE: eddie2 NODE : 000 APPHDL : 0-248 APPID: *N0.eddie2.080304201035 AUTHID : EDDIE2 FUNCTION: DB2 UDB, base sys utilities, sqleSubsequentConnect, probe:65 MESSAGE : SQL1117N A connection to or activation of database "DB8 " cannot be made because of ROLL-FORWARD PENDING. You might also see the following from the db2_all script: db2y01@uncletitus:/db2/Y01/sqllib/acs>db2_all "<<-0<|| db2 backup db y01 to /dev/null exclude logs" rah: omitting logical node 0 rah: primary monitoring process for db2 is 5554390 uncletitus: SQL2406N The BACKUP cannot be performed because the database needs to be uncletitus: rolled forward. SQLSTATE=57019 uncletitus: db2 backup db y01 ... completed rc=4 uncletitus: SQL2406N The BACKUP cannot be performed because the database needs to be uncletitus: rolled forward. SQLSTATE=57019 uncletitus: db2 backup db y01 ... completed rc=4 uncletitus: uncletitus: Backup successful. The timestamp for this backup image is : 20080213122721 uncletitus: uncletitus: db2 backup db y01 ... completed ok
The workaround is to backup the individual non-catalog nodes serially. Defect 379514 will fix this issue.
See notes above.
First fixed in DB2 UDB Version 8, FixPak 17.
Reported component name
DB2 UDB ESE AIX
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
DB2 UDB ESE AIX
Fixed component ID
Applicable component levels