Basis Errors and Solutions

Symptom

DB2 9.1 FP4SAP “V9.1.0.4″, “special_19276″.
DB2 might crash with Signal #11 (SIGSEGV) due to a bad pointer.
Other terms

DB2, DB6, UDB, Fixpak, crash, Signal #11 (SIGSEGV)
Reason and Prerequisites

db2level:
DB21085I Instance “db2rdp” uses “64″ bits and DB2 code release “SQL09014″ with level identifier “01050107″.
Informational tokens are “DB2 v9.1.0.4″, “special_19276″, “U811793_19276″, and Fix Pack “4″.
Due to a bad pointer DB2 might encounter different problems depending on the operating system and could even crash with signal 11. Usually the error occurs during compilation of a SQL statement.
IBM cannot predict if a certain system is vulnerable to this defect, because it depends on various variables e.g. type of workload, SQL cache size, memory usage and operating system.
If a crash occurs the following or a similar stack trace will indicate that the crash was caused by this defect:
Stack #1 Signal #11
0 sqlra_get_var
1 sqlrr_process_open_request
2 sqlrr_open
3 sqljs_ddm_opnqry
4 sqljsParseRdbAccessed
5 sqljsParse
6 sqljsSqlam
7 sqljsDriveRequests
8 sqljsDrdaAsDriver
9 sqleRunAgent
10 sqloCreateEDU
11 sqloSpawnEDU
12 sqleCreateNewAgent
13 sqleGetAgentFromPool
14 sqleGetAgent
15 sqleInitSysCtlr
16 sqleSysCtlr
17 ?unknown
18 main
19 _start
The error will always occur in function sqlra_get_var. There is no significant db2diag.log message connected to the crash.
The defect was introduced with APAR IZ05531, which is one of the additional APAR’s in FP4SAP.
Due to the uncertainty if a system is vulnerable to encounter this defect, SAP recommends that you implement one of the solutions described below.

Solution

There are several possibilities to solve this problem:

The defect is also fixed DB2 9.1 FP5 which will be certified by SAP in June 2008.

It is also possible to downgrade the system and use DB2 9.1 FP3SAP.

SAP has withdrawn Fixpak FP4SAP from SAP Marketplace.