1

AWC : PANASONIC EBS UPGRADE 11.5.10.X TO 12.1.X DBA STEPS AND CHECK LIST

UPGRADE ORACLE APPS (EBS) TO R12 (12.1.3) FROM 11.5.10.2

Existing Architecture We have a single node instance, here are the details: Operating System Oracle Application Oracle Database Linux x86 11.5.10.2 Oracle9i Enterprise Edition Release 9.2.0.5.0 - Production

Final Architecture OS Users names have been retained as in production. New directories have been created for R12 upgraded file system. Rest remains as it is.

2 Phase: First (Prepare Existing system for upgrade to R12) Step 1 Apply 11i.AD.I patch. The most current version of this minipack is 11i.AD.I.7 and ptach Number is 7429271 Step 2 Run TUMS Utility Patch Number 6727612 and apply it to the administration server node on your Release 11i APPL_TOP. It supplies you with the script (adtums.sql) you need to generate the TUMS report (tumsr12.html). Generate the TUMS report. UNIX: $ cd $AD_TOP/patch/115/sql $ sqlplus <APPS username>/<APPS password> @adtums.sql <DIRECTORY> For the <DIRECTORY> value, enter the full path of the directory that you want the report to be written to. This directory must be listed in the UTL_FILE_DIR parameter of the init.ora file before TUMS can write the report and must have the appropriate WRITE permissions. Review the report. The tumsr12.htm report lists the steps (identified by the TUMS step key in this book) that do not apply to your installation. You may safely ignore any steps listed in this report. Step 3 Back up database, Applications, and customizations (recommended) Make a cold backup of the Oracle Applications database. You can use it to restore the database should you encounter problems during the upgrade process. Step 4 Prepare an upgrade plan for customizations (conditional) Rename any custom database objects with Applications prefixes that you have created so that they do not conflict with Oracle object names. At your discretion, and depending on the customizations in your system, you should also perform the following tasks: Preserve the CUSTOM library by making a backup copy of CUSTOM.pll. You can use this copy later in the upgrade process to migrate your CUSTOM library to Release 12.0.4.

3 If you have customized forms with Oracle Forms 6i, upgrade them to Oracle Forms 10i after the upgrade. Step 5 Convert to Multiple Organizations architecture (Functional Task) : Not Applicable Multiple Organizations architecture supports performance improvements across all Oracle Applications. It also supports Multiple Organizations Access Control, which enables an Applications responsibility to access multiple operating units if desired. This release requires that Multiple Organizations be enabled. If you have not done so already, you must convert to this architecture now. Converting to Multiple Organizations does not require the use of multiple operating units or sets of books it does enable you to use this functionality at any time in the future. If you are converting from a Single Organization architecture to a Multiple Organization architecture, complete the following steps: 1. Create an operating unit. 2. Assign the operating unit you created to the profile option MO:Operating Unit. Step 6 Drop event alert triggers in custom schemas (conditional) To drop all event alert database triggers in custom schemas, run the alrdtrig.sql script, located in $ALR_TOP/admin/sql (in your Release 11i system). Re-create the triggers after the upgrade is complete. Step 7 Review sizes of old and new tablespaces Step 8 Run AD preparation scripts To prepare your system for the Oracle Applications Tablespace Model (OATM) functionality, you must run some preparation scripts. Download and unzip patch 7197489. Follow the instructions in the readme for running these scripts: adgncons.sql The tablespace model for this release (OATM) is based on database object type rather than product affiliation. The adgncons.sql script prepares adcrtbsp.sql, configures the database to hold the new products to be added during the upgrade, and switches your system to use the new tablespace model. adcrtbsp.sql

4 Generated by adgncons.sql, this script creates the new tablespaces, allocates unlimited tablespace to all APPS users, updates fnd_product_installation table with correct data and index tablespace information, assigns default tablespace to all APPS users, and sets the new_ts_mode flag in fnd_product_groups to Y. adgrants.sql (adgrants_nt.sql for Windows) Grants SYS privileges needed by Applications, and creates required views in SYS. Step 9 Gather schema statistics for CBO (required) Step 10 Back up the database (recommended) Step 11 Disable AOL Audit Trail (conditional) If you use the Oracle Applications Object Library Audit Trail feature, you must disable it before the upgrade. From the System Administrator responsibility under the 11i APPL_TOP, navigate to Security > Audit Trail > Groups. In the Audit Groups window, set the Group State field to Disable - Prepare for Archive for each audit group defined. Run the Audit Trail Update Tables report from the Submit Requests window (Requests > Run). If you plan to re-enable auditing after the upgrade, archive and purge the shadow tables now. Data changes made after implementing this step are not audited. Step 12 Disable custom triggers, constraints, and indexes (conditional) Disable custom triggers or constraints on Oracle Applications tables. Re-enable these triggers after the upgrade. If you have custom indexes on Applications tables, determine whether they can affect performance during the upgrade, and drop them if necessary. If you are not sure, it is best to drop the indexes and add them after the upgrade, if the new release has not created a similar index. Step 13 Drop MRC schema (conditional) All programs and reports now use the APPS schema. Because the MRC_APPS schema is no longer needed, dropping it frees space and reduces processing overhead during the upgrade. If you have not previously done so, drop the MRC schema now. Step 14 Down the database and Application Service completely.

Step 15 Apply Patch set 7 to upgrade database from 9.2.0.5 to 9.2.0.8 (Patch 4547809)

Step 16 Apply latest timezone patch y Apply Patch 5632264 by using OPATCH utility

Step 17 Create SYSAUX tablespace Step 17 finally takes the backup of DB_TOP and DATA_TOP

Phase- Two (Upgrade the Database to Oracle 11g Release 1) Step 1 We must use oracle 11g software, which is laid down by R12 Setup a) Connect to the oracle database form 9i and run pre-upgrade Information tool scripts (utlu111i.sql), which is store in Oracle 11 g Home/rdbms/admin. b) Follow the steps suggested from output of above steps. Step 2 Shutdown database. Step 3 Copy init file from 9i default directory to 11G default directory Step 4 Connect to the new oracle 11g instance as a user sysdba privilege and issue following command: SQL>STARTUP UPGRADE You dont need to use the PFILE option to specify the location of your initialization parameter file in our case because we are using INIT file in default location (which is reside in Oracle10gHome/database). We have just put init file at new oracle 10g home from 9i.

6 The error may be occur, when you attempting to start the new oracle Database 10g release. If you receive, issue the SHUTDOWN ABORT commands to shut down the database and correct the problem. Step 5 Set the system to spool results to a log file for later verification of success: SQL> SPOOL upgrade.log Step 6 Run the upgrade scripts. SQL>@catupgrd.sql The catupgrd.sql script determines which scripts need to be run and then runs each necessary scripts. Step 7 Run the result of the upgrade display report. SQL>@utlu111s.sql The Post-upgrade status Tool display the status of the database components in the upgrade database and time required to complete each component upgrade. Step 8 Turn off the spooling of script result to the log file SQL>spool off; Step 9 Shutdown the instance and restart. SQL> STHTDOWN IMMEDIATE SQL> STARTUP Step 10 Check Invalid objects in database by using following Query: Step 11 Run utlrp.sql scripts to recompile any remaining stored Pl/SQL and java codes. SQL > @utlrp.sql

7 Step 12 Update init.ora with upgrade parameters (required) Database Initiation Parameter for EBS Release 12 (396009.1) Initialization parameters required at each stage of an upgrade may vary depending on when you upgrade your database. Set the appropriate parameters now. Phase- Three (Install Upgraded R12 file system) Step 1 Run Rapid Install (R12) from media.