This chapter covers the following topics:
This section describes the tasks required to initiate the upgrade process. All the tasks must be performed during the upgrade downtime. The following table provides a checklist of the tasks required in this chapter.
Disable AOL Audit Trail (conditional)
Applies to 11i release level: All
TUMS step key: N/A
If you use the Oracle Applications Object Library Audit Trail feature, you must disable it before the upgrade.
From the System Administrator responsibility under the 11i APPL_TOP, navigate to Security > Audit Trail > Groups. In the Audit Groups window, set the Group State field to Disable - Prepare for Archive for each audit group defined. Run the Audit Trail Update Tables report from the Submit Requests window (Requests > Run).
If you plan to re-enable auditing after the upgrade, then archive and purge the shadow tables now. Data changes made after implementing this step are not audited.
Note: See Audit Trail in Oracle E-Business Suite System Administrator’s Guide - Security.
Shut down application tier listeners and concurrent managers (required)
Applies to 11i release level: All
TUMS step key: N/A
Navigate to Concurrent > Requests. In the Find Requests window, select All my requests. Click Find, and click Cancel Pending requests as necessary. Then, as System Administrator, choose Administer Concurrent Managers. Navigate to the Control field and select Deactivate.
Shut down forms listeners, web listeners, and the concurrent managers before you begin the upgrade. Do this from your Release 11i APPL_TOP.
Migrate database to at least Oracle10g Release 2 (conditional)
Applies to 11i release level: All
TUMS step key: N/A
The upgrade requires at least version Oracle10g Release 2 (10.2.0) database. If you have not done so already, then upgrade or migrate your database now. Follow the instructions in Database Preparation Guidelines for an Oracle Applications Release 12.1.1 Upgrade (Doc ID: 761570.1).
Update init.ora with upgrade parameters (required)
Applies to 11i release level: All
TUMS step key: N/A
Initialization parameters required at each stage of an upgrade may vary depending on when you upgrade your database. Set the appropriate parameters now.
Note: See Database Initialization Parameters in Chapter 1, "Planning for an Upgrade" for specific parameters. See also Database Initialization Parameters for Oracle Applications Release 12 (Doc ID: 396009.1).
Disable custom triggers, constraints, and indexes (conditional)
Applies to 11i release level: All
TUMS step key: N/A
Disable custom triggers or constraints on Oracle E-Business Suite tables. Re-enable these triggers after the upgrade. If you have custom indexes on Applications tables, then determine whether they can affect performance during the upgrade, and drop them if necessary. If you are not sure, then it is best to drop the indexes and add them after the upgrade, if the new release has not created a similar index.
Applies to 11i release level: All
TUMS step key: N/A
All programs and reports now use the APPS schema. Because the MRC_APPS schema is no longer needed, dropping it frees space and reduces processing overhead during the upgrade. If you have not previously done so, drop the MRC schema now.
UNIX:
$ cd APPL_TOP/admin
$ sqlplus <SYSTEM username>/<SYSTEM password> @addrpmrc.sql
<APPLSYS username> FORCE
Windows:
C:\> cd %APPL_TOP%\admin
C:\> sqlplus <SYSTEM username>/<SYSTEM password> @addrpmrc.sql
<APPLSYS username> FORCEBack up the database (recommended)
Applies to 11i release level: All
TUMS step key: N/A
Make a cold backup of the Oracle E-Business Suite database. If you encounter problems during the upgrade process, you can use this backup to restore your system to the same state as before you began the upgrade.
Note: Shut down with the NORMAL option. You may not be able to restore the database from the backup if you use the IMMEDIATE or ABORT option.
Ensure that Maintenance Mode is enabled (required)
Applies to 11i release level: All
TUMS step key: N/A
Maintenance Mode restricts logins and the type of operations that the system can perform. Make sure that Maintenance Mode is enabled before you continue.
From the AD Administration Main Menu, choose the Change Maintenance Mode option.
The Change Maintenance Mode menu displays the current Maintenance Mode status at the top of the screen. The status should be Disabled at this point.
Select Option 1, Enable Maintenance Mode.
Apply AD 12.1.1 upgrade driver (required)
Applies to 11i release level: All
TUMS step key: N/A
Download and unzip the AD Upgrade Driver for 12.1.1 (patch 7461070). Use AutoPatch to run it on all application tier server nodes on your Release 12.1.1 APPL_TOP.
Run the American English upgrade patch driver (required)
Applies to 11i release level: All
TUMS step key: N/A
To bring your database to the full Oracle E-Business Suite Release 12.1.1 level, use AutoPatch to run the (American English) unified driver (u6678700.drv). It is located in $AU_TOP/patch/115/driver.
Run the driver on the administration server node on your Release 12.1.1 APPL_TOP using the following commands:
$ adpatch options=nocopyportion,nogenerateportion
Run the NLS upgrade patch driver (conditional)
Applies to 11i release level: All
TUMS step key: N/A
If American English is the only language that is active in your system, then you can omit this step.
After you have successfully applied the American English unified driver, download the NLS Release 12.1.1 software for each active language in your system, and run each driver (u6678700.drv) on your Release 12.1.1 APPL_TOP. Note that the NLS patch driver has the same name as the American English patch driver.
If you have several languages to download and run, then you can merge the patches and apply them as a single, merged patch.
Note: See Oracle E-Business Suite NLS Release Notes for your release level for more information. See also Oracle E-Business Suite Patching Procedures for information about merging NLS patches.
Apply latest product patches (required)
Applies to 11i release level: All
TUMS step key: N/A
Determine the latest product-specific patches. Then, download the American English patches. Using AD Merge Patch, create a merged patch and apply it to your Release 12.1.1 APPL_TOP.
Note: See Patch Wizard Main Page in Chapter 2 of Oracle E-Business Suite Patching Procedures. See also AD Merge Patch in Oracle E-Business Suite Patching Procedures.
If your system requires translated patches, complete the instructions in Step 13.
Synchronize NLS and American English product patches (conditional)
Applies to 11i release level: All
TUMS step key: N/A
If you applied product-specific patches in Step 12 and your system uses NLS functionality, then you must apply the NLS equivalents of each American English product-specific patch. To obtain the latest NLS patches and synchronize them with the American English patches, run the NLS Translation Synchronization patch:
Generate the manifest.
Log on to the administration node as the applmgr user and set the environment. Run the manifest generation script to generate a file manifest:
perl $AD_TOP/bin/adgennls.pl
The manifest is in $APPL_TOP/admin/$TWO_TASK/out/adgennls.txt format. Do not be concerned if it contains files from untranslated products for your language.
Upload the manifest file and request a Translation Synchronization patch.
Go to http://updates.oracle.com/TransSync (use your My Oracle Support user name and password). Follow the instructions on the screen to upload the manifest file and request a Translation Synchronization patch.
Note that there is a Translation Level Updates check box. Do not select it at this time, as it can add extra time to the upgrade process. However, you can use it at a later date to request a manifest that will check for enhancements to translations files that are new to your system, but are not required to synchronize your files with the American English files.
Download and apply the patch.
Once the patch is ready, you will receive an email stating its availability. Download the patch and follow the instructions in the readme file to apply it.
Verify the installation of the translations.
Check the log files generated by AutoPatch to ensure that the translations were installed successfully. You can delete the downloaded patch when you are sure the installation is complete.
Note: You can download the latest NLS product-specific patches without requesting a Translation Synchronization patch. However, this action may not provide the most current patches for your system.
Note: See Requesting Translation Synchronization Patches (Doc ID: 252422.1) for more information.
Disable Maintenance Mode (required)
Applies to 11i release level: All
TUMS step key: N/A
Maintenance mode controls the system downtime period by managing user logons. To disable maintenance mode, use the Change Maintenance Mode menu in AD Administration.
From the AD Administration Main Menu, choose the Change Maintenance Mode option.
The Change Maintenance Mode menu displays the current Maintenance Mode status at the top of the screen. It should be Enabled.
Select Option 2, Disable Maintenance Mode.
Note: See Oracle E-Business Suite Patching Procedures for information on the "hotpatch" method of applying patches when Maintenance Mode is disabled.
Reset init.ora parameters (required)
Applies to 11i release level: All
TUMS step key: N/A
Follow the instructions in Database Initialization Parameters for Oracle Applications Release 12 (Doc ID: 396009.1) and reset the init.ora parameters as needed.
Back up Oracle E-Business Suite (recommended)
Applies to 11i release level: All
TUMS step key: N/A
Downtime: Yes
Have the system administrator back up the Oracle E-Business Suite product files. On a server or stand-alone machine, have the database administrator back up the Oracle E-Business Suite database.
You must complete the tasks in this section to finish the upgrade. All the tasks are performed on the Release 12.1.1 APPL_TOP and should be completed during system downtime.
Reset ORACLE schema passwords (recommended)
Applies to 11i release level: All
TUMS step key: N/A
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 abbreviation (short name). To maintain product security, reset these default passwords now. Use the Oracle Users window from the System Administrator responsibility.
Note: See Oracle E-Business Suite Schema Password Change Utility in the Oracle E-Business Suite System Administrator’s Guide - Security.
Configure and start server processes (required)
Applies to 11i release level: All
TUMS step key: N/A
When you ran Rapid Install in the Prepare for the Upgrade section of Chapter 2, it created and stored an instance-specific context by replacing system variables you entered on the wizard screens with the specific values you saved in the configuration file (config.txt). At this point in the upgrade, you point Rapid Install to the Applications context file. Rapid Install (using AutoConfig) updates your system configuration using the values it finds in the context file.
Rapid Install creates the appropriate server process control scripts and starts all server processes, including the concurrent managers. Any concurrent programs created during the upgrade run automatically at this point.
Concurrent processing (CP) may run PL/SQL (inside of the database) that creates output and log files using the utl_file package. On all CP nodes, ensure that the $APPLPTMP environment variable is set to the first directory listed in the UTL_FILE_DIR parameter from the database’s init.ora. If you use a RAC database, then $APPLPTMP should point to a directory on a shared file system visible to all the RAC nodes. This ensures that CP can locate the output and log files created from PL/SQL.
Update the RDBMS ORACLE_HOME file system with AutoConfig files.
On the application tier (as the APPLMGR user), log on to the APPL_TOP environment (source the environment file) and run this Perl script to create appsutil.zip in <INST_TOP>/admin/out.
perl <AD_TOP>/bin/admkappsutil.pl
On the database tier (as the ORACLE user), copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME> and unzip the file. Change directory to RDBMS Oracle Home as follows:
cd <RDBMS ORACLE_HOME>
Unzip the file with the following command:
unzip -0 appsutil.zip
Install JRE on the database tier to ensure that the application tier and the database tier match:
If you are using a “fully certified” platform, refer to My Oracle Support (Doc ID: 418664.1) to install JRE under the <RDBMS_ORACLE_HOME>/appsutil directory.
If you are using a “database tier only” platform, refer to My Oracle Support (Doc ID: 456197.1) to install JRE under the <RDBMS_ORACLE_HOME>/appsutil directory.
Create a <CONTEXT_NAME> directory under $ORACLE_HOME/network/admin, where CONTEXT_NAME is <ORACLE_SID>_<DB_hostname>. Copy listener.ora and tnsnames.ora from the $ORACLE_HOME/network/admin directory to the $ORACLE_HOME/network/admin/<CONTEXT_NAME> directory.
Set and export the following environment variables:
ORACLE_HOME=<RDBMS_ORACLE_HOME>
LD_LIBRARY_PATH = $ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
ORACLE_SID = <instance name for current database node>
PATH = $PATH:$ORACLE_HOME/bin
TNS_ADMIN = $ORACLE_HOME/network/admin/<CONTEXT_NAME>
Generate a new Database context file as follows:
UNIX:
cd <RDBMS ORACLE_HOME>/appsutil/bin perl adbldxml.pl
Windows:
cd /d <RDBMS ORACLE_HOME>\appsutil\bin perl adbldxml.pl
Run AutoConfig on the database tier nodes.
UNIX:
<RDBMS ORACLE_HOME>>/appsutil/bin/adconfig.sh contextfile=<context file created in step 5>
Windows:
<RDBMS ORACLE_HOME>\appsutil\bin\adconfig.cmd contextfile=<context file created in step 5>
Note: See the following Installation Guide to Configure and Start Server processes: Oracle E-Business Installation Guide: Using Rapid Install, Release 12.1 (12.1.1) Part No. E12842-02.
Configure Applications client software for forms applet (required)
Applies to 11i release level: All
TUMS step key: N/A
The connection between the client and the Applications forms is provided through an applet in the client Web browser. Instead of using the browser’s own JVM, Oracle E-Business Suite uses the Sun Java (J2SE) native plug-in. You can find download instructions in Upgrading Sun J2SE (Native Plug-in) with Oracle Applications 12.0 Windows Clients (Doc ID: 393931.1).
Reapply customizations (conditional)
Applies to 11i release level: All
TUMS step key: N/A
If you customized Applications environment files (APPLSYS.env or devenv), then re-integrate them in devenv.env, or in the adovars.env file ($APPL_TOP/admin for UNIX or %APPL_TOP%\admin for Windows). Restart the application server processes so that the changes take affect.
Note: See Managing Server Processes in Oracle E-Business Suite Maintenance Procedures.
If your system includes customized forms, reports, programs, libraries, or other Applications files, then reapply all changes that you need for this release.
Integrate custom objects and schemas (conditional)
Applies to 11i release level: All
TUMS step key: N/A
If you previously created custom objects or have custom schemas that must be tightly integrated with Oracle E-Business Suite, then follow the steps in Oracle E-Business Suite Developer’s Guide to re-integrate these customizations with the APPS schema.
This release 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. Oracle recommends you explicitly declare Invoker Rights or Definer Rights for custom PL/SQL packages. See the 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 E-Business Suite.
Caution: When naming database objects, use XX as a part of the short name. For example, you might define the custom application to use the short name XXGL, and database objects to begin with an XXGL_ prefix.
Note: See Defining your Custom Applications in Oracle E-Business Suite Developer’s Guide.
Re-enable custom triggers, constraints, and indexes (conditional)
Applies to 11i release level: All
TUMS step key: N/A
During the upgrade, custom triggers or constraints may have been modified. If you disabled these triggers and constraints, identify any data updates that must be made before you re-enable them.
If you dropped any custom indexes, then review the new data model to determine if the index is necessary before you redefine it.
Complete these tasks before you continue with the tasks in Chapter 4, "Post-upgrade Tasks".
This section applies to all users, regardless of which products are registered as active.
Configure SSL for Web Services (conditional)
Applies to 11i release level: All
TUMS step key: N/A
If you have implemented Secure Sockets Layer (SSL) and plan to use Web Services, then you must generate certificates using the Oracle Wallet Manager from your Oracle E-Business Suite Server home ($IAS_ORACLE_HOME). Set up a password to protect your certificates.
Note: See Enabling SSL in Release 12 (Doc ID: 376700.1) for more information.
Use the Oracle Wallet Manager to generate the Wallet file. Then, follow these steps to complete the configuration:
Set the s_websrv_wallet_file parameter in the Applications context file to the location of the Web Services Wallet file. Note that the value is a file location, not a URL.
UNIX:
/etc/ORACLE/Wallets/system1/exported_wallet
Windows:
d:\oracle\system1\exported_wallet
Place the exported file in this location.
Provide the password for the exported Wallet file by running the following script:
$FND_TOP/patch/115/sql/txkSetWalletPass.sql
Complete Workflow Notification Mailer configuration (required)
Applies to 11i release level: All
TUMS step key: MP_WORKFLOW_TASKS
Before you send Oracle Workflow e-mail notifications, you must complete the Workflow Notification Mailer configuration, using the Notification Mailer Configuration wizard in Oracle Applications Manager.
Log on to Oracle Applications Manager.
From the Applications Dashboard, select the Workflow Manager from the "Navigate to" pull-down menu. Click Go.
In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page. The Notification Mailers status icon should show a status of Down.
On the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the notification mailer configuration wizard.
In the Outbound Email Account (SMTP) region, enter the name of the outbound SMTP mail server.
If you want to enable inbound e-mail processing, select the Inbound Processing parameter in the Inbound Email Account (IMAP) region, and enter the name of the inbound IMAP mail server, user name and password of the mail account that the notification mailer uses to receive e-mail messages, and the reply-to address of the e-mail account that receives incoming messages, to which notification responses should be sent.
Click Apply.
Return to the Service Components page, and verify that the status of the Workflow Notification Mailer service component status is Running.
Note: See Oracle Workflow Administrator’s Guide for more information.
If you have previously implemented the C-based Notification Mailer concurrent program or the Generic Service Management Notification Mailer, the tag definitions and configuration parameter settings for those parameters that are still applicable are automatically transferred to the Java-based Workflow Notification Mailer configuration parameters.
Complete Transport Agent setup (conditional)
Applies to 11i release level: All
TUMS step key: N/A
If you are using a proxy server to handle your outbound Oracle Transport Agent requests, then set following OXTA parameters in the container configuration:
OXTAOutUseProxy=True
OXTAOutProxyHost=<Your proxy server name>
OXTAOutProxyPort=<Your proxy server port>
To set the parameters, go to the Oracle Applications Manager Site Map and choose AutoConfig > Applications Node > Edit Parameters. Then, use the Search field to find OXTA. After you set the parameters, run AutoConfig to regenerate the oc4j.properties file ($INST_TOP/ora/10.1.3/j2ee/oafm/config/oc4j.properties).
Note: See Oracle XML Gateway User’s Guide for more information.
Complete setup for Oracle XML Gateway (required)
Applies to 11i release level: All
TUMS step key: N/A
The Oracle XML Gateway engine uses style sheets from an operating system directory you specify in the UTL_FILE_DIR database initialization parameter for your Applications instance. You must also specify the same directory in the ECX: XSLT File Path profile option. The value you specify for both the parameter and the profile option must be an absolute path and cannot contain a symbolic link or other operating system-specific parameters.
Also, ensure that the following profile options are set at site level for Oracle XML Gateway. If you have previously set these profile options, then no action is necessary, as the upgrade preserves these values.
| Profile Option | Description |
|---|---|
| ECX: XSLT File Path | Path to the directory specified as the location for style sheets to be used for XSLT transformations. It must be one of the valid values specified in the UTL_FILE_DIR database initialization parameter. Ensure that there is no slash at the end of the directory name. |
| ECX: System Administrator Email Address | Address to which Oracle XML Gateway error notifications should be sent. |
| ECX: Server Time Zone | Time zone the database server is running in. |
Note: See Oracle XML Gateway User’s Guide for more information.
These tasks apply to all users, regardless of which products are registered as active.
Enable PDF printing (required)
Applies to 11i release level: All
TUMS step key: N/A
The PDF Publisher print style and PASTA_PDF printer driver provide the capability to print PDF files using a third-party utility. You can use this style and driver to print a generated PDF. The Pasta Universal Printer type has been associated with the style and driver for ease of use.
Note: See Oracle XML Publisher Administration and Developer’s Guide for configuration steps.
Specify a temporary directory for XML Publisher (required)
Applies to 11i release level: All
TUMS step key: N/A
Use the Oracle XML Publisher’s Administration interface to assign a temporary directory for the site level. The temporary directory improves performance and allows unlimited XML file size.
Note: See Oracle XML Publisher Administration and Developer’s Guide for more information about this directory.