|
Problem IC75477
|
Status: Closed |
db2stop -force fails to shutdown DB2 pureScale instance |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
The following scenario results in a failure to shutdown the DB2
pureScale instance:
Four members , two CFs
Assume member 3 is used to generate this issue.
On member 3, issue command
db2stop member 3
On the system that is hosting member 3 , shutdown the operating
system.
Then issue the command:
db2stop force
The db2stop force command will fail with the following
information:
2011-02-28 14:35:13 3 0 SQL1690N An error occurred
during DB2STOP processing of a DB2 member or CF with identifier
"3" on host "host3d". Reason code "1".
2011-02-28 14:35:47 3 0 SQL1690N An error occurred
during DB2STOP processing of a DB2 member or CF with identifier
"3" on host "host3d". Reason code "1".
2011-02-28 14:36:20 3 0 SQL1690N An error occurred
during DB2STOP processing of a DB2 member or CF with identifier
"3" on host "host3d". Reason code "1".
2011-02-28 14:36:20 0 0 SQL1064N DB2STOP processing was
successful.
2011-02-28 14:36:20 1 0 SQL1064N DB2STOP processing was
successful.
2011-02-28 14:36:20 2 0 SQL1064N DB2STOP processing was
successful.
SQL6033W Stop command processing was attempted on "4" node(s).
"3" node(s) were successfully stopped. "0" node(s) were already
stopped. "1" node(s) could not be stopped.
2011/02/28 14:36:20
Return Code of db2stop force : 6
db2instance -list command shows the following:
ID TYPE STATE
HOME_HOST CURRENT_HOST ALERT
PARTITION_NUMBER LOGICAL_PORT NETNAME
-- ---- -----
--------- ------------ -----
---------------- ------------ -------
0 MEMBER STOPPED host3a
host3a YES
0 0 host3a-ib
1 MEMBER STOPPED host3b
host3b YES
0 0 host3b-ib
2 MEMBER STOPPED host3c
host3c YES
0 0 host3c-ib
3 MEMBER STOPPED host3d
host3d YES
0 0 host3d-ib
128 CF PRIMARY host3p
host3p NO
- 0 host3p-ib
129 CF CATCHUP host3s
host3s NO
- 0 host3s-ib
HOSTNAME STATE INSTANCE_STOPPED
ALERT
-------- ----- ----------------
-----
host3s ACTIVE NO
NO
host3p ACTIVE NO
NO
host3d INACTIVE NO
YES
host3c ACTIVE NO
NO
host3b ACTIVE NO
NO
host3a ACTIVE NO
NO
There is currently an alert for a member, CF, or host in the
data-sharing instance. For more information on the alert, its
impact, and how to clear it, run the following command:
'db2cluster -cm -list -alert'.
Applying this APAR fix will result in a proper shutdown of the
DB2 pureScale instance. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* The following scenario results in a failure to shutdown the *
* DB2 *
* pureScale instance: *
* *
* *
* *
* Four members , two CFs *
* *
* *
* *
* Assume member 3 is used to generate this issue. *
* *
* On member 3, issue command *
* *
* *
* *
* db2stop member 3 *
* *
* On the system that is hosting member 3 , shutdown the *
* operating *
* system. *
* *
* *
* *
* Then issue the command: *
* *
* db2stop force *
* *
* *
* *
* The db2stop force command will fail with the following *
* *
* information: *
* *
* *
* *
* 2011-02-28 14:35:13 3 0 SQL1690N An error occurred *
* during DB2STOP processing of a DB2 member or CF with *
* identifier *
* "3" on host "host3d". Reason code "1". *
* *
* 2011-02-28 14:35:47 3 0 SQL1690N An error occurred *
* during DB2STOP processing of a DB2 member or CF with *
* identifier *
* "3" on host "host3d". Reason code "1". *
* *
* 2011-02-28 14:36:20 3 0 SQL1690N An error occurred *
* during DB2STOP processing of a DB2 member or CF with *
* identifier *
* "3" on host "host3d". Reason code "1". *
* *
* 2011-02-28 14:36:20 0 0 SQL1064N DB2STOP processing *
* was *
* successful. *
* *
* 2011-02-28 14:36:20 1 0 SQL1064N DB2STOP processing *
* was *
* successful. *
* *
* 2011-02-28 14:36:20 2 0 SQL1064N DB2STOP processing *
* was *
* successful. *
* *
* *
* *
* SQL6033W Stop command processing was attempted on "4" *
* node(s). *
* "3" node(s) were successfully stopped. "0" node(s) were *
* already *
* stopped. "1" node(s) could not be stopped. *
* *
* *
* *
* 2011/02/28 14:36:20 *
* *
* Return Code of db2stop force : 6 *
* *
* *
* *
* db2instance -list command shows the following: *
* *
* *
* *
* ID TYPE STATE *
* *
* HOME_HOST CURRENT_HOST ALERT *
* *
* PARTITION_NUMBER LOGICAL_PORT NETNAME *
* *
* *
* *
* -- ---- ----- *
* *
* --------- ------------ ----- *
* *
* ---------------- ------------ ------- *
* *
* 0 MEMBER STOPPED host3a *
* *
* host3a YES *
* *
* 0 0 host3a-ib *
* *
* 1 MEMBER STOPPED host3b *
* *
* host3b YES *
* *
* 0 0 host3b-ib *
* *
* 2 MEMBER STOPPED host3c *
* *
* host3c YES *
* *
* 0 0 host3c-ib *
* *
* 3 MEMBER STOPPED host3d *
* *
* host3d YES *
* *
* 0 0 host3d-ib *
* *
* 128 CF PRIMARY host3p *
* *
* host3p NO *
* *
* - 0 host3p-ib *
* *
* 129 CF CATCHUP host3s *
* *
* host3s NO *
* *
* - 0 host3s-ib *
* *
* *
* *
* HOSTNAME STATE *
* INSTANCE_STOPPED *
* ALERT *
* *
* -------- ----- *
* ---------------- *
* ----- *
* *
* host3s ACTIVE *
* NO *
* NO *
* *
* host3p ACTIVE *
* NO *
* NO *
* *
* host3d INACTIVE *
* NO *
* YES *
* *
* host3c ACTIVE *
* NO *
* NO *
* *
* host3b ACTIVE *
* NO *
* NO *
* *
* host3a ACTIVE *
* NO *
* NO *
* *
* *
* *
* There is currently an alert for a member, CF, or host in the *
* *
* data-sharing instance. For more information on the alert, *
* its *
* impact, and how to clear it, run the following command: *
* *
* 'db2cluster -cm -list -alert'. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB versio 9.8 fix pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.8 FixPack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.03.2011
26.09.2011
26.09.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
