Skip to content

OraOperator v1.2.0 switchover is triggered after 3 minutes waiting #185

@andbos

Description

@andbos

I have noticed that switchover is triggered after 3 minutes waiting after upgrade to OraOperator v.1.2.0. In v.1.1.0 switchover was triggered immediately after patching .spec.setAsPrimaryDatabase.

The kubectl patch command was executed 14:33:35 CEST.

1211  2025-07-04 14:33:35 kubectl -n oracle-database --type=merge -p '{"spec":{"setAsPrimaryDatabase":"NCNFDB11"}}' patch dataguardbroker cnfdb-dgbroker

But as the pod log shows the switchover didn't start until 12:36:59 UTC:

PR00 (PID:3496): Media Recovery Waiting for T-1.S-8 (in transit)
2025-07-04T12:31:33.380796+00:00
Recovery of Online Redo Log: Thread 1 Group 5 Seq 8 Reading mem 0
  Mem# 0: /opt/oracle/oradata/NCNFDB11/onlinelog/o1_mf_5_n6hh4bhf_.log
2025-07-04T12:31:34.058791+00:00
TT02 (PID:3514): Waiting for all non-current ORLs to be archived
2025-07-04T12:31:34.058896+00:00
TT02 (PID:3514): All non-current ORLs have been archived
2025-07-04T12:32:37.819932+00:00

XDB installed.

XDB initialized.
2025-07-04T12:36:59.200461+00:00
 rfs (PID:3735): krsr_rfs_atc: Identified database type as 'PHYSICAL': Client is Foreground (PID:157)
2025-07-04T12:36:59.296169+00:00
SWITCHOVER VERIFY BEGIN
SWITCHOVER VERIFY COMPLETE
2025-07-04T12:36:59.409596+00:00
 rfs (PID:3743): krsr_rfs_atc: Identified database type as 'PHYSICAL': Client is Foreground (PID:157)
2025-07-04T12:36:59.487843+00:00
SWITCHOVER VERIFY BEGIN
SWITCHOVER VERIFY COMPLETE
2025-07-04T12:36:59.546933+00:00

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions