|
Problem IC97531
|
Status: Closed |
THE "DB2CLUSTER -CM -REPAIR -RESOURCES" COMMAND SHOULD FAIL IF THE INSTANCE IS STARTED |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When the db2 instance is started, if someone issues the
"db2cluster -cm -repair -resources" command, it is not blocked
but stops the instance and fails leaving resources in an
inconsistent state. A second attempt after the instance has been
brought down from the failed repair will be successful. The
expected behavior is for the command to be blocked if the
instance is started.
How to reproduce the problem:
db2start
db2cluster -cm -repair -resources |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 pureScale users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.11.2013
03.03.2014
03.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
