Query regarding setting up physical standby for EBS 12.2.7

[raja]

Hi Erman

I have a current configuration with PROD as Primary database and PRODDR as standby database.
PRODDR was created using active duplicate feature of RMAN and it uses a static listener registration.

1. tns entries for PROD while setting up the physical standby was:

PROD=
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=ebs3.oracle.com)(PORT=1521))
            (CONNECT_DATA=
               (SERVICE_NAME=PROD)
                (SERVER=DEDICATED)
            )
        )
PRODDR=
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=rac2.localdomain)(PORT=1521))
            (CONNECT_DATA=
                (SERVICE_NAME=PROD)
                (SERVER=DEDICATED)
            )
        )


tns entries for PRODDR while setting up the physical standby was:

PROD=
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=ebs3.oracle.com)(PORT=1521))
            (CONNECT_DATA=
               (SERVICE_NAME=PROD)
                (SERVER=DEDICATED)
            )
        )
PRODDR=
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=ebs2.oracle.com)(PORT=1521))
            (CONNECT_DATA=
                (SERVICE_NAME=PROD)
                (SERVER=DEDICATED)
            )


Thus both were able to tnsping each other.

2. Enabled autoconfig in the physical standby and configured EBS 12.2.7 for both the primary and Standby

3. Verified the log shipping and logs were getting shipped correctly from primary to standby with no lag.

Now my doubt is, whenever i am running autoconfig in the primary or standby database tier, it basically regenerates the tnsnames.ora file along with other .ora file which is normal. The problem is the new tnsnames.ora file doesn't have the entries for PRODDR(standby) instance and hence whenever primary is not able to tnsping the standby and log shipping from primary to standby is getting impacted. Then i had to manually put the PRODDR entries and it started running normal after then. Thus, everytime when i run autonconfig, do i need to manually feed the details in the tns entries?


2. During switchover, the primary becomes standby and standby becomes primary. In this case, i had first deferred the log_archive_dest_2 parameter in the primary to defer.

SQL>alter system set LOG_ARCHIVE_DEST_STATE_2=defer scope=both sid='*';
SQL>alter database recover managed standby database disconnect from session;

On the new primary
SQL>alter system set LOG_ARCHIVE_DEST_STATE_2=enable scope=both sid='*';

Do you think for log shipping from new primary to standby, do i need to modify any other parameter settings?

i changed one more parameter for log_archive_dest_1 as it was in deferred state.

SQL> alter system set log_archive_dest_1='LOCATION=/u01/app/oracledb/droracledb/data/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRODDR';

For the switchover, what would be the settings for the below two parameters. Do i need to change them. Presently, i have.

    set log_archive_dest_1='LOCATION=/u01/app/oracledb/droracledb/data/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PROD'

    set log_archive_dest_2='service=PRODDR ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=PRODDR'


Please suggest


Thanks

[ErmanArslansOracleBlog]

For your autoconfig related concern;

You define those TNS entries in ifiles.. ( <CONTEXT_NAME>_ifile.ora... )
ifiles are not touched by autoconfig.
So no need for any concerns.

These are all documented in "Business Continuity for Oracle E-Business Suite Release 12.2 Using Oracle 12c (12.1.0.2) Physical Standby Database (Doc ID 1963472.1)"

As for your switchover related concerns, please read ->

These are all documented in "Business Continuity for Oracle E-Business Suite Release 12.2 Using Oracle 12c (12.1.0.2) Physical Standby Database (Doc ID 1963472.1)"
"Section 6: Performing Role Transitions"

[raja]

Thanks Erman. So just to confirm, to save the changes done from autoconfig, i will have to add the contents of tnsnames.ora aand listener.ora as well to _CONTEXT_ifile.ora file?

[ErmanArslansOracleBlog]

Do exactly what the above document says.

You will not write anything in your EBS-related tnsnames.ora.
You will write your standby configuration-related tns entries in your ifiles..
The standard (autoconfig managed) EBS tnsnames ora files have ifile pointers.. So what you will write into ifiles, will be recognized accordingly.

[raja]

Hi Erman

I have added the tnsnames entries and the listener.ora entries in the respective ifiles in the primary and the standby but whenever i am starting the listener, it is reading the same from listener.ora file. Am i missing something? Do i need to set some variables so that it will read the ifiles.


Thanks
Raja

[ErmanArslansOracleBlog]

What do you mean by same listener.ora file?

Oracle will read the listener.ora file (and from there it will read the ifile, in addition to the listener.ora file)

the same applies for tnsnames.ora and tnsnames ifile.. The same applies even for sqlnet and sqlnet ifile..