DB2 - Problem description
Problem IC85492 | Status: Closed |
DB2 CLP TRAPPED IN CLP_FP_EXIT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
DB2 CLP process trapped with the following stack: sqloCleanupEnvironment(0xffffffffffffffff) at 0x900000016c22d8c sqloFreeOSSInternalMemory() at 0x900000016c232dc sqloAppLibTerm() at 0x900000016c237b8 mod_fini1(??, ??) at 0x9fffffff00020ac usl_fini_mods(??, ??, ??, ??) at 0x9fffffff0002c70 usl_exit_fini_mods(??) at 0x9fffffff0002b64 __modfini64() at 0x9000000000461bc exit(??) at 0x90000000006dc0c sqloexit(??, ??) at 0x900000016bb4fd4 clp_fp_exit.fdpr.chunk.4__Fi(0x0) at 0x900000016bb4f44 clp_api(0x8fffffff00017b8, 0x0, 0x800200140000000, 0x0, 0xffffffffffffffff, 0x0, 0x0) at 0x900000016bb4ce8 main(??, ??) at 0x100000904 Since this CLP trapping signal is ignored, one of symptoms is that the file descriptor of db2diag.log is not released after trapping, that can prevent the other thread writing into the db2diag.log | |
Problem Summary: | |
SUMMARY: Users Effected: This problem effects all users. Problem Description: DB2 TRAPPED IN CLP_FP_EXIT. Problem Summary: DB2 TRAPPED IN CLP_FP_EXIT. | |
Local Fix: | |
Rename db2dida.log (use OS command or db2diag -A), so the new db2diag records can be written to the newly renamed db2diag.log file. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
Upgrade to DB2 Version Version 9.7, FixPak 7. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC89630 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.07.2012 17.01.2013 24.01.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |