IC87206: DB2START FAILS WITH SQL1032N ERROR

APAR status

• Closed as Permanent restriction.

Error description

• After a node is rebooted and the db2start command is issued a
  db2start SQL1032N error may be encountered.  If this happens it
  could be due to the fact that Tivoli System Automation (TSA) has
  not fully initialized yet, which results in any automation
  requests being sent to TSA being ignored.
  
    An example of the above problem is shown below. The following
  message will appear in the db2diag.log file:
  
  2012-08-19-05.30.08.373475+540 E484754A1498         LEVEL: Error
  PID     : 123456789             TID  : 1             PROC :
  db2star2
  INSTANCE: db2inst              NODE : 000
  HOSTNAME: hostA
  EDUID   : 1
  FUNCTION: DB2 UDB, high avail services,
  sqlhaWaitForResourceState, probe:14793
  DATA #1 : String, 28 bytes
  idle_db2inst_997_hostA-rs
  DATA #2 : String, 0 bytes
  Object not dumped: Address: 0x0FFFFFFFFFFB3134 Size: 0 Reason:
  Zero-length data
  DATA #3 : signed integer, 4 bytes
  21
  DATA #4 : signed integer, 4 bytes
  1
  DATA #5 : SQLHA Control Block, PD_TYPE_SQLHA_CONTROL_BLOCK, 4136
  bytes
  sqlhaCB->timeout: 56
  sqlhaCB->runMode: INFRASTRUCTURE
  sqlhaCB->options: NONE
  sqlhaCB->vendorHandle: 00000001100758c0
  sqlhaCB->sqlhaClusterHandle->clusterHandle: 1
  sqlhaCB->sqlhaClusterHandle->clusterErrorNum: 0
  sqlhaCB->sqlhaClusterHandle->errorMessage:<
  DATA #6 : ZRC, PD_TYPE_ZRC, 4 bytes
  0x87000057
  DATA #7 : SQLHA Cluster Session Handle,
  PD_TYPE_SQLHA_CLUSTER_HANDLE, 4112 bytes
  sqlhaClusterHandle->clusterHandle: 1
  sqlhaClusterHandle->clusterErrorNum: 0
  sqlhaClusterHandle->errorMessage:<
  DATA #8 : signed integer, 4 bytes
  0
  CALLSTCK:<
    [0] 0x0900000009E797FC
  sqlhaWaitForResourceState__FP25SQLHA_CLUSTER_OBJECT_INFO15_sqlha
  ObjStatesP19SQLHA_CONTROL_BLOCK + 0xD8
    [1] 0x0900000009E875BC
  sqlhaSetStartPreconditions__FP25SQLHA_CLUSTER_OBJECT_INFOP19SQLH
  A_CONTROL_BLOCK + 0x1518
    [2] 0x000000010000973C DB2StartMain + 0x8CBC
    [3] 0x0000000100011590 main + 0x10
    [4] 0x0000000100000320 __start + 0x98
  
    This message indicates that the resource
  'idle_db2inst_997_hostA-rs' has not come online yet, which is
  necessary in order to allow db2start to succeed. The reason it
  has not come online may be due to TSA still initializing, which
  results in the online request against the idle resource issued
  by DB2 being ignored.
  

Local fix

• Try issuing db2start again after a short time to allow TSA to
  complete its initialization which can be monitored by lssrc -ls
  command like below.
    ex, $ lssrc -ls IBM.RecoveryRM
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * pureScale feature user                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * It is recommended for the workaround to apply Local Fix.     *
  ****************************************************************
  

Problem conclusion

• This behavior is restriction and it is recommended for the
  workaround to apply Local Fix.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels