DB2 - Problembeschreibung
Problem IC65702 | Status: Geschlossen |
DB2DIAG RETURN CODE IS 0 REGARDLESS OF MATCHES WERE FOUND OR NOT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Regardless of matches were found or not, db2diag always returns 0. For example: $ db2diag -l Critical $ echo $? 0 $ db2diag -l Error 2010-01-07-15.43.23.068247-300 E5614458E495 LEVEL: Error PID : 12345 TID : 183102335328 PROC : db2sysc INSTANCE: dbguest1 NODE : 000 EDUID : 1 EDUNAME: db2sysc FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr, probe:50 MESSAGE : ADM7006E The SVCENAME DBM configuration parameter was not configured. Update the SVCENAME configuration parameter using the service name defined in the TCP/IP services file. $ echo $? 0 The exit code should be 1 if no matches were found. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * db2diag users who use scripts to call db2diag and check * * thereturn code * **************************************************************** * PROBLEM DESCRIPTION: * * db2diag users who use scripts to call db2diag and check * * thereturn code were not seeing proper return codes from * * db2diag * **************************************************************** * RECOMMENDATION: * * Available db2_v97fp2 onwards * **************************************************************** | |
Local-Fix: | |
N/A | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
Code was fixed to solve this problem | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 20.01.2010 19.05.2010 19.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
9.7.0.2 |