SQLUV_IO_ERROR 25 IO error encountered

Question : In the db2diag.log file – I’m getting the the error message Vendor RC=0x00000019=25 -- see DB2 API Guide for meaning. 2012-04-25-06.30.42.834149+060 I1209204241E814 LEVEL: Error PID : 13535 TID : 47410969569600PROC : db2sysc 0 INSTANCE: myInst NODE : 000 EDUID : 17727 EDUNAME: db2logmgr (myDB) 0 FUNCTION: DB2 UDB, data protection services, sqlpWriteToVendorDevice, probe:2700 MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR "A vendor device reported a media error." DATA #1 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes Vendor RC=0x00000019=25 -- see DB2 API Guide for meaning. DATA #2 : Hexdump, 48 bytes 0x00002B1ED2603150 : 9B00 0000 3133 3338 2031 3535 0000 0000 ....1338 155....... Read more →

Troubleshooting DB2 Return Codes, failed to archive log and SQLUV_INIT_FAILED

Question The following error log files appeared in the DB2 db2diag.log file. Along with failed to archive log errors . How do I find the DB2 return codes and TSM API return codes to pass onto the TSM system administrators for troubleshooting? 2012-04-23-15.56.48.740689+060 E1197154810E363 LEVEL: Error PID : 14425 TID : 47122517441600PROC : db2vend (db2logmgr.meth1 - 17727 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, database utilities, sqluvint, probe:402 DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes TSM RC=0xFFFFFFCE=-50 -- see TSM API Reference for meaning. 2012-04-23-15.56.48.741076+060 E1197155174E868 LEVEL: Error PID : 13535 TID : 47410969569600PROC : db2sysc 0 INSTANCE:... Read more →

Failed to archive log file and db2 online backup

Question: These errors started appearing in the db2diag.log files for a production DB2 database. I have a process to Manage DB2 db2diag.log files.The daily DB2 online backup was successful – but failed to archive log. 2012-04-20-11.15.52.720713+060 E1088884685E547 LEVEL: Error PID : 13535 TID : 47411049261376PROC : db2sysc 0 INSTANCE: db2misc NODE : 000 EDUID : 24 EDUNAME: db2logmgr (db1) 0 FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3160 MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR "A vendor device reported a media error." DATA #1 : Failed to archive log file S0005908.LOG to TSM chain 2 from /db2inst1/logs/db1/NODE0000/. Answer: 1) check the configuration on the... Read more →

DB2 LOGINDEXBUILD

According to the DB2 documentation, the LOGINDEXBUILD database configuration parameter “specifies whether index creation, recreation, or reorganization operations are to be logged so that indexes can be7 reconstructed during DB2 rollforward operations or high availability disaster recovery (HADR) log replay procedures” db2 get db cfg for mydb | grep 'LOGINDEXBUILD' Log pages during index build (LOGINDEXBUILD) = OFF| ON Notes 1) For HADR the recommendation is to have LOGINDEXBUILD turned on. This will create extra log files . Need to complete a capacity planning task. Capacity planning for log space required during an index build can be complicated – as... Read more →

SQL2563W The restore process has completed successfully

Question: I am getting the SQL2563W messages on a DB2 database restore SQL2563W The restore process has completed successfully, but one or moretable spaces from the backup were not restored. How do I resolve the SQL2563W messages? Answer: The SQL2563W message means the restore is completed , but at least one of the tablespaces is not restored. Consider: a) Check if tablespaces have been dropped since the last backup b) Check to see if tablespaces used by the tablespace containers in the backup exist in the target environment c) Check backup command and contents of a database Read more →