PRK Failover Testing

7/31/2019 PRK Failover Testing

http://slidepdf.com/reader/full/prk-failover-testing 1/5

Failover Test

PRK-DR-ACS = reuxgbuz414PRK-DR-PAS = reuxgbuz404PRK-DR-SAS = reuxgbuz405PRK-DR-DB = reuxgbuz403

PRK-ACS = reuxeuuz1091PRK-PAS = reuxeuuz1095PRK-SAS = reuxeuuz1096PRK-DB = reuxeuuz1094

High level steps

1) Enable/Check flashback configuration on PRK-DR-DB

2) Suspend log shipping on PRK-DB.

3) Open the Standby database.4) Add datafiles to PSAPTEMP tablespace on PRK-DR-DB

5) Start SAP on PRK-DR-ACS / PAS / SAS and connect to SAP and check things out

6) Rollback PRK-DR-DB to the point before the failover test started.

7) Resume log shipping on PRK-DB

8) Delete local /etc/hosts entry for sapPRK from the local laptops/desktops and also

update DNS alias (This step will require DNS update and hence " G Global DNSAdministrator" team needs to be involved)

Detailed Steps

1) Enable/Check flashback configuration on PRK-DR-DB

Login to PRK-DR-DB

FLASHBACK configuration

• We have a file system /oracle/PRK/oraflash for testing this.



• Cancel redo apply and create a guaranteed restore point

select name from v$restore_point;

2) Prepare Primary PRK-DB to have physical standby be diverged

Login to PRK-DB

Defer archive log destination pointing to standby

Create .lock.bra in /oracle/PRK/saparch directory so that archive logs don't go to tape

3) Open the Standby database.

Activate the Physical standby database

Login to PRK-DR-DB



Below is to defer log shipping to primary JUST in case even though not required technically

4) Add datafiles to PSAPTEMP tablespace on PRK-DR-DB

Add datafiles to PSAPTEMP

5) Start SAP on PRK-DR-ACS / PAS / SAS and connect to SAP and check things out

• Do the Basis checks and handover the system to Functional users for checkout

• All the users who want to use PRK-DR-CI will need to update the local /etc/hosts with thefollowing entry

149.189.161.121 sapPRK sapPRK.bp.com sapPRK.bpweb.bp.com



• Make sure that in SAP LOGON pad you are using the application server name of sapprk.bp.com

Create a test user TESTDR (much easier to change rather than creating table through se11 askingfor access key

Also, take screenshots for J2EE Home page, System Status

6) Rollback PRK-DR-DB to the point before the failover test started.

Stop SAP on PRK-DR-CI

Revert the activated Standby database to a physical standby database

Login to PRK-DR-DB



7) Resume log shipping on PRK-DB

Reenable archiving to the physical standby database destination

Login to PRK-DB

Login to PRK-DR-DB

Verify everything that test DR is successful and then delete the restore point you created earlier.

Check Oracle Alert log to see whether logs are getting shipped. Also, check archive log listcommand on both PRK-DR-DB and PRK-DB

8) Delete local /etc/hosts entry for sapPRK from the local laptops/desktops

• All the users who were using PRK-DR-CI will need to delete the following entry from thelocal /etc/hosts

149.195.58.231 sapPRK sapPRK.bp.com sapPRK.bpweb.bp.com

• Make sure that in SAP LOGON pad you are using the application server name of sapPRK.bp.com

Documents

PRK Failover Testing