WLS 10.3.x setup in Data Guard environment

Hi all,
We are setting up the following environment:
Oracle Database 11.2.0.2 EE RAC primary and physical standby
WebLogic Server (WLS) 10.3.0
We are using MultiDataSource (MDS) per the documentation which is fine. However, this setup requires the data sources to specify the RAC hostnames (VIPs), instance names, and the service name. Per various documents we are not using the SCAN hostname. Considering this is a phsyical data guard environment, how do we set this up so we can have the best 'seamless' transfer of the WLS envrionment when a switchover or failover occurs from the primary to the standby database?
Thus far we've discussed using instead of the RAC virtual hostname (racprd1), a DNS cname (wls-racnode1) which points to racprd1, but we would modify in the DNS to point to racstby1 when a DG switch or failover occurs.
Any thoughts or recommendations otherwise?
Thanks.

OK...
Alter database rename should be ok As long as both the PRIMARY directory strucures are same or if you have set the parameter db_file_name_convert
While asking a question..
You should post all the necessary information for us to help(is possible)
1.Oracle version
2.Os version
Thread spesific
3.Directory strucutrs of Both Priimary and Standby
4.Init .Ora of both PRIMARY AND STANDBY

Similar Messages

ACLs in a Failsafe/data guard environment

Hi,
We have recently upgraded to Oracle Enterprise Edition 11.2.0.3
We had a slight issue with a few batch processes which sent success emails - we hadn't configured ACL permissions (We knew about it, and was on the log, but somehow got missed). All set up fine now in our test environment, but got a couple of queries before I set up in production.
Had a look in the documentation and tried searching
The ACLs I believe are managed as an XML file, on the database server, correct?
If so, how do we manage this on both a clustered, and a data guard environment? Or in the case of a database restore? Is the ACL file automagically regenerated out of some database metadata? Or do we need to recreate in each environment?
Any ideas?
Cheers,
Carl

Hi,
there is two ACL(Access Control List) one at Db level ans one is used at UNIX command for file permission , as you mentioned you have permission issue in batch execution.
so you can check below link
http://www.dartmouth.edu/~rc/help/faq/permissions.html
i am not sure which ACL you required.

Switchover in a data guard environment using Grid Control 10.2.0.3

I've tested switchover in a data guard environment using Data Guard Broker in Grid Control.
However, at times, i receive the message "RemoteOperationException: failed to establish input streaming thread". It looks like it has problems connecting to the remote node using the host credentials supplied. I know the credentials are ok because this worked before. If i test preferred credentials, it's ok too..
The workaround has been to restart the database and this seems to work.
Has anyone experienced this?

Thanks for All for replying.
*1. How can I upgrade my Grid control 10.2.0.3 to 10.2.0.4?*
I have upgraded the Grid Control Agent and OMS from 10.2.0.3 to 10.2.0.4
When we upgrade the OMS which also upgrade the Repository database.
Apply the patchset p3731593_10204_Linux-x86-64.zip (Which comes with Grid_Control_10.2.0.4.0_Linux-x86-64.zip)
su - oracle
cd 3731593/Disk1
./runInstaller (Run two times for Agent and oms upgrade)
Agent upgrade_
During upgrade
Specify Home Details: Select the Agent Home to upgrade Grid Control Agent.
Ex: /u01/app/oracle/OracleHomes/agent10g
OMS upgrade+
Specify Home Details: Select the oms home to upgrade oms
Ex: /u01/app/oracle/OracleHomes/oms10g
*2. How can I monitor/Connect my Existing database 10.2.0.4 from Grid Control 10.2.0.3?*
Install Grid Agent on the existing database server 10.2.0.4
Download Linux_x86_64_Grid_Control_agent_download_10_2_0_4_0.zip from OTN http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
su - oracle
cd /u01/software/GridAgent/linux_x64/agent
./runInstaller
Refer:
[To Install an Additional Management Agent Using OUI|http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/installing_em.htm#sthref318]
OracleÂ® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 4 (10.2.0.4)
Part Number E10953-05
3 Installing Enterprise Manager
Thanks
Mukarram Khan
Edited by: Mukarram Khan on Feb 6, 2009 11:04 PM

How many physical standbys can be created in one data guard environment?

Hi Experts,
How many physical standbys can be created from primary in one data guard environment? Why LOG_ARCHIVE_CONFIG limits up to 9 unique database names? Thanks.

Victor Jin-Oracle wrote:
Hi Experts,
How many physical standbys can be created from primary in one data guard environment? Why LOG_ARCHIVE_CONFIG limits up to 9 unique database names? Thanks.
Post the source of your information abouit the limit of 9 names.
Even the Oracle doc shows 1..30 names in the same provided although that doesn't necessarily indicate a limit.
https://docs.oracle.com/database/121/REFRN/refrn10237.htm

Multiple Location of datafiles in Data Guard Environment

I have Data Guard setup in my oracle 10g database. Uptil now , all the datafiles were at same location, therefore db_file parameter setting in pfile was fine. Now I want to move my few of the datafiles at another location. Say, few of my datafiles would be in F:\ and some of them in G:\. How do I now set db_file parameters in Pfile ?

OK...
Alter database rename should be ok As long as both the PRIMARY directory strucures are same or if you have set the parameter db_file_name_convert
While asking a question..
You should post all the necessary information for us to help(is possible)
1.Oracle version
2.Os version
Thread spesific
3.Directory strucutrs of Both Priimary and Standby
4.Init .Ora of both PRIMARY AND STANDBY

Oracle 11g Goldengate working in a Data Guard environment

Hey Guys, I have the following setup:
Oracle 11.2.0.4.4 running on RHEL 6.6 64-bit
3 node RAC Primary
Single-node Standby with GI (Oracle Restart)
4 DBs on Primary - AA, BB, CC and DD
4 DBs running in Active Standby - AADR, BBDR, CCDR and DDDR
Databases AA and BB replicate schemas into CC, which is a Reporting/Operational Data Store. GoldenGate 11.2.x is used for the replication
XAG used for Goldengate HA
All good here with the Primary DBs and replication humming along quite nicely.
I have questions as part of building the DR environment. How should this work? As part of the real-time apply and active standby, CCDR should keep pace with the replicated primary DB CC. Now from a role transition perspective, I need to be have the GoldenGate software installed and configured on the Standby Server for starting the processes.
Question 1: When the role transition happens, based on the data guard role, I could well have a system trigger to spawn off a shell script that starts off the goldengate processes. Would this be the correct approach?
Question 2: Do I need to worry about setting/starting the extract/replicat from a specific CSN? The checkpoint table will be kept in sync as part of the SQL apply, so would just starting the extract and replicat process on the new Primary (old DR) work?
I am unable to get any pointers on this in Metalink. Would appreciate anyone could point me to a MOS document that talks about using GG and Data Guard together.
Thanks

On the first day, there is no backup to recover. It is only on the third day's run that this command will really be successful.
The white paper does explain this.
Hemant K Chitale

Backuping up a standby database in a Data Guard environment!

Hello everyone,
I have set a Data Guard in Oralce 10.2.0 between 2 databases for testing purposes. Each database is located on a different server. I want to schedule an incremental backup of the standby database to do an incremental level_1 backup everyday. I am following this paper:
[Using Recovery Manager with Oracle Data Guard in Oracle Database 10g|http://www.oracle.com/technetwork/database/features/availability/rman-dataguard-10g-wp-1-129486.pdf]
but it's really unclear, for me, how this command sequence is constructed:
RECOVER COPY OF DATABASE WITH TAG ‘OSS’;
BACKUP DEVICE TYPE DISK INCREMENTAL LEVEL 1 FOR
RECOVER OF COPY WITH TAG ‘OSS’ DATABASE;
BACKUP ARCHIVELOG ALL NOT BACKED UP TO SBT;
BACKUP BACKUPSET ALL;How can I recover a copy of database that wasn't backed up before? When I did that in RMAN, I got the following output:
Starting recover at 03-APR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=159 devtype=DISK
no copy of datafile 1 found to recover
no copy of datafile 2 found to recover
no copy of datafile 3 found to recover
no copy of datafile 4 found to recover
no copy of datafile 5 found to recover
Finished recover at 03-APR-11Could anyone please help me understanding this sequence of commands in a simple way to get a better idea of how to backup a standby database?
Thanks in advance...

On the first day, there is no backup to recover. It is only on the third day's run that this command will really be successful.
The white paper does explain this.
Hemant K Chitale

Applying recommended patch bundles to a Data Guard environment.

I've learned that there are 3 recommended patch bundles for 10.2.0.4 Data Guard, as follows:
7937113 - 10.2.0.4 Data Guard Logical Recommended Patch Bundle #1
7936993 - 10.2.0.4 Data Guard Physical Recommended Patch Bundle #1
7936793 - 10.2.0.4 Data Guard Broker Recommended Patch Bundle #1
My question is this...should I apply the logical and physical patch bundles to the primary database as well?
Thanks,
Michael Anderson
OCP - Bank of the West

That's what I suspected. Now, in my environment, I could never conceive of a situation where I would switch roles between the primary and the logical standby database, so I would only apply the DG physical patch bundle to the primary database but not the DG Logical patch bundle. Agree?

RMAN restore UNTIL SCN in DATA GUARD environment

Hello,
OS=RHL5
DB=11.2.0.3 Primary and 1 Physical STANDBY database.
I have a huge application changes tomorrow and its possible that I have the requirement to ROLLBACK the database 5 hours back because the application.
I am thinking to adopt following method from the official Oracle documentation (untilClause):
STARTUP FORCE MOUNT
RUN
SET UNTIL SCN 1418901; ## Any required SCN number will be used here.
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
I will of course take LEVEL0 backup tonight and LEVEL1 backup before the start of work.
My humble question to you is that: If this is the correct method I am adopting? and if yes, then what about Physical standby database? Will there something to restore/recover too? or it's not required or standby database need to create again (which I am afraid of)?
Flash back is not enabled.
Bundle of thanks for the suggestion.
Best Regards

hello John-MK,
My humble question to you is that: If this is the correct method I am adopting?
the method is correct but not the BEST PRACTICE...create a RESTORE POINT instead of using SCN. for example:
SET UNTIL RESTORE POINT before_app_changes;
1. drawbacks of using flashback feature are:
a. you need more disk space
b. there is CPU overhead associated with flashback log operation
c.compulsorily need to use fast recovery area and you can not backup flashback log
d.others..
but my own opinion, i think the advantage out weight the drawbacks, since you are paying for it already
2. if the standby database did not apply redo data past the new resetlogs SCN, then you do not need to re-build. no manual intervention
HTH
Tobi

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.

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?

Oracle 11g Active Data Guard help ?

Hi Friends,
I successfully setup an Active data guard environment(11g). But, I dont know when the PROD database is highly utilize , its read only tasks like reporting and backup are doing in STANDBY. How can I know which db (prod or stand by) is used for these readonly operations ?
Regards
Vish

It is not so simple to direct reports to the Physical Standby as you seem to assume.
You need to do some work for the setup.
See here for a description:
http://uhesse.com/downloads/real-time-query-presentation/
Kind regards
Uwe Hesse
Don't believe it, test it!"
http://uhesse.com

Data guard difference in primary and standby OS.

Dear All,
We are planning to setup a data guard in our landscape. But my question what are the prerequisites should be consider before getting in to that.
Like my environment -
1. The primary database is running with Red hat Linux 5 - IBM 64 bit and the standby database is Redhat Linux 2.1 IBM 32 bit system.
2. The primary database is running with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 and the standby database is
Linux 2.1 IBM 32 bit system with oracle 10g.
Is the above thing is possible? or we should maintain the same OS / DB combination in the data guard setup.
I am following the below link.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/standby.htm#i72053
If anyone have thoughts on this please do advice me.
Regards
Vijay

Please explain to us what exactly you want to do with the standby database?
According to note 105047 - Support for Oracle functions in the SAP environment
12. Data Guard
You can use "Physical Standby", but Oracle provides support (not SAP).
You cannot use "Logical Standby"
So in short, no a data guard configuration with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 to Linux 2.1 IBM 32 bit system with oracle 10g is NOT possible.
Regards, Michael

Data Guard broker compatiblity

Hi All,
I have environment where we are running following version of databases
1- Oracle 9.2.0.6
2- Oracle 10.2.0.1
3- Oracle 10.2.0.2
4- Oracle 10.2.0.3
5- Oracle 10.2.0.4
6- Catalog DB 11.2.0
My question is whether 10g/11g data guard will support these databases?
Thanks in advance.

The dataguard broker (basically that is the DMON background process) is always from the same version as the database.
Maybe you confuse Grid Control with the dataguard broker. Indeed can a higher versions Grid Control maintain lower versions databases.
It may also setup & maintain Data Guard for these lower versions databases.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Active data guard 11gr2

hi,
I want to setup Active Data Guard Oracle 11gr2. This is my first time. Is there any good guide or cookbook for setting up active data guard 11g. I want to setup on linux. I'll be thankful.
thanx

There's not so much to configure, it's only a sequence of statements:
http://download.oracle.com/docs/cd/E11882_01/server.112/e22491/manage_ps.htm#sthref597
More important - not technical - point is you need an extra licence.
In fact Real-Time Query means Active DataGuard.
Edited by: oradba on 05.10.2011 11:49

WLS 10.3.x setup in Data Guard environment

Similar Messages

Maybe you are looking for