11i Upgrading Oracle Applications - Section 5: Final tasks and release of the instance.

1. Verify invalid objects.

Compare the present list of invalid objects with the one before the upgrade.

select owner, object_type, object_name from dba_objects A where status='INVALID' and not exists (select null from apps.invalids_before_upgrade B where a.object_name = b.object_name);

2. Run autoconfig.

Do run first adchkcfg.sh (check section 1, step 7) and take care of the customizations first before running autoconfig. Review Note 165195.1.

3. Change password policy control.

If you had change the profile option SIGNON_PASSWORD_HARD_TO_GUESS in the pre update tasks to 'N', then set it to 'Y' again.

4. Place the database in archive log mode.

sqlplus "/ as sysdba"
Shutdown immediate;
startup mount
alter database archivelog;
archive log list
alter database open;

5. Disable Maintenance mode, using adadmin.

6. Bring all the Oracle Applications services and perform health-checks.

Troubleshoot any issues, which you would encounter. If you encounter an issue which existing even before the upgrade, then upgrade shouldn't have brought that issue.

7. Backup.

Once you have satisfied with the health-checks, then you can bring the instance down and take a backup. Normally it is a practice to take a backup after the upgrade, to have a state of the instance (just after the upgrade) in hand.

8. Release the instance.

Bring up the services and release the instance.

All the other steps given below can be performed after the instance is released.

9. Drop MRC Schema .

The schema for Multiple Reporting Currencies (MRC) is no longer used. AutoPatch and the AD Administration utility recognize this fact and no longer maintain it. 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/ @addrpmrc.sql SAFE

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

10. Run the "Gather schema statistics" concurrent request.

11. Apply latest consolidated online help patch.

Apply the US version of the Patch 3275245, followed by the NLS (which you are using) version of the patch. NLS version of Patch 3275245. is only required, if you require online help in that language.

12. Run the "Rebuild Help Search Index" concurrent request.

You have now completed all the steps related to upgrade. You should now monitor and attack any issues, which the users are reporting. If this is a test upgrade, you should note down all the issues encountered and try to tackle them proactively during the next iteration of the upgarde or while doing it on PROD instance. Once you get a confirm from the testing team that everything is good, you can remove all the patches downloaded and log files.