A fix is available
APAR status
Closed as program error.
Error description
A user promoted a virtual system pattern that was built on the previous virtual system pattern architecture to the new advanced architecture for virtual system patterns that was introduced in PureApplication System Version 2.0. The original pattern contains a DB2 component. The new pattern gets stuck during deployment in the "Launching" state. Logging into the DB2 virtual machine the 0config.log contains errors such as: failure in 6_opmdb2_start_monitoring.py
Local fix
Problem summary
A promoted virtual system pattern does not maintain the same code paths that were being used in the prior architecture version of the virtual system pattern. The database monitoring was attempting to perform an action and failing to start, leaving the virtual machine in Launching state.
Problem conclusion
A code fix has been provided in the database monitoring to check for a code path and to skip it and continue deploying if necessary.
Temporary fix
Comments
APAR Information
APAR number
IT05048
Reported component name
PAPP SYS 8382 I
Reported component ID
5725G3200
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-10-20
Closed date
2014-10-20
Last modified date
2014-10-20
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
R200 PSY
UP
R100 PSN
UP
R110 PSN
UP
RESP PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSM8NY","label":"PureApplication System"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"200","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
20 October 2014