My Oracle Support Banner

View V$HM_RUN on Standby Database Shows Failures (Doc ID 2254780.1)

Last updated on MARCH 09, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


Oracle Data Guard 12.1 environment where primary and physical standby databases are synchronized.

V$HM_RUN check on the primary database doesn't returned any issues.

V$HM_RUN check on the physical standby database shows failures:

select * from V$HM_RUN;

Basic Run Information
Run Name : <RUN_NAME>
Run Id : <nnnnn>
Check Name : DB Structure Integrity Check
Start Time : 2017-03-27 11:05:29.065000 +03:00
End Time : 2017-03-27 11:06:10.966000 +03:00
Error Encountered : 0
Source Incident Id : 0
Number of Incidents Created : 0

Input Paramters for the Run
Run Findings And Recommendations
Finding Name : Datafiles are inconsistent
Finding ID : 9342
Status : CLOSED
Priority : HIGH
Message : Datafiles are mutually inconsistent
Message : Database may not be able to open

Further checks on the physical standby database:

RMAN> list failure; shows no failures.

RMAN> validate database; shows no failures.

ADRCI shows incidents.



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

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