Upgrading Developer 6i with Oracle E-Business Suite 11i Page 1 of 11

Upgrading Developer 6i with Oracle Applications 11i [ID 125767.1]

Modified 05-AUG-2010 Type WHITE PAPER Status PUBLISHED

Upgrading Developer 6i with Oracle E-Business Suite 11i

NOTE Historically Forms and Reports upgrade metalink notes are updated on a regular basis with latest
one-off patches on top of a particular release. Customers are recommended to review this note
periodically for any latest fixes that may get included in this document at a later point. In case you
are applying the additional one-off patches at a later point, you are advised to perform the tasks
mentioned in Step 7 and then regenerate product jar files using adadmin utility.

This document will explain the steps needed to upgrade the version of Oracle Developer used with Oracle
E-Business Suite 11i. Oracle strongly recommends that you upgrade to the latest certified version of
Developer 6i Patchset for your hardware platform, which is covered by this document. If you want to
upgrade to any of the earlier Developer 6i Patchset releases, please refer to Metalink Note 232313.1 titled
'Information on Previous Versions of Developer 6i Patchsets'. It is important that you read and follow this
document in its entirety before starting an upgrade or applying any patch.

The overall process consists of the following steps:

1. Select Forms runtime Architecture and communications mode

2. Download the latest Certified Developer 6i Patchset and Applications Interoperability Patch
3. Download Additional Developer6i Patches
4. Stop the Forms, Reports, HTTP, Concurrent Manager Servers
5. Install the Developer6i Patch
6. Install the Additional Developer6i Patches
7. Relink Applications Executables on UNIX Platforms
8. Apply the Oracle Applications 11i Interoperability Patch
9. Configure Applications to use Sun JRE Native Plug-in
10. Verify your upgrade
11. Start the Forms, Reports, HTTP, Concurrent Manager Servers
12. Review the Known Issues

If you were directed to this document from a README file included in an Applications patch, then you must
upgrade Oracle Developer to the version specified
or higher in the README in order to use the product that issued the patch.

NOTE As with all technology upgrades, we recommend that you apply these instructions to a test instance
first, and verify that your implementation and customizations work properly before upgrading your
production instances.

This document contains instructions to modify configuration files that are also maintained by the AutoConfig
infrastructure.

• For more information on AutoConfig or to verify whether you are using it, please refer to the
MetaLink Note 165195.1 titled 'Using AutoConfig to Manage System Configurations with Oracle
Applications 11i' or the AD Utilities Reference Guide.
• If you are not using AutoConfig, please proceed with the manual steps described in the respective
sections.
• Customers with Developer 6i installed on Desktops outside of Apps for customizations etc. should
also upgrade their Developer 6i version to match the version being used on the server.

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 2 of 11

Step 1: Select Forms runtime architecture and Communications

mode
There are two Forms Server deployment architectures in Developer 6i. The Forms Listener, where a direct
connection is established between the Forms client applet and the Forms runtime process on the middle
tier, and the Forms Servlet, where communication between the Forms applet and the Forms runtime
process is via the Forms servlet. The Forms servlet acts as a "proxy", with the Forms applet sending
sending http or https requests to the Forms servlet, which redirects the messages on to the appropriate
Forms runtime process, allowing industry standard configuration, with no additional ports or certificates.

The Forms Listener

The Forms Listener supports both Socket, and HTTPS connect mode. (HTTP connect mode is not
supported for Oracle E-Business Suite customers using the Forms Listener architecture). There is a direct
connection between the Forms Applet and runtime process in each case, so https is handled on the middle
tier by the Forms process, requiring a separate certificate, and additional configuration.

If considering using HTTPS communications mode with the Forms Listener, please be advised that it
requires a more expansive set of actions including obtaining a certificate from a signing authority, such as
VeriSign, and reinstalling domestic versions of Oracle Forms and Wallet Manager. These steps can be time
-consuming and require additional testing, hence we recommend you leave ample time to perform the
switch to HTTPS mode. These issues are further reviewed in a MetaLink Note 123718.1 titled ' 11i: A
Guide to Understanding and Implementing SSL for Apps'. Another resource is Forms 6i documentation
titled 'Deploying Forms Applications to the Web'. This can be done independently of the upgrade steps
outlined in this document.

If you are AutoConfig enabled:

NOTE Please ensure you are running the latest version of Autoconfig by reviewing MetaLink note
165195.1 entitled 'Using AutoConfig to Manage System Configurations with Oracle Applications
11i'. The most current Autoconfig patches are documented in this note. You can complete the
Developer 6i upgrade first and then perform the steps as mentioned in MetaLink note 165195.1.

1. On your Forms server node, run the AutoConfig Context Editor as described in AutoConfig MetaLink
Note 165195.1.
2. In the Context Detail screen; Set the Form Connnection Mode context value
s_frmConnectMode in $APPL_TOP/admin/_.xml to socket or https.
For example, if you want to change the Forms communication mode to socket, then
Form Connection Mode = socket
3. Save your changes.
4. Generate new configuration files by running AutoConfig as described in MetaLink Note 165195.1
5. You can skip to the next point.

If you are NOT AutoConfig enabled:

1. Edit the startup script for the Forms6i server and change mode=http to mode=socket or
mode=https. This change will take effect the next time you restart the Forms server.

For UNIX platforms, this involves changing the script used to start the Forms
server. In 11.5.1, the file is called adfroctl.sh; in 11.5.2 and later, the file is
called adfrmctl.sh. The script resides in the directory
[COMMON_TOP]/admin/scripts, where [COMMON_TOP] refers to the
location of your COMMON_TOP directory. (Refer to the manual Oracle
Applications Concepts if you are not sure where this should be.)

In the above file, change all lines containing mode=http to mode=socket or

mode=https. For example:

f60ctl start port=$FORMS_PORT mode=socket

exe=f60webmx >> $FRMLOG 2>/dev/null &

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 3 of 11

On Microsoft Windows platforms, you must edit the registry entry for the
Forms service. When changing between connection modes, make sure you
choose the correct service to edit. The names of these services correspond to
those in the services control panel.

Open the Registry Editor by running regedit or regedt32.

For 11.5.1, go to the Registry key -

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleFormsServer
SID, where SID is the name of your database instance. Double-click on Mode
value and change the data from http to socket or https .

For 11.5.2 and later, go to the Registry key -

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleFormsServer
SID\Application, where SID is the name of your database instance. Double-
click on the Parameters value and change the data so that the mode equals
socket or https. Note that in 11.5.1, Mode and Port are separate registry
values, but in later releases, they are combined into a single Parameters
registry key.

2. On the web server used by Forms, you must modify the variable connectMode in the file
$OA_HTML/bin/appsweb.cfg . Change the value from http to socket or https.

This file should always be kept in sync with the version at $FND_TOP/resource/appsweb.cfg.
NOTE Be sure any changes you make are reflected in both locations.

The Forms Servlet

The Forms Servlet supports both HTTP and HTTPS, using industry standard architecture. Socket mode is
not applicable to this architecture. HTTPS configuration on the middle tier is at the Apache layer, with no
additional ports or certificates required to run Forms. The standard Apache HTTPS configuration supports
Forms as well as Self Service. The Forms Servlet is supported in Developer 6i Patch 7 and later.

Follow the instructions in MetaLink Note 201340.1 , titled 'Using Forms Listener Servlet with Oracle
Applications 11i '.

Recommendations

We recommend the use of socket mode for intranet users, and HTTPS for Internet users. We recommend
the Forms Servlet for customers wishing to use HTTPS due to the simplified, industry standard
configuration. Please review MetaLink's Certify , under Product Lifecycle -> Certifications , for the list of
currently supported communications modes.

Step 2: Download the latest Certified Developer 6i Patchset and

Applications Interoperability Patch
Since Developer patches are cummulative, you will only need the patchset for the latest Developer 6i level.
In addition, you will also need the Applications/Forms Interoperability Patch corresponding to the Developer
patchset you are installing. The number for the interoperability patch is given in the right-hand column.

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

Apps
Developer Developer
Forms Reports Graphics Interop
6i 6i Patch
Patch
Patch 19* 6194129 6.0.8.28.x 6.0.8.28.x 6.0.8.17.x 9935935

* Dev 6i Patch 19 will not be available for HP Tru64 customers.

* Dev 6i Patch 19 for AIX is a 64 bit patch, this patch can also be applied to 32
bit operating systems.

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 4 of 11

Please refer MetaLink Note 232313.1 titled 'Information on Previous Versions of Developer 6i Patchsets' if
you need to upgrade to any of the previous Developer 6i Patchset versions.

Step 3: 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. Where
applicable please ensure you download the 6.0.8.28 version of the patch:

Developer 6i Sun Solaris HP-UX IBM AIX Linux MS Windows Server

Patch 19 *7423534
9863561 + 9863561 + 9863561 + 9863561 + 9863561 +
6125732 6125732 6125732 6125732 9436629**
6857221 6857221 6857221 6857221
5232832 5232832 5232832 5232832 5232832
8888184** 8888184** 8888184** 8888184**
7329300 7329300 7329300 7329300
6747939 6747939 6747939 6747939
7552880 7552880 7552880 7552880

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

** These patches cause errors when clicking a forms link from the Notification Details Page.
This is fixed by patch 9094950, see Notification Details Page in the 'Known Issues' section of
this note for further information.
+ You must download and apply the latest interop 9935935 in order for this fix to work.

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.

Step 4: 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 .

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 5 of 11

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 5: 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 6: 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 7: 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.

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 6 of 11

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 8: 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.

Step 9: Configure Applications to use Sun JRE Native Plug-in

NOTE Oracle JInitiator 1.3.1.x reached end of error correction support (ECS) for E-Business Suite 11i
versions on 31st July 2009. For full details regarding Product Obsolescence/De-Support information
please see note 552692.1.

Deploy the latest certified version of the JRE native plug-in by following note 290807.1, titled 'Deploying
Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i.

To see what versions of Sun JRE Plug-in are certified for use with E-Business Suite, go to MetaLink's
Certify , select View Certification by product, select E-Business Suite from the Product Group list.
Choose E-Business Suite 11i and Earlier for the product, and then your client-side operating system
(e.g.: Microsoft Windows 2000 x86) for the Platform. Then choose Applications Release 11.5.x, and follow
the "Other" link for the latest certified versions.

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' on Unix platforms and '%ORACLE_HOME%
\bin\ifcmp60.EXE help=y' on Windows to display various component versions. (If the version shown is still
8.0.6.0.x please refer to Metalink Note 191573.1 )

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 7 of 11

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

NOTE Some of the patches mentioned in the Known Issues section are not available on all platforms. If
any of the patches are not available for your operating system please log a Service Request with
Oracle Support requesting the same.

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.

Notification Details Page

• Patch 8888184 causes the following errors when attempting to launch a form by clicking the forms
link from the Notification Details Page;
◦ FRM-40723 : No such parameter named G_QUERY_FIND exists in form APXIWALL
◦ ORA-00911: invalid character
◦ FRM-40505: Oracle error Unable to perform query
• To fix this issue please apply patch 9094950

Form Crash in multi selection hierarchial tree

• In a multi selection hierarchial tree when collapsing a tree node which has a selected (highlighted)
tree item may result in Forms Applet abort session. Please apply patch 2574342 if you enconter this
problem.

FRM-92100 for Korean users

• Korean users may see FRM-92100 while clicking "Document Catalog" button while viewing Menu
Attachments. Check bug 8637247 for more details. This is fixed in patch 8663266.

Forms Freeze while typing in a multi-line text field with large data

• Forms might freeze while entering text in a mutli-line text field having datatype as LONG. This issue
is fixed in patch 9319252. This patch also has EUM support fixes for Developer 6i.

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 8 of 11

FRM-92101 while more number of forms are open on Solaris

• Solaris users may get FRM-92101 when more than few forms are open at the same time. Solaris
5.10 customers can download and apply patch 9583514. You also need to apply TXK
AUTOCONFIG AND TEMPLATES ROLLUP PATCH U - 9535311 to get the complete fix.

Reports consuming 100% CPU

• Reports may consume 100% CPU or may run for 2-3 days and never finish when number of pages
in report output exceeds 65535 and the report uses page numbering format "m of N". There is no fix
for this issue yet. Respective product teams need to change their page numbering format to "m" to
avoid such issues.

Reports Issue when arguments have Turkish special characters

• Turkish users may experience an issue where several AR reports do not intiate if the input contains
Tuskish special characters. The report runs but never completes. This issue is fixed in patch
7016961. You must also apply patch 7423786 to get the complete fix.

Allignment issues with Reports having Vietnamese characters

• While running reports having Vietnamese characters, especially when there are multiple rows in the
same column, the allignment for the next column is not proper, please apply 8884353 to fix the
issue. Patch 8604052 needs to be applied on 8.0.6 HOME for any issues with allignment with
Vietnamese pre-composed characters.

Abnormal termination of Reports printing bar code

• Reports using barcode font may get terminated abruptly. This issue is fixed in patch 8826546.

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.

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'.

On Unix Platforms:

1. Stop the Forms Server process.

2. Add the following environment variable to the 'Oracle Forms 6.0 environment
variables' section of your '$APPL_TOP/< SID >.env' file as;

FORMS60_RESTRICT_ENTER_QUERY="TRUE"
export FORMS60_RESTRICT_ENTER_QUERY

3. Source the environment, then restart the Forms Server process.

On Windows Platforms:

1. Stop the Forms Server process.

2. Add the following environment variable to the 'Oracle Forms 6.0 environment
variables' section of your '$APPL_TOP/< SID >.cmd' file as follows:-

FORMS60_RESTRICT_ENTER_QUERY=TRUE

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 9 of 11

3. Source the environment, then restart the Forms Server process.

Windows Server customers should make sure they are using NTFS file
systems. If they are using FAT file systems, they will run into bug 2094643.
When attempting to patch Developer 6i, installation will fail with Error message
"Directory '8.0.6' of the ORACLE_HOME Path is not a legal name"

Customers wishing to use Cancel Query functionality in E-Business Suite 11i

must review 'Cancelling Long-Running Queries in Applications 11i' ( 138159.1)

Maintenance

• On Microsoft Windows server platforms, you will have to stop the Forms, Reports and Concurrent
Manager for steps 7-10, and the HTTP server for step 10.

• On Unix platforms, at step 7 you should discourage new connections (change/hide the link to start E
-Business Suite 11i). New connections started during steps 7-11 will experience instabilities. After
step 11 you need to restart the Forms and Reports servers, and flush the Apache cache.
Communicate to all users that the environment has been patched, and that they should restart their
sessions at the earliest convenience. Already connected users can continue with their current
sessions, but they should restart their sessions soon, as they could eventually get into an
inconsistent state.

• This approach allows daytime patching for environments with low session turnover (e.g. professional
users that stay connected all day). If something goes wrong with the hot patching bounce the
environment -- stop and restart all servers.

VNC Display

• In order to use VNC display with Oracle Reports, please follow the instructions in metalink note
181244.1 entitled "Using VNC or XVFB as the X server for Applications 11i".

Printer Configuration File

• If you have customized the printer configuration file located in

$ORACLE_HOME/guicommon6/tk60/admin/uiprint.txt with your printer definitions, you will have to
redo the configurations after applying the Developer 6i patch. Your previous uiprint.txt is backed up
as $ORACLE_HOME/guicommon6/tk60/admin/uiprint.txt.PRE_P<patch#>.

Be sure to review the known issues section within MetaLink Note 232313.1 titled 'Information on Previous
Versions of Developer 6i Patchsets' if you have applied any of the Previous Developer 6i Patchsets.

Change Log
Date Description

• Replaced client MLR 9444996 with 9863561

• Replaced interop patch 9410366 with 9935935. Please note that 7343387,
8758105 and 9410366 are older versions of interops which are obsolete
now.
Jul 29,
• Added new one offs 6747939 and 7552880 as per doc bugs 9830881 and
2010
9876801
• Added Known Issues text for issues with Vietnamese reports as per doc bug
9765169
• Added Known Issues text for Solaris users as per doc bug 9746903

Apr 27, • Updated as per doc bugs 9094408, 9378492, 9547175 and 9562645
2010 • Replaced MLR 8717874 with 9444996 as per doc bug 9480884

Feb 26, Updated new interop patch, moved 7329300 to mandatory one-off of list. Removed
2010 11.5.9 references from Known Issues.

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 10 of 11

Feb 16, Added Patch 9094950 to known issues due to a regression in required patch
2010 8888184.
Jan 11,
Added MLR 8888184 to the one off list as per bug 9089042
2010
Sep 14, Added one off 5232832 to the list and 8663266 to Known Issues section as per
2009 bug 8826287 and 8888014
Aug 18, Removed 4586086 from Step 4 as it is included in Patch 19. Removed all
2009 references to JInitiator as it is desupported
Aug 7, Replaced interop patch 7343387 with 8758105, added 5658282 to Known Issues
2009 section
Aug 5,
Replaceed MLR 8402746 with 8717874 as per bug 8745538
2009
Jun 29,
Updated Known issues section for Bug 7322285
2009
Jun 11, Added 8258313 to the one-off list and added patch 8485936 to known issues
2009 section as per bug 8590516
Apr 10, Replaced MLR 7594318 with 8402746 and added comments against patch
2009 7657973.
Feb 04,
Added 7657973 to the one off list as per bug 8217697.
2009
Feb 02,
Added HRMS Configurator issue, note 753481.1 to Known Issues.
2009
Dec 23,
Replaced java MLR with 7156414 with new MLR 7594318.
2008
Nov 17,
Updated the Oracle Jinitiator requirement to 1.3.1.x.
2008
Nov 03,
Updating Known issues for bug 7507622, 7322285.
2008
Oct 03,
Updated to reflect HP UX as certified along with the one off list.
2008
Sep 17,
Updated comments for HP UX platform.
2008
Sep 15,
Removed the note for one off 6857221on Solaris since the issue is closed now.
2008
Sep 5,
Updated issue regarding one off 6857221on Solaris.
2008
Aug 21, Updated the interop number since the older one had incorrect version of README-
2008 Config-Developer.html.
Aug 7,
Updated for Patchset 19 certification.
2008

Last Updated: 29th July 2010

Related

Products

• Oracle E-Business Suite > Applications Technology > Technology Components > Oracle
Applications Technology Stack
• Oracle E-Business Suite > Applications Technology > Technology Components > Oracle
Applications Technology Stack

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010
Upgrading Developer 6i with Oracle E-Business Suite 11i Page 11 of 11

Errors

FRM-92101; FRM-92100; FRM-40505; FRM-40723; ORA-911

Back to top

Rate this document

https://support.oracle.com/CSP/main/article?cmd=show&id=125767.1&type=NOT 16/9/2010