News From the Trenches – an E-business Suite R12 11g Implementation # 1458

1. News From the Trenches – an E-business Suite R12 11g Implementation# 1458 Jerry Ireland Mark W. Farnham 36 West Street Lebanon, NH 03766 Office: 603.448.1803 www.rightsizinginc.com

2. Jerry Ireland Principal, Rightsizing, Inc. Co-founding Director, ODTUG Current VP ODTUG Member Oracle VLDB Co-founder, APPSPERF

3. Mark W. Farnham President, Rightsizing, Inc. Co-founding Director, OAUG VP, OAUG DBSIG Member, MOSES, Oracle VLDB Co-founder, APPSPERF Member, Oaktable Network

4. Agenda • Background of Project • Approach • Challenges and Tips • Multiple Environments • Seeded Templates for autoconfig • Moving to Different Systems • 11g • Non-RAC to RAC – 11g • Sequence RAC-tax, FND_DUAL

5. Background of Project • Two separate existing general ledger systems (different charts of accounts) to combine • Adding Project Accounting • Set some standards for E-business suite administration and development • Take advantage of linux systems and provisioning new nodes where needed • Slender Development, Scalable Deployment • Just the technology for this project phase

6. Installation Versions • E-Business Suite R12 RUP6 • Database 11.1.0.6 • Tools 10.1.2.2 • WEB 10.1.3.3

7. General Project Plan • Create “Gold Copies” • Standard Vision Installation • Standard non-Vision Installation • Move to RAC • But keep slender development, test, etc. • Maintain clonability in all directions • Move to multiple Application servers

8. Approach • Create Standards for Recreating Steps • Create tools for repetitive or error-prone steps

9. Challenges and Tips • Multiple Installation Environments • Seeded Templates for autoconfig • Moving to Different Systems • 11g Topics • Non-RAC to RAC – 11g • Sequence RAC-tax • FND_DUAL

10. Multiple Installation Environments • 10g, Install 11g, 11g, Tools, Web, Cloning • Ensuring correct versions of java, perl, unzip, etc. • .bashrc • PATCH – set to common location for patches and scripts specific to phase • Execute appropriate *.env • Create functions and aliases for common activities • pdup – preserve and duplicate a file • cdoh – cd to current $ORACLE_HOME • cdash – cd to $ADMIN_SCRIPTS_HOME

11. Seeded Templates for autoconfig • $PATH • Autoconfig concatenates what it wants to current • Doesn’t include opatch or adpatch and other utilities • Database startup • Starts using pfile which loses dynamic performance parameter settings • init.ora errors

12. Seeded Templates for autoconfig • Configuring Templates • Run adtmplreport.sh to get template name and location • Create custom directory • Think of as “site configuration” or “local” • Put modified template in custom directory • Survives Cloning • Can easily be moved to 11g after upgrade

13. Seeded Templates for autoconfig • Init.ora parameters for 11g • Core_dump_destination • All documentation and upgrade wizard says it is deprecated along with background_dump_dest and user_dump_dest to be replaced with diag_destination • Actual • Others cause a warning when 11g starts • Core_dump_destination does not • Core_dump_destination defaults to 10g behavior • Set it to same location as diag_destination • job_queue_processes • Business Event System Event Messages • Recommended 2 • Change to 10 for better performance of workflow

14. Moving to Different Systems • E-busness Suite uses <db_name> and <sys_name> a lot for naming things • Create templates with <db_name> and <sys_name> • Need <sid_name> for RAC • Create tools to establish translation values • Create tools to translate the templates for specific database and system

15. 11g Topics • Cloning Challenges • Native Compile

16. Cloning Challenges • 11.1.0.6 certified for 12.0.6 • Clone of 12.0.6 on 11.1.0.6 database failed if upgraded to jdk 1.6 • adcfgclone.sh fails to make new executables • Known problem at Oracle

17. Native Compile • Much easier in 11g • Stores compiled code in database • Don’t need multiple directories xxx1, xxx2… • Generation of code is much improved • Some extra overhead during upgrades • Gain performance for production processes • Data access will not improve • E-Business Suite has lots of if..then..else • Don’t bother compiling package specifications

18. Non-RAC to RAC – 11g • Clone “Gold Copy” to system with ASM • Convert to RAC (single node) • Clone additional RAC nodes • Clone Application Nodes from “Gold Copy”

19. Non-RAC to RAC – 11g • Prelude to RCONFIG broken as of this writing • Slight of hand • Clone existing to RAC home destination • Move aside and install RAC software • Copy appsutil into RAC directory • Avoid regenerating init files (diag, etc.)

20. Sequence RAC-tax • Multiple RAC Nodes accessing same blocks • Application affinity benefits muted by multiple sequences per block • Spreading sequences one per block may help

21. “Hermitize” sequences, FND_DUAL • Especially higher potential win on RAC • May be useful for any busy OLTP system • FND_DUAL only E-Business Suite

22. Q&ANews From the Trenches – an E-business Suite R12 11g Implementation# 1458 Mark W. Farnham mwf@rsiz.com Jerry Irelandjerryi@rsiz.com www.rsiz.com www.appsperf.org