DB2 - Problembeschreibung
Problem IC70988 | Status: Geschlossen |
DB2ICRT SHOWS A CORE DUMP IF THE HOST NAME DOESN'T RESOLVE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
If your host name doesn't properly resolve to an IP address, db2icrt will do a core dump. e.g. host name not defined in /etc/hosts: The contents of your /etc/hosts doesn't contain machineA: # cat /etc/hosts | grep machineA # hostname machineA machineA:/opt/ibm/db2/V9.5/instance # ./db2icrt -u db2inst1 db2inst1 The host name "machineA" is invalid. Specify a valid host name. 2010-09-08-09.47.16.697682-240 I1E1538 LEVEL: Event PID : 6189 TID : 46967641952016PROC : db2bp INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120 START : New Diagnostic Log file DATA #1 : Build Level, 152 bytes Instance "db2inst1" uses "64" bits and DB2 code release "SQL09057" with level identifier "06080107". Informational tokens are "DB2 v9.5.0.7", "s100830", "IP23143", Fix Pack "7". DATA #2 : System Info, 440 bytes System: Linux sles10inst 6 2 x86_64 CPU: total:2 online:2 Cores per socket:2 Threading degree per core:1 Physical Memory(MB): total:3958 free:83 Virtual Memory(MB): total:6014 free:2139 Swap Memory(MB): total:2056 free:2056 Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:4096 msgNumberOfHeaders:65536 msgMaxQueueSize:65536 msgMaxSegmentSize:16 shmMax:4149784576 shmMin:1 shmIDs:4096 shmSegments:4096 semMap:256000 semIDs:1024 semNum:256000 semUndo:256000 semNumPerID:1250 semOps:100 semUndoSize:20 semMaxVal:32767 semAdjustOnExit:32767 Cur cpu time limit (seconds) = 0xFFFFFFFF Cur file size limit (bytes) = 0xFFFFFFFF Cur data size (bytes) = 0xFFFFFFFF Cur stack size (bytes) = 0x00800000 Cur core size (bytes) = 0x00000000 Cur memory size (bytes) = 0xFFFFFFFF nofiles (descriptors) = 0x00000400 Information in this record is only valid at the time when this file was created (see this record's time stamp) 2010-09-08-09.47.16.697396-240 I1540E706 LEVEL: Severe PID : 6189 TID : 46967641952016PROC : db2bp INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32 MESSAGE : ZRC=0xFFFFE871=-6031 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4 sqlerrmc: 0 11 sqlerrp : SQLFRCFG sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2010-09-08-09.47.16.699502-240 I2247E330 LEVEL: Severe PID : 6189 TID : 46967641952016PROC : db2bp INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, command line process, clp_bp_main, probe:2 DATA #1 : Hexdump, 4 bytes 0x00007FFF2DC8BD68 : 71E8 FFFF q... 2010-09-08-09.48.16.890557-240 I2578E386 LEVEL: Error PID : 6187 TID : 47723022940928PROC : db2 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, command line process, clp_start_bp, probe:3 MESSAGE : CLP frontend unable to get REQUEST queue handle DATA #1 : Hexdump, 4 bytes 0x00007FFF4D247C98 : 4200 0F87 B... DBI1703E No valid service name or port number found. Explanation: No valid service name or port number for this instance can be found in the TCP/IP services file. This information is either missing or is invalid. If you installed "DB2 Extended Server Edition" product, a service name must be specified for the instance before using this command. User response: Specify valid service name and port number for this instance and enter this command again. DBI1079I Output is saved in the log file /tmp/db2icrt.log.5036. Explanation: All processed and failed operations have been saved into this log file. User response: Do not modify this file in any way. This file is for IBM Technical Support reference. After applying the fix, the core dump will not be shown and just the error message will be shown. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * If your host name doesn't properly resolve to an IP * * * * address, db2icrt will do a core dump. * * * * * * * * e.g. host name not defined in /etc/hosts: * * * * The contents of your /etc/hosts doesn't contain machineA: * * * * # cat /etc/hosts | grep machineA * * * * # hostname * * * * machineA * * * * * * * * machineA:/opt/ibm/db2/V9.5/instance # ./db2icrt -u db2inst1 * * * * db2inst1 * * * * The host name "machineA" is invalid. Specify a valid host * * name. * * * * * * 2010-09-08-09.47.16.697682-240 I1E1538 LEVEL: * * Event * * PID : 6189 TID : 46967641952016PROC : * * db2bp * * INSTANCE: db2inst1 NODE : 000 * * * * FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, * * probe:120 * * START : New Diagnostic Log file * * * * DATA #1 : Build Level, 152 bytes * * * * Instance "db2inst1" uses "64" bits and DB2 code release * * * * "SQL09057" * * * * with level identifier "06080107". * * * * Informational tokens are "DB2 v9.5.0.7", "s100830", * * "IP23143", * * Fix Pack "7". * * * * DATA #2 : System Info, 440 bytes * * * * System: Linux sles10inst 6 2 x86_64 * * * * CPU: total:2 online:2 Cores per socket:2 Threading degree * * per * * core:1 * * * * Physical Memory(MB): total:3958 free:83 * * * * Virtual Memory(MB): total:6014 free:2139 * * * * Swap Memory(MB): total:2056 free:2056 * * * * Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 * * * * msgMaxQueueIDs:4096 * * * * msgNumberOfHeaders:65536 * * msgMaxQueueSize:65536 * * msgMaxSegmentSize:16 shmMax:4149784576 * * shmMin:1 * * shmIDs:4096 * * * * shmSegments:4096 semMap:256000 semIDs:1024 * * * * semNum:256000 * * * * semUndo:256000 semNumPerID:1250 semOps:100 * * * * semUndoSize:20 * * * * semMaxVal:32767 semAdjustOnExit:32767 * * * * Cur cpu time limit (seconds) = 0xFFFFFFFF * * * * Cur file size limit (bytes) = 0xFFFFFFFF * * * * Cur data size (bytes) = 0xFFFFFFFF * * * * Cur stack size (bytes) = 0x00800000 * * * * Cur core size (bytes) = 0x00000000 * * * * Cur memory size (bytes) = 0xFFFFFFFF * * * * nofiles (descriptors) = 0x00000400 * * * * * * * * Information in this record is only valid at the time when * * this * * file was * * * * created (see this record's time stamp) * * * * * * * * 2010-09-08-09.47.16.697396-240 I1540E706 LEVEL: * * Severe * * PID : 6189 TID : 46967641952016PROC : * * db2bp * * INSTANCE: db2inst1 NODE : 000 * * * * FUNCTION: DB2 UDB, base sys utilities, * * * * sqleInitApplicationEnvironment, probe:32 * * * * MESSAGE : ZRC=0xFFFFE871=-6031 * * * * DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes * * * * sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6031 sqlerrml: 4 * * sqlerrmc: 0 11 * * * * sqlerrp : SQLFRCFG * * * * sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) * * * * 0x00000000 * * * * (4) 0x00000000 (5) 0x00000000 (6) * * * * 0x00000000 * * * * sqlwarn : (1) (2) (3) (4) (5) (6) * * * * (7) (8) (9) (10) (11) * * * * sqlstate: * * * * * * * * 2010-09-08-09.47.16.699502-240 I2247E330 LEVEL: * * Severe * * PID : 6189 TID : 46967641952016PROC : * * db2bp * * INSTANCE: db2inst1 NODE : 000 * * * * FUNCTION: DB2 UDB, command line process, clp_bp_main, * * probe:2 * * DATA #1 : Hexdump, 4 bytes * * * * 0x00007FFF2DC8BD68 : 71E8 FFFF * * * * q... * * * * * * * * 2010-09-08-09.48.16.890557-240 I2578E386 LEVEL: * * Error * * PID : 6187 TID : 47723022940928PROC : db2 * * * * INSTANCE: db2inst1 NODE : 000 * * * * FUNCTION: DB2 UDB, command line process, clp_start_bp, * * probe:3 * * MESSAGE : CLP frontend unable to get REQUEST queue handle * * * * DATA #1 : Hexdump, 4 bytes * * * * 0x00007FFF4D247C98 : 4200 0F87 * * * * B... * * * * DBI1703E No valid service name or port number found. * * * * * * * * Explanation: * * * * * * * * No valid service name or port number for this instance can * * be * * found in * * * * the TCP/IP services file. This information is either missing * * or * * is * * * * invalid. * * * * * * * * If you installed "DB2 Extended Server Edition" product, a * * * * service name * * * * must be specified for the instance before using this * * command. * * * * * * User response: * * * * * * * * Specify valid service name and port number for this instance * * and * * enter * * * * this command again. * * * * * * * * * * * * DBI1079I Output is saved in the log file * * /tmp/db2icrt.log.5036. * * * * * * Explanation: * * * * * * * * All processed and failed operations have been saved into * * this * * log file. * * * * * * * * User response: * * * * * * * * Do not modify this file in any way. This file is for IBM * * * * Technical * * * * Support reference. * **************************************************************** * RECOMMENDATION: * * Upgrade to IBM DB2 V9.5 Fix Pack 7 * **************************************************************** | |
Local-Fix: | |
Ensure your host name maps to the correct IP address in /etc/hosts If you are using DNS ensure the hostname is resolved to a correct IP address. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Lösung | |
Upgrade to IBM DB2 V9.5 Fix Pack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.09.2010 12.10.2010 12.10.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP7 | |
Problem behoben lt. FixList in der Version | |
9.1.0.7 | |
9.5.0.7 |