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

WHEN DATABASE IS ACTIVATED AND LIST APPLICATIONS COMMAND IS ISSUED, SQLCODE
IS NOT SET CORRECTLY.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When a database is activated but there are no active 
applications, the list applications command shows SQL1611W but 
sqlcode is set to 0, not 1611. 
 
Reproduce Steps : 
$ db2start 
$ db2 list active databases 
SQL1611W  No data was returned by Database System Monitor. 
$ db2 -ec list active databases 
SQL1611W  No data was returned by Database System Monitor. 
1611 
$ db2 -ec list applications 
SQL1611W  No data was returned by Database System Monitor. 
1611                                                <<< returned 
1611 correctly 
$ db2 activate db sample 
DB20000I  The ACTIVATE DATABASE command completed successfully. 
$ db2 -ec list active databases 
 
                           Active Databases 
 
Database name                      = SAMPLE 
Applications connected currently   = 0 
Database path                      = 
/home/db2inst1/NODE0000/SQL00001/ 
 
0 
$ db2 -ec list applications 
SQL1611W  No data was returned by Database System Monitor. 
0                                                  <<< returned 
0 even the message shows SQL1611W
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 connect                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v97fp8                                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
v97fp8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2013
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList