RESTORE and RECOVER ERRORS

———————————————————————————————-

ORA-01248: file <num> was created in the future of incomplete recovery

———————————————————————————————-

========
Problem
========

ORA-01248: file 8 was created in the future of incomplete recovery
ORA-01110: data file 8: ‘/app/oracle/oradata/DB11R2/users03.dbf’

===========
Description
===========

Oracle Error :: ORA-01248

file string was created in the future of incomplete recovery

Cause

Attempting to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed.
Action

If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE.

===========
Example
===========

RMAN> alter database open resetlogs;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 06/09/2011 09:59:09
ORA-01248: file 8 was created in the future of incomplete recovery
ORA-01110: data file 8: ‘/app/oracle/oradata/DB11R2/users03.dbf’

sys@db11r2> alter database datafile 8 offline for drop;

Database altered.

RMAN> alter database open resetlogs;

sys@rman11r2> select status from v$instance;

STATUS
————
OPEN

Done.

———————————————————————-

ORA-00275: media recovery has already been started

———————————————————————-

============

Description

============

Oracle Error :: ORA-00275

media recovery has already been started

Cause

An attempt was made to start a second media recovery operation in the same session.

Action

Complete or cancel the first media recovery session or start another session to perform media recovery.

========

Example

============


SQL> recover database cancel;

———————————

ORA-00289: suggestion
———————————

ORA-00289:    suggestion < string >

Cause:   

This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.

Action:   

Consider using this filename for the next log needed for recovery.

Example

SQL> alter database recover datafile 24;
alter database recover datafile 24
*
ERROR at line 1:
ORA-00279: change 818332336 generated at 04/05/2007 05:15:16 needed for thread
1
ORA-00289: suggestion : J:\ARCHIVE_DEST2\ARCRECON_S358351594984777.ARC
ORA-00280: change 818332336 for thread 1 is in sequence #35835

After it proposes you an archived log either:
1/ accept it with: alter database recover continue;
2/ change the name with: alter database recover logfile '<name>';
3/ stop with: alter database recover cancel;

You can also say it continues automatically without asking you for each log file, answer:

4/ alter database recover continue default;

Or start with:

5/ alter database recover automatic datafile 24;

———————————————————————————————————————————————-
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence <num>
———————————————————————————————————————————————-

—————

Problem

————–

RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 29

Example


RMAN> recover database noredo; 
 SQL> alter database open resetlogs;
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: