AVDF Observer Not Running on primary and standby servers
(Doc ID 3055395.1)
Last updated on DECEMBER 02, 2024
Applies to:
Oracle Audit Vault and Database Firewall - Version 20.9.0.0.0 to 20.9.0.0.0 [Release 20]Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Observer not running on primary and standby servers
[oracle@xxxx ~]$ ps -ef | grep -i observer
oracle 3855533 3854717 0 06:15 pts/0 00:00:00 grep --color=auto -i observer
[oracle@xxx ~]$ /usr/local/dbfw/bin/observerctl --start
[oracle@xxxxxx ~]$ ps -ef | grep -i observer
oracle 3855727 3854717 0 06:15 pts/0 00:00:00 grep --color=auto -i observer
[oracle@ ~]$
[oracle@xxxxx~]$ /usr/local/dbfw/bin/setup_ha.rb --status
HA mode: PRIMARY
HA server 1: xxx.xx.x.xx
HA server 2: xxx.xx.x.xx
Unique database name: DBFWDB_HA1
Current database role: PRIMARY
Data guard broker: ENABLED
Data guard observer: NO
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: 199,715,979,264
FRA used: 3,452,960,768
FRA reclaimable: 1,746,927,616
FRA available: 198,009,946,112
Gap status: NO GAP
Archived sequence: 103352
Applied sequence: 103352
Apply lag: 0:00:18
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 |
| Cause |
| Solution |
| References |