|
Problem IT00726
|
Status: Closed |
AN ATTEMPT TO ATTACH LOCAL NODE BY DATA SERVER CLIENT MIGHT THROW SQL1032N. |
| product: |
DB2 COMMON CLIE / DBCMNCLNT / A10 - DB2 |
| Problem description: |
Server Client will throw SQL1032N for scenario where client
instance and server instance resides on the same platform.
clientInst1> ps -ef | grep db2sysc
serverInst1 7521 7519 0 Feb19 ? 00:00:33 db2sysc 0
clientInst1> db2 list node directory
Node Directory
Number of entries in the directory = 2
Node 1 entry:
Node name = LOCAL_NODE
Comment =
Directory entry type = LOCAL
Protocol = LOCAL
Instance name = serverInst1
clientInst1> db2 attach to LOCAL_NODE
SQL1032N No start database manager command was issued.
SQLSTATE=57019 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 for Linux, UNIX and Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* . *
**************************************************************** |
| Local Fix: |
Please catalog tcpip node instead of local node. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.1 Fix Pack 4
At a minimum, this fix should be applied on the client |
| Workaround |
As a workaround you can catalog a TCPIP node instead of a local
node. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.04.2014
26.06.2014
26.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
