E Business Suite Release 12 2 Maximum Availability

E Business Suite Release 12 2 Maximum Availability-PDF Download

  • Date:05 Jul 2020
  • Views:4
  • Downloads:0
  • Pages:137
  • Size:1.82 MB

Share Pdf : E Business Suite Release 12 2 Maximum Availability

Download and Preview : E Business Suite Release 12 2 Maximum Availability


Report CopyRight/DMCA Form For : E Business Suite Release 12 2 Maximum Availability


Transcription:

Table of Contents,1 Introduction 1,2 Overview of Engineered Systems 2. 2 1 Oracle Exadata Database Machine 2,2 2 Oracle Exalogic 2. 3 Oracle E Business Suite Release 12 2 Maximum Availability Architecture 2. 3 1 Oracle Database Maximum Availability Architecture 4. 3 1 1 Oracle Real Application Clusters and Oracle Clusterware 4. 3 1 2 Oracle Data Guard 5,3 1 3 Oracle Data Guard Broker 5. 3 1 4 Oracle Flashback Database 6,3 1 5 Oracle Automatic Storage Management 6. 3 1 6 Oracle Recovery Manager and Oracle Secure Backup 6. 3 1 7 Online Upgrades Using Edition Based Redefinition 7. 3 2 Oracle E Business Suite Release 12 2 High Availability 7. 3 2 1 Parallel Concurrent Processing PCP 8, 3 2 2 Multiple Load Balanced Application Tier Services 10.
3 2 3 Oracle E Business Suite Release 12 2 Online Patching 10. 3 2 4 Logical Host Names 11, 3 2 5 Fusion Middleware Administration Server Configuration 11. 4 Oracle E Business Suite Database Configuration Best Practices 11. 4 1 OS Role Separation 11,4 2 Database Initialization Parameters 12. E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 4 3 Configure Linux HugePages 13,4 4 Take Backups of the Database Oracle Homes 13. 4 5 Handle Database Password Expiration 13,4 6 Exadata Fast Node Death Detection 14. 4 7 Reduce Timeout on Oracle RAC Node Failure 14,4 8 Implement Flashback Database 15.
4 9 Exadata Smart Flash Logging 15,4 10 Exadata Smart Flash Cache 15. 4 11 Memory Management Exadata Only 16,4 12 Oracle Advanced Compression 16. 4 13 Log Writer Tuning Exadata Only 17,4 14 Fixed Object Statistics 17. 4 15 Exadata I O Resource Manager IORM 18, 4 16 Oracle Engineered Systems Best Practices and Health Check 18. 5 Oracle E Business Suite Release 12 2 Application Tier Configuration. Best Practices 18, 5 1 Create an Oracle E Business Suite Central Inventory on the.
Application Tier 19,5 2 Move the Apache Lock File to Local Storage 19. 5 3 Take Regular Backups of the Release 12 2 Application File System 19. 5 4 Use NFSv4 for NFS Mounted File Systems 20,5 5 Disable NFS Delegation Exalogic Only 20. 5 6 Disable Failback for IPMP Setting Exalogic Only 20. 5 7 Mount ZFS Shares over IPoIB Exalogic Only 21, E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 6 Summary of Best Practices 22, 6 1 Best Practices Oracle E Business Suite Database Maximum Availability 22. 6 2 Best Practices Oracle E Business Suite Application High Availability 23. 6 3 Best Practices Oracle E Business Suite Maximum Availability 24. 7 Oracle E Business Suite MAA Case Study Architecture 25. 7 1 Method 25,7 2 Case Study Topology 25,7 3 Software Versions 26.
7 4 Oracle E Business Suite Application Tier High Availability Architecture 27. 7 4 1 SMTP Server for Concurrent Processing 28,7 5 Oracle E Business Suite Database Tier MAA 28. 7 5 1 Database Setup 29, 7 5 2 Database Features for the Disaster Recovery Site 30. 7 6 Delegation of Roles and Administration 30, 7 6 1 Administrative Roles on Exadata Database Machine 30. 7 6 2 Administrative Roles on Exalogic Machine 31, 7 7 Oracle E Business Suite Application and Web Tier Setup 31. 7 8 Logical Host Names 33,8 Case Study Roadmap 33,8 1 Prepare the Network 33.
8 1 1 Set Up Global or Local Traffic Managers 34,8 2 Prepare the Primary 34. E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 8 2 1 Set up the Linux Groups and Users 34, 8 2 2 Set Up Logical Host Names of Database Servers 35. 8 2 3 Set Up Logical Host Names for the Application Tier Servers 36. 8 2 4 Clone the Database to Itself Using EBS Rapid Clone Methodology 39. 8 2 5 Clone the Application Tier to Itself Using EBS Rapid Clone. Methodology 45, 8 2 6 Configure the Primary Database for Oracle Data Guard 51. 8 3 Prepare the Standby 55, 8 3 1 Set Up Logical Host Names for Standby Database Tier 55. 8 3 2 Set Up Logical Host Names and Configure Standby Middle Tiers 56. 8 3 3 Set Up the Standby Database 57,8 3 4 Set Up Standby Application Tier 75.
8 4 Disaster Recovery Site Test using Snapshots 79. 8 4 1 Convert the Physical Standby Database to a Snapshot Standby 79. 8 4 2 Create a Snapshot Clone of the Shared File System Being. Replicated to the Disaster Recovery Site 80,8 4 3 Set Up OS User Equivalency 81. 8 4 4 Configure the Web Entry URLs and Port Numbers 83. 8 5 Test Switchover 85, 8 5 1 Shut EBS Application Services Down at the Primary Site 85. 8 5 2 Switch Database Roles 86,8 5 3 Reverse ZFS Replication Direction 87. E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 8 5 4 Mount the EBS Application File System and Start Application. Services at the Standby 88,8 6 Test Failover 91,8 6 1 Perform a Data Guard Failover 92. 8 6 2 Perform a Role Reversal 92,8 6 3 Perform State Cleanup 93.
8 6 4 Start Application Services 94, 8 7 Patching the Database in an Engineered Systems Environment 96. 8 7 1 Prepare for Database Patching 96,8 7 2 Patch One Standby Database Instance Home 97. 8 7 3 Check the Patched Standby Database Home 100,8 7 4 Propagate the Patched Oracle Home 102. 8 7 5 Complete the Database Patching Process 104,8 7 6 Test the Standby 105. 8 7 7 Propagate the Patch Database Homes to the Primary 106. 9 References 112,9 1 Database MAA 112,9 2 Database Oracle Data Guard 112.
9 3 Oracle Real Application Clusters RAC 112,9 4 Oracle E Business Suite MAA 112. 9 5 Oracle E Business Suite Parallel Concurrent Manager 112. 9 6 Oracle E Business Suite Configuration and Management 113. 9 7 Cloning Oracle E Business Suite 113, E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 9 8 Oracle E Business Suite Application Tier Patching 113. 9 9 Oracle Engineered Systems Exadata SuperCluster 114. 9 10 OS Required Packages and HugePages 114, 10 Appendix A Verify Oracle E Business Suite Required Packages 114. 11 Appendix B Managing SCAN for Primary and DR Sites 115. 11 1 The custom txt File 117,11 2 The ebs scan db sh Script 117. 11 3 The ebs scan app sh Script 119,12 Appendix C Set Web Entry Point 121.
13 Appendix D Add Managed Services 122, 13 1 Review the Configuration on the Admin Server 122. 13 2 Add and Start Managed Services 123,13 3 Finalize the Configuration 124. 13 4 Bounce the HTTP Server 124,14 Appendix E Perform rsync on Oracle Homes 124. 14 1 Using the rsync EBS OH sh Script 125,14 1 1 Copy a patched ORACLE HOME 125. 14 1 2 Copy an ORACLE HOME to its standby 126,14 2 The rsync EBS OH sh script 126.
E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 1 Introduction, The Oracle E Business Suite is a comprehensive suite of integrated global business applications. spanning enterprise resource planning customer relationship management human resource. management financial management service management project portfolio management value chain. planning and execution procurement and supply chain planning These mission critical functions. require protection to ensure they continue to be available at all times Whether Oracle E Business. Suite is deployed in the Cloud or on premises planning for and implementing strategies for high. availability and disaster recovery are paramount, In this paper we apply the principles of Oracle s Maximum Availability Architecture MAA to the. Oracle E Business Suite EBS Release 12 2 infrastructure The major difference between the. methods described here for Oracle E Business Suite Release 12 2 and those documented elsewhere. for earlier releases is the use of logical host names instead of physical host names in the EBS. managed topology This allows us to make the configuration of the standby site the same as the. primary site from an Oracle E Business Suite perspective thus allowing you to switch between the. two sites with minimal configuration efforts and facilitating a reduction in downtime as compared to. using physical host names,This paper provides, A high level description of the Oracle E Business Suite Release 12 2 MAA architecture and. configuration best practices In general the MAA best practices described are generic across all. platforms We identify where there are best practices unique to deployments on Oracle engineered. A case study of Oracle E Business Suite Release 12 2 on Oracle Exalogic and Exadata machines. showing the steps for, Reconfiguring an existing Oracle E Business Suite implementation to use logical host names. Establishing the disaster recovery DR site, Non destructive testing of Oracle E Business Suite at the DR site.
Switchover and failover procedures, Simplified patching of Oracle E Business Suite s Oracle Database homes. This MAA implementation for Oracle E Business Suite Release 12 2 combines the proven technology. used by Oracle E Business Suite on Oracle s Exalogic and Exadata machines with tested MAA best. practices You can follow the steps in this document to implement these MAA best practices. 1 E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 2 Overview of Engineered Systems, Oracle engineered systems combine best of breed hardware and software components with game changing. technical innovations Designed engineered and tested to work best together Oracle engineered systems can. power the cloud or streamline data center operations to make traditional deployments more efficient The. components of Oracle engineered systems are preassembled for the targeted functionality and then as a complete. system optimized for extreme performance By taking the guesswork out of these highly available purpose built. solutions Oracle delivers a solution that integrates across every layer of the technology stack This simplicity. translates into less risk and lower costs for your business Only Oracle can innovate and optimize at every layer of. the stack to simplify data center operations drive down costs and accelerate business innovation. 2 1 Oracle Exadata Database Machine, Oracle Exadata Database Machine is Oracle s database platform delivering extreme performance for database. applications including online transaction processing data warehousing reporting batch processing and. consolidation of mixed database workloads Exadata is a pre configured pre tuned and pre tested integrated. system of servers networking and storage all optimized around the Oracle Database As Exadata is an integrated. system it offers superior price performance availability and supportability Exadata frees you from the need to. build test and maintain systems and allows you to focus on higher value business problems. Exadata uses a scale out architecture for database servers and storage This architecture maintains an optimal. storage hierarchy spanning memory flash storage and disk Features of the Exadata Database Machine include. Smart Scan queries offload database processing to the storage cells. The Exadata Smart Flash Cache feature ensures optimal use of Flash storage for reads and writes to benefit. database performance, The high bandwidth low latency InfiniBand network runs specialized database networking protocols and connects. all the components inside an Exadata Database Machine. The database industry s best data compression to provide a dramatic reduction in storage requirements. In Memory OLTP Acceleration where data blocks are naturally aged out of the buffer cache and relocated into. DRAM in the storage cells where they can be accessed more quickly than from flash cache. 2 2 Oracle Exalogic, Oracle Exalogic is an Engineered System used by enterprises to deploy Oracle business applications Oracle.
Fusion Middleware and third party software products Oracle Exalogic comes pre built with compute nodes. memory flash storage and centralized storage that are all connected using InfiniBand in a high redundancy. architecture with in built fault tolerance and zero down time maintenance. 3 Oracle E Business Suite Release 12 2 Maximum Availability Architecture. Oracle E Business Suite Maximum Availability Architecture MAA is an EBS high availability HA architecture. layered on top of the Oracle Database including a secondary site to provide business continuity in the event of a. primary site failure, 2 ORACLE E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. In this section we first present the Oracle Database Maximum Availability Architecture then we describe how to. provide high availability for Oracle E Business Suite on top of that foundation resulting in a full Oracle E Business. Suite MAA implementation, Figure 1 Oracle E Business Suite Release 12 2 full MAA implementation. Figure 1 illustrates a full MAA implementation of an Oracle E Business Suite Release 12 2 deployment consisting of. two separate sites a primary site and a disaster recovery site At the primary site Oracle Real Application Clusters. Oracle RAC ensures high availability of the database tier and multiple application tiers provide high availability for. Oracle E Business Suite users and applications Database replication to the disaster recovery site is achieved using. Oracle Data Guard Application tier file system replication is achieved using storage replication rsync or any other. common UNIX Linux tool The disaster recovery site is identical to the primary site in terms of system infrastructure. 3 ORACLE E BUSINESS SUITE RELEASE 12 2 MAXIMUM AVAILABILITY ARCHITECTURE. 3 1 Oracle Database Maximum Availability Architecture. Figure 2 Oracle Database Maximum Availability Architecture. 3 2 Oracle E Business Suite Release 12 2 High Availability 7 3 2 1 Parallel Concurrent Processing PCP 8 3 2 2 Multiple Load Balanced Application Tier Services 10 3 2 3 Oracle E Business Suite Release 12 2 Online Patching 10 3 2 4 Logical Host Names 11 3 2 5 Fusion Middleware Administration Server Configuration 11 4 Oracle E Business Suite Database Configuration Best Practices 11 4 1 OS Role

Related Books