Upgrading 11i E-business Suite to R12 E-business Suite
Upcoming SlideShare
Loading in...5
×
 

Upgrading 11i E-business Suite to R12 E-business Suite

on

  • 6,681 views

Planning for an upgrade

Planning for an upgrade
Preparing for Upgrade
Upgrading to R12
Post Upgrade Tasks

Statistics

Views

Total Views
6,681
Views on SlideShare
3,343
Embed Views
3,338

Actions

Likes
4
Downloads
489
Comments
0

12 Embeds 3,338

http://www.iwarelogic.com 3259
http://functional-scm.blogspot.com 38
http://functional-scm.blogspot.in 14
http://iwarelogic.com 10
http://www.slideshare.net 5
http://webcache.googleusercontent.com 4
http://translate.googleusercontent.com 3
http://site2.way2sms.com 1
file:// 1
https://www.google.com 1
http://functional-scm.blogspot.ae 1
http://functional-scm.blogspot.ca 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Release 11.5.10 CU2 > Release 12.1.1 Upgrading Oracle Applications, Release 11.5.10.2 > Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1 Release 11.5.10 CU2 > Release 12.1.1 Maintenance Pack Installation Notes, Release 11.5.10 CU2 (Doc ID: 289788.1) > Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1 . Release 12.1.1 Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1 .
  • For Example: A test upgrade of the largest Oracle production system (oraprod) used the following CPUs: • Database tier machine - 24 CPUs (900 MHz SUNW, UltraSPARC-III+) • Application tier machine - 4 CPUs (3.05 GHz Intel Xeon) A test upgrade of the Vision database and application tier machine used 4 CPUs (3.05 GHz Intel Xeon). Note: See E-Business Suite Release 12 Upgrade Sizing and Best Practices (Doc ID: 399362.1) for the statistics on these production system upgrades. Memory To calculate the memory requirements for an upgrade, consider the following: • Number of concurrent users • Infrastructure requirements for multi-tiered architecture For Example A test upgrade of the largest Oracle production system (oraprod) used the following: • Database tier machine - 48 GB of memory
  • To estimate the increase in required disk space for upgrading, consider the products, the number of languages being installed, and changes in the data model For Example In a test upgrade of the largest Oracle production system (oraprod), the database increased 10-20 percent. In a test upgrade, the Vision database increased 5 percent. For guidelines based on an upgrade of the Oracle production system (oraprod), see E-Business Suite Release 12 Upgrade Sizing and Best Practices (Doc ID: 399362.1).
  • This release uses the Oracle Applications Tablespace Model (OATM), which is based on database object type rather than product affiliation. OATM uses 12 locally managed tablespaces for all products, including the temporary tablespace, system tablespace, and system-managed undo (SMU) tablespace. Each database object is mapped to a tablespace based on its input/output characteristics, including object size, life span, access methods, and locking granularity. Oracle has successfully tested systems with extent sizes of 128 K for small systems (100 GB database) and 4-10 MB for large, multi-terabyte database systems. We supply scripts in the upgrade process to create the tablespaces for all new products and configure the database for the new tablespace model. Then, the upgrade process creates the new objects. However, your existing objects are not automatically migrated. We strongly recommend that you migrate the existing objects after the upgrade is complete. Use the Tablespace Migration Utility (introduced in Release 11i) to perform this task
  • Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade ID 761570.1 Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade ID 403339.1
  • The TUMS report lists tasks that you can omit from the upgrade because they do not apply to your system (for example, a task required for a product that you do not use or for applying a patch that you have previously applied). TUMS is delivered in a patch, which supplies the scripts you need to examine your system and create the report. We strongly recommend you create and review the TUMS report before you begin the upgrade
  • Refer : Oracle Applications Developer's Guide
  • Set the schema name to ALL to gather statistics for all Oracle Applications schemas (having an entry in the FND_PRODUCT_INSTALLATIONS table). In addition to gathering index and table-level statistics, the program gathers column-level histogram statistics for all columns listed in the FND_HISTOGRAM_COLS table. Step 3 :Use the Rapid Install wizard to lay down the file system and install the new technology stack for your Release 12.1.1 Oracle Applications system. The wizard collects configuration parameters and stores them in a configuration file (config.txt) in the Applications file system. When you run Rapid Install, it uses these values to lay down the file system structure and technology stack components for your configuration. As it runs, it creates a context file (.xml) that contains all the parameters that describe your system. This context file is created and managed by AutoConfig.
  • F

Upgrading 11i E-business Suite to R12 E-business Suite Upgrading 11i E-business Suite to R12 E-business Suite Presentation Transcript

  • Upgrading 11i EBS to R12 Webinar
  • Objective
    • Planning for an upgrade
    • Preparing for Upgrade
    • Upgrading to R12
    • Post Upgrade Tasks
  • Planning for Upgrade
  • Overview
    • Releases of E-Business Suite
    • Best Practice for Upgrade
    • Oracle Application Upgrade Path
    • R12 Technology stack installed on Apps Tier
    • System Requirements
    • Database Size
    • Tablespace Model
    • Scheduling Time for an Upgrade
    • Database Initialization Parameters
  • Releases of E-Business Suite
    • 11i E-Business Suite -May 2000
      • 11.5.7
      • 11.5.9
      • 11.5.10
      • 11.5.10.2
    • R12 E-Business Suite - Jan 2007
      • 12.0.1
      • 12.0.4
      • 12.0.6
      • 12.1.1
      • 12.1.2
  • Best Practice for Upgrade Phase 1: DB Upgrade Phase 2: Apps Upgrade Phases may happen in Separate critical downtimes Dual-Phase Upgrade Single-Phase Upgrade Apps and DB Upgrades must be completed during the same critical downtimes 11.5.1-11.5.6 Upgrade to 11.5.10.2 11.0 Upgrade to 11.5.10.2 11.5.7 11.5.8 9iR2 11.5.9cu2 11.5.10.2 9iR2,10gR1 R12 10gR2 11.5.9(cu1) 11.5.10(cu1) 9iR2,10gR1 Not certified on 10gR2 Certified on 10gR2 Upgrade Target (R12)
  • Oracle Application Upgrade Path Release level Upgrade path 11.0 Release 11.5.10.2  Release 12.1.1 11.5.1 – 11.5.8 Release 11.5.10 CU2  Release 12.1.1 11.5.9, or 11.5.10 (base, CU1,CU2) Release 12.1.1
  • R12 Technology stack installed on Apps Tier
    • Oracle 10g Application Server (AS) 10.1.2
    • Oracle 10g Application Server (AS) 10.1.3
    • Oracle Developer 10g (includes Oracle Forms)
    • Java (J2SE) native plug-in 1.6.0_10
    • Java Developer Kit (JDK) 6.0
  • System Requirements
    • CPU Requirements
      • The size of the database
      • The amount of data in the primary product installation group
      • The number and duration of long-running processes associated with products in this release
    • Memory Requirements
      • Number of concurrent users
      • Infrastructure requirements for multi-tiered architecture
  • Database Size
    • Consider the products.
    • Number of languages being installed.
    • And changes in the data model.
  • Tablespace Model
    • R12 uses the Oracle Applications Tablespace Model (OATM)
    • OATM uses 12 locally managed Tablespace for all products including
      • Temporary tablespace
      • System tablespace
      • System-managed undo (SMU) tablespace.
    • Extent Size
      • For Small systems (upto 100GB) 128k
      • For Multi Tera byte systems 4-10MB
  • Scheduling Time for an Upgrade
    • Reducing Upgrade Downtime
      • Performing certain product-specific tasks before
      • Use Cloning methodology and a test file system to upgrade production system.
    • Backup
      • Strongly recommended to take backup of entire System
  • Database Initialization Parameters
    • Change the following initialization parameters as specified below for upgrade process. Once the upgrade process completes, reset the parameters back.
      • db_file_multiblock_read_count
        • Remove this parameter. (this is not required).
      • _db_file_optimizer_read_count = 8
        • (default setting is 8. Keep default setting).
      • job_queue_processes
        • (set the value of this parameters equal to number of CPUs).
      • parallel_max_servers
        • (set the value of this parameters equal to twice the number of CPUs).
  • Database Initialization Parameters Cont..
      • pga_aggregate_target
    • For 11g
      • _pga_max_size=104857600 (restart the database after changing it)
  • Temporary Tablespace
    • Drop the existing TEMP tablespace
    • Create a New TEMP tablespace as a locally managed tablespace with uniform allocation size.
    • Verify using following query
    select CONTENTS,EXTENT_MANAGEMENT,ALLOCATION_TYPE from dba_tablespaceswhere tablespace_name='TEMP';
  • Select the path to upgrade E-Business Suite Releases Available Paths 11.5.9 (base or CU1) with 9.2.0.x or 10.1.0.x database Path A 11.5.9 CU2 with 9.2.0.x or 10.1.0.x database Path A or Path B 11.5.9 CU2 with 10.2.0.2 database Path B 11.5.9 CU2 with 10.2.0.3 database Path B or Path D 11.5.9 CU2 with 10.2.0.4 database Path B or Path D 11.5.10 (base or CU1) with 9.2.0.x or 10.1.0.x database Path A 11.5.10.2 with 9.2.0.x or 10.1.0.x database Path A, Path B, or Path C 11.5.10.2 with 10.2.0.2 database Path B or Path C 11.5.10.2 with 10.2.0.3 database Path B, Path C, or Path D 11.5.10.2 with 10.2.0.4 database Path C or Path D 11.5.10.2 with 11.1.0.6 database Path C or Path E 11.5.10.2 with 11.1.0.7 database Path C or Path E 11.5.10.2 with 11.2.0.1 database Path E
  • Preparing for the Upgrade
  • Overview
    • Step 1: Apply 11i.AD.I.6
    • Step 2: Run TUMS utility
    • Step 3: Database and System Administration Tasks
    • Step 4: Perform Product Specific Tasks
    • Step 5: Prepare for Upgrade
    • Step 6: Migrate or upgrade your database to at least Oracle 10g Release 2
  • Step 1: Apply 11i.AD.I.6
    • Apply latest AD patch level. p6502082_11i_LINUX_AD.I.6
    SQL> select patch_level from fnd_product_installations where patch_level like ‘%AD%’; PATCH_LEVEL —————————— 11i.AD.I.6
  • Step 2: Run TUMS utility
    • Examines current configuration
    • Creates a report detailing which of the tasks in these instructions to complete and ignore.
    • Apply Patch 7705743, adtums.sql need to run to generate the TUMS report tumsr12.html
    $ cd $AD_TOP/patch/115/sql $ sqlplus <APPS username> / <APPS password> @adtums.sql <directory>
  • Step 3: Database and System Administration Tasks
    • 1 : Perform the Complete Backup for
      • Database
      • Applications
      • Customizations
    • 2 : Upgrade Plan for Customizations
      • For custom Database Objects , rename objects name having Product prefix.
      • Preserve the CUSTOM backup by take custom.pll file. Late it can be used to migrate to new release.
      • Customized forms with 6i will need to upgrade to 10g.
  • Step 4 : Perform Product Specific Tasks
    • Customer Relationship Management Tasks
    • Financials and Procurement Tasks
    • Leasing and Finance Management Tasks
    • Projects Tasks
    • Public Sector/University Tasks
    • Supply Chain Management Tasks
    • Database Upgrade
  • Step 5 : Prepare for Upgrade
    • 1 : Gather schema statistics for CBO
      • Submit a Concurrent Request “Gather Schema Statistics” by providing schema name to All. It is a Required Step
    • 2 : Take cold Backup of the Database
    • 3: Run Rapid Install
      • Run Wizard to lay down the file system and install the new technology stack for the upgraded version.
      • It may have errors because of the database has been yet upgraded.
  • Run Rapidwiz
  • Run rapidwiz: Select Upgrade Action Cont..
  • Run rapidwiz: Select the Port Pool Cont..
    • On the Database Node Configuration screen, describe your existing database.
  • Run Rapidwiz Cont..
    • After completing all required details, click Next to continue.
    • Enter the Character set and NLS Details, Click Next
    • Enter Primary Node and other Node Details and click on Next
    • It performs the pre-install checks
  • Run Rapidwiz Cont..
    • Click on Next , Review the Installations list and Click Next to Start
    • The Installation
  • Run Rapidwiz Cont..
  • Step 6: Migrate or upgrade your database to at least Oracle 10g Release 2 Oracle Application 11.5.9 with CU 2 Oracle Application 11.5.10 With CU 2 Oracle Database 10gR2 Oracle Database 11g Certified with Certified with Certified with
  • Database Upgrade
    • Shut down Applications server processes and database listener
    • Prepare to upgrade
      • Run Database Upgrade Assistant ( Oracle Database Upgrade Guide 11g Release 1 (11.1) )
    • Upgrade Database instance
      • Perform the steps from the &quot;Run the Pre-Upgrade Information Tool&quot; section to the &quot;Upgrade the Database Using the Database Upgrade Assistant“
      • Set Auto Extend for SYSAUX Tablepsace and recommended size is 500MB of size.
      • Modify the Parameter as per the Metalink Note Id:216205.1
      • Perform 11.1.0.7 patch set post-installation tasks (Except 9.1,9.2 and 9.12 Sections)
      • Compile the PL/SQL Codes
  • Database Upgrade Cont..
    • Post Database Tasks
      • Start the New Database Listener
      • Run adgrants.sql from $APPL_TOP/admin
      • Grant create procedure privilege on CTXSYS
        • Copy $AD_TOP/patch/115/sql/adctxprv.sql to database server node and run using following command:
      • Run Autoconfig at database node
        • $ sqlplus apps/<APPS password> @adctxprv.sql <SYSTEM password> CTXSYS
  • Database Upgrade Cont..
    • Gather Statistics for sys schema
    • Re-create Grants and Synonyms
      • 1. run AD Administration
      • 2. select the &quot;Recreate grants and synonyms for APPS schema&quot; task from the Maintain Applications Database Objects menu.
    $ sqlplus &quot;/ as sysdba&quot; SQL> shutdown normal; SQL> startup restrict; SQL> @adstats.sql SQL> shutdown normal; SQL> startup; SQL> exit;
  • Upgrade Process
  • Overview
    • Step 1 : Perform the Upgrade
    • Step 2 : Finishing Upgrade
  • Perform the Upgrade
    • The following tasks are need to perform during the upgrade downtime. Under this step.
      • Disable AOL Audit Trail
        • As a System Administrator Responsibility Navigate to Security=>Audit Trail => Group, set the Group, Set the field to Disable.
        • Run Audit Trail Update Tables report from the Submit Requests window
      • Shut down application tier listeners and concurrent managers
      • Update init.ora with upgrade parameters. (Refer steps in “Planning for Upgrade”)
      • Disable custom triggers, constraints, and indexes
        • Can be enabled after the Upgrade.
      • Drop MRC schema
        • MRC_APPS schema is no longer needed, dropping it frees space and reduces processing overhead during the upgrade.
  • Perform the Upgrade Cont..
      • Back up the database (recommended)
        • Perform a Cold Backup
      • Ensure that Maintenance Mode is enabled
      • Apply AD 12.1.1 upgrade driver (required)
        • Download and unzip the AD Upgrade Driver for 12.1.1 (patch 7461070).
        • Use AutoPatch to run it on all application tier server nodes on your Release 12.1.1 APPL_TOP.
      • Run the American English upgrade patch driver (required)
        • Use AutoPatch to run the (American English) unified driver (u6678700.drv). It is located in $AU_TOP/patch/115/driver.
        • Run the driver on the administration server node on updated Release APPL_TOP using the following commands:
        • $ adpatch options=nocopyportion,nogenerateportion
      • select FND_PROFILE.VALUE('APPS_MAINTENANCE_MODE') from dual
  • Perform the Upgrade Cont..
    • Apply latest product patches (required)
      • Apply Latest Patches for Specific Products. It can be merged using admrgpch and apply once.
    • Disable Maintenance Mode (required)
      • After upgrade Disable Maintenance Mode from adadmin.
    • Reset init.ora parameters (required)
      • Reset the init.ora parameter which was changed before upgrade process.
    • Backup Oracle Applications
  • Finishing Upgrade
    • Configure and start server processes (required)
    • 1) Update the RDBMS ORACLE_HOME file system with AutoConfig files.
        • Login as applcrp2 on ERPTEST and source the environment file.
        • Run admkappsutil.pl:
      • perl $AD_TOP/bin/admkappsutil.pl
      • Script will generate appsutil.zip under $INST_TOP/admin/out directory.
        • Copy appsutil.zip into and unzip RDBMS ORACLE_HOME.
        • Run AutoConfig on the database tier nodes.
      • $ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh
    • 2) Configure and start server processes
      • Start Rapid Install by typing rapidwiz on the command line
  • Finishing Upgrade Cont..
  • Finishing Upgrade Cont..
  • Finishing Upgrade Cont.. /oracle/erptest/appl/inst/apps//iware_erptest/appl/admin/iware_
  • Finishing Upgrade Cont..
  • Finishing Upgrade Cont..
    • Click Next and Complete the configurations.
    • Reapply the Customizations.
      • Re-integrate the custom application, make necessary changes in devenv.env / adovars.env and restart the services effect the changes made.
    • Integrate custom objects and schemas
    • Re-enable custom triggers, constraints, and indexes
    Finishing Upgrade Cont..
  • Post – Upgrade Tasks
  • Overview
    • Post – Upgrade Tasks
    • Upgrade R12.x.x to R12.1.1
    • Upgrade to R12.1.2
  • Post – Upgrade Tasks
    • Complete Workflow Notification Mailer configuration
      • Log with System Administrator Responsibility having access to Oracle Applications Manager.
      • From the Applications Dashboard, select the Workflow Manager from the &quot;Navigate to&quot; pull-down menu. Click Go.
      • In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page. The Notification Mailers status icon should show a status of Down.
      • On the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the notification mailer configuration wizard.
      • Enter Outbound Email Account (SMTP) and inbound (IMAP) server details Click Apply.
      • Return to the Service Components page, and verify that the status of the Workflow Notification Mailer service component status is Running.
  • Post – Upgrade Tasks Cont..
    • Complete setup for Oracle XML Gateway
    Profile Option Description ECX: XSLT File Path Path to the directory specified as the location for style sheets to be used for XSLT transformations. It must be one of the valid values specified in the UTL_FILE_DIR database initialization parameter. Ensure that there is no slash at the end of the directory name. ECX: System Administrator Email Address Address to which Oracle XML Gateway error notifications should be sent. ECX: Server Time Zone Time zone the database server is running in
    • Verify completion of concurrent programs
    • Install online help (recommended)
    • Update/verify custom responsibilities
    • Migrate custom development to new technologies
    • Migrate the CUSTOM library
    Post – Upgrade Tasks Cont.. Note : Post – Upgrade tasks depends on the Application implemented and Setup environment
  • Upgrade R12.x.x to R12.1.1 R12.0.1 – R12.0.6 R12.1.1 R12.1.X 11.5.7 – 11.5.10.2
  • Upgrade to R12.1.2
    • For Upgrade R12.0.4  R12.1.1
      • Metalink Note : 752619.1
      • Release 12.1.1 maintenance pack Patch 7303030.
    • Metalink Note : 949406.1
      • For Upgrade R12.1.1  R12.1.2
      • E-Business Suite Release 12.1.delta.2 Release Update Pack (12.1 RUP2)
    • Help Upgrade for R12
      • 12.1.1 Help (7303031)
      • 12.1.2 Help (7303032)
  • Metalink References Details Doc Id Estimate tablespace sizes for test upgrade 399362.1 E-Business Suite Release 12 Upgrade Sizing and Best Practices 399362.1 Initialization parameters 396009.1 Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade 761570.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0) 452783.1 Oracle E-Business Suite Readme, Release 12.1.2 949406.1 Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 upgrade 403339.1 Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade 761570.1
  • Summary
    • Planning for Upgrade
      • Best Practice for Upgrade
      • Oracle Application Upgrade Path
      • Select the path to upgrade
    • Preparing for the Upgrade
      • Apply 11i.AD.I.6 and Run TUMS utility
      • Prepare for Upgrade
      • Migrate or Upgrade your database to at least Oracle 10g Release 2
    • Upgrade Process
      • Perform the Upgrade
      • Finishing Upgrade
    • Post – Upgrade Tasks
      • Post – Upgrade Tasks
    • Upgrades to R12.1.2
  • iWare Logic's Oracle DBA and Apps DBA Services
    • iWare Logic, an Oracle Gold Partner, focuses on Oracle Enterprise Applications. We provide expertise to our customers in the efforts to Implement and Support Oracle's Enterprise Business Applications and Technologies.
    • iWare Logic's Oracle DBA and Apps DBA Services
    • iWare Logic has highly experienced Oracle DBA and Oracle Apps DBA team and. We offer a range of Onsite and Remote Oracle DBA and Oracle Apps DBA support and services,
    •         Installations, Configurations
    •          Migrations
    •          Upgrades (releases 11.0, 11i, and R12)
    •          Onsite Support
    •          Remote Database Support
    •         AMC (Annual Maintenance Contracts)
    • Database Audits and Recommendations
    • Clones and cloning automation
    • Patching
    • Capacity and maintenance planning
    • Training
  • Questions and Answers
  • Thank You
    • iWare Logic Technologies Pvt. Ltd.
    • Aditi Samruddhi,
    • Baner, Pune,
    • India - 411045
    • Email: [email_address]
    • Website: www.iwarelogic.com