Apply archive logs to database

I have a production database that is online. I'm planning to setup a pc with the same configurations as that of the db server and use that server as the reporting generation. The clone pc's database will be one day delay compared to the production database. I'm planning to use export/import but someone suggested to use the archive log files of the production database and apply it to the clone pc, is this doable?
I have a full export backup and all the archive log of the production database, is this enough to restore the clone pc to the state( one day back) of the production database?
Need your suggestions. Thanks

You can do this while configuring physical standby database.
go through the link below to know more about physical standby
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm
regards

Similar Messages

Could u tell me last applyed archive log in disaster recovery server

Hi DBA'S,
we are using oracle 9.2.0.8 my production database has dr(our dr is not a stand by it is created in diff way) server every time one cron job sync the database and transfer the new logs from production server to dr server. i want to know last applied archive in dr server.
i am using this query select max(sequence#) from v$log_history; it is showing same results in boath production and dr when ever we backup 2 days before archive to some backup directory sync is going to fail
please tell me correct query to find out the last applied archived log in dr server
Thanks&Regards
Tirupathi

we are using oracle 9.2.0.8 my production database has dr(our dr is not a stand by it is created in diff way) server every time one cron job sync the database and transfer the new logs from production server to dr server. i want to know last applied archive in dr server.i am using this query select max(sequence#) from v$log_history; it is showing same results in boath production and dr when ever we backup 2 days before archive to some backup directory sync is going to fail
please tell me correct query to find out the last applied archived log in dr server>
As you are running cron job to bring the dr in sync, i suppose v$log_history might give you the wrong results.In your case check :-
select sequence#,applied from v$archived_log where applied='YES';
select max(sequence#) from v$archived_log where applied='YES';Would like to know, why manual recovery (archive logs being manually applied) is being performed, and not automatic.
In case you switch to automatic below query would be useful :-
select al.thrd "Thread", almax "Last Seq Received", lhmax "Last Seq Applied"
    from (select thread# thrd, max(sequence#) almax
            from v$archived_log
           where resetlogs_change#=(select resetlogs_change# from v$database)
           group by thread#) al,
         (select thread# thrd, max(sequence#) lhmax
           from v$log_history
            where first_time=(select max(first_time) from v$log_history)
           group by thread#) lh
          where al.thrd = lh.thrd;Refer [http://aprakash.wordpress.com/2010/07/21/use-of-varchived_log-and-vlog_history-on-physical-standby/]
HTH
Anand

New standby not applying archive log

I have just created standby database....but its not applying archive log...
when I checked the alerlog file of standby....
ora-19527 physical standby redo log must be renamed

yes, I have created at onlien redo logs at standby database..
what is test and test?
i saw one command like this...
log_file_name_convert= ((''/u01/oradata/prod'', ''/u01/oradata/standby''),(''/u02/oradata/prod'', ''/u02/oradata/standby''))
My Primary DB name is OraclePM
My Standby DB name is OracleDR
I have placed all redo logs in direcrtory (D:\oracle\product\logs\ ) the directory structure for both databases is same... I have created 3 additionals redo logs at standby database...
How can I edit my standby init file...

Is there a way to apply archive logs, standby DB is opened with 'resetlogs'

Hi All,
I have setup a standby database (Oracle 10g SE). I applied hot backup and archive logs to the standby database till yesterday. I have opened the standby database using 'alter database open resetlogs;" and validated the application functionality using the standby database.
Now I want to regularly apply logs from the Primary database to the standby database, but today I have opened the standby database using 'alter database open resetlogs;"
Need assistance to know the way to apply archive logs, once the standby database is opened with 'resetlogs' option to keep it in sync with the Primary database.
Thanks
Kunal

Welcome to OTN,
I have setup a standby database (Oracle 10g SE). I applied hot backup and archive logs to the standby database till yesterday. I have opened the standby database using 'alter database open resetlogs;" and validated the application functionality using the standby database.Standby opened with *resetlogs* ? What you did? have you performed failover of standby database?
Now I want to regularly apply logs from the Primary database to the standby database, but today I have opened the standby database using 'alter database open resetlogs;"
Need assistance to know the way to apply archive logs, once the standby database is opened with 'resetlogs' option to keep it in sync with the Primary database.Have you enabled Flashback & created Restore point? If so you can do it.. If not rebuild standby again.
Check this scenario How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]

Delete only applied archive logs

Hi,
I am new to RMAN. What is the command to delete all applied archive logs using RMAN in 11g Release2 ?
Thx

Hi,
What is your os ?
If it s linux/unix then try this shell script.
#!/bin/bash
ALERT=/oracle/app/oracle/diag/rdbms/dgbrm/dgbrm/trace/alert_dgbrm.log
tail -30000 $ALERT | grep "Media Recovery Log" | cut -d " " -f 4 | head --lines=-2 > files.txt
awk '{ system( "rm -rf " $_ ) }' files.txt
source: http://emrebaransel.blogspot.in/2009/03/delete-applied-archivelogs-on-standby.html
Thanks,
Ranjith

Manually apply archived log to standby database.

Hi all,
I am working on oracle 10g EE(10.2.0.4).I am having a very difficult database switchover case in my hand.
1.> There are two database .one primary(prim) and another standby(standby).
2.> Initially both of them was configured as oracle data guard, where prim was primary and standby was standby using rman .(RMAN>duplicate target database for
standby dorecover).
3.>But the rate of generation of archivelog is very high( 20 archivelog per hour with 200mb each).
4.> So automatic shipping of archivelog has been disabled from primary.(log_archive_dest_state_2=defer and nullifying the value of log_archive_dest_2).
5> Now after a period of time archived logs are shipped to dr site manually and applied manually.(alter database recover automatic standby database;)
6.> Now there is a hardware problem occured at primary..it will take 72 hours to come up.
How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
Is it possible to switchover and switch back these two database with such a configuration?

How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
Is it possible to switchover and switch back these two database with such a configuration?
As of now you can perform failover your standby to primary database. you should have flashaback enabled, so you have to create a restore point.
Then it can be opened in read & write mode, So once you finished again you can go back to that point.
http://docs.oracle.com/cd/B19306_01/server.102/b14239/manage_ps.htm#i1017111
The above case applicable if you ready to loose, But it doesnt make sense. But in your case this doesnt work. Because once you start use of Standby as primary, there would be live/production data, which you need very much.
So there is lot of work to do.
You have to rebuild standby database and then switchover back to same location. So its a little trip work.
Have you enabled Dataguard Broker ?
Edited by: CKPT on Mar 13, 2012 1:43 PM

Manually Apply Archived log to stand by database

Hi all,
I'm using Oracle 10g. So, we need to apply the archived logs of Primary database to stand by database, but this process must be manually.
A "robot" copy the archived logs to destination. I need to get these archived logs from destination and manually apply to stand by database.
How can I do this?
thank you very much!!!!

How can I do this?First stop current recover process as
alter database recover managed standby database cancel;Then transfer all need archive logs from primary to standby side and apply these manually using below command.
recover standby database until cancel
/*this command will ask full path of archive logs
and give these then finally enter "CANCEL" word*/Finally you can continue normal/automatic state using
alter database recover managed standby database ;

RMAN: How to apply Archive Logs after recoverying of all physical files

Hi;
I am using RMAN Oracle10g; my test database has being corrupted. I have already taken 0 level backup through this command
run {
allocate channel c1 type disk;
backup incremental level 0 tag = Test_Weekly_database format 'O:\rman\backup\Full_Weekly_%d_%s_%p_%t'(database);
release channel c1;
configure controlfile autobackup format for device type disk to 'O:\rman\backup\Auto_Ctrl_weekly_%F';
allocate channel c1 type disk;
sql 'alter system archive log current';
BACKUP tag = Test_Weekly_Arch ARCHIVELOG UNTIL TIME 'SYSDATE-7' format 'O:\rman\backup\Archive_weekly_%d_%s_%p_%t';
DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
release channel c1;
After backing up I inserted few records in TEST123 table. And switch current log file.
Then my database has been corrupted. Now I have last 0 level backup (RMAN) and archive logs files on OS level.
I am recovering my database with the following commands; but archive logs have not being applied. And my inserted records were not presented in TEST123 table.
Kindly guide me
SQL> startup nomount
CMD> RMAN target=/
RMAN>set DBID 1168995671
RMAN>RUN {
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
RESTORE CONTROLFILE from autobackup;
RMAN> ALTER DATABASE MOUNT;
RMAN> RESTORE DATABASE CHECK READONLY;
RMAN> RECOVER DATABASE NOREDO;
RMAN> restore archivelog all;
SQL> startup mount
SQL> alter database backup controlfile to trace;
SQL> shut immediate
SQL> startup nomount
SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG................;
SQL> alter database open resetlogs
---Database altered.
SQL> select * from TEST123;
Not record found
regards;
Asim

Dear Khurram;
Kindly advise where i m worrg???????
C:\>RMAN target=/
RMAN> set DBID 1168995671
executing command: SET DBID
RMAN> RUN {
2> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
3> RESTORE CONTROLFILE from autobackup;
4> }
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
Starting restore at 27-DEC-07
using channel ORA_DISK_1
recovery area destination: O:\rman\backup
database name (or database unique name) used for search: ORCL
channel ORA_DISK_1: no autobackups found in the recovery area
channel ORA_DISK_1: looking for autobackup on day: 20071227
channel ORA_DISK_1: autobackup found: O:\rman\backup\Auto_Ctrl_weekly_c-11689956
71-20071227-04
channel ORA_DISK_1: control file restore from autobackup complete
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
Finished restore at 27-DEC-07
RMAN> ALTER DATABASE MOUNT;
database mounted
released channel: ORA_DISK_1
RMAN> RESTORE DATABASE CHECK READONLY;
Starting restore at 27-DEC-07
Starting implicit crosscheck backup at 27-DEC-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=155 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=154 devtype=DISK
Crosschecked 9 objects
Finished implicit crosscheck backup at 27-DEC-07
Starting implicit crosscheck copy at 27-DEC-07
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 27-DEC-07
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
restoring datafile 00005 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST.DBF
restoring datafile 00006 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST2
channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_
1_642420573
channel ORA_DISK_1: restored backup piece 1
piece handle=O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_1_642420573 tag=Test_WEEKLY_DATAB
ASE
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
Finished restore at 27-DEC-07
RMAN> restore archivelog all;
archive log thread 1 sequence 1 is already on disk as file O:\ARCHIVE\ARC00001_0642356125.001
archive log thread 1 sequence 2 is already on disk as file O:\ARCHIVE\ARC00002_0642356125.001
archive log thread 1 sequence 3 is already on disk as file O:\ARCHIVE\ARC00003_0642356125.001
archive log thread 1 sequence 4 is already on disk as file O:\ARCHIVE\ARC00004_0642356125.001
archive log thread 1 sequence 5 is already on disk as file O:\ARCHIVE\ARC00005_0642356125.001
archive log thread 1 sequence 6 is already on disk as file O:\ARCHIVE\ARC00006_0642356125.001
archive log thread 1 sequence 7 is already on disk as file O:\ARCHIVE\ARC00007_0642356125.001
archive log thread 1 sequence 8 is already on disk as file O:\ARCHIVE\ARC00008_0642356125.001
archive log thread 1 sequence 9 is already on disk as file O:\ARCHIVE\ARC00009_0642356125.001
archive log thread 1 sequence 10 is already on disk as file O:\ARCHIVE\ARC00010_0642356125.001
archive log thread 1 sequence 11 is already on disk as file O:\ARCHIVE\ARC00011_0642356125.001
archive log thread 1 sequence 12 is already on disk as file O:\ARCHIVE\ARC00012_0642356125.001
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=15
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=16
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=17
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=18
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=19
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=20
channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630
channel ORA_DISK_1: restored backup piece 1
piece handle=O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630 tag=Test_WEEKLY_ARCH
channel ORA_DISK_1: restore complete, elapsed time: 00:00:08
Finished restore at 27-DEC-07
RMAN> ALTER DATABASE OPEN;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 12/27/2007 10:27:10
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
Regards;
Asim

How to apply archive in Standby Database?

Hello,
My Database are running in linux plateform. I am seeing that archives which are generating are not copying to standby server & not applying.
Can anybody suggest me how to copy archive from primary database(ASM file system) to standby Database & apply those archives?
Thanks

Hi,
I am having similar problem. The primary logs are shipping on to standby but are not getting applied.
Here are the outputs:
From primary
SQL > select thread#,max(sequence#) from v$archived_log where archived='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
1 27908
2 28476
3 31643
select max(sequence#) from gv$archived_log;
MAX(SEQUENCE#)
31643
From Standby
SQL > select thread#,max(sequence#) from v$archived_log where applied ='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
1 26862
2 27580
3 30874
select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
31643
Any help is appreciated.
Thanks in advance.

Purge archive logs standby database

How can I purge automaticly the archives logs in the standby database?
I have oracle versión 11.2.0.2 with +ASM in solaris.
Thanks.

My bad.
Will update my notes.
This is still there :
Applied Archivelogs Are Not Deleted On Physical Standby Site from Flash Recovery Area [ID 404338.1]
Since you have your DELETION POLICY set correctly you can also run something like this on the Standby :
run {
allocate channel for maintenance device type disk;
delete archivelog until time 'sysdate -5';
}Best Regards
mseberg
Edited by: mseberg on Aug 16, 2012 4:36 AM

Dataguard sync and applying archive log

Just did a check on my primary and standby using:
Primary:
SELECT max(sequence#) AS "PRIMARY" FROM v$log_history;
PRIMARY
45527
Standby:
SELECT max(sequence#) AS "STANDBY", applied FROM v$archived_log GROUP BY applied:
STANDBY APP
45476 NO
45528 YES
My question is how do I fix my sync?

SQL> select OPEN_MODE from v$database;
OPEN_MODE
MOUNTED
SQL> recover standby database until cancel;
ORA-01153: an incompatible media recovery is active
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> recover standby database until cancel;
ORA-00279: change 4558008 generated at 08/21/2010 14:02:39 needed for thread 1
ORA-00289: suggestion : /data_gpfs/oracle/archivelogs/1_112_726952005.dbf
ORA-00280: change 4558008 for thread 1 is in sequence #112
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
*/data_gpfs/oracle/archivelogs/2_118_726952005.dbf*
ORA-00325: archived log for thread 1, wrong thread # 2 in header
ORA-00334: archived log: '/data_gpfs/oracle/archivelogs/2_118_726952005.dbf'

Applying Archive logs after restore by RMAN

We user RMAN for our backup. I wanted to restore the database and apply all the archive logs.
After I use
RMAN> Restore database ( from last night backup)
RMAN> Recover database
And now I want to apply all the archive logs from which were generated from last night backup say 11:00 pm till 10:00 am today morning.
How can I apply the archive logs.
Thanks

I have the RMAN backup on tape , and I have the archive logs on the disk , as the archive logs would be backed up only the following night.
i.e i want to restore a 10th night backup , and apply the logs from 10th night 11:00 pm to 10:00 am 11th morning. As the archive logs would still be on the disk , how can I apply them..
Thanks

Applying transaction log corrupted database?

Hi experts,
Symptoms:
I built a standby system this Monday and I completed a full DB restore without errors. I used log shipping to apply logs but an error occurred: SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 20:5746350; actual 0:0). It occurred during a read of page (20:5746350) in database ID 5 at offset 0x00000af5d5c000 in file 'l:\TCPDATA4\TCPDATA19.ndf'.
I run dbcc page and found page(20:5746350) did corrupt on standby system. However, I ran dbcc page on production and it is ok. I restored this full db to another standby and ran dbcc page and it is ok. Also, Checkalloc, Checkcatalog, Checktable on production are ok.
Questions:
Does checktable detect secondary indexes corruption? I am re-compressing COSP indexes and running full checkdb on production right now to find out what's going on in our DB. How do I fix this issue? Any information will be really appreciated.
Error message:
2011-08-23 17:26:00.19 spid52      The log shipping secondary database TCCDBM1.TCP has restore threshold of 45 minutes and is out of sync. No restore was performed for 1 minutes. Restored latency is 720 minutes. Check agent log and logshipping monitor information.
2011-08-23 17:26:39.62 Backup      Log was restored. Database: TCP, creation date(time): 2011/07/03(05:36:16), first LSN: 184193:4075900:1, last LSN: 184193:7288500:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'w:\LogB\TCP_20110822213010.trn'}). This is an informational message. No user action is required.
2011-08-23 17:28:00.88 spid52      Error: 14421, Severity: 16, State: 1.
2011-08-23 17:28:00.88 spid52      The log shipping secondary database TCCDBM1.TCP has restore threshold of 45 minutes and is out of sync. No restore was performed for 2 minutes. Restored latency is 716 minutes. Check agent log and logshipping monitor information.
2011-08-23 17:28:34.03 Backup      Log was restored. Database: TCP, creation date(time): 2011/07/03(05:36:16), first LSN: 184193:7288500:1, last LSN: 184193:10880343:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'w:\LogB\TCP_20110822213511.trn'}). This is an informational message. No user action is required.
2011-08-23 17:28:53.06 spid65      Error: 824, Severity: 16, State: 2.
2011-08-23 17:28:53.06 spid65      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 20:5746350; actual 0:0). It occurred during a read of page (20:5746350) in database ID 5 at offset 0x00000af5d5c000 in file 'l:\TCPDATA4\TCPDATA19.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2011-08-23 17:30:00.54 spid52      Error: 14421, Severity: 16, State: 1.
2011-08-23 17:30:00.54 spid52      The log shipping secondary database TCCDBM1.TCP has restore threshold of 45 minutes and is out of sync. No restore was performed for 2 minutes. Restored latency is 713 minutes. Check agent log and logshipping monitor information.
2011-08-23 17:30:35.94 spid53      Error: 824, Severity: 16, State: 2.

Hi Dennis!
I understand your reasonable doubt, but think that physical corruptions are 99,999...% caused by a hardware failure e.g. a defective RAM module, or a related, low-level failure as e.g. an outdated NIC driver, etc.
Then, in this case it is clear that you have a platform problem only on your standby system, and not in the one running productively right now.
Maybe you already checked your platform, but you should take into account that in most cases just reading the logs is not enough; stress tests on all of the components are usually necessary. Most of the time, when we analyze hardware related problems, the problem is only reproduced when special tests are performed. Furthermore it is possible that more than one component is weak or broken.
My recommendation is that you check the components in this order:
   - disks (complete surface) (while SAP and SQL Server are shut down)
   - disk controller
   - Memory (stress test)
   - CPU
   - all other components
Consider that restoring a backup and running in a damaged platform would imply further problems. You would be waiting until the next problem arises and that would imply a system halt or corruptions, maybe even with data loss.
Once the hardware checked and -if necessary- fixed, you can proceed as explained in SAP notes 142731 and 1420452. Of course you can also restore in a different hardware, but remember checking the platform as it is also exposed to hardware failures.
Cheers!!
--Jesú

Applied archived log

Hi,
on 11g R2 dataguard,
on Primary I have :
SQL> select MAX(SEQUENCE#), THREAD# from gv$log where status='CURRENT'
group by THREAD#
order by THREAD# asc;
2    3
MAX(SEQUENCE#)    THREAD#
        700602          1
        259893          2
        261564          3
        259332          4On standby :
SQL> select MAX(SEQUENCE#), THREAD# from gv$log where status='CURRENT'
group by THREAD#
order by THREAD# asc;
2    3
MAX(SEQUENCE#)    THREAD#
        700602          1
        259893          2
        261564          3
        259331          4Then very small gap (only one sequence of thread 4.
But whith the following query on standby :
select THREAD#,SEQUENCE#,to_char(completion_time,'DD-MM-YYYY HH24:MI:SS' ),applied from v$archived_log where to_char(completion_time,'DD-MM-YYYY HH24:MI:SS' ) like '%14-08-2012%'and applied='NO' and THREAD#=4;
   THREAD# SEQUENCE# TO_CHAR(COMPLETION_ APPLIED
         4     259325 14-08-2012 15:14:57 NO
         4     259327 14-08-2012 15:15:12 NO
         4     259326 14-08-2012 15:15:19 NO
         4     259328 14-08-2012 15:17:56 NO
         4     259329 14-08-2012 15:18:01 NO
         4     259330 14-08-2012 15:20:36 NO
         4     259331 14-08-2012 15:20:56 NO
260 rows selected.Can any one be kind to tell me why 260 rows from this query as not applied ?
Thank you.

thank you.
here they are :
SQL> select * from v$archive_gap;
no rows selected
SQL> select THREAD#,SEQUENCE#,to_char(completion_time,'DD-MM-YYYY HH24:MI:SS' ),applied from v$archived_log where to_char(completion_time,'DD-MM-YYYY HH24:MI:SS' ) lik        e '%16-08-2012%'and applied='NO';
   THREAD# SEQUENCE# TO_CHAR(COMPLETION_ APPLIED
         3     136579 16-08-2012 10:11:05 NO
         1     137179 16-08-2012 10:11:05 NO
         4     354265 16-08-2012 10:11:06 NO
select PROCESS, STATUS, GROUP#, THREAD#, SEQUENCE#, BLOCK#, BLOCKS, DELAY_MINS from
         v$managed_standby where PROCESS like 'MR%';
PROCESS   STATUS       GROUP#                                      THREAD# SEQUENCE#     BLOCK#     BLOCKS DELAY_MINS
MRP0      WAIT_FOR_LOG N/A                                               3     136580          0          0          0

Recover database from archive log: Time based recovery

Hi,
Could you pelase help regarding the following:
I have power outage in my machine running oracle 9i on Solaris OS 9
Oracle is mounted but failed to open
Once it is started showing the error message
SQL> startup;
ORACLE instance started.
Total System Global Area 9457089744 bytes
Fixed Size 744656 bytes
Variable Size 3154116608 bytes
Database Buffers 6291456000 bytes
Redo Buffers 10772480 bytes
Database mounted.
ORA-01113: file 4 needs media recovery
ORA-01110: data file 4: '/opt/oracle/oradata/sysdb/indx/indx01.dbf'
So I tried to recover the database
SQL> recover database;
ORA-00279: change 1652948240 generated at 12/03/2007 13:09:08 needed for thread
1
ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183942.dbf
ORA-00280: change 1652948240 for thread 1 is in sequence #183942
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 1652948816 generated at 12/03/2007 13:09:19 needed for thread
1
ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183943.dbf
ORA-00280: change 1652948816 for thread 1 is in sequence #183943
ORA-00278: log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' no
longer needed for this recovery
The power outage at 16:00pm and the recovery archive log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' at 11 am
Always I am applying the next sequence it is giving the same message and asking the next sequence. I have more than 900 archive log from 11am to 4pm and each of them having the size of 100mb and it take 1 minute to get back from each to provide this error message.
How I can start my recovery from say 15:45 onwards until 16:15?
I have all archive logs in the proper destination.
Still my database is not opened and it is starts applying archive log since 5 hours back, please help me regarding this
Thanks in advance

Wrong forum. Post your question in the following forum:
General Database Discussions

Apply archive logs to database

Similar Messages

Maybe you are looking for