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.

Similar Messages

RMAN script problem to create logical standby database !

Dear Friends ,
I am using Oracle10g database . I want to create a logical standby database . I create two database :
Primary : orcl
standby : orclsby1
Every steps I followed successfully , but when I am going to create "standby database" from "primary database" using rman then I found the following error :
The script is below which I have to run in Primary (orcl) database :
Script :
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'orcl','orclsby1'
set db_unique_name='orclsby1'
set db_file_name_convert='/orcl/','/orclsby1/'
set log_file_name_convert='/orcl/','/orclsby1/'
set control_files='/u01/app/oracle/oradata/orclsby1.ctl'
set log_archive_max_processes='5'
set fal_client='orclsby1'
set fal_server='orcl'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(orcl,orclsby1)'
set log_archive_dest_1='service=orcl ASYNC
valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=orcl'
Problem which I got :
[oracle@localhost DG]$ rman target sys/sys123@orcl auxiliary sys/sys123@orclsby1
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Oct 19 15:58:17 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1227832857)
connected to auxiliary database: ORCLSBY1 (not mounted)
RMAN> @cr_phys_sby1.txt
RMAN> run {
2> allocate channel prmy1 type disk;
3> allocate channel prmy2 type disk;
4> allocate channel prmy3 type disk;
5> allocate channel prmy4 type disk;
6> allocate auxiliary channel stby type disk;
7> duplicate target database for standby from
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "from": expecting one of: "dorecover, db_file_name_convert, nofilenamecheck, ;"
RMAN-01007: at line 7 column 39 file: cr_phys_sby1.txt
I try to edit the above script using 'nofilenamecheck' 'dorecover' etc. , but cannot resolve the problem . Would u plz help me .... where the problem is .
Both databases are running on Oracle10g platform .
Waiting for ur kind reply .. ...

You need to:
- create a SPFILE manually for standby database
- use the RMAN command: DUPLICATE TARGET DATABASE FOR STANDBY
- remove all SPFILE statements from RMAN script.

Problem in recover physical standby database(Data Guard) by rman

Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle Error:
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: '/u01/app/oracle/oradata/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PM

hi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks

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 while creating Physical standby database on remote Server

Hi
I try to create a physical standby datbaase using OEM 10gr2, it is working when I create on same server. No issue but when I try to create same on remote server it is giving below warning and process failing. Please let me know what needs to be down in this senario...
It is showing redo log information in v$log and v$log_file but not creating physically on PHYSICAL Standby instance..
I appriciate your help and ur time too..
These messages are from PRIMARY database alert*.log file
There is space for up to 12 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800;
WARNING: OMF is enabled on this database. Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames.
Thanks and Regards,
RK

Well, it is simply warning that "Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames"
For instance, the path for the logfile name in "ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800" may need to be changed manually. It is advisable to check the mentioned documentation.

Archive apply issue for standby database in Standard Edition.

We have setup standby database in Oracle standard edition. the archive log cannot be send by oracle automatically. So we manually send the archive over. But do not see the database apply the archive log file. What could be wrong and where should we check on it?
We also used following when finishing the standby DB after running "recover standby database;" for a few archive log file:
alter database recover managed standby database disconnect from session;
======================================================================================
This is the status:
SQL> select OPEN_MODE, SWITCHOVER# ,REMOTE_ARCHIVE ,ARCHIVELOG_CHANGE#,SWITCHOVER_STATUS, DATABASE_ROLE from v$database;
OPEN_MODE SWITCHOVER# REMOTE_A ARCHIVELOG_CHANGE# SWITCHOVER_STATUS DATABASE_ROLE
MOUNTED 495550636 ENABLED 1.2201E+13 SESSIONS ACTIVE PHYSICAL STANDBY

The DB version is 10.2.0.5
I can do this to apply at standby DB:
SQL> set autorecovery on
SQL> recover standby database;
Then I tried to run this to leave the session:
alter database recover managed standby database disconnect from session;
Do not seen any apply.
=============================
Here is the last lines of alert log:
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /u02/cntus/redolog/redo01a.log
Clearing online log 1 of thread 1 sequence number 10158
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 10166
Thu Sep 06 15:08:35 EDT 2012
Completed: alter database recover managed standby database disconnect from session
======
We have the directory /u02/cntus/redolog and /u03/cntus/redolog. But nothing in there. Should we create redo for it? Is this a separate issue?
Thanks!

CCMS MAIL ALERT FOR STANDBY DATABASE

Hi All,
I've configured the CCMS alert monitor in my entire landscape & I'm successfully getting alert mails from CCMS alert monitor (T-codes involved are RZ20 & RZ21).
I want to activate the same functionality for my standby database. At least I want to configure the CCMS alert monitor for File System Utilization in my Standby database.
Can any one guide me about the configuration setting for file system utilization in Standby Database through CCMS monitor.
Regards,
Neehir Bhatt

Hi,
Highlevel steps:
- Install the sapccm4x agent on the standby host
- Register the agent to the CEN
- In the agent home directory create a file like oscolfilter.ini In this file enter the filesystems you would like to monitor
- Add the oscolfilter.ini file into the sapccmsr.ini file This is also located in the agent home directory
- Create a MTE for filesystem monitoring in your CEN. Add the relevant monitor attribute there.
- Assign autoreaction via RZ21
For more information, see OSS Note 522453 - RZ20: Monitoring operating system data

Procedure for Standby Database for SAP ERP 6.0

Hello All,
We are using SAP ERP 6.0 with Oracle 10g with AIX 5.3.
We are planning to setup a standby database for our SAP ERP 6.0 production system as part of remote DR site using Oracle Data Guard.
I was under the assumption that i can first install an erp 6.0 (ABAP) system using homogeneous system copy from my erp 6.0 (ABAP) production system and then start configuring oracle dataguard.
But the System Copy Guide "System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP" has mentioned that "You cannot create standby systems with a system copy".
Please suggest the best practise or the procedure for creating standby database for SAP ERP 6.0 system. Iam not looking at the steps for creating a pure oracle 10g standby database, but with SAP instances as well.
Thanks in advance.
CVS

Hi,
Please refer the below mentioned link for configuring data guard.
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm
Below mentioned are the sequence of stpes, which needs to be followed for setting up data guard.
3.1 Configuring the Primary Database
3.1.1 Enable archiving and define a local archiving destination
3.1.2 Create a password file
3.1.3 Configuring the Oracle networking files
3.1.4 Set initialization parameters on the primary database
3.1.5 Take Offline/Online backup of the primary database
3.1.6 Create a control file for the standby database
3.1.7 Prepare initialization parameter file for the standby database and start the primary database with the changed pfile.
3.1.8 Copy all files from the primary host to the standby host
3.2 Configuring the Standby Database
3.2.1 Configuring the Oracle networking files
3.2.2 Create a INIT parameter file for the standby database
3.2.3 Copy the standby controlfile to the appropriate location
3.2.4 Create Oracle Password File
3.2.5 Start the physical standby database
3.2.6 Initiate log apply services
Regards,
Ranjith

Best way for standby database?

hi,
I heard that DataGuard and Streams are two ways to have a standby database ready in case your normal database fails?
Can someone please share their experience of using either of these so that I can decide which one I should research into?
thanks

I am not very good in streams but whatever little I know , based on that , DG is a block by block copy of the production over the standby making it sure that in the case of the disaster, if you would do failover, there won't be anything that you would be missing. That's why physical standby is the best and if I can say, the only way to do take care of a disaster. Further enabled with Broker, it can be done completely without the dba's intervention which would happen in 20seconds maximumly ( I hope the timing is correct) making it an idle solution for the HA. With 11g enhancements of Active Dataguard and Snapshot Standby, it has really become a useful entity for normal functionality/working of the databases as well.
Streams, on the other hand is a replicaton tool based on some rules that you define. Compared to DG, it can be just a part of the production system which is replicated over the other side. So I won't consider this as an ideal to take care of disasters.
Just my 2 cents.
Happy new year and belated merry Christmas as well :-) .
Aman....

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.

Autorecover for standby database....

Does anyone know if there are plans to allow the autorecover function to apply log files to a standby database without bringing the database online? It would seem like a logical option to have and greatly simplify the management of log files on the standby server.
Alternatively, does anyone have any template scripts (RHEL4) that they could post for applying log files on a standby server. I don't believe in re-inventing the wheel if I don't have to.
Thanks,
George M-A

Hello George,
we are in the same situation of not to re-invent the wheel.
So I used the forum search and some google and found the following link:
http://lists.mysql.com/maxdb/24407
In this thread a script for autorecovering is discussed.
We are now trying to verify the script and to customize it for our environment.
Regards,
Thomas

Force logging at tablespace level for standby database

Hi
Can we create a standby database by enabling force logging at tablespace level instead of enabling it at database level.I want to out the tablespace containing indexes in nologging mode so that when I rebuild the indexes no logs will be generated.

Technically, you can create a Standby without having set FORCELOGGING at the Primary database.
You can also then selectively FORCELOGGING for all your important tablespaces (beginning with SYSTEM, SYSAUX, UNDO ....)
However, for a Physical Standby Redo Apply will mark the blocks (e.g. those populated by the CREATE INDEX .. NOLOGGING) as "corrupt". You will get Read Errors (ORA-1578 and ORA-26040) when you attempt to read the index (e.g. for a Table query).
So you have to monitor your NOLOGGING operations and the datafiles where NOLOGGING is applied. You can take Incremental RMAN Backups of such datafiles and restore them to the Standby immediately after the NOLOGGING operations.
Hemant K Chitale

Initial setup for standby database - doubts ??

Hi,
While creating a physical standby database from a primary database what is the initial setup in case of the standby database which will be created.
1.Is it that I will only install the oracle with no starter database and then continue with the steps for creating standby database.
2. The SID has to be the same for both the database or can it be different.
Waiting for your answer.
sl

1)
Fulfill the prerequisites
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14239/standby.htm#i58150
2) It has to be same.

SAPOSCOL for standby Database

Hi ,
To read the SAPOSCOL information of DB system ( distributed environment) from SAP Applicaiton, I have created the SAPOSCOL destination SAPCCMSR.<<Hostname>>.99 with below utility
/sapmnt/<SID>/exe/sapccmsr -R pf=/usr/sap/tmp/sapccmsr/sapccmsr.pfl
However, I cannot use this to read OS information when system is running on standby database.
I have searched lot and gone through many links to setup destination for standby DB OS information and no luck.
Can any one help me by providing some information how to setup destination.

Hi Murugesan,
You can configure CCMS monitoring on the standby database .
You can do the following to achieve the same
install the sapccm4x agent on the standby host
- Register the agent to the CEN
- In the agent home directory create a file like oscolfilter.ini In this file enter the filesystems you would like to monitor
- Add the oscolfilter.ini file into the sapccmsr.ini file This is also located in the agent home directory
- Create a MTE for filesystem monitoring in your CEN. Add the relevant monitor attribute there.
- Assign autoreaction via RZ21
For more information, see OSS Note 522453 - RZ20: Monitoring operating system data
Hope this helps.
Regards,
Deepak Kori

Flashback for standby database

Hi,
We have dataguard environment with Sun OS & Oracle 10g, 11g. Now we want to enable flashback for the primary database as well as standby database (physical standby). NO RMAN. I did manage to configure the flashback for the primary database but confusion is:
-- Do I need to configure flashback at standby or recreate standby after enabling flashback at primary site?
-- Suppose if I use flashback database to restore point and open database with resetlogs, what would be the situation at standby site? Will it be in sync with primary or after resetlogs I need to make new standby database??
-- Is there any space requirement ratio for flashback recovery partition?
Thanks,
Amit.

Amit_P wrote:
Hi,
We have dataguard environment with Sun OS & Oracle 10g, 11g. Now we want to enable flashback for the primary database as well as standby database (physical standby). NO RMAN. I did manage to configure the flashback for the primary database but confusion is:
-- Do I need to configure flashback at standby or recreate standby after enabling flashback at primary site?
-- Suppose if I use flashback database to restore point and open database with resetlogs, what would be the situation at standby site? Will it be in sync with primary or after resetlogs I need to make new standby database??
-- Is there any space requirement ratio for flashback recovery partition?refer these notes.
*How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]*
+Restore Points in Oracle10g Release2 [ID 330535.1]+

Problem on archivelog for standby database

Similar Messages

Maybe you are looking for