Recovery process applies old archivelogs on standby database
Right now my standby database is in sync with my primary database and is waiting for the archived log sequeuence# 8378 to arrive.
But when I stop the recovery process (alter database recover managed standby database cancel;) and re-start it (alter database recover managed standby database disconnect), it starts all over again and starts applying archive logs starting from the sequence# 5739 (looks like its scanning thru the logs). To catchup with primary it takes 2+ hours as it need to skim thru all the logs starting from 5739 to 8377.
Please let me know if you need any further information to fix this.
Thank you
Sunny boy
Details:
Database version: 11.2.0.3
OS : RHEL 5
On Standby Database
SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
FROM V$LOG_HISTORY
GROUP BY THREAD#; 2 3
THREAD# LAST_APPLIED_LOG
1 8377
Alert log
alter database recover managed standby database disconnect
Attempt to start background Managed Standby Recovery process (MNODWDR)
Tue May 08 16:13:09 2012
MRP0 started with pid=28, OS id=26150
MRP0: Background Managed Standby Recovery process started (MNODWDR)
started logmerger process
Tue May 08 16:13:15 2012
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 8 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Completed: alter database recover managed standby database disconnect
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/arch/mnodw_1_5739_765032423.arc
Tue May 08 16:13:48 2012
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5740.1466.781015749
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5741.1468.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5742.1474.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5743.1473.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5744.1477.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5745.1478.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5746.1472.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5747.1475.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5748.1469.781017203
Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5749.1470.781017203
Tue May 08 16:13:57 2012
Edited by: Sunny boy on May 8, 2012 5:29 PM
Hello;
V$LOG_HISTORY is the information from the control file. I would use a different query to check :
From the Primary :
SET PAGESIZE 140
COL DB_NAME FORMAT A10
COL HOSTNAME FORMAT A14
COL LOG_ARCHIVED FORMAT 999999
COL LOG_APPLIED FORMAT 999999
COL LOG_GAP FORMAT 9999
COL APPLIED_TIME FORMAT A14
SELECT
DB_NAME, HOSTNAME, LOG_ARCHIVED, LOG_APPLIED, APPLIED_TIME, LOG_ARCHIVED-LOG_APPLIED LOG_GAP
FROM
( SELECT
NAME DB_NAME
FROM
V$DATABASE
SELECT
UPPER(SUBSTR(HOST_NAME,1,(DECODE(INSTR(HOST_NAME,'.'),0,LENGTH(HOST_NAME), (INSTR(HOST_NAME,'.')-1))))) HOSTNAME
FROM
V$INSTANCE
SELECT
MAX(SEQUENCE#) LOG_ARCHIVED
FROM
V$ARCHIVED_LOG
WHERE
DEST_ID=1
AND
ARCHIVED='YES'
SELECT
MAX(SEQUENCE#) LOG_APPLIED
FROM
V$ARCHIVED_LOG
WHERE
DEST_ID=2
AND
APPLIED='YES'
SELECT
TO_CHAR(MAX(COMPLETION_TIME),'DD-MON/HH24:MI') APPLIED_TIME
FROM
V$ARCHIVED_LOG
WHERE
DEST_ID=2
AND
APPLIED='YES'
);Change DEST_ID as needed for your system. I would also bump the parameter LOG_ARCHIVE_MAX_PROCESSES assuming its set to default to a higher value up to 30.
Maybe instead of stopping the recovery process you should DEFER on the Primary
alter system set log_archive_dest_state_2=defer;Change the _n from 2 to what your system requires. I use this and have watch DG catch up 200 archives in about 15 minutes.
You have Standby Redo setup and are using the same size as your redo right?
Have never seen the Standby try to apply twice.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1] ( But I do not see your issue )
Metalink Note 241438.1 Script to Collect Data Guard Physical Standby Diagnostic Information
Metalink Note 241374.1 Script to Collect Data Guard Primary Site Diagnostic Information
Best Regards
mseberg
Edited by: mseberg on May 8, 2012 5:16 PM
Similar Messages
-
What are the steps applying incremental backups to standby database 11g
Hi All,
I have built 11g none ASM standby database from ASM RAC Database. Now I want to apply incremental backup to the standby database from primary but not sure how to do it. I tried following and I had an error “ORA-01103: database name 'ins-prim' in control file is not 'ins-sec'”
1- I have configured standby database with RMAN backup.
2- After finishing installation, I took a incremental backup from primary server(ins-prim) and moved incremental backup and control file to the standby (ins-sec) database
3- I stared standby database nomount mode
4- restore controlfile from “incremental backup location in standby database”
5- alter database mount; and got this error
“ORA-01103: database name 'ins-prim' in control file is not 'ins-sec'”
What are the steps applying incremental backups to standby database with 11g?
Thank youI build the database from backup and changed from ASM to none ASM and changed location of data files and logfiles. I think this changes makes the standby database as logical one.
You can a have a physical standby with different locations for everything (redo/controlfiles/datafiles), ASM and no ASM etc. I have a such a configuration in production (10gR2)
I build the database from backup
Are you sure you have a standby ? Ins-sec receives the archivelog files from the primary ? How did you proceed to build this database ? I suspect you don't have a standby at all ! If you have duplicated the database ins-sec and ins-pri are independent databases and you won't be able to apply an incremental backup (your script was not correct but it is another story) -
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 -
Hi Friends,
I am getting the following exception in logical standby database at the time of Sql Apply.
After run the command alter database start logical standby apply sql apply services start but after few second automatically stop and getting following exception.
alter database start logical standby apply
Tue May 17 06:42:00 2011
No optional part
Attempt to start background Logical Standby process
LOGSTDBY Parameter: MAX_SERVERS = 20
LOGSTDBY Parameter: MAX_SGA = 100
LOGSTDBY Parameter: APPLY_SERVERS = 10
LSP0 started with pid=30, OS id=4988
Tue May 17 06:42:00 2011
Completed: alter database start logical standby apply
Tue May 17 06:42:00 2011
LOGSTDBY status: ORA-16111: log mining and apply setting up
Tue May 17 06:42:00 2011
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 4, Transaction Chunk Size = 201
LOGMINER: Memory Size = 100M, Checkpoint interval = 500M
Tue May 17 06:42:00 2011
LOGMINER: krvxpsr summary for session# = 1
LOGMINER: StartScn: 0 (0x0000.00000000)
LOGMINER: EndScn: 0 (0x0000.00000000)
LOGMINER: HighConsumedScn: 2660033 (0x0000.002896c1)
LOGMINER: session_flag 0x1
LOGMINER: session# = 1, preparer process P002 started with pid=35 OS id=4244
LOGSTDBY Apply process P014 started with pid=47 OS id=5456
LOGSTDBY Apply process P010 started with pid=43 OS id=6484
LOGMINER: session# = 1, reader process P000 started with pid=33 OS id=4732
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1417, X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Turning ON Log Auto Delete
Tue May 17 06:42:01 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1418, X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
LOGSTDBY Apply process P008 started with pid=41 OS id=4740
LOGSTDBY Apply process P013 started with pid=46 OS id=7864
LOGSTDBY Apply process P006 started with pid=39 OS id=5500
LOGMINER: session# = 1, builder process P001 started with pid=34 OS id=4796
Tue May 17 06:42:02 2011
LOGMINER: skipped redo. Thread 1, RBA 0x00058a.00000950.0010, nCV 6
LOGMINER: op 4.1 (Control File)
Tue May 17 06:42:02 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1419, X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1420, X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1421, X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Analyzer process P004 started with pid=37 OS id=5096
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Apply process P007 started with pid=40 OS id=2760
Tue May 17 06:42:03 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY Apply process P012 started with pid=45 OS id=7152
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1422, X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1423, X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1424, X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
LOGMINER: session# = 1, preparer process P003 started with pid=36 OS id=5468
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
Tue May 17 06:42:04 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1425, X:\TANVI\ARCHIVE2\ARC01425_0748170313.001
LOGSTDBY Apply process P011 started with pid=44 OS id=6816
LOGSTDBY Apply process P005 started with pid=38 OS id=5792
LOGSTDBY Apply process P009 started with pid=42 OS id=752
Tue May 17 06:42:05 2011
krvxerpt: Errors detected in process 34, role builder.
Tue May 17 06:42:05 2011
krvxmrs: Leaving by exception: 600
Tue May 17 06:42:05 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY status: ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_lsp0_4988.trc:
ORA-12801: error signaled in parallel query server P001
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
LogMiner process death detected
Tue May 17 06:42:06 2011
logminer process death detected, exiting logical standby
LOGSTDBY Analyzer process P004 pid=37 OS id=5096 stopped
LOGSTDBY Apply process P010 pid=43 OS id=6484 stopped
LOGSTDBY Apply process P008 pid=41 OS id=4740 stopped
LOGSTDBY Apply process P012 pid=45 OS id=7152 stopped
LOGSTDBY Apply process P014 pid=47 OS id=5456 stopped
LOGSTDBY Apply process P005 pid=38 OS id=5792 stopped
LOGSTDBY Apply process P006 pid=39 OS id=5500 stopped
LOGSTDBY Apply process P007 pid=40 OS id=2760 stopped
LOGSTDBY Apply process P011 pid=44 OS id=6816 stopped
Tue May 17 06:42:10 2011Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []submit an SR to ORACLE SUPPORT.
refer these too
*ORA-600/ORA-7445 Error Look-up Tool [ID 153788.1]*
*Bug 6022014: ORA-600 [KRVXBPX20] ON LOGICAL STANDBY* -
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 -
Problem on archivelog for standby database
Hi,
I have an RAC architecture on linux in standard edition.
I build a standby database on an other server in standard edition.
I have build my standby database and open in read only but when i do some modifications in my rac i can't apply my archive logs because in
RAC i have the thread notion and the apply give me an error:
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/db/RSAPRODS/FRA/RSAPROD/archivelog/2011_03_30/thread_1_seq_166.354.747075275
ORA-00325: archived log for thread 2, wrong thread # 1 in header
ORA-00334: archived log:
I don't know how to do to generate an archive log for my standby.
Thanks$ oerr ora 325
00325, 00000, "archived log for thread %s, wrong thread # %s in header"
// *Cause: The archived log is corrupted or for another thread. Can not
// use the log for applying redo.
// *Action: Find correct archived log.Make sure you have transfered archived redo logs in binary mode if using ftp and that they are not corrupted : you can try to use cksum or md5sum on source archived redo log and on target archived redo log. -
Archivelog in standby database
Hai
i have some confusion regarding the archiving process in the primary database and the standby database.so log_archive_dest_2 ='service=stby' param copies the archive logfiles to the standby from the primary database.
at the same time will the changes in the redolog files in the primary database will be applied to the standby lofiles of the target database.
is it a correct method to copy the redolog files from the primary database to the standby database or its better to create the standby lofiles for the target database in the primary database and then copy it to the target database.wat method should be implemented?
if group numbers for primary database are assigned as group 1.group 2 and group 3 then how should i name the newly created standby redolog groups.can i name it as group 4.group 5 and group 6.can i follow this method?
Regards
orauser123i have some confusion regarding the archiving process in the primary database and the standby database.so log_archive_dest_2 ='service=stby' param copies the archive logfiles to the standby from the primary database.
at the same time will the changes in the redolog files in the primary database will be applied to the standby lofiles of the target database.
is it a correct method to copy the redolog files from the primary database to the standby database or its better to create the standby lofiles for the target database in the primary database and then copy it to the target database.wat method should be implemented?You can opt for any one of the two process. I would personally suggest you to do it by setting parameter log_archive_dest_2 ='service=stby' in this case log shipping will happen automatically. You need not worry about that.
if group numbers for primary database are assigned as group 1.group 2 and group 3 then how should i name the newly created standby redolog groups.can i name it as group 4.group 5 and group 6.can i follow this method?You can transfer a normal archive log generated at primary site, so far and register them with the standby database. After this you can apply and then delete them.
Rgds. -
Check actual apply log time on standby database after synchronization
Hi All,
I want to check the date and time stamp of applied archived logs on stanby database. How should I check that??
My dataguard link was broken for sometime and meanwhile lot of transactions happened on primary database. Now When the link came up the synchronisation happened within few hours and ultimatly transport and appliy lag became 0. But now I want to check actual time taken for tranporting the logs and applying them on standby database. Is there any way I could do that easily..
ThanksThis script written by Yousef Rifai I found here http://www.dba-village.com/village/dvp_forum.OpenThread?ThreadIdA=34772&DestinationA=RSS might be just what you need (run on standby database):
set ver off
alter session set nls_date_format='dd-mon-yy hh24:mi:ss'
select app_thread, seq_app, tm_applied,
nvl(seq_rcvd,seq_app) seq_rcvd, nvl(tm_rcvd,tm_applied) tm_rcvd
from
(select sequence# seq_app, FIRST_TIME tm_applied, thread# app_thread
from v$archived_log where applied = 'YES'
and (first_time, thread#) in (
select max(FIRST_TIME ), thread#
from v$archived_log where applied = 'YES'
group by thread# )
(select sequence# seq_rcvd, FIRST_TIME tm_rcvd, thread# rcvd_thread
from v$archived_log where applied = 'NO'
and (first_time, thread#) in (
select max(FIRST_TIME ), thread#
from v$archived_log where applied = 'NO'
group by thread# )
where rcvd_thread(+)= app_thread
Best regards,
Robert
http://robertvsoracle.blogspot.com -
How do I clone a database but still apply old archivelogs? Getting ORA-1223
Hi,
I'm doing a clone from PROD to DEV in 9.2.0.6 for 11.5.10.2 on Solaris 9. I worked through many issues, such as copying the files, changing the init<SID>.ora to the new DEV values, re-editing all of the env files with the new SID on the new (target) machine name, etc.
The data is about 2 weeks old and so I was hoping to not only recover this database during the clone, but ALSO roll forward, applying all of the old archive logs to date. (Nothing changed in the middle tier save for a few
paramaters in the xml file which I've already edited).
Normally when I'm cloning -- I do it with fresh/recent data files so I don't care about reseting the archivelogs, I just reset them and say si-a-nerra!
But.... now I am trying to both change the database name (SID) and apply a bunch of archvie logs (about 2 weeks worth). Note: I also recreate the control file as part of my whole process too.
Here's the problem I am having -- after doing a startup nomount in the new location (with my new environment files, data files, etc all in place) and
then doing @recreate.sql (which is the edited control file script from the 'backup controlfile to trace' on prod) I am getting this message:
SQL> @recreate.sql
CREATE CONTROLFILE SET DATABASE "DEV11i" NORESETLOGS
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01223: RESETLOGS must be specified to set a new database name
- well OK this message makes sense to me - yes I could easily just keep the new name and say RESETLOGS, but I don't want to do this !!! I want to set the new name for the clone, and keep the logs unset so that I can then recover until cancel, applying my 2 weeks worth of logs.
- What is the solution? Do I have to just bite the bullet and do RESETLOGS instead? (and in effect make my recovery practice seperate from my current cloning tasks)
- Or should I change everything back to the old (original name) LIVE11i (for Prod), including the env files, data files etc .. on the new (target) machine.., recover the database completely (maybe even disconnect it from the network and rename the (target) machine to the old prod server name), and then do another whole procedure (which I'd have to find - but I know it's similar) for changing the SID...
Please help. Thanks in advance! Marvin.
Message was edited by:
umfan866Oviwan,
Because of getting the error message, the recreate controlfile has not
gone through, thus I have not yet reset the logs.
What I'm going to do for now is in fact change the script to SET
the new name for DEV11i and RESET the logs, just to test my clone. The
data will be 2 weeks out of date, but I'll have verified that my files from tape
work (these files had come of the tape, and are now 2 weeks old).
To make the DB fresher, I can just re-clone with RESET using last night's
hot backup from PROD. That'll freshen DEV's files up no problem.
I had wanted to test all these archive logs and see if they apply nicely,
but I'll just have do that on a separate box (disconnected from the network)
where I keep the DB name and machine name the same as prod.
Thanks for your help! Marvin. -
Standby database recovery error
Dear All,
When Im trying to apply redologs for my standby database, the following error is coming up
ORA-00279: change 276067636 generated at 08/22/2010 05:03:25 needed for thread 1
ORA-00289: suggestion : /oracle/BWP/oraarch/BWParch1_30490_684267445.dbf
ORA-00280: change 276067636 for thread 1 is in sequence #30490
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 32769 change 276075175 time 08/22/2010 05:03:49
ORA-00334: archived log: '/oracle/BWP/oraarch/BWParch1_30490_684267445.dbf'
ORA-01112: media recovery not started
Could you please help out.
Thanks n Regards,
KKHi Stefan,
Oracle data guard is implemented by one of the expert on the same.
The following is result of the command you listed.
NAME TYPE VALUE
log_archive_dest string /oracle/BWP/oraarch/BWParch
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
NAME TYPE VALUE
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string defer
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
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
Thanks,
Anees -
Apply Patches on Oracle Database with Logical Standby Database
Here I am:
I got a primary database with a logical standby database running Oracle 11g. I got two client applications, one is the production site pointing to the primary one, another one is just a backup site pointing to the logical one.Things will only be written into the primary database every mid night and client applications can only query the database but not add, update nor delete.And now, I want to apply the latest patch on both of my databases. I am also the DNS administrator, I can make the name server pointing to the backup site instead of the production one.I want to firstly apply the patch on the logical one, and then the physical one.
I found some reference which explains how to apply patches by adopting "Rolling Upgrade Method". however, I want to avoid doing any "switch over" mentioned in the reference because I can make use of name server. Can I just apply patches as the following way?
1)Stop SQL apply
2)Apply patches on logical standby database
3)let the name server point to the backup site
4)Apply patches on the primary database
5)Start SQL apply
6)Let the name server point back to the production site
Thanks in advance.Pl follow the steps in MOS Doc 437276.1 ( Upgrading Oracle Database with a Logical Standby Database In Place )
HTH
Srini -
Physical Standby database Vs. Logical Standby database
I have few questions regarding capability of Logical Standby Database against Physical Standby database.
1. How efficient is Logical Standby database in terms of Physical Standby Database?? How both differ from each other and can I use Logical Standby Database for disaster Recovery?? Can It be use for recovering the failed Primary Instance?? If yes how efficient and reliable it is??
2. What are the known bugs and roadblocks for logical standby database on Oracle 10.2.0.1 on Soalris X86-64?
3.As logical standby database not going to replicate each and every schema of Primary database?? how is the change management effects to the logical standby from primary?? I mean there are some parameters and job that we create on primary how can it be transferred over to the logical standby??1. How efficient is Logical Standby database in terms
of Physical Standby Database?? How both differ from
each other and can I use Logical Standby Database for
disaster Recovery?? Can It be use for recovering the
failed Primary Instance?? If yes how efficient and
reliable it is??I'm not sure what sort of "efficiency" you're talking about here...
Physical standby is just the old, tried and true application of archived logs to recover a database. Very solid, very old school.
Logical standby, on the other hand, is parsing the redo log, extracting logical change records, and applying them to the standby database. This obviously takes a bit more processing effort, it's newer technology, it doesn't have quite the level of support that physical standby does (i.e. certain data types are excluded), etc. You certainly can use it for failover, but it isn't quite as robust as a physical standby. Of course, this is getting better and better all the time and is definitely a focus of Oracle's development efforts.
On the other hand, logical standby systems can do things other than act as a warm standby. They can be open serving reports, for example. You can create additional structures (i.e. new materialized views) to support reporting. A physical standby is pretty much always going to be in managed recovery mode, so it cannot be queried.
2. What are the known bugs and roadblocks for logical
standby database on Oracle 10.2.0.1 on Soalris
X86-64?a) You'll want to do a Metalink search
b) If you're talking about a high-availability solution, why are you looking at a base release of the database? Why wouldn't you apply the latest patchset?
3.As logical standby database not going to replicate
each and every schema of Primary database?? how is
the change management effects to the logical standby
from primary?? I mean there are some parameters and
job that we create on primary how can it be
transferred over to the logical standby??I'm not sure I understand... Changes made to the primary generate redo. Oracle parses that redo, generates a LCR, and sends that to the standby database where that change record gets applied.
Justin -
Hi All,
I have some doubts in Oracle Standby database configuration and log transfer and redo apply.
I have read the below document.
Oracle® Data Guard Concepts and Administration
Now my doubts are *(in Physical standby database with Maximum performance mode)*
1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?
Please Advice..
TIA,1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?It is not for role transition.
A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases.
You can recover more data than only applying archive logs in case of failure.
SRLs' are a must for real time apply.
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?The data is directly written from production to SRL of standby database using lgwr process(with the help of RFS), that is why it real time. Not waiting for a log switch. See the [diagram.|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1021537]
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?No. Only standby redo log will generate archived logs.
Regards,
S.K. -
Redologs in physical standby database
The MRP process is started and the standby database is physical standby, which is running under managed standby. My Question is as below
1. Under managed recovery mode do we require the redo logs created on the physical standby database.
2. How does oracle keep the database in sync when there are no redo logs are created on the standby database.The output is as below
SQL> select status, pid, sequence# from v$managed_standby where process like 'MRP%';
STATUS PID SEQUENCE#
WAIT_FOR_GAP 29710 88576
SQL>
The contents of alertlog ; i Just restarted the managed recovery to capture the information
RFS[1]: Archived Log: '/u02/archive/1_88817_665420030.dbf'
Sun Apr 18 18:34:26 2010
RFS[2]: No standby redo logfiles created
RFS[2]: Archived Log: '/u02/archive/1_88818_665420030.dbf'
Sun Apr 18 18:44:26 2010
RFS[3]: No standby redo logfiles created
RFS[3]: Archived Log: '/u02/archive/1_88819_665420030.dbf'
Sun Apr 18 18:54:26 2010
RFS[4]: No standby redo logfiles created
RFS[4]: Archived Log: '/u02/archive/1_88820_665420030.dbf'
Sun Apr 18 18:56:32 2010
alter database recover managed standby database cancel
Sun Apr 18 18:56:50 2010
MRP0: Background Media Recovery cancelled with status 16037
Sun Apr 18 18:56:50 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_29710.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Sun Apr 18 18:56:51 2010
Waiting for MRP0 pid 29710 to terminate
Sun Apr 18 18:56:51 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_29710.trc:
ORA-16037: user requested cancel of managed recovery operation
Sun Apr 18 18:56:51 2010
MRP0: Background Media Recovery process shutdown (rmdp3)
Sun Apr 18 18:56:52 2010
Managed Standby Recovery Canceled (rmdp3)
Completed: alter database recover managed standby database cancel
Sun Apr 18 18:57:19 2010
alter database recover managed standby database disconnect
from session
Sun Apr 18 18:57:19 2010
Attempt to start background Managed Standby Recovery process (rmdp3)
MRP0 started with pid=19, OS id=2123
Sun Apr 18 18:57:19 2010
MRP0: Background Managed Standby Recovery process started (rmdp3)
Managed Standby Recovery not using Real Time Apply
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /u03/redologs/rmdp3/redo01.log
Clearing online log 1 of thread 1 sequence number 88818
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Sun Apr 18 18:57:24 2010
Errors in file /opt/home/oracle/admin/rmdp3/bdump/rmdp3_mrp0_2123.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u03/redologs/rmdp3/redo01.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 88576
Fetching gap sequence in thread 1, gap sequence 88576-88675
FAL[client]: Error fetching gap sequence, no FAL server specified
Sun Apr 18 18:57:25 2010
Completed: alter database recover managed standby database disconnect
from session
Sun Apr 18 18:57:54 2010
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 88576-88675
DBID 440735188 branch 665420030
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Edited by: user11982297 on Apr 18, 2010 10:58 AM -
Basic standby database configuration in Oracle10g standard edition
Have anyone successfully implemented the technology in Oracle8i and earlier known as "Basic standby database" in Oracle10g SE? From the information, that I've been able to gather, this technology still exists in Oracle9i and later, along with Oracle Data Guard.
I'm not interested in the complete Data Guard environment - only the standby database feature as mentioned above. Basci
I've tried the documentation regarding the configuration of Data Guard (in lack off precise documentation on this technology) - but it's very confusing what's possible on SE an EE editions.
I've followed all the guidelines, enabled archive logging on primary database, created standby control file, copied the primary database files, created the pfile from the primary database - and then used this as the source for the spfile on the standby database.
I can then mount the standby database and start the recovery process with the following command:
alter database recover standby database disconnect;
The database is altered but no archive is applied (I've manually copied the archive logs from the primary). I've configured the standby_archive_dest - but the status for the MRP0 process keeps saying: WAITING_FOR_LOG
It seems like the "automatic" recovery mode doesn't work on SE. My conclusion is that you'll have to do everything manually - which means that I've have run the recover command manually - everytime I want to apply the archive logs from the primary.
Does anyone have a complete how-to-guide on this issue or have tried implementing in a real solution?Hi,
>>The database is altered but no archive is applied (I've manually copied the archive logs from the primary). I've configured the standby_archive_dest - but the status for the MRP0 process keeps saying: WAITING_FOR_LOG
because ur using standard edition and in this edition the archivelog will not automatically move to standby from primary database.so u have to automatically transfer and apply it.
Thanks
Kuljeet
Maybe you are looking for
-
Broken links on the web page :(
Hi Guys I have been chasing this for a few weeks now & no one seems very interested in the issues with the web site On this web page http://www.palm.com/au/support/treo680/downloads/680mr_win.html Their is a link Download: Treo680_2_12_ROW_desktopupd
-
System shuts down when grey screen and grey Apple logo appear
My system (G4 desktop from 2000) is old enough to not support 500 GB HD's natively. So I bought a Tempo controller card that fits into a PCI slot and have used it successfully with Tiger for the past 2 years. I upgraded to Leopard and found that I ca
-
Hi, I Want detailed information about the communication technology between the SAP Server and any SAP Front-end. Can anyone help me? Thanks... Regards. M G
-
i ask me because it sounds not really logic...
-
Hello to all, and thanks in advance for any help I may receive! I can truly say that my new 9630 Tour is the best cellphone I have ever had. It has "almost" replaced my home computer. What few problems I have, I am "learning" my way out of; except on