APAR status
Closed as program error.
Error description
During portal 2 datacenter failover, the active cluster appears stuck in 'progressing to passive' until the passive cluster reaches 'active' state. See docs: https://www.ibm.com/docs/en/api-connect/10.0.1.x?topic=mtdcd-fai lure-handling-two-data-center-deployment
Local fix
Problem summary
During manual portal failover, active site does not go passive until passive site is made active. See note added to step 2 of the portal failover guidance here: https://www.ibm.com/docs/en/api-connect/10.0.1.x?topic=mtdcd-fai lure-handling-two-data-center-deployment
Problem conclusion
Fix targeted for release in v10.0.4.0 and v10.0.1.4. Active site will complete transition to passive without waiting on state of the other site.
Temporary fix
Comments
APAR Information
APAR number
LI82267
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
A0X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-08-03
Closed date
2021-11-09
Last modified date
2021-11-09
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
API CONNECT ENT
Fixed component ID
5725Z2201
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X"}]
Document Information
Modified date:
10 November 2021