Symptom
You notice that Db2 is no longer writing log entries to the db2diag.log file.
The following file sharing violation messages are being reported repeatedly in the db2<sid>.nfy notification log:
2019-01-23-12.00.53.428953 Instance:db2mcp Node:000
PID:58614(db2stmm (SID) 0) TID:3779061504 Appid:*LOCAL.DB2.180811174835
RAS/PD component pdDmpErrMsg Probe:20 Database:SID
ADM14000E DB2 is unable to open diagnostic log file
"/db2/SID/db2dump/db2diag.log". Run the command "db2diag -rc "0x870f0016"" to find out more.
The operating system log (Linux in this case) reports the following:
2019-01-23T11:59:04.380045-05:00 n01d08ldbp778 DB2[58614]:Open of log file "/db2/SID/db2dump/db2diag.log" failed with rc 0x870F0016#012
Instance name: db2mcp#012Node number: 0#012Process ID: 58614#012Process name:db2sysc 0#012EDU ID: 23311#012EDU name: db2agent (SID) 0#012
Thread ID: 140201762481920#012Database name: SID#012Probe number: 11#012Product Name: DB2 UDB#012Component Name: common communication#012Function Name: sqlcctcptest
Read more...
Environment
DB2 (DB6) 10.5 Fixpacks 8 and 9 Unix platforms only.
Product
Keywords
timeout hang SIGHUP SQLO_SHAR sqlnlsMessage sqlnlscmsg signal , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.