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
orauser123

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?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.

Similar Messages

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

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.

How to delete the foreign archivelogs in a Logical Standby database

How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?

OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923

How to delete archivelog with RMAN in the Primary and Standby database?

Hello,
I am working on Oracle 10gR2.
My question is :
How could I implement a automatized and secure way of:
1) Delete archivelogs on my PRIMARY server only when these logs are successfully TRANSFERED to all my standby databases?
2) Delete archivelogs on my STANDBY server only when these logs are sucessfully APPLIED to the database?
Thanks a lot for your help!

on 10G
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#CHDBEICE
Coskan Gundogar
http://coskan.wordpress.com

Manual Standby Database not in sync with missing archivelogs

Hello,
OS: Solaris
DB: Oracle 11.2.0.1 EE
Not Using ASM or RAC
I have a Production database that is in archivelog mode and a Standby DR server.
Both servers (Prod, Standby) have exact same structure and db name/version.
We manually scp archive logs and recover them to a manual standby database via SQL Scripts "cron". (I.E. set autorecovery on; recover standby database;)
We recently got out of sync with our log files and have not been applying them to the standby. As part of Prod Maintenance, these log files were deleted and are not available anymore.
I've tried several ways to "rebuild" our standby database. I have tried to Shutdown prod, backup all the db files and scp them to standby, re-create standby controlfile and startup mount and recover standby.
Every time I try to apply a new archive log via recover standby, these are the errors:
ORA-00279: change 211077622 generated at 1/27/2012 12:18:42 needed for thread 1
ORA-00289: suggestion : /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
ORA-00280: change 211077622 for thread 1 is in sequence #69486
ORA-00308: cannot open archived log '/oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-10879: error signaled in parallel recovery slave
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/oradevices/PROD/oraPRODsystem1.dbf'
When I check v$log_history, the new logs have not been applied.
I've also tried the "Restore from incremental backup via SCN" method with same results.
Is there a way to re-create the standby clean and ensure that the log chain that is currently broken gets fixed or reset?
I would eventually like to get DataGuard in here, but that's not the case at the moment.
Thanks for your suggestions.
-Dav

if you are using the cold backup to create the standby database, Check that have you followed the following steps or not.
1. remove
all the datafiles and controlfiles from the standby database.
2. Create a new standby controlfile of the production for standby using the following cmd
'alter database create standby controlfile as 'Location';'
3. move the new controlfile to standby database server location as specified in initialization parameter file.
4. Restore all the datafiles to its appropriate loaction which was taken through cold backup.
5. startup nomount
6. alter database mount standby database;
7. recover standby database.
scp the archive log sequence that is asked by the database, from production.
You can try this steps.

Forward physical standby archivelog files to a logical standby database

Hi,
We have a production database (1) and we have a physical standby database (2) for it.
Is it possible to forward the archivelogs files from (2) to a logical standby database (3). We want to use the (3) as a UAT - Ad Hoc read only Database.
Thanks.

Hi,
The following Data Guard configurations using cascaded destinations are supported.
A. Primary Database > Physical Standby Database with cascaded destination > Physical Standby Database
B. Primary Database > Physical Standby Database with cascaded destination > Logical Standby Database
A physical standby database can support a maximum of nine (30 as of Version 11.2) remote destinations.
Physical Standby Forwarding Redo to a Logical Standby :
Advantages :
1. Users can connect to Logical Standby database and they can access
2. Instead of querying primary database they can use logical standby database.
3. without any additional overhead on your primary system, and without consuming any additional transatlantic bandwidth.
Disadvantages :
The following data types will not support in Logical standby database just check your application before implementing logical standby
a. BFILE
b. Collections (including VARRAYS and nested tables)
c. Multimedia data types (including Spatial, Image, and Oracle Text)
d. ROWID, UROWID
e. User-defined types
f. LOBs stored as SecureFiles
g. XMLType stored as Object Relational
h. Binary XML
Thanks
LaserSoft

How to apply archivelog with gap on standby database

Hi All,
Oracle Database version : 9.2.0.6
Following is my sequence of commands on standby database.
SQL>alter database mount standby database;
SQL> RECOVER AUTOMATIC STANDBY DATABASE UNTIL CHANGE n;
ORA-00279: change 809120216 generated at 07/24/2006 09:55:03 needed for thread
1
ORA-00289: suggestion : D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC
ORA-00280: change 809120216 for thread 1 is in sequence #19921
ORA-00278: log file 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' no longer
needed for this recovery
ORA-00308: cannot open archived log
'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
I have check the last sequence# on standby database which is 19921. And I have archivelog starting from sequence# 20672 onwards. When I am trying to apply archive log starting from sequence# 20672 , it is searching for 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' file and cancel the recovery. Please note that I don't have those missing archive on Primary server as well. So How can I apply the remaining archive log which I do have from 20672 onwards.
I hope I am not creating any confusion.
Thx in advance.

Hi Aijaz,
Thx for your answer. But my scenario is bit complex. I have checked my standby database status which is not running in recovery mode. I have tried to find archive_gap which is 0 on standby server. I am copying all archived log from primary to standby thru the script every 2 hour and appying them on standby. After applying, the script is removing all applied log files from primary as well as standby. So it is something like I have archivelog from 1,2,3,7,8,9,10. So 4,5 and 6 archivelog are missing which is required when I am trying to recover standby database. Also note that I want to apply 7,8,9,10. I will loose some data from those missing archive but I have cold back any way. I don't have those missing archivelog files(4,5 and 6) anywhere at all. So how can I recover standby database. I am using standby just for the backup purpose.
I hope my question is clear now.
Thx in advance
- Mehul

Archivelog Source Directory in Standby Database

Hi Guys
I created a standby database yesterday and everything is working correctly. I need to make some tweaks, however, and one of those is the directory that the standby database expects the archivelogs to be.
I found that the archivelogs were being shipped to $ORACLE_HOME/dbs and named arch*.arc. Interestingly a log switch ships the archivelog minus the "arch" at the front and all archivelogs now do not have that format.
I moved the archivelogs to the correct location and renamed them. I have been able to set the correct location using standby_archive_dest and can see that the archivelogs are shipped to there. Also, v$archived_log shows the correct path and filename.
The problem I have is that when I come to apply the archivelogs it still seems to think that they should be in $ORACLE_HOME/dbs and named with "arch" at the front. Can someone please tell me what parameter I need to change to tell oracle the correct path and filename to use when applying the archivelogs?
Thanks
Simon

Hi saurabh
I am using the spfile/pfile created by the rman duplicate command.
Yes, the log_archive_dest_1 and 2 parameters are set.
This is the spfile from the standby server:
TAPSPROD.__db_cache_size=570425344
TAPSDR.__db_cache_size=1191182336
TAPSPROD.__java_pool_size=33554432
TAPSDR.__java_pool_size=16777216
TAPSPROD.__large_pool_size=16777216
TAPSDR.__large_pool_size=16777216
TAPSPROD.__oracle_base='/opt/oracle'#ORACLE_BASE set from environment
TAPSDR.__oracle_base='/opt/oracle'#ORACLE_BASE set from environment
TAPSPROD.__pga_aggregate_target=4831838208
TAPSDR.__pga_aggregate_target=4831838208
TAPSPROD.__sga_target=1610612736
TAPSDR.__sga_target=1610612736
TAPSPROD.__shared_io_pool_size=0
TAPSDR.__shared_io_pool_size=0
TAPSPROD.__shared_pool_size=956301312
TAPSDR.__shared_pool_size=369098752
TAPSPROD.__streams_pool_size=16777216
TAPSDR.__streams_pool_size=0
*.audit_file_dest='/opt/oracle/admin/TAPSDR/adump'
*.audit_trail='NONE'
*.compatible='11.2.0.0.0'
*.control_files='/opt/oracle/admin/TAPSDR/controlfiles/1/control.TAPSDR.01.ctl','/opt/oracle/admin/TAPSDR/controlfiles/2/control.TAPSDR.02.ctl','/opt/oracle/admin/TAPSDR/controlfiles/3/control.TAPSDR.03.ctl'
*.db_block_size=8192
*.db_create_file_dest='+TAPSDATA'
*.db_create_online_log_dest_1='/opt/oracle/admin/TAPSDR/redologs/1'
*.db_create_online_log_dest_2='/opt/oracle/admin/TAPSDR/redologs/2'
*.db_create_online_log_dest_3='/opt/oracle/admin/TAPSDR/redologs/3'
*.db_create_online_log_dest_4='/opt/oracle/admin/TAPSDR/redologs/4'
*.db_domain=''
*.db_flashback_retention_target=2880
*.db_name='TAPSPROD'
*.db_recovery_file_dest_size=4070572032
*.db_recovery_file_dest='+TAPSDATA'
*.db_unique_name='TAPSDR'
*.diagnostic_dest='/opt/oracle/diag/'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=TAPSDRXDB)'
*.event=''
*.fal_client='TAPSDR'
*.fal_server='TAPSPROD'
*.job_queue_processes=10
*.log_archive_config='dg_config=(TAPSPROD,TAPSDR)'
*.log_archive_dest_1='LOCATION=/opt/oracle/rman/sbvx10603/TAPSDR/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=TAPSPROD'
*.log_archive_dest_2='service=TAPSPROD ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=TAPSPROD'
*.log_archive_format='%t_%s_%r.arc'
*.log_archive_max_processes=5
*.open_cursors=300
*.pga_aggregate_target=4831838208
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1610612736
*.smtp_out_server='localhost:25'
*.standby_archive_dest='/opt/oracle/rman/sbvx10603/TAPSDR/archivelog'
*.standby_file_management='AUTO'
*.undo_tablespace='TBS_UNDO'

Duplicate archivelog sequence on standby database

Hi,
In our standby database when i check archivelog (below command), i see 2 duplicate sequence number. One is applied and another is not applied. Is there any problem with dataguard and how to solve it
TQ
SQL> sELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG where SEQUENCE# like '369%' order by SEQUENCE#;
THREAD# SEQUENCE# APP
1 36900 YES
1 36901 YES
1 36902 YES
1 36902 NO
1 36903 YES
1 36903 YES
1 36904 YES
1 36904 YES
1 36905 YES
1 36905 NO
1 36906 YES
1 36907 YES
1 36908 YES
1 36909 YES
1 36910 YES
1 36911 YES
1 36911 NO
1 36912 YES
1 36912 NO
1 36913 YES
1 36913 YES
1 36914 YES
1 36914 NO
1 36915 YES
1 36915 NO
1 36916 YES
1 36917 YES
1 36918 YES
1 36919 YES
1 36919 YES
1 36920 YES

Result At primary
ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
1 VALID OPEN ARCH IDLE MAXIMUM PERFORMANCE 0 0 38320
2 VALID UNKNOWN ARCH UNKNOWN MAXIMUM PERFORMANCE 7 7 38318
archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /xxx/xxx
Oldest online log sequence 38316
Next log sequence to archive 0
Current log sequence 38321
Result at standby
ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
1 VALID MOUNTED-STANDBY ARCH MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE 0 0 38316
11 VALID MOUNTED-STANDBY ARCH MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE 0 0 38318
archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /xxx/xxx
Oldest online log sequence 38316
Next log sequence to archive 0
Current log sequence 38321

How to delete archivelog file at standby database

Hi All,
I'm running Physical Standby Database on ASM. At standby database, I can see all logs using asmcmd:
ASMCMD> ls
thread_1_seq_14.330.625772527
thread_1_seq_15.346.625772527
thread_1_seq_16.329.625772527
thread_1_seq_17.327.625772559
thread_1_seq_18.324.625772599
thread_1_seq_19.341.625772367
thread_1_seq_2.325.625772329
But when I run RMAN to delete all these archivelogs, its give me error:
oradr:/u01/app/oracle$rman rcvcat rman/rman@rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 28 13:50:41 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: AIXDB (DBID=2438430915, not open)
connected to recovery catalog database
RMAN> delete archivelog all;
Starting implicit crosscheck backup at 28-JUN-07:01:50:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 06/28/2007 13:50:56
RMAN-12010: automatic channel allocation initialization failed
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 06/28/2007 13:51:06
RMAN-08040: full resync skipped, control file is not current or backup
Even it is not registering it. So how to delete archivelog file at standby database.
Thanks in Advance
Rakesh

This appears related to Bug 3298797 that was supposed to be fixed in 10.2.0.1. The workaround is to switch over to the standby, register the standby and then switch back.

MANAGED RECOVERY AT STANDBY DATABASE REQURING OLD ARCHIVELOGS ORA-00308

Oracle 9.2.0.4
HP-UX 11.11i
The database in Archivelog mode, single standby database in managed recovery
mode.
keeping standby in sync with manual applying the ARCHIVELOG from primary to
standby database.
primary database was 3 REDO log members of 100 MB with 1 member each.
what i did, 1 drop and re-create the INACTIVE REDO group for all three, and
make them
5 REDO logs of 200 MB with 1 member each,
then in order to keep fresh copy of primary database onto standby database, i
send the cold backup after 15 days (last week) with standby controlfile.
now, with that standby controlfile and the database, i can mount the database
but while to open the database, receives messages as , it requiring the
ARCHIVELOGS generated log time ago.
changes the REDO groups from 3 to 5 and size 100 to 200 MB at INACTIVE state
### Workarounds Used ###
SQL> alter database mount standby database;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
SQL> alter database recover automatic standby database;
alter database recover automatic standby database
ERROR at line 1:
ORA-00279: change 1655989696 generated at 08/12/2005 12:46:25 needed for thread
1
ORA-00289: suggestion :
/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
ORA-00280: change 1655989696 for thread 1 is in sequence #16849
ORA-00278: log file
'/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf' no longer needed
for this recovery
ORA-00308: cannot open archived log
'/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf'
ORA-27037: unable to obtain file status
HP-UX Error: 2: No such file or directory
Additional information: 3
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /user02/oracle9i/oradata/iobasprd/archive
Oldest online log sequence 53052
Next log sequence to archive 53056
Current log sequence
53056
-----------------------AlertIOBASPRD.log----------------------------
alter database mount standby database
Mon Oct 24 12:05:05 2005
Successful mount of redo thread 1, with mount id 3283884781.
Mon Oct 24 12:05:05 2005
Standby Database mounted.
Completed: alter database mount standby database
Mon Oct 24 12:05:12 2005
alter database open read only
ORA-16004 signalled during: alter database open read only...
Mon Oct 24 12:05:23 2005
alter database recover automatic standby database
Mon Oct 24 12:05:23 2005
Media Recovery Start
Starting datafile 1 recovery in thread 1 sequence 52617
Datafile 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
Starting datafile 2 recovery in thread 1 sequence 52617
Datafile 2: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_005.dbf'
Starting datafile 3 recovery in thread 1 sequence 52617
Datafile 3: '/user01/oracle9i/oradata/iobasprd/drsys01.dbf'
Starting datafile 4 recovery in thread 1 sequence 52617
Datafile 132: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_002.dbf'
Starting datafile 133 recovery in thread 1 sequence 52617
Datafile 133: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_003.dbf'
Starting datafile 134 recovery in thread 1 sequence 52617
Datafile 134: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_004.dbf'
Media Recovery Log
Media Recovery Log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
Errors with log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf.
ORA-279 signalled during: alter database recover automatic standby database...
Mon Oct 24 12:06:01 2005
Restarting dead background process QMN0
QMN0 started with pid=9
The snap of alertIOBASPRD.log can understand me that it requiring the
ARCHIVELOG 52617 only
and its lying in LOG_ARCHIVE_DET location also as
$ pwd
/user02/oracle9i/oradata/iobasprd/archive
$ ls archive_5261*.dbf
archive_52610.dbf archive_52613.dbf archive_52616.dbf archive_52619.dbf
archive_52611.dbf archive_52614.dbf archive_52617.dbf
archive_52612.dbf archive_52615.dbf archive_52618.dbf
$
now, even the files are lying , why ORACLE requing the old archive logs ?????

You haven't given any usefuly information on your problem.
show parameter log_archive_dest
show parameter fal
show parameter dg
What errors are in your alert logs ?
What command are you using to recover ?
Check the contents of v$archived_log
# run on primary to detect failures :-
select destination, status, fail_date, valid_now
from v$archive_dest
where status != 'VALID' or VALID_NOW != 'YES';
# run on standby to get exact position of rollforward :-
select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;
Are you using dataguard broker ?

Different archivelog destination on physical standby database

Hi,
Can I set different archivelog destination for physical standby database in duplicate command? (Due to space problem ) How can I do it?
For ex. on primary site archivelogs reside in /u01/ORCL/archivelog, and I want on phy. standby side archive dest. under /u08/ORCL/archivelog.

Even you can give LOG_ARCHIVE_DEST_1 in standby init file, So whenever you start standby/auxiliary instance automatically the dest_1 will refer to /u08/orcl(whereever you want). So you can have archive destination any where but should have proper permissions and location should be available.
If you want to assign one by one destinations, then still you can use "ALTERNATE" clause so that when the primary location unavailable or unable to archive, then of course it writes into alternate location you have specified from pfile.
You can check this
http://docs.oracle.com/cd/B28359_01/server.111/b28294/log_arch_dest_param.htm#i91817

Apply all ArchiveLogs manually to the Standby Database

Hi,
we can create a Physical Standby Database on Standard Edition, but we have to transfer and apply all ArchiveLogs manually to the Standby Database. How can we do this ?
many thanks

Thank you, but I opened a SR and asked :
1-can we install DATAGUARD (Primary and Standby) with STANDARD edition ?
many thanks.
they answered :
DataGuard is not available with Standard Edition. You need to have the Enterprise Edition in
stalled on the Primary and Standby Host. The Standard Edition only provides basi
c Standby Database without Log Transport and Log Apply Services. So you can create a Physical Standby Database on Standard Edition, but you have to transfer and apply all ArchiveLogs manually to the Standby Database.
that's why I asked you the question.
What is the exact synatx for recover database using backup control file please ?
Thanks again.

Deleting archivelog files once applied to physical standby database

Hi,
Any procedure for automatically deleting the archivelog files after applied to physical standby database.

also pls see DataGuard: auto delete redo logs after applied to physical standby?

Archivelog in standby database

Similar Messages

Maybe you are looking for