Oracle E-Business Suite Release 12.

1 upgrade and platform migration guide HP AlphaServer systems running Tru64 Unix to HP-UX on Integrity servers
Technical white paper

Table of contents
Executive summary............................................................................................................................... 3 Introduction ......................................................................................................................................... 4 Recommended test platform and backup strategies............................................................................... 6 Project test environment .................................................................................................................... 6 Recommended migration path ........................................................................................................... 7 Conventions ........................................................................................................................................ 8 Prerequisites ........................................................................................................................................ 9 Migration project test platform............................................................................................................. 10 Preliminary phase .............................................................................................................................. 11 Migration prerequisites ....................................................................................................................... 13 Phase 1: Upgrading the source RDBMS to 10gR2 ................................................................................. 15 1.1 Prepare the source database server for 10gR2 upgrade ............................................................... 16 1.2 Install RDBMS 10gR2 on the source database server .................................................................... 17 1.3 Upgrade Applications database to 10gR2 .................................................................................. 20 Phase 2: Migrating Oracle Applications 11i database to HP Integrity server ............................................ 28 Constraints of using XTTS ................................................................................................................ 28 2.1 Prepare the source database node ............................................................................................. 29 2.2 Prepare the target database node .............................................................................................. 31 2.3 Export the source Applications 11i database objects .................................................................... 36 2.4 Import the Applications 11i database objects to the target database node ...................................... 39 2.5 Upgrade the target Applications 11i database instance................................................................ 41 Phase 3: Migrating to E-Business Suite Release 12.1.1 ........................................................................... 47 3.1 Prepare source for E-Business Suite Release 12.1.1 upgrade ......................................................... 47 3.2 Upgrade to E-Business Suite Release 12.1.1 ................................................................................ 50 3.3 Perform post upgrade product specific tasks ................................................................................ 51 Phase 4: Upgrade E-Business Suite R12.1.1 to Release 12.1.2 ............................................................... 52 4.1 Pre-requisite checks .................................................................................................................. 52 4.2 Applying the Release Update Pack ............................................................................................. 53 4.3 Apply Post-Release Update Patch ............................................................................................... 53 4.4 Post-update steps ...................................................................................................................... 53 Phase 5: Upgrade E-Business Suite RDBMS from 10gR2 to 11gR2........................................................... 55 5.1 Prepare the database server for 11gR2 upgrade ......................................................................... 55 5.2 Install Oracle RDBMS 11gR2..................................................................................................... 56

5.3 Upgrade E-Business Suite RDBMS to 11gR2 ................................................................................ 59 Appendix A: Kernel parameters .......................................................................................................... 66 Appendix B: Pre-Upgrade Information Utility output file .......................................................................... 67 Appendix C: Post-Upgrade Information Utility output file ......................................................................... 72 Appendix D: XTTS example files .......................................................................................................... 74 Appendix E: Oracle E-Business Suite R12 Upgrade Report (TUMS) – VIS .................................................. 82 Appendix F: Recommended Oracle Support Portal documents ................................................................ 83 Appendix G: Validate the E-Business Suite environment .......................................................................... 84 For more information .......................................................................................................................... 86

Executive summary
Oracle Applications Release 11i is widely deployed across a broad range of HP server platforms: HP AlphaServer systems running Tru64 UNIX®, HP 9000 servers running HP-UX and HP ProLiant servers running Linux or Microsoft® Windows®. Customers on those and other vendor platforms are faced with the impending obsolescence of Oracle Applications Release 11i and/or the operating system hardware combinations on which they are deployed. The decisions facing these customers relate to how to migrate their Oracle Applications Release 11i environments to a new platform, and whether to upgrade to Oracle E-Business Suite Release 12.1 at the same time. Oracle E-Business Suite Release 12.1 is certified on several new platforms including HP Integrity servers running HP-UX 11i v3 for both application and database tiers. Also, HP Integrity servers running Linux and Windows are fully certified as the database-only platform for both Oracle Applications Release 11i and Oracle E-Business Suite Release 12.1(known as “Split Configuration Database Tier” in Release 11i and "Mixed Platform Architecture" in Release 12.1). This document is a guide for Oracle Applications Release 11i customers looking to perform platform migration from HP AlphaServer systems running Tru64 UNIX to HP Integrity servers running HP-UX 11i v3 and upgrade their Oracle Applications Release 11i environment to Oracle E-Business Suite Release 12.1. The procedures captured within this document are extracted from various Oracle notes and guides, and includes additional steps required for customers running HP AlphaServer systems to complete the migration. This document can also be used as an outline to migrate other vendor platforms to HP Integrity servers. The procedures within this document are common amongst Oracle Applications Release 11i environments. However, Oracle Applications is comprised of over 200 business software products, such as Financials, Manufacturing, Human Resources, and so on. Each product will have its own specific upgrade tasks that will not be covered within this document. HP recommends that the local experts study the document Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.1 (Part# E14010-01) in order to determine the proper migration plan for each business software product. Target audience: The intended audience for this document is IT professionals who deploy and support Oracle E-Business Suite on HP platform. In-depth familiarity with Oracle Database and Oracle EBusiness Suite is required. DISCLAIMER OF WARRANTY This document may contain the following HP or other software: XML, CLI statements, scripts, parameter files. These are provided as a courtesy, free of charge, “AS-IS” by Hewlett-Packard Company (“HP”). HP shall have no obligation to maintain or support this software. HP MAKES NO EXPRESS OR IMPLIED WARRANTY OF ANY KIND REGARDING THIS SOFTWARE INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NONINFRINGEMENT. HP SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, WHETHER BASED ON CONTRACT, TORT OR ANY OTHER LEGAL THEORY, IN CONNECTION WITH OR ARISING OUT OF THE FURNISHING, PERFORMANCE OR USE OF THIS SOFTWARE.

3

Introduction
Oracle E-Business Suite (EBS) is Oracle‟s original Enterprise Resource Planning (ERP) application and incorporates over 200 product-specific business applications. ERP, in this case, is a term referring to a set of applications connected by a single database (DB) that serves some or all of the business processes within an organization. Oracle E-Business Suite includes an application tier that contains all the business logic for the various business processes and a database tier that stores all the businesscritical data. E-Business Suite deployments generally require a unique plan for each environment to successfully migrate the data, application customizations, and product-specific functionality to the target platform. This document does not cover the procedures for patching, migrating customizations, performing product-specific tasks, functional testing, add-on software, or other languages support. The focus is strictly platform migration and the upgrade of the Oracle E-Business Suite technology stack.
Note: Oracle Applications Release 11i customization coding uses Developer 6i Forms & Reports and OA Framework (BC4j Java Container) using JDeveloper9i/10g. Most of the core functionality in Release 11i utilized Developer 6i Forms & Reports. But, E-Business Suite Release 12.1 uses Developer 10g Forms & Reports and OA Framework (OC4J Java Container). Also, a lot of core functionality in Release 12.1 has been moved from Forms & Reports to OA Framework web pages i.e. a functional flow which used to be executed in Forms in Release 11i now utilized OA Framework web pages for the same in Release 12.1. Due to aforementioned technology stack differences in Oracle E-Business Suite Release 11i & 12.1, it is not possible to automatically upgrade Release 11i customization to the new Release 12.1. Developers may need to recompile Forms & Reports customization and rebuilt OA Framework extension while migrating to Release 12.1. There are Oracle notes to help in doing the same, e.g. 563258.1 - How to Upgrade 11i Custom Forms to R12 451934.1 - Accessing Custom Forms After Upgrading From To R12 780989.1 - R12: Upgrade vs. Reimplementation (Financials) 1292611.1 - Upgrading Form Personalizations and OA Framework Personalizations from Oracle E-Business Suite Release 11i to 12.1 In a technological white paper like this, it is not possible to cover the customization and extensions as it varies from customer to customer.

Depending on the release of Oracle Applications 11i, the platform migration and application upgrade may require a preliminary phase. The preliminary phase consists of upgrading to the recommended 11.5.10.2 release. This phase is required for all Oracle Applications 11i environments running 11.5.8 and earlier. Customers running Oracle Applications Release 11.5.9 (base, CU1) and 11.5.10 (base, CU1) are not required to upgrade to 11.5.10.2 release if they are willing to perform all the platform migration and application upgrade phases in a single downtime window. Only Oracle Applications 11.5.9 (CU2) and 11.5.10 (CU2) versions support the split-configuration deployment that allows for pausing between the phases described in this document. For this particular project, the source configuration used Oracle Applications 11i Release 11.5.10 (CU2), which did not require a preliminary phase. At the end of each phase of the migration the EBusiness Suite environment will be in a fully supported configuration. This migration strategy allows for the migration to be paused between phases in order to resume normal operation until continuing onto the next phase. The platform migration and application upgrade consist of three main phases and two optional phases.

4

1. Phase 3: Upgrade Oracle E-Business Suite to Release 12.2. Phase 2: Migrate Oracle Applications Release 11 i database Phase 2 consists of creating a split configuration database tier in Oracle Applications Release 11i by performing a platform migration of the source Oracle Applications Release 11i database instance from the HP AlphaServer systems running Tru64 UNIX to the HP Integrity server. or IBM AIX as the application tier platform and most of the RDBMS supported platforms. Tru64 UNIX. For more details review Oracle Support Portal document: Cross Platform Transportable Tablespaces on 11i with 10gR2 [ID 454574. installing a new Oracle E-Business Suite Release 12. applying Release 12. review the „Certifications‟ page on the Oracle Support Portal website. Microsoft Windows. This document explains & utilizes Cross-Platform Transportable Tablespace (XTTS) migration process of the source Applications 11i database to target Integrity HP server. At the end of this phase. You can also use alternative migration option such as export and import of the source Applications 11i database as explained in Oracle Support Portal document: 10g Release 2 Export/Import process for Oracle Applications Release 11i [ID 362205.1. Oracle Split configuration database tier also supports Linux. For more details review Oracle Support Portal document Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 2 [ID 369693. you can optionally upgrade to Oracle E-Business Suite Release 12.1.Phase 1: Upgrading the source RDBMS to 10 gR2 Phase 1 consists of upgrading the source Oracle Applications 11i database instance to 10gR2 (Version 10.1 with RDBMS 10gR2. Also.1 upgrade steps. Oracle Solaris. At this stage. Premier Support for 10gR2 Database officially ended in July 2010.04).1.1.1. For that reason.1.1].1.0. HP recommends upgrading to 11gR2 as part of the EBS migration process.1 Phase 3 consists of preparing the Oracle Applications Release 11i database for E-Business Suite Release 12.1 to upgrade it to Release 12.2 and Oracle RDBMS 11gR2 by following two optional phases: Phase 4: Upgrade Oracle E-Business Suite to Release 12.1 and HP Integrity servers. 5 .1. Note Oracle RDBMS 11gR2 Patch set 11.1 home on the target HP Integrity server.2.1 upgrade patch and executing rest of the R12.1.3 or above may skip this phase and move on to Phase 2.1 is now supported with Oracle EBusiness Suite Release 12.1].2 Phase 5: Upgrade Oracle E-Business Suite database to Oracle RDBMS 11gR2 This phase consists of upgrading the Oracle E-Business Suite database to Oracle RDBMS 11gR2.1]. For more details on supported Oracle Applications 11i Split Configuration database tier. Customers who have already upgraded to RDBMS 10.1.0.2. the Oracle Applications 11i environment will be in a fully supported split configuration where the Oracle Applications 11i application tier components are running on the HP AlphaServer systems and the database tier components are running on the HP Integrity server.1] and Using Oracle EBS with a Split Configuration Database Tier on 11gR2 [ID 946413. you can continue to use Release 12.2 This phase consists of patch application on top of Oracle E-Business Suite R12.

e. Such testing should use a recent clone with the same patch level as the production environment to yield an accurate estimate of downtimes.2 environment and two HP Integrity servers running HP-UX 11i v3 for the target Oracle E-Business Suite Release 12. one for application tier and other for database tier.1. Plan the testing of all phases on a suitable test environment to get a fair estimate of downtimes required for each phase. The length of downtime will depend on the system configuration and database size.5. These backups will minimize the risk of business disruption by enabling a quick rollback to a working configuration should an unexpected failure occur. 6 .1 environment.10.1. The test executions also provide the opportunity to document any additional steps or patches required for each phase of your migration/upgrade. It is strongly recommended to perform a complete backup of the E-Business Suite environment before and after each phase. third-party products.These additional phases (4 and 5) are independent of each other. This migration strategy allows customers to pause the migration/upgrade process between phases in order to resume normal operation and minimize disruption of the business processes. Only the base components for E-Business Suite and the Vision Demo database were installed. In this document we have first upgraded the database from 10gR2 to 11gR2 and then upgraded Oracle E-Business Suite from R12. Project test environment The test environment used to develop this white paper comprised of two HP AlphaServer systems running Tru64 UNIX as the source platform for the Oracle Applications Release 11. the E-Business Suite environment will be in a fully supported configuration. Oracle E-Business Suite two-node installation has been used i.1 to R12.2. excluding any Oracle add-on software. At the end of each phase. and foreign languages. Recommended test platform and backup strategies Each phase will require some downtime.

2.Recommended migration path The following figure outlines the approach to the migration/upgrade process.2.2 Tech Stack Oracle Applications 11.4 Applications 11i DB RDBMS 10.4 Applications 11i DB RDBMS 10.tier HP-UX Integrity Target DB.0.1 Techstack EBS Release 12.6 Applications 11i DB RDBMS 10.4 EBS Release 12.4 Phase II Migrate Applications 11i Database Phase III Perform Pre-Upgrade product specific tasks and apply R12.4 Source DB-tier HP Alpha Server TRU64 UNIX Phase III Install R12.2 Tech Stack Source Apps-tier HP Alpha Server TRU64 UNIX RDBMS 9.10.2.2.4 Software only RDBMS 10. Figure 1.5.0.4 Applications 11i DB Retired RDBMS 10.0. Recommended Migration path Source Applications 11i Environment Phase I Upgrade Database 10.10.0.2.2 Tech Stack Retired Oracle Applications 11.0.0.2 Tech Stack Oracle Applications 11.1 Applications Tech Stack Target EBS R12.5.10.5.1 Upgrade Patch EBS Release 12.2.0.0.0.10.2 Tech Stack Oracle Applications 11.5.4 Applications 11i DB RDBMS 10.1 Upgrade Patch Oracle Applications 11.tier HP-UX Integrity RDBMS 10.2.2.2.1 Environment Phase II Migrate Applications 11i Database Phase III Pre-Upgrade Tasks Target Apps.1 DB 7 .0.5.2.10.4 Applications 11i DB RDBMS 10.1 Applications Tech Stack Phase III Apply EBS R12.

concurrent processing.3 and OC4J ) Applications Developer 10. Conventions and meaning Convention Software staging area Source application tier Meaning Generally located on an NFS server consisting of Oracle and HP installation software and patches for the migration. HP-UX Integrity server consisting of the RDBMS 10gR2_ORACLE_HOME. applications technology stack. HP AlphaServer systems running Tru64 UNIX consisting of the Oracle Applications Release 11i home. HP AlphaServer systems running Tru64 UNIX consisting of the RDBMS 9iR2 and 10gR2 ORACLE_HOMEs and the Applications 11i Database <10g_ORACLE_HOME>10gR2 home.3 home (Tools. report. Applications 8. and the admin. applications technology stack.1 Database RDBMS 10gR2 home. Source APPLMGR environment file: <APPL_TOP>/APPS<SID>_<hostname>. 11gR2_ORACLE_HOME and the Applications R12. or Dev ORACLE_HOME. report.0.sh opatch rapidwiz runInstaller Monospace Text <> # $ <SID> Database Site Identifier Application DBA administration utility Application DBA patching utility Application DBA configuration utilities (AutoConfig) RDBMS DBA patching utility Oracle Rapid Install Wizard for E-Business Suite Oracle Install Wizard for RDBMS Represents command line text Text enclosed in angle brackets represents a variable Preceding # on a command line text represents ROOT level access Preceding $ on a command line text represents ORACLE or APPLMGR user access Source database tier Source ORACLE_HOMEs Target database tier Target ORACLE_HOMEs 8 . and the admin. and web server services. home. 11gR2 home Applications 10. <9i_ORACLE_HOME> 9iR2 home Applications iAS home. C.6 home Source APPL_TOP Target application tier Applications 11i home HP-UX Integrity server consisting of the E-Business Suite Release 12.1. Source ORACLE environment file: <ORACLE_HOME>/<SID>_<hostname>.1 home User who owns the Applications file systems. concurrent processing.env ORACLE User who owns the database file systems.1.env ORACLE_SID adadmin adpatch adconfig.Conventions Table 1. and web server services. Apache 1.4 AS home (Web or Java ORACLE_HOME. forms.3 . forms. Forms 10 and Reports 10) Target APPL_TOP APPLMGR E-Business Suite Release 12.2.1.

Prerequisites Prior to beginning the platform migration the following software versions should be considered the minimum operating version levels. September 2010 Details 5.1 RDBMS 10gR2 RDBMS 11gR2 target APPS-Tier HP-UX on Intel Itanium Database release target DB-Tier HP-UX on Intel Itanium The following operating system patches should be applied.x target DB-Tier E-Business Suite Release 12.1b Location source DB-Tier source APPS-Tier Applications release Applications Release 11.5. Table 2.1b 9 . Minimum operating version levels Source software Tru64Unix Minimum version 5. Table 3.1.1.10. Operating system patches OS patches Tru64Unix (Source) HP-UX 11i v3 (Target) n/a Patch number n/a Location application Tier database Tier applications Tier database Tier Quality Pack.2 Includes RDBMS 9iR2 source APPS-Tier source DB-Tier Details HP AlphaServer systems running Tru64 UNIX HP AlphaServer systems running Tru64 UNIX HP AlphaServer systems running Tru64 UNIX Database release RDBMS 9iR2 RDBMS 10gR2 source DB-Tier HP AlphaServer systems running Tru64 UNIX Target software HP-UX Minimum version 11i v3 Location target DB-Tier target APPS-Tier Details HP Integrity server (HP-UX on Intel® Itanium®) HP-UX on Intel Itanium Unzip for HP-UX 11i v3 Applications release 5.

2 Source DB server: HP AlphaServer systems Tru64 UNIX 5.6 Oracle RDBMS 10gR2 Target APPS server: HP Integrity HP-UX 11i v3 Oracle E-Business Suite Release 12.5.1. The target APPS server was prepared for the installation of E-Business Suite Release 12. admin. The target DB server was installed with Oracle RDBMS 10gR2 and prepared for Applications 11i Vision Demo database platform migration. and web server) and database tier (RDBMS file system and Applications 11i database) installed on two different servers.1B Oracle E-Business Suite 11. 10 .1 Target DB server: HP Integrity HP-UX 11i v3 Oracle RDBMS 10gR2 Oracle RDBMS 11gR2 The source application and database components for Oracle Applications Release 11. A two-node installation consists of application tier (application file system. technology stack. concurrent processing. forms.0. Oracle RDBMS 10gR2 was also installed on the source DB server in a different ORACLE_HOME for the Applications 11i Vision Demo database 10gR2 upgrade. Source APPS server: HP AlphaServer systems Tru64 UNIX 5. The migration document was developed using the following configuration.2 were installed in a two-node architecture using the Vision Demo database.1 home.5. The Vision Demo database is a sample database used to simulate a medium-size company using some of the more popular E-Business Suite software components.2. report.1B Oracle RDBMS 9.10.10.Migration project test platform All the steps recorded in this migration document are specific to this test platform.

9(CU2) before beginning the migration process is highly recommended in order to take advantage of the phased migration approach.5.1 uses Oracle E-Business Suite Tablespace model (OATM). Oracle E-Business Suite Release 12.5.2 prior to beginning the migration process described in this document. at a minimum. Release 11. For more information.10. Customers who need to continue operating the deployment at some intermediate point – for example after the initial database upgrade to 10gR2 – should consider upgrading to 11.2 Maintenance Pack Installation Instructions [ID 316365.10.Tablespace Migration Utility [ID 248857.9 and 11. 11. refer Upgrading Oracle Applications Release 11i (11.2 before beginning the migration.Preliminary phase Upgrading to Oracle Applications Release 11. refer to Oracle Support Portal document: Oracle Applications Release 11.2).1] 11 .5. including the temporary tablespace.10.10.1] Deployments of 11. system tablespace.10 support this tablespace model while earlier releases will need to migrate to this model to take full advantage of the Release 12.5. Part Number B19297-01.8 and earlier must upgrade to 11. and systemmanaged undo (SMU) tablespace. OATM uses 12 locally managed tablespaces for all products.1 features.5. which is based on database object type rather than product affiliation.5.10. For more information.2 or.5. For further details see Oracle Support Portal document: Oracle Applications Tablespace Model Release 11i .5.5.

5.2. Figure 2.6 · Apply 11.8 And earlier Perform Phases I Through III Of the migration/Upgrade Perform All phases of the Migration/Upgrade Note: Only after completing all phases can the EBS environment be brought on-line in a fully supported state Source EBS 11.10.5. Process migration flow Preliminary Phase Upgrade in Place EBS 11.The following figure shows the process migration flow.0.0.2 CU2 Maintenance pack Source EBS 11.6 Tasks: · Upgrade RDBMS to 9.2. CU1) 11.6 · Apply 11.0.2 CU2 RDBMS 9.2.5.9(base.10.5.2 CU2 Maintenance pack Perform Phases I Through III Of the migration/Upgrade 12 .10.10.5.5.6 Tasks: · Upgrade RDBMS to 9.2.5.10(base.0.2 CU2 RDBMS 9. CU1) OR Preliminary Phase Upgrade in Place EBS 11.

and customizations. Note This document was written in September of 2010 and all of the following patches named in this document were available at that time.1] The Applications 11i patches in the following table were applied to the application tier in the order listed.5. Most customers will run through the migration process a number of times on their test environments before finally implementing it in the production environment. Oftentimes. HP strongly recommends that all migration tasks described in this document be applied first to a test environment in order to determine application downtime and record any additional steps that may be necessary for proper migration of add-on software‟s.AD. There may be some advantages to applying a superseded patch or patch set that better supports your current environment. It is also recommended to perform a full backup of the entire environment before starting and ending each phase of the migration. to reduce resource bottlenecks and expedite the effort. National language support (NLS) will also require additional patches. The following application patch list includes the patches required before starting the migration. a superseded patch or patch set will contain many other patches.0) [ID 362203.2.2.I. Pay close attention to possible dependent patches and note any additional steps not covered in the guide. Additional patches may be required for third-party products and other E-Business Suite software modules not included with the base installation. The test source platform included Oracle Applications 11. 13 .Migration prerequisites Oracle E-Business Suite is highly configurable and customizable with many customers deploying their own unique environments. languages.2. additional storage and CPU resources may be required during the migration process. Always confirm patch list with the latest Oracle Support Portal documents and follow the patch readme instructions unless otherwise directed. which may produce unexpected results. Developer 6i Patch Set 16 and AutoConfig 11i. For more information. refer to Oracle Support Portal document: Oracle Applications Release 11i with Oracle 10g Release 2 (10. For this reason. Also.10.

Logon as the owner of the 9i database instance and source the environment file. If any invalid objects are found.I.I. Re-check the database for invalid objects before and after each phase or milestone.object_type FROM dba_objects WHERE status=’INVALID’.AD. 14 .AD. Application patches Application patches Dev6i Patch Patch number 4948577 Details Developer 6i Patch Set 18 Oracle Support Portal document: 125767.7 and TXK Rollup Patch includes dependent patches listed in the readme notes for the 10gR2 Interoperability patch. Interoperability patch 4888294 8217898 4653225 EBS Interoperability patch for Developer 6i Patch Set 18 TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH T Applications DBA Minipack Patch 11I.1 One-off patches for Developer 6i Patch Set 18 Additional Dev6i Patches 5713544 4261542 5216496 5753922 6195758 Interoperability patch Dependent patch Dependent patch Note: The latest Applications DBA Minipack 11i. although it is possible that the steps conducted during the migration may repair or otherwise eliminate some object corruption. use ADADMIN to remove as many as possible before continuing.Table 4. Note You can expect some additional invalid database objects to be generated during the migration process. SQL> SELECT owner. $ sqlplus '/ as sysdba' SQL> SELECT count(*) FROM dba_objects WHERE status='INVALID'. Connect to the 9i database using SQL*Plus with SYSDBA privileges to check for any invalid objects.7 4653225 10gR2 APPS INTEROPERABILITY PATCH Before starting the migration. record any invalid objects in the 9iR2 database.object_name.

1.0. At this time. Phase 1 will upgrade the database instance to Oracle RDBMS 10gR2 by first installing a new 10gR2_ORACLE_HOME.2 RDBMS 9. Oracle Database release 10.1.1b EBS 11.2.2.2) for HP Tru64 UNIX Part Number B25300-01 and Oracle Support Document: Oracle Applications Release 11i with Oracle 10g Release 2 (10. During this upgrade phase of the migration.0.4 Phase II Migrating Applications 11i database to HP Integrity server Phase III Upgrade to Release 12.10.2.0.2.0.2.6 to 10. An upgrade of Oracle Applications Release 11i to Oracle E-Business Suite Release 12.10. and then upgrade the Applications 11i database instance using the Database Upgrade Assistant (DBUA).2 in new 10g Oracle home · Apply RDBMS 10. Upgrading now to 10.0.1.6 Section 1: Prepare DB Node to Upgrade · Full Backup · Update Software to required level · Apply 10gR2 Introp patch Section 2: Installing 10.Phase 1: Upgrading the source RDBMS to 10gR2 The source environment consists of HP AlphaServer systems running Tru64 UNIX with Oracle Applications Release 11.2. Figure 3.0.2.0.3 is the minimum RDBMS release supported by Oracle E-Business Suite Release 12.2.4 patchset Section 3: Upgrade 11i applications database · Perform DBUA (Database Upgrade assistant) · Migrate Autoconfig · Validation tests Once all the tasks have been completed in phase 1.0.0.0.6 to 10gR2 Phase I Upgrade RDBMS 9. Upgrade source RDBMS 9.0.0.2.1. then you can proceed directly to Phase 2: Migrating Applications 11i database to HP-UX 11i v3 on Integrity server.4. the migration can be paused to resume normal operations or if time permits.1 is currently supported.2. 15 .2. the E-Business Suite 11i environment will be in a fully supported mode with the upgraded 10gR2 database. you will: · Section 1: Prepare the source database server for 10gR2 upgrade · Section 2: Install RDBMS 10gR2 on source database server · Section 3: Upgrade Applications 11i database to 10gR2 on source database server Section 2 does not depend on section 1 and can be performed first or simultaneously.4 for HP AlphaServer systems running Tru64 UNIX.0. determine if your particular environment requires any additional steps by thoroughly reading both the Oracle Database Installation Guide 10g Release 2 (10.2 and the Vision Demo database instance based on Oracle RDBMS 9.4 will reduce the need to upgrade at a later date.2.2. If your company has already upgraded the Applications 11i database to 10g R2 10.4 · Install RDBMS 10.2.2. Before proceeding.6.3 to 11.0) [ID 362203. continue on with Phase 2: Migrating Oracle Applications 11i database to HP-UX Integrity server.5.1 on HP Integrity server Source Tru64 5.0.5.1 with database versions from 10.1] Note Oracle Applications Release 11i now supports Oracle RDBMS 10.0.2.3 or later and you do not want to upgrade to 10.

4 Update applications tier context file In this phase of the migration. 1. It is recommended that a backup of the context file be made before making any changes. 1. shutdown the Oracle Applications 11i environment and take a full cold backup of both the application tier and database tier. and port addresses will remain the same for the database tier.4. Download and stage the Oracle RDBMS 10gR2 (Version 10.9 from E-Business Suite 11i [ID 312349. host.1]. SID.2) and Example CD installation media for HP AlphaServer systems running Tru64 UNIX from Oracle‟s software download website.0.0 for Oracle database server on HP AlphaServer systems running Tru64 UNIX from Oracle Support Portal. The only change needed at this time will be to update the variable s_apps_jdbc_connect_descriptor to a NULL value in the applications context file. An improper value could render the applications inaccessible.9 should be removed only after the installation of Oracle Portal 10g.0.0. along with some additional steps to complete the upgrade.xml \ $APPL_TOP/admin/<SID>_<hostname>. download and stage the Oracle RDBMS 10gR2 patch set 6810189 10.0. then you must also update AutoConfig setup on the database tier and deregister the existing database server node.2.1]. To use OAM to modify the context file.com/technology/software/index. then the existing Oracle Portal functionality must be migrated to Oracle Portal 10g to ensure compatibility with Oracle Database 10gR2.0.1. Also. Oracle Portal 3.0) [ID 362203.oracle. the hostname.1. 1.2.html.9 in future then you can remove Oracle Portal 3. $ cp $APPL_TOP/admin/<SID>_<hostname>.0.1.DOMAIN_NAME:8000). http://www.0.xml.1]. The following steps were derived from Oracle Support Document: Oracle Applications Release 11i with Oracle 10g Release 2 (10.2 Oracle Portal 3.1 Prepare the source database server for 10gR2 upgrade This section includes the tasks to prepare the source database server for the upgrade to RDBMS 10gR2.9 and any dependencies from Oracle Applications 11i by performing the steps in Oracle Support Portal document: Remove Oracle Portal 3. SID. • From your browser link to the E-Business Suite Web server port (Default http://APPS_NODE. If you are not planning to use Oracle Portal 3.9 in your current Oracle Applications 11i environment.1. Review the Oracle Support Portal document: Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i [ID 233436.orig It is recommended to use Oracle Applications Manager (OAM) to edit the context file. • • Login OAM as “sysadmin” Click on “Site Map” link 16 .0. or database name parameters on the database server.1 Backup the Oracle Applications 11i environment For rollback purposes. 1.3 Deregister the existing database server (conditional) If you are planning to use a new database port.9 check (conditional) If you are using and planning to continue to use Oracle Portal 3.1.2.

0.2_staging_directory> $ .0. as well as some kernel settings have been superseded or discontinued.sh contextfile=<APPL_TOP>/admin/<SID>_<hostname>.2 installation media staging area. Many of the required patches.0 software Start up an Xterm session on the source database server as the “oracle” user.sh apps/<apps_password> $AD_TOP/bin/adconfig.sh apps/<apps_password> 1. DO NOT source the 9i database environment file. $ cd <10./runInstaller Select Installation Type Enterprise Edition Specify Home Details Name: OUIHome2 Path: <10gR2_ORACLE_HOME> Product-specific prerequisite checks The warning status for the OS and kernel patches can be ignored if running the prescribed software releases and kernel settings. select OA_VAR In the next field enter “s_apps_jdbc_connect_descriptor” Click on the GO button Update the value to NULL Click on the SAVE button Enter a comment if necessary In order for this value to take effect. $COMMON_TOP/admin/scripts/<SID>_<HOSTNAME>/adstpall.2) for HP Tru64 UNIX Part Number B25300-01 and the "System Considerations and Requirements" section of Chapter 3 of the Oracle Database Upgrade Guide 10g Release 2 (10. 1. read Chapters 1 and 2 of the Oracle Database Installation Guide 10g Release 2 (10.2) Part Number B14238-02.2.1 Preparation to create the 10.2.xml $ $COMMON_TOP/admin/scripts/<SID>_<HOSTNAME>/adstrtall.0.2.2 Install RDBMS 10gR2 on the source database server This section includes the steps to install the software-only version of the Oracle RDBMS 10gR2 on the source HP AlphaServer systems running Tru64 UNIX. you will have to shut down the APPS-Tier server services.• • • • • • • • Click on “AutoConfig” link Click on the Edit Parameters icon for Applications Tier Under the Search pull down menu.2 Oracle home To understand the installation and upgrade processes. Upgrade an Existing Database NO 17 . Execute any additional steps that are relevant for your environment. 1.2.2.2. and run the Oracle Universal Installer (OUI).2 Install the base 10. run AutoConfig and then restart the APPS-Tier server services. change directory to the 10.

2.2. 1. change directory to the 10.4 patch set staging area and run the Oracle Universal Installer.2. "Installing Oracle Database 10g Products" in the Oracle Database Companion CD Installation Guide for your platform.0.2. · The ORACLE_HOME environment variable points to the new 10.2.5. In the Installation Types window.0. · The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new Perl executable is located (usually $ORACLE_HOME/perl/bin).2. Make sure that: · You DO NOT source the 9i database environment file.Select Configuration Option Install database software only Execute Configuration scripts Popup As root user run the following script: # <10gR2_ORACLE_HOME>/root. · The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib. patch set installation process and any "Preinstallation Tasks" before starting the patch set installation.3 \ :$ORACLE_HOME/perl/lib/site_perl/5.8.0. use the Product Languages button to select any languages other than American English that are used by your Applications database instance. extract the 10. Understand the upgrade. Do not perform the tasks in the "Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation" section. execute the tasks in section 3.4 patch set pre-installation tasks On the database server node.0.8.4 patch set file. 18 .2.4 Execute 10.3 $ cd <10.sh End of Installation 1.3 Install Oracle Database 10gR2 Products from the 10g Companion CD On the database server node.4 patch set installation tasks Start up an Xterm session on the source database server as the “oracle” user. Start up an Xterm session on the source database server as the “oracle” user.html.5 Execute 10.0 export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:. as the owner of the Oracle 10g file system. · The PERL5LIB environment variable points to the directories where the new Perl libraries are located (usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>)./runInstaller 1.2. export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5. change directory to the 10.2 Example CD staging area and run the Oracle Universal Installer.2.0 Oracle home.0 Example CD staging_directory> $ . as the owner of the Oracle RDBMS file system. Read the patch set notes in README.0.2. Set the following environment variables and run the install wizard to install the 10gR2 database software: $ $ $ $ export ORACLE_HOME=/oracle/<sid>db/10.2.

2.2.2. If any are found. Refer to the specific critical patch update documentation for installation information.pl $ export ORA_NLS10=$ORACLE_HOME/nls/data/9idata 1. resolve them first before continuing to the next step.2.8 Install the latest available critical patch update and any required patches Once you have installed the major Oracle Database 10g software.8.8. · The PERL5LIB environment variable points to the directories where the new Perl libraries are located (usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>). 6521934 Oracle 10.2.0 export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:. $ $ $ $ export ORACLE_HOME=<10gR2_ORACLE_HOME> export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:.4 (HP Tru64 UNIX) 6600051 Oracle 10. then set the ORA_NLS10 environment variable.0.Make sure that: · You DO NOT source the 9i database environment file. · The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.0.3 \ :$ORACLE_HOME/perl/lib/site_perl/5.7 Apply additional RDBMS One-off patches Shutdown the Applications server services.3 \ :$ORACLE_HOME/perl/lib/site_perl/5.3 $ cd <10./runInstaller 1.2.8.2. export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5. set the ORACLE_HOME variable and run the cr9idata.2.8.4 (HP Tru64 UNIX) 7497678 Oracle 10. The latest critical patch update for Oracle Database 10g Release 2 should be installed prior to upgrading your databases. 19 . export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5.3 $ cd $ORACLE_HOME/nls/data/old $ perl cr9idata.4 (HP Tru64 UNIX) Run opatch lsinventory before and after applying patches. Review all the readme files before applying any patch and review the logs for any discrepancy after applying each patch. Set the following environment variables and run the install wizard to install the 10gR2 database software: $ $ $ $ export ORACLE_HOME=/oracle/<sid>db/10.0. 1.0 Oracle home. · The ORACLE_HOME environment variable points to the new 10. database and listener before applying the following platform specific RDBMS One-off patches.6 Create nls/data/9idata directory As the owner of the 10gR2 RDBMS file system.2.2.4 patch set staging_directory> $ . check to see if there is a critical patch update that needs to be installed. Also apply Patch 6880880 OPatch 10.0 before applying these additional RDBMS patches.0.pl Perl script. · The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new Perl executable is located (usually $ORACLE_HOME/perl/bin).

6 to 10gR2.2) Part Number B14238-02.out SQL> @utlu102i.3 Upgrade Applications database to 10gR2 This section includes the tasks to upgrade the Oracle Applications Release 11i applications database from 9.3 Prepare for upgrading the database instance The following steps were derived from the Oracle Database Upgrade Guide 10g Release 2 (10.FND_STATTAB. to prepare for the upgrade.out.sql SQL> spool off 20 .sql by connecting to 9i Database using SQL*Plus with SYSDBA privileges.3.2. 1. $ cd <upg_1024_log_directory> $ sqlplus '/ as sysdba' SQL> spool utlu102i. # cat /etc/oratab <SID>:<9i_ORACLE_HOME>:N: Run the pre-upgrade information tool using the following steps: · Logon as the owner of the 9i_RDBMS file system and source the environment.2 Shut down the applications server processes and the database listener Shut down applications server services on the application node: # su – applmgr $ cd $COMMON_TOP/admin/scripts/<SID>_<HOSTNAME> $ . · Copy and run the utlu111i.1. · Oracle recommends that you use 500MB as the SYSAUX tablespace size and set autoextend on the SYSAUX tablespace. 1. # su – oracle $ lsnrctl stop <SID> 1. · Verify that the /etc/oratab file has correct entries for the 9i Database and 9i Oracle Home. Make sure that you unset the TNS_ADMIN environment variable and if event="38004 trace name context forever.2.0.ora server parameter file. disable the compilation of objects. · If you plan to change the PL/SQL compilation mode. level 1" is defined in either the init<SID>.2) Part Number B1423802 and Oracle Support Document: Oracle Applications Release 11i with Oracle 10g Release 2 (10. remove it.ora initialization parameter file or the spfile<SID>.sh apps/<apps_password> Shut down database listener on the database node. note that Oracle Applications has only one statistics table. that needs to be upgraded. Chapters 3 and 4.3. During this process.sql \ <upg_1024_log_directory> · Execute the utlu102i. the environment will be unavailable until the upgrade has completed.sql from <upg_10204_log_directory>. · When upgrading all statistics tables.3./adstpall.1 Preparation before Applications database upgrade Review Chapter 2 of Oracle Database Upgrade Guide 10g Release 2 (10. $ cp <10gR2_ORACLE_HOME>/rdbms/admin/utlu102i.1].0) [ID 362203. APPLSYS. Spool the output of this execution into utlu102i.

ora and backup the init<SID>. The upgrade log files are located in $<10gR2_ORACLE_HOME>/cfgtoollogs/dbua/<SID>/upgrade.3. After the 10gR2 upgrade. 1.5 Edit the initialization parameter file The newly installed Oracle 10gR2 will not be tuned for Oracle Applications 11i. Note: During the database startup.4 Upgrade the Applications 11i database Make sure that the Applications server processes and the 9i database listener are shut down. For further details.· Review the output for any errors or warnings and make any necessary changes before proceeding on to the next step. See Appendix B for the pre-upgrade information tool output file generated by this project and the steps performed to resolve the warnings identified by the tool. $ export ORACLE_HOME=<10gR2_ORACLE_HOME> $ cd $ORACLE_HOME/bin $ . Review the Oracle Support Portal document: 216205. Start an Xterm session on the source database server as the “oracle” user. see Oracle Support Document: How to Download and Run Oracle's Database Pre-Upgrade Utility [ID 884522. See Appendix C for the upgrade results of this project. 1. Set the environment variable ORACLE_HOME to point to the 10gR2_ORACLE_HOME directory created in the previous step and run the Oracle Database Upgrade Assistant (DBUA) against the Applications 11i database.1]. Make sure that you rename the spfile<SID>.3. both pfile and spfile have the same values. Monitor the progress of the DBUA. and run the DBUA from $ORACLE_HOME/bin. Take note of the section pertaining to the Database Upgrade Assistant (DBUA).ora) file.html” and make any necessary changes.ora before modifying.1 Database Initialization Parameters and Configuration for Oracle Applications Release 11i. Make the following modification and restart the database. DBUA will automatically start the instance. At the end of the upgrade process. Common EBS 11i modifications db_file_multiblock_read_count = 8 optimizer_max_permutations = 2000 query_rewrite_enabled = true _sort_elimination_cost_ratio = 5 _like_with_bind_as_equality = TRUE _fast_full_scan_enabled = FALSE _sqlexec_progression_cost = 2147483647 21 . Read Chapter 2 of Oracle Database Upgrade Guide 10g Release 2 (10. Oracle DB 10g first looks in $ORACLE_HOME/dbs for the spfile (spfile<SID>. export the new ORACLE_HOME.2) Part Number B14238-02.ora) and if not found the RDBMS will attempt to load the pfile (init<SID>. It will be easier to modify the pfile and then recreate the spfile after all the changes are made and the database started. Review “UpgradeResults./dbua Select the 9i database from the list of available databases.

Query returning the number of objects compiled so far. "Enabling Oracle Database Vault".2.3.0.x to Oracle Database 10g Release 10. 22 .0.4 patch set post-installation tasks Review the “Postinstallation Tasks” section of the 10. SQL> SELECT COUNT(*) FROM obj$ WHERE status IN (4.2. you must perform the post-installation tasks.1 Database Initialization Parameters and Configuration for Oracle Applications Release 11i and follow the instructions in these sections: · Release-specific database initialization parameters for 10gR2 · Enabling System Managed Undo (SMU) · Temporary Tablespace Setup 1.2.0.2.7 Perform 10.2.html).3. After you install the patch set.6 Additional database modification System Managed Undo (SMU) should be enabled in the database instance and define the temporary tablespace properly. Review My Oracle Support Portal document: 216205. 6).4" of the patch set notes.2.0 session_cached_cursors = 500 sga_target = 1G shared_pool_reservered_size=40M shared_pool_size=400M 10gR2 EBS 11i removed parameters _kks_use_mutex_pin=FALSE background_dump_dest core_dump_dest db_block_buffers db_file_multiblock_read_count db_cache_size java_pool_size large_pool_size query_rewrite_enabled undo_retention 1. and "Upgrading Oracle Database 10g Release 10.sql Use the following queries to track recompilation progress: Query returning the number of invalid objects remaining. SQL> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED. 5. Skip the sections "Upgrading Earlier Oracle Database to Oracle Database 10g Release 2 (10. This number should decrease with time. This number should increase with time. SQL> shutdown SQL> startup SQL> @?/rdbms/admin/utlrp.4 patch set notes (README.4)".0.10gR2 EBS 11i modifications _b_tree_bitmap_plans = FALSE optimizer_secure_view_merging = FALSE _optimizer_autostats_job=false compatible = 10.0. Bounce the database and run the SQL script to validate invalid objects within the database.

23 . connect to the database as SYSDBA and run the following command: SQL> connect / as sysdba. When modifying the initialization parameters pertaining to the PL/SQL native compilation.1. refer to Oracle Support Portal document: 216205.sql 1. Database Initialization Parameters and Configuration for Oracle Applications Release 11i as a guideline. then connect to the database as SYSDBA.3.1. refer to the Compiling PL/SQL Code for Native Execution section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference 10g Release 2 (10. Create the associated subdirectories for the given plsql_native_library_dir and plsql_native_library_subdir_count parameters.sql SYSAUX TEMP If the query does not return AMD.sql SYSAUX TEMP 1.3.3. 1.1.sql using the following command: $ sqlplus "/ as sysdba" @$ORACLE_HOME/ctx/sample/script/drkorean. To install Data Mining. Connect to the database as SYSDBA and run the following command: SQL> connect / as sysdba. and run drkorean.0 or previous releases.2). start the listener with the lsnrctl executable.10 Fix Korean lexers If you have upgraded from 10. Cross check that Oracle Data Mining and OLAP are installed in your database. then your database does not have Oracle Data Mining installed. connect to the database as SYSDBA and run the following command: SQL> connect / as sysdba. SQL> @$ORACLE_HOME/olap/admin/olap.2) for more information. If the query does not return ODM. 10g Release 2 (10. To install OLAP.3. then your database does not have OLAP installed. You can set the plsql_native_library_subdir_count parameter as described in the PL/SQL user's guide.11 Start the new database listener Since AutoConfig has not yet been implemented.8 Install Oracle Data Mining and OLAP Note: Restricted use licenses for Oracle Data Mining and OLAP are included with Oracle Database Enterprise Edition for the purposes of upgrading existing E-Business Suite databases. See the Oracle Database Net Services Administrator's Guide.9 Natively compile PL/SQL code (optional) You can choose to run Oracle Applications Release 11i PL/SQL database objects in natively compiled mode with Oracle Database 10g. SQL> @$ORACLE_HOME/rdbms/admin/dminst. SQL> select comp_id from dba_registry where comp_id='ODM' or comp_id='AMD'. For detailed steps.

3. then you must also run AutoConfig on each application tier server node to update the system with the new listener.13 Grant create procedure privilege on CTXSYS Copy $AD_TOP/patch/115/sql/adctxprv. If you have different configuration for the database listener in the new Oracle home. For more information review Oracle Support Portal document: 165195. Use SQL*Plus to connect to the database as APPS and run the script using the following command: $ cd $ORACLE_HOME/admin $ sqlplus apps/<apps_password> SQL> @adctxprv. $ vi $TNS_ADMIN/listener.0 to 10. you can also use the appsutil. $ lsnrctl start <SID> 1. then run the admkappsutil.Prior to starting the listener. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command: $ sqlplus "/ as sysdba" @adgrants. and restart them to load the new environment settings.2.ora $ vi $TNS_ADMIN/tnsnames.zip file located in the $APPL_TOP/admin/out directory.pl script. including the database and the listener. $ $ $ $ $ $ export ORACLE_HOME=<10g_ORACLE_HOME> export ORACLE_SID=<SID> export PATH=$ORACLE_HOME/bin:$PATH:. $ cp <9i_Oracle_Home>/network/admin/<SID>_<hostname>/* $TNS_ADMIN Modify the following .sql Copy $APPL_TOP/admin/adgrants. This task will migrate AutoConfig to the DB Tier.0.1. Logon to the Application node. $ perl $AD_TOP/bin/admkappsutil. Shut down all processes.pl 24 .3. perform these additional steps: Create the $TNS_ADMIN directory in the 10g_ORACLE_HOME.zip located in the 9i_ORACLE_HOME.12 Run adgrants. Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i. most commonly named APPLSYS.sql from the administration server node to the database server node.ora $ vi $TNS_ADMIN/sqlnet. This Perl script will create the appsutil. export ORA_NLS10=$ORACLE_HOME/nls/data/9idata mkdir –p $ORACLE_HOME/network/admin/<SID>_<hostname> export TNS_ADMIN=$ORACLE_HOME/network/admin/<SID>_<hostname> Copy the contents of 9i_TNS_ADMIN to $TNS_ADMIN.sql <APPLSYS schema name> where <APPLSYS schema name> is the Applications Object Library user.sql <SYSTEM password> CTXSYS 1.14 Implementing AutoConfig on upgraded database You need to configure and run AutoConfig in the new Oracle home on the database server node. 1.3. source the environment file.ora files changing all directory reference of 9.2. If current.sql from the administration server node to the database server node.ora Start the new Oracle Net Listener.

Copy and unzip the appsutil.zip file in the Database node <10gR2_ORACLE_HOME>.
$ cd <10gR2_ORACLE_HOME> $ unzip -o appsutil.zip

Set the following environment variables to be incorporated in the database context file.
# $ $ $ $ $ $ $ $ $ su - oracle export ORACLE_SID=<SID> export ORACLE_HOME=<10gR2_ORACLE_HOME> export PATH=$ORACLE_HOME/bin:$PATH:. export TNS_ADMIN=$ORACLE_HOME/network/admin/<SID>_<hostname> export ORA_NLS10=$ORACLE_HOME/nls/data/9idata export JRE_TOP=$ORACLE_HOME/jre/1.4.2 export LD_LIBRARY_PATH=$ORACLE_HOME/lib32 export SHLIB_PATH=$ORACLE_HOME/lib32 export LIBPATH=$ORACLE_HOME/lib32

Generate the database context file.
$ cd $ORACLE_HOME/appsutil/bin $ perl adbldxml.pl tier=db appsuser=apps appspasswd=<apps_password>

The newly-created context file and log file are located in following locations: Context File = <10gR2_ORACLE_HOME>/appsutil/<SID>_<hostname>.xml Log file = <10gR2_ORACLE_HOME>/appsutil/log/adbldxml_<date>.log Modify the context file, changing all reference of 9.2.0 to 10.2.0.
Note: An improper entry introduced into the context file can render the applications environment inoperable. Always make a backup prior to editing the context file.

Run AutoConfig to generate a new 10gR2 environment file located in the <10g_ORACLE_HOME> directory.
$ cd $ORACLE_HOME/appsutil/bin $ ./adconfig.sh \ contextfile=<10gR2_ORACLE_HOME>/appsutil/<SID>_<hostname>.xml \ appspass=<apps_password>

Review log file for any failures, errors, or warnings and resolve those issues before continuing. Shut down the 10g database and listener, source the new database environment file, and then start up the listener and the 10g database.
$ sqlplus / as sysdba SQL> shutdown normal SQL> exit $ lsnrctl stop <SID> # su – oracle $ . <10gR2_ORACLE_HOME>/<SID>_<hostname>.env $ lsnrctl start <SID> $ sqlplus / as sysdba SQL> startup

25

1.3.15 Gather statistics for SYS schema Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node. SQL script adstats.sql requires database running in restricted mode. Connect to the database as SYSDBA and use the following commands to restart the database in restricted mode, run adstats.sql, and restart the database in normal mode:
$ sqlplus / as sysdba SQL> shutdown normal SQL> startup restrict SQL> @?/admin/adstats.sql SQL> shutdown normal SQL> startup

There should be at least 1.5 GB of free default temporary tablespace. 1.3.16 Re-create custom database links (conditional) If you have different configuration for the database listener in the new Oracle home, then you must recreate any custom self-referential database links that exist in the Applications database instance. Verify the existing database links. Connect to the Applications database instance as APPS and run the following query:
$ sqlplus apps/<apps password> SQL> select db_link from dba_db_links;

If EDW_APPS_TO_WH and APPS_TO_APPS database links exist, then they should have been updated with the new port number by AutoConfig in the step „1.3.13 Implement and run AutoConfig‟. For custom self-referential database links (if any) in the database instance, use the following commands to drop and re-create them:
$ sqlplus apps/<apps password> SQL> drop database link <custom database link>; SQL> create database link <custom database link> connect to <user> identified by <password> using '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>) (PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';

where <custom database link>, <user>, <password>, <hostname>, <port number>, and <ORACLE_SID> reflect the new Oracle Net listener for the database instance. 1.3.17 Re-create grants and synonyms You must re-create the grants and synonyms in the APPS schema as Oracle database 10g Release 2 (10.2) contains new functionality for grants and synonyms compared to previous database releases. On the administration server node, as the owner of the Applications file system, run AD Administration and select the Recreate grants and synonyms for APPS schema task from the Maintain Applications Database Objects menu. If you are using MRC (Multiple Reporting Currencies) in your Applications system, then run the Maintain Multiple Reporting Currencies schema task to re-create MRC triggers in the APPS schema. Change directory to $ORACLE_HOME/rdbms/admin. Start SQL*Plus session with sysdba privilege and shutdown the database. Startup database using the upgrade option. SQL> startup upgrade

26

Run the utlirp.sql. SQL> @utlirp.sql Bounce the database and run the utlrp.sql. SQL> @utlrp.sql Check invalid objects SQL> select count(*) from dba_objects \ where status = ‘INVALID’; Use adadmin on the Administration server node to re-create grants and synonyms.
# su – applmgr $ . <APPL_TOP>/APPS<SID>_<hostname>.env $ adadmin Maintain Applications Database Entities Re-create grants and synonyms for APPS schema

1.3.18 Recreate spfile from pfile
$ cd $ORACLE_HOME/dbs $ sqlplus / as sysdba SQL> CREATE SPFILE FROM PFILE = '<ORACLE_HOME>/dbs/init<SID>.ora’;

1.3.19 Apply Oracle Receivables patch Apply Oracle Receivables patch 5753621. 1.3.20 Compile invalid objects Check for invalid database objects before and after this step (see Migration prerequisites section for details). Use adadmin on the Administration server node to compile invalid objects. $ adadmin Compile/Reload Applications Database Entities Compile APPS schema(s) You may want to also use the utlrp.sql script on the database node to decrease the number of invalid objects in the database. Connect to the 10gR2 Database using SQL*Plus with SYSDBA privileges and run the utlrp.sql script. $ sqlplus / as sysdba SQL> @?/rdbms/admin/utlrp.sql Check for invalid objects. SQL> Select count(*) from dba_objects where status = “INVALID”; 1.3.21 Restart Applications server processes (conditional) Start the database instance and Oracle Net listener for the database instance in the new 10.2.0 Oracle home. Start all the Application tier server processes. 1.3.22 Validate environment and perform a full backup After successfully validating the E-Business Suite environment as explained in Appendix F, perform a full backup to complete the upgrade to 10gR2 phase. The migration process can be paused at this stage and normal business operations can resume. If time permits, the next phase can be continued immediately or during the next planned downtime.

27

Phase 2: Migrating Oracle Applications 11i database to HP Integrity server
This phase includes the tasks to migrate the source 10gR2 database instance from HP AlphaServer systems running Tru64 UNIX to the target HP Integrity server. The Oracle Applications 11i environment will be offline during part of this phase. After the completion of this phase, the Oracle Applications 11i environment can resume normal operations as a fully supported split configuration where the application tier is running on HP AlphaServer systems running Tru64 UNIXs and the database tier is running on HP Integrity server. The instructions below are based partly on Oracle Support Portal document: Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 2 [ID 369693.1] and Oracle Support Portal document: Cross Platform Transportable Tablespaces (XTTS) on 11i with 10gR2 [ID 454574.1].

Constraints of using XTTS
1. The character set and national character set must be same at source and target databases. 2. XTTS is not supported for tables having columns encrypted using the Transparent Data Encryption (TDE) functionality of Oracle Database 10g (Review Oracle Support Portal document: Using TDE Column Encryption with Oracle E-Business Suite Release 11i [ID 403294.1]). You must de-crypt the encrypted columns prior to transportable tablespaces migration and then encrypt again in the target database after migration. Other detail limitations are documented in the Chapter 8 ('Managing Tablespace) of Oracle Database Administrator's Guide 10g Release 2 (10.2) Part# B14231-02.

Note: Since there is a potential for data corruption when using XTTS, suitable alternative migration options (such as export/import) may be needed due to unforeseen/non-reproducible errors.

During phase 2 of the migration, you will: · Section 1: Prepare the source database node · Section 2: Prepare the target database node · Section 3: Export the source Applications 11i database objects · Section 4: Import the Applications 11i database objects to the target database node · Section 5: Upgrade the target Applications 11i database instance

28

transport_set_violations table which will be used later while running automatic scripts.1] for any latest update.AD.6 Phase I Upgrade RDBMS 9. this requirement has already been satisfied during the previous step 'Migration prerequisites' in this white paper while applying dependent patches.4 Create a working directory Create a working directory named xttsexpimp in the source system that will contain all generated files and scripts required to complete this section. As this patch has been superseded by Oracle Applications 11i patch 7429271 Applications DBA Minipack Patch 11I.7. 2.0.Figure 4.1.4 Section 1: Prepare source DB Node · Full Backup · Apply export/ import utility patch Section 2: Prepare target DB Node · Prep Integrity server · Install 10gR2 Software only · Apply 10. This patch requires customers to file a Service Request (SR) with Oracle Support to receive the password to download.0. 2.1 Prepare the source database node 2.1 AutoConfig upgrade to the latest version This has already been executed during the previous step 'Migration prerequisites' in this white paper while applying dependent patch 8217898 TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH T.5 Create transport_set_violations table Use SQL*Plus to connect to the source database as sysdba and run the following command: SQL> exec dbms_tts. hence. You can ignore if any errors appear as this command will create the SYS.1.DRV to every application tier node.4 patchset Section 3: Export source DB objects · Prepare for export · Export DB objects · Convert endian format Section 4: Import DB objects to target Node · Copy export dump and data files · Import DB objects Section 5: Upgrade the target DB instance · Perform post import DB steps · Perform post import Apps 11i steps 2.1.1.10.1 on HP Integrity server Source Tru64 5.2.1. As an example.0. Review Oracle Support Portal document: AutoConfig to Manage System Configurations with Oracle Applications 11i [ID 165195.2 RDBMS 9. 2. $ mkdir /oratmp/xttsexpimp 2.2.1b EBS 11. „APPS_TS_SUMMARY‟. 29 . Phase 2 – Migrating Applications 11i database to the target HP Integrity server Phase II Migrating Applications 11i database to HP Integrity server Phase III Upgrade to Release 12.5.6 to 10.g.1.I.2.0. You can also use any existing tablespace name for [TABLESPACE] e.3 Apply latest Applications database preparation scripts patch Apply Oracle Applications 11i Patch 7225862 APPSST10204: RECREATE PATCH 6954610 TO INCLUDE FILE.2.transport_set_check('[TABLESPACE]').2 Apply the Applications consolidated export/import utility patch Download and apply the 'Controlled' export/import Oracle Applications 11i Patch 6158038 Export/import patch 9/09 including transportable tablespaces to the administration server node.

2.sql 2. SQL> @auque1. To remove the rebuild index parameter.sql in the current directory.sql The script will generate files listed and explained in Appendix D. You need to fix all the transport set violations listed in the log file. As the owner of the source database server file system. $ sqlplus /nolog SQL> connect / as sysdba. SQL> @auxttspre. 2. where [parameters] is the original parameter set without the rebuild_index parameter.1. Copy the auque1. These files will be used in the migration process using XTTS during Phase 2. As the owner of the source database server file system.sql script. connect to the source database as SYSDBA and run the auque1.sql script Copy the auxttspre. prior to the XTTS export. These indexes will need to be recreated in the target database (or dropped and recreated in the source database without the "rebuild index" qualifier). Make sure you review and understand the files description and usage explained in the Appendix D before proceeding with this phase. 30 .log for any transport set violations. Hence.1.1.1.sql script (installed as part of the export/import patch) from the application tier‟s $AU_TOP/patch/115/sql directory over to the database tier's working directory. It generates auque2. which generates a script called auque2. Patch 4872830 contains auque1. To see if you have any rebuild index parameters.4 Create a working directory‟. perform the PREPARE_FOR_TTS procedure for spatial indexes: SQL> EXECUTE SDO_UTIL.PREPARE_FOR_TTS('spatial_tbs'). connect to the source database as SYSDBA and run the auxttspre.sql to enable the settings in the target database instance.sql script. connect to the source database as sysdba and run the following command: SQL> select * from dba_indexes where index_type='DOMAIN' and upper(parameters) like '%REBUILD%'.6 Run the auxttspre.sql.7 Collect Advanced Queue settings Collect the Advanced Queue settings before migration as they will not be moved to the target database instance during the migration process.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the source database server node into the working directory created in „Step 2. $ sqlplus /nolog SQL> connect / as sysdba. as the owner of the source database server file system. Spatial indexes can have clause "rebuild index" that may cause error in export during XTTS migration. Make sure to review and analyze the resulting log file auxttspre.sql. connect to the source database as the owner of the index and run the following command: SQL> alter index [index name] rebuild parameters [parameters]. You can use auque2. and then re-do the instructions in this step before proceeding with the rest of this document.8 Removal of rebuild index parameter in spatial indexes Cross check the spatial indexes for the „rebuild index‟ parameter.

These are only suggested kernel settings and should be considered a starting point for additional operation system tuning.1].0_staging_directory> $ .sh End of Installation 31 .1) for HP-UX Itanium [ID 762891. refer to Oracle Support Portal document: Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12. apply the required operating system patches. Upgrade an Existing Database NO Select Configuration Option Install database software only Execute Configuration scripts Popup As root user run the following script: # <10gR2_ORACLE_HOME>/root.2.2 Modify operating system kernel parameters Refer to Appendix A for a list of kernel parameters for HP-UX 11i v3. as well as some kernel settings have been superseded or discontinued. and run the Oracle Universal Installer wizard using the “-ignoreSysPreReqs” option.2) Part Number B14238-02.2.2 Prepare the target database node This section will create an empty target database and populates it with all of the required system objects prior to running XTTS import.2. and incorporate the required kernel parameter settings.2.2.0 staging area. For more information.4 Install the base 10.3 Preparation to create the 10.1.2.0 software Start an Xterm session on the target database server as the “oracle” user.2. DO NOT source the 9i database environment. read Chapters 1 and 2 of the Oracle Database Installation Guide 10g Release 2 (10.2) for HP-UX Itanium Part Number B25293-01 and the System Considerations and Requirements section of Chapter 3 of the Oracle Database Upgrade Guide 10g Release 2 (10./runInstaller Select Installation Type Enterprise Edition Specify Home Details Name: OUIHome2 Path: <10g_ORACLE_HOME> Product-specific prerequisite checks The warning status for the OS and kernel patches can be ignored if running the prescribed software releases and kernel settings.2. Complete the preparation steps by staging the installation media and Operating System patches for 10gR2 database for HP-UX Itanium. 2. Execute any additional steps that are relevant for your environment.1 Configure the HP-UX 11i on target node Configure the HP Integrity server and install the HP-UX 11i v3 operating system according to HP product installation notes. Many of the required patches.2. 2. $ cd <10.0 Oracle home on Integrity server To understand the installation and upgrade processes. 2. change directory to the 10. 2.

· The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.2.4 patch set installation tasks Start up an Xterm session on the source database server as the “oracle” user. · The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.3 \ :$ORACLE_HOME/perl/lib/site_perl/5. · The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new Perl executable is located (usually $ORACLE_HOME/perl/bin). change directory to the 10. export LD_LIBRARY_PATH=$ORACLE_HOME/lib export SHLIB_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5.0.2. 2. Change directory to staging area for the 10.4 patch set file. · The PERL5LIB environment variable points to the directories where the new Perl libraries are located (usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>). Make sure that: · You DO NOT source the 9i database environment file.7 Execute 10.3 \ :$ORACLE_HOME/perl/lib/site_perl/5. · The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new Perl executable is located (usually $ORACLE_HOME/perl/bin).0.0 software Start up an Xterm session as the “oracle” user on the target database server.0 export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:.0 Oracle home.6 Execute 10.4 patch set staging_directory> $ .3 $ cd <10.0.html.5 Install the Companion CD for the base 10.2.3 $ cd <stage_directory>/Disk1 $ .2. Set the following environment variables and run the install wizard to install the 10gR2 database software: $ $ $ $ export ORACLE_HOME=/oracle/<sid>db/10.8. Understand the upgrade and patch set installation process before starting the patch set installation.0 Oracle home./runInstaller 2.4 patch set pre-installation tasks On the database server node.4 patch set staging area and run the Oracle Universal Installer.2. Read the patch set notes in README. Set the following environment variables and run the install wizard to install the 10gR2 database software: $ $ $ $ $ export ORACLE_HOME= <10gR2_ORACLE_HOME> export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:. DO NOT source the 9i database environment and make sure that: · The ORACLE_HOME environment variable points to the new 10.8.8.8.2. extract the 10. as the owner of the Oracle 10g file system./runInstaller 32 .2.2.2. · The ORACLE_HOME environment variable points to the 10.2.2.2. export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5. · The PERL5LIB environment variable points to the directories where the new Perl libraries are located (usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>).0.2.0 Companion CD and run the Oracle Universal Installer wizard.0.2.

0.ora) settings for Oracle Applications Release 11i and update both the init.2.3 $ cd $ORACLE_HOME/nls/data/old $ perl cr9idata. if necessary. 2. You may also need to update initialization parameters involving the db_name. and directory structures. set the ORACLE_HOME variable and run the cr9idata.0. then set the ORA_NLS10 environment variable.8. Refer to database initialization parameters (init. If any are found.11 Verify one-off patch equivalence with source RDBMS ORACLE_HOME The RDBMS software versions should be exactly equivalent on the AlphaServer systems and Integrity server in order to avoid any complications during migration of the database instance. export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5.4 HP-UX HP-UX HP-UX HP-UX Itanium Itanium Itanium Itanium Run opatch lsinventory before and after applying patches. 2.2.2.2. The OPatch utility should be used to list the installed patches and confirm that the two ORACLE_HOMEs are indeed equivalent.2.0. Refer to the specific critical patch update documentation for installation information. 6521934 6600051 7496636 7497678 10.3 \ :$ORACLE_HOME/perl/lib/site_perl/5.pl Perl script.0 RDBMS patches Shutdown the Applications server services. Ignore the initialization parameters that pertain to the native compilation of PL/SQL code. $ $ $ $ export ORACLE_HOME=<10gR2_ORACLE_HOME> export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:.2.13 Create a working directory Create a working directory named xttsexpimp in the target system which will contain all generated files and scripts required to complete this section. Review all the readme files before applying any patch and review the logs for any discrepancy after applying each patch.12 Create the target initialization parameter file and CBO parameter file From the source database server node.4 10.2. check to see if there is a critical patch update that needs to be installed. 2.4 10.2. copy initialization parameter files to the Oracle 10g $ORACLE_HOME/dbs directory on the target database server node. resolve them first before continuing to the next step. 2.2. Also apply OPatch 10.8 Create nls/data/9idata directory As the owner of the 10gR2 RDBMS file system. control_files.2. $ mkdir /oratmp/xttsexpimp 33 . The latest critical patch update for Oracle Database 10g Release 2 should be installed prior to upgrading your databases. database and listener before applying the following platform specific RDBMS One-off patches.2. You will be instructed to add them later.8. As an example.ora and ifilecbo.pl $ export ORA_NLS10=$ORACLE_HOME/nls/data/9idata 2.4 10.0.0 (Patch 6880880) for HP-UX Itanium (or the latest OPatch version for 10 gR2) before applying these additional RDBMS patches.9 Install the latest available patch set release and any required patches Once you have installed the major Oracle Database 10g software.0.0.ora files with any necessary changes.2.2.10 Apply additional 10.

Review the scripts using text editor before you run each of the next four steps and also note the following: · The remarks section at the beginning of each script contains additional information.sql.sql script.15 Copy database preparation scripts to target Oracle home The database preparation scripts patch that was applied to the source administration server node in Step „2. If PL/SQL of the source database was natively compiled.sql 34 . $ sqlplus "/ as sysdba" @addb1020. or tablespaces.sql. especially the ORACLE_HOME. data file(s).sql script‟ from the source database server node to the target database server node. reflecting the layout of the target database server node.sql script. Oracle does not support switching the PL/SQL compilation mode from interpreted to native (and vice-versa).1. and admsc1020. $ sqlplus system/[system password] @adsy1020. review the "Compiling PL/SQL Code for Native Execution" section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference 10g Release 2 (10. SQL> @aucrdb. connect to the target database instance as SYSDBA and run addb1020.sql.sql. When the target database instance has been created. · Each script creates a log file in the current directory. Update the script on the target database server node with any necessary changes to the directory structures for the log file(s). Add the parameters that pertain to the native compilation where specified.sql SQL> exit. Setup the environment variables appropriately on the target database server for the target database instance.14 Create the target database instance Copy the aucrdb.sql 2. Do not use the natively compiled code generated by the source database.2.2) Part Number B14261-01 for instructions on how to natively compile PL/SQL in the target database. 2.2.2.ora file.sql. adsy1020.log. On the target database server node. ORACLE_SID.3 Apply latest Applications database preparation scripts patch‟ contain four scripts that are needed on the target database server node. adjv1020. Copy the following files from the $APPL_TOP/admin directory of the source administration server node to the target database server node into the working directory created during „Step 2.17 Configure the SYSTEM schema Configure the SYSTEM schema for use with the Applications using the adsy1020. Confirm the default temporary and undo tablespaces are according to your requirement. use the following commands to run aucrdb.2.) Then.16 Configure the SYS schema Configure the SYS schema for use with the Applications using the addb1020.sql and create the target database instance: $ sqlplus /nolog SQL> connect / as sysdba. SQL> startup nomount.13 Create a working directory‟: addb1020. (ORACLE_SID must be set to the same value as the db_name parameter in the init[SID]. Review the example file in Appendix D. SQL> spool aucrdb.2.6 Run the auxttspre.sql script generated in Step „2. and ORA_NLS10 environment settings. 2. On the target database server node.sql. Using native mode takes significantly more time than interpreted mode. restart the database instance.2.1. connect to the target database instance as SYSTEM and run adsy1020.

21 Backup the target database instance The target database instance is now prepared for an import of the Applications data.sql SQL> exit.18 Java Virtual Machine installation Use adjv1020. interMedia.2.sql.19 Other required components installation Use admsc1020. in the order specified: Table 5. and ConText. Arguments for admsc1020.sql: $ sqlplus "/ as sysdba" SQL> shutdown normal.sql Argument remove context? SYSAUX tablespace temporary tablespace Value FALSE SYSAUX TEMP $ sqlplus system/[system password] @admsc1020.2.2. Data Mining. 2.20 Disable automatic gathering of statistics Copy $APPL_TOP/admin/adstats.2. Spatial. 2.sql.2. OLAP.sql from the administration server node to the target database server node. You should perform a backup before starting the import.sql Note: This script can be run only once in a given database instance. On the target database server node. connect to the target database instance as SYSTEM and run admsc1020.sql script to install the following required components in the database: ORD. On the target database server node. You must pass the following arguments to the script. SQL> @adstats.sql to install the Java Virtual Machine (JVM) in the database. Here is an example: $ sqlplus system/[system password] @adjv1020.sql FALSE SYSAUX TEMP Note: All of the components are created in the SYSAUX tablespace regardless of where it was installed in the source database. 35 . Connect to the database as SYSDBA and use the following commands to restart the database in restricted mode and run adstats. connect to the target database instance as SYSTEM and run adjv1020. 2. because the scripts that it calls are not rerun able. SQL> startup restrict. XDB.

auexpmsc.1. you must also reconfigure AutoConfig on the database tier and deregister the current database server node.2 Modify the export parameter files Modify the auexpxtts.1.2.dat export parameter file created in Step „2.log dumpfile Filesize Logfile Create a directory in the system schema that corresponds to the directory specified in the template. or xttssys%U.dat.3 Export the source Applications 11i database objects After a successful installation of RDBMS 10gR2 on the target database node. For example: $ sqlplus system/[system password] SQL> create directory xttsdmpdir as '/oratmp/xttsexpimp'.dmp. expmsc.1 Deregister the source database server machine If you are planning to use a different database port.6 Run the auxttspre. Make a backup on any parameter file before modifying. export the source Applications 11i database and import into the target database node. or database name parameter on the database server. Table 6. This section describes the detail steps of exporting data from the source Oracle Applications database.sql script” according the source environment and other customized parameters using a text editor.log.dat data pump parameter files created in Step „2. Review the example file in Appendix D. SID.sql script‟ according the source environment and other customized parameters using a text editor. xttsmsc%U. host.pl appspass=apps / contextfile=$CONTEXT_FILE -removeserver 2. Customizable parameters in export parameter files Parameter directory Description directory where export dump files will be created export dump file name(s) export dump file size Log file name Template value dmpdir xttsmeta%U. or expsys.6 Run the auxttspre.log.3. Review the example file in Appendix D. 2.dmp. 36 . $ perl $ORACLE_HOME/appsutil/bin/adgentns.dat. Modify the auexpglb.dmp 1 GB Expmeta. and auexpsys.3.

Delta. Oracle Data Pump version 10. 2. SQL> purge recyclebin.AZ.dat 37 .5 Back up AZ table data (conditional) If you are using AZ. 2. upgrade to AZ.dat Parameter file Description export dump file name export dump file size log file name Template value gtab.3. Execute step 2 of Oracle Support Portal document: iSetup dependency with Deinstall and Reinstall of XMLDB [ID 402785.3 Shut down Applications server processes Shut down all Applications server processes except the database and the Net Services listener for the database.3.H.sql Review the example file in Appendix D 2.1] for instructions.3. Customizable parameters in auexpglb.7 Change the tablespaces within the transportable set to read only Connect to the database as SYSDBA and run auxttsread. Run the following commands to find and purge the recycle bin: SQL> select owner.H.sql to change the tablespaces within the transportable set as read only: $ sqlplus "/ as sysdba" @auxttsread.1] to back up the data within XML type columns. SQL> connect [user]/[password].dba_unused_col_tabs.log 2. SQL> alter table [table name] drop unused columns.3.DELTA. count(*) from dba_recyclebin group by owner.1 [ID 403092.8 Export the transportable tablespace set Use the following command to start an export session on the source database server node using the auexpxtts.4 Purge unused columns and recycle bin Connect to the source database as sysdba and run the following commands to find and purge any unused columns: SQL> select * from sys.H.6 Grant privilege to source system schema Connect to the database as SYSDBA and use the following command to grant the exempt access policy privilege to system: SQL> grant EXEMPT ACCESS POLICY to system.3. 2.dmp filesize log 1 GB expgtab.3. Users cannot use the Applications until the import is completed.1.2 does not allow tables with XML type columns to be migrated. Review Oracle Support Portal document: About Oracle iSetup Minipack 11i. 2.dat parameter file: $ expdp system/[system password] parfile=auexpxtts.Table 7.

Please see Oracle Support Portal document: 10g Transportable Tablespaces Across Different Platforms [ID 243304.dat 2. and directory location (where the data files with converted endian format will be generated). directory format.9 Export SYSTEM tablespace schemas Use the following command to export the SYSTEM tablespace schemas by starting an export session on the source database server node using the auexpsys. with the target platform name.3.dat‟. 38 . PLATFORM_NAME from v$database.sql script‟.dat parameter file to export the global temporary tables: $ exp system/[system password] parfile=auexpglb.10 Export global temporary tables Global temporary tables are not exported as they do not reside in any tablespace.3. Modify the aurman.dat 2.dat script.dat parameter file: $ expdp system/[system password] parfile=auexpsys. Review the example file in Appendix D Then.dat 2. use the following command to create the new data files: $ rman target / @aurman.1.3.11 Export miscellaneous data Start an export session on the source database server node using the auexpmsc.6 Run the auxttspre. Use the following command: $ expdp system/[system password] parfile=auexpmsc. which was generated in Step „2.dat To avoid space constraint at source DB node. Use the following command to start an export session on the source database server node using the auexpglb. PLATFORM_ID PLATFORM_NAME ----------.1] for information on the endian-ness of various platforms.2. a conversion is necessary.12 Convert endian format of the data files Connect to the database as SYSDBA and use the following command to check the endian formats of the source and target platforms: Source: SQL> select PLATFORM_ID. you can mount the target DB node directory at Source DB node and specify the mount point in „aurman.--------------------------------------------------------------------4 HP-UX IA (64-bit) As the source and target platforms have different endian formats. PLATFORM_ID PLATFORM_NAME ----------.--------------------------------------------------------------------- 5 HP Tru64 UNIX Target: SQL> select PLATFORM_ID. PLATFORM_NAME from v$database.3.dat parameter file to export other objects.

then copy all the data files and export dump files generated in Step „2. Review the example file in Appendix D.dmp. Modify the auimpxtts.sql script‟ from the source database server node to the target database server node.dat.4. Table 8.log. 2. auimpmsc.1 Copy the export dump and data files If you have not already moved or copied the database files with converted endian format from source DB node to target DB node in previous steps. xttsmsc%U.14 Shutdown the database Use SQL*Plus to connect to the database as SYSDBA and use the following command to shut down the database: $ sqlplus "/ as sysdba" SQL> shutdown normal.4 Import the Applications 11i database objects to the target database node This section describes the detail steps of data import into the target database. 2.6 Run the auxttspre. Customizable parameter in import parameter files Parameter directory Description Directory where the export dump files are located export dump file name(s) Template value dmpdir xttsmeta%U. or impsys.dat. For example: $ sqlplus system/[system password] SQL> create directory xttsdmpdir as '/oratmp/xttsexpimp'. 2. or xttssys%U.3.2 Edit the import parameter files Copy all the import parameter files generated in Step „2.logg ?/dbf/[file name] dumpfile logfile Log file name Location of every data file in the transportable tablespace set transport_datafiles Change the directory structures for transport_datafiles to reflect the location of the data files on the target database server node. 39 .1. Create a directory in the system schema that corresponds to the directory specified in the template. 2.4.2.log.13 Revoke privilege from source system schema Connect to the database as SYSDBA and revoke the exempt access policy privilege from system using the following command: SQL> revoke EXEMPT ACCESS POLICY from system. impmsc.dmp.log impmeta.3.3 Export the source Applications 11i database objects‟ from the source database server node to the target database server node.dat data pump parameter files according the target environment and other customized parameters using a text editor. and auimpsys.

sql script‟ to reflect the target environment and other customized parameters using a text editor.dat 2. Compare this result with that on the source machine and if there are any discrepancies.sql script.4 Import the transportable tablespace set Use the following command to start the import on the target database server node using the auimpxtts.3 Export the source Applications 11i database objects‟ to the target database server node.log 2.sql.6 Change the default tablespaces of users Copy audeftbsp. $ sqlplus "/ as sysdba" @auxttswrite.4.dat import parameter file created in Step „2.sql script. $ sqlplus "/ as sysdba" @audeftbsp. Table 9. count(*) from dba_ts_quotas group by username order by username. connect to the source database as sysdba and run the audeftbsp. Review the example file in Appendix D. as the owner of the source database server file system.6 Run the auxttspre.1.4.5 Revert the tablespaces to read/write mode Copy auxttswrite. Then.3 Import miscellaneous data Use the following command to start the import session on the target database server node using the auimpmsc. as the owner of the target database server file system.dat 2.3 Export the source Applications 11i database objects‟ to the target database server node.dmp log impgtab. Review the example file in Appendix D.sql Note: Cross check the tablespace quota on the target system by issuing the sqlplus command: sqlplus> select username.Edit the auimpglb. Customizable parameter in auimpglb. connect to the source database as sysdba and run the auxttswrite.dat parameter file: $ impdp system/[system password] parfile=auimpxtts.dat file Parameter file Description import file name import log file name Template value gtab.sql generated in Step „2.dat parameter file: $ impdp system/[system password] parfile=auimpmsc.4. Then.4. issue the sqlplus command: sqlplus> grant quota on [tablespace] to [user] 40 . generated in Step „2. Review the example file in Appendix D.sql 2.

1. Start the listener with the lsnrctl executable since AutoConfig has not yet been implemented.sql 2. Use the following command: $ impdp system/[system password] parfile=auimpmsc.dat parameter file: $ impdp system/[system password] parfile=auimpsys.5. as the owner of the Oracle 10g file system.2.4.dat parameter file: $ imp system/[system password] parfile=auimpglb. on the target database server node.1 Reset Advanced Queues Copy the auque2.dat to “INCLUDE=PROCOBJ".sql script‟ to the target database server node.dat 2. Then. connect to the target database as SYSDBA and run the auque2.4.5 Upgrade the target Applications 11i database instance This step explains the post-import steps required to restore the target database to a fully functional state. change the log file name. The script creates a log file in the current directory.7 Import global temporary tables Use the following command to start the import on the target database server node using the auimpglb.1) for more information. See the Oracle Database Net Services Administrator's Guide 10g Release 2 (11. 2.sql script that was generated in Step „2.dat parameter file.sql script to enable the Advanced Queue settings that were lost during the process.6 Run the auxttspre. $ sqlplus "/ as sysdba" @auque2.4. $ lsnrctl start <SID> Note: Set the TNS_ADMIN environment variable to the directory where you created your listener.dat 2. and remove the remap_tablespace setting using a text editor. 41 .2 Start the new database listener Start the Oracle Net listener for the database instance in the new Oracle home if it has not been started.dat 2.510 Revoke privilege from target system schema Connect to the database as SYSDBA and revoke the exempt access policy privilege from system using the following command: SQL> revoke EXEMPT ACCESS POLICY from system. Start the import session on the target database server node using the auimpmsc.9 Import SYSTEM tablespace schemas Use the following command to start the import on the target database server node using the auimpsys.5.8 Import procedural objects Change the "EXCLUDE=PROCOBJ" line in auimpmsc. Review the example file in Appendix D.ora and tnsnames. 2.ora files.

5.pl · This action will create appsutil.2.sql from the administration server node to the database server node.4 Grant create procedure privilege on CTXSYS Copy $AD_TOP/patch/115/sql/adctxprv.5 Migrate the AD Utilities to the target database server node This task will enable migration of the AD Utilities from the source administration server node to the target database server node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command: $ sqlplus "/ as sysdba" @adgrants.sql from the administration server node to the database server node. 2.3 Run adgrants.5.sql in the adgrants. Use SQL*Plus to connect to the database as APPS and run the script using the following command: $ sqlplus apps/[APPS password] @adctxprv.sql require the APPLSYS schema name parameter to be passed instead of APPS. Older versions of adgrants.zip file to the <RDBMS ORACLE_HOME> $ cd <RDBMS ORACLE_HOME> $ unzip -o appsutil. 2. refer to Section 5 of Oracle Support Portal document: 165195.zip 42 .sql [SYSTEM password] CTXSYS 2.zip in $APPL_TOP/admin/out directory.sql Copy $APPL_TOP/admin/adgrants.1 Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i. On the Application Tier (as the Applications File system user): · · Log in to the APPL_TOP environment (source the environment file) Create appsutil.sql script. On the Database Tier (as the Oracle user): Copy and unzip the appsutil. In summary: Update the ORACLE_HOME with the AutoConfig files by performing the following steps: 1. For more information.sql [APPS schema name] Note: Verify the usage of adgrants.5.zip file $ perl <AD_TOP>/bin/admkappsutil.

If they exist. SQL> @adstats.sql SQL> alter system disable restricted session. they should have been updated with the new port number by AutoConfig in Step „2. 2. Cross check the existence of database links. and startup the listener and database./adconfig.3.5. 2. Generate your database context file.xml \ appspass=<apps_password> To complete this task shutdown all database processes including the listener. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to enable restricted mode.7 Re-create custom database links (conditional) If you have created a new or different the Oracle Net listener in the 10. · Verify that the following environment settings are set properly: $ $ $ $ $ $ $ export export export export export export export ORACLE_SID=<SID> ORACLE_HOME=<10gR2_ORACLE_HOME> PATH=$ORACLE_HOME/bin:$PATH:. and disable restricted mode: $ sqlplus "/ as sysdba" SQL> alter system enable restricted session. then you must re-create any custom self-referential database links that exist in the Applications database instance.sql from the administration server node to the database server node.log 4.0 Oracle home.5 GB of free default temporary tablespace. Connect to the Applications database instance as APPS and run the following query: $ sqlplus apps/<apps password> SQL> select db_link from dba_db_links.5. Run AutoConfig on the target database node: $ cd $ORACLE_HOME/appsutil/bin $ .2.pl tier=db appsuser=apps \ appspasswd=<apps_password> · The context file and its creation log were generated in the following locations: Context File = $ORACLE_HOME/appsutil/<SID>_<hostname>. Note: Make sure that you have at least 1. 43 . The EDW_APPS_TO_WH and APPS_TO_APPS database links. SQL> exit. TNS_ADMIN=$ORACLE_HOME/network/admin/<SID>_<hostname> ORA_NLS10=$ORACLE_HOME /nls/data/9idata LD_LIBRARY_PATH=$ORACLE_HOME/lib SHLIB_PATH=$ORACLE_HOME/lib · Run the AD build XML Perl script: $ cd $ORACLE_HOME/appsutil/bin $ perl adbldxml. run adstats.5.sql. source the newly create environment file.sh \ contextfile=<10gR2_ORACLE_HOME>/appsutil/<SID>_<hostname>.xml Log = $ORACLE_HOME/appsutil/log/adbldxml_*.6 Gather statistics for SYS schema Copy $APPL_TOP/admin/adstats.5 Migrate the AD Utilities to the target database server node‟.

You can use the following commands to drop and re-create them: $ sqlplus apps/<apps password> SQL> drop database link <custom database link>. as the owner of the Oracle 10g file system and database instance.OWA_MATCH on the target database.Cross check custom self-referential database links (if any) in the database instance. The export/import utility patch 4872830 that you applied to the source administration server node in Step „2. Run the following command as the owner of the Applications file system: $ perl $AU_TOP/patch/115/driver/dpost_imp.sql script to compile invalid objects. and <port number> is the port number of the new Oracle Net listener for the database instance. $ sqlplus "/ as sysdba" @$ORACLE_HOME/rdbms/admin/utlrp.0. 2. SQL> create database link <custom database link> connect to <user> identified by <password> using '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>) (PORT=<portnumber>))(CONNECT_DATA=(SID=<ORACLE_SID)))'.9 Restore AZ table data (conditional) If you previously performed the step to back up the AZ table data.sql script‟ contains a Perl script. 2.9 CU2 FOR BUG 5525015.12 Compile invalid objects On the target database server node. 2.<hostname> . perform steps 4 and 5 of document 402785. where <custom database link>.5. 2.6 Run the auxttspre. use AutoPatch to apply it on the target administration server node. <password>.5.8 Apply Oracle Receivables patch Apply Oracle Receivables Patch 5753621 ONE-OFF REQUEST ON TOP OF 11. and <ORACLE_SID> are all as they were in the source database link definition.5.sql 44 .pl that you can run to generate an AutoPatch driver file.1 to create SYS.2.1 on My Oracle Support to restore the AZ table data.pl [driver file] Once the driver file has been generated. 2.10 Create OWA_MATCH package (conditional) If you are using iAS 1.11 Create ConText and Spatial objects Certain ConText and Spatial objects are not preserved by the import process. <user>. perform the steps in Note: 312165.5.5. dpost_imp.5. You use this driver file to call the scripts that create these objects.1. use SQL*Plus to connect to the target database as SYS and run the $ORACLE_HOME/rdbms/admin/utlrp.

5. perform the following tasks: · · Compile flexfield data in AOL tables Recreate grants and synonyms for APPS schema If you use Multiple Reporting Currencies: · Maintain Multiple Reporting Currencies schema Enter Yes for the following options: · · · Update MRC schema itself Compile invalid objects after updating MRC schema objects Recreate MRC triggers in the APPS schema 2. You can allow users to access the system at this time. Specify "ALL" in the schema name to gather statistics for all database objects.5. Log on to Oracle Applications with the "System Administrator" responsibility. Click "Submit". Enter appropriate parameters. 45 . You may choose individual schemas to make the process run faster.5.13 Maintain Applications database objects Run AD Administration on the target administration server node.5. gather the statistics by following these steps: · · · · · Ensure that there are no concurrent programs running.14 Start Applications server processes Start all the server processes on the target Applications system. From the Maintain Applications Database Objects menu. 2.16 Gather Applications statistics (conditional) If you encountered failures importing statistics.2.15 Create DQM indexes Create DQM indexes by following these steps · · · · · Log on to Oracle Applications with the "Trading Community Manager" responsibility Click Control > Request > Run Select "Single Request" option Enter "DQM Staging Program" name Enter the following parameters: o o o o Number of Parallel Staging Workers: 4 Staging Command: CREATE_INDEXES Continue Previous Execution: NO Index Creation: SERIAL: 2. Click Navigation List > Request > Run.

17 Validation tasks Verify that the migrated database functions properly with the source Application Tier environment. · Select a responsibility (such as the System Administrator responsibility). Verify the database server hostname and database release version: · Go to the Oracle E-Business Suite Rapid Install Portal. such as the Concurrent->Requests form. 46 . If time permits. and verify that the server hostname and release version correspond to those of the new HP Integrity database server. and log on to the E-Business Suite home page as the sysadmin user.5. perform a full backup to complete the upgrade to 10gR2 phase. The Oracle Applications 11i environment is now in a fully supported split configuration with the Applications 11i server application tier services running on HP AlphaServer systems and the database instance 10gR2 is running on HP Integrity sever. · From the Help menu click "About Oracle E-Business Suite". the next phase can be continued immediately or during the next planned downtime. After successfully validating the E-Business Suite environment as per Appendix F. · Click on any form.2. The migration process can be paused at this stage and normal business operations can resume.

1.6 Phase I Upgrade RDBMS 9. Oracle Database Preparation Guidelines for E-Business Suite Release 12. Phase 3 .1b EBS 11.0. Part Number E14010-01.1.9 CU2 or 11. This phase could have significant downtime and product specialists and application DBAs should work closely during this phase of the migration.1 on HP Integrity server · Apply R12 Mega Patch · Section 3: Perform Post -Upgrade Product specific tasks · Use TUMS report · Perform final validation tests · Release to production 3.10.5.2.0. For more information.1 applications home on the target HP Integrity server.1 Apply 11i.1. review the steps in the Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.6 to 10.Phase 3: Migrating to E-Business Suite Release 12.AD. This note should be used to determine the specific upgrade path and the required database patches to be applied to prepare for the upgrade.4 Database ". About Oracle E-Business Suite DBA Minipack 11i.10.2 with 10gR2 database.5.2.2 RDBMS 9. 3. The Oracle E-Business Suite Upgrade Guide: Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12. Make sure that the AutoConfig is migrated over to the database node before continuing. which is applicable for Applications Release 11.0.1 upgrade The detailed planning process begins with reviewing the Oracle Support Portal document: 761570.AD.0. Thoroughly read and understand the procedures in this guide before continuing. This section includes the following tasks: · Section 1: Prepare source for E-Business Suite Release 12.1 Phase 3 will prepare the 10gR2 database instance to be E-Business Suite Release 12. refer to Oracle Support Portal document: 233044.1 · Install R12.5.I minipack on all application tier nodes. will be used extensively to complete the final phase of this migration.1. Chapter 2.AD.1.I. Part Number E14010-01.I Minipack If you have not previously done so.2.1.0.2.2.1 Upgrade · Section 2: Upgrade to E-Business Suite Release 12.1.1 · Section 3: Perform post upgrade product specific tasks Figure 5.1. This project will use "Path D: Upgrade Path for Systems with 11.1.4 Phase II Migrating Applications 11i database to HP Integrity server Section 1: Prepare source for EBS R12.1.1.1. apply the latest 11i.1.1 Prepare source for E-Business Suite Release 12. After determining the details of the upgrade plan.1.3 or 10. Closely review Chapter 1.1.1.1 upgrade · Run the TUMS script · Performa preupgrade product specific Tasks per TUMS report Section 2: Upgrade to Release 12. 47 .1 on HP Integrity server Source Tru64 5.1.Upgrade to Release 12.1.5.1.1 upgrade.1 aware and then install the new E-Business Suite Release 12.2 with a 10.10.1 on HP Integrity server Phase III Upgrade to Release 12. “Planning for an Upgrade” of the Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.

From your Release 11i APPL_TOP. “Preparing for the Upgrade”. To generate the TUMS report. These tasks are derived from the “Prepare for the Upgrade” sections of Chapter 2.4 Product-specific tasks These tasks are executed on the Release 11i APPL_TOP. excluding the ones listed in the TUMS report.html).1. before continuing with the final preparations for upgrade task.1. Navigate to the Submit Request window (Request > Run). Log in to Oracle E-Business Suite 11i instance with the System Administrator responsibility. Then change to the “$AD_TOP/patch/115/sql” directory and run the adtums.1. 48 .sql script.1. Download and apply Oracle Applications patch 7705743: TUMS for R12: To Deliver TUMS Utility For Upgrades From 11i TO R12 to the administration server node on your Release 11i APPL_TOP. See Appendix E to view the TUMS report for this project.1. 2.1.1.1 environment. The patch supplies the script (adtums.sql) to generate the TUMS report (tumsr12. Set the schema name to ALL to gather statistics for all Oracle E-Business Suite schemas (having an entry in the FND_PRODUCT_INSTALLATIONS table). Part Number E14010-01.1. Part Number E1401001.2 Run the Upgrade Manual Scripts (TUMS) utility The TUMS utility reviews the current Oracle Applications Release 11i environment and creates a report that lists all the tasks that can be omitted during the upgrade process.5 Gather schema statistics for CBO (required) Release 12. in the Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12. before continuing with the product-specific tasks.html. This section completes the final preparation tasks for your existing Release 11i system and installs the new Oracle E-Business Suite Release 12.1. Complete all tasks in the “Applications Technology Tasks” and “Product Specific Tasks” sections of Chapter 2. Complete all tasks in the “Database and System Administration Tasks” section of Chapter 2. the program gathers column-level histogram statistics for all columns listed in the FND_HISTOGRAM_COLS table.3 Database and system administration tasks These tasks are executed on the Release 11i APPL_TOP. login as the applications administrator and source the environment. $ cd $AD_TOP/patch/115/sql $ sqlplus apps/<apps_password> @adtums.ora file before TUMS can write the report. which you initiate by running the Gather Schema Statistics concurrent program. TUMS is delivered in a patch. This directory must be listed in the UTL_FILE_DIR parameter of the init. 3. complete the following steps: 1. 3.1. excluding the ones listed in the TUMS report. in the Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12. These statistics are gathered by the FND_STATS process. enter the full path of the directory to which you want the report to be written. which supplies the scripts you need to examine your system and create the report. Part Number E14010-01. 3. “Preparing for the Upgrade”.1 employs cost-based optimization.1. The report will be generated on the database node: <DIRECTORY>/tumsr12.sql <DIRECTORY> For the <DIRECTORY> value. 3. in the Oracle EBusiness Suite Upgrade Guide: Release 11i to Release 12. Submit the Gather Statistics program (Schema). which examines FND table statistics to determine the most efficient access paths and join methods for executing SQL statements.3. “Preparing for the Upgrade”. In addition to gathering index and table-level statistics.

1.1 staging area>startCD/Disk1/rapidwiz. 3.1. Stage the Oracle E-Business Suite Release 12.1.1. Start Rapid Install by typing rapidwiz on the command line. or supported by.1.2 Prepare the target database node. Click Next. 5.1. modify the database node sqlnet.ora to include the <new_host_name> in the “tcp. user names and passwords.1 Applications node and run Rapid Install (required) Prepare the HP Integrity server for E-Business Suite Release 12.1 system.invited_nodes” section. product license types.1. existing and new database node descriptions (including mount points). and mount points for other nodes in your system.6 Backup the database (recommended) Make a cold backup of the Oracle E-Business Suite database. Shut down the entire Release 11i environment and make sure that the database is shut down with the NORMAL option. 2. enter the parameters required to set up your new environment and run Rapid Install. On the Wizard Operation screen. Click Next. On the Select Upgrade Action screen. Logon to the HP Integrity server designated as the new applications R12.1 installation media. 1.1. select Upgrade to Oracle E-Business Suite Release 12. If any problems occur during the upgrade process the only method to rollback is to restore your system from a recent backup. In the associated screen flow.ora file to recognize the new HP Integrity server Release 12. 49 .Note Gather schema statistics on a regular basis to fully utilize the cost-based optimization feature. internationalization and language settings. 4. Before running Rapid Install.1 node as the owner of the applications file system and change to: <R12. Edit the sqlnet.7 Prepare the R12. select Create Upgrade File system.1.ora file has been updated.1. for preparing the target server and then use the Rapid Install wizard to lay down the file system and install the new technology stack for your Oracle E-Business Suite Release 12. this needs to be one of the last tasks you perform before initiating the upgrade so that the statistics are current. this release of Oracle E-Business Suite. In preparation for an upgrade. 6. Using the IMMEDIATE or ABORT option may result in an unusable database backup.1 target application node. The Welcome screen lists the components that are included in. 3. See section 2. Run Rapid Install and supply basic information about your system such as port specifications. within this document. restart the listener process on the database server so that the target applications server can properly connect to the remote database.1.1 application node. 3. Once the sqlnet.

4 Database".2.1.3. 3.1 in the Upgrade Guide: Release 11i to Release 12.1.1” of Upgrading to Release 12.1. query the Inventory: >opatch lsinventory |grep <OneOff patch number> 3. “Upgrading to Release 12.1 Rapid Install.1 APPL_TOP and should be completed during system downtime.1 Upgrade.1.8 Migrate or upgrade your database Oracle 10gR2 Review Oracle Support Portal document: 761570.1” There are two options in Step 3 of the above guide: Migrate database to Oracle 11g Release 2.1. Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Perform all the necessary steps in Chapter 3: “Upgrading to Release 12. Apply listed interim patches for Path D.1.2 Upgrade to E-Business Suite Release 12. Patch the existing 10gR2 home or install a new 10gR2 home using Release 12.5.1. It may possible that some of the OneOff patches have already been applied. 3. Notes: Refer Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.9 CU2 or 11.1” in the Upgrade Guide: Release 11i to Release 12. All the tasks must be performed during the upgrade downtime. Hence.1. All the tasks are performed on the Release 12.3 or 10. Chapter 3: “Upgrading to Release 12.0.0.1. This project used the former option.1.1 Upgrading to E-Business Suite Release 12.1 This section describes the tasks required to initiate the upgrade process. 50 .1.5.2 Finish the upgrade Complete all tasks in the “Finish the Upgrade” and “Finish System Administration Tasks” sections of Chapter 3.2. "Path D: Upgrade Path for Systems with 11.1.1.2 with a 10.1.1.2.2.10.1.

1.1. 51 .1. Complete all tasks in Chapter 4. Hence.1.2 and RDBMS 11gR2.1. E-business Suite Release R12. and then clone the environment for use with production support environment. Oracle E-Business Suite Release 12. excluding the tasks listed in the TUMS report.1.3 Perform post upgrade product specific tasks This section describes tasks that complete the upgrade for specific products. Perform validation testing as listed in Appendix F.e.2 is now available. you can also perform following two optional phases to upgrade to latest Oracle E-Business Suite and RDBMS versions i. Shut down the environment and perform a full backup of the environment.3. This section includes the following tasks: · Applications technology tasks · Customer relationship management tasks · Financials and procurement tasks · Human resources tasks · Intelligence tasks · Projects tasks · Supply chain management tasks · System maintenance tasks · Additional tasks This completes the Oracle E-Business Suite upgrade to Release 12. Post-upgrade Tasks in the Upgrade Guide: Release 11i to Release 12.

1. For any latest patches and changes. complete the upgrade to R12.1.2 During this patching phase of the migration. including the postupgrade steps.1. statutory/regulatory updates.1.1. 4. you will execute: · Section 1: Pre-requisite checks · Section 2: Applying the Release Update Pack · Section 3: Apply Post-Release Update Patch · Section 4: Post-update steps Note Apply Oracle E-Business Suite 12.1.1.Phase 4: Upgrade E-Business Suite R12.5 ) or Oracle Support Portal document 728531.1 Oracle E-Business Suite Readme.1. review Oracle Support Note 949406.1 RUP2) (Patch 7303033) This release update pack (RUP) combines error corrections.2 patch.1. such as disabling fast validation for PL/SQL recompilations. · Review the latest copy of Oracle Support Portal document 437878. 4. 4.1 (for 10. While upgrading from Release 11i to Release 12.1 and perform additional changes to database initialization file for 10gR2.1 and apply all required patches that are mentioned in this document before upgrading to Release 12.1.3.1.1 environment.1.2 Cross check the OracleAS patches for EBS R12 · Review the latest copy of Oracle Support Portal document 454811.1. before upgrading to 12.1 (for 10.1.1 Pre-requisite checks 4.1. before upgrading to Release 12.1 to ensure that all patches specific to 10gR2 database release are applied on the environment. before upgrading to Release 12.2 Release Update Pack only to an existing Release 12.3.1.1 Cross check the database initialization parameters for 10gR2 Review Oracle Support Portal document 761570.1 to Release 12. and functionality enhancements into a consolidated.1.1. suitewide patch set.2.2 Release Update Pack (12. This is a mandatory pre-install step.2 Cross check the database patches for 10gR2 Refer Oracle Support Portal document 761570.2.2 52 .2 This phase covers the detailed steps to apply the Oracle E-Business Suite Release 12.1. Release 12. before you apply release 12. This release is a maintenance pack and can only be installed on top of an existing Oracle E-Business Suite Release 12.1 environment.1.4 ) and apply all required patches mentioned in the document.2.

4.1. provided by Release 12.AD.1. Run the admkappsutil.2 Apply the latest consolidated online help Patch 7303032 using AutoPatch and follow the instructions in the patch readme file. For more information.pl utility to create the file appsutil.1.2.Delta.3 Apply Post-Release Update Patch The post-release update patch addresses issues that were identified after the release of Release 12.env · · Run AutoConfig on the APPL_TOP.2. refer to Oracle Support Portal document 387859. $perl <AD_TOP>/bin/admkappsutil./<APPL_TOP>/APPS<CONTEXT_NAME>.1.1 Apply R12 AD Patch Apply R12. refer to Note 981033. 4.2 for more information about R12.AD. R12.2 RUP Patch Apply Release 12.B.1.AD.B.1 Oracle Payment Application Data Security Standard (PA-DSS) Consolidated Patch Release Notes. Apply the following patch on top of a Release 12.2 code level After upgrading Release 12.1 Update database tier nodes with the Release 12.2.This PA-DSS consolidated patch allows Oracle Payments customers to benefit from the ongoing enhancements made to conform to PA-DSS requirements.4.2: Application tier: · As the APPLMGR user.B.1.Delta.2 Applying the Release Update Pack To apply Release 12.1. 4.1.2 Apply R12. $. before you complete any of the other steps in this section. Release 12. follow these steps: 4.DELTA.1. 4.2.1.pl For details on how to run AutoConfig and create appsutil. run the environment file for the current APPL_TOP. .zip in the <INST_TOP>/admin/out directory.2 must be applied separately and should not be merged with any other patch.2. · Patch 8937577 .4 Post-update steps 4.2.2. 4.1 Using AutoConfig to Manage System Configurations in Oracle Applications Release 12 53 .1 Oracle E-Business Suite DBA Software Updates. Release 12. Refer to Oracle Support Portal document 879322.zip.3 Apply Online Help Patch for R12.2 instance.2 Patch 7303033 using AutoPatch and follow the instructions in the patch readme file.1.2 Patch 8502056 using AutoPatch. perform the following post-update steps to update all database tier nodes with the code level.

Step 3.3 Perform product-specific steps (conditional) After you have completed the steps to update all database tier nodes with the code level. apply the translated version(s) of Release 12. If you plan to install new languages after you apply Release 12.Database tier · As the ORACLE user./<RDBMS ORACLE_HOME>/<CONTEXT_NAME>. . $cd <RDBMS ORACLE_HOME> $. Patching AutoConfig of Oracle Support Portal document 387859. refer to Section 2. See the Installing Translations section and follow the instructions for adding a new language to a Release 12.1.pl on the database tier and the application tier.1.1.2 Perform NLS-related step (conditional) If you have languages other than American English already installed in your Release 12. refer to Oracle Support Portal document: 788053.2 Patch 7303033 for the new language(s).1. 4. run the environment file for the current ORACLE_HOME.zip under the <RDBMS ORACLE_HOME>.zip file to the <RDBMS ORACLE_HOME>.2 Patch 7303033 for each active language immediately after applying the American English version of the Release 12. $cd <ORACLE_HOME> $unzip -o appsutil.2 Patch 7303033.1 system.zip · Run AutoConfig on the <RDBMS ORACLE_HOME>.1 Oracle Applications NLS Release Notes.4. for product specific patches.pl appsTier For details on how to run adpreclone. refer to Oracle Support Portal document 406982. 54 .1.pl.4. perl adpreclone. adpreclone must be run again to apply the updates to the clone directory structures that were used during cloning.1 system.2.1 Oracle EBusiness Suite Readme. It is not necessary to apply the Release 12.2 Patch 7303033.1 Cloning Oracle Applications Release 12 with Rapid Clone. 4. Review Oracle Support Note 949406. Uncompress appsutil. For details on how to run AutoConfig on the database tier and how to transfer the AutoConfig updates from the APPL_TOP to the RDBMS ORACLE_HOME.1.pl dbTier perl adpreclone. Since updates included in RUP6 were applied to the system.1.env · · Copy or FTP the appsutil. Release 12. perform the post-update steps for products licensed by you.1 Using AutoConfig to Manage System Configurations in Oracle Applications Release 12 Database tier and application tier Re-run adpreclone.

55 . determine if your particular environment requires any additional steps by thoroughly reading both the Oracle Database Upgrade Guide: 11g Release 2 (11. This phase will upgrade the database instance to Oracle RDBMS 11gR2 by first installing a new 11gR2_ORACLE_HOME.1 Interoperability Notes Oracle E-Business Suite Release R12 with Oracle 11g Release 2 (11.1.0). or database name parameters on the database server.1 and the Vision Demo database 10gR2 instance on HP Integrity servers running HP-UX 11i v3.1. 5.2 database to 11gR2 Section 2 does not depend on section 1 and can be performed first or simultaneously.html.2. and then upgrading the E-Business Suite R12.1.1 Interoperability Notes Oracle E-Business Suite Release R12 with Oracle 11g Release 2 (11.0) During this upgrade phase of the migration. 5. SID.2 Pre-requisite before the database install Review the Step 1 Verify software versions in Before the Database Installation of Oracle Support Portal document: 1058763.Phase 5: Upgrade E-Business Suite RDBMS from 10gR2 to 11gR2 The source environment consists of Oracle E-Business Suite Release 12. you must also update AutoConfig on the database tier and deregister the current database server node.com/technology/software/index. http://www. Part# E1081902 and Oracle Support Portal document: 1058763. you will: · Section 1: Prepare the database server for 11gR2 upgrade · Section 2: Install Oracle RDBMS 11gR2 software · Section 3: Upgrade E-business Suite Release 12. Download and stage the Oracle RDBMS 11gR2 and Example CD installation media for HP Integrity server from Oracle‟s software download website.2. host. Make sure all the requirements are satisfied.0). shutdown the E-Business Suite environment and take a full cold backup of both the application tier and database tier.2).1.1 Backup the E-Business Suite environment For rollback purposes.3 Deregister the current database server (conditional) If you plan to change the database port.1 Prepare the database server for 11gR2 upgrade This section includes the tasks to prepare the source database server for the upgrade to RDBMS 11gR2. along with some additional steps to complete the upgrade. Before proceeding. 5.oracle. The following steps were derived from Oracle Support Portal document: 1058763.2. 5.1 Interoperability Notes Oracle E-Business Suite Release R12 with Oracle 11g Release 2 (11.1 database instance using the Database Upgrade Assistant (DBUA).

2.2.2. The AutoConfig run will cut off the entire application tier from the database instance until the upgrade is complete. HP-UX: 11gR2 runInstaller Fails with "An internal error occurred within cluster verification framework" to apply HP-UX patches before starting the 11gR2 Run Installer. 56 .0 installation media staging area.0 Oracle home Read the System Considerations and Requirements section of Chapter 3 in Oracle Database Installation Guide: 11g Release 2 (11.2.1.0 software Start up an Xterm session on the source database server as the “oracle” user.1. Part# E10851-05 Note Refer Oracle Support Note 983713. 5.1 Prepare to create the 11.0 configuration: Variable Name Value s_dbhost New database hostname s_dbdomain New database domain name s_db_serv_sid New database SID s_dbport New database listener port s_apps_jdbc_connect_descriptor NULL Review Oracle Support Portal document: 387859. change directory to the 11. 5. and run the Oracle Universal Installer. Use the Context Editor to update the following variables in the Applications context file on each application tier server node to reflect the 11. DO NOT source the 10gR2 database environment file.4 Update application tier context file with new database listener port number (conditional) The new 11.2.2) for HP-UX. Do not run AutoConfig on the application tier once the context file has been updated.2 Install Oracle RDBMS 11gR2 This section includes the steps to install only the software of Oracle RDBMS 11gR2 on HP Integrity server. $ cd <11gR2_staging_directory> $ . replacing the current database listener. You will be running AutoConfig on the application tier to configure the system for the new port number after the upgrade is finished and the new database listener is in use.0 Oracle home uses its own database listener for the database instance.5.1 Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12 for instructions on how to update and run the Context Editor./runInstaller Select Installation Type Enterprise Edition Specify Home Details Name: OUIHome2 Path: <11gR2_ORACLE_HOME> Product-specific prerequisite checks The warning status for the OS and kernel patches can be ignored if running the prescribed software releases and kernel settings.2.2. 5.2 Install the base 11.

The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new Perl executable is located (usually $ORACLE_HOME/perl/bin). export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5.1 patch set for your platform.0 export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:. The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.0 Example CD staging_directory> $ .0. The ORACLE_HOME environment variable points to the new 11. Make sure that: · · · · · You DO NOT source the 10gR2 database environment file.sh End of Installation 5. and run the Oracle Universal Installer directly from that staging area. Read the patch set notes (usually README.html).2.2. Start up an Xterm session on the source database server as the “oracle” user. Start up an Xterm session on the source database server as the “oracle” user. The PERL5LIB environment variable points to the directories where the new Perl libraries are located (usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>).2.4 Perform RDBMS 11gR2 patch set pre-installation tasks On the database server node.Many of the required patches. as the owner of the Oracle 11g file system and database instance.0 \ :$ORACLE_HOME/perl/lib/site_perl/5./runInstaller 5.10.2. Make sure you thoroughly understand the upgrade and patch set installation process before you begin. as well as some kernel settings have been superseded or discontinued. 57 . 5. $ $ $ $ export ORACLE_HOME=/oracle/<sid>db/11. Upgrade an Existing Database NO Select Configuration Option Install database software only Execute Configuration scripts Popup As root user run the following script: # <11gR2_ORACLE_HOME>/root.0 $ cd <11. change directory to the 11gR2 Patch Set staging area.3 Install Oracle Database 11g Products from the 11gR2 Example CD Review the tasks in section 3.5. change directory to the 11gR2 Example CD staging area and run the Oracle Universal Installer.2. of Installing Oracle Database 11g Products in the Oracle Database Example CD Installation Guide Part#E10402-02 for your platform.0 Oracle home. Check Oracle Support Portal or contact Oracle Support Services to determine any known issues with the patch set and its interoperability with Oracle E-Business Suite R12. download and unzip the 11.10.2. Do not perform the tasks in the Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation section.2.5 Perform RDBMS 11gR2 patch set installation tasks Review the tasks in the Installing the Oracle Database 11g Patch Set interactively section of the patch set notes.

as the owner of the Oracle RDBMS file system and database instance. If any are found.2. $ $ $ $ export ORACLE_HOME=<11gR2_ORACLE_HOME> export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:.1.0) certified with Oracle E-Business Suite Release 12 is 11. The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib. 5. database and listener before applying the following platform specific RDBMS one-off patches.0.0 $ cd <11.10.0 before applying this additional RDBMS patch.2.· · · · · Make sure that: You DO NOT source the 10gR2 database environment file. The PERL5LIB environment variable points to the directories where the new Perl libraries are located (usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>) $ $ $ $ export ORACLE_HOME=<11gR2_ORACLE_HOME> export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:. 58 . The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new Perl executable is located (usually $ORACLE_HOME/perl/bin). make sure that the ORA_NLS10 environment variable is set to the full path of the 9idata directory whenever you enable the 11gR2 Oracle home.2. export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5.0 Oracle home. Review all the readme files before applying any patch and review the logs for any discrepancy after applying each patch. Currently. The ORACLE_HOME environment variable points to the new 11.0 stage directory>/Disk1 $ .2. run the $ORACLE_HOME/nls/data/old/cr9idata.2. Check the OPatch inventory before and after applying patches.pl script to create the $ORACLE_HOME/nls/data/9idata directory.8 Install the latest available patch set release and any required patches (conditional) Once you have installed the major Oracle Database 11g software. 5.2. the only patch set level of Oracle Database 11g Release 2 (11.10.1 WITH EBS RELEASE 12.2. check to see if there is a patch set release and/or critical patch update to be installed.2.2.10.7 Apply additional RDBMS one-off patches Shutdown the Applications server services.0.pl $ export ORA_NLS10=$ORACLE_HOME/nls/data/11gR2data After creating the directory.0 \ :$ORACLE_HOME/perl/lib/site_perl/5.10./runInstaller 5.0 $ cd $ORACLE_HOME/nls/data/old $ perl cr9idata. Do not run any of the post install instructions as those will be done after the upgrade.6 Create nls/data/9idata directory On the database server node. Also apply OPatch executable for 11. export LD_LIBRARY_PATH=$ORACLE_HOME/lib export PERL5LIB=$ORACLE_HOME/perl/lib/5.0 \ :$ORACLE_HOME/perl/lib/site_perl/5. Apply one-off Patch 9218789 N-APPLY BUNDLE PATCH FOR RDBMS 11. resolve them first before continuing to the next step.

4 Run the pre-upgrade information tool The following steps were derived from the Oracle Database Upgrade Guide: 11g Release 2 (11.2).ENABLED$INDEXES (conditional) If the SYS. Take note of the section pertaining to the Database Upgrade Assistant (DBUA).3. # su – oracle $ lsnrctl stop <SID> 5.3 Upgrade E-Business Suite RDBMS to 11gR2 This section includes the tasks to upgrade the Oracle E-Business Suite database from 10gR2 to 11./adstpall.0). Run the pre-upgrade information tool using the following steps: · Logon as the owner of the 11gR2_RDBMS file system and source the environment.The latest patch set release and critical patch update for Oracle Database 11g Release 1 should be installed prior to upgrading your databases.2). # cat /etc/oratab <SID>:<11gR2_ORACLE_HOME>:N: 5.2 Stop the Applications server processes and the database listener Stop applications server services on the Applications Administrator Service Node. # su – applmgr $ cd $COMMON_TOP/admin/scripts/<SID>_<HOSTNAME> $ .3. Verify that the /etc/oratab file has correct entries for the 11gR2 Database and 11gR2 Oracle Home.0.3. Make sure that you unset the TNS_ADMIN environment variable.ENABLED$INDEXES table exists. · Copy and run the utlu112i.sql \ <upg_1120_log_directory> 59 . Part Number E17222-05. 5. connect to the database as SYSDBA and run the following command to drop it: SQL> drop table sys. $ cp <11g_ORACLE_HOME>/rdbms/admin/utlu112i.enabled$indexes. 5.1 Interoperability Notes Oracle E-Business Suite Release R12 with Oracle 11g Release 2 (11.2.sh apps/<apps_password> Stop database listener on the database node.3 Drop SYS. to prepare for the upgrade. Also review Oracle Support Portal document: 1058763. If you plan to change the PL/SQL compilation mode.2. Refer to the specific patch release and critical patch update documentation for installation information. disable the compilation of objects. Part# E10819-02. 5. During this process. the environment will be unavailable until the upgrade has completed.sql from <upg_1120x_log_directory>.3.1 Prepare to upgrade Review Chapter 2 of Oracle Database Upgrade Guide: 11g Release 2 (11.

Select the 11gR2 database from the list of available databases. note that Oracle E-Business Suite has only one statistics table. set the _disable_fast_validate parameter using the following command: $ export ORACLE_HOME=<11gR2_ORACLE_HOME> $ cd $ORACLE_HOME/bin $ . Review “UpgradeResults. and run the DBUA from $ORACLE_HOME/bin.3. The upgrade log files are located in $<11gR2_ORACLE_HOME>/cfgtoollogs/dbua/<SID>/upgrade.out SQL> @utlu112i. you must have the _disable_fast_validate parameter in your initialization file.1 Database Initialization Parameters for Oracle Applications Release 12.6 Modify initialization parameters The newly installed Oracle 11gR2 will not be tuned for E-Business Suite.1 How to Download and Run Oracle's Database Pre-Upgrade Utility.3. For further details. Set the environment variable ORACLE_HOME to point to the 11gR2_ORACLE_HOME directory created in the „Step 5. DBUA will automatically start the instance./ dbua -initParam "_disable_fast_validate=TRUE" When upgrading all statistics tables.2 Install Oracle RDBMS 11gR2‟ and run the Oracle Database Upgrade Assistant (DBUA) against the Applications 11i database. APPLSYS.FND_STATTAB that needs to be upgraded.sql by connecting to 11gR2 Database with SYSDBA privileges. Monitor the progress of the DBUA.5 Upgrade database Make sure that the Applications server processes and the 11gR2 database listener have been stopped. disable the compilation of objects. Start an Xterm session on the source database server as the “oracle” user. see Oracle Support Portal document: 884522. If you plan to change the PL/SQL compilation mode. $ cd <upg_1120_log_directory> $ sqlplus '/ as sysdba' SQL> spool utlu112i. 5. At the end of the upgrade process. When running DBUA.sql SQL> spool off Review the output for any errors or warnings and make any necessary changes before proceeding on to the next step. Review the Oracle Support Portal document: 396009. 5. Before performing any upgrade or maintenance operation. Spool the output of this execution into utlu112i.out.· Execute the utlu112i. export the new ORACLE_HOME.html” and make any necessary changes. Make sure you use the following sections as a guideline for modifying the initialization parameter file: · Common database initialization parameters · Release-specific database initialization parameters for 11gR2 · Database initialization parameter sizing 60 .

Query returning the number of objects compiled so far.9 Natively compile PL/SQL code (optional) You can choose to run Oracle E-Business Suite Release 11i PL/SQL database objects in natively compiled mode with Oracle Database 11gR2. For detailed steps.2.3.3. 5.0 patch set post-installation tasks Run only the catmgdidcode. If you encounter the error: ORA-04030: out of process memory when trying to allocate 822904 bytes (pga heap.sql scripts for the post install instructions in patch 9218789.sql Use the following queries to track recompilation progress: Query returning the number of invalid objects remaining. When modifying the initialization parameters pertaining to the PL/SQL native compilation.ora before modifying. 61 .2).ora and backup the init<SID>. SQL> SELECT COUNT(*) FROM obj$ WHERE status IN (4. SQL> shutdown SQL> startup SQL> @?/rdbms/admin/utlrp. Make sure that you rename the spfile<SID>. 5. 6). If native compilation of PL/SQL code is disabled in your database instance.1.8 Validate invalid objects within the database. 5.7 Perform 11. This number should decrease with time. SQL> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED. This number should increase with time. Database Initialization Parameter Settings for Oracle Applications Release 12 as a guideline. kco buffer) ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48] then set the _pga_max_size initialization parameter to a larger value as follows: _pga_max_size=104857600 Restart your database. Ensure the parameter "_disable_fast_validate=TRUE" is in the initialization file.Note: During the database startup. You are not confined to using the parameter files generated by the database upgrade assistant.sql and utlrp. Make the appropriate modification and restart the database. both pfile and spfile have the same values.ora) and if not found the RDBMS will attempt to load the pfile (init<SID>. Oracle DB 11g first looks in $ORACLE_HOME/dbs for the spfile (spfile<SID>. 5. Ensure that the temporary tablespace is properly defined. Bounce the database and run the SQL script to validate invalid objects within the database. The other scripts are run as part of the DBUA upgrade. refer to the Compiling PL/SQL Code for Native Execution section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference 11g Release 2 (11. This line will have to be commented out after the upgrade and any other maintenance procedures. After the 11gR2 upgrade. It will be easier to modify the pfile and then recreate the spfile after all the changes are in and the database started. ignore the initialization parameters that pertain to the native compilation of PL/SQL code.ora) file.3. refer to Oracle Support Portal document: 396009.

sql. Section 3.2) for more information. including the database and the listener.2 explains how to generate a context file on the database tier. 11g Release 2 (11.sql script using the following command: $ sqlplus [APPS user]/[APPS password] @wfaqupfix.12 Set CTXSYS parameter Connect to the database as SYSDBA and run the following command: $ sqlplus "/ as sysdba" SQL> exec ctxsys.sql require the APPLSYS schema name parameter to be passed instead of APPS. 5. and restart them to load the new environment settings.11 Run adgrants. See the Oracle Database Net Services Administrator's Guide. $ cp <11gR2_Oracle_Home>/network/admin/<SID>_<hostname>/* $TNS_ADMIN Start the new Oracle Net Listener. start the listener with the lsnrctl executable. perform these additional steps: Create the $TNS_ADMIN directory in the 11gR2_ORACLE_HOME.3. Connect to the database as SYSDBA and run the script using the following command: $ sqlplus "/ as sysdba" @adgrants. see Oracle Support Portal document: 387859.sql from the administration server node to the database server node.3. you must also run AutoConfig on each application tier server node to update the system with the new listener.13 Validate Workflow ruleset On the administration server node.sql) [APPS schema name] Verify the syntax and usage of adgrants.3.sql\ [APPLSYS user] [APPS user] 5. $ lsnrctl start <SID> 5. 62 .14 Implement and run AutoConfig Configure and run AutoConfig in the new Oracle home on the database server node. For instructions on how to implement and run AutoConfig. Prior to starting the listener. If the database listener of the new Oracle home is defined differently than the old Oracle home. connect to the database as APPS and run the $FND_TOP/patch/115/sql/wfaqupfix.5.10 Start the new database listener (conditional) Since AutoConfig has not yet been implemented.ctx_adm.sql (conditional) Copy $APPL_TOP/admin/adgrants. $ $ $ $ $ $ export ORACLE_HOME=<11g_ORACLE_HOME> export ORACLE_SID=<SID> export PATH=$ORACLE_HOME/bin:$PATH:. 5.set_parameter('file_access_role'. 'public').sql (or adgrants_nt.3. Shut down all processes. export ORA_NLS10=$ORACLE_HOME/nls/data/<11gR2 data> mkdir –p $ORACLE_HOME/network/admin/<SID>_<hostname> export TNS_ADMIN=$ORACLE_HOME/network/admin/<SID>_<hostname> Copy the contents of 11gR2_TNS_ADMIN to $TNS_ADMIN.3. Older versions of adgrants.1 Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12.

1 Additional Database Privilege needed for Demantra Schema when Running on Oracle 11g Database. Connect to the database as SYSDBA and use the following commands to run adstats.3.16 Create Demantra privileges (conditional) If you are using Demantra. SQL> exit. SQL> @adstats. source the new database environment file.sh \ contextfile=<11g_ORACLE_HOME>/appsutil/<SID>_<hostname>.15 Gather statistics for SYS schema Copy $APPL_TOP/admin/adstats. errors. Make sure that default temporary tablespace has at least 1. 63 . perform the steps explained Oracle Support Portal document: 730883.xml \ appspass=<apps_password> Review log file for any failures.sql $ sqlplus "/ as sysdba" SQL> alter system disable restricted session.sql has to be run in restricted mode: $ sqlplus "/ as sysdba" SQL> alter system enable restricted session. $ cd $ORACLE_HOME/appsutil/bin $ . Shut down the 11g database and listener./adconfig. ensure the variable s_jretop points to a proper JRE directory.5 GB of free.3. or warnings and resolve those issues before continuing. Note: An improper entry introduced into the context file can render the applications environment inoperable. 5.After creating the XML context file. Run AutoConfig to generate a new 11g environment file located in the <11g_ORACLE_HOME> directory.env $ lsnrctl start <SID> $ sqlplus / as sysdba SQL> startup 5.sql from the administration server node to the database server node. Always make a backup prior to editing the context file. $ sqlplus / as sysdba SQL> shutdown normal SQL> exit $ lsnrctl stop <SID> # su – oracle $ . This task will migrate AutoConfig on the DB Tier.sql in restricted mode as adstats. and then start up the listener and the 11g database. <11g_ORACLE_HOME>/<SID>_<hostname>.

<APPL_TOP>/APPS<SID>_<hostname>. · Use adadmin on the Administration server node to re-create grants and synonyms.3.sql from the directory where you launch the SQL*Plus session. · Startup the database using the upgrade option. SQL> create database link <custom database link> connect to <user> identified by <password> using '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>) (PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))'.17 Re-create custom database links (conditional) If you have different configuration for the database listener in the new Oracle home. where <custom database link>. as the owner of the Applications file system.18 Re-create grants and synonyms You must re-create the grants and synonyms in the APPS schema as Oracle Database 11g Release 1 (11.14 Implement and run AutoConfig‟.3. · Start SQL*Plus session with sysdba privilege and shutdown the database. then you must recreate any custom self-referential database links that exist in the Applications database instance. <hostname>. run adadmin and select the Recreate grants and synonyms for APPS schema task from the Maintain Applications Database Objects menu. Verify the existing database links. For custom self-referential database links (if any) in the database instance. SQL> @utlirp. <password>.3. <port number>. 5. · Change directory to $ORACLE_HOME/rdbms/admin.sql · Check invalid objects SQL> select count(*) from dba_objects \ where status = ‘INVALID’. SQL> startup upgrade · Run the utlirp.env $ adadmin Maintain Applications Database Entities Re-create grants and synonyms for APPS schema 64 .sql from the directory where you launch the SQL*Plus session. # su – applmgr $ . then they should have been updated with the new port number by AutoConfig in the step „5.5. and <ORACLE_SID> reflect the new Oracle Net listener for the database instance. If EDW_APPS_TO_WH and APPS_TO_APPS database links exist. use the following commands to drop and re-create them: $ sqlplus apps/<apps password> SQL> drop database link <custom database link>. Log on the administration server node. Connect to the Applications database instance as APPS and run the following query: $ sqlplus apps/<apps password> SQL> select db_link from dba_db_links.sql · Bounce the database and run the utlrp. SQL> @utlrp.2) contains new functionality for grants and synonyms compared to previous database releases. <user>.

ora’. perform a full backup to complete the upgrade to 11gR2 phase.3.1. You should start the Oracle Net listener for the database instance.20 Restart Applications server processes Restart all the Application tier server processes that you shut down previously. This completes the upgrade and migration of Oracle Applications 11i running on HP AlphaServer systems running Tru64 UNIXs to Oracle E-Business Suite Release 12. 5.21 Synchronize Workflow views Log on to Oracle E-Business Suite with the "System Administrator" responsibility.2 running on HP Integrity servers. Enter the following parameters: Request Name = Workflow Directory Services User/Role Validation p_BatchSize = 10000 p_Check_Dangling = Yes Add missing user/role assignments = Yes Update WHO columns in WF tables = No Click "OK" and "Submit". Navigate to Click Requests > Run > Single Request and the OK button. 65 . as well as the database instance itself in the 11. 5.19 Recreate spfile from pfile $ cd $ORACLE_HOME/dbs $ sqlplus / as sysdba SQL> CREATE SPFILE FROM PFILE = '<ORACLE_HOME>/dbs/init<SID>.22 Validate environment and perform a full backup After successfully validating the E-Business Suite environment as per Appendix G.3.2 Oracle home.5.3. 5.3.

These are only suggested kernel settings and should be considered a starting point for additional operation system tuning. whichever is greater. SHMMNI SHMSEG SWCHUNK 400 300 2048 66 .824. Table 10.767 For the Database tier up to 50% of available physical memory or 1. List of 11i v3 kernel parameters MAXTSIZ MAXFILES_LIM NPROC KSI_ALLOC_MAX MAX_THREAD_PROC MAXDSIZ MAXDSIZ_64BIT MAXFILES MAXSSIZ MAXSSIZ_64BIT MAXUPRC MSGMNB MSGMNI MSGTQL NFLOCKS NINODE NKTHREAD SEMMNS SEMMNI SEMMNU SEMVMX SHMMAX 100663296 4096 4200 (NPROC*8) 1200 1073741824 4294967296 2048 8388608 268435456 256 16384 512 1024 4096 (2*NPROC+1024) (NPROC *2) 4096 2048 256 32.Appendix A: Kernel parameters Table 10 is a list of HP-UX 11i v3 kernel parameters.073.741. The Applications tier normally requires no more than 1GB.

. minimum required size: 58 MB --> APPS_TS_QUEUES tablespace is adequate for the upgrade. No changes are required.3.. .ora or spfile] ********************************************************************** WARNING: --> "streams_pool_size" is not currently defined and needs a value of at least 50331648 WARNING: --> "large_pool_size" needs to be increased to at least 8388608 WARNING: --> "session_max_open_files" needs to be increased to at least 20 .. .0 --> compatible: 9. ********************************************************************** Components: [The following database components will be upgraded or installed] ********************************************************************** --> Oracle Catalog Views [upgrade] VALID --> Oracle Packages and Types [upgrade] VALID --> JServer JAVA Virtual Machine [upgrade] VALID 67 . ********************************************************************** Database: ********************************************************************** --> name: VIS --> version: 9. ********************************************************************** Logfiles: [make adjustments in the current environment] ********************************************************************** --> The existing log files are adequate. No changes are required.sql Oracle Database 10.. ********************************************************************** Update Parameters: [Update Oracle Database 10..2 Upgrade Information Utility 07-02-2010 18:32:27 . minimum required size: 11038 MB --> ODM tablespace is adequate for the upgrade. minimum required size: 23 MB --> TEMP tablespace is adequate for the upgrade..0.6.2 init.ora or spfile] ********************************************************************** --> "optimizer_max_permutations" --> "row_locking" --> "undo_suppress_errors" --> "max_enabled_roles" --> "enqueue_resources" --> "sql_trace" . minimum required size: 15 MB . minimum required size: 590 MB --> APPS_TS_TX_DATA tablespace is adequate for the upgrade.. ********************************************************************** Obsolete/Deprecated Parameters: [Update Oracle Database 10.ora or spfile] ********************************************************************** -.No renamed parameters found.2 init..2.. .... . . Prepare for upgrading the database instance. ********************************************************************** Renamed Parameters: [Update Oracle Database 10. ..0 --> blocksize: 8192 .Appendix B: Pre-Upgrade Information Utility output file This is the Pre-Upgrade Information Utility output file generated in section 1.. minimum required size: 7548 MB --> APPS_UNDOTS1 tablespace is adequate for the upgrade.2 init.3. SQL> @utlu102i.2. .... . ********************************************************************** Tablespaces: [make adjustments in the current environment] ********************************************************************** --> SYSTEM tablespace is adequate for the upgrade..

.is required to be installed from the 10g Companion CD. 68 .2 environment] ********************************************************************** --> New "SYSAUX" tablespace .. SQL> exit The following steps were performed to address the Miscellaneous Warnings section of the output file: Issues requiring further analysis prior to upgrading If the Pre-Upgrade Utility displays a warning about any of the following issues. Passwords will be encrypted during the upgrade. ********************************************************************** Miscellaneous Warnings ********************************************************************** WARNING: --> Passwords exist in some database links... USER APPS has 2 INVALID objects.. OLAPSYS .. minimum required size for database upgrade: 500 MB .. .... WARNING: --> Deprecated CONNECT role granted to some user/roles... MDSYS WARNING: --> Database contains INVALID objects prior to upgrade..... either inadvertently or maliciously....... .. CONNECT role after upgrade has only CREATE SESSION privilege.... WARNING: --> Database contains stale optimizer statistics...required to be installed from the 10g Companion CD.The 'Oracle interMedia Image Accelerator' is .. .. .. USER APPLSYS has 1 INVALID objects. PL/SQL procedure successfully completed. .The 'JServer JAVA Virtual Machine' JAccelerator (NCOMP) . then further analysis of the database is recommended prior to upgrading to Oracle Database 11g: · Deprecated CONNECT Role · Database Links With Passwords · TIMESTAMP WITH TIMEZONE Datatype · Optimizer Statistics Deprecated CONNECT Role Each user should ONLY have those privileges appropriate to the tasks he needs to do.. Component Schemas with stale statistics: . --> Spatial [upgrade] VALID .. . --> Oracle XDK for Java [upgrade] VALID --> Oracle Java Packages [upgrade] VALID --> Oracle Text [upgrade] VALID --> Oracle XML Database [install] --> Real Application Clusters [upgrade] INVALID --> OLAP Analytic Workspace [upgrade] UPGRADED --> OLAP Catalog [upgrade] VALID --> Oracle OLAP API [upgrade] UPGRADED --> Oracle interMedia [upgrade] VALID .. Downgrade of database links with passwords is not supported. ********************************************************************** SYSAUX Tablespace: [Create tablespace in the Oracle Database 10.. ...... . Refer to the 10g Upgrade Guide for instructions to update . SYS ... statistics prior to upgrading the database.. so that it remains easy to do what is needed while concurrently reducing the ability to do inappropriate things.. Least privilege mitigates risk by limiting privileges..

'OLAPDBA'. The upgrade scripts adjust the privileges for the Oracle-supplied users. then save the information about affected database links from the SYS. GRANTEE -----------------------------------------EUL_US SSOSDK WEBSYS PROJMFG SERVICES WIRELESS EDWEUL_US 7 rows selected. 'SYSTEM'. 'ORDPLUGINS'. If you anticipate a requirement to be able to downgrade back to your original release. you must run the utltzuv2. so that you can recreate the database links after the downgrade. 'WK_TEST'.The CONNECT role privilege reduction feature reduces the number of privileges granted to the connect role to only one: CREATE SESSION The seven other privileges have been removed from the CONNECT role: 1. 'WMSYS'. 'DMSYS'.CREATE VIEW 2. 'SYSMAN'. the other privileges granted to the CONNECT role in earlier releases will be revoked during the upgrade. 'XDB'. then grant the specific required privileges prior to upgrading.CREATE CLUSTER 5. 'OLAPSVR'. 'MDDATA'. 'OEM_MONITOR'. To identify which users and roles in your database are granted the CONNECT role. 'ORDSYS'.sql script on 69 . 'CTXSYS'. the database links will not exist in the downgraded database. TIMESTAMP WITH TIMEZONE datatype The time zone files that are supplied with Oracle Database 11g have been updated from version 3 to version 4 to reflect changes in transition rules for some time zone regions.CREATE SYNONYM 4.CREATE DATABASE LINK 6. 'OLAPSYS'. the CONNECT role will only have the CREATE SESSION privilege. Consequently. 'EXFSYS'. To downgrade back to the original release. 'DBSNMP'.ALTER SESSION After upgrading to Oracle Database 11g. 'MDSYS'.CREATE TABLE 3. use the following query: SELECT grantee FROM dba_role_privs WHERE granted_role = 'CONNECT' and grantee NOT IN ( 'SYS'. 'LOGSTDBY_ADMINISTRATOR'. 'WKSYS'. 'OUTLN'. 'LBACSYS'. To preserve this TIMESTAMP data for updating according to the new time zone transition rules. 'OLAP_USER'. The changes may affect existing data of TIMESTAMP WITH TIME ZONE datatype.LINK$ table. 'WKPROXY'. If users or roles require privileges other than CREATE SESSION. 'SI_INFORMTN_SCHEMA'.CREATE SEQUENCE 7. 'WKUSER'. all of the database links with encrypted passwords must be dropped prior to the downgrade. Database links with passwords During the upgrade to Oracle Database 11g. 'ODM'). any passwords in database links will be encrypted.

then you should use the DBMS_STATS. the conversion will happen automatically during the import. exec dbms_stats.0.gather_schema_stats('WMSYS'. Optimizer statistics When upgrading to Oracle Database 11g.options=>'GATHER'. After the upgrade. If you are using Release 9. estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE.gather_schema_stats('MDSYS'.gather_schema_stats('CTXSYS'. cascade => TRUE). This script analyzes your database for TIMESTAMP WITH TIME ZONE columns that are affected by the updated time zone transition rules. As of Oracle Database 10g Release 10.GATHER_SCHEMA_STATS procedure to gather statistics.AUTO_SAMPLE_SIZE.GATHER_DICTIONARY_STATS procedure to gather these statistics. Component Schemas with stale statistics: SYS MDSYS The following steps were used to optimize statistics. exec dbms_stats. If you export the tables before upgrading and import them after the upgrade. This script is located in the new 11g ORACLE_HOME/rdbms/admin directory. method_opt => 'FOR ALL COLUMNS SIZE AUTO'. Refer to the 11g Upgrade Guide for instructions to update statistics prior to upgrading the database. and recreate the TIMESTAMP data from these tables after the upgrade. $ cd /tmp $ sqlplus ‘/ as sysdba’ spool opt_stats.sql script identifies columns with time zone data affected by a database upgrade. This statistics collection can be time consuming for databases with a large number of dictionary tables.AUTO_SAMPLE_SIZE. The following warning was also generated by the Pre-Upgrade Information Utility report. you must update the tables to ensure that the data is stored based on the new rules. you can collect statistics prior to performing the actual database upgrade. you can enter the following: EXEC DBMS_STATS. cascade => TRUE). To decrease the amount of downtime incurred when collecting statistics.SSXFF TZR').2. Alternatively. estimate_percent => DBMS_STATS. TO_CHAR(column.options=>'GATHER'. estimate_percent => DBMS_STATS.0. Oracle recommends that you use the DBMS_STATS. then back up the data in character format before you upgrade the database.GATHER_DICTIONARY_STATS.1 or 9. method_opt => 'FOR ALL COLUMNS SIZE AUTO'.gather_schema_stats('XDB'.1. cascade => TRUE). create tables with the time zone information in character format (for example.MI. method_opt => 'FOR ALL COLUMNS SIZE AUTO'.sql script If the utltzuv2.AUTO_SAMPLE_SIZE. but statistics gathering only occurs for those tables that lack statistics or are significantly changed during the upgrade. optimizer statistics are collected for dictionary tables that lack statistics. See also: Oracle Database Globalization Support Guide for a detailed description of the utltzuv.options=>'GATHER'. exec dbms_stats. WARNING: --> Database contains stale optimizer statistics. estimate_percent => DBMS_STATS. 'YYYY-MM-DD HH24.options=>'GATHER'. For example.the database before upgrading. - 70 .out exec dbms_stats.

AUTO_SAMPLE_SIZE.options=>'GATHER'.options=>'GATHER'.AUTO_SAMPLE_SIZE. -method_opt => 'FOR ALL COLUMNS SIZE AUTO'. estimate_percent => DBMS_STATS. exec dbms_stats.method_opt => 'FOR ALL COLUMNS SIZE AUTO'.AUTO_SAMPLE_SIZE. cascade => TRUE). cascade => TRUE).AUTO_SAMPLE_SIZE.gather_schema_stats('ORDSYS'.gather_schema_stats('SI_INFORMTN_SCHEMA'. method_opt => 'FOR ALL COLUMNS SIZE AUTO'. SQL> spool off 71 . exec dbms_stats. exec dbms_stats. exec dbms_stats.AUTO_SAMPLE_SIZE. exec dbms_stats. cascade => TRUE). cascade => TRUE). method_opt => 'FOR ALL COLUMNS SIZE AUTO'.AUTO_SAMPLE_SIZE. exec dbms_stats.AUTO_SAMPLE_SIZE.options=>'GATHER'. exec dbms_stats.gather_schema_stats('SYS'.gather_schema_stats('WKSYS'.gather_schema_stats('SYSTEM'. estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE.options=>'GATHER'. cascade => TRUE). method_opt => 'FOR ALL COLUMNS SIZE AUTO'.options=>'GATHER'. cascade => TRUE).options=>'GATHER'.gather_schema_stats('OUTLN'. cascade => TRUE). estimate_percent => DBMS_STATS.options=>'GATHER'. method_opt => 'FOR ALL COLUMNS SIZE AUTO'. estimate_percent => DBMS_STATS. estimate_percent => DBMS_STATS. estimate_percent => DBMS_STATS. exec dbms_stats. estimate_percent => DBMS_STATS. cascade => TRUE). estimate_percent => DBMS_STATS. method_opt => 'FOR ALL COLUMNS SIZE AUTO'.gather_schema_stats('DBSNMP'. method_opt => 'FOR ALL COLUMNS SIZE AUTO'. estimate_percent => DBMS_STATS.gather_schema_stats('LBACSYS'.AUTO_SAMPLE_SIZE. exec dbms_stats.options=>'GATHER'. cascade => TRUE).options=>'GATHER'. method_opt => 'FOR ALL COLUMNS SIZE AUTO'.gather_schema_stats('ORDPLUGINS'. cascade => TRUE). method_opt => 'FOR ALL COLUMNS SIZE AUTO'.

0.log Successful OLAP Catalog Oracle_Server.0 10. as well as this summary.log Successful Post Upgrade PostUpgrade.log Successful Oracle XML Database Oracle_Server.6. Step Name Log File Name Status Database Backup Backup.2.log Successful Oracle XDK for Java Oracle_Server.0. See upgrade detail.4.2.0. Source Database Target Database Name: VIS VIS Version: 9.Appendix C: Post-Upgrade Information Utility output file This is the Post-Upgrade Information Utility output file generated in section 1.log Successful Oracle Java Packages Oracle_Server.log Successful* Enterprise Manager Configuration emConfigUpgrade.4 Database Backup Backup Location /oracle/EBS/VIS/backup Available Space (MB) 131451 Space Required (MB) 61896 Upgrade Details The following is a summary of the steps performed during the database upgrade. are available at "/oracle/EBS/visdb/10. Log files for all the steps.4 Oracle Home: /oracle/EBS/visdb/9.log Failed OLAP Analytic Workspace Oracle_Server.log Successful Oracle Server Oracle_Server.2.log Successful* Generate Summary generateSummary.2.3. Upgrade Results DBUA failed to upgrade the database or some of its components.log Successful Spatial Oracle_Server.log Successful Enterprise Manager Repository emRepository. Upgrade the Applications 11i database.log Successful Oracle OLAP API Oracle_Server.log Successful JServer JAVA Virtual Machine Oracle_Server.log Successful Oracle Text Oracle_Server.0.log Successful Oracle interMedia Oracle_Server.0 /oracle/EBS/visdb/10.log Successful* Pre Upgrade PreUpgrade.2.log Successful 72 .log Successful Real Application Clusters Oracle_Server.4/cfgtoollogs/dbua/VIS/upgrade0".

4/bin/emctl config emkey -repos -sysman_pwd < Password for SYSMAN user > 4) /oracle/EBS/visdb/10.0.sh" from the backup location. Step Execution Information: Database Backup The Database can be restored by running the following script "/oracle/EBS/VIS/backup/VIS_restore.2.4/bin/emctl stop dbconsole 3) /oracle/EBS/visdb/10. The Database Control URL is Enterprise manager configuration succeeded with the following warning Error securing Database Control.*Some information about the step is available.2.0. To secure the Database Control execute the following command(s): 1) Set the environment variable ORACLE_SID to VIS 2) /oracle/EBS/visdb/10.4/bin/emctl start dbconsole To secure Em Key.2. Database Control has been brought up in non-secure mode.2.0.4/dbs/spfileVIS.0. run /oracle/EBS/visdb/10. NOTE: This operation will remove all the upgrade changes made by the Database Upgrade Assistant.2.4/bin/emctl config emkey -remove_from_repos -sysman_pwd < Password for SYSMAN user > Initialization Parameter changes The following changes have been made in the initialization parameters: Parameters Added: Name streams_pool_size large_pool_size session_max_open_files Value 50331648 8388608 20 Obsolete Parameters Removed: Name optimizer_max_permutations row_locking undo_suppress_errors max_enabled_roles enqueue_resources sql_trace Enterprise Manager The Database will be managed locally using the Oracle Enterprise Manager Database Control.ora.2.4/bin/emctl secure dbconsole -sysman_pwd < Password for SYSMAN user > 5) /oracle/EBS/visdb/10. Enterprise Manager Configuration The Database will be managed locally using the Oracle Enterprise Manager Database Control.0. Post Upgrade A persistent initialization parameter file (spfile) has been created at the following location: /oracle/EBS/visdb/10.0. The Database Control URL is 73 .

Database Characterset information REM .sql auxttswrite.dat auque2. Import parameter file for the other objects Import parameter file for the global temporary tables.sql auexpxtts.dat auimpxtts.sql REM BEFORE RUNNING THE SCRIPT YOU MUST REVIEW REM IT FOR THE FOLLOWING: REM . Recovery manager parameter file to convert the endian format of data files.dat auexpmsc.dat auexpsys.dat auimpglb.dat auexpglb. Import parameter file for the transportable tablespace set.sql.sql Please review the following example file created above: aucrdb. Export parameter file for the other objects.dat auimpmsc. Import parameter file for the SYSTEM tablespace schemas.dat auimpsys. which in turn generates auque2.sql Description Script that creates the target database instance with the appropriate tablespace and file structure Script that converts the transportable tablespace set in the source database to read only Script that converts the transportable tablespace set in the source database back to read write Script that converts the users to their corresponding default tablespaces.sql.sql audeftbsp. XTTS example files File aucrdb. Patch 4872830 contains auque1.Location and size of the data files REM . Export parameter file for the transportable tablespace set.Temporary Tablespace information CREATE DATABASE 74 .Undo Tablespace information REM . auxttsread.Appendix D: XTTS example files Table 11.dat aurman. Export parameter file for the SYSTEM tablespace schemas. Enable the Advanced Queue settings in the target database instance. Export parameter file for the global temporary tables.

'/oracle/EBS/db/apps_st/data/sys3.dbf') SIZE 1024M. '/oracle/EBS/db/apps_st/data/sys6.dbf' SIZE 1500M. APPS_TS_SUMMARY.dbf' SIZE 1500M. 75 .MAXDATAFILES 512 CHARACTER SET UTF8 NATIONAL CHARACTER SET AL16UTF16 LOGFILE GROUP 1 ('/oracle/EBS/db/apps_st/data/log3.dat directory=dmpdir dumpfile=xttsmeta%U. APPS_TS_QUEUES.dbf' SIZE 2000M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M / ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "TEMP". prompt prompt Ignore any errors related to the setting prompt of the default temporary tablespace prompt above: auexpxtts.dbf' SIZE 1500M.dbf' SIZE 1500M. '/oracle/EBS/db/apps_st/data/sys7.dbf' SIZE 1500M.dbf') SIZE 1024M. APPS_TS_TX_INTERFACE.dmp filesize=10485760000 logfile=expxtts.dbf') SIZE 1024M DATAFILE '/oracle/EBS/db/apps_st/data/sys1. '/oracle/EBS/db/apps_st/data/sys5. '/oracle/EBS/db/apps_st/data/sys2. '/oracle/EBS/db/apps_st/data/undo04.dbf' SIZE 1000M. '/oracle/EBS/db/apps_st/data/undo02. APPS_TS_TX_IDX.dbf' SIZE 1000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE "TEMP" TEMPFILE '/oracle/EBS/db/apps_st/data/tmp1. ODM.dbf' SIZE 1024M UNDO TABLESPACE "APPS_UNDOTS1" DATAFILE '/oracle/EBS/db/apps_st/data/undo01. OLAP. GROUP 2 ('/oracle/EBS/db/apps_st/data/log2. APPS_TS_MEDIA. '/oracle/EBS/db/apps_st/data/sys4.dbf' SIZE 1500M.dbf' SIZE 1000M.dbf' SIZE 1000M SYSAUX DATAFILE '/oracle/EBS/db/apps_st/data/sysaux01.dbf' SIZE 1000M.log transport_tablespaces= APPS_TS_ARCHIVE. '/oracle/EBS/db/apps_st/data/undo03. APPS_TS_TX_DATA. GROUP 3 ('/oracle/EBS/db/apps_st/data/log1. APPS_TS_SEED. APPS_TS_NOLOGGING.

MATERIALIZED_VIEW_LOG auexpsys. PTG.dat file=gtab. AD_MONITOR.dat directory=dmpdir dumpfile=xttsmsc%U. PTE. ORDPLUGINS.dmp filesize=10485760000 76 . MDDATA. REPADMIN. ORACLE_OCM.log SCHEMAS= SYSTEM.INDEX. SYS. PROJMFG. SI_INFORMTN_SCHEMA. WEBSYS. MATERIALIZED_VIEW. DIP. PORTAL. ORDSYS. DMSYS. OUTLN. TSMSYS.log exclude=TABLE. AOLDEMO.RLS_POLICY.dmp filesize=1048576000 logfile=expsys.COMMENT. CTXTEST. WIRELESS.dat directory=dmpdir dumpfile=xttssys%U. DLD. DBSNMP auexpglb. SYNCSERVER auexpmsc.dmp full=y filesize=1048576000 logfile=expmsc. TRACESVR. ANONYMOUS. CSDUMMY. XDB.CONSTRAINT.OWAPUB. MDSYS.

alter tablespace APPS_TS_QUEUES read only.AD_GENERIC_TEMP'.AK_LOADER_TEMP'.GL_AHE_DETAIL_RANGES_GT'.MSC_PLANNING_ORGS') auxttsread. aurman. alter tablespace ODM read only. alter tablespace APPS_TS_SEED read only. 'APPS. APPS_TS_TX_IDX.IEC_TZ_OFFSET_MAP_CACHE'.IEC_VAL_ENTRY_CACHE'. 'JTF. alter tablespace APPS_TS_SUMMARY read only. 'APPLSYS. alter tablespace APPS_TS_NOLOGGING read only. alter tablespace APPS_TS_TX_INTERFACE read only. alter tablespace OLAP read only.ZPB_DC_VAL_RESULTS_GT'. 'MSC.log tables=( 'ZPB. 'GL. alter tablespace OWAPUB read only. 'AK.sql REM REM Ensure that you have no Apps processes running REM before running this script REM connect / as sysdba.dat CONVERT TABLESPACE APPS_TS_ARCHIVE. 'APPLSYS. alter tablespace PORTAL read only. 'WSH. 'APPS. …… Similar global temporary tables …… 'WSH. alter tablespace APPS_TS_TX_DATA read only.JTFB_TEMP_BIN'.AD_PROCESSED_FILES_TEMP'. APPS_TS_MEDIA.IEC_TC_TZ_PAIRS_CACHE'.log=expgtab.MSC_SOURCING_TRANSACTIONS'. alter tablespace APPS_TS_MEDIA read only.IEC_TZ_MAPPING_CACHE'. alter tablespace APPS_TS_TX_IDX read only.WSH_TMP'. alter tablespace APPS_TS_ARCHIVE read only. APPS_TS_TX_DATA. APPS_TS_QUEUES. alter tablespace SYNCSERVER read only. 'APPS. APPS_TS_SUMMARY. APPS_TS_SEED. 'APPS. 77 .WSH_REGIONS_GLOBAL'. APPS_TS_NOLOGGING. 'MSC.

dbf'.'/db/trudata/tx_data4. '/oracle/EBS/visdata/odm.dbf'. '/oracle/EBS/visdata/tx_idx11. '/oracle/EBS/visdata/tx_idx4.dbf'.dbf'.'/db/trudata/reference1. '/oracle/EBS/visdata/media1.dbf'. '/oracle/EBS/visdata/tx_idx1.dbf'.'/db/trudata/queues2.dbf'.dbf'. 78 .dbf'.'/db/trudata/apps_ts_tx_interface. '/oracle/EBS/visdata/tx_data6.'/db/trudata/odm.dbf'.'/db/trudata/portal. '/oracle/EBS/visdata/tx_data2.'/db/trudata/summary4.dbf'.dbf'.dbf'.dbf'. '/oracle/EBS/visdata/summary3. '/oracle/EBS/visdata/reference1.dbf'.dbf'.dbf'.'/db/trudata/tx_data7. SYNCSERVER TO PLATFORM 'HP-UX IA (64-bit)' DB_FILE_NAME_CONVERT '/oracle/EBS/visdata/archive1.dbf'.'/db/trudata/tx_idx7.'/db/trudata/tx_idx6.dbf'.dbf'.dbf'.dbf'.'/db/trudata/queues1. '/oracle/EBS/visdata/tx_idx9.'/db/trudata/tx_data9.dbf'.dbf'.'/db/trudata/tx_idx9.'/db/trudata/owa1.dbf'. '/oracle/EBS/visdata/tx_idx2.dbf'. '/oracle/EBS/visdata/owa1.dbf'. '/oracle/EBS/visdata/summary4.'/db/trudata/tx_data3.dbf'.dbf'.dbf'.'/db/trudata/tx_idx5.dbf'.dbf'. '/oracle/EBS/visdata/tx_data7.dbf'. '/oracle/EBS/visdata/tx_data5. '/oracle/EBS/visdata/tx_idx3.dbf'.'/db/trudata/media2.dbf'. '/oracle/EBS/visdata/summary1.dbf'. '/oracle/EBS/visdata/tx_data11.'/db/trudata/olap.dbf'. OLAP.dbf'.dbf'. '/oracle/EBS/visdata/tx_idx7. '/oracle/EBS/visdata/tx_data9.dbf'. '/oracle/EBS/visdata/tx_idx5.dbf'. '/oracle/EBS/visdata/tx_idx8.dbf'.'/db/trudata/tx_data10. '/oracle/EBS/visdata/reference2.dbf'. OWAPUB.dbf'.'/db/trudata/summary1. '/oracle/EBS/visdata/nologging1.'/db/trudata/tx_idx3. PORTAL.dbf'.'/db/trudata/tx_data6.'/db/trudata/media1.dbf'.dbf'.dbf'. '/oracle/EBS/visdata/tx_data10.dbf'.dbf'.'/db/trudata/tx_data1.'/db/trudata/media3. '/oracle/EBS/visdata/portal.dbf'.dbf'. '/oracle/EBS/visdata/media3.dbf'.'/db/trudata/tx_idx1.'/db/trudata/archive2. '/oracle/EBS/visdata/tx_idx10.dbf'.'/db/trudata/tx_idx2.dbf'.dbf'. '/oracle/EBS/visdata/tx_data3.'/db/trudata/tx_idx11.'/db/trudata/summary3.dbf'.dbf'.'/db/trudata/tx_data8. '/oracle/EBS/visdata/apps_ts_tx_interface.'/db/trudata/nologging1.'/db/trudata/tx_idx10.dbf'.dbf'.'/db/trudata/summary5. '/oracle/EBS/visdata/summary5.'/db/trudata/tx_data5. '/oracle/EBS/visdata/mobile01.dbf'.dbf'.dbf'.dbf'.'/db/trudata/tx_idx4.dbf'.'/db/trudata/tx_data11.dbf'. '/oracle/EBS/visdata/archive2.dbf'.dbf'.dbf'. '/oracle/EBS/visdata/tx_data8.dbf'.'/db/trudata/mobile01.dbf'.dbf'.dbf'.'/db/trudata/tx_data2. '/oracle/EBS/visdata/queues2.dbf'. '/oracle/EBS/visdata/tx_data1.dbf'. '/oracle/EBS/visdata/tx_data4.'/db/trudata/reference2.dbf'.dbf'.dbf'.dbf'.dbf'.'/db/trudata/summary2. '/oracle/EBS/visdata/summary2.'/db/trudata/tx_idx8.dbf'. '/oracle/EBS/visdata/queues1.dbf'. '/oracle/EBS/visdata/tx_idx6. ODM.dbf'. '/oracle/EBS/visdata/media2.dbf'.dbf'. '/oracle/EBS/visdata/olap.'/db/trudata/archive1.APPS_TS_TX_INTERFACE.dbf'.

'/oracle/EBS/db/apps_st/data/olap. '/oracle/EBS/db/apps_st/data/portal.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/tx_data8.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/tx_idx8.dbf'. '/oracle/EBS/db/apps_st/data/odm.dbf'. '/oracle/EBS/db/apps_st/data/tx_data6.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/media1. '/oracle/EBS/db/apps_st/data/apps_ts_tx_interface. '/oracle/EBS/db/apps_st/data/archive2.dbf'. '/oracle/EBS/db/apps_st/data/media2.dbf'. '/oracle/EBS/db/apps_st/data/tx_data3.dbf'. '/oracle/EBS/db/apps_st/data/reference1. '/oracle/EBS/db/apps_st/data/tx_data5. '/oracle/EBS/db/apps_st/data/tx_data10.dmp logfile=impxtts.auimpxtts. '/oracle/EBS/db/apps_st/data/summary4. '/oracle/EBS/db/apps_st/data/summary1.dbf'. '/oracle/EBS/db/apps_st/data/tx_idx3. '/oracle/EBS/db/apps_st/data/tx_idx4.dbf'.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/archive1.dbf'. '/oracle/EBS/db/apps_st/data/tx_idx1.dbf'. '/oracle/EBS/db/apps_st/data/tx_idx10.dbf'.dbf'.log transport_datafiles= '/oracle/EBS/db/apps_st/data/mobile01. '/oracle/EBS/db/apps_st/data/media3. '/oracle/EBS/db/apps_st/data/tx_idx9. '/oracle/EBS/db/apps_st/data/tx_data7. '/oracle/EBS/db/apps_st/data/tx_idx7. '/oracle/EBS/db/apps_st/data/summary3.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/queues1.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/tx_data9. '/oracle/EBS/db/apps_st/data/summary2. '/oracle/EBS/db/apps_st/data/reference2.dbf'.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/tx_data1.dbf'. '/oracle/EBS/db/apps_st/data/tx_idx5.dbf'.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/tx_idx6.dbf'.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/owa1.dat directory=dmpdir dumpfile=xttsmeta01.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/tx_idx2. '/oracle/EBS/db/apps_st/data/summary5. '/oracle/EBS/db/apps_st/data/tx_data11. '/oracle/EBS/db/apps_st/data/tx_data2.dbf' 79 . '/oracle/EBS/db/apps_st/data/tx_idx11.dbf'.dbf'.dbf'.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/nologging1. '/oracle/EBS/db/apps_st/data/tx_data4.dbf'.dbf'. '/oracle/EBS/db/apps_st/data/queues2.

OLAP:SYSTEM. APPS_TS_SEED:SYSTEM.dmp filesize=1048576000 full=y log=impgtab. 80 . PORTAL:SYSTEM.dat file=gtab. ODM:SYSTEM. alter tablespace APPS_TS_SEED read write.dmp full=y logfile=impmsc. APPS_TS_SUMMARY:SYSTEM. alter tablespace APPS_TS_SUMMARY read write.dmp full=y logfile=impsys. alter tablespace APPS_TS_MEDIA read write.dat directory=dmpdir dumpfile=xttsmsc01. APPS_TS_QUEUES:SYSTEM. APPS_TS_TX_INTERFACE:SYSTEM. alter tablespace APPS_TS_QUEUES read write.log EXCLUDE=PROCOBJ remap_tablespace= APPS_TS_ARCHIVE:SYSTEM.log auimpglb. alter tablespace APPS_TS_NOLOGGING read write. alter tablespace APPS_TS_TX_INTERFACE read write. APPS_TS_NOLOGGING:SYSTEM. alter tablespace ODM read write.auimpmsc. alter tablespace APPS_TS_TX_DATA read write. OWAPUB:SYSTEM. alter tablespace APPS_TS_ARCHIVE read write.dat directory=dmpdir dumpfile=xttssys01. APPS_TS_MEDIA:SYSTEM. alter tablespace APPS_TS_TX_IDX read write. APPS_TS_TX_DATA:SYSTEM.log auxttswrite. APPS_TS_TX_IDX:SYSTEM.sql REM REM Ensure that you have no Apps processes running REM before running this script REM connect / as sysdba. SYNCSERVER:SYSTEM auimpsys.

DEQUEUE =>TRUE).AQ_EVENT_TABLE_Q'. exit.start_queue(queue_name =>'SYS. DEQUEUE =>TRUE). DEQUEUE =>TRUE).ENQUEUE =>TRUE. auque2. ALTER USER JA DEFAULT TABLESPACE APPS_TS_TX_DATA. DEQUEUE =>TRUE). ALTER USER OKC DEFAULT TABLESPACE APPS_TS_TX_DATA.ENQUEUE =>TRUE.start_queue(queue_name =>'SYS. audeftbsp.ENQUEUE =>TRUE.ENQUEUE =>TRUE.start_queue(queue_name =>'SYS.ENQUEUE =>FALSE. ALTER USER WIRELESS DEFAULT TABLESPACE SYSTEM. exec dbms_aqadm.ENQUEUE =>TRUE.AQ$_ALERT_QT_E'. ALTER USER PTG DEFAULT TABLESPACE SYSTEM. exec dbms_aqadm. exec dbms_aqadm. ALTER USER PRP DEFAULT TABLESPACE APPS_TS_TX_DATA.start_queue(queue_name =>'SYSTEM. 81 .DEF$_AQCALL'. ALTER USER DDD DEFAULT TABLESPACE APPS_TS_TX_DATA. exec dbms_aqadm.ALERT_QUE'. …… exec dbms_aqadm.out.SYS$SERVICE_METRICS'.DEF$_AQERROR'. PORTAL read write. ALTER USER GMF DEFAULT TABLESPACE APPS_TS_TX_DATA. DEQUEUE =>TRUE). exec dbms_aqadm. DEQUEUE =>TRUE). OWAPUB read write.start_queue(queue_name =>'SYS. exec dbms_aqadm. exec dbms_aqadm. DEQUEUE =>TRUE).ENQUEUE =>TRUE. DEQUEUE =>TRUE).ENQUEUE =>TRUE. exec dbms_aqadm.SRVQUEUE'. SYNCSERVER read write.start_queue(queue_name =>'JTF.AQ_SRVNTFN_TABLE_Q'.JTF_STAGING_MSG_QUEUE'. …… ALTER USER HRI DEFAULT TABLESPACE APPS_TS_TX_DATA.ENQUEUE =>TRUE.sql connect / as sysdba. ALTER USER ODM DEFAULT TABLESPACE ODM. DEQUEUE =>TRUE).start_queue(queue_name =>'SYSTEM.sql spool auque2.alter alter alter alter tablespace tablespace tablespace tablespace OLAP read write.start_queue(queue_name =>'SYS. ALTER USER AD_MONITOR DEFAULT TABLESPACE SYSTEM.start_queue(queue_name =>'SYS.

Step 1 (OKS_VALIDATE_GCD) Service Contracts. Step 2 (IBY_SEC_UPGRADE) Depot Repair. Step 1 (IBY_WALLET_SETUP) iPayment. Step 5 (PER_RIW_WINRUNNER) Appendix E: Reducing Downtime Service Contracts. Step 1 (JAI_CHECK_PA_CUST) Human Resources. Step 1 (CSD_DATA_CHECK) Service Contracts. Step 1 (JAI_CHECK_CUST) Internet Expense. Step 1 (OKS_R12_MIGRATE) 82 . Chapter 2: Preparing for the Upgrade Application Object Library. Step 3 (FND_WORKFLOW_TASKS) Marketing.Appendix E: Oracle E-Business Suite R12 Upgrade Report (TUMS) – VIS Please review the following example of TUMS Report: Unnecessary steps Based on the analysis of your installation. Step 2 (OKS_VALIDATE_RULE) Chapter 4: Post-Upgrade Tasks iPayment. Step 1 (AMS_OSO_PLM_CHK) Incentive Compensation. Step 1 (FND_ENABLE_MULTI_ORG) Application Object Library. it has been determined that you do not need to perform the following upgrade steps. Step 1 (CN_PAYRN_REP_CHK) Oracle Financials (India). Step 3 (IBY_REMIT_ADV_CONTROL_IT) Oracle Financials (India). Step 1 (OIE_IMPORT_INTERCOMPANY_CHECK) iPayment. You may safely omit carrying out these steps from the Upgrading Oracle Applications Release R12 manual during your upgrade.

1 Upgrade Phase 4: Upgrading to E-Business Suite Release 12.1 About Oracle E-Business Suite DBA Minipack 11i.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.1 Oracle 10gR2 Database Preparation Guidelines for E-Business Suite Release 12.1 Database Initialization Parameters and Configuration for Oracle Applications Release 11i 165195.I 761570.1.1 Oracle E-Business Suite Readme.5.0) 396009.2 Maintenance Pack Installation Instructions 248857. Several additional notes were also included for your convenience.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 10gR2 165195.AD.2 Phase 5: Upgrading Oracle RDBMS to 11gR2 1058763.1 Remove Oracle Portal 3.1.1 Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i Phase 3: Migrating to E-Business Suite Release 12.9 from E-Business Suite 11i Phase 2: Migrating 10gR2 DB to target HP-UX Integrity platform 762891.1 Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12 83 .1.1 Oracle E-Business Suite Tablespace Model Release 11i – Tablespace Migration Utility Phase 1: Upgrading the Source database to 10gR2 362203.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.1 Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i 233436. Preliminary phase: 316365.1.1 Installing Oracle E-Business Suite Server 10g with Oracle Applications Release 11i 312349.0.10.1 Database Initialization Parameter Settings for Oracle Applications Release 12 387859.1 Upgrading Developer 6i with Oracle E-Business Suite 11i 216205.1 Interoperability Notes Oracle E-Business Suite Release R12 with Oracle 11g Release 2 (11.2 949406.1 233044.2.1.2.1) for HP-UX Itanium 369693. Release 12.0) 125767.1 Oracle Applications Release 11.Appendix F: Recommended Oracle Support Portal documents This list enumerates the Oracle Support Portal documents that are explicitly referenced in the above documentation of the platform migration and E-Business Suite upgrade process.

<domain name>:<HTTP port>/forms/frmservlet 7. Concurrent Manager check. Make sure your Database and Database Listener is up and running 2. http://<host name>.<domain name>:<HTTP port>/oa_servlets/AppsLogin or http://<host name>. Make sure that all the Middle Tier Services are up and running using AD Scripts located at $INST_TOP/admin/scripts e. Cross check if OA CORE services are working or not? a) http(s)://<host><domain>:<port>/OA_HTML/ServletPing b) http(s)://<host><domain>:<port>/OA_HTML/OA.conf 4. any exception/error will be shown in red color.jsp Execute each step. $sh adopmnctl. try login as: http://<host name>. 8. This should launch Forms Applet in J2SE Plug-in b) Directly launching Forms Applet. Cross check if Oracle HTTP Web Server is serving the HTTP requests: http(s)://<hostname>.jsp 6. Form Server check a) Select any Forms based responsibility from user home page (SSWA Home Page.3/Apache/Apache/conf/httpd.jsp?OAFunc=OAHOMEPAGE 5. a) Login as System Administrator. If you are using load balancer or Proxy Server in front of Web Server then use the load balancer / Proxy Server Name and port on which Oracle HTTP Web Server is listening. OAHOMEPAGE). b) Navigate to Concurrent request and submit “Active Users” concurrent request to check if requests are getting executed.<domain name>:<HTTP Port> Where <hostname>. Login check.sh status 3.<domain name>:<HTTP port>/OA_HTML/AppsLocalLogin. Application Object Library and Java Access and execute the full AOL/J test with http(s)://<host><domain>:<port>/OA_HTML/jsp/fnd/aoljtest. (Conditional) Check AOL/J Health i.g.<domain name> is Machine Name on which Oracle HTTP Web Server is running. 84 .e. Select "Administer Concurrent Manager" and check if "Actual" and "Target" are same. This information is configured in $ORA_CONFIG_HOME/10.Appendix G: Validate the E-Business Suite environment Execute the following steps to validate your E-Business Suite environment: 1.1.

fsc. 85 .object_type from dba_objects where status='INVALID' group by object_type. b) In the forms-based Applications.concurrent_queue_id(+) order by COMPONENT_STATUS .9. Cross check if iHelp is working or not? a) In the SSWA Home Page.fsc. SQL>Select count(*) from dba_objects where status='INVALID'. 12. Workflow Check: Login to OAM (Oracle Application Manager). click on the "Help" icon at the top of the screen. check if you can see report in PDF format. fnd_svc_components fsc where fsc. count(*) from dba_objects where status = „INVALID‟ group by owner. Invalid Objects (Post Patch/Upgrade): SQL>select owner. COMPONENT_NAME.concurrent_queue_id = fcq. SQL>select count(object_type). click on the "?" icon on the toolbar and also select the "Help -> Oracle Applications Library" option from the menu bar. 10. Workflow status: SQL>select fsc.COMPONENT_NAME. Submit Active Users request and click on Output. Reports Server check: Change "Active Users" reports output from "Text file" to "PDF" from Define Concurrent Request Screen. on top right of page from "Navigate to" select "Workflow Manager" from the drop down menu and click on GO button. STARTUP_MODE . 13.FND_CONCURRENT_QUEUES_VL fcq. 11.COMPONENT_STATUS from APPS. Check if "Notification Mailers" is up. then test the search utility by searching for a common keyword such as "form".STARTUP_MODE.

Part # E14010-01 Oracle E-Business Suite Installation Guide: Using Rapid Install Release 12.S. The information contained herein is subject to change without notice.5.com/?jumpid=reg_R1002_USEN Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.S.1).www2. and other countries.hp.For more information HP Integrity server product information site: http://www.www3.com/go/bladesystems HP Storage information site http://www.Maintenance Part # E12894-02 Oracle E-Business Suite System Administrator's Guide .2) for HP-UX Itanium.1. Inc.com/go/hpux HP AlphaServer systems running Tru64 UNIX product information site: http://h30097. Part # B19297-01. Oracle and Java are registered trademarks of Oracle and/or its affiliates.1.html. 4AA2-0266ENW.2) for HP-UX Part # E17880-01 To help us improve our documents.1 Part # E12841-02 Upgrading Oracle Applications Release 11i (11. Microsoft and Windows are U.com/go/storageworks HP-UX 11i v3 product information site: http://www.2).hp. Nothing herein should be construed as constituting an additional warranty.hp.Security Part # E12843-03 Oracle E-Business Suite Concepts R12.com/go/integrity HP BladeSystem product information site: http://www. Part # B28310-04 Oracle Database Installation Guide 10g Release 2 (10.1. AMD is a trademark of Advanced Micro Devices. Created June 2008.1 Part # E12842-04 Oracle E-Business Suite Maintenance Procedures Part # E13675-02 Oracle E-Business Suite Maintenance Utilities Part # E13676-02 Oracle E-Business Suite Patching Procedures Part # E12148-02 Oracle E-Business Suite System Administrator's Guide – Configuration Part # E12893-02 Oracle E-Business Suite System Administrator's Guide .10.2) for hp Tru64 UNIX Part # B25300-01 Oracle Database Quick Installation Guide: 11g Release 1 (11. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. 2011 Hewlett-Packard Development Company. © Copyright 2008. L.2).P.1). UNIX is a registered trademark of The Open Group. Part # E1824502 Oracle Database Installation Guide 11g Release 2 (11. registered trademarks of Microsoft Corporation. Rev.hp.hp. Part # E10819-02 Oracle Database Administrator‟s Guide: 11g Release 1 (11.hp. 1 . Oracle Database Upgrade Guide: 11g Release 1 (11. HP shall not be liable for technical or editorial errors or omissions contained herein. please provide feedback at http://h20219. Intel and Itanium are trademarks of Intel Corporation in the U. Part # B28300-03 Oracle Database Upgrade Guide: 11g Release 2 (11. Updated March 2011.

Sign up to vote on this title
UsefulNot useful