Bug 19791146 - startup fails with ORA-1194 because 'end backup' on physical standby This note gives a brief overview of bug 19791146. Click here for details of each of the sections below. Interim patches may be available for earlier versions - click here to check. On Physical STANDBY database, STARTUP of the database might fail with ORA-1194. Variable Size 520097408 bytes. ORA-10458: standby database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: '/u01/app/oracle/oradata/DBVONE/system02.dbf' This usually happens, when you try to open your standby database directly after switchover/synchronizing or creation. Database mounted. ORA-10458: standby database requires recovery&ORA-01196&ORA-01110 SQL> alter database recover managed standby database cancel; Database altered. Completed Standby Crash Recovery. FAL [server, ARC3]: FAL archive failed, see trace file. You can use LOG_FILE_NAME_CONVERT and DB_FILE_NAME_CONVERT parameter explicitly with DUPLICATE command Now create new online redo logs When SQL Server allocates a page to a table or index for which no file group was specified when they were created, the pages are allocated from Go to Primary database and SQL> recover managed standby database using current logfile disconnect; Media recovery complete. Drop standby logs on standby database ALTER DATABASE DROP STANDBY LOGFILE GROUP 4; ALTER DATABASE DROP STANDBY LOGFILE GROUP 5; ALTER DATABASE DROP STANDBY LOGFILE GROUP 6; ALTER DATABASE DROP STANDBY LOGFILE GROUP 7; 4 You have to stop the standby or data guard database recovery However, this is not a Database mounted.
ORA-01013: user requested cancel of current operation Recovery interrupted! ORA-01152: file 1 was not restored from a sufficiently old backup. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '//.dbf' Changes Problem happens with following conditions. Physical Standby Database Introduction - Physical and Logical Standby.
ORA-10458: standby database requires recovery ORA-01196: 1 ORA-01110: 1: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF' rmanORA-01152 file 1 was not restored from a sufficiently old backuoffline) Eclipse:the file dx.jar was not loaded from the SDK matlab"Message Catalog MATLAB:FileIO was not loaded from the file. To start real-time apply: SQL> alter database recover managed standby database using current logfile disconnect; 15 SQL>ALTER DATABASE DROP LOGFILE GROUP 2; If you have skipped Step 4 then you will get ORA-01624 while droping the Online Redolog Group with Status CLEARING I copied this example from MSDN: USE AdventureWorks2012; GO -- Truncate the log by Chybov kd databzy Oracle 12cR2 ORA-10458 - standby database requires recovery. openORA-10458: standby database requires recovery_cuihengju8933-. It is always kept in a managed recovery mode and is unusable as long as primary is up and functional. SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; Database altered. ORA-10458: standby database requires recovery. RACDGmountopen. ORA-10458: standby database requires recovery ORA-01196: 1 . ORA-01110: 1:'XXXXXXXXXXXXX\\XXXXX1.DBF' SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT; Database altered. mount alter database recover managed standby database using current logfile disconnect from session; . We are going to create the standby database by duplicating the primary database for standby using RMAN. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '/u01/app/oracle/oradata/dg02/system01.dbf' - - Switch logs on primary and verify that redo apply has stopped on standby A few tasks are to be performed beforehand, then away we go. DGMGRL>EDIT database set property LogXptMode='SYNC' SQL>ALTER DATABASE DROP LOGFILE GROUP 2; If you have skipped Step 4 then you will get ORA-01624 while droping the Online Redolog Group with Status CLEARING log References: ORA-19527 reported in Standby Database when starting Managed Recovery (Doc ID 352879 SQL> alter system set The datafile will require media recovery from that time, and at to either a) a time past the end backup in the archivelogs or b) to the current redolog. Error code: ORA-10458 Description: standby database requires recovery Cause: A standby database was in a state requiring media recovery when an attempt was made to open the standby database. DIA-49108: Event Name [PARAMETER] not found, DIA-49100: Failed to process event statement [parameter], ORA-01078: failure in processing system parameters ORA-10458: Standby Database Requires Recovery; Oracle ORA-01668: standby database requires DROP option for offline of data file. ORA-01196: file 1 is inconsistent due to a failed media Oracle 12c DGSQL> alter database open read only;alter database open read only*ERROR at line 1:ORA-10458: standby database requires. Few Days later the storage was returned, I 3) Take incremental backup from primary using DR current SCN number. SQL> Alter Database Recover Managed Standby Database Disconnect; Database altered. Databza: 11g ORA-01110: data file 1: /u01/app/oracle/oradata/prime/system01.dbf SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery. ORA-10458: standby database requires recovery. [ [email protected] trace]$ tail -f alert_sde1.
Answer: We start by using the oerr utility for information on the ORA-01152 error: ORA-01152: file 1 was not restored from a sufficiently old backup. SQL> alter database add standby logfile group 12 '+DG_TST_FRA' size 2048M; Database altered Drop the Online Redo Logfile Group: SQL>ALTER DATABASE DROP LOGFILE GROUP 2; If you have skipped Step 4 then you will get ORA-01624 while droping the Online Redolog Group with Status CLEARING alter database add logfile thread 1 group 5 To solve this error, Stop the Standby database instances as follows, then start standby database as One node. ERROR at line 1: ORA-10458: standby database requires recovery. ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '//.dbf' ORA-10458: standby database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: '/u01/app/oracle/oradata/ORCL/system01.dbf' ORA-01152 means that we might have some data files which are newer than the controlfile, so the database needs to be recovered. ORA-10458: standby database requires recovery. ORACLE instance started. ORA-01196: file 1 is inconsistent due to a failed media recoverysession. ORA-10458: standby database requires recovery&ORA-01196&ORA-01110 This file is still in the future of the last log applied. Confirm each of the logs that you are prompted for until you receive the message "Media Recovery Complete". The prominent difference with a logical standby database is that the latter is not an exact replica of the primary database. i.o.w: Login to the database as the USER that runs the procedure, and see whether the db link you are trying to connect to does exist.. more specifically, is its HOST property correct ORA-10458: standby database requires recovery ORA-01196: 1 . ORA-01110: 1:'XXXXXXXXXXXXX\\XXXXX1.DBF' ORA-10458: standby database requires recovery ORA-01196: 1 ORA-01110: 1: 'XXXXXXXXXXXXXXXXXX\XXXXX1.DBF' . SQL>alter database drop standby logfile group 4; Database altered NOTE: SIZE OF STANDBY LOGFILE SHOULD BE SAME AS ONLINE LOGFILE c SQL> alter database drop standby logfile group 11; alter database drop standby logfile group 11 ERROR at line 1: ORA-01156: recovery or flashback in progress may need access to files Solution: cancel the recovery On a I guess we can solve this issue by executing the below commands. ORA-01152: file 1 was not restored from a sufficiently old backup Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent. This file is still in the future of the last log applied. Check the alert log.
SQL> ALTER DATABASE OPEN READ ONLY; Database altered. ERROR at line 1: ORA-10458: standby database requires recovery. SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; Database altered. Action: Either apply more logs until the database is consistent or restore the database file from an older backup and repeat recovery. SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup 11g. ORA-01152: file 1 was not restored from a sufficiently old backup. ORA-10458: standby database requires recovery ORA-01196: 1 ORA-01110: 1: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF' Fixed Size 2924928 bytes. SQL> alter database recover managed standby database cancel; Database altered. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '+DATA/stby11g/datafile/system.258.937841323' SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: Fixed Size 2257520 bytes. Check the alert log. Database Buffers 1375731712 bytes. Redo Buffers 13848576 bytes. Search: Alter Database Clear Logfile Group Standby. Getting ORA-01078: failure in processing system parameters when trying to upgrade the database using Transaction code DBUA. Each task is outlined in the following code: Task #1: get the service name for the standby database. VMware Workstation 9.0 RACDB 192.168.1.61/62 DB:oracle 11g R2 OS:readhat linux 5.5 ORA-01157: cannot identify/lock data file 97 - see DBWR trace file. SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery ORA-01152: file 1 So after the application of archivelog the standby database opened read only successfully, because controlfile and all datafiles have the same If you create a DB Instance without specifying a DB Parameter Group, a default DB Search: Alter Database Clear Logfile Group Standby. Total System Global Area 1610612736 bytes. If you are prompted for a non-existing archived log, Oracle probably needs one or more of the online logs to proceed with the recovery. ORA-01110: data file 1: ORA-01111: name for data file 97 is unknown - rename to correct file. . DG. DIA-49108: Event Name [PARAMETER] not found, DIA-49100: Failed to process event statement [parameter], ORA-01078: failure in processing system parameters ORA-10458: Standby Database Requires Recovery; Oracle Variable Size 1811942800 bytes. standby RAC restart database ASM DBFILE1 FRA1 . Total System Global Area 3206836224 bytes. ORA-10458: standby database requires recovery. *. Clear Alter Logfile Standby Group Database . Saw errors ORA-01196 thrown by the database when trying to activate a standby database. I have 3 database 1 primary and two standby, The storage of one the standby was abruptly removed without shutting down the database. SQL> SQL> SQL> recover managed standby database cancel; Media recovery complete. openORA-10458: standby database requires recovery. ORA-10458: standby database requires recovery. Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent.
SQL> alter database drop standby logfile group 5; Database altered SQL> alter system set standby_file_management=auto; NAME DATABASE_ROLE -bugra PRIMARY STANDBY_SQL > alter database recover managed standby database disconnect from session; Database altered Hence, the MySQL ALTER COLUMN performs the query to add, modify, delete, ORA-01196: file 1 is inconsistent due to a failed media recovery session. Database Buffers 1073741824 bytes. Take note of database file system location in Standby: Capture records of all physical files Standby crash recovery failed to bring standby database to a consistent point because needed redo hasn't arrived yet. ERROR at line 1: ORA-01196: file 1 is inconsistent due to a failed media recovery session. oracle@testdb01 (db1tesd) bin]$ srvctl start database -d db1tesd PRCR-1079 : Failed to start resource ora.db1tesd.db CRS-5017: The resource action "ora.db1tesd.db start" encountered the following error: ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session To solve this error, Stop the Standby database instances as follows, then start standby database as One node. sqlplus / as sysdba. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '/u01/app/oracle/oradata/proe/system01.dbf'. If Managed recovery is already running on a instance and you want it to be run from specific instance: Stop the Managed recovery from the instance it is running and start managed recovery from first/specific instance.
ORA-01013: user requested cancel of current operation Recovery interrupted! ORA-01152: file 1 was not restored from a sufficiently old backup. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '/
ORA-10458: standby database requires recovery ORA-01196: 1 ORA-01110: 1: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF' rmanORA-01152 file 1 was not restored from a sufficiently old backuoffline) Eclipse:the file dx.jar was not loaded from the SDK matlab"Message Catalog MATLAB:FileIO was not loaded from the file. To start real-time apply: SQL> alter database recover managed standby database using current logfile disconnect; 15 SQL>ALTER DATABASE DROP LOGFILE GROUP 2; If you have skipped Step 4 then you will get ORA-01624 while droping the Online Redolog Group with Status CLEARING I copied this example from MSDN: USE AdventureWorks2012; GO -- Truncate the log by Chybov kd databzy Oracle 12cR2 ORA-10458 - standby database requires recovery. openORA-10458: standby database requires recovery_cuihengju8933-. It is always kept in a managed recovery mode and is unusable as long as primary is up and functional. SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; Database altered. ORA-10458: standby database requires recovery. RACDGmountopen. ORA-10458: standby database requires recovery ORA-01196: 1 . ORA-01110: 1:'XXXXXXXXXXXXX\\XXXXX1.DBF' SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT; Database altered. mount alter database recover managed standby database using current logfile disconnect from session; . We are going to create the standby database by duplicating the primary database for standby using RMAN. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '/u01/app/oracle/oradata/dg02/system01.dbf' - - Switch logs on primary and verify that redo apply has stopped on standby A few tasks are to be performed beforehand, then away we go. DGMGRL>EDIT database set property LogXptMode='SYNC' SQL>ALTER DATABASE DROP LOGFILE GROUP 2; If you have skipped Step 4 then you will get ORA-01624 while droping the Online Redolog Group with Status CLEARING log References: ORA-19527 reported in Standby Database when starting Managed Recovery (Doc ID 352879 SQL> alter system set The datafile will require media recovery from that time, and at to either a) a time past the end backup in the archivelogs or b) to the current redolog. Error code: ORA-10458 Description: standby database requires recovery Cause: A standby database was in a state requiring media recovery when an attempt was made to open the standby database. DIA-49108: Event Name [PARAMETER] not found, DIA-49100: Failed to process event statement [parameter], ORA-01078: failure in processing system parameters ORA-10458: Standby Database Requires Recovery; Oracle ORA-01668: standby database requires DROP option for offline of data file. ORA-01196: file 1 is inconsistent due to a failed media Oracle 12c DGSQL> alter database open read only;alter database open read only*ERROR at line 1:ORA-10458: standby database requires. Few Days later the storage was returned, I 3) Take incremental backup from primary using DR current SCN number. SQL> Alter Database Recover Managed Standby Database Disconnect; Database altered. Databza: 11g ORA-01110: data file 1: /u01/app/oracle/oradata/prime/system01.dbf SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery. ORA-10458: standby database requires recovery. [ [email protected] trace]$ tail -f alert_sde1.
Answer: We start by using the oerr utility for information on the ORA-01152 error: ORA-01152: file 1 was not restored from a sufficiently old backup. SQL> alter database add standby logfile group 12 '+DG_TST_FRA' size 2048M; Database altered Drop the Online Redo Logfile Group: SQL>ALTER DATABASE DROP LOGFILE GROUP 2; If you have skipped Step 4 then you will get ORA-01624 while droping the Online Redolog Group with Status CLEARING alter database add logfile thread 1 group 5 To solve this error, Stop the Standby database instances as follows, then start standby database as One node. ERROR at line 1: ORA-10458: standby database requires recovery. ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '/
SQL> ALTER DATABASE OPEN READ ONLY; Database altered. ERROR at line 1: ORA-10458: standby database requires recovery. SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; Database altered. Action: Either apply more logs until the database is consistent or restore the database file from an older backup and repeat recovery. SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup 11g. ORA-01152: file 1 was not restored from a sufficiently old backup. ORA-10458: standby database requires recovery ORA-01196: 1 ORA-01110: 1: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF' Fixed Size 2924928 bytes. SQL> alter database recover managed standby database cancel; Database altered. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '+DATA/stby11g/datafile/system.258.937841323' SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: Fixed Size 2257520 bytes. Check the alert log. Database Buffers 1375731712 bytes. Redo Buffers 13848576 bytes. Search: Alter Database Clear Logfile Group Standby. Getting ORA-01078: failure in processing system parameters when trying to upgrade the database using Transaction code DBUA. Each task is outlined in the following code: Task #1: get the service name for the standby database. VMware Workstation 9.0 RACDB 192.168.1.61/62 DB:oracle 11g R2 OS:readhat linux 5.5 ORA-01157: cannot identify/lock data file 97 - see DBWR trace file. SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-10458: standby database requires recovery ORA-01152: file 1 So after the application of archivelog the standby database opened read only successfully, because controlfile and all datafiles have the same If you create a DB Instance without specifying a DB Parameter Group, a default DB Search: Alter Database Clear Logfile Group Standby. Total System Global Area 1610612736 bytes. If you are prompted for a non-existing archived log, Oracle probably needs one or more of the online logs to proceed with the recovery. ORA-01110: data file 1: ORA-01111: name for data file 97 is unknown - rename to correct file. . DG. DIA-49108: Event Name [PARAMETER] not found, DIA-49100: Failed to process event statement [parameter], ORA-01078: failure in processing system parameters ORA-10458: Standby Database Requires Recovery; Oracle Variable Size 1811942800 bytes. standby RAC restart database ASM DBFILE1 FRA1 . Total System Global Area 3206836224 bytes. ORA-10458: standby database requires recovery. *. Clear Alter Logfile Standby Group Database . Saw errors ORA-01196 thrown by the database when trying to activate a standby database. I have 3 database 1 primary and two standby, The storage of one the standby was abruptly removed without shutting down the database. SQL> SQL> SQL> recover managed standby database cancel; Media recovery complete. openORA-10458: standby database requires recovery. ORA-10458: standby database requires recovery. Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent.
SQL> alter database drop standby logfile group 5; Database altered SQL> alter system set standby_file_management=auto; NAME DATABASE_ROLE -bugra PRIMARY STANDBY_SQL > alter database recover managed standby database disconnect from session; Database altered Hence, the MySQL ALTER COLUMN performs the query to add, modify, delete, ORA-01196: file 1 is inconsistent due to a failed media recovery session. Database Buffers 1073741824 bytes. Take note of database file system location in Standby: Capture records of all physical files Standby crash recovery failed to bring standby database to a consistent point because needed redo hasn't arrived yet. ERROR at line 1: ORA-01196: file 1 is inconsistent due to a failed media recovery session. oracle@testdb01 (db1tesd) bin]$ srvctl start database -d db1tesd PRCR-1079 : Failed to start resource ora.db1tesd.db CRS-5017: The resource action "ora.db1tesd.db start" encountered the following error: ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session To solve this error, Stop the Standby database instances as follows, then start standby database as One node. sqlplus / as sysdba. ORA-10458: standby database requires recovery ORA-01196: file 1 is inconsistent due to a failed media recovery session ORA-01110: data file 1: '/u01/app/oracle/oradata/proe/system01.dbf'. If Managed recovery is already running on a instance and you want it to be run from specific instance: Stop the Managed recovery from the instance it is running and start managed recovery from first/specific instance.