Step 1: Apply AD mini-pack (required)
If you applied the AD mini-pack and associated AD patches in Category 2, you need to apply the same mini-pack and patches now. Note that in Category 2, you applied the mini-pack and patches in pre-install mode to add certain components needed for the upgrade. Now, you must apply them in their entirety (normal mode) to "turn on" new AD functionality.
Step 2: Update database to current Applications release level (required) Additional Information: See Patching Your System in AD
Procedures Guide.
Checklist Performed by
1. Apply AD mini-pack (required) Database Administrator
2. Update database to current Applications release level (required) Database Administrator
3. Install NLS translated software (conditionally required) Database Administrator
4. Update installed and licensed products (required) Database Administrator
5. Install online help (conditionally required) Database Administrator
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator Reference manual: No Requires concurrent manager: No
Note: The AD mini-pack may require that you apply additional AD patches as prerequisite. Review the readme files for both the AD mini-pack and the AD patches for complete instructions.
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator Reference manual: No Requires concurrent manager: No
Apply Updates
To bring your database to the full Oracle Applications Release 11i maintenance level, apply d2123967.drv on the admin server node. This driver is located in $AU_ TOP/patch/115/driver (UNIX) or %AU_TOP%\patch\115\driver (Windows). It is potentially long-running. There is no copy driver or generate driver.
Step 3: Install NLS translated software (conditionally required)
The only language AutoUpgrade installs is American English. If American English is the only active language in your installation, omit this step.
Complete the steps now to install the translated software for each active non-American English language in your installation.
Step 4: Update installed and licensed products (required)
Using OracleMetaLink, determine the latest product-specific patches and updates for your installation, then, download the patches and updates for all active
languages (American English and, if applicable, non-American English) present in your installation. Using AD Merge Patch, merge the American English
patches/updates and apply them to your environment using AutoPatch. Merge the non-American English patches/updates (if any) and apply them to your
environment as well.
Warning: Do not attempt to complete the remaining upgrade steps or run Oracle Applications without first applying the AD minipack and this update.
Additional Information: See Applying Patches in AD Procedures
Guide.
Perform if upgrading from: 10.7, 11.0 with one or more non-American English active languages
Performed by: Database Administrator Reference manual: No Requires concurrent manager: No TUMS Step Key: AD_INSTALL_NLS
Additional Information: See Set up National Language Support (NLS) in Installing Oracle Applications.
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator Reference manual: No Requires concurrent manager: No
Environment Preparation Steps
Step 5: Install online help (conditionally required)
Instructions for installing online help are located in the Finishing your Upgrade chapter of this book. However, you may want to install online help now so that you can reference it for the remaining upgrade steps. For instructions, see Step 2, in Chapter 7. Before you make the decision about when to install help, note that it may take a considerable amount of time to complete this process.
Environment Preparation Steps
All users must complete this portion of the upgrade. Complete these tasks before you perform the Database Upgrade, the Applications Technology, or the
product-specific steps.
Environment Preparation Tasks
Step 1: Run Rapid Install to configure and start server processes (required)
As a pre-upgrade step, you ran Rapid Install to set up the technology stack and create your file system. Now, run Rapid Install to configure and restart the server
Additional Information: See Merging Patches in AD Procedures
Guide.
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator Reference manual: No Requires concurrent manager: No
Checklist Performed by
1. Run Rapid Install to configure and start server processes (required) Database Administrator / System Administrator
2. Configure Applications client software (conditionally required) Database Administrator / System Administrator
3. Reapply customizations (conditionally required) Database Administrator / System Administrator
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator / System Administrator
Environment Preparation Steps
processes. Go to Chapter 4 in Installing Oracle Applications and follow the
instructions beginning with the Configure and Start Server Processes step. When instructed to do so, return here and complete the remaining Category 4 steps.
Step 2: Configure Applications client software (conditionally required)
If your installation uses multiple web servers, you must configure your client software to use the Oracle Java Virtual Machine on each web server before you log on to Oracle Applications for the first time, or run AutoPatch. See Configure Client Software in Installing Oracle Applications for instructions.
Step 3: Reapply customizations (conditionally required)
If you customized Applications environment files (APPLSYS.env or devenv), re-integrate them in the APPL_TOP <SID>.env file, in devenv.env, or in the
adovars.env file $APPL_TOP/admin (UNIX) or %APPL_TOP%\admin (Windows). Restart the application server processes so that the changes take affect.
If your site has customizations to forms, reports, programs, libraries, or other Applications files, reapply the changes that apply to the new release.
Additional Information: See Review Server Process Control Scripts in Chapter 7.
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator / System Administrator Reference manual: No Requires concurrent manager: No
Additional Information: See Complete Guide to JInitiator for Oracle’s
E-Business Suite: Overview, Setup & Troubleshooting (OracleMetaLink
Doc ID: 162488.1) and Upgrading the JInitiator Version used with
Oracle Applications 11i (OracleMetaLink Doc ID: 124606.1).
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator / System Administrator Reference manual need: No
Additional Information: See Managing Server Processes in Chapter 1 of AD Procedures Guide.
Database Upgrade Steps
Database Upgrade Steps
All users must complete this portion of the upgrade. Complete these tasks before you perform the Applications Technology steps or the product-specific steps.
Database Upgrade Tasks
Step 1: Reset ORACLE schema passwords (recommended)
During the upgrade, Rapid Install preserves the passwords that you set previously for existing products. However, as it creates a schema for each new product
installed, it sets up a default password derived from the product short name. To maintain product security, reset these default passwords now. Use the Oracle Users window from the System Administrator responsibility.
Checklist Performed by
1. Reset ORACLE schema passwords (recommended) Database Administrator / System Administrator
2. Gather database statistics for CBO (required) Database Administrator / System Administrator
3. Set rollback segments for normal use (required) Database Administrator
4. Validate and compile APPS schema(s) (required) Database Administrator / System Administrator
5. Integrate custom objects and schemas (conditionally required) Database Administrator / System Administrator
6. Re-enable custom triggers, constraints, and indexes (conditionally required) Database Administrator / System Administrator
7. Back up Oracle Applications (recommended) Database Administrator / System Administrator
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator / System Administrator Reference manual: No Requires concurrent manager: No
Additional Information: See Oracle Applications Schema Password Change Utility in the Oracle Applications System
Database Upgrade Steps
Step 2: Gather database statistics for CBO (required)
You run the Gather Schema Statistics concurrent program (System Administration > Submit Request) to gather database statistics. If the schema name is ALL, then all Apps-specific schema (having an entry in the FND_PRODUCT_INSTALLATIONS table) statistics are gathered. In addition to gathering index and table-level statistics, the procedure also gathers column-level histogram statistics for all the columns listed in the FND_HISTOGRAM_COLS table. This program is potentially
long-running.
Because it is important to have an up-to-date set, gather database statistics periodically to make sure your database queries are optimized.
Step 3: Set rollback segments for normal use (required)
Set your rollback segments for normal operation, typically, 1 for each 25 users, plus 1 for each concurrent manager. Make the maximum extent size 1 MB and the minimum size 60 MB.
Step 4: Validate and compile APPS schema(s) (required)
Before you continue with your upgrade, fix invalid objects in your database. Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator / System Administrator Reference manual: No Requires concurrent manager: Yes
Additional Information: See Cost-based Optimization in Oracle Applications in Oracle Applications System Administrator’s Guide. See also Cost-based Optimization in Oracle Applications Concepts and Introduction to Optimization in Oracle8i Concepts.
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator Reference manual: Oracle8i Administrator’s Guide
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator / System Administrator
Database Upgrade Steps
1. Create list of invalid objects.
From the Maintain Applications Database Objects menu in AD Administration, select the Validate APPS Schema(s) option. Review the output and take
corrective action as indicated in the report.
2. Compile objects in APPS schema.
Select the Compile APPS Schema(s) option to compile all the invalid objects in your APPS schema.
3. Re-generate list of invalid objects and re-compile until there are no more invalid objects.
Step 5: Integrate custom objects and schemas (conditionally required)
If you previously created custom objects or have custom schemas that must be tightly integrated with Oracle Applications, follow the steps in Oracle Applications
Developer’s Guide to re-integrate these customizations with the APPS schema.
Release 11i uses Invoker Rights for most PL/SQL packages. Executing these packages from custom schemas may require additional grants from, and synonyms to, APPS schema objects. We recommend you explicitly declare Invoker Rights or Definer Rights for custom PL/SQL packages. See Oracle8i PL/SQL User’s Guide and
Reference for more information.
Custom database objects must follow the naming standards for custom object names to avoid conflict with Oracle Applications.
Important: MRC users must perform this step. You must correct all
problems in the report and log files before continuing. Failure to do so will result in an incomplete or unusable MRC installation.
Additional Information: See AD Administration in AD Utilities
Reference Guide.
Perform if upgrading from: 10.7, 11.0 Performed by: Database Administrator / System Administrator