Oracle case study ORA-19573

1.1.1 ORA-19573

Date:

Environment: test environment

[Scenario description]

When the database instance is in the OPEN state (read write), an error is reported when the database restoration and restoration operations are performed in RMAN.

[Error message]

RMAN> run {

2> allocate channel category type disk;

3> allocate channel ch2 type disk;

4> set until scn 1520939;

5> restore database;

6> recover database;

7> release channel restart;

8> release channel ch2;

9>}

......

Released channel: released

Released channel: ch2

RMAN-00571: ========================================================== ==============================

RMAN-00569: ==================== error messagestack follows ======================

RMAN-00571: ========================================================== ==============================

RMAN-03002: failure of restore command at05/21/2014 17:04:43

ORA-19870: error while restoring backuppiece/U01/app/test/rman/fra/TESTDB/backupset/2014_05_21/o1_mf_nnndf_TAG20140521T164225_9qrsqkyw _. bkp

ORA-19573: cannot obtain exclusive enqueuefor datafile 1

RMAN>

[Error details]

[Oracle @ oracle ~] $ Oerr ora 1, 19870

19870,000 00, "error while restoringbackup piece % s"

// * Cause: This error shocould be followed byother errors indicating

// The cause of the problem.

// * Action: See other errors actions.

[Oracle @ oracle ~] $ Oerr ora 1, 19573

19573,000 00, "cannot obtain % senqueue for datafile % s"

// * Cause: The file access enqueue cocould not be obtained for a file

// Specified in a backup, copy or restore operation.

// If the enqueue type shown is 'shared ', then the file is

// Input file for a backup or copy. If the type is 'clusive ', then

// The file is the output file for a datafile copy or restore which

// Is attempting to overwrite the currently active version of that

// File-in this case, the file must be offline or the database must

// Be closed. If the type is 'read-only', then you are attempting

// To back up or copy this file while the database is in NOARCHIVELOG

// Mode.

// * Action: Wait until the conflictingoperation is complete, then retry

// The copy or backup. If thedatabase is in NOARCHIVELOG mode, then

// All files being backed up must be closed cleanly.

[Oracle @ oracle ~] $

[Error cause]

The database is in the OPEN state, and all tablespaces and data files are ONLINE. oracle cannot restore the database.

[Solution]

In this test case, first shut down the database instance, then turned on to the MOUNT status, and then logged on to RMAN again for Incomplete recovery.