IBM Support

ObjectStore creation can intermittently fail when using DB2 for LUW 9.7 Fix Pack 2 or Fix Pack 3

Troubleshooting


Problem

The DB2 for LUW server, when running 9.7 Fix Pack 2 or Fix Pack 3, crashes intermittently during ObjectStore creation operations. This technote describes the problem and presents two workarounds to be used until DB2 for LUW 9.7 Fix Pack 4 can be installed.

Symptom

The ObjectStore creation fails due to the crash of the DB2 for LUW server. Once the ObjectStore has been created, there have been no observed cases of this issue with DB2 9.7 Fix Pack 2 or Fix Pack 3.

Cause

The DB2 for LUW team has linked this issue to "extended indicator" functionality that was added to version 9.7 Fix Pack 2.

Diagnosing The Problem

Looking in the DB2 server logs, one will find information similar to the following messages:

2010-07-30-16.42.38.942372-360 I565007E577 LEVEL: Severe
PID : 5674 TID : 47968656812352PROC : db2sysc 0
INSTANCE: xxinst NODE : 000 DB : xxdb
APPHDL : 0-324 APPID: 10.62.32.67.39255.100730224159
AUTHID : xxuser
EDUID : 307 EDUNAME: db2agent (FNEDE1) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250
RETCODE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR
"Severe programming error"
DIA8516C A severe internal processing error has occurred.

010-07-26-13.45.42.917807-420 E79194A1253 LEVEL: Critical
PID : 4300968 TID : 106920 PROC : db2sysc 0
INSTANCE: xxinst NODE : 000 DB : xxdb
APPHDL : 0-212 APPID: 9.39.44.204.61151.100726204602
AUTHID : xxuser
EDUID : 106920 EDUNAME: db2agent (ATOSICA) 0
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:90
MESSAGE : ADM14011C A critical failure has caused the following type of error:
"Trap". The DB2 database manager cannot recover from the failure.
First Occurrence Data Capture (FODC) was invoked in the following
mode: "Automatic". FODC diagnostic information is located in the
following directory:
"/home/xxinst/sqllib/db2dump/FODC_Trap_2010-07-26-13.45.27.385820/"

Resolving The Problem

APAR IC71365 has been resolved in DB2 for LUW Fix Pack 4. Until that fix pack is installed, there are currently two workarounds to this issue.

1. Temporarily grant the database user specified on the ObjectStore data sources DBADM privileges. Once the ObjectStore creation has succeeded, optionally revoke that privilege from the user.

2. Downgrade your DB2 for LUW server to 9.7 Fix Pack 1.

[{"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Content Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.5.1;5.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21446494

Page Feedback