Media Recovery

I am running Oracle 10g on windows 2003 R2.
1) My UNDO TBS require media recovery, but the data file is in place for the mentioned location.
Error encountered ORA - 01113 - needs media recovery.
How can i do media recovery.
2) My PROD1 TBS was full and i wanted to resize the datafile. i got error on the client admin console and connection was lost.
When i try to connect again to the instance i get ORA- 12638 - credential fail error.
Am not able to connect to the instance from client admin console, but i am already connect thru SQL Plus on the DB Server.
Please adivse how can i resolve this.
Regards

I get following error when i try to recover undo tbs
datafile.
SQL> recover datafile
'e:\oracle\oradata\ptmn\undotbs.dbf';
ORA-00603: ORACLE server session terminated by fatal
errorCheck your alert.log see if there any additional errors.
Check if the datafile is still online,
select * from dba_data_files
where file_id=2Do you have any active transaction in the database ?
select * from v$transactionIf there's no active undo segment, it's might be easier just create a new undo tablespace, change your default undo tablespace to new one and offline drop the old one.

Similar Messages

RMAN Restore Error - media recovery requesting unknown log: thread 1 seq 7

Im using RMAN to copy a database to another server. The new server is IDENTICAL to the old one. By identical I mean it has the same sever name, ip address, operating system, Oracle version and directory structure.
The new server already has the instance created, (same name as the old server instance, paths etc)
The backup files have been manually restored to the new server, same locations as they were on the old one. ( RMAN did an automatic controlfile backup and also the archivelogs on the old server ).
Ive restored the control file on the new server from the RMAN backup pieces.
Ive catalogued the RMAN backup pieces on the new server.
I know the last sequence available in the archivelogs backup by running on the new server :
list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
5 14.43M DISK 00:00:03 11-MAY-11
BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163502
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
011_05_11\O1_MF_ANNNN_TAG20110511T163502_6WOC5833_.BKP
List of Archived Logs in backup set 5
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2 550217 10-MAY-11 556559 11-MAY-11
1 3 556559 11-MAY-11 559776 11-MAY-11
1 4 559776 11-MAY-11 560093 11-MAY-11
1 5 560093 11-MAY-11 560794 11-MAY-11
BS Key Size Device Type Elapsed Time Completion Time
7 15.50K DISK 00:00:01 11-MAY-11
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163653
Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
List of Archived Logs in backup set 7
Thrd Seq Low SCN Low Time Next SCN Next Time
1 6 560794 11-MAY-11 560851 11-MAY-11
So far its all going swimmingly well.
Now I want to restore the datafiles and recover. So I ran :
RMAN run { restore database; recover database; alter database open resetlogs; }
This gave me the output below which goes great but I get a final error, I think the error is because its looking for an archive log thats not in the backup set, but it should be. However, I think SCN 560851 is for a log that hadnt been created yet on the old server when the backup was ran ?
How do I address resolving the error ? Its worth pointing out log, "archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741" isnt on the old server either which is why its not in the backup set.
I can do a alter database open reset logs but Id prefer to know why its failing.
Any help would be much appreciated.
RMAN> run { restore database; recover database; alter database open resetlogs; }
Starting restore at 11-MAY-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSTEM01.DBF
restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\UNDOTBS01.DBF
restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSAUX01.DBF
restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\USERS01.DBF
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP tag=TAG20110511T163507
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
Finished restore at 11-MAY-11
Starting recover at 11-MAY-11
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=6
channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP tag=TAG20110511T163653
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC thread=1 sequence=6
channel default: deleting archive log(s)
archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
\2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741
unable to find archive log
archive log thread=1 sequence=7
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/11/2011 18:15:42
RMAN-06054: media recovery requesting unknown log: thread 1 seq 7 lowscn 560851
RMAN>
Edited by: user12173666 on 11-May-2011 10:28

You need to do incomplete recovery i.e. to ask RMAN to restore/recover to some specific point in time. This is usually done with some UNTIL clause or SET UNTIL statement. Example in your case:
SET UNTIL SEQUENCE 7;See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta065.htm#RCMRF160.

How to do media recovery from cold backup?????????/

Hi
i take cold backup of my 9i database ....
in case my database is up .....
how will i recover my database if i lose a single database file and i want to recover it from cold backup......
Thanks in advance
Gagan

Here you go
These are the steps:
1. Restore the lost file from a backup.
2. If the database is down, mount it.
SVRMGR> STARTUP MOUNT PFILE=<location_of_pfile>;
3. Issue the following query:
SVRMGR> SELECT V1.GROUP#, MEMBER, SEQUENCE#,
FIRST_CHANGE#
FROM V$LOG V1, V$LOGFILE V2
WHERE V1.GROUP# = V2.GROUP# ;
This will list all your online redolog files and their respective
sequence and first change numbers.
4. If the database is in NOARCHIVELOG mode, issue the query:
SVRMGR> SELECT FILE#, CHANGE# FROM V$RECOVER_FILE;
If the CHANGE# is GREATER than the minimum FIRST_CHANGE# of your logs,
the datafile can be recovered. Just keep in mind that all the logs to
applied will be online logs, and move on to step 5.
If the CHANGE# is LESS than the minimum FIRST_CHANGE# of your logs, the
file cannot be recovered. Your options at this point would be to restore
the most recent full backup (and thus lose all changes to the database
since) or recreate the tablespace as explained in scenario a.
5. Recover the datafile:
SVRMGR> RECOVER DATAFILE '<full_path_file_name>'
6. Confirm each of the logs that you are prompted for until you receive the
message "Media recovery complete". 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. Compare the sequence number referenced in the
ORA-280 message with the sequence numbers of your online logs. Then enter
the full path name of one of the members of the redo group whose sequence
number matches the one you are being asked for. Keep entering online logs
as requested until you receive the message "Media recovery complete"
7. If the database is at mount point, open it.

Media Recovery Waiting for thread 1 sequence (in transit)

I have rebuilt our standby database using an rman duplicate since it was missing many archive logs.
Following the duplicate, the standby is now almost in sync with the primary. Logs are shipping across but are not being applied in a timely manner. How long should it take for an archive log from the primary to be applied to the standby?
I need to know this so that a proper script can be set up to check the primary and standby. At the moment they are never exactly in sync - always one sequence number behind the primary.
Why is the standby is not applying in a timely manner?
From the alert log:
Media Recovery Waiting for thread 1 sequence 11278 (in transit)
The log seems to be "in transit" for a long time
PRIMARY:
SQL> select max (sequence#) current_seq from v$log;
CURRENT_SEQ
11278
SB:
SQL> select MAX (SEQUENCE#), APPLIED FROM V$ARCHIVED_LOG where APPLIED ='YES' GROUP BY APPLIED;
MAX(SEQUENCE#) APP
11277 YES
ALERT LOG:
RFS[2]: Archived Log: '/backup/prod/log_1_11277_704816194.dbf'
Primary database is in MAXIMUM PERFORMANCE mode
Mon Nov 1 15:22:01 2010
Media Recovery Log /backup/prod/log_1_11272_704816194.dbf
Mon Nov 1 15:26:49 2010
Media Recovery Log /backup/prod/log_1_11273_704816194.dbf
Mon Nov 1 15:29:54 2010
Media Recovery Log /backup/prod/log_1_11274_704816194.dbf
Mon Nov 1 15:34:18 2010
Media Recovery Log /backup/prod/log_1_11275_704816194.dbf
Mon Nov 1 15:36:42 2010
Media Recovery Log /backup/prod/log_1_11276_704816194.dbf
Mon Nov 1 15:39:43 2010
Media Recovery Log /backup/prod/log_1_11277_704816194.dbf
Mon Nov 1 15:42:34 2010
Media Recovery Waiting for thread 1 sequence 11278 (in transit)
I should add that I understand that for the Primary and Standby to be out by one log is not cause for concern (they are applying). Its just that I wanted to script a check that would compare them both, and and the moment they are never equal - when I understand that they should be and that the logs should be applied almost immediately.
Edited by: Dan A on Nov 1, 2010 4:36 PM

How long should it take for an archive log from the primary to be applied to the standby?depends on network speed also.
make sure the archives are shipped to standby location.
PRIMARY:
SQL> select max (sequence#) current_seq from v$log;
CURRENT_SEQ
11278(this is log not archivelog ) ..... :)SB:
SQL> select MAX (SEQUENCE#), APPLIED FROM V$ARCHIVED_LOG where APPLIED ='YES' GROUP BY APPLIED;
MAX(SEQUENCE#) APP
11277 YES
Hi check is MRP started or not?
primary database you need not check current sequence, check last generated sequence..not current sequence.
current sequence is redo log which has been not yet archived
I think everything is perfect here.. no issues.
Hope you understood, let me know if not clear , thanks.

RMAN-06054: media recovery requesting unknown archived log

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/16/2013 09:03:43
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 34751 and starting SCN of 8923445274I am receiving the error above on performing RMAN Active cloning, please advise how to resolve this

In addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
Edited by: user11989003 on May 29, 2013 10:17 AM

Media Recovery Log    DATAGUARD

hi all ,
i have installed 10.2.0.2 databases and configure dataguard. everything works fine but i have 1 problem.
imagine that server 1 is primary ;
when i check on server 1 ; (primary DB)
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination            /u01/app/oracle/archive/SID
Oldest online log sequence 215
Next log sequence to archive 218
Current log sequence 218
server 2 ( Standby server )
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination            dgsby_Stan
Oldest online log sequence 216
Next log sequence to archive 0
Current log sequence 218
on the alert_log of stanby server , it locate the archived logs from primary on */u01/app/oracle/product/10g/dbs/* not on */u01/app/oracle/archive/SID*
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[6]: Successfully opened standby log 5: '/u02/app/oracle/oradata/SID/stdby_log01_1.log'
Mon Dec 19 13:16:28 2011
Media Recovery Log /u01/app/oracle/product/10g/dbs/dgsby_Stan1_217_767463156.dbf
Media Recovery Waiting for thread 1 sequence 218 (in transit)
Mon Dec 19 13:16:31 2011
Recovery of Online Redo Log: Thread 1 Group 5 Seq 218 Reading mem 0
Mem# 0 errs 0: /u02/app/oracle/oradata/SID/stdby_log01_1.log
if i do switchover i faced with same reverse situation ; ( old primary acts like the old standby and old standby acts like old primary db )
i have already set log_archive_dest_1 on both server.
i want both standby and primary db locates the archive logs on */u01/app/oracle/archive/SID* not on */u01/app/oracle/product/10g/dbs/*
what do i have to correct this situation ???
thanks

here is the output from standby ;
SQL>
SQL> show parameter standby_archive_dest
NAME TYPE VALUE
standby_archive_dest string /u01/app/oracle/archive/TELE
SQL>
SQL> show parameter log_archive_dest_1
NAME TYPE VALUE
log_archive_dest_1 string location="/u01/app/oracle/arch
ive/SID", valid_for=(ONLINE_L
OGFILE,ALL_ROLES)
log_archive_dest_10 string
SQL> show parameter log_archive_dest
NAME TYPE VALUE
log_archive_dest string
log_archive_dest_1 string location="/u01/app/oracle/arch
ive/SID", valid_for=(ONLINE_L
OGFILE,ALL_ROLES)
log_archive_dest_10 string
log_archive_dest_2 string location="dgsby_Stan", valid_
for=(STANDBY_LOGFILE,STANDBY_R
OLE)
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
NAME TYPE VALUE
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string ENABLE
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
NAME TYPE VALUE
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable

What is Media Recovery Log ..? Physical Standby Database

Hello All,
In my physical stdby database alert log I could see the below message, I'm not sure what id Media Recovery Log and why it is dumping ORACLE_HOME Directory..?
Could any one please help on this..? I need to house keep ORACLE_HOME directory.
Oracle 11gR2 / RHEL5
RFS[164]: No standby redo logfiles available for thread 2
RFS[164]: Opened log for thread 2 sequence 1995 dbid 287450012 branch 760028574
Fri Nov 11 19:39:05 2011
Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1992_760028574.dbf
Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1993_760028574.dbf
Media Recovery Waiting for thread 1 sequence 5568 (in transit)
Fri Nov 11 19:39:53 2011
Archived Log entry 948 added for thread 2 sequence 1994 rlc 760028574 ID 0x1122a1
FYI : The primary and standby database are in sync.

Hello;
The alert log is providing you with information. If you want more run this query :
select process,status,client_process,sequence# from v$managed_standby;You should see processes like ARCH, RFS and MRP0.
MRP will tell you if its applying log(s), waiting for a log, or if it thinks there's a gap.
PROCESS   STATUS       CLIENT_P SEQUENCE#
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
MRP0      APPLYING_LOG N/A            5051
RFS       IDLE         N/A               0
RFS       IDLE         UNKNOWN           0There's a tiny amount of information about this under "9.3.1 Adding a Datafile or Creating a Tablespace" in Oracle document E10700-02.
If you find this helpful please click the "helpful" button.
Best Regards
mseberg

"needs media recovery" after a successful recovery ???

RMAN novice here....
Oracle 9.2.0.1.0 on Redhat Linux (Itanium)
Running in NOarchivelog mode
In RMAN, I backed up a set of datafiles in read only mode taking this approach....
sql "alter tablespace foo read only";
configure channel 1 device type disk format 'backupdisk/mybackuparea/foo.dbf.bck';
backup datafile 'dbdisk/mydb/foo.dbf';
sql "alter tablespace foo read write;
Everything seemed to go fine.
After some time, I wanted to restore/recover. This is what I did (again, in RMAN"...
sql "alter fablespace foo offline";
restore datafile 'dbdisk/mydb/foo.dbf';
recover datafile 'dbdisk/mydb/foo.dbf' noredo;
sql "alter tablespace foo online";
My first stab at it, without the "noredo" failed. But with the "noredo" I got
"Starting recover at ...."
A set of channel assignment statements
"Finished recover at ..."
Looks to have run OK.
But then, when I try to put the tablesopace back online...
"failure of sql command on default channel at...."
"failure during parse/execution of SQL statement: alter tablespace foo online"
"file 1 needs media recovery"
"data file 1: 'dbdisk/mydb/foo.dbf'"
What gives?
Thanks for any help

I've read the books and googled this to death.
Looks like I'm screwed.
At this point, I don't even care about the datafile or the tablespace it contained. I just want my database back.
I dropped the tablespace and it's datafile (and it's data too). I'll have to repopulate from scratch.
Lesson learned
This is what I want to do.....
I want to do a 1x/wk backup of a schema (not the whole DB, I don't have enough disk space for that, just 1 of the schemas). I've designed the thing such that each schema has it;s own tablespaces (no overlap) and each tablespace maps to a single datafile.
I would have liked to do some sort of online backup of the schema (read/write while backup is happening), but I'll settle for read only. If Oracle can't hack that, then I'll take the tablespaces offline.
The schema contains hundreds of millions of records, and the load preocess involves several times that number of data manipulation statements (deletes, updates, inserts). I'd rather not use archivelog mode because I don't have the disk space for it. And, given the volume and nature of the data I'm loading (hundreds of millions of records, created from the data in large raw data files), and how it's being loaded (precompiled C/SQL programs), I would never have need to "rerun" the enormous archives for any reason.
So...
1) backup a single schema (an exclusive set of tablespaces/datafiles)
2) as "online" as possible
3) in noarchivelog mode.
The only thing that I've seen that can do this is EXPORT/IMPORT. I tried that, but extrapolating IMPORT performance, even with all the streamlining recommendations, would take over 3 days. For this reason, IMPORT is not a viable option.
-dave

Media Recovery failed with error 1111

Hi,
on 10g R2 on Unix I have :
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
Fri Jun 24 10:56:52 2011
Media Recovery failed with error 1111
From alert.log :
Errors in file /data01/oracle/mydb/admin/bdump/hhhh_17637.trc:
ORA-01111: name for data file 523 is unknown - rename to correct file
ORA-01110: data file 523: '/oracle/product/10g/db_1/dbs/UNNAMED00523'
ORA-01157: cannot identify/lock data file 523 - see DBWR trace file
ORA-01111: name for data file 523 is unknown - rename to correct file
ORA-01110: data file 523: /oracle/product/10g/db_1/dbs/UNNAMED00523'
Any idea ?
Thanks.

here is one test case, i ran into same issue. and reolved as below.
When Standby_file_management is set to “MANUAL” , if any data files added on primary database, These changes certainly won’t be altered in standby database.
After starting MRP process, it dies and terminated with the following errors.
Errors from Alert log file:-
Errors in file /oracle/app/oracle/admin/CC/bdump/cc_mrp0_22294.trc:
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
Errors from Trace file:-
MRP0: Background Media Recovery terminated with error 1111
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
ORA-01111: name for data file 536 is unknown - rename to correct file
ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
ARCH: Connecting to console port...
Check out from SQL, Which files need to be recovered on standby database?
SQL> select * from v$recover_file where error like '%FILE%';
FILE# ONLINE ONLINE_ ERROR CHANGE# TIME
+536 ONLINE ONLINE FILE MISSING 0+
SQL>
On Primary check out for actual naming convention:-
SQL> select file#,name from v$datafile where file#=536;
FILE# NAME
+536 DATA/c/datafile/undotbs9.595.750444337
SQL>
On Standby check datafile name:-
SQL> select file#,name from v$datafile where file#=536;
FILE# NAME
+536 /oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536+
SQL>
Make sure still standby_file_management is set to “MANUAL”, After performing media recovery again can be enabled to “AUTO”.
Rename datafile from standby database:-
SQL> alter database create datafile '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536' as 'DATA3/cc/datafile/undotbs9_595_750444337';+
Database altered.
Start the MRP Now:-
SQL> alter database recover managed standby database disconnect from session;
Database altered.
After creating the file, MRP will start applying archives on standby database.

Media recovery issue

Hello
Why is media recovery is faster than, normal DML,DDL,etc?
In production database, It took 1 hour to rebuild indexes and move some objects to diffrent tablespace.
However, When I apply the archivelog of these changes to standby, it took about 20 minutes.
What is reason for this?
Cheers

Media Recovery / Physical Standby operations are faster because they actually only write the final results.
For example, in the index rebuild case, the operations doing the SQL are
a. read table, get column values from table
b. sort values
c. if allocated pga/sort_area is insufficient, overflow to disk
d. run final sort pass, if necessary
e. write sorted results to the index segment
(recursive SQLs to allocate extents, update the data dictionary for the index definition also have to be applied, each of these also having to read the existing extent maps and data dictionary before updating them).
However, when you run media recovery
1. Oracle does not have to read the table
2. There is no sort operation
3. Writes to temp are avoided (as Temp operations are nologging and there is nothing in the redo to "replay" against the tempfiles)
4. The index blocks are "updated" directly

Standby media recovery waiting for inactive thread

Hi,
Please let me know any idea on this scenario. Thanks.
Environment:
Oracle 11.2.0.2
primary: 3 node RAC
standby: 3 node RAC
Problem:
there is thread 5 (not registered instance or did not show in srvctl) that generates archivelog. but the lag apply stopped because of this when the instance (of thread 5) is shutdown.
question: somehow an instance is registered in the cluster but in srvctl only 3 instance is running. it should have 4 instance but 1 is not running. How can I remove the thread 5 so when someone startup then shutdown instance#4 it will not create archivelog that will stopped the apply of archivelog in standby.
note: this is perf environment server so someone and "other" DBA is accessing this environment which I am not aware what are they doing with the cluster.
looking in alert log file: - it is waiting for thread 5 sequence 510. But the instance is down so log is not shipped to standby database and this resulted to lag in other threads.
Sat Aug 03 18:54:47 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
Media Recovery Waiting for thread 5 sequence 510
   THREAD# LAST_SEQ_RECEIVED LAST_SEQ_APPLIED
         1             13745            13717
         2             17728            17664
         3             15527            15464
         5               509              509
what I did is:
1. primary (asm copy to file system)
2. scp primary to standby
3. standby (file system copy to asm)
4. rman target / -> catalog archivelog <thread 5 sequence 510)
5. then looking into alert log file; it performed media recovery
Sat Aug 03 23:03:13 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
Media Recovery Waiting for thread 5 sequence 510
Sat Aug 03 23:15:21 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_5_seq_510
Sat Aug 03 23:15:32 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15466.10925.822316315
Sat Aug 03 23:17:18 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17666.853.822333143
Sat Aug 03 23:18:39 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15467.834.822333553
Sat Aug 03 23:20:54 2013

in Standby, thread 4 and 5 are both UNUSED, and size is incorrect (not equal to other redo log). I want to recreate it but cannot drop redo log. I follow Doc ID 740675.1.
any idea what are the missing steps? thanks.
ORA-01624: needed for crash recovery of instance UNNAMED_INSTANCE_5 (thread 5)
select group#,thread#,archived,status,bytes from v$log;
primary DB:
    GROUP#    THREAD# ARC STATUS                BYTES
         1          1 YES INACTIVE         1073741824
         2          1 YES INACTIVE         1073741824
         3          2 NO CURRENT          1073741824
         4          2 YES INACTIVE         1073741824
         5          3 YES INACTIVE         1073741824
         6          3 YES INACTIVE         1073741824
         7          2 YES INACTIVE         1073741824
         8          1 NO CURRENT          1073741824
         9          3 NO CURRENT          1073741824
        10          4 YES INACTIVE         1073741824
        11          4 NO CURRENT          1073741824
    GROUP#    THREAD# ARC STATUS                BYTES
        12          4 YES INACTIVE         1073741824
        13          5 YES INACTIVE         1073741824
        14          5 YES INACTIVE         1073741824
        15          5 NO CURRENT          1073741824
standby DB:
    GROUP#    THREAD# ARC STATUS                BYTES
         1          1 YES INACTIVE         1073741824
         2          1 YES INACTIVE         1073741824
         3          2 NO CURRENT          1073741824
         4          2 YES INACTIVE         1073741824
         5          3 YES INACTIVE         1073741824
         6          3 YES INACTIVE         1073741824
         7          2 YES INACTIVE         1073741824
         8          1 NO CURRENT          1073741824
         9          3 NO CURRENT          1073741824
        10          4 YES INACTIVE         1073741824
        11          4 NO CURRENT          1073741824
    GROUP#    THREAD# ARC STATUS                BYTES
        12          4 YES INACTIVE         1073741824
        13          5 YES INACTIVE         1073741824
        14          5 YES INACTIVE         1073741824
        15          5 NO CURRENT          1073741824

Block Media Recovery and RMAN Incremental Level 1 backup

Hi
I have read somewhere that Block Media Recovery will not work if a database is backed up using rman incremental 1. Is this true, and if so is there a work around?
I cannot seem to find this in oralce's documentation.
Regards
Me

Hi,
1) is Full Backup = Incremental level 0 backup?
Yes
2) When oralce say BMR does not work with incremental, will it work in the case I put forward. becuase Im doing an incremental 0...
But does you have the Archive logs available.. ?? If yes then it will Support.
3) Im my case will BMR work...that is use Incr level 0 on Sunday and then use archive logs for mon, tues etc
Yes, I believe.
@Hemanth .. am I right.. ?? Wait for your inputs...
- Pavan Kumar N

About Media Recovery

Hi,
I'm confused what will cause the Media Recovery. I found some documents said when the Checkpoint SCN in datafile does not equal to the SCN in control file will lead to Media Recovery, but some documents said it's caused by the difference of the Checkpoint Count. All the refered document are come from Oracle.
Besides, when the tablespace be online backup, the SCN in datafile and control file are frezed, but the Checkpoint Count in datafile is still changed. I'm not the checkpoint count in control file is also changed or not? But if shutdown database without ending the online backup, it will raise the ora-01113 error. Is it said the Checkpoint Count the judging condition?
Regards,
Edgar

Hi
. A recovery that SMON can perform entirely automatically is known as an instance recovery. One which requires manual intervention from the DBA is known as a media recovery.
A reasonable question to ask is, 'On what basis does SMON assess a database as being healthy or in need of recovery?'. To which the answer is: checkpoint change numbers. Periodically, the database is "timestamped" with a new sequence number (the latest number from a pool of ever-increasing sequence numbers). So long as every file in the database has been stamped with the same number, we can say that the database is 'consistent to that point of time'. If all the checkpoint change numbers that SMON reads during the database opening procedure, and which are stored in the headers of every physical file constituting the database, are the same, the database is healthy. If they are not all the same, and if there are no good reasons for the difference, the database is presumed to have suffered some sort of failure and a recovery procedure is therefore invoked.
CKPT (Checkpoint) is another reasonable question to then ask, 'What writes the checkpoint change number, which SMON reads, into the headers of each database file?'. To which the answer is, 'Another background process called Checkpoint, abbreviated as CKPT'. The occasions when CKPT writes its information into the headers of all database files are known as checkpoint events.
Every transaction that takes place on an Oracle database (that is, every insert, update or delete of a record) causes a system-wide sequence number called the System Change Number or SCN to be incremented. At a checkpoint event, the latest SCN is deemed to be the latest Checkpoint change number, and it is this CCN which is written by CKPT into the headers of all database files.
It is fair to say that, during prolonged database operation, CKPT will forever be writing new checkpoint change numbers into the headers of all the database files; it is SMON's job, at the opening of the database, to ensure that every constituent component of the database agrees on what the latest checkpoint change number should be. If they are all in agreement, the database opens. If there is disagreement, recovery is called for.
To make things even simpler: SMON reads what CKPT writes, and both processes are intimately involved in identifying when databases need recovery, and how much recovery they need, if any.
Govinda Krishna

Database Crash - Media Recovery Required - [SOLVED]

I am trying to understand why media recovery was required when our database had crashed ( this was 2 months ago ). This is just for my understanding and I would appreciate if you could explain it to me.
We have a 10g database on Solaris 10 and EMC SAN for storage. One of the technicians came in look at some electrical issue. And accidentally turned off the power supply to the SAN.
This caused the database instance to crash.
When the DBA tried to startup the database, he said that he was getting errors that some datafiles were corrupted and ruled that media recovery was required.
He took the backups taken 12 hours ago and applied the archived redo logs. Everything was fine except for the downtime ( it took 6 hours for this whole process).
I have several questions:
1. why would the datafiles get corrupted? was the disk in the process of writing and could not complete the task?
2. why did the database not do crash recovery i.e use redo logs? why did we have to use backup?
Thanks.
Message was edited by:
sayeed

1. why would the datafiles get corrupted? was the
disk in the process of writing and could not complete
the task?This could happen if a datafile being accessed during the power failure resulting in corrupting the file which can happen to any file during power failure..In this case it was datafile resulting in dataabse crash...
2. why did the database not do crash recovery i.e
use redo logs? why did we have to use backup?Since the file is corrupted you need to replace it with a last backup and apply logs to bring it consistent state....
Again ..This is what i have understood so far
correct me if i am wrong

ARC0: media recovery disabled

In the Alert log file, I found this message "ARC0: media recovery disabled". Please share with us, if you know how to resolve it.

Hi,
>>In the Alert log file, I found this message "ARC0: media recovery disabled". Please share with us, if you know how to resolve it.
This happens when a database running in NOARCHIVELOG mode is started with the parameter LOG_ARCHIVE_START=TRUE. IF your intention is to have database in NOARCHIVELOG mode then do not start an archive process on startup:
set LOG_ARCHIVE_START=FALSE
For more information, take a look at Note:304974.1 from Oracle Metalink
Cheers
Legatti

Media Recovery

Similar Messages

Maybe you are looking for