Archive for the ‘Database Recovery’ Category

You can control whether you want to perform a manual (autorecovery off) or an automatic recovery (autorecovery on). Procedure Enter the appropriate SQLPLUS command before you enter the recover command. set autorecovery on The required offline redo log files are automatically applied without requiring any user entry. The names and paths of the offline redo log files are derived from the init.ora parameters log_archive_dest and log_archive_format, which means that required […]

Generally, Oracle treats an index tablespace just like a user tablespace. Therefore, you can use the recovery procedure for a user tablespace. The procedure below describes an additional recovery option for SAP databases. Procedure Shut down the database with this SQLPLUS command: shutdown immediate If this fails, use: shutdown abort Find out which data file is affected by the media error, using the information in the ALERT and trace files. […]

You use this recovery procedure if: One or more data files are missing from a tablespace. A user tablespace does not contain data from the Oracle Data Dictionary, active rollback segments, or temporary segments. Oracle issues error messages when a user attempts to access the involved tablespace. Error information is also written to the database ALERT and trace files. Caution If only one user tablespace is lost, you can perform […]

You can use BR*Tools for Oracle to perform a complete database recovery. BRRECOVER performs the recovery. Note This section discusses how to perform a complete database recovery. For more information about how to approach a complete database recovery, see Complete Database Recovery. End of the note. Prerequisites Make sure you have set the necessary BRRECOVER parameters in the initialization profile, because BRTOOLS uses these when it calls BRRECOVER. BRRECOVER […]

A member of the group – or the entire group – of current online redo log files (that is, the redo log files in which the database changes are currently being recorded) is lost. Use the entries in the ALERT file and in the LGWR trace file to analyze the error situation. You must check all sources of information for possible LGWR errors. Even if an error allows the instance […]

This section describes the measures you need to take after an incomplete recovery in the following cases: Case 1 Restore of a complete offline backup and subsequently opening the database, without performing a complete recovery of the database Case 2 Restore of a complete online or offline backup and subsequent point-in-time recovery of the database (with ALTER DATABASE OPEN RESETLOGS) Prerequisites There are the following possible problem situations: Situation A […]

If only one member of an inactive online redo log group has been lost, you can use the recovery procedure described in Recovering from Current Online Redo Log Missing. Experienced users can correct this error without shutting down the database. For more information, see the Oracle documentation. The recovery procedure is different when the database pauses because a redo log switch to an online redo log file was unsuccessful. None […]