Step 4: Download Additional Developer 6i Patches

You will need to separately obtain certain additional Developer (Forms) patches, depending on your Developer Patch and Platform.

These patches must be applied BEFORE any Forms security CPU patch.  The CPU patch is designed to be applied on top of these patches.  Any conflicts between the patches listed here and the CPU should already be resolved in the CPU patch by Oracle Development.  If any of these patches are already merged into the CPU patch, it is not strictly necessary to apply the non-CPU patch first, but it will not cause a problem if you have already done so. Applying these patches AFTER the CPU may cause problems if the two patches update common files, and is therefore not supported.  If you discover unresolved conflicts between the patches listed here and the CPU, please log a tar with Oracle Support.

There is no automatic conflict checking in Developer 6i, so if you apply additional one-offs, other than the ones listed here or the CPU, you should check for conflicts in the files updated, and request merged fixes through Oracle Support as necessary. 

For Developer 6i Patch 19 on Sun Solaris, IBM AIX, Linux and Microsoft Windows Servers:

Developer 6i	Sun Solaris	HP-UX	IBM AIX	Linux	MS Windows Server
Patch 19		*7423534
	8402746	8402746	8402746	8402746	8402746
	6125732	6125732	6125732	6125732	6125732
	6857221	6857221	6857221	6857221	6857221
	#7657973	#7657973	#7657973	#7657973	#7657973
	8258313	8258313	8258313	8258313	8258313

* Patch 7423534 needs to be applied prior to applying any other one-offs.

# Patch 7657973 is applicable only for customers using Sun JRE Native Plug-in, customers using Oracle JInitiator can choose to ignore this patch.

NOTE	Be sure to review the README file for each individual patch before applying it in step 7 Install the Additional Developer6i Patches below.

Linux Users

Linux users must also apply the Linux interoperability patch 3830807 and 4586086.

Step 5: Stop the Forms, Reports, HTTP, and Concurrent Manager Servers

You must stop all server processes that may be impacted by the Developer 6i patch before applying it.

Stop the Forms and Reports server processes.

For Microsoft Windows platforms, note the name of the Forms and Reports services in Control Panel - Services.Also for Microsoft Windows platforms, stop all Forms user connections still active. To do this, open Task Manager and kill all processes named ifweb60.exe or ifsrv60.exe .

Stop the HTTP server used for your Forms server.

Stop the Concurrent Manager servers as they will need to use the new Reports executable.

For Microsoft Windows platforms also shut down the 'OracleTNSListener80APPS_SID' & 'Oracle TCF SocketServer SID' Services.

Step 6: Install the Developer 6i Patch

Install the full Developer 6i Patch on all Application Tier nodes hosting the Forms server, Reports server, HTTP server and Concurrent Processing server.

NOTE	All references to ORACLE_HOME refer to the 8.0.6-based Oracle Home.

The following platform-specific notes regarding Developer 6i Patch installation should be considered:

For Microsoft Windows platforms, install Developer 6i Patch using the Oracle Installer. If any pre-install patches were applied, use the fixed image produced by those patches. E-Business Suite users should know the name of their 8.0.x Oracle Home containing the Developer 6i Install; disregard the Developer instructions to use 'iAS_6iServer' home unless you have explicitely migrated to iAS. To verify which Oracle Home you are using, check your environment files.

If your E-Business Suite instance was created using Rapid Install 11.5.7or later;
When running the Installer for the Developer 6i patch, choose "English" as the language and "Typical" as the install option.

Note, that you should upgrade all other products on all nodes. You can ignore the Installer's request to check the physical location of the JInitiator directory. You should instruct the Installer not to create a new service for the Forms listener; you already have a service which you stopped in the previous step.

NOTE

Please note that the ReadMe document is incorrect and in some cases missing from the various Patch 19 MetaLink downloads (this is detailed in bug 6338981). For installation instructions for Patch 19 on Unix and Windows platforms please check the release notes here. The document contained in this note encompasses the ReadMe install instructions as well as the information in the Patch 19 Release Notes.

Step 7: Install the Additional Developer 6i Patches

For each of the Additional Patches you downloaded earlier, follow the instructions in the accompanying README file to apply it to your installation.

NOTE	HP-UX Customers will need to apply 7423534 prior to applying any other one off patches on 8.0.6 Oracle Home.

Step 8: Relink Applications Executables on UNIX Platforms

After applying the Oracle Developer 6i Patch on UNIX platforms, you must relink several Oracle E-Business Suite executables to include Developer patch changes. The executables are f60webmx, ar60run , ar60runb, ar60rund, and are all owned by FND.

NOTE	If your environment is  NOT Autoconfig enabled, make sure you have modified the LD_LIBRARY_PATH or SHLIB_PATH variable as indicated in step 6 above, before performing this step, or the relink will fail.

You can relink these executables by running adadmin
When the Main Menu appears select 'Maintain Applications Files Menu' and then select 'Relink Applications Program'
Answer the questions below as follows, in order to select the individual executables for relinking.

Enter list of products to link ('all' for all products)[all] : fnd
Generate specific executables for each selected product [No] ? y
Relink with debug information [No] ? n

(You will then be offered a list of executables that are available for relinking)

Enter executables to relink, or enter 'all' [all] : f60webmx ar60run ar60runb ar60rund *

* In a multi-node configuration, not all these executables exist on each node. The list of executables will show those that do exist on the node you are currently running on, and only those should be entered to avoid errors.

Refer to the Maintaining Oracle Applications manual for more information on how to use the AD Administration Utility or AD Relink Utility for relinking executables.

Step 9: Apply the Oracle Applications 11i Interoperability Patch

Apply the Applications/Forms Interoperability Patch you downloaded. If this document was referenced from another patch, apply that patch, as well.

NOTE	Make sure you have performed all the required Oracle Applications 11i Post Install steps as described in your Installing Oracle Applications Release 11i manual before performing this step, or you will face the yellow bar Known Issue discussed below.

Step 10: Verify your upgrade

Verify that the fndforms.jar and fndewt.jar JAR files have been rebuilt by checking the timestamp for both files in the $OA_JAVA/oracle/apps/fnd/jar directory. If the timestamp is not current and the previous steps completed successfully, run the AD Administration Utility (adadmin), select Maintain Applications Files, then select Generate Product JAR Files. Do not force the regeneration of all JAR files. Again, verify that the fndforms.jar and fndewt.jar JAR files have been rebuilt by checking their timestamps again.

If your JAR files are still not updated, verify all the prior steps, and the Known Issues section below.

If you have applied Developer 6i Patch 6 or above, verify that the PL/SQL version installed is 8.0.6.3.x. You can run '$ORACLE_HOME/bin/f60gen help=y' to display various component versions. (If the version shown is still 8.0.6.0.x please refer to Metalink Note 191573.1 )

For Microsoft Windows platforms, look under Control Panel - Services to see if additional Forms and Reports services were added. If so, disable the new ones by pressing the Startup button, and setting the Startup Type to Disabled.

Step 11: Start the Forms, Reports, HTTP, Concurrent Manager Servers

Restart the listener processes, as follows:

                     Restart the Forms and Reports server processes. On Microsoft Windows Server, start the original Oracle Forms Server service you stopped earlier, if it is not already running.

                     Restart the HTTP server used by the Forms server if it is not already running.

                     Restart the Concurrent Processing server (the concurrent managers).

                     On Microsoft Windows platforms also start the 'OracleTNSListener80APPS_SID' & 'Oracle TCFSocketServer SID' Services.

Step 12: Review the Known Issues

HRMS Configurator Problem

Using Forms patchset 19 (6.0.8.28) causes an frm-92101 error when selecting templates in the forms configurator form, PERWSFCR. Please see note 753481.1 for further details and bug fix.

Relinking issues for ASO/ANO Customers

                     ASO/ANO Customers may hit relinking errors as mentioned in bug 7507622. Please refer to the workaround given in "Appendix A - Troubleshooting Guide" section of metalink note 391248.1.

Issues with README files for various Patch 19 downloads

                     Please note that the ReadMe document is incorrect and in some cases missing from the various Patch 19 MetaLink downloads (this is detailed in bug 6338981). For installation instructions for Patch 19 on Unix and Windows platforms please check the release notes here. The document contained in this note encompasses the ReadMe install instructions as well as the information in the Patch 19 Release Notes.

Forms Crashing issue

                     You may experience forms crashing with FRM-92101 error while selecting Organization when you open Inventory Plan --> Names form. As a workaround you will need to select the organization from the list instead of using the text box to find. For more details check bug 7322285. The issue is fixed in patch 7329300 which is available on all platforms except windows. Windows customers are requested to log a Service Request with support if they require a fix.

Issue while starting APPS Listener

                     Windows customers may have issues while starting 8.0.6 listener. Please shutdown all services, run autoconfig to get rid of this issue. For more information on AutoConfig please refer to the MetaLink Note 165195.1 titled 'Using AutoConfig to Manage System Configurations with Oracle Applications 11i'.