By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,143 Members | 855 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,143 IT Pros & Developers. It's quick & easy.

BAckup online with include logs fails !!!

P: 9
Hi all,

db2 9.1 fixpak 0
aix 5.3

I have a big problem every time I start an online backup with include logs via veritas comes out an error!!!
The db2diag shows:
2009-10-29-17.57.22.240269+060 E10634592A396 LEVEL: Info
PID : 995458 TID : 1 PROC : db2agent (idle)
INSTANCE: db2inst1 NODE : 000 DB : ATMDB
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1391
MESSAGE : Starting an online db backup.

2009-10-29-18.34.34.020288+060 I10634989A414 LEVEL: Warning
PID : 1253454 TID : 1 PROC : db2logmgr (ATMDB)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpReadFromVendorDevice, probe:1240
MESSAGE : Return code from sqlpReadFromVendorDevice:
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFD010 : 0000 0019 ....

2009-10-29-18.34.34.021707+060 I10635404A288 LEVEL: Error
PID : 1253454 TID : 1 PROC : db2logmgr (ATMDB)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogVendor, probe:3720
RETCODE : ZRC=0x00000019=25

2009-10-29-18.34.34.961017+060 I10635693A401 LEVEL: Error
PID : 983148 TID : 1 PROC : db2lfr (ATMDB)
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, recovery manager, sqlplfrOpenExtentRetrieve, probe:225
MESSAGE : Received error from db2logmgr on retrieve:
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFD260 : 0000 0019 ....

2009-10-29-18.34.34.961173+060 I10636095A442 LEVEL: Error
PID : 647378 TID : 1 PROC : db2bm.995458.1
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, data protection services, sqlpOpenLogForBackup, probe:20
RETCODE : ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED
"Log could not be retrieved"

2009-10-29-18.34.34.967397+060 E10636538A491 LEVEL: Error
PID : 647378 TID : 1 PROC : db2bm.995458.1
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent, probe:1855
MESSAGE : ADM8010E Backup was unable to copy requested log file "S0004615.LOG"
for inclusion in the backup image. The backup has been aborted.

2009-10-29-18.34.34.967558+060 I10637030A385 LEVEL: Error
PID : 647378 TID : 1 PROC : db2bm.995458.1
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
MESSAGE : Current extent:
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFF6A58 : 0000 1207 ....

2009-10-29-18.34.34.967677+060 E10637416A483 LEVEL: Severe
PID : 647378 TID : 1 PROC : db2bm.995458.1
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent, probe:1910
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-2428
DATA #2 : Hexdump, 4 bytes
0x000000011127E840 : FFFF F684 ....

2009-10-29-18.34.34.967828+060 E10637900A886 LEVEL: Severe
PID : 647378 TID : 1 PROC : db2bm.995458.1
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent, probe:1910
MESSAGE : SQL2428N The BACKUP did not complete because one or more of the
requested log files could not be retrieved.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2428 sqlerrml: 0
sqlerrmc:
sqlerrp : sqlubPro
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2009-10-29-18.34.34.968773+060 E10638787A473 LEVEL: Severe
PID : 647378 TID : 1 PROC : db2bm.995458.1
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubbuf, probe:338
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-2044
DATA #2 : Hexdump, 8 bytes
0x000000011127E840 : FFFF F804 0000 0002 ........

2009-10-29-18.34.34.968905+060 E10639261A872 LEVEL: Severe
PID : 647378 TID : 1 PROC : db2bm.995458.1
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubbuf, probe:338
MESSAGE : SQL2428N The BACKUP did not complete because one or more of the
requested log files could not be retrieved.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2428 sqlerrml: 0
sqlerrmc:
sqlerrp : sqlubPro
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2009-10-29-18.34.39.978211+060 I10640134A664 LEVEL: Error
PID : 1118270 TID : 1 PROC : db2med.995458.0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:939
DATA #1 : String, 110 bytes
Vendor error: rc = 17 returned from function sqluvend.
Return_code structure from vendor library nbdb2.sl64:

DATA #2 : Hexdump, 48 bytes
0x0FFFFFFFFFFFD858 : 0000 020C 4E65 7442 6163 6B75 7020 436F ....NetBackup Co
0x0FFFFFFFFFFFD868 : 6D6D 6974 2041 6374 696F 6E20 4661 696C mmit Action Fail
0x0FFFFFFFFFFFD878 : 6500 08BA 18A8 08BA 0000 0000 0000 0000 e...............

2009-10-29-18.34.39.978615+060 I10640799A313 LEVEL: Warning
PID : 1118270 TID : 1 PROC : db2med.995458.0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluMCTerminateBackup, probe:1322
MESSAGE : Media controller -- Problem closing vendor device

2009-10-29-18.34.39.983990+060 E10641113A708 LEVEL: Error
PID : 995458 TID : 1 PROC : db2agent (idle)
INSTANCE: db2inst1 NODE : 000 DB : ATMDB
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubCleanupPartialBackup, probe:578
MESSAGE : Error returned by sqluvdel
DATA #1 : unsigned integer, 4 bytes
26
DATA #2 : Hexdump, 48 bytes
0x0FFFFFFFFFFE4A68 : 0000 01F9 4E65 7442 6163 6B75 7020 4442 ....NetBackup DB
0x0FFFFFFFFFFE4A78 : 3220 496E 7075 7420 496E 7661 6C69 6400 2 Input Invalid.
0x0FFFFFFFFFFE4A88 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2009-10-29-18.34.39.990737+060 E10641822A374 LEVEL: Severe
PID : 995458 TID : 1 PROC : db2agent (idle)
INSTANCE: db2inst1 NODE : 000 DB : ATMDB
APPHDL : 0-692 APPID: *LOCAL.db2inst1.091029165722
AUTHID : DB2INST1
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:850
MESSAGE : Backup terminated.

Attach the db_cfg.

Backup command is:

db2 online backup db dbname online load / usr/openv/netbackup/bin/nbdb2.sl64 inlude logs
Help me please...
Attached Files
File Type: txt db_cfg.txt (6.8 KB, 475 views)
Oct 30 '09 #1
Share this Question
Share on Google+
2 Replies


P: 5
Hi,

I don't know a great deal about Veritas , but it might be a good idea to check if this particular log i.e. "S0004615.LOG" actually exists where Veritas is archiving it to.

Looking at the db cfg file, the first active log file in use is S0004617.LOG.

Hence it appears that either S0004615.LOG was not archived properly by veritas which would explain why the db2 online backup is failing because online backup is looking for this transaction log file during the backup process; or it was archived correctly by veritas but veritas is having issues retrieving it back due to other reasons.

Another thing you can try is increasing the value of the LOGPRIMARY db cfg parameter from 13 to a higher value. Depending on the volume of the workload handled by the database and how often the online backups are occurring it may improve the likely hood that all transaction logs that are to be backed up are in the active log directory and not archived off by veritas.

Also just as an aside I noticed LOCKTIMEOUT= -1 in the db cfg file which can cause applications to wait indefinitely to obtain a lock. You may want to set the LOCKTIMEOUT to any value other than -1 to avoid the possibility of global deadlocks from occurring for applications.

Good luck & hope this helps
Oct 31 '09 #2

P: 1
Check for a hostname mismatch between DB2 ($INSTHOME/sqllib/db2nodes.cfg) and NetBackup ($HOME/db2.conf).

See IBM Technote 1382709 located at http://www-01.ibm.com/support/docvie...id=swg21382709 for more details.
Feb 26 '10 #3

Post your reply

Sign in to post your reply or Sign up for a free account.