Compressing redo data for Physical Standby

Hi All,
I have been checking option of compressing redo data for a Physical Standby database. I did not find many details in the docs. Any one has implemented this kind of compression.
Cheers/Aditya

per Oracle support, redo compression in DG makes sense only if the bandwidth between the primary & standby server is less than 100mbps and is expected to be heavily taxing on CPU.
you may check metalink article ID: 729551.1 where they have given some test stats. Not a whole lot of data, but it might help you make a good judgement.
Cheers.

Similar Messages

How to check data in physical standby database?

Hi!
I'm maintaining physical standby database system. everyday, i must check tranfer and apply progress. I known, it operate very good. No archive gap is found.
But i want to check data in physical standby database that there is consistant with primary database, there isn't? What method do I use? How to do?
thankS

I hope the following will help
Verifying the Physical Standby Database
==========================================
Once you create the physical standby database and set up log transport services, you may want verify that database modifications are being successfully shipped from the primary database to the standby database.
To see the new archived redo logs that were received on the standby database, you should first identify the existing archived redo logs on the standby database, archive a few logs on the primary database, and then check the standby database again. The following steps show how to perform these tasks.
Step 1 Identify the existing archived redo logs.
On the standby database, query the V$ARCHIVED_LOG view to identify existing archived redo logs. For example:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
3 rows selected.
Step 2 Archiving the current log.
On the primary database, archive the current log using the following SQL statement:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Step 3 Verify that the new archived redo log was received.
On the standby database, query the V$ARCHIVED_LOG view to verify the redo log was received:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
11 11-JUL-02 17:51:03 11-JUL-02 18:34:11
4 rows selected.
The logs are now available for log apply services to apply redo data to the standby database.
Step 4 Verify that the new archived redo log was applied.
On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log was applied.
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
2 ORDER BY SEQUENCE#;
SEQUENCE# APP
8 YES
9 YES
10 YES
11 YES
4 rows selected.

About Data Guard - Physical Standby Database

Dear All,
I have read many documents regading Data Guard.
I am about to setup Data Guard in our current environment but want to clear few tings.
I have a confusion between physical and logical standby database.
What I have read from different documents is:
-Physical Standby Database in (11g)
1) It is the most efFicient
2) I can be either in mount or open state
3) Select queries and reporting can be done to improve performance of the primary database.
4) Schema on primary and standby database is always the same
-- Logical Standby Database
1) You can create additional tables, indexes, etc.
2) Always in open mode
3) Select queries and reporting can be done to improve performance of the primary database
Now our scenerio is, that we have one server at the moment, OS is linux and operating system is 11g. We want to setup an other server in another country, will also be 11g on Linux in a way that it acts as standby/backup server. Schema and data is always the same. In case due to unavailability of primary server, standby server acts as the primary server (This has to be automated). The reason for unavailability could be any like maintenance work on primary server, network or hardware failure at primary server. The last and the most important thing is that users from this country where we will setup standby database will insert/update data on the primary server BUT queries and reporting will be done from this newly created standby data.
Kindly recomend the best Data Guard in this scenerio and kindly correct me where I am wrong.
Thanks, Imran

A logical standby has various limitations on things like data types. It's also a much more complex architecture, which makes it more likely that something will break periodically and require attention. Applying redo to a physical standby is code that has been around forever and is as close to bullet-proof as you'll get. And you would generally prefer to fail over to a physical standby-- if you do things like create new objects in the logical standby, you may have to get rid of those objects during a failover to get acceptable OLTP performance.
Justin

Oracle DataGuard - Standy Redo log on physical Standby db

Hello Guys,
A quick question on my 10.2.0.2 db with Windows 2003 x64 OSs.
I have 2 machines - One for primary & the other for physical standby
I have successfully setup DG with Real Time Apply and also tested switchover & failover scenarios and they work well and as expected...
But I have a query which popped up when I was trying to set this up at home.
I create the physical standby db by shutting the primary db and copying all the datafiles, tempfiles,online redo logs and then creating a standby control file which will be used for the physical standby db to start off with.
After mounting the standby db, I tried to create standby redo logs files starting with Group 4 but I got error that standby group 4 already exists.
Upon querying v$logfile view, I noticed that the standby redo logs that I created on primary are also showing up on the standby db which I understand is from the standby control file.
So here is my quesiton: What is correct method of creating these standby redo logs on the standby database?
I know that I could drop those 4 standby redo logs from the standby db and recreate them but all the DG docs online and the documents that I have referred say that I should create the standby redo logs on the standby as I did on the primary but how can this duplication be avoided i.e. from the standby control file?
I know that I could use another method to create a hot backup such as RMAN etc...but I wanted to follow this way of shutting down the primary and copy the relevant database files.
Any help appreciated...and thanks in advance guys!
-Bharath

so with the setup that I used, i.e. create a standby control file which contains info about the standby redo logs at the primary site, should I also copy over the standby redo logs from the primary to standby as I only copied the datafiles, tempfile(s) & online redo logs? But then the filenames of the standby redo logs will be the exact same as that of the primary. Will that cause any issue during a switchover/failover?
I don't remember exactly how I did it when I got the whole thing working but I have a vague remembrance that I drop the std. redo log files entries from the std database and then recreate new ones with different filenames (as compared to primary).
Thanks

Test scenario for Physical Standby

Dear Team,
Could you please share the Test scenario for Physical Standby.
1. Read only.
2. Switch Over
3. Fail Over.
Many Thanks in Advance
Arjun.

You didnt mention the version.
Oracle10g Release 2, Data Guard Switchover and Failover best practices
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_SwitchoverFailoverBestPractices.pdfOracle9i, Data Guard Switchover & Failover best practices
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_9iSwitchoveFailoverBestPractices.pdfKhurram

Using streams to capture data from physical standby database.

Does anybody know if it is possible to use streams to capture data from physical standby database instead of PROD database? The standby database is in read only mode. We use Oracle 11gR2.
Thanks in advance.

physical are closed : how will it managed the queues and overspill queues when target is not present? Also the data dictionary must reflect the primary but If you run capture, then you introduce rules that are not on primary: How ?

Data Guard - Physical Standby Setup by RMAN

I am trying to set up a physical standby using RMAN. After I brought up the standby db, I failed to turn on redo apply. I found out that the standby redo log files were not copied over to the standby.
The back up script I use is as follows.
run {
allocate channel ch2 type disk;
backup current controlfile for standby format '/backups/sitv/cf_%d_t%t_s%s_p%p';
backup format '/backups/sitv/%U.bkup' database;
sql 'alter system archive log current';
backup format '/backups/sitv/al_t%t_s%s_p%p.bkup' archivelog all;
release channel ch2;
What command should I use to be able to make a backup of the standby log files as well?
Thanks.

Hi Sybrand,
Thank for the reply. Let me give a little bit more detailed information on what I did.
I followed the documentation as follows to set up the physical standby
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
I created the standby log files per section 3.1.3 on the primary db before the standby is created.
I used the following command to restore the standby on a different server.
run {
allocate auxiliary channel ch1 device type disk;
duplicate target database for standby dorecover nofilenamecheck;}
My question is the standby log files did not show up on the standby server. However, the log files showed in the v$logfile table. After I tured on the redo apply, the changes I made in primary db did not happen in the standby db.
Any idea on how to fix it?
Thanks.

OEM for physical standby database

Hello All,
I am using Oracle 11.2.0.3. My enterprise manager is db console 11.2
I have Oracle Enterprise manager dbcnsole for my RAC primary database and I have created through sqlplus command line a physical standby database.
My questions
Can I use the RAC primary dbconsole to monitor my physical standby database? if yes what the steps?
Is it mandatory to use grid control in that case? if yes, what steps are needed to implement grid control ?
Regards,

Hi,
It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control. This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality). In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
Using EM cloud control 12c is best available option to monitor your standby databases
For install docs refer to
http://docs.oracle.com/cd/E24628_01/install.121/e22624/toc.htm
For Software download link
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
Regards,
Rahul

Read-only agent synching to a Data Guard physical standby?

Hi all,
we are trying to use TimesTen 11.2.2.4.1 as a read-only memory cache for an Oracle 11.2.3.0.7 schema on Linus RedHat 6.3, while using Oracle Data Guard to replicate the Oracle instance over geographically remote sites. On each site we would like to have two TT instances synchronizing with the local Oracle 11g instance. This works fine against the master DB, but are the TT agents going to be able to synchronize against physical standby instances?
The problem it seems is that the TT agent uses dedicated structures in the Oracle master instance (related to the cache grid), which are going to be replicated into the standby instances. Is the TT agent able to use the read-only, replicated structures to complete synchronization, or is this approach unworkable? What would be your advise as how to achieve this?
Thanks for your help,
Chris

Hi again,
so after testing a little bit it appears that this approach works indeed, at least against a limited number of manual DML operations. What I needed to do on the slave instance to have it working is the following:
1 - Entirely exclude TTADMIN and TIMESTEN schemas from the Data Guard replication:
ALTER DATABASE STOP LOGICAL STANDBY APPLY;
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL', schema_name => 'TTADMIN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL', schema_name => 'TIMESTEN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'DML', schema_name => 'TTADMIN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'DML', schema_name => 'TIMESTEN', object_name => '%');
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
2 - Erase both schemas from the local instance:
DROP USER TTADMIN CASCADE;
DROP USER TIMESTEN CASCADE;
CREATE USER TTADMIN etc
3 - Temporarily disable the database guard while creating the local ttCache structures, as the scripts seem to need to set a table-level lock on the source table:
ALTER DATABASE GUARD NONE;
ttIsql> CREATE READONLY CACHE GROUP etc
ALTER DATABASE GUARD STANDBY;
4 - Unset the "Fire_Once_Only" property for the local TTADMIN triggers:
execute dbms_ddl.set_trigger_firing_property(trig_owner=> 'TTADMIN', trig_name=> 'TT_06_70560_T', fire_once => FALSE);
At that point the cache seems to replicate properly in the most simple cases. I will try to test with some substantial load and against DG failovers to see how this behaves.
Regards,
Chris

DB link for physical standby database

Hi All ,
I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
SQL> create database link synct connect to system identified by 123 using 'stdby';
Database link created.
SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
select max(sequence#) from v$archived_log@synct where applied='YES'
ERROR at line 1:
ORA-02068: following severe error from SYNCT
ORA-01033: ORACLE initialization or shutdown in progress
Database version is 10.2 standard edition
My requirement is i need to get max(sequence#) of standby database from primary database using db link.
what i was trying to do is
on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
Any suggestions will be really helpful

976422 wrote:
Hi All ,
I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
SQL> create database link synct connect to system identified by 123 using 'stdby';
Database link created.
SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
select max(sequence#) from v$archived_log@synct where applied='YES'
ERROR at line 1:
ORA-02068: following severe error from SYNCT
ORA-01033: ORACLE initialization or shutdown in progress
Post Standby/DataGuard/ADG all questions further in Oracle Discussion Forums » High Availability » Data Guard
If you try to connect any users other than SYS in standby the error is very much expected. Of course you can connect with other users if you open database in OPEN READ ONLY mode, from 11gRx you can connect with other users even MRP is running if you are using ADG(active Data Guard licensed) .
I like to know, what you want to achieve by creating DB Link on physical standby database? Which is not allowed.
Database version is 10.2 standard edition
My requirement is i need to get max(sequence#) of standby database from primary database using db link.
what i was trying to do is
on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
Any suggestions will be really helpfulNote:- Standard edition, Data Guard not enabled.
To use this you should use Oracle Net Service, you no need of DB Links.
Ex:- sqlplus sys/****@standby as sysdba
Here standby refers to Oracle net service, Where you will have entries in $ORACLE_HOME/network/admin/tnsnames.ora file.
Edited by: CKPT on Dec 12, 2012 2:01 PM

Cannot Clear Critical Alert for Physical Standby Databases

10.2.0.4.0 Grid Control monitoring 10.2.0.4.0 databases and standby databases with 10.2.0.4.0 agents.
The standby databases are running on Xen guests. The O/S is Red Hat 4 Advanced Server.
I had a failure of Xen guest on Saturday that caused me to have to rebuild the standby servers. EM Grid Control successfully verifies the configurations and the status is normal for both physical standby databases. (A rebuilt logical standby database shows no alerts.)
Grid Control database targets page shows a single critical alert for each physical standby database. The alert is for "number of missing media files is 4". The metric graph shows the count as 0 since before the rebuilds. I cannot clear the alerts from the Critical Alerts page. Grid Control reports "The selected alert(s) cannot be manually cleared. They will clear automatically once the metric is no longer in a critical or warning state.".
Any suggestions?
Thanks,
Ray Westphal

Thanks for the reply Anthony.
The result of the query on both standby databases is '0'. The metric graph also shows the value at '0' since before rebuilds.
And the OMS db and agents have been reset several times since I posted this.
Ray Westphal.

Data Guard Physical Standby Failover

I need clarification on Physical Standby Failovers. Say I have a Primary db (A) and a physical standby (B), (A) fails and (B) is now the primary, can (A) be setup to become a standby of (B)? I've read 2 different statements in Oracle 10g Data Guard Concepts and Admin
"During failovers involving a physical standby database: In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration."
vice
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
Much thanks.

In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration.
TRUE ! But this doesn't mean that you cannot make your failed primary a new standby database !.
You can achieve this using FLASHBACK DATABASE option:
From the documentation:
After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.
Read the following documents:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#sthref995
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
In addition to this I'd like to mention that you can achieve the same with doing an incomplete recovery instead of using FLASHBACK DATABASE.
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
TRUE. If you enable Fast-Start Failover:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDFFEC
Cheers!

Standby Redolog Creation for Physical standby

I want to migrate my primary database from one server X to standby database which i want to create on other server Y. once Primary and standby will get SYNC , i will do Fail over to make standby as primary and divert current application on standby considering as full functional Primary.
Is it mandatory to create SRL ( Standby redo log)? or I can create physical standby without SRL? If Yes, on which side (primary or standby) i need to create SRL?
Appreciate your help..

Hello,
Now, My standby database has configured. Since i had restore and recover standby database from standby controlfile instead of RMAN Duplicate. I had done following step:
ON standby side:
$rman target /
RMAN> restore standby controlfile from '/app/oracle/standbyctl.ctl'
RMAN> sql 'alter database mount standby database';
RMAN> restore database;
RMAN> list backup of archive log all;
RMAN> RMAN> recover database until sequence 1670;
SQL> alter database recover managed standby database disconnect from session;
• On Primary:
SQL> alter system set log_archive_dest_state_2=ENABLE;
• On Standby:
SQL> select sequence#,applied from v$archived_log order by sequence#;
I am at this stage now. My primary and standby database in synchronization. As per my first thread above, we will have planned outage to move application to standby database and make it full functional primary database. once application will move on new server( standby database). we will not use current primary database anymore.
what are the procedure i need to do on primary side and standby side when migrate application on new server.? rightnow my standby database in MOUNT mode and archive log is shipping from primary to standby. we have no dataguard broker configuration. i need to do it manually using SQL command.

How to deal with tempfiles named '+DATA' on physical standby databases

Hi gurus,
I have a 3-node RAC with 2 standby databases, all of them 11.2.0.3, on CentOS 5.10 64 bits.
I use Active Data Guard (with DB open in read-only mode, obviously).
My problem is that somehow I have 3 tempfiles named '+DATA' on one standby database, so I can't drop nor rename these files. Is there any way to fix this?
Looks like the tempfiles couldn't be created when the database was opened in read-only mode.
Thanks a lot for your help.
# Primary DB:
col TABLESPACE format a10
col TEMPFILE format a50
select a.name TABLESPACE, b.TS#, b.FILE#, b.name TEMPFILE, b.bytes/1024/1024 MB, b.status from v$tablespace a, v$tempfile b where a.name='TEMP';
TABLESPACE        TS#      FILE# TEMPFILE                                                   MB STATUS
TEMP                3          4 +DATA/racdb/tempfile/temp.382.873892319                  8192 ONLINE
TEMP                3          7 +DATA/racdb/tempfile/temp.383.873892341                  8192 ONLINE
TEMP                3          8 +DATA/racdb/tempfile/temp.384.873892341                  8192 ONLINE
# Standby DB:
col TABLESPACE format a10
col TEMPFILE format a50
select a.name TABLESPACE, b.TS#, b.FILE#, b.name TEMPFILE, b.bytes/1024/1024 MB, b.status from v$tablespace a, v$tempfile b where a.name='TEMP';
TABLESPACE        TS#      FILE# TEMPFILE                                                   MB STATUS
TEMP                3          4 +DATA                                                       0 ONLINE
TEMP                3          7 +DATA                                                       0 ONLINE
TEMP                3          8 +DATA                                                       0 ONLINE
TEMP                3          9 /u02/oradata/RACDBSB1/tempfile/temp_01.dbf                512 ONLINE
RMAN> report schema;
using target database control file instead of recovery catalog
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name RACDBSB1
List of Temporary Files
=======================
File Size(MB) Tablespace           Maxsize(MB) Tempfile Name
4    3072     TEMP                 8192        +DATA
7    3584     TEMP                 8192        +DATA
8    5120     TEMP                 8192        +DATA
9    512      TEMP                 8192        /u02/oradata/RACDBSB1/tempfile/temp_01.dbf
SQL> show parameter db_create_file_dest
NAME                                 TYPE                             VALUE
db_create_file_dest                  string                           /u02/oradata
Thanks!

Hi all,
Regarding Hemant's question, YES, I use that config, and the error I receive is:
SQL> alter database tempfile 4 drop;
alter database tempfile 4 drop
ERROR at line 1:
ORA-01516: archivo log, archivo de datos o archivo temporal "+DATA" inexistente
Segey, yes, I've tried with no luck.
The good news are that today we've resolved the problem, we had to use:
SQL> alter tablespace temp drop tempfile 4;
Tablespace altered.
OMG, what's the difference... alter database tempfile 4, alter tablespace temp drop tempfile 4... they are both the same...!! lol
Thanks guys!

11g Data guard 建physical standby database配置相关问题

General information
OS:red hat Linux 2.6.32-200.13.1.el5uek x86_64(primary,standby)
Home version:11.2.0.3(primary,standby)
Situation:
实验用库，想学习data guard，在另一个服务器上克隆了一个HOME并按照官方文档http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ps.htm#i1225703
中去实验，步骤均按照官方文档来,最后在mount standby库时校验select sequence# from v$archived_log没有记录，出错日志如下（从mount开如截取）
standby alert_dbacoe.log
Error logs
alter database mount
Completed: alter database mount
Error 604 received logging on to the standby
+FAL[client, ARC2]: Error 604 connecting to PRIMARYSV for fetching gap sequence+
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Addition:
因为是实验用库，所以结构有点怪，大体如下:
Primary
数据文件在BASE所在的oradata下即/u03/app/oracle下,
redo文件每组两份，一份在oradata下，另一份在同机的/u04/app/oracle/redundancy中（以_s结尾命名）
archive文件在/u04/app/oracle/fast_recovery_area中
standby
数据文件在/u05/oracle/app/oracle/oradata下
redundancy中的redo文件随着该目录放到oradata下的red中了
archive文件目录则是/u05/oracle/app/oracle/fast_recovery_area中
接下来是对应的init文件与TNS信息
Primary端的init主要信息
db_unique_name='PRIMARY'
fal_client='PRIMARYSV'
fal_server='STANDBYSV'
log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
log_archive_dest_1='location=/u04/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=PRIMARY'
log_archive_dest_2='service=STANDBY ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=STANDBY'
log_archive_dest_state_1='enable'
log_archive_dest_state_2='enable'
db_file_name_convert='/u05/oracle/app/oracle/oradata/dbacoe','/u03/app/oracle/oradata/dbacoe',/u05/oracle/app/oracle/oradata/red','/u04/app/oracle/redundancy'
log_file_name_convert='/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog','/u04/app/oracle/fast_recovery_area/DBACOE/archivelog'
Standby端的init信息
log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
db_unique_name='STANDBY'
db_file_name_convert='/u03/app/oracle/oradata/dbacoe','/u05/oracle/app/oracle/oradata/dbacoe','/u04/app/oracle/redundancy','/u05/oracle/app/oracle/oradata/red'
log_file_name_convert='/u04/app/oracle/fast_recovery_area/DBACOE/archivelog','/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog'
log_archive_dest_1='location=/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=STANDBY'
log_archive_dest_state_1=enable
log_archive_format=log%t_%s_%r.arc
log_archive_dest_2='SERVICE=PRIMARYSV ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
log_archive_dest_state_2=enable
TNS信息如下(均能tnsping通）
PRIMARYSV =
+(DESCRIPTION =+
+(ADDRESS = (PROTOCOL = TCP)(HOST = db1.ad.xxxxxx.com)(PORT = 1521))+
+(CONNECT_DATA =+
+(SERVER = DEDICATED)+
+(SERVICE_NAME = dbacoe)+
+)+
+)+
STANDBYSV =
+(DESCRIPTION =+
+(ADDRESS = (PROTOCOL = TCP)(HOST = db2.ad.xxxxx.com)(PORT = 1529))+
+(CONNECT_DATA =+
+(SERVER = DEDICATED)+
+(SERVICE_NAME = dbacoe)+
+)+
+)+
PS：请大家花费一点点时间阅读一下这冗长的段子，刚开学data guard，参数上设置都很生疏，（光照着文档做了，是否有redo log相关的操作遗漏？）敬请指教
Edited by: 961394 on Dec 10, 2012 1:52 AM
Edited by: 961394 on 2012-12-10 上午4:58

结贴了，感谢maclean一群的Jesse Lui帮我解决问题

Compressing redo data for Physical Standby

Similar Messages

Maybe you are looking for