|
Problem IC88051
|
Status: Closed |
WHEN DATABASE IS ACTIVATED AND LIST APPLICATIONS COMMAND IS ISSUED, SQLCODE IS NOT SET CORRECTLY. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack8 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
First fixed in DB2 Version 9.7 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC91305
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.11.2012
29.04.2013
29.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
