Upgrading to Oracle Forms 14.1.2.0.0

Upgrade to Oracle Forms 14.1.2.0.0 by either installing the software in the same Oracle Home directory path ("in-place") or installing in a new Oracle Home directory path ("out-of-place"). After the upgrade, complete the applicable configuration steps.

Although using the out-of-place method may sometimes be necessary, it is generally not recommended. Some configuration files may not be automatically updated by the Reconfiguration Wizard and may need to be manually updated. Exactly which files may need to be manually updated depends on the level of customization previously performed.

To get the Oracle Fusion Middleware Infrastructure and Oracle Forms and Reports software, refer to Obtaining the Oracle Fusion Middleware Software.

This section includes these topics:

Performing an In-Place Upgrade

To perform an in-place upgrade, you'll back up the existing Oracle Home directory, install the latest versions of the required software in the existing directory, then copy over any required files from the backup directory.

The in-place approach is the preferred upgrade method as it allows you to keep the existing Oracle Home path and minimizes the amount of manual steps post-upgrade.

To perform an in-place upgrade, you'll first back up the existing Oracle Home directory by renaming it—for example, to Oracle_Home_OLD). Then, you'll install Fusion Middleware Infrastructure 14.1.2.0.0 and Oracle Forms and Reports 14.1.2.0.0 into the same directory path which previously represented the Oracle Home before renaming it.

After installing the software, copy any custom files from the renamed directory into the same directory of the new Home. For example, custom files in \forms\java\ may need to be copied. This may also include the WLS domain (user_projects) if it was previously located in the Oracle Home. This must be moved into the new Home if it was previously located in the old Home. Do not move or copy the domain if it currently resides in a directory outside the Oracle Home.

Finally, use the Upgrade Assistant and Reconfiguration Wizard to upgrade the domain repository and configuration.

Note:

Do not copy any Oracle-provided files from the old version into the new Home. For example, do not copy Oracle-provided JARs or binary files. Doing so will cause the new installation not to function properly.

To perform an in-place upgrade:

Shut down all servers and processes associated with the Oracle Home being upgraded.
Rename the Oracle Home parent directory on this node. For example, Oracle_Home_OLD.
Install Fusion Middleware Infrastructure 14.1.2.0.0 using the same Oracle Home path as used previously before renaming it in step 2.
Install Oracle Forms and Reports 14.1.2.0.0 using the same Oracle Home path used in step 3.
If the WLS Domains directory (user_projects) and its subdirectories were located in the old Oracle Home, copy these directories to the new Oracle Home in the same location as they were previously.
If you haven't yet created a backup copy of the domain (user_projects), do it now before continuing.

WARNING:
Once the Upgrade Assistant and/or Reconfiguration Wizard have been run their changes cannot be reversed.
Run the Upgrade Assistant to upgrade the domain schemas:
1. Start the Upgrade Assistant:
  $ORACLE_HOME/oracle_common/upgrade/bin/ua
2. Select All Schemas Used By a Domain.
3. Type the path to the domain to be upgraded.
4. On the Prerequisite screen, select all check boxes to acknowledge that you have complied with the noted prerequisites.
5. When prompted for the DBA user name, enter a user with DBA privileges (for example sys as sysdba).
6. Click Connect, then Next to continue.
7. Continue to click Next until you reach the WLS Schema screen.
8. If the schema user name is <YOUR PREFIX>_WLS_RUNTIME, change it to <YOUR PREFIX>_WLS, then continue.
Run the Reconfiguration Wizard:
1. Start the Reconfiguration Wizard:
  $ORACLE_HOME/oracle_common/common/bin/reconfig.sh
2. Type the path to the domain to be reconfigured (upgraded).
3. Continue clicking Next until you reach the Database Configuration Type screen.
4. Click Get RCU Configuration to load details from the associated schemas, then continue.
5. On the Advanced Configuration screen, select Administration Server and Topology.
6. On the Administration Server screen, verify that a value is set for Listen Address. If no value is set, select All Local Addresses from the list, then click Next to continue.
7. Continue until you reach the Configuration Summary screen, then click Reconfig.
Run the Upgrade Assistant again to complete the reconfiguration and upgrade of the domain:
1. Start the Upgrade Assistant:
  $ORACLE_HOME/oracle_common/upgrade/bin/ua
2. Select All Configurations Used By a Domain.
3. Type the path to the domain to be upgraded.
4. On the Prerequisite screen, select all check boxes to acknowledge that you have complied with the noted prerequisites.
5. After the Examine phase has completed, click Next, then Upgrade to begin the processing.
Start the Node Manager, Admin Server, the managed servers, and any other system components (such as OHS).

Note:
Starting the servers for the first time after upgrading may take longer than usual. This is expected.

If you are upgrading in a multi-node environment, repeat all these steps for each additional node except for step 7. You do not need to upgrade domain schemas on each additional node.

After completing the installation and starting the servers, you can delete the Oracle_Home_OLD directories. However, before deleting, make sure you have copied any custom files needed from the Oracle_Home_OLD directory. It is recommended you not delete the previous Oracle Home until you have tested the new installation to confirm it is working correctly.

Once you have completed these steps, proceed to Completing the Upgrade.

Performing an Out-of-Place Upgrade

To perform an "out-of-place" upgrade, you'll install the software as for a fresh install, then use the WLS Reconfiguration Wizard and Upgrade Assistant to complete the upgrade.

The out-of-place upgrade lets you to change the location of the Oracle Home directory from its previous location. However, if the domain (user_projects) is located within the old Home, this directory structure must be retained indefinitely.

Note:

This method of upgrading may require you to edit some configuration files manually that cannot be updated by the Upgrade tooling. Exactly which files you need to update depends on which files you updated previously.

To perform an out-of-place upgrade, install Fusion Middleware Infrastructure 14.1.2.0.0 and Oracle Forms and Reports 14.1.2.0.0 into the same but new, empty directory path. Then copy any required custom files from the old Home into the new directory. This may include any custom files you previously had in the old Home (for example custom files in \forms\java). After you've done this, use the Upgrade Assistant and Reconfiguration Wizard to upgrade the domain repository and configuration.

Note:

Do not copy any Oracle-provided files from the old Home into the new Home. For example, do not copy Oracle-provided JAR or binary files. Doing so will cause the new installation not to function properly.

To perform an out-of-place upgrade:

Shut down all servers and processes associated with the Oracle Home being upgraded.
Install Fusion Middleware Infrastructure 14.1.2.0.0 into a new and empty directory on this node.
Install Oracle Forms and Reports 14.1.2.0.0 into the same Oracle Home path used in step 2.
If you haven't yet created a backup copy of the domain (user_projects), do it now before continuing.

WARNING:
Once the Upgrade Assistant and/or Reconfiguration Wizard have been run their changes cannot be reversed.
Run the Upgrade Assistant to upgrade the domain schemas.
1. Start the Upgrade Assistant:
  $ORACLE_HOME/oracle_common/upgrade/bin/ua
2. Select All Schemas Used By a Domain.
3. Type the path to the domain to be upgraded.
4. On the Prerequisite screen, select all check boxes to acknowledge that you have complied with the noted prerequisites.
5. When prompted for the DBA user name, enter a user with DBA privileges (for example sys as sysdba).
6. Click Connect, then Next to continue.
7. Continue to click Next until you reach the WLS Schema screen.
8. If the schema user name is <YOUR PREFIX>_WLS_RUNTIME, change it to <YOUR PREFIX>_WLS, then continue.
Run the Reconfiguration Wizard:
1. Start the Reconfiguration Wizard:
  $ORACLE_HOME/oracle_common/common/bin/reconfig.sh
2. Type the path to the domain to be reconfigured (upgraded).
3. Continue clicking Next until you reach the Database Configuration Type screen.
4. Click Get RCU Configuration to load details from the associated schemas, then continue.
5. On the Advanced Configuration screen, select Administration Server and Topology.
6. On the Administration Server screen, verify that a value is set for Listen Address. If no value is set, select All Local Addresses from the list, then click Next to continue.
7. Continue until you reach the Configuration Summary screen, then click Reconfig.
Run the Upgrade Assistant again to complete the reconfiguration and upgrade of the domain:
1. Start the Upgrade Assistant:
  $ORACLE_HOME/oracle_common/upgrade/bin/ua
2. Select All Configurations Used By a Domain.
3. Type the path to the domain to be upgraded.
4. On the Prerequisite screen, select all check boxes to acknowledge that you have complied with the noted prerequisites.
5. After the Examine phase has completed, click Next, then Upgrade to begin the processing.
Start the Node Manager, Admin Server, the managed servers, and any other system components (such as OHS) on the node.

Note:
Starting the servers for the first time after upgrading may take longer than usual. This is expected.

If you are upgrading in a multi-node environment, repeat all these steps for each additional node except for step 5. You do not need to upgrade the domain schemas on each additional node.

If the domain (user_projects) is located in the old Home, this directory structure must be retained and remain accessible. However, if the domain was not previously located within the old Home and the new installation has been tested and confirmed to be working properly, the old Home installation can be uninstalled then deleted. Do not delete the domain (user_projects) directory.

Once you have completed these steps, proceed to Completing the Upgrade.

Completing the Upgrade

After you upgrade Oracle Forms to 14.1.2.0.0, you may need to perform these additional steps depending on your configuration.

Forms Application Services (FADS) Configuration

If Forms Application Services (FADS) was configured in the environment, you will need to run the FADS configuration script (fads_config.py) with the upgrade option:

Run this command:
ORACLE_HOME/oracle_common/common/bin/wlst.sh fads_config.py upgrade
Follow the prompts.

Userid Encryption

If the previous installation was upgraded from 12.2.1.3 then to 12.2.1.4 or 12.2.1.19, you will need to manually enable encryption for the userid parameter and grant access to the Forms application keystore.

Note:

These steps are not necessary if upgrading from 12.2.1.4 or 12.2.1.19.

To enable encryption for the userid parameter:

(Out-of-place upgrade only) Set the forms.userid.encryption.enabled server parameter to true for the Admin Server and the Forms managed servers.

Refer to Customizing Domain Wide Server Parameters in Administering Server Startup and Shutdown for Oracle WebLogic Server.

Here is a sample of the setUserOverridesLate.sh file (use setUserOverridesLate.cmd for Windows), where the forms.userid.encryption.enabled parameter is enabled:

echo ""
echo "*****************************************************"
echo "** Executing setUserOverridesLate.sh"
echo "*****************************************************"
 
# specify additional java command line options for all servers

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Dforms.userid.encryption.enabled=true"
export EXTRA_JAVA_PROPERTIES

echo "USER_MEM_ARGS=\"${USER_MEM_ARGS}\""
echo "EXTRA_JAVA_PROPERTIES=\"${EXTRA_JAVA_PROPERTIES}\""
echo ""
echo "*****************************************************"
echo "** End of setUserOverrideLate.sh"
echo "*****************************************************"
echo ""

Run the following commands using WLST (online mode) to provide grants to the forms application or mbeans to access the Forms application keystore:

connect("<ADMIN SERVER USERNAME>","<PASSWORD>","localhost:7001")

grantPermission(codeBaseURL="file:${common.components.home}/../forms/provision/forms-config-mbeans.jar",
permClass="oracle.security.jps.service.keystore.KeyStoreAccessPermission",permTarget="stripeName=formsapp,
keystoreName=formsks,alias=*", permActions="*") 

grantPermission(codeBaseURL="file:${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/formsapp_14.1.2/-",
permClass="oracle.security.jps.service.keystore.KeyStoreAccessPermission", permTarget="stripeName=formsapp,
keystoreName=formsks,alias=*",permActions="*")

Restart the Node Manager, the Admin Server, and Forms managed server(s).