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 IC76055 Status: Closed

REQUEST TO CHANGE DB2DIAG.LOG MESSAGE FROM ERROR TO WARNING FOR SQL1496W
FROM SQEDBMGR::STARTUSINGLOCALDATABASE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
This APAR is in response to a request to change the following 
message from Error level to Warning or Info level and make the 
message a bit clearer. 
 
Example db2diag.log message 
 
2011-03-16-18.11.25.053617-240 I1582409A515       LEVEL: Error 
 
PID     : 2040054              TID  : 1801        PROC : db2sysc 
 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.110316221125 
AUTHID  : DB2INST1 
 
EDUID   : 1801                 EDUNAME: db2agent (SAMPLE) 
 
FUNCTION: DB2 UDB, base sys utilities, 
sqeDBMgr::StartUsingLocalDatabase, probe: 72 
 
DATA #2 : Hexdump, 4 bytes 
 
0x078000000072BD0C : 0000 05D8 
 
This is a positive return code for the SQL1496W warning when a 
deactivate is issued against a database that is not activated. 
 
$db2 deactivate db sample 
 
SQL1496W  Deactivate database is successful, but the database 
was not  activated.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any users doing a deactivate database against any already    * 
* deactivated database.                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This APAR is to change an Error level message to a Warning   * 
* level message and clarify the warning.                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 fixpack 5 or later                           * 
****************************************************************
Local Fix:
n/a
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in V9.7 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.04.2011
22.12.2011
22.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList