My Oracle Support Banner

Error OAV-46599: internal error Error when performing Manual Switchover of AV Server (Doc ID 2881030.1)

Last updated on JULY 17, 2022

Applies to:

Oracle Audit Vault and Database Firewall - Version 20.6.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Testing Production HA switchover to standby .

AVDF configured in HA mode
When trying to switch the roles, error below is reported:
OAV-46599: internal error Error: The Data Guard Observer is not present

Changes

1.After HA pairing,status was as below:

Dataguard Observer status as YES here

[oracle@avsprimary ~]$ /usr/local/dbfw/bin/setup_ha.rb --status

HA mode: PRIMARY

HA server 1: <IP 1>

HA server 2: <IP 2>

Unique database name: DBFWDB_HA1

Current database role: PRIMARY

Data guard broker: ENABLED

Data guard observer: YES

Current log mode: ARCHIVELOG

Logging forced: YES

Flashback mode: YES

Current open mode: READ WRITE

Switchover status: TO STANDBY

Automatic failover: ENABLED

Failover status: TARGET UNDER LAG LIMIT

Missing listener services: NONE

Archive destination: ENABLE

Recovery mode: MANAGED REAL TIME APPLY

FRA size: 814,970,044,416

FRA used: 439,351,246,848

FRA reclaimable: 436,235,927,552

FRA available: 811,854,725,120

Gap status: NO GAP

Archived sequence: 205779

Applied sequence: 205779

Apply lag: 0:00:39

oracle@avsstandby ~]$ /usr/local/dbfw/bin/setup_ha.rb --status

HA mode: STANDBY

HA server 1: <IP 1>

HA server 2: <IP 2>

Unique database name: DBFWDB_HA2

Current database role: PHYSICAL STANDBY

Data guard broker: ENABLED

Data guard observer: YES

Current log mode: ARCHIVELOG

Logging forced: YES

Flashback mode: YES

Current open mode: MOUNTED

Switchover status: NOT ALLOWED

Automatic failover: ENABLED

Failover status: TARGET UNDER LAG LIMIT

Missing listener services: NONE

Archive destination: ENABLE

Recovery mode: MANAGED REAL TIME APPLY

FRA size: 814,970,044,416

FRA used: 31,186,747,392

FRA reclaimable: 27,226,275,840

FRA available: 811,009,572,864

2.Automatic failover was disabled

3.HA status was as below after automatic disabling automatic failover:

observer is blank on both Primary and Standby

[oracle@avsprimary ~]$ /usr/local/dbfw/bin/setup_ha.rb --status

HA mode: PRIMARY

HA server 1: <IP 1>

HA server 2: <IP 2>

Unique database name: DBFWDB_HA1

Current database role: PRIMARY

Data guard broker: ENABLED

Data guard observer:

Current log mode: ARCHIVELOG

Logging forced: YES

Flashback mode: YES

Current open mode: READ WRITE

Switchover status: TO STANDBY

Automatic failover: DISABLED

Failover status: DISABLED

Missing listener services: NONE

Archive destination: ENABLE

Recovery mode: MANAGED REAL TIME APPLY

FRA size: 814,970,044,416

FRA used: 76,646,711,296

FRA reclaimable: 70,382,518,272

FRA available: 808,705,851,392

Gap status: NO GAP

Archived sequence: 210770

Applied sequence: 210770

Apply lag: 0:00:18

 

STATUS Of STANDBY

[oracle@avsstandby ~]$ /usr/local/dbfw/bin/setup_ha.rb --status

HA mode: STANDBY

HA server 1: <IP 1>

HA server 2: <IP 2>

Unique database name: DBFWDB_HA2

Current database role: PHYSICAL STANDBY

Data guard broker: ENABLED

Data guard observer:

Current log mode: ARCHIVELOG

Logging forced: YES

Flashback mode: YES

Current open mode: MOUNTED

Switchover status: NOT ALLOWED

Automatic failover: DISABLED

Failover status: DISABLED

Missing listener services: NONE

Archive destination: ENABLE

Recovery mode: MANAGED REAL TIME APPLY

FRA size: 814,970,044,416

FRA used: 377,057,443,840

FRA reclaimable: 370,713,559,040

FRA available: 808,626,159,616

 

 

 

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.