home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC65435 Status: Closed

WHEN QUERIES ARE FORCED NO MESSAGES ARE WRITTEN IN DB2DIAG.LOG ON SERVER

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When end user queries are forecd via load w/ force, force 
application cmd, qp or wlm force, no messages are written to 
db2diag.log in server. End user may get -1224 or -30081 errors. 
The -30081 errors are ofter confused with network problems. To 
clarify the situation messages are needed in the db2diag.log. 
When loads force queries, the db2diag.log messages needs to 
indicate what object was being loaded that caused the load to 
force the queries.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When end user queries are forced via load w/ force, force    * 
*                                                              * 
* application cmd, qp or wlm force, no messages are written to * 
*                                                              * 
* db2diag.log in server. End user may get -1224 or -30081      * 
* errors.                                                      * 
* The -30081 errors are ofter confused with network problems.  * 
* To                                                           * 
* clarify the situation messages are needed in the             * 
* db2diag.log.                                                 * 
* When loads force queries, the db2diag.log messages needs to  * 
*                                                              * 
* indicate what object was being loaded that caused the load   * 
* to                                                           * 
* force the queries.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 7                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.5 Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.01.2010
21.01.2011
21.01.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList