Oracle Applications Release Maintenance Pack Installation Instructions

Subject: Oracle Applications Release Maintenance Pack Installation Instructions.

Section 1: Pre-Update Tasks 

The tasks in this section are required. They can be performed at any time prior to the application of this maintenance pack. Complete them in the order listed. 

1. Determine Required Steps (Optional)

Run TUMS-MP by applying patch 4238286 and following the instructions in the associated readme file. Apply the patch on the administration server node. The Upgrade Manual Script for the Maintenance Pack (TUMS-MP) examines your current configuration and creates a report detailing which of the steps in these instructions you must complete and which steps you can ignore. 

2. Apply the AD Minipack

Apply AD Minipack I.2 (4337683The most recent replacement for this patch is 4712852) on all application tier server nodes. You must have implemented AutoConfig to apply this patch. 

3. Update AutoConfig technology stack template by applying patch 4104924 (Superseded by 3480000- ORACLE APPLICATIONS RELEASE MAINTENANCE PACK).

4. Install and run the Technology Stack Validation Utility 

To install the utility, apply patch 4318672 on all application tier server nodes. Follow the instructions in the patch readme file to run the utility. If it reports any failures or warnings, follow the instructions it provides and fix each reported failure. 

5. Configure database for new products and new tablespace requirements

AD patch 3180164 provides scripts and instructions for adding and updating the necessary products and tablespaces. Carefully review the patch instructions. 

6. Change password policy control (conditional)

If the profile option SIGNON_PASSWORD_HARD_TO_GUESS exists with a value of Y, set it to N. You can restore this value to Y after you complete Section 2 of these instructions. 

7. Unzip the American English maintenance pack files.

8. Unzip and merge NLS Maintenance Packs (conditional).

Section 2: Applying the Release Maintenance Pack

In this section, you apply the American English version of the Release Maintenance Pack and the appropriate NLS versions. The downtime associated with the application depends on many factors, such as the speed and configuration of your servers, the number of products you have registered, the number of languages you use, the release from which you are upgrading, and the number of AutoPatch and AD Administration workers you specify.

1. Shut down application tier server processes or services

2. Upgrade the database (conditional) 

If you plan to upgrade to Oracle Database 10g Release 2, we recommend that you complete the upgrade to Oracle Applications Release before you upgrade your database. 

3. Apply the maintenance pack 

Use AutoPatch to apply the u3480000.drv driver from the American English patch. If you have a multi-node system, you must apply the driver on the administration server node first. Then, apply it to all other application tier server nodes, in any order. You were also required to use either AD Administration or AutoPatch (in conjunction with a generate driver) to generate Oracle Forms, Reports, and Graphics files. AutoPatch now performs these tasks automatically. 

Section 3: Post-Update Tasks 

1. Restart server processes or services

Restart all the application tier server processes or services that you shut down at the beginning of Section 2, and any new server processes or services introduced by this maintenance pack. 

2. Apply latest consolidated online help patch

Apply patch 3275245. Unzip the American English version to a temporary location on the administration server node and HTTP server node, and follow the instructions in the readme file to apply it. 

3. Drop MRC Schema

The schema for Multiple Reporting Currencies (MRC) is no longer used. You can safely drop the MRC schema at your convenience, even after users have returned to the system. Remove it by entering the following commands:            

$ cd $APPL_TOP/admin
$ sqlplus SYSTEM/<password> @addrpmrc.sql <APPLSYS USERNAME> SAFE

Depending on your configuration, this script may run for two or three hours.

Section 4: Product-specific Tasks 

Once you have successfully applied this maintenance pack, additional product-specific tasks may be required depending on the products you have registered or plan to register in your system. This section describes all the product-specific tasks. Once you have performed the appropriate tasks, shut down and restart all application tier server processes or services so that the changes take effect.

1. Payables and Receivables

Regardless of whether your system uses multi-org functionality, you should confirm that the profile options were migrated in a manner that meets your business needs. This release includes two reports that compare the pre-migration data with the post-migration data.

For Payables:
Submit the Mini-pack Upgrade Report concurrent program from a Payables responsibility.

For Receivables:
Submit the Profile Option Migration Report concurrent program from a Receivables responsibility.

2. All Products

If you made any system changes based on the information in this section, you must shut down and restart the application tier server processes or services to ensure that the changes take effect.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s