Is data guard supported on mainframe zLinux? Anything limitation?

We have Oracle database 9.2.0.4 running on mainframe zLinux. We are thinking of building a data guard for HA.
Is there data guard supported on mainframe zLinux? Anything limitation for zLinux version? can I use 9.2.0.4 on one side, 11.1 on other side?

I am aware of some limitations regarding the logical standby with different chipsets (not supported in one of my environments), but nothing specific in your case. Since limitations on IBM zSeries Based Linux (z/Linux) are not mentioned specifically, it might mean that most of the features would work with the same db version and os version. On the other hand, it might mean there are limitations not discovered or reported to Oracle support.
HTH.

Similar Messages

Oracle 9i Data Guard supported on Windows 2000 platform ?

Is Oracle 9i Data Guard supported on Windows 2000 platform ?

YES, we are currently using Data guard on 2000 Windows Server. Will need to have the Management server installed in order to get the Data guard function.

Active Data Guard in different database versions (11.2.0.3 and 11.2.0.4)

In case of Active Data Guard can i run different database versions (11.2.0.3 and 11.2.0.4) at Primary and DR for production environment ? And will having RAC in environment make any difference?

Hi,
>>In case of Active Data Guard can i run different database versions (11.2.0.3 and 11.2.0.4) at Primary and DR for production environment ?
As per normal Data Guard requirement, Oracle 11.2 does support flexibility where Primary and Standby may have different hard wares such as CPU architecture and OS etc. but the Oracle RDBMS software version must be the same. Having said so does not mean it will not support it. Beginning with 11.1.07, a physical standby database can be used to execute a rolling database upgrade to a new Oracle Patch Set or database release by using the transient logical rolling database upgrade process. It means you can have with different database version but for how long, you need to check above documents.. For complete information you should read this note:
Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration (Doc ID 413484.1) &
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-transientlogicalrollingu-1-131927.pdf
2) >> And will having RAC in environment make any difference?
NO. You can find answer at - https://docs.oracle.com/cd/E11882_01/server.112/e41134/standby.htm#SBYDB4716
**The primary database can be a single instance database or an Oracle Real Application Clusters (Oracle RAC) database. The standby databases can be single instance databases or Oracle RAC databases.
HTH,
Pradeep

HT204266 My iPad (version 1, IOS 5.1) has quit connecting with the store. I am unable to update or buy any app. I did a reboot and a reset with deleting the data. I can not find anything in support for this problem. Any help will be appreciated.

My iPad (version 1, IOS 5.1) has quit connecting with the store. I am unable to update or buy any app. I did a reboot and a reset with deleting the data. I can not find anything in support for this problem. Any help will be appreciated.

My iPad (version 1, IOS 5.1) has quit connecting with the store. I am unable to update or buy any app. I did a reboot and a reset with deleting the data. I can not find anything in support for this problem. Any help will be appreciated.

Does Oracle 10g support Active Data-guard?

Hi all,
Can Oracle Database 10g support Active Data-guard?
Thanks you!
Dan
Edited by: Dan on Jul 12, 2011 10:13 AM

no, active data guard is 11gR1 new feature.
In Oracle Database 10g and below you could open the physical standby database for read-only activities (say, to offload some reporting), but only after stopping the recovery process. With these releases, If Data Guard is a part of your DR solution, you really can't afford to pause the recovery process for a long duration for fear of falling behind, so the physical standby database is essentially useless for any read-only activity.
With Oracle Database 11g, that situation changes: You can open the physical standby database in read-only mode and restart the recovery process. This means you can continue to be in sync with primary but can use the standby for reporting. (As in previous versions, you can take the backup from the standby as well.)
refer:- http://www.oracle.com/technetwork/articles/sql/11g-dataguard-083323.html

Data Guard as a pass through?

Scenario is . . .
Host A is the Primary
Host B is a Standby
Host C is a Standby
Now I know we can set up A->B and A->C
Can we set up A->B->C ?
Essentially using B as a pass through between A and C. Or you can see it as B being in a DMZ.
Would B have to be Active Data Guard or anything special?
I guess what I am really asking is can a Standby be used as the source for another Standby.

See http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/cascade_appx.htm#i638620 for more information on Cascaded Standby Destinations. There are a few restrictions:
Cascading has the following restrictions:
* Logical and snapshot standby databases cannot cascade primary database redo.
* SYNC destinations cannot cascade primary database redo in a Maximum Protection Data Guard configuration.
* Cascading is not supported in Data Guard configurations that contain an Oracle Real Applications Cluster (RAC) primary database.
* Cascading is not supported in Data Guard broker configurations.
Keep an eye on this chapter and Note 409013.1 "Cascaded Standby Databases" when the next patch set for 11.2 comes out :^)
Larry

Data Guard - How?

Hi!
What I need to install Data Guard? I read, I need OEM Grid Control too. On download page there are 3 zips! This is more than database software! Am I right? Generally I'm looking for nice "step by step" tutorial for Data Guard.
And License question: Now, I'm using downloable software from Oracle, but later I will use CDs from my customer: 10gR2 EE. Is this version enough?
Thanx,
Jacek

And License question: Now, I'm using downloable software from Oracle, but later I will
use CDs from my customer: 10gR2 EE. Is this version enough?There is no (none, nada, zero, zilch) diffference between the downloaded version and the CD version if the version number is the same.
Long ago, Oracle separated the software from the license. Some consideration:
a) Software
- [Most] Oracle software is free;
- All Oracle software is used under specific license;
b) License
- The license defines the 'right to use' conditions of using the software;
- Some forms of license require associated payment;
Patches
- In this discussion (ie. in my definition), patches are not considered software;
- Patches require paid support;
- Paid support can only be attached to specific 'right to use' licenses (usually for-fee licenses);
And finally, Oracle reserves the right to audit you (and your customers) to make sure you have the correct license for your use.
By the way - Data Guard is part of the database and does not require anything from Grid Control. Go to this page to get help: http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

Clarification on Data Guard(Physical Standyb db)

Hi guys,
I have been trying to setup up Data Guard with a physical standby database for the past few weeks and I think I have managed to setup it up and also perform a switchover. I have been reading a lot of websites and even Oracle Docs for this.
However I need clarification on the setup and whether or not it is working as expected.
My environment is Windows 32bit (Windows 2003)
Oracle 10.2.0.2 (Client/Server)
2 Physical machines
Here is what I have done.
Machine 1
1. Create a primary database using standard DBCA, hence the Oracle service(oradgp) and password file are also created along with the listener service.
2. Modify the pfile to include the following:-
oradgp.__db_cache_size=436207616
oradgp.__java_pool_size=4194304
oradgp.__large_pool_size=4194304
oradgp.__shared_pool_size=159383552
oradgp.__streams_pool_size=0
*.audit_file_dest='M:\oracle\product\10.2.0\admin\oradgp\adump'
*.background_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\bdump'
*.compatible='10.2.0.3.0'
*.control_files='M:\oracle\product\10.2.0\oradata\oradgp\control01.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control02.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control03.ctl'
*.core_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='oradgp'
*.db_recovery_file_dest='M:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=21474836480
*.fal_client='oradgp'
*.fal_server='oradgs'
*.job_queue_processes=10
*.log_archive_dest_1='LOCATION=E:\ArchLogs VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=oradgp'
*.log_archive_dest_2='SERVICE=oradgs LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=oradgs'
*.log_archive_format='ARC%S_%R.%T'
*.log_archive_max_processes=30
*.nls_territory='IRELAND'
*.open_cursors=300
*.pga_aggregate_target=203423744
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=612368384
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\udump'
*.service_names=oradgp
The locations on the harddisk are all available and archived redo are created (e:\archlogs)
3. I then add the necessary (4) standby logs on primary.
4. To replicate the db on the machine 2(standby db), I did an RMAN backup as:-
RMAN> run
{allocate channel d1 type disk format='M:\DGBackup\stby_%U.bak';
backup database plus archivelog delete input;
5. I then copied over the standby~.bak files created from machine1 to machine2 to the same directory (M:\DBBackup) since I maintained the directory structure exactly the same between the 2 machines.
6. Then created a standby controlfile. (At this time the db was in open/write mode).
7. I then copied this standby ctl file to machine2 under the same directory structure (M:\oracle\product\10.2.0\oradata\oradgp) and replicated the same ctl file into 3 different files such as: CONTROL01.CTL, CONTROL02.CTL & CONTROL03.CTL
Machine2
8. I created an Oracle service called the same as primary (oradgp).
9. Created a listener also.
9. Set the Oracle Home & SID to the same name as primary (oradgp) <<<-- I am not sure about the sid one.
10. I then copied over the pfile from the primary to standby and created an spfile with this one.
It looks like this:-
oradgp.__db_cache_size=436207616
oradgp.__java_pool_size=4194304
oradgp.__large_pool_size=4194304
oradgp.__shared_pool_size=159383552
oradgp.__streams_pool_size=0
*.audit_file_dest='M:\oracle\product\10.2.0\admin\oradgp\adump'
*.background_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\bdump'
*.compatible='10.2.0.3.0'
*.control_files='M:\oracle\product\10.2.0\oradata\oradgp\control01.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control02.ctl','M:\oracle\product\10.2.0\oradata\oradgp\control03.ctl'
*.core_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='oradgp'
*.db_recovery_file_dest='M:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=21474836480
*.fal_client='oradgs'
*.fal_server='oradgp'
*.job_queue_processes=10
*.log_archive_dest_1='LOCATION=E:\ArchLogs VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=oradgs'
*.log_archive_dest_2='SERVICE=oradgp LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=oradgp'
*.log_archive_format='ARC%S_%R.%T'
*.log_archive_max_processes=30
*.nls_territory='IRELAND'
*.open_cursors=300
*.pga_aggregate_target=203423744
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=612368384
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='M:\oracle\product\10.2.0\admin\oradgp\udump'
*.service_names=oradgs
log_file_name_convert='junk','junk'
11. User RMAN to restore the db as:-
RMAN> startup mount;
RMAN> restore database;
Then RMAN created the datafiles.
12. I then added the same number (4) of standby redo logs to machine2.
13. Also added a tempfile though the temp tablespace was created per the restore via RMAN, I think the actual file (temp01.dbf) didn't get created, so I manually created the tempfile.
14. Ensuring the listener and Oracle service were running and that the database on machine2 was in MOUNT mode, I then started the redo apply using:-
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It seems to have started the redo apply as I've checked the alert log and noticed that the sequence# was all "YES" for applied.
****However I noticed that in the alert log the standby was complaining about the online REDO log not being present****
So copied over the REDO logs from the primary machine and placed them in the same directory structure of the standby.
########Q1. I understand that the standby database does not need online REDO Logs but why is it reporting in the alert log then??########
I wanted to enable realtime apply so, I cancelled the recover by :-
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
and issued:-
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
This too was successful and I noticed that the recovery mode is set to MANAGED REAL TIME APPLY.
Checked this via the primary database also and it too reported that the DEST_2 is in MANAGED REAL TIME APPLY.
Also performed a log swith on primary and it got transported to the standby and was applied (YES).
Also ensured that there are no gaps via some queries where no rows were returned.
15. I now wanted to perform a switchover, hence issued:-
Primary_SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
All the archivers stopped as expected.
16. Now on machine2:
Stdby_SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
17. On machine1:
Primary_Now_Standby_SQL>SHUTDOWN IMMEDIATE;
Primary_Now_Standby_SQL>STARTUP MOUNT;
Primary_Now_Standby_SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
17. On machine2:
Stdby_Now_Primary_SQL>ALTER DATABASE OPEN;
Checked by switching the logfile on the new primary and ensured that the standby received this logfile and was applied (YES).
However, here are my questions for clarifications:-
Q1. There is a question about ONLINE REDO LOGS within "#" characters.
Q2. Do you see me doing anything wrong in regards to naming the directory structures? Should I have renamed the dbname directory in the Oracle Home to oradgs rather than oradgp?
Q3. When I enabled real time apply does that mean, that I am not in 'MANAGED' mode anymore? Is there an un-managed mode also?
Q4. After the switchover, I have noticed that the MRP0 process is "APPLYING LOG" status to a sequence# which is not even the latest sequence# as per v$archived_log. By this I mean:-
SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS,FROM V$MANAGED_STANDBY;
MRP0 APPLYING_LOG 1 47 452 1024000
but :
SQL> select max(sequence#) from v$archived_log;
46
Why is that? Also I have noticed that one of the sequence#s is NOT applied but the later ones are:-
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
42 NO
43 YES
44 YES
45 YES
46 YES
What could be the possible reasons why sequence# 42 didn't get applied but the others did?
After reading several documents I am confused at this stage because I have read that you can setup standby databases using 'standby' logs but is there another method without using standby logs?
Q5. The log switch isn't happening automatically on the primary database where I could see the whole process happening on it own, such as generation of a new logfile, that being transported to the standby and then being applied on the standby.
Could this be due to inactivity on the primary database as I am not doing anything on it?
Sorry if I have missed out something guys but I tried to put in as much detail as I remember...
Thank you very much in advance.
Regards,
Bharath
Edited by: Bharath3 on Jan 22, 2010 2:13 AM

Parameters:
Missing on the Primary:
DB_UNIQUE_NAME=oradgp
LOG_ARCHIVE_CONFIG=DG_CONFIG=(oradgp, oradgs)
Missing on the Standby:
DB_UNIQUE_NAME=oradgs
LOG_ARCHIVE_CONFIG=DG_CONFIG=(oradgp, oradgs)
You said: Also added a tempfile though the temp tablespace was created per the restore via RMAN, I think the actual file (temp01.dbf) didn't get created, so I manually created the tempfile.
RMAN should have also added the temp file. Note that as of 11g RMAN duplicate for standby will also add the standby redo log files at the standby if they already existed on the Primary when you took the backup.
You said: ****However I noticed that in the alert log the standby was complaining about the online REDO log not being present****
That is just the weird error that the RDBMS returns when the database tries to find the online redo log files. You see that at the start of the MRP because it tries to open them and if it gets the error it will manually create them based on their file definition in the controlfile combined with LOG_FILE_NAME_CONVERT if they are in a different place from the Primary.
Your questions (Q1 answered above):
You said: Q2. Do you see me doing anything wrong in regards to naming the directory structures? Should I have renamed the dbname directory in the Oracle Home to oradgs rather than oradgp?
Up to you. Not a requirement.
You said: Q3. When I enabled real time apply does that mean, that I am not in 'MANAGED' mode anymore? Is there an un-managed mode also?
You are always in MANAGED mode when you use the RECOVER MANAGED STANDBY DATABASE command. If you use manual recovery "RECOVER STANDBY DATABASE" (NOT RECOMMENDED EVER ON A STANDBY DATABASE) then you are effectively in 'non-managed' mode although we do not call it that.
You said: Q4. After the switchover, I have noticed that the MRP0 process is "APPLYING LOG" status to a sequence# which is not even the latest sequence# as per v$archived_log. By this I mean:-
Log 46 (in your example) is the last FULL and ARCHIVED log hence that is the latest one to show up in V$ARCHIVED_LOG as that is a list of fully archived log files. Sequence 47 is the one that is current in the Primary online redo log and also current in the standby's standby redo log and as you are using real time apply that is the one it is applying.
You said: What could be the possible reasons why sequence# 42 didn't get applied but the others did?
42 was probably a gap. Select the FAL columns as well and it will proably say 'YES' for FAL. We do not update the Primary's controlfile everytime we resolve a gap. Try the same command on the standby and you will see that 42 was indeed applied. Redo can never be applied out of order so the max(sequence#) from v$archived_log where applied = 'YES' will tell you that every sequence before that number has to have been applied.
You said: After reading several documents I am confused at this stage because I have read that you can setup standby databases using 'standby' logs but is there another method without using standby logs?
Yes, If you do not have standby redo log files on the standby then we write directly to an archive log. Which means potential large data loss at failover and no real time apply. That was the old 9i method for ARCH. Don't do that. Always have standby redo logs (SRL)
You said: Q5. The log switch isn't happening automatically on the primary database where I could see the whole process happening on it own, such as generation of a new logfile, that being transported to the standby and then being applied on the standby.
Could this be due to inactivity on the primary database as I am not doing anything on it?
Log switches on the Primary happen when the current log gets full, a log switch has not happened for the number of seconds you specified in the ARCHIVE_LAG_TARGET parameter or you say ALTER SYSTEM SWITCH LOGFILE (or the other methods for switching log files. The heartbeat redo will eventually fill up an online log file but it is about 13 bytes so you do the math on how long that would take :^)
You are shipping redo with ASYNC so we send the redo as it is commited, there is no wait for the log switch. And we are in real time apply so there is no wait for the log switch to apply that redo. In theroy you could create an online log file large enough to hold an entire day's worth of redo and never switch for the whole day and the standby would still be caught up with the primary.

What are the pros and cons using Active Data Guard vs Data Guard?

My understanding is that Active Data Guard is an additional database option for Oracle 11gR2 Enterprise Edition. I need to know the pros and cons using Active Data Guard vs Data Guard in order to decide whether to get pay extra for the Active Data Guard.
Thanks for any help.

Hemant K Chitale wrote:
Before jumping in to Active Data Guard, one needs to evaluate :
a. Is there really a need to run queries on the Standby ? The Standby could / should be at a remote site so queries are "across the network". Depending on the nature of the queries and the volume of output, the "performance" of the queries may not seem to be the same.
b. If the database is not in Maximum Protection mode, the data "seen" at the standby may not be in "real-time" synch
c. Not all applications are truely read-only when querying. Some applications use "jobs" that write to tables when querying. Such would not work with Active DataGuard. (example : EBusiness Suite). There are very complicated ways of handling this -- and one needs to consider if the complications can be introduced and supported.
Over the network accessing standby read only is really not an good idea, I think no one will compare performance with primary and standby,
But some of them they want to validate data which are very critical, as it is matching with primary or not, Its an added advantage with ACTIVE DATAGUARD
Prior to that until unless stop MRP, open database and then we need to validate, So there is an interruption of recovery, I can say its also an advantage where there is no interruption of recovery.

Data Guard Broker and Cold Failover clusters

Hi,
I wanted to use Data Guard Broker to control primary/standby systems on AIX clusters but found that without Oracle clusterware it is not supported on failover of a database to another node (unless you drop and recreate the configuration which in my opinion is not support at all!).
The 11g documentation states that DG Broker offers support for single instance databases configured for HA using Oracle Clusterware and "cold failover clusters".
Does anyone know whether this support for cold failover clusters in 11g means "proper support" i.e the configuration detects that the hostname has changed and automatically renames it so it continues to work?, or is the support in 11g the same as that in 10g?.
Thanks,
Andy

Hi Jan,
We already use virtual hostnames.
When I set up the configuration the hostname for the databases default to the server name. The only way I know of changing this is to disable the configuration, then use the "edit database...set property" command but when I enable the configuration again it reverts back to its previous value.
regards,
Andy

Data Guard Broker fails with ORA-16635 and ORA-03135

Hi All,
I configured Oracle RAC with Dataguard 11.2 on Windows 2003.
I've already configured Standby without Data Guard Broker and everything is working fine, but when I try to use Data Guard Broker, he can not synchronize the files from the Data Guard Broker.
I've tried everything including MOS, but not found anything.
I'm getting this error.
From Primary
DG 2011-02-11-09:15:41        0 2 0 NSV1: (MIV = 57) Start sending metadata file: "+DG_DATA/orcl/dgbroker/dg_config_file1.dat"
DG 2011-02-11-09:15:41        0 2 0 NSV1: Sending block #1 (containing MIV = 57), 67 blocks
DG 2011-02-11-09:15:42        0 2 0 NSV1: Error sending block #1, size 67 blocks. Error is ORA-16635.
DG 2011-02-11-09:15:42        0 2 0 NSV1: Current network link for metadata resync is broken.
DG 2011-02-11-09:15:42        0 2 0 NSV1: (MIV = 57) End metadata file transmission: opcode CTL_ENABLE (1.1.1825138532)
DG 2011-02-11-09:15:42        0 2 0 NSV1: Can't send CLOSE message to DRCX. Network error is: ORA-16635.
DG 2011-02-11-09:15:42        0 2 0 NSV1: Error is ORA-03135 connection lost contact
DG 2011-02-11-09:15:42        0 2 0 NSV1: Current network link for metadata resync is broken.From Standby
DG 2011-02-11-08:35:39 3001000 3 1825138419       for opcode = CTL_ENABLE, phase = RESYNCH, req_id = 1.1.1825138419
DG 2011-02-11-08:35:39        0 2 0 NSV2: Error sending block #1, size 67 blocks. Error is ORA-16635.
DG 2011-02-11-08:35:39        0 2 0 NSV2: Current network link for metadata resync is broken.
DG 2011-02-11-08:35:39        0 2 0 NSV2: (MIV = 11) End metadata file transmission: opcode CTL_ENABLE (1.1.1825138419)
DG 2011-02-11-08:35:39        0 2 0 NSV2: Can't send CLOSE message to DRCX. Network error is: ORA-16635.
DG 2011-02-11-08:35:39        0 2 0 NSV2: Current network link for metadata resync is broken.
DG 2011-02-11-08:35:39        0 2 0 NSV2: Metadata Resync failed. Status = ORA-16635
DG 2011-02-11-08:35:39 3001000 3 1825138419 DMON: Database ORCLSTBY returned ORA-16635

Hi,
Are you using firewall between Hosts?
If yes check if firewall is blocking yours connections.
Set the following parameter in the sqlnet.ora file that would be referenced by each database, primary and standby.
SQLNET.EXPIRE_TIME=n
Where n is some number of minutes. Preferably below 10. When this parameter is enabled, a small 10 byte probe packet will be sent from node to node at specific intervals.
Regards,
Levi Pereira

Steps for data guard RAC primary RAC standby

Hi,
I have some doubt in configuring data guard for rac DR to rac primary.
1) In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
2) While configuring RAC DR , should one node be down in standby?.
3) After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR,
Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?.
4) After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?.
If anybody have made the setup and have the prepared document , requesting you to share with me.
Thank you very much,
Sunand

Hi Sunand,
Please follow the following My Oracle Support (MOS) Document ID:
MAA - Creating a RAC Physical Standby for a RAC Primary [ID 380449.1]
For further details, see the referred documents in previous post. Try practicing on VMWare because it will give you the flexibility for creating snapshots to save your work. Please see the answers for your question below:
Q1. In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
Answer: Yes, this is recommend but not mandatory. You can add a second node later on.
Q2. While configuring RAC DR , should one node be down in standby?
Answer: Yes, there are some database configuration commands that should be run in exclusive mode. You can start the remaining instance(s) after DB creation. Do not forget to set CLUSTER_DATABASE parameter to TRUE. Also, all instances except one should be close while performing switchover/failover.
Q3. After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR, Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?
Answer: Yes, this is recommended for RAC configuration to take advantage of high availability services.
Q4. After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?
Answer: You can start up all the instances after DR creation. In this case if your one node goes down log apply services will continue to apply changes in DR.
Hope, this helps to clear your questions.
Regards,
Shahid

DATA Guard Logical Standby v.s. Streams Apply (10gR2, rac -- rac )

Greetings -
We currently have a 3 node cluster, doing a 'Schema' capture, with a 2 node cluster serving as the apply side. Both are on 10gR2 (solaris 10)
We have been experiencing apply latency due to large transactions. The way logminer/streams evaluates the arch logs, it converts each updated row into a transaction as part of a transaction set, using 'decode (' statements.
I am under the impression a physical standby will do the same thing. But what about a logical Standby ?
(this from the Oracle Documentation)
[10g Concepts|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/concepts.htm#SBYDB00010]
...Contains the same logical information as the production database, although the physical organization and structure of the data can be different. The logical standby database is kept synchronized with the primary database though SQL Apply, which transforms the data in the redo received from the primary database into SQL statements and then executing the SQL statements on the standby database.
Does anyone know firsthand if SQL APPLY re-issues the original sql, or if it relies on the 'decode' command as well ?
Thanks
The Nets Edge

A Physical standby does not do anything with SQL. It is running media recovery under the covers. A Logical standby uses the Logminer to read the redo, converts it to SQL and Data and applies those transactions to the Logical standby.
The both build logical change records, figure out order, dependencies etc etc and applies the transaction. Both are susceptible to long running transactions on the Primary (source) database.
Streams uses Logminer, Logical Standby use part of the Streams apply so as Mr. Morgan said, they are very similar :^)
If you are having apply performance issues you may want to look at Active data Guard.
Larry

Data Guard: db_file_name_convert/log_file_name_convert when using ASM/OMF

All,
I have a call currently open with Oracle regarding the setting of the parameters db_file_name_convert and log_file_name_convert in a data guard environment. We use ASM / OMF for storage and file naming and my question is basically do these parameters have to be set. The documentation says they do where the file structure is different between PRIMARY and STANDBY.
I have successfully tested failover and switchover without these parameters. I have also added a new tablespace on the PRIMARY and watched it create a new OMF datafile on standby when the logs are switched.
I just can't see a reason for setting them when using ASM / OMF.
I'm hoping someone can enlighten me here because I'm getting nowhere whith support. The following is our Data Guard setup:
PRIMARY
DB_NAME=IBSLIVE
DB_UNIQUE_NAME=IBSLIVE
ASM Disk Groups:
+PRODDATA (Data Files, Control Files, Redo Logs)
+PRODFLASH (Archive Logs, Flashback Logs, RMAN backups)
+PRODLOGS (Multiplexed Control & Redo Logs)
STANDBY
DB_NAME=IBSLIVE
DB_UNIQUE_NAME=IBSDR
ASM Disk Groups:
+DRDATA (Data Files, Control Files, Redo Logs)
+DRFLASH (Archive Logs, Flashback Logs, RMAN backups)
+DRREDO (Multiplexed Control & Redo Logs)
Many Thanks,
Ian.

Ian,
I'm having similar thoughts.
I have created a new instance with files in asm under +datadisk/obosact (this is the smae name as primary)
I then modify the db_unique_name from obosact to obosactdr as is required for standby to work
When I recover (duplicate target database for standby; ) I find that the files are in datadisk/obosactdr not in the datadisk/obosact area
I found this reference http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
4. Connect to the ASM instance on one standby host, and create a directory within the DATA disk group that has the same name as the DB_UNIQUE_NAME of the standby database. For example: SQL> ALTER DISKGROUP data ADD DIRECTORY '+DATA/BOSTON';
This step seems to indicate that the location of the files is determined by the db_unique_name not the db_file_name_convert paramenter
DId you ever resolve the issue?

Is data guard supported on mainframe zLinux? Anything limitation?

Similar Messages

Maybe you are looking for