How to fix DIA8052C the Event Monitor has reached its file capacity

Question: This DB2 error message appears in the DB2Diag.LOG file

 ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor full of data"

          DIA8052C The Event Monitor "" has reached its file capacity. Delete

          the files in the target directory "" or move them to another

          directory.

 

How can I fix it?

Answer:   There’s probably a limit on the event monitor size. To check the current size – connect to the database and issue the statement:

 

SELECT  * FROM SYSCAT.EVENTMONITORS

Find the event monitor name under the EVMONNAME  column.

DROP EVENT MONITOR <monitor_name>

SQL1427N An instance attachment does not exist

Question : When I run the  command,  db2 get dbm cfg show detail  ,I get the following error:

SQL1427N  An instance attachment does not exist

How can I  avoid this error message and view details ?

Answer :   If  you’re another node you may need to attach first.

db2 attach to myinstanceNodedb2 get dbm cfg show detail  db2 detach 

ADM1847W Failed to retrieve log file

Question: The db2diag.log reported the error message . The message appeared during an ONLINE BACKUP:

ADM1847W  Failed to retrieve log file "S0003896.LOG" on chain "0" from "/myinst/logs/TADDM/NODE0000/".

 

Why is the DB2 db2diag.log reporting this warning?

Answer:  If an archived log has been renamed , removed or not available in the active log path, the warning is reported.

Different reason can cause this problem.  Essentially forcing two things to occur at once

Some examples:

a)       DB2 PRUNE HISTORY  after the backup has started

b)       Network speed.

 

SQL0911N Reason Code 68 The current transaction has been rolled back because of a deadlock or timeout

Question : I am seeing this SQL0911N Reason Code 68 message in my DB2 diaglog file:

command : db2 backup db MYDB online use TSM include logs
SQL0911N  The current transaction has been rolled back because of a deadlock
or timeout.  Reason code "68".  SQLSTATE=40001

 

How do I fix this SQL0911N error?

 

Answer: The DB2  command line error utility  shows this detail for  the SQL0911N Reason Code 68 error., indicating that the SQL0911N error is caused by a deadlock or locktimeout.

A DB2  ONLINE backup attempts to obtain a IN lock on tables in SMS table spaces. DB2 tries to upgrade BLOB fileds to an S LOCK during an ONLINE backup.

 If an application is holding a lock incompatible with the ONLINE backup lock attempt, The ONLINE BACKUP waits for the period of the LOCKTIMEOUT ,  where the ONLINE backup fails.

Possible solutions

1)       Analyse scheduled backup times and move to a quieter time frame

2)       Change table space to DMS from SMS. DMS doesn’t require the SHARE lock for BLOBs

3)       Force the application off.

4)       Increase LOCKTIMEOUT

Read More

How to monitor a deadlock in DB2 - DBA DB2

DB2 - Drop the DB2DETAILDEADLOCK event monitor

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: 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    ................

 

Answer:

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

-050 E: DSM_RC_TCPIP_FAILURE Session rejected: TCP/IP connection failure

Explanation

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.

System action

Session rejected. Processing stopped.