SAP Note

Header Data

Symptom

A database shutdown fails with:   ORA-01149: cannot shutdown - file <nr> has online backup set When you start the database, the following messages are displayed although all data files are current and a recovery is unnecessary:   ORA-01113: file <nr> needs media recovery   ORA-01110: data file <nr>: '<path_and_name>' Caution: The errors ORA-01113 and ORA-01110 may also be displayed if a recovery is actually required. In this case, see Note 4161. The system generates an unusually high number of redo logs.

Other Terms

Reason and Prerequisites

1. Forgotten or missing "end backup" after manual ONLINE DB backup or after a backup tool (for example, BRBACKUP) has crashed  or

2. DB crash or "shutdown abort" during an ONLINE backup after "alter tablespace <tspname> begin backup"

Solution

See Note 23070 for general information about the basic terminology and the correlation between ORACLE backup and recovery. Also see the ORACLE and SAPDBA documentation ("SAP ORACLE Database Management"). Information about the backup status: SVRMGR> select * from v$backup;  (Status after "begin backup": 'ACTIVE'                                         otherwise:           'NOT ACTIVE') For 1.: If the DB is still open, simply use "end backup" on the relevant tablespace(s): SQL> alter tablespace <tspname> end backup; (for all tablespaces affected) (There are no ill effects if "end backup" is used several times or used without a preceeding "begin backup".) As of Oracle 10g, you can also use the simple command SQL> ALTER DATABASE END BACKUP; instead. This automatically resets all tablespaces or data files that are still in the BEGIN BACKUP mode. Problem 2. You can also reset the "Begin Backup" status in MOUNT state (for example, after a "Shutdown abort"): SQL> startup mount; SQL> alter database datafile '<datafile>' end backup;      (this command for all files in "Begin Backup" status, see above) SQL> alter database open; If all or a large number of data files are in backup mode, this procedure can be simplified by creating a script: SQL> startup mount; SQL> spool end_backup.sql SQL> select 'alter database datafile '

    4162 - Missing "end backup"  

Version   20     Validity: 18.06.2008 - active   Language   English

Released On 18.06.2008 11:52:07

Release Status Released for Customer

Component BC-DB-ORA Oracle

Priority Recommendations / Additional Info

Category Consulting

     || file#  || ' end backup;'      from v$backup where status = 'ACTIVE'; SQL> spool off; Then check the script end_backup.sql and make sure that each line ends with a semicolon.  A line that has become too long may be truncated.  In the above statement, note the blanks required after "datafile" and before the inverted comma as well as after the third inverted comma and the word "end". The script can be started as follows: SQL> @end_backup.sql You should then be able to open the database with the following command: SQL> alter database open; As of Oracle 10g, point 2. can be truncated like point 1. with SQL> ALTER DATABASE END BACKUP;

Other Attributes

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (7)

ORACLE

656363   Composite SAP Note: ORA-01194/ORA-01195

618868   FAQ: Oracle performance

605062   FAQ: Restore and recovery

43490   Collective note: SAPDBA - Restore/recovery

618868   FAQ: Oracle performance

605062   FAQ: Restore and recovery

584548   Unusually high number of redo logs

656363   Composite SAP Note: ORA-01194/ORA-01195

694155   Error due to corrupt redo logs

112266   SAP and MS Cluster Server: Frequent questions and tips

43490   Collective note: SAPDBA - Restore/recovery

Database System