IT26355: PRIMARY DB2 PATTERN INSTANCE FAILS DURING EXECUTION OF CREATEDB_HADRPRIMARY SCRIPT

IBM PureApplication Version 2.3.1.x
IBM Cloud Pak System Version 2.3.1.x

APAR status

• Closed as program error.

Error description

• DB2 Pattern instance containing Primary DB2 Server fails during
  execution of CreateDB_HADRPrimary script
  
  The  /tmp/CreateDB_HADRPrimary/std.err reports following
  exception:
  
  Exception: Can not get all information of Standby Node!
  
  Detailed message:
  
  Traceback (most recent call last):
  
    File
  "/0config/nodepkgs/common/python/maestro/vsys/util/py_executor.p
  y", line 47, in <module>
  
      execfile(sys.argv[0])
  
    File "/tmp/CreateDB_HADRPrimary/create_database.py", line
  125, in <module>
  
      hadrManager.hadrPrimarySetup(parms)
  
    File
  "/opt/IBM/maestro/agent/usr/servers/<nodename>/scripts/DB2/lib/u
  til.py", line 49, in profile_wrapper
  
      value = func(*args, **kwargs)
  
    File
  "/opt/IBM/maestro/agent/usr/servers/<nodename>/scripts/DB2/lib/H
  ADRManager.py", line 360, in hadrPrimarySetup
  
      self.createHADRProfile(parms)
  
    File
  "/opt/IBM/maestro/agent/usr/servers/<nodename>/scripts/DB2/lib/H
  ADRManager.py", line 74, in createHADRProfile
  
      if not self.hadrProfile.generate(parms):
  
    File
  "/opt/IBM/maestro/agent/usr/servers/<nodename>/scripts/DB2/lib/H
  ADRProfile.py", line 177, in generate
  
      self.initHADRProfileForGenerate(parms)
  
    File
  "/opt/IBM/maestro/agent/usr/servers/<nodename>/scripts/DB2/lib/H
  ADRProfile.py", line 154, in initHADRProfileForGenerate
  
      raise Exception('Can not get all information of Standby
  Node!')
  
  Exception: Can not get all information of Standby Node!
  

Local fix

• na
  

Problem summary

• Setup HADR across 2 deployments in different racks from Virtual
  classic pattern is not working by following the knowledge center
  documentation.
  

Problem conclusion

• Tech note  https://www.ibm.com/support/pages/node/1074939 is
  published on the Knowledge Center documentation topic links to
  deploy primary and standby parts from the Virtual System
  Patterns (Classic) page are no longer applicable - Fixed on the
  2310 level
  

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

• Fixed component name

  PAPP SYS 8382 I

• Fixed component ID

  5725G3200

Applicable component levels

• R231 PSY

     UP