Guenadi N Jilevski's Oracle BLOG

Upgrading EBS 12.1.1 to latest Oralcle 11g

Upgrading Oracle Applications EBS R12 12.1.1 to latest Oracle RDBMS 11g

Keeping the Oracle database up to the latest version certified with EBS is of paramount importance to ensure that all new performance, manageability, administrative and security features to name a few are available. Upgrading an EBS 12 with the latest release of Oracle conceptually involves the following steps as follows.

• Create a new Oracle home for the latest Oracle 11g release, install the Oracle 11gR1 software. After that, install Oracle 11gR1 database examples from the Oracle Example media. Patch to the latest 11gR1 release. Note as of the time of writing EBS 12.1.1 was not certified with Oracle 11gR2 instead only EBS 11i was certified with Oracle 11gR2.
• Apply inter-operability patches for both EBS application and DB tier.
• Shutdown the application tier and all the listeners and perform a database upgrade, modify init parameters, perform all the patch special instructions and post install tasks. Optionally you can choose to run an EBS PL/SQL database objects in a natively compiled mode with Oracle 11g.
• After the database upgrade start the new listener in the new oracle home. Run adgrants.sql from sqlplus while logged in as sysdba. Run the following command $ sqlplus apps/ @adctxprv.sql CTXSYS where adctxprv.sql is from $AD_TOP/patch/115/sql/adctxprv.sql. Execute sqlplus / @wfaqupfix.sql where wfaqupfix.sql is from $FND_TOP/patch/115/sql/wfaqupfix.sql.
• Implement and run AutoConfig in the new Oracle home on the database server node. If the database listener of the new Oracle home is defined differently than the old Oracle home, you must also run AutoConfig on each application tier server node to update the system with the new listener. Please see Note 387859.1 Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12. Shut down all processes, including the database and the listener, and restart them to load the new environment settings.
• Gather statistics for the sys schema. Connect as sysdba using sqlplus and run the script $APPL_TOP/admin/adstats.sql in restricted mode.

$ sqlplus “/ as sysdba”

SQL> shutdown normal;

SQL> startup restrict;

SQL> @adstats.sql

SQL> shutdown normal;

SQL> startup;

SQL> exit;

• Recreate Demantra privileges note 730883.1
• Re-create custom database links
• Re-create grants and synonyms. Oracle 11g contains new functionality for grants and synonyms compared to previous database releases. As a result, you must re-create the grants and the synonyms in the APPS schema. On the server node, as owner of the application file system, run AD administration and select ‘Recreate grants and synonyms for APPS schema’ from the Maintain Applications Database Objects menu.
• Restart application server processes. Restart all the Application tier server processes that you shut down previously. Remember that the Oracle Net listener for the database instance, as well as the database instance itself, need to be started in the 11.1 Oracle home. Users may return to the system.
• Synchronize Workflow views. Log on to Oracle EBS with the “System Administrator” responsibility. Click Requests > Run > Single Request and the OK button. Enter the following parameters:
• Request Name = Workflow Directory Services User/Role Validation
• p_BatchSize = 10000
• p_Check_Dangling = Yes
• Add missing user/role assignments = Yes
• Update WHO columns in WF tables = No

Click “OK” and “Submit”.

December 13, 2009 - Posted by gjilevski | oracle