24 April,2012 by Tom Collins
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: db2inst1 NODE : 000 EDUID : 17727 EDUNAME: db2logmgr (mydb) 0 FUNCTION: DB2 UDB, data protection services, sqlpInitVendorDevice, probe:1030 MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR "A vendor device reported a media error." DATA #1 : String, 29 bytes Init failed! Vendor rc info: DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes Vendor RC=0x0000000B=11 -- see DB2 API Guide for meaning. DATA #3 : Hexdump, 48 bytes 0x00002B1ED2603150 : CEFF FFFF 3430 3220 2D35 3000 0000 0000 ....402 -50..... 0x00002B1ED2603160 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00002B1ED2603170 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
The definitions for all DB2 to Vendor API return codes are found under the instance home directory <sqllib>/include/ in the sqluvend.h header file.
The DB2 error code returns : #define SQLUV_INIT_FAILED 11 /* Initialization failed */
The Vendor Code is returned using the return code
#define SQLUV_COMMENT_LEN 30 typedef struct Return_code { sqlint32 return_code; /* return code from the vendor function */ char description[SQLUV_COMMENT_LEN]; /* descriptive message */ void *reserve; /* reserve for future use */ } Return_code; 0x00002B1ED2603150 : CEFF FFFF 3430 3220 2D35 3000 0000 0000 ....402 -50..... 0x00002B1ED2603160 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00002B1ED2603170 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
Checking Version 6.2.0 API return codes
An attempt to connect to the server using TCP/IP communications failed. This can be a result of incorrect TCP/IP option settings in your client options file. This error can also occur if the LAN connection went down or if your system administrator canceled a backup operation.
Session rejected. Processing stopped.
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |