Oracle Dataguard broker & CFC Part 2

fuadar — Mon, 03 May 2010 18:28:41 +0000

In an earlier post i mentioned how Oracle Dataguard Broker does not support a cold failover cluster like HACMP. Well turns out Broker can be used on a Cold Failover Cluster.
There are a few simple steps that needs to be followed to make the data broker be able to function.

On the primary

 alter system set local_listener=;

This will ensure that the database knows about the listener that is running on a virtual host name.

After this step is completed Follow the steps in Metalink Doc # 808783.1
I’m listing the steps below

ALTER SYSTEM SET DG_BROKER_START=FALSE;
 SQL> show parameter dg_broker_config_file
--- remove files that are displayed on the primary and the start broker on both the primary and the standby
SQL>ALTER SYSTEM SET DG_BROKER_START=TRUE;

After this connect to Dataguard Manager

DGMGRL>CREATE CONFIGURATION 'DGCONF' AS PRIMARY DATABASE IS 'PROD' CONNECT IDENTIFIER IS PROD;
DGMGRL> ADD DATABASE 'STDBY' AS CONNECT IDENTIFIER IS STDBY MAINTAINED AS PHYSICAL; --or LOGICAL
DGMGRL> ENABLE CONFIGURATION;
-- validate
DGMGRL> SHOW CONFIGURATION;
--Success means all is good

The above commands are from the Metalink Doc above and work perfectly for a CFC . We are now able to failover our clusters and have Dataguard broker work for us to manage our configurations.

Physical Dataguard Password change Oracle Performs redo shipping and authentication services between the primary...
Oracle ASM (Automatic Storage Management) 11.1 with a 10Gr2 database The last couple of weeks I’ve been working on converting...

Related posts brought to you by Yet Another Related Posts Plugin.

Physical Dataguard Password change

fuadar — Mon, 14 Sep 2009 12:06:25 +0000

Oracle Performs redo shipping and authentication services between the primary and the standby using Password files and if your security protocols dictate a sys password change you will start having issues with stopped log shipping with errors like .

Error 1017 received logging on to the standby
————————————————————
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
————————————————————

The solution to fixing thiscan be

1. Open the physical Standby read only and change the sys password.

2. Use orapwd to create anew password file.

3. ship/sftp the password file from the primary.

11g Brings a new twist to options 1 and 2 .

SEC_CASE_SENSITIVE_LOGON=TRUE by default in Oracle 11g which means the option 1 and 2 will generate different hash when done on different systems

Metalink note #462219.1 provides an explanation and the solution to this problem. The solution includes a new option in the orapwd utility which allows you to ignorecase.

$ORAPWD FILE=filename [ENTRIES=numusers] [FORCE={Y|N}] [IGNORECASE={Y|N}] [NOSYSDBA={Y|N}

The other solution includes changing case sensitivity by changing SEC_CASE_SENSITIVE_LOGON=FALSE . This is a dynamic parameter.

Please evaluate and implement all solutions based on your company security practice.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Fuad Arshad's Blog » dataguard

Oracle Dataguard broker & CFC Part 2

Physical Dataguard Password change