One primary and two physical standby database creation

hi
i want to create two standby (physical) and one primary dataguard.
so please tell me what is sequence for db_file_name_convert and db_file_name_convert.
i mean how i will give database name or path in this parameter.

Hello;
One option is Data Guard Cascading Standby.
Here are my complete test notes if it help :
http://www.visi.com/~mseberg/Data_Guard_Cascading_Standby_Setup_and_Test.pdf
Best Regards
mseberg

Similar Messages

One primary and two Physical standby

Hi everyone,
I want configure two separate Physical standby one work in Redo apply and one in log apply mode.
is it posible?

user011232 wrote:
Hi everyone,
I want configure two separate Physical standby one work in Redo apply and one in log apply mode.
is it posible?Yes it can possible very much. You have to configure as below in remote destinations.
Example_:-
Log_archive_dest_2='service= stby1 lgwr async ';
Log_archive_dest_3='service= stby2 arch async ';
What is the plan behind that? just for testing purpose? Even me too not tested but you can try configuring as above. :)
Edited by: CKPT on Feb 14, 2012 5:46 PM

Physical Standby Database Creation with RMAN

Hi,
I'm in 10g on Linux. I want to create a standby database on another Linux server. I did not find a clear procedure to create it in Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02
and niether in Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-04
In the last one chapter 3 sends you to F appendix and F appendix says do nothing before having than all in chapter 3 :
In F.1.1 page F-2 it is said :
See Chapter 3 for a complete discussion of physical standby database preparation,including initialization parameter settings. You must perform all necessary preparation tasks described in these chapters before RMAN can successfully create the standby database files and mount the standby database.
Any way I'm looking for a procedure or clear article to create it.
Many thanks before.

Physical Standby Database Creation with RMAN
Use the DUPLICATE command.
Check out this metalink doc: Note:374069.1 and Note:118409.1
Message was edited by:
STW
Message was edited by:
STW

How to stop and cancel physical standby database (ORACLE 10g)

Dear All,
I have physical standby setup and I want stopped for the time being that to use the database as an normal DB (standalone inestance).
Kindly advise and show me how do I do that.
Regards,

executing below query on primary db stops log shipping to standby.......i think this is sufficient for disabling your physical standby setup temporary
alter system set log_archive_dest_state_2=defer scope=both;
In future if you want your dataguard setup back..............you can rebuild the standby and enable the log_archive_dest_state_2 parameter.
Edited by: Veeresh.S on Nov 14, 2012 5:45 PM

Lost one primary and two extended partitions - testdisk isn't working

Hey everyone... long time no see. I needed a break
("Conclusion" below if the following is TL;DR)
Background:
First up... don't pull the plug on your PC, even if you are over-fatigued, and try to minimize the number of times you have to force-switch your system off. Read on if you would like to know why.
About four days ago, I was working on something, and everything was all good. Nothing was wrong, awry, or weird, and the only thing I could've written home about my partition structure was that cfdisk showed all the metadata for my extended entries.
That all changed one simple reboot later.
Three days ago, I greeted a system that booted up perfectly, and before entering X I decided to work on a document in textmode. Once I'd had enough of that, I fired up X and continued working on some changes to the QEMU VGA BIOS that makes it look like an old 512K VGA card from 1991 that I have. Or rather, tried to. I fired up my editor and a console and tried to compile... and /stuff, /dev/sda4, wasn't mounted. No problem; it isn't in my fstab. I should get around to adding it one da--whoa, what the...? /dev/sda4 is SWAP?!
It got worse from there. Three days ago I was extremely fatigued because I left a CRT plugged in that I don't usually plugged in (and I didn't know until the next morning!), and being tragically sensitive to radiation, I was rather unreasonable (and had been all day, even while away from the computer), so didn't think clearly about what I did next.
First, I proceeded to use cfdisk to change the partition type from 82 (Swap/Solaris) to 83 (Linux). The partition table decided not to "catch", so cfdisk pointed out that the prudent thing to do would be to reboot, which I ignored (major failure #1) and fired up TestDisk to try and fix (major failure #2) and was like "Enter, enter, enter, enter, enter, enter, ^C, reboot" (catastrophic failure #1).
***************** FILESYSTEM CHECK FAILED ****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
The rest was history, unfortunately.
I had a 26GB "hole" of free space in my hard disk and... eek. Deciding I'd done enough damage, I fought off my OCD/Autistic "GAH, the computer is DEAD, DO SOMETHING" and got some sleep.
The next day (the day I discovered the CRT was off but plugged in) I decided to have a crack at fixing the problem.
Conclusion:
Worst case scenario, I thought, would be that the 26GB of data was simply gone, and best case, I'd have a ~5GB hole in the disk someplace that would hold my two Syllable AFS partitions (partition type 2A), which I was sure no utility I knew of would be able to figure out. I was almost completely correct: I got my 17GB /storage partition back (WHEW), but I lost my two Syllable partitions as well as a third primary partition of unknown filesystem type.
Here's my evidence:
Going through /var/log reveals files showing lines like
messages.log.2:May 14 10:27:53 hornet sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 > sda4
This proves that sda4 did once exist as a real partition and wasn't mountable as the result of a freak accident on the disk.
In addition, sda4 is indicated to be a primary partition at the end of my extended partitions. This makes me wonder what on earth's happened here, because I only have a single "Free Space" hole inside my extended header, not after it. Did the extended partition header somehow manage to get resized? :S
I remember - and have the .bash_history to prove - that I chowned and chgrp'd /stuff (ie /dev/sda4) such that I could read/write it as my own user, and this isn't possible with FAT* partitions - you have to dive into /etc/fstab to make them user-writable, and I know I didn't do that. So this partition is possibly ext2, ext3, or JFS (and I'm thinking JFS).
While probably not useful, the fact that the "Free Space" hole is after sda9 but before sda10 lines up with the fact that I had to move sda12 and 13 (a FAT32 partition as well as a JFS partition, the one I mount at /storage) down two notches in order for my system to boot up without complaint.
TestDisk is only listing what I've already got fixed and in working order at this point. In other words, it isn't seeing the other partition. Incidentally, PhotoRec, a program analogous to TestDisk, probably wouldn't be useful here since I doubt that partition contains images.
-dav7
Last edited by dav7 (2009-06-24 04:10:59)

You really got yourself into a big mess ....
As for the partitions magically changing places .... have you recently used gparted (or parted which I believe is the program that actually does the changes) to resize or move any partitions? If you have that's the reason why the partition table is so messed up.
If testdisk can't fix that I have no idea of what can ... once I had a similar problem and testdisk saved the day but I had only ntfs/ext3/swap/extended primary partitions and logical ext3/ntfs partitions.

Upgrading the primary and physical standby database

Solaris 9
oracle 9i (9.2.0.8)
upgrade to 10g (10.2.0.3)
Hi,
I would like to know how to upgrade database in dataguard envronment.(primary and remote physical standby database)
Is rolling upgrade possible in this case?
Or any steps or Document is appreciated.
Thanks.
Message was edited by:
user539835

Read this Metalink Note:407040.1

Problem discovering 9.2.0 physical standby database in 10GR1 OEM

We have a Dataguard test setup in our company which was done using 9.2.0 OEM consisting of two 9.2.0 databases(one primary and another physical standby).
I could get the 10GR1 agent discover the primary database properly, but couldnot discover the physical standby database? The 10GR1 agent on the remote host is running fine, but just not discovers the database that is in physical standby mode and running fine.
Any suggestions???

Have you tried manually adding the standby?
Note that in grid, in the monitoring configuation screen, use the sys as sysdba account, dbsnmp doesn't have enough privileges.
Bazza

Configuring both logical and physical standby databases.

Hi,
I am trying to set up one primary and two standby databases which are physical and logical. together. What I am wondering is if i tis posiible to set both log_archive_dest_n parameters in init.ora of primary db to 'LGWR ASYNC'.. I tried to do that but I noticed that while redo data goes the first remote log destination including LGWR statement properly but for the second it does not.
So my assumption is only one remote archive dest. can be set for the LGWR process. Is ıt right?
Regards
ALPER ONEY
email:[email protected]

Hi,
when I set remote archive dest _n parameter for logical standby database to the value like 'LGWR AYSNC' and for the phy. standby to 'ARCH', it is ok. But if I change both parameters to 'LGWR'. I can see that only one destination receives the redo data and this destination is also the first destination configured for receiving redodata . I am just wondering that LGWR process is able to serve two or more to destinations at the same time. If it is ok, I am wrong and I better to try harder to solve the problem. I read the Dataguard document for 10GR' and the example for the case I created (two standby databases),, it uses ARCH process to send redo data and so everything is ok in that example.
P.S I also configured standbys for real time apply.
Waiting for your comments.
Regards.
ALPER ONEY

Backups on Physical standby database?

I am using dataguard and a physical standby database.How to assign backups on physical standby database to reduce the load on Primary database.
environment: windows
Database version:11.2.0.1.0
What are the pro and cons on assigning RMAN backups jobs to physical standby database?

Is it better to assign the RMAN backups on standby?i am using the RMAN catalog.Yes, Already mentioned to reduce contention on primary. You can register even standby.
Do i need to change the setting to backup archive logs from standby database? If i won't backup the archive logs on Primary the FRA will be full and i can't access it ?You can include even archive logs with your database backup.
How to assign the archive logs backups,full backup on standby database?Same script will work, Before that cancel MRP and after backup start MRP. That should be fine.
Recently i tested backup from standby and restore, Please see below log.
=================================================================================================
Backup Scrpts:-
=================================================================================================
RMAN> run
2> 3> ALLOCATE CHANNEL dev11 type disk;
4> backup as compressed backupset
5> format '/home/oracle/backup/DBF_FULLCOLD_BKP_%s'
6> filesperset 30
7> (database);
backup current controlfile format
8> 9> '/home/oracle/backup/CTL_FULLCOLD_BKP_%s';
RELEASE CHANNEL dev1;
RELEASE CHANNEL dev2;
10> 11> 12> }
using target database control file instead of recovery catalog
allocated channel: dev11
channel dev11: SID=1 device type=DISK
Starting backup at 03-FEB-13
Starting implicit crosscheck backup at 03-FEB-13
Finished implicit crosscheck backup at 03-FEB-13
Starting implicit crosscheck copy at 03-FEB-13
Crosschecked 4 objects
Finished implicit crosscheck copy at 03-FEB-13
searching for all files in the recovery area
channel dev11: starting compressed full datafile backup set
channel dev11: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf
channel dev11: starting piece 1 at 03-FEB-13
channel dev11: starting compressed full datafile backup set
channel dev11: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf
channel dev11: starting piece 1 at 03-FEB-13
channel dev11: finished piece 1 at 03-FEB-13
piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_23 tag=TAG20130203T192535 comment=NONE
channel dev11: backup set complete, elapsed time: 00:03:57
channel dev11: starting compressed full datafile backup set
channel dev11: specifying datafile(s) in backup set
including current control file in backup set
channel dev11: starting piece 1 at 03-FEB-13
channel dev11: finished piece 1 at 03-FEB-13
piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_24 tag=TAG20130203T192535 comment=NONE
channel dev11: backup set complete, elapsed time: 00:00:02
Finished backup at 03-FEB-13
Starting backup at 03-FEB-13
channel dev11: starting full datafile backup set
channel dev11: specifying datafile(s) in backup set
including current control file in backup set
channel dev11: starting piece 1 at 03-FEB-13
channel dev11: finished piece 1 at 03-FEB-13
piece handle=/home/oracle/backup/CTL_FULLCOLD_BKP_25 tag=TAG20130203T192939 comment=NONE
channel dev11: backup set complete, elapsed time: 00:00:03
Finished backup at 03-FEB-13
released channel: dev11
=================================================================================================
Backup Files:-
=================================================================================================
[oracle@oracle-stby backup]$ ls -ltr
total 364572
-rw-r----- 1 oracle oinstall 361684992 Feb 3 19:29 DBF_FULLCOLD_BKP_23
-rw-r----- 1 oracle oinstall   1163264 Feb 3 19:29 DBF_FULLCOLD_BKP_24
-rw-r----- 1 oracle oinstall 10092544 Feb 3 19:29 CTL_FULLCOLD_BKP_25
[oracle@oracle-stby backup]$
=================================================================================================
Restore CONTROL FILE:-
=================================================================================================
RMAN> restore controlfile from '/home/oracle/backup/CTL_FULLCOLD_BKP_25';
Starting restore at 03-FEB-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u02/app/oracle/oradata/orcl/control01.ctl
output file name=/u02/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 03-FEB-13
RMAN> sql 'alter database mount';
sql statement: alter database mount
released channel: ORA_DISK_1
RMAN>
=================================================================================================
Restore Database:-
=================================================================================================
RMAN> restore database;
Starting restore at 03-FEB-13
Starting implicit crosscheck backup at 03-FEB-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
Crosschecked 2 objects
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
Sun Feb 03 19:37:47 2013
Checker run found 4 new persistent data failures
Sun Feb 03 19:38:40 2013
Full restore complete of datafile 3 /u01/app/oracle/oradata/orcl/undotbs01.dbf. Elapsed time: 0:00:56
checkpoint is 1595132
last deallocation scn is 1519218
channel ORA_DISK_1: piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_23 tag=TAG20130203T192535
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:02:07
Finished restore at 03-FEB-13
RMAN>
=================================================================================================
Open Database:-
=================================================================================================
SQL> alter database open resetlogs;
Database altered.
SQL> select open_mode,database_role from v$database;
OPEN_MODE            DATABASE_ROLE
READ WRITE           PRIMARY
SQL>Edited by: CKPT on Feb 21, 2013 11:24 PM

Physical standby database Version 11g Creation over grid control 10g

We are useing oracale 11g enterprise edition and want to create a physical standby database on another machine:
On primary host we've installed "standard database" and turned on archive log mode over em.
On the standby host we've installed only oracle without a database and without a listener.
On a third machine we've installed grid control and registered the primary and standby hosts. Using EM with Data Grid I'm attempting to create a Physical Standby on standby host. Everything is working except for the last part as noted here:
SQL*Plus: Release 11.1.0.6.0 - Production on Do Apr 3 11:21:17 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> SQL> Bei einer nicht hochgefahrenen Instance angemeldet.
SQL> SQL> ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE-Instance hochgefahren.
Total System Global Area 535662592 bytes
Fixed Size          1334380 bytes
Variable Size          167773076 bytes
Database Buffers     360710144 bytes
Redo Buffers          5844992 bytes
SQL>
Datenbank wurde geändert.
SQL> Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSTEM01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSAUX01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\UNDOTBS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\USERS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\EXAMPLE01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO01.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO01.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO02.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO02.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO03.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO03.log'
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 1
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 2
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 3
dgcreate.DGgetRecoverySCN: SELECT MAX(NEXT_CHANGE#) FROM V$ARCHIVED_LOG
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER AUTOMATIC FROM '%ORACLE_HOME%\RDBMS' STANDBY DATABASE UNTIL CHANGE 1061001
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER CANCEL
dgcreate.DGrecoverStby: ALTER DATABASE OPEN READ ONLY
SQL Error: ORA-16004: Sciherungs-Datenbank muss wiederhergestellt werden
ORA-01152: Backup-Datei zum Wiederherstellen der Datei 1 war nicht alt genug
ORA-01110: Datendatei 1: 'C:\ORACLE\PRODUCT\11.1.0\DB_1\ORADATA\DG3\SYSTEM01.DBF' (DBD ERROR: OCIStmtExecute)
What is to do?
What mean's in this case:
"ORA-01152 file string was not restored from a sufficiently old backup
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery."

Thanks for your immediate reply,
but there's a problem: We don't create the standby database manually. The creation is done by data guard over grid control. And the "automatic" creation stopps at this point.
Unfortunatly we don't know, wich steps of a manuall standby database creation are done and wich steps are not done at this point.
The oracle documentation (for release 11g) to create a manuall standby database is "B28294-02". But there's no step 5 "alter database recover managed standby database disconnect from session". Do you mean step 4 of chapter 3.2.6?
Is there no way, to create a standby database automatically over grid control? Or do we have to do something else before creating the physical standby database? Perhaps we have to create a full backup after switching to archive log mode?

SQL exception during creation of a physical standby database with EM

Version: EM Oracle 10.2.5 (agents running, repository running, primary db running, all targets visible and reachable with EM)
I try to create a physical standby database with the enterprise manager and each time the process is aborted with a SQL exception during the preparation of the job by the EM. I have added a part of the OMs log containing the error at the end of the excerpt.
=============
2010-04-29 16:00:39,856 [EMUI_16_00_39_/console/targets] WARN pref.SubtabPref getFolders.710 - Unknown folder id: VirtualServers retrieved from repository
2010-04-29 16:01:04,765 [EMUI_16_01_04_/console/database/dataguard/create] ERROR em.dataguard validate.1329 - CreateBean: ClassNotFoundException: null
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone checkSetFileError.79 - DatabaseFileAttributes.checkSetFileError(): Null database file!
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone setControlfiles.160 - DatabaseFileAttributes.setDatafiles(): Invalid control file!
2010-04-29 16:02:05,492 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone getControlFileNames.616 - DatabaseFileAttributes.getDatafileNames(): null datafile names!
2010-04-29 16:02:32,823 [Thread-28] ERROR em.jobs remoteOp.2389 - DBVerify.remoteOp(): Error: max_stamp# 6071384
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3297 - DBCloneObject.submitJobPreparation(): getMaxLogSequenceNum: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3501 - DBCloneObject.submitJobPreparation(): Exception: java.lang.Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitDBCloneJob.3716 - DBCloneObject.submitDBCloneJob(): Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:37,496 [EMUI_16_02_37_/console/database/dataguard/create] ERROR em.dataguard onEvent.1243 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
=========
I have set the agent perl script tracing to DEBUG, but can't find any reason, why the job preparation failed.
Has anyone an idea why the job cannot be prepared? Thanks in advance for investigation :-)

Can you please tell me how can i see data gaurd on EM..
I have oracle 11gR1..i have implemmented primary as well standby database..
I have already started EM but i have no idea where to find datagaurd option..or how to create standdby db using EM..
You got error that means u did it using EM..how can i do it on EM

More than One Physical Standby Database

Hi All!
Is it possible to have more than one physical standby database? Does the procedure on how to create a single physical standby is the same as creating more than one? How about the configuration of the Primary database? Im planning this because I want the other physical standby to be used for read only access for our testing environment.
Please enlighten me.
Regards,
cmadiam

Think about it.
Q. What's the crux of Dataguard setup?
A. Redo transfer from primary to standby
Q.Which is the parameter you use to direct the redo transfer
A. LOG_ARCHIVE_DEST_n
Q. How many LOG_ARCHIVE_DEST_n parameters can be set?
A. 10; LOG_ARCHIVE_DEST_1 to LOG_ARCHIVE_DEST_10
Of the 10 LOG_ARCHIVE_DEST_n, one of them should be LOCAL destination, which means you can have 9 other REMOTE destinations ~~ 9 standby database. Physical or logical or mix of both.
Cheers.
Note: Each of the 9 standby database can cascade redo transfer to 9 other cascaded standby databases. WOW! now you do the math.

Difference between physical standby database and Data Guard

Hi guys,
Today I attended one interview. They asked me a difference between the Oracle Physical Standby database and Oracle Dataguard?
Upto my knowledge Oracle Physical Standby Database is one type of Standby Database can be configured using Oracle Databaguard Feature.
Can you people calrify me on this.
Regards,
Vijayaraghavan K

hello,
yes you are right upto some extent...here is para form oracle doc
Oracle Data Guard is the most effective and comprehensive
data availability, data protection, and disaster recovery solution
for enterprise databases. It provides the management, monitoring,
and automation software infrastructure to create and maintain one
or more synchronized standby databases to protect data from failures,
disasters, errors, and corruptions.
Data Guard standby databases can be located at remote disaster
recovery sites thousands of miles away from the production data center,
or they may be located in the same city, same campus,
or even in the same building. If the production database
becomes unavailable because of a planned or an unplanned outage,
Data Guard can switch any standby database to the production role,
thus minimizing downtime and preventing any data loss.oracle data guard is maximum availiblity solution which maintain physical standby databases and in case of failure of production can switch production role to and standby database.
read it here
http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html
thanks and regards
VD
Edited by: Dixit on Aug 31, 2009 1:35 AM
Edited by: Dixit on Aug 31, 2009 1:36 AM

Issue with physical standby database not in sync with primary

Hi,
I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
SQL> select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 7
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
RFS OPENING 1 12
ALERT LOG :
Tue Mar 20 07:31:32 2012
alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:32 2012
Attempt to start background Managed Standby Recovery process (PRIMARY)
MRP0 started with pid=18, OS id=16370
Tue Mar 20 07:31:32 2012
MRP0: Background Managed Standby Recovery process started (PRIMARY)
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 8 processes
Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
Tue Mar 20 07:31:39 2012
Completed: alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:54 2012
Incomplete recovery applied all redo ever generated.
Recovery completed through change 9677325080303
Tue Mar 20 07:31:54 2012
MRP0: Media Recovery Complete (PRIMARY)
Tue Mar 20 07:31:55 2012
MRP0: Background Media Recovery process shutdown (PRIMARY)
Thanks,
Rakesh

HI CKPT,
Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
36 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/STDBY/arch/
Oldest online log sequence 13
Next log sequence to archive 0
Current log sequence 14
SQL> ho ls -ltra /oracle/STDBY/arch/
total 3754456
drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
-rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
-rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
-rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
-rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
-rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
-rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
-rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
-rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
-rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
-rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
-rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
SQL>

Steps for Data Guard with one primary and 2 standby

Hi,
Database :10.2.0.4, 11.2.0.1
Os: Windows , Unix
A ----------------> Primary database
B ----------------> Standby Database 1
C ----------------> Standby Database 2
I want to configure *2 standby* databases for single primary database.
Lets take, A ,B and C are my machines.My data guard configuration will be like,*archive logs will be moving* from A to B and A to C.
If i do any switchover in between A and B , now B is primary and remaining A and C are standby databases.At this stage also , archive logs should move from B to A and B to C. Also, same should happen from C to A and C to B,If i do switchover in between B and C.If everything is fine , then i will do switchback to main Primary database(A).
How do i have to mention PFILE in all machines ,the parameters like
LOG_ARCHIVE_DEST_1=LOCATION=<PATH> -- LOCAL ARCHIVE PATH
LOG_ARCHIVE_DEST_2=SERVICE=
LOG_ARCHIVE_DEST_3=SERVICE=
FAL_SERVER=
FAL_CLIENT=
STANDBY_FILE_MANAGEMENT=
In my tnsnames.ora , primary,standby1 and standby2 are my service entries and these are same in all of my machines.
Please suggest me , how do i can configure my pfiles in all machines ?.
Thanks,
Sunand

Not yet, but now you have me interested.
Please consider Flashback.
I still have to test but here's my take:
PRIMARY SETTINGS
*.FAL_SERVER=STANDBY
*.FAL_CLIENT=PRIMARY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=PRIMARY
*.LOG_FILE_NAME_CONVERT='STANDBY','PRIMARY'
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_DEST_STATE_3=ENABLE
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY 1 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_2='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY2 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY2
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY2
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY2'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY2'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
Edited by: mseberg on Nov 29, 2010 9:39 AM
The first test slapped me. Looking at 409013.1 Cascaded Standby Databases
Edited by: mseberg on Nov 29, 2010 12:49 PM

One primary and two physical standby database creation

Similar Messages

Maybe you are looking for