Results 1 to 3 of 3
  1. #1
    Join Date
    Jun 2009
    Location
    Arlington Heights, IL
    Posts
    1

    Unanswered: ADM14000E DB2 is unable to open diagnostic log file 0x870f0016

    We had a production system go down as a result of this error...

    ADM14000E DB2 is unable to open diagnostic log file
    "~/sqllib/db2dump/db2diag.log". Run the command "db2diag -rc
    "0x870f0016"" to find out more.


    Symptoms started with users complaining about being unable to access the database. When we logged in to investigate, DB2 commands like "list applications show detail" hung. They just didn't complete, while operation system commands (AIX 7.1) completed without issue. We saw no issues with system resource utilization.

    We were able to resolve this issue by copying the original diagnostic log to another directory and touching a new one. As soon as we did that, all problems ceased immediately.

    However, business wants to understand root cause. So, in searching for that, our db2fodc -hang command for IBM ran, ah, kind of, generated output directories, but output directories with no actual output files within them. So IBM responded with "Ah well, we can't really help you without the fodc output."

    I've researched this error a little bit online, including this website, but these errors were typically for transaction logs being inaccessible. Output for those errors were found in the diagnostic log itself. However, as our diagnostic log happened to be the inaccessible file, we had no information populated within. The output you see below was from our instance.nfy file.

    I'm not seeking conjecture on what we should have done differently, we simply want to reach out to others to explain what worked for us and are curious to understand potential causes for this issue so we can prevent this from reoccurring in the future.

    It would be nice to know if anyone else got better traction on the potential for root cause with IBM Support.

    Output below. Thanks!

    --------------------------------------------------
    Database and O/S details
    ---------------------------------------------------
    DB: DB2 v9.7 FixPack 4 LUW
    O/S: AIX 7.1
    Processor Type: PowerPC_POWER7
    Processor Implementation Mode: POWER 6
    Processor Version: PV_6_Compat
    Number Of Processors: 9
    Processor Clock Speed: 4004 MHz
    CPU Type: 64-bit
    Kernel Type: 64-bit
    Memory Size: 49152 MB
    Good Memory Size: 49152 MB
    -------------------------------------------------
    Instance.nfy output (reoccured dozens of times)
    -------------------------------------------------

    2014-07-23-10.55.35.977814 Instance:bigappi1 Node:000
    PID:40763636(db2logmgr (BIGAPPD1) 0) TID:3343 Appid:none
    RAS/PD component pdLogInternal Probe:20

    2014-07-23-11.12.47.381569 Instance:bigappi1 Node:000
    PID:40763636(db2agent (BIGAPPD1) 0) TID:1003129 Appid:XXX.XXX.XXX.XXX.xxxxx.xxxxxxxx
    RAS/PD component pdLogInternal Probe:20 Database:BIGAPPD1

    ADM14000E DB2 is unable to open diagnostic log file
    "~/sqllib/db2dump/db2diag.log". Run the command "db2diag -rc
    "0x870f0016"" to find out more.

    ------------------------------------
    and from the comand line thereafter....
    -------------------------------------

    ~/sqllib/db2dump >db2diag -rc 0x870f0016

    Input ZRC string '0x870f0016' parsed as 0x870F0016 (-2029060074).

    ZRC value to map: 0x870F0016 (-2029060074)
    V7 Equivalent ZRC value: 0xFFFFF616 (-2538)

    ZRC class :
    Global Processing Error (Class Index: 7)
    Component:
    SQLO ; oper system services (Component Index: 15)
    Reason Code:
    22 (0x0016)

    Identifer:
    SQLO_SHAR
    Identifer (without component):
    SQLZ_RC_SHAR

    Description:
    File sharing violation.

    Associated information:
    Sqlcode -902
    SQL0902C A system error (reason code = "") occurred. Subsequent SQL
    statements cannot be processed.

    Number of sqlca tokens : 1
    Diaglog message number: 8519

  2. #2
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Your sysadmin should be able to discover the identity of the other process that is opening db2diag.log with an unsuitable filemode that's causing the sharing violation.

  3. #3
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by db2mor View Post
    Your sysadmin should be able to discover the identity of the other process that is opening db2diag.log with an unsuitable filemode that's causing the sharing violation.
    It was probably the sysadmin, so probably covered their tracks by now.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •