Professional Documents
Culture Documents
San Francisco
September 1923, 2010
S317131: Maximum Availability Architecture Best Practices: Oracle E-Business Suite R12.1 Ray Dutcher
PMTS, MAA Group Oracle Server Technologies
Lyn Pratt
CMTS, MAA Group Oracle Server Technologies
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracles products remains at the sole discretion of Oracle.
Agenda
<Insert Picture Here> Maximum Availability Architecture (MAA) E-Business Suite MAA E-Business Suite Disaster Recovery New Database Features and E-Business Suite
Presentation Focus
This presentation is on Oracle E-Business Suite Release 12.1 MAA with RDBMS 11.2
Please see the MAA home page for detailed papers covering Oracle E-Business Suite 11i and R12 MAA
http://www.oracle.com/technetwork/database/features/availability/maa-best-practices-155366.html
10
11
E-Business Suite
MAA on Exadata
Primary Site Secondary Site
Application Tier
Exadata DB Servers
12
E-Business Suite MAA Install and Transition, Sun Oracle Database Machine
Fresh Install
Standard Installation with Rapid Install Upgrade the database to 11.2.0.1 Using rconfig: convert database to RAC and move the database files to ASM Paper available soon
Transportable Database
same endian format same Oracle software version and patches installed
13
14
How to set up and operate an E-Business Suite disaster recovery site Detailed papers for 11i and R12 are on the MAA Best Practices home page
http://www.oracle.com/technetwork/database/features/availability/maa-best-practices155366.html
Use the Rapid Clone process; see Support note 1070033.1, Business Continuity for Oracle E-Business Release 12 Using Oracle 11g Physical Standby Database
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1070033.1
15
16
E-Business Suite Disaster Recovery Creating the Standby Site Establish Standby Hardware and System Software
Install the standby site middle tier and database hardware, networks, etc. Think carefully about the performance and HA requirements - best to mimic production Plan also for all required external services Install System Software
Establish ASM
17
E-Business Suite Disaster Recovery Preparation on the Primary Prepare for Data Guard operation
Enable archive log mode Enable forced logging Create database password files Configure Oracle*NET communication between sites Set database parameters for Data Guard Create standby redo logs Add primary role-based service
18
Run clone steps on each standby database server Configure standby database Data Guard parameters Configure Oracle*NET Communication on standby site [RAC Only] Restart the listeners
19
20
[RAC Only] Register the standby database with Oracle Clusterware and create11.2 role-based service
21
Shut down the app and all but one database instance on each site Execute the database switchover Remove the applications topology from the database
EXEC FND_CONC_CLONE.SETUP_CLEAN; commit;
Run AutoConfig on database tier (twice for RAC) then middle tiers to configure the application for DR operation Adjust the load balancer to the active application tier nodes Start the Apps
22
23
Stop redo apply and shut down all but one RAC instance Ensure the database is mounted, but not open Requires the fast recovery area to be configured
It is not necessary for flashback database to be enabled
Perform testing at the standby site Convert the database back to a physical standby
24
E-Business Suite Disaster Recovery Automating Switchover and Failover Use the Data Guard Broker to automate Data Guard operations
Configure Data Guard Fast Start Failover
automatically detect a database failure automatically initiate failover
Create a DB_ROLE_CHANGE trigger that will execute the script on switchover and failover Create a role-based service
25
26
Named Database Listener Coordinated recovery in an integrated architecture Active Data Guard for E-Business Suite reporting Roadmap: Edition-Based Redefinition
27
Same listener name on all RAC database nodes Autoconfig supports this as of:
11i - 9535311 12.0 R12.TXK.A.delta.7 [9386653] or higher 12.1 R12.TXK.B.delta 3 [8919489] or higher
<DB_LISTENER oa_var="s_db_listener">LISTENER_VISMIG</DB_LISTENER>
28
29
30
Coordinated Recovery Whats the procedure? Recover or halt all impacted databases Determine if a database has data loss Identify lowest SCN of databases with data loss. This is the target recovery SCN. Flash back all databases with SCNs greater than the target SCN, to the target SCN
Challenges:
Inactive / quiet database SCNs lag behind Any application that doesnt use 2PC/XA leaves a gap
31
32
E-Business Suite and Active Data Guard Further Utilizing Standby The basic challenge to offloading EBS reporting:
An Active Data Guard standby is read-only Logging into EBS, managing concurrent requests both require writes
33
E-Business Suite and Active Data Guard Further Utilizing Standby The starting point:
Available as a patch on top of R12.1.3 Oracle Database 11.2 Only ReportWriter programs will be supported Reports must have been run previously on primary, and marked as runnable on standby
34
E-Business Suite MAA Roadmap the final piece of the HA jigsaw puzzle
High Availability Make planned changes to software Survive hardware failure
35
E-Business Suite MAA Roadmap Edition-based Redefinition 11.2 brings these revolutionary new features: the edition, the editioning view, and the crossedition trigger
Code changes are installed in the privacy of a new edition Data changes are made safely by writing only to new columns or new tables not seen by the old edition
An editioning view exposes a different projection of a table into each edition to allow each to see just its own columns
A crossedition trigger propagates data changes made by the old edition into the new editions columns, or (in hotrollover) vice-versa
36
References
MAA Best Practices home page
http://www.oracle.com/technetwork/database/features/availability/maa-best-practices-155366.html
1133355.1 - Migrating an Oracle E-Business Suite Database to Sun Oracle Database Machine 1070033.1 - Business Continuity for Oracle E-Business Release 12 Using Oracle 11g Physical Standby Database
OpenWorld 2010 Session S316297 - Oracle Development Tips: Seamless Application Failover with Oracle Data Guard
37
5:00p Five Key HA Innovations, Rm 103 5:00p GoldenGate Strategy & Roadmap, Moscone West, Rm 3020
Tuesday, 21 Sep Moscone South * 11:00a App Failover with Data Guard, Rm 300 12:30p Oracle Data Centers & Oracle Secure Backup, Rm 300
2:00p ASM Cluster File System, Rm 308 2:00p Exadata: OLTP, Warehousing, Consolidation, Rm 103 3:30p Deep Dive into OLTP Table Compression, Rm 104 3:30p MAA for E-Business Suite R12.1, Moscone West, Rm 2020 5:00p Instant DR by Deploying on Amazon Cloud, Rm 300
Thursday, 23 Sep Moscone South * 10:30a Active Data Guard Under the Hood, Rm 103 1:30p Minimal Downtime Upgrades, Rm 306 3:00p DR for Database Machine, Rm 103
38
search.oracle.com
Maximum availability architecture
or oracle.com
39
40
41