How to failover in Oracle Kubernetes environment when primary pod deleted with Observer?
0
votes
0
answers
24
views
I am running my Oracle primary database instance on pod
oracle-0
(SID=ORCLP) and standby database instance on oracle-1
Kubernetes pod. They are connected with a headless service. data guard broker, fast_start failover all are enabled and configured properly. I am running an data guard broker observer on another pod.
When I'm giving shutdown abort
command from primary pod, observer is successfully failover primary to standby pod oracle-1
.
But when I'm deleting primary pod(SID=ORCLP) for testing purpose if observer is handling failover properly, Observer is not failover primary to standby pod. Its giving me this error log continuously:
[W000 2025-01-08T05:53:05.356+00:00] Standby is in the SUSPEND state.
[W000 2025-01-08T05:53:06.355+00:00] Primary database cannot be reached.
[W000 2025-01-08T05:53:06.355+00:00] Fast-Start Failover suspended. Reset FSFO timer.
[W000 2025-01-08T05:53:06.355+00:00] Fast-Start Failover threshold has not exceeded. Retry for the next 30 seconds
[W000 2025-01-08T05:53:07.355+00:00] Try to connect to the primary.
[P005 2025-01-08T05:53:08.044+00:00] Failed to attach to ORCLP.
ORA-12545: Connect failed because target host or object does not exist
Unable to connect to database using ORCLP
Instead of failover after failover threshold, Its continuously trying connect with deleted primary pod(SID=ORCLP).
Is there anyway to solve this?
Asked by Sayed
(1 rep)
Jan 9, 2025, 05:16 AM
Last activity: Jan 9, 2025, 05:17 AM
Last activity: Jan 9, 2025, 05:17 AM