Environment
Details:
Operating System       :
EL 4 Update 6
Oracle DB                  
: 10.2.0.4
EBiz                            
: 11.5.10.2
Two
node architecture:
DB & Concurrent  in
one node ( PRIMDBSERV)
Web ,Reports & Forms in one node   (PRIMAPPSERV)

Operating System & User Details:
DB Host Name = PRIMDBSERV
DB OS User = ORACLE
APPS Host Name = PRIMAPPSERV
Apps Os User = APPPRDMGR
In
this DR Simulation we are going to switch over the primary instance to standby
and standby instance to primary. After successful testing , we will bring back
to the original
Setup.
Step 1 => Switch Primary instance to
Standby Instance
Down the Application
Services ( Forms & Web) in PRIMARY Node
In
PRIMAPPSERV – OS USER – APPPRDMGR
1.       cd $COMMON_TOP/admin/scripts/PROD_PRIMAPPSERV
2.       sh adstpall.sh
Review
the log file after all the application services are down on PRIMAPPSERV.doyen.in
Down the Application
Services ( Concurrent) in PRIMARY Node
In
PRIMDBSERV – OS USER – APPPRDMGR
3.       cd $COMMON_TOP/admin/scripts/PROD_PRIMDBSERV
4.       sh adstpall.sh
Review
the log file after all the application services are down on PRIMAPPSERV.doyen.in
5.       ps -ef | grep FNDLIBR | grep -v grep
| wc –l

Note:  APPL_TOP folder from PRIMDBSERV(Concurrent)
& PRIMAPPSERV (Forms & Web) has to be moved to STBYDBSERV(Concurrent)
& PRIMAPPSERV(Forms & Web) respectively.
Change the XML file from Standby
appl top to newly moved appl top from primary.
If you migrate the application
changes like changing rdf,sql’s , custom.pll  to standby regularly as part of your migration
then you don’t need to move the appl top to your standby environment .
In
PRIMDBSERV – OS USER – ORACLE
1.       Shut
Down the Database      

                                sqlplus ‘/as sysdba’
shut
immediate;
2.       Check
Listeners on Both Primary & Standby

 lsnrctl status
listener_name or ps –ef|grep lsnr from os prompt

3.       Check
Switch Over Status

               startup;
SELECT
SWITCHOVER_STATUS FROM V$DATABASE;
It has to be
SWITCHOVER_STATUS
               ——————————
TO STANDBY
4.      
Switching the Primary Database to
Physical Standby

alter
database commit to switchover  to
physical standby;
shut
Immediate;

5.       Copy
the init.ora file of Standby

cd
$ORACLE_HOME/dbs
cp
-p PROD_PRIMDBSERV_ifile.ora_switchover PROD_PRIMDBSERV_ifile.ora
Parameters
Changed in the above files are:
Since
we are making our primary as standby we disabling the dest_state_2 parameter in
Primary
(which is going to be standby) server.
Existing
Parameter:

#log_archive_dest_state_2
= defer
 log_archive_dest_state_2
= enable
After
Changing Parameter:
log_archive_dest_state_2 =
defer
#
log_archive_dest_state_2 = enable
6.       After  Changing the parameter Start the EBS
Prod  instance as Physical Standby
startup
nomount;
Alter database mount standby
database;
7.       Start
Applying Archive Logs from SBYPROD Instance
alter database recover managed
standby database disconnect from session;
8.       check
for errors in alert.log

9.       Check
Switchover Status
SELECT
SWITCHOVER_STATUS FROM V$DATABASE;
It
has to be
SWITCHOVER_STATUS
                —————————
SESSIONS ACTIVE
Step 2 => Switch Standby instance
to Primary Instance
SWITCHING STANDBY TO
PRIMARY
In
STBYDBSERV
Since
the application services were already down in the standby node , we starting
the switchover steps in the Database.
1.       Check
for the Switch Over Status of the database

Sqlplus
‘/as sysdba’
select
SWITCHOVER_STATUS FROM V$DATABASE;
It
has to be
SWITCHOVER_STATUS
               ——————————
TO PRIMARY
2.       Switching
the Physical Standby to Primary Instance

alter database commit to switchover
to primary;
shut immediate
3.       Copy
the init.ora file of Primary

Cd
$ORACLE_HOME/dbs
cp
-p SBYPROD_STBYDBSERV_ifile.ora_switchover 
SBYPROD_STBYDBSERV_ifile.ora
Parameters Changed in the above
files are:
Since
we are making our Standby as Primary we enabling the dest_state_2 parameter in
Standby
(which is going to be Primary) server.
Existing
Parameter:

log_archive_dest_state_2 =
defer
#log_archive_dest_state_2
= enable
After
Changing Parameter:
#
log_archive_dest_state_2 = defer
log_archive_dest_state_2 = enable
4.       After Changing the Parameters Start
the SBYPROD instance
 and create temporary tablespace
                                sqlplus
‘/as sysdba’
startup
alter
database default temporary tablespace temp;
drop
tablespace user_temp including contents and datafiles;
create
temporary tablespace user_temp tempfile
‘/oradata2/PROD/proddata/user_temp02.dbf’
size  16000m reuse autoextend on next
500m maxsize 25000m;
Alter
database default temporary tablespace user_temp;
5.       Check for archive log movement.

6.       Verify any error in ALERT LOG file.

7.       Check the Switch Over Status

select
SWITCHOVER_STATUS FROM V$DATABASE
It
has to be
SWITCHOVER_STATUS
               ——————————
SESSIONS
ACTIVE
8.       Copy
XML from old APPL_TOP IN STBYDBSERV – OS USER – APPPRDMGR
 cp -p
/oracle/PROD/app/prodappl_17NOV2010/admin/SBYPROD_STBYAPPSERV2.xml  /oracle/PROD/app/prodappl/admin/.
IN STBYAPPSERV2
– OS USER – APPPRDMGR
cp
-p /oracle/PROD/app/prodappl_17NOV2010/admin/SBYPROD_STBYAPPSERV2.xml  /oracle/PROD/app/prodappl/admin/.
9.       Run
Autoconfig in  STBYDBSERV (Concurrent
& Admin Node)

su –
appprdmgr
                                cd
$COMMON_TOP/admin/scripts/SBYPROD_STBYDBSERV
                                sh
adautocfg.sh
10.    Run Auto Config  in STBYAPPSERV2 (Web & Forms Node)

cd $COMMON_TOP/admin/scripts/SBYPROD_STBYAPPSERV2
sh
adautocfg.sh
11.   Start
the EBS Application in STBYDBSERV (Concurrent Node)

cd
$COMMON_TOP/admin/scripts/SBYPROD_STBYDBSERV
                                sh
adstrtal.sh
                                Review
the log file after all the application services are up on STBYDBSERV.doyen.in.
                                Check
whether all the concurrent managers are up or not from os prompt.
                                ps
–ef | grep FNDLIBR ( verify the number of FNDLIBR’s processes)
12.   Start
the EBS Application STBYAPPSERV2  (Forms
& Web Node)

cd
$COMMON_TOP/admin/scripts/SBYPROD_STBYAPPSERV2
sh
adstrtal.sh
Review
the log file after all the application services are up on STBYAPPSERV2.doyen.in.
                                Check
whether all the concurrent managers are up or not from os prompt.
13.   Login to the standby application
server using new URL.

http://STBYAPPSERV2.doyen.in:8075/
Login as
sysadmin run active users report and any XML report.
Verify
the output and log files for the concurrent reports run.
Save the
entire concurrent requests output files to your local machine.
14.   Perform Functional Testing and submit
all necessary to reports and save the output files.

After Successful Switchover Simulation , We are bringing back the original
setup.
Step 3=> Switch Primary instance
to Standby Instance
RE
SWITCHING OF PRIMARY TO STANDBY
In
STBYAPPSERV2 – OS USER – APPPRDMGR
15.   Stop
the EBS Application (Forms & Web Node)

cd
$COMMON_TOP/admin/scripts/SBYPROD_STBYAPPSERV2
sh
adstpall.sh
Review
the log file after all the application services are up on STBYAPPSERV2.doyen.in.
In
STBYDBSERV – OS USER – APPPRDMGR
16.   Stop
the EBS Application (Concurrent & Admin Node)

cd
$COMMON_TOP/admin/scripts/SBYPROD_STBYDBSERV
sh
adstpall.sh
Review
the log file after all the application services are up on STBYDBSERV.doyen.in.
Check
whether all the concurrent managers are up or not from os prompt.
ps –ef |
grep FNDLIBR ( verify the number of FNDLIBR’s processes)
In  STBYDBSERV – OS USER – ORACLE
17.   Shut
Down the Database      
sqlplus
‘/as sysdba’
shut
immediate;
18.   Check
Switch Over Status

startup;
SELECT
SWITCHOVER_STATUS FROM V$DATABASE;
It
has to be
SWITCHOVER_STATUS
               ——————————
TO STANDBY
19.   Switching
the SBYPROD Database to Physical Standby

alter
database commit to switchover  to
physical standby;
shut
Immediate;
20.   Copy
the init.ora file of Standby

cd
$ORACLE_HOME/dbs
cp
-p SBYPROD_STBYDBSERV_ifile.ora_org_120909 SBYPROD_STBYDBSERV_ifile.ora
(Changed
Parameters discussed in the step1 & step 2)
 21.   Start
the SBYPROD  instance as Physical Standby
startup
nomount;
Alter database mount standby
database;
22.   Start
Applying Archive Logs from PROD Instance

alter database recover managed
standby database disconnect from session;
23.   check
for errors in alert.log

24.   Check
Switchover Status

SELECT SWITCHOVER_STATUS FROM
V$DATABASE;
It
has to be
SWITCHOVER_STATUS
               ——————————
SESSIONS ACTIVE                
 In PRIMDBSERV
25.   Check
for the Switch Over Status of the database

Sqlplus
‘/as sysdba’
select
SWITCHOVER_STATUS FROM V$DATABASE;
It
has to be
SWITCHOVER_STATUS
               ——————————
TO PRIMARY
26.   Switching
the Physical Standby to Primary Instance
alter
database commit to switchover to primary;
shut
immediate
27.   Copy
the init.ora file of Primary

Cd
$ORACLE_HOME/dbs
cp -p PROD_PRIMDBSERV_ifile.ora_org_121009 PROD_PRIMDBSERV_ifile.ora                  
(Changed Parameter Discussed in Step 1 & 2 )
28.   Start
the PROD instance and create temporary tablespace

               sqlplus
‘/as sysdba’
startup
alter
database default temporary tablespace temp;
drop
tablespace user_temp including contents and datafiles;
create
temporary tablespace user_temp tempfile ‘/oradata2/PROD/proddata/user_temp02.dbf’
size   16000m reuse autoextend on next
500m maxsize 25000m;
Alter
database default temporary tablespace user_temp;
29.   Check
for archive log movement.

30.   Verify
any error in ALERT LOG file.

31.   Check
the Switch Over Status
select
SWITCHOVER_STATUS FROM V$DATABASE
It
has to be
SWITCHOVER_STATUS
               ——————————
SESSIONS ACTIVE
32.   Run
Autoconfig in  PRIMDBSERV  (Concurrent & Admin Node)

su –
appprdmgr
                                cd
$COMMON_TOP/admin/scripts/PROD_PRIMDBSERV
                                sh
adautocfg.sh
33.    Run Auto Config  in PRIMAPPSERV (Forms & Web Node)

cd
$COMMON_TOP/admin/scripts/PROD_PRIMAPPSERV
sh
adautocfg.sh
34.   Start
the EBS Application in PRIMDBSERV

cd
$COMMON_TOP/admin/scripts/SBYPROD_STBYDBSERV
                                sh
adstrtal.sh
                                Review
the log file after all the application services are up on PRIMDBSERV.doyen.in.
                                Check
whether all the concurrent managers are up or not from os prompt.
                                ps
–ef | grep FNDLIBR ( verify the number of FNDLIBR’s processes)
35.   Start
the EBS Application PRIMAPPSERV

cd
$COMMON_TOP/admin/scripts/PROD_PRIMAPPSERV
sh
adstrtal.sh
Review
the log file after all the application services are up on PRIMAPPSERV.doyen.in
                                Check
whether all the concurrent managers are up or not from os prompt.
36.   Login
to the PRIMARY application server using URL.

http://PRIMAPPSERV.doyen.in:8075/
Login as
sysadmin run active users report and any XML report.
Verify
the output and log files for the concurrent reports run.
Save the
entire concurrent requests output files to your local machine.
37.   Perform
Functional Testing and submit all necessary to reports and save the output
files.
Recommended Posts

Start typing and press Enter to search