SAP Note 1173256 - DB6: 9.1 FP4SAP database might crash due to a bad pointer

Component : Database Interface/DBMS for DB2 Universal Database -

Solution : https://service.sap.com/sap/support/notes/1173256 (SAP Service marketplace login required)

Key words :
stack #1             signal #110        sqlra_get_var1        sqlrr_process_open_request2        sqlrr_open3        sqljs_ddm_opnqry4        sqljsparserdbaccessed5        sqljsparse6        sqljssqlam7        sqljsdriverequests8        sqljsdrdaasdriver9        sqlerunagent10       sqlocreateedu11       sqlospawnedu12       sqlecreatenewagent13       sqlegetagentfrompool14       sqlegetagent15       sqleinitsysctlr16       sqlesysctlr17, similar stack trace, unknown18       main19       _startthe error, log message connected, withdrawn fixpak fp4sap, db2 code release, sql cache size, bad pointer db2, signal #11, bad pointer

Related Notes :

977845DB6: Known Errors and available Fixes in DB2 9.1 LUW
101809DB6: Supported Fix Packs IBM DB2 for Linux,UNIX and Windows