|
Problem IC81773
|
Status: Closed |
-1032 WHEN TRYING TO CONNECT TO DB EVEN THOUGH MEMBER IS STARTED |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
After a successful global db2start, connect attempt to a db
could failed with -1032 (SQL1032N No start database manager
command was issued) which is inconsistent
$ cat db2nodes.cfg
0 coralx501 0 coralx501-10ge - MEMBER
1 coralx505 1 coralx505-10ge - MEMBER
128 coralx507 0 coralx507-10ge - CF
129 coralx508 0 coralx508-10ge - CF
$ db2instance -list
ID TYPE STATE HOME_HOST
CURRENT_HOST ALERT PARTITION_NUMBER
LOGICAL_PORT NETNAME
-- ---- ----- ---------
------------ ----- ----------------
------------ -------
0 MEMBER STARTED coralx501
coralx501 NO 0 0
coralx501-10ge
1 MEMBER STARTED coralx505
coralx505 NO 0 1
coralx505-10ge
128 CF PRIMARY coralx507
coralx507 NO - 0
coralx507-10ge
129 CF PEER coralx508
coralx508 NO - 0
coralx508-10ge
HOSTNAME STATE INSTANCE_STOPPED
ALERT
-------- ----- ----------------
-----
coralx508 ACTIVE NO
NO
coralx507 ACTIVE NO
NO
coralx505 ACTIVE NO
NO
coralx501 ACTIVE NO
NO
(jcolaco@coralx505) /home/jcolaco
$ db2 connect to X
SQL1032N No start database manager command was issued.
SQLSTATE=57019 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* PureScale *
****************************************************************
* PROBLEM DESCRIPTION: *
* db2instance -list shows that all the members have started. *
* However, when trying to connect, it will fail with -1032 (no *
* start database manager command issued.) *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v98fp5 *
**************************************************************** |
| Local Fix: |
N/A |
| Solution |
v9.8.0.5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.03.2012
13.06.2012
13.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.0.5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.5
|
 |
