IBM Support

Connection fails due to SQLP_BADLOG errors

Troubleshooting


Problem

Database connections either remote or local may fail if a bad log is encountered. This can happen during a database restart or an HADR replication for example.

Symptom

Possible messages that can appear in db2diag.log:

      2015-04-07-04.10.50.693000+120 I1825037F2003        LEVEL: Severe
      PID     : 7964                 TID : 6552           PROC : db2syscs.exe
      INSTANCE: DB2                  NODE : 000           DB   : XXXXXXX
      APPHDL  : 0-1170               APPID: *LOCAL.DB2.150406213008
      AUTHID  : XXXXXXX              HOSTNAME: XXXXXXX
      EDUID   : 6552                 EDUNAME: db2agent (XXXXXXX) 0
      FUNCTION: DB2 UDB, data protection services, SQLP_DBCB::setLogState,
      probe:5000
      MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be
      used"
               DIA8414C Logging can not continue due to an error.
         
      2015-04-07-04.10.50.912000+120 E1827042F1032        LEVEL: Critical
      PID     : 7964                 TID : 6552           PROC : db2syscs.exe
      INSTANCE: DB2                  NODE : 000           DB   : XXXXXXX
      APPHDL  : 0-1170               APPID: *LOCAL.DB2.150406213008
      AUTHID  : XXXXXXX              HOSTNAME: XXXXXXX
      EDUID   : 6552                 EDUNAME: db2agent (XXXXXXX) 0
      FUNCTION: DB2 UDB, base sys utilities, sqleDoForceDBShutdownFODC,
      probe:10
      MESSAGE : ADM14001C  An unexpected and critical error has occurred:
               "ForceDBShutdown". The instance may have been shutdown as a
      result.  "Automatic" FODC (First Occurrence Data Capture) has been
      invoked and diagnostic information has been recorded in directory
      "C:\ProgramData\IBM\DB2\DB2COPY1\DB2\FODC_ForceDBShutdown_2015-04-07-
      04.10.50.912000_0000\". Please look in this directory for detailed
      evidence about what happened and contact IBM support if necessary to
      diagnose the problem.

      2015-04-07-04.10.50.974000+120 I1829244F595         LEVEL: Severe
      PID     : 7964                 TID : 2896           PROC : db2syscs.exe
      INSTANCE: DB2                  NODE : 000           DB   : XXXXXXX
      APPHDL  : 0-1172               APPID: *LOCAL.DB2.150406213009
      AUTHID  : XXXXXXX              HOSTNAME: XXXXXXX
      EDUID   : 2896                 EDUNAME: db2agent (XXXXXXX) 0
      FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_pre1, probe:650
      MESSAGE : Marking DBBAD since DB not active
      DATA #1 : Hexdump, 1 bytes
      0x0000000009E4A77A : 02

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Recovery - Logging","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.1;10.5;8.2;9.1;9.5;9.7;9.8","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
30 April 2025

UID

swg21701602

Page Feedback