|
Problem IC70805
|
Status: Closed |
WHEN DATABASE IS ACTIVATED AND LIST APPLICATIONS COMMAND IS ISSUED, CLP RETURN CODE 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
CLP return code is not set to 2.
For example:
db2 activate db <dbname>
db2 list applications; echo "return code=$?";
SQL1611W No data was returned by Database System Monitor.
return code=0 ==> This should be 2 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* When a database is activated but there are no active *
* applications, the list applications command shows SQL1611W *
* but CLP return code is not set to 2. *
* *
* For example: *
* $ db2 activate db <dbname> *
* $ db2 list applications; echo "return code=$?"; *
* SQL1611W No data was returned by Database System Monitor. *
* return code=0 ==> This should be 2 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 FixPack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 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 |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.08.2010
19.05.2011
19.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
