RAC to single instance Data Guard Physical Standby


SHUTDOWN STANDBY DATABASE
step 1: Disable standby archive writing:

Primary/production database

step 2: auto recovery standby de deaktif edilir.

PS: In case of RAC: above command should run on just ONE of the standby RAC node.

RAC ortamında tüm stanby node larda uygulanmalı

STARTUP STANDBY DATABASE
Gerek olursa archivelog lar standby a taşınır.

Step 2: standby database açılır ve automatic recovery başlatılır.

PS: RAC ortamında bütün standby node larda uygulanır.

step 3: standby archive writing aktif edilir (enable)
primary/production database

RAC ortamında sadece bir node da çalıştırılması yeterli (sid=’*’).

*****************************************************************************************************

Bozulmadan önleyelim. Ayrıntılı bilgi için Doc ID 1302539.1
primary

standby

Errors & Resolution

1

Hatasi alinirsa
root ile

2
Deletion of Applied Archivelogs
If the archivelog files are being managed in the Fast Recovery Area then automatic deletion of backed up and applied archivelog files can be setup by issuing the following RMAN configure command on the primary database:

Creating a physical standby from ASM primary [ID 787793.1]
http://www.datadisk.co.uk/html_docs/oracle_dg/troubleshooting.htm
http://www.datadisk.co.uk/html_docs/oracle_dg/troubleshooting.htm
http://www.oracledba.org/">http://www.oracledba.org

3
Data Guard Broker Status Summary:
Type Name Severity Status

hata varsa
show database 'stdhira’ 'InconsistentProperties’;
ile farkli degerler bulunup (bazan degerler ayni olsa da ) scope=spfile/both ile degistirince düzeliyor.

4

Solution
Ozet
o anki primary de

RAC

single instance

metalink te ise asagidaki adimlar anlatilmis.
a. Use DGMGRL to gather information about the Broker configuration.
- From current Primary

# This should be done for the primary and each standby.

b. Remove the Broker configuration.

- From current Primary:

# This will ensure standby operations continue while the Broker
# configuration is being re-created.

c. Change the LOG_ARCHIVE_DEST_n destinations defined with LOCATION to remove DB_UNIQUE_NAME.

# This must be done on all databases in the Data Guard environment
# that Broker will manage.

d. Re-create the Broker configuration.

- From current Primary:

# Use the info from Step #1 to re-create the Broker configuration
# and modify the properties on each database before enabling.
e.
ORA-16826: apply service state is inconsistent with the DelayMins property
dgmgrl configurasyonunu disable/enable edince düzeliyor.

5 . Bağlantı sorunları yaşandığında bakılacak yerler

6.Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/OraInstall2013-12-30_01-26-43PM/jdk/jre/lib/sparcv9/motif21/libmawt.so: ld.so.1: java: fatal: libXm.so.4: open failed: No such file or directory….

Çözüm

Yararlanilan kaynaklar :

http://tahiti.oracle.com
http://asanga-pradeep.blogspot.com/2010/11/rac-to-single-instance-physical-standby.html
http://easyoradba.com/2012/11/20/rac-to-single-instance-dataguard-oracle-11gr2-physical-standby/
http://www.cozumpark.com/blogs/oracle/archive/2011/02/26/oracle-11g-r2-11-2-0-2-rac-mimarisinde-data-guard-kurulumu-ve-y-netimi-d-nyada-lk-ve-tek.aspx
http://dpmappsdba.blogspot.com/p/rac-to-single-instance-physical-standby.html
http://unixoracledba.wordpress.com/2012/03/29/how-to-create-a-single-instance-physical-standby-dataguard-for-a-rac-database/

*****************************************************************************************************

Kategori seçin...