Install Oracle R12 software for Apps Upgrade

1. Create the new base directory (directories)

on the apps tier as root:

mkdir /APPS_MI_R12

chown applmgr:applmgr  /APPS_MI_R12

2. Install the R12 software

run the Oracle Installer as applmgr user:

cd /media/usbdisk/12i_APPS_Stage/startCD/Disk1/rapidwiz

./rapidwiz

Click on "Next".

Choose "Upgrade to Oracle Applications Release 12" . Click on "Next".

Accept the Agreement. Click on "Next".

Enter the CSI number, your Metalink account and the Country you work in. Click on "Next".

Choose "Create Upgrade File System". Click on "Next".

Choose the global system settings. Click on "Next".

Enter DB node information. Click on "Next".

Click on "Next".

Choose the Internalizations settings. Click on "Next".

Enter Apps node information. Click on "Next".

Click on "Next".

Click on "Next".

Click on "Next".

Click on "Next".

Click on "Finish".

Configure the Maintenance Wizard for Upgrade

1. Login as Upgrade Engineer User

2. Select a Category

3. Complete configuration of Maintenance Wizard

4. Enable remote access of the Applications database

5. Filter steps

6. Generate patch list and dynamically create pre-upgrade patching steps

7. Configure the Maintenance Wizard: status

1. Login as Upgrade Engineer User

   a) Login as Upgrade Engineer User

   b) Choose the Project you want to view:

2. Select a Category

Select the "Configuration" Category. 

The following screen will appear:

3. Complete configuration of Maintenance Wizard

Click on the "Execute" button for the first task. The following screen will appear:

Click on "Run" button. 

When the job complete you must see the following message at the end of the log information:

*******************************************************************************
*******************************************************************************
**                                                                                                                 **
**                                   Congratulations!!!                                                 **
**                                                                                                                 **
**      You have successfully completed project node configuration.         **
**                                                                                                                 **
*******************************************************************************
*******************************************************************************

If you have any errors please fix them and redo this run ( from Redo the Action button) and run this job again.

NOTES: 

    1) For this step please define utl_file_dir database initialization parameter;

    2) Check if $APPL_TOP/patch (on the apps node)  and  $ORACLE_HOME/patch (on the database node) are created. 

4. Enable remote access of the Applications database

  a) Check if the database of the Oracle Applications 11i and the database listener are running. If there are not started, start them. 

  b) Click on the "Execute" button for the 2nd task. Click "Run". 

  c) At the end of the job the following message must be at the end of the log information:

Successfully created a database link named REMOTE_1597
Testing it now...
Test of database link succeeded.

PL/SQL procedure successfully completed.

Successfully completed enabling remote access of the Applications database.

   d) Click on "Complete" button, and after that on "Success" button. 

5. Filter steps

This step runs filtering routines against the content of the upgrade instructions. The results of this step are used in determining what steps to display in the tool, and what steps to suppress or mark as automatically completed.

If the following message will appear in the log information "Found that at least one of Student Systems, Student Recruiting and/or  Financial Aid products is installed! Setting this project back to  DATA COLLECTION COMPLETE to prevent continuation of this upgrade.", only in a test environment you can force to fix the error by updating the fnd_product_installations table:  

update fnd_product_installations set status = 'N' where application_id in (8406, 8405);

commit;

If this step complete successfully, you will see the following message at the end of the log information:

Checking to see if Student Systems or Student Recruiting are installed...
Neither Student System nor Student Recruiting are installed.
It is safe to proceed with the Release 12 upgrade.
Successfully performed all filtering routines.

6. Generate patch list and dynamically create pre-upgrade patching steps

This step loads only relevant patches into EOF_REQUIRED_PATCHES, based on the upgrade from version and the product filter built in a previous step. It then queries the Applications database to determine the list of patches which have already been applied and flags the appropriate records in EOF_REQUIRED_PATCHES, by updating the APPLIED_FLAG. Finally, it dynamically generates steps in the 11i Pre-Upgrade Category for downloading, merging and applying those patches.

This step will contains in the log information the following message:

Creating 1 merge step(s).
Creating the Compilation step.
Creating the Verification step.
PL/SQL procedure successfully completed.
Completed execution of eof17208e.sh.

7. Configure the Maintenance Wizard: status

If the Maintenance Wizard complete the configuration successfully, you can see the following screen:

Prepare the Maintenance Wizard for Upgrade

1. Create a new Customer

2. Create a new Project

3. Create a new User

4. Create a Project Administrator

5. Register the nodes for the Project (must be done when APPs R12 software is already installed )

6. Assigning Responsibilities to "Engineers"

1. Create a new Customer (connected as sysadmin)

In the same window we can modify the customer's rights: 

      - Open Access    = full access to the customer 

      - Access Locked = all accesses are locked for the customer 

2. Create a new Project (connected as sysadmin)

In order to upgrade a system, you must create a project. A project is used for a single iteration of an upgrade process. If you have to upgrade 3 systems (test, dev, prod) you have to create 3 projects. 

From "Product" Choose "Upgrade Assistant for Release 12" in order to create an upgrade (from 11i to R12) project. Click on "More Details".

Choose the "Source Version", "Destination Version", the remote EOF_HOME (only the name of the directory; do NOT put the full path here! ) and "Copy Steps from ..." Master. Press "Add" button. 

Now the project is created and some proprieties can be still modified. 

3. Create a new User (connected as sysadmin)

The user information can be changed from the "Edit User" tab. 

4. Create a Project Administrator (connected as sysadmin)

5. Register the nodes for the Project (connected as Project Administrator; in my case p1admin)

Choose the project name from the list. A new screen will appear. Click on "Edit" button. 

Click on "Define Nodes" tab.  The following screen will appear:

Choose a method for defining NodeType(s). Me I will choose "Read from AutoConfig". The "Administration Node Autoconfig Setup" page will appear:

Put the correct values (the database node is not chosen) and click "Next".

Repeat this step for the database node too. After that edit the Database node and put the correct SYSTEM and APPS passwords. 

For the R12 node, choose the "Manual config" setup. 

Select the correct values for the specified field and click on Save. 

Press on "Configure" button and "DATA COLLECTION COMPLETE" message will change. The new one will be "CONFIGURATION COMPLETE".

6. Assigning Responsibilities to "Engineers"

Create a new user (named UpgEngineer, in my example) and assign to him all the privileges needed for the upgrade. In my case I will assign all the privileges to the UpgEngineer. In real life, several users are created and the right privileges are assigned to each user by the Project Administrator. 

Connected as Project Administrator, choose the Upgrade Engineer:

 

The following screen will appear (Here I have chosen all the privileges available):

Click on "Save" button to save the new changes.