|
Problem IC63934
|
Status: Closed |
LEVEL OF DB2DIAG.LOG ENTRIES FOR SUCCESSFUL COMPLETION OF QUIESCE AND UNQUIESCE IS REPORTED AS AN ERROR. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
LEVEL of following db2diag.log entries is ERROR.
2009-01-08-02.03.01.360121+540 E171520A396 LEVEL: Error
PID : 360630 TID : 1 PROC : db2agent
(WPSZDB) 0
INSTANCE: db2inst1 NODE : 000 DB : WPSZDB
APPHDL : 0-274 APPID:
*LOCAL.db2inst1.090107170251
FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce,
probe:1
MESSAGE : ADM7506W Database quiesce has been requested.
.
2009-01-08-02.03.01.385147+540 E171917A412 LEVEL: Error
PID : 360630 TID : 1 PROC : db2agent
(WPSZDB) 0
INSTANCE: db2inst1 NODE : 000 DB : WPSZDB
APPHDL : 0-274 APPID:
*LOCAL.db2inst1.090107170251
FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseQuiesce,
probe:2
MESSAGE : ADM7507W Database quiesce request has completed
successfully
2009-01-08-02.06.23.344099+540 E174777A401 LEVEL: Error
PID : 1097910 TID : 1 PROC : db2agent
(WPSZDB) 0
INSTANCE: db2inst1 NODE : 000 DB : WPSZDB
APPHDL : 0-277 APPID:
*LOCAL.db2inst1.090107170622
FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseUnquiesce,
probe:1
MESSAGE : ADM7510W Database unquiesce has been requested.
.
2009-01-08-02.06.23.345646+540 E175179A416 LEVEL: Error
PID : 1097910 TID : 1 PROC : db2agent
(WPSZDB) 0
INSTANCE: db2inst1 NODE : 000 DB : WPSZDB
APPHDL : 0-277 APPID:
*LOCAL.db2inst1.090107170622
FUNCTION: DB2 UDB, base sys utilities, sqleDatabaseUnquiesce,
probe:2
MESSAGE : ADM7509W Database unquiesce request has completed
successfully.
It would be either WARNING / INFO . In case of successful
completion, db2 should not report LEVEL as an ERROR in
db2diag.log. |
| Problem Summary: |
Users Affected: All user prior to DB2 Version 97 Fix Pack 1.
Problem Description: LEVEL OF DB2DIAG.LOG ENTRIES FOR SUCCESSFUL
COMPLETION OF QUIESCE AND UNQUIESCE IS REPORTED AS AN ERROR. |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 97 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
02.03.2010
02.03.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
