Delay In PCP Failover Potentially Due To Delay In OAM Dashboard Reflecting The App Host Status
(Doc ID 2735194.1)
Last updated on MAY 27, 2022
Applies to:
Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]Information in this document applies to any platform.
Symptoms
On : 12.1.3 version, RAC/DCP issues
ACTUAL BEHAVIOR
---------------
Delay in PCP Failover potentially due to delay in OAM Dashboard reflecting the app host status
We are migrating to Oracle Cloud Infrastructure and as part of Non Functional Testing, we were testing the concurrent PCP fail-over.
The concurrent program definition is updated with an active App server and a passive app server.
During this testing, we shut down the primary concurrent manager app server using OCI console, once it was shut down, we noticed the concurrent managers were down as expected, however it took around 30-40 minutes for the managers to automatically failing over to the passive concurrent host.
We noticed and think this happened because the primary host status in OAM was still showing up, it was only until the status reflected correctly in OAM dashboard, we saw the concurrent managers failing over.
EXPECTED BEHAVIOR
-----------------------
The PCP Failover should take less then 30 - 40 minutes and should be faster.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Shut down the primary concurrent manager
2. Check if the concurrent managers automatically failing over to the passive concurrent host.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use PCP Failover .
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |