<<Back to Oracle Backup & Recovery Main Page
Datafiles are mutually inconsistent Oracle Physical Standby
rman target /Recovery Manager: Release 12.1.0.2.0 - Production on Mon Sep 23 11:23:32 2019
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCLTP (DBID=XXXXX)
RMAN> list failure;
using target database control file instead of recovery catalog
Database Role: PHYSICAL STANDBY
List of Database Failures
=========================
Failure ID Priority Status Time Detected Summary
---------- -------- --------- ------------- -------
142322 HIGH OPEN 21-SEP-19 Datafiles are mutually inconsistent
RMAN> advise failure;
Database Role: PHYSICAL STANDBY
List of Database Failures
=========================
Failure ID Priority Status Time Detected Summary
---------- -------- --------- ------------- -------
142322 HIGH OPEN 21-SEP-19 Datafiles are mutually inconsistent
Mandatory Manual Actions
========================
1. Ensure the primary database is up and recover database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT command. Check alert log for potential failures that may cause recovery not to run. Potential problems may include missing archived logs or datafiles being in an orphaned incarnation.
2. Contact Oracle Support Services if the preceding recommendations cannot be used, or if they do not fix the failures selected for repair
Optional Manual Actions
=======================
no manual actions available
Automated Repair Options
========================
no automatic repair options available
SQL> Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
$sqlplus "/as sysdba"
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
SQL> recover managed standby database cancel;
Media recovery complete.
SQL>
RMAN> list failure;
Database Role: PHYSICAL STANDBY
no failures found that match specification
no rows selected
Conclusion: If you are experiencing this issue in physical standby database, just stop and start the recovery. It will fix the issue.
Comments
Post a Comment