Monday, October 3, 2011

Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem: Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12


Symptoms:
Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12



Solution:

Section 1: Overview

Section 1.1: Forms and Reports Architecture in Oracle E-Business Suite Release 12

Forms and Reports 10.1.2.x as used by Oracle E-Business Suite Release 12 are components of Oracle Application Server 10.1.2 (OracleAS 10g 10.1.2). Applying a OracleAS 10g 10.1.2.x patch will patch all the OracleAS 10g 10.1.2 components, not just Forms and Reports. Note that some components (such as the 10.1.2 Oracle HTTP Server) are not used in Release 12.
By default, Oracle E-Business Suite Release 12 utilizes the Forms Servlet architecture, with either an HTTP or HTTPS connection. Oracle recommends using this architecture as it provides an efficient, industry-standard configuration. However, in some circumstances there can be a performance overhead. In such a case, some customers may wish to use the older Socket mode, which is supported with OracleAS 10g (Forms) for Oracle E-Business Suite Release 12 customers. Instructions for doing this can be found in My Oracle Support Knowledge Document384241.1,"Using Forms Socket Mode with Oracle E-Business Suite Release 12".
For Oracle E-Business Suite Release 12, the Forms Servlet is configured to run in an OracleAS 10.1.3 OC4J container, so that a single OracleAS 10.1.3 version of the Oracle HTTP Server services all Forms, Reports and HTTP-based (formerly Self-Service) requests. The Forms runtime process (frmweb) is still forked into a 10.1.2 environment.The instructions for deploying the Forms Servlet to the 10.1.3 OC4J container during the patching process are described below. This step is still required even if you only use Socket mode, as the Forms Servlet is still used to generate the initial HTML page.

Section 1.2: Forms and Reports Builders

By default, OracleAS 10g 10.1.2 does not include the Forms and Reports builders. These are normally shipped as a separate product, Oracle Developer Suite 10.1.2. However, for the convenience of E-Business Suite Release 12 customers, the builders are included in the OracleAS 10g 10.1.2 Oracle Home on the Linux, Sun Solaris SPARC, and Windows platforms. Customers running Release 12 on platforms that do not support Developer Suite will need to install Developer Suite 10.1.2 separately on one of the supported platforms if they wish to use the builders.
OracleAS 10g 10.1.2.x patchsets and one-off patches can be applied to both OracleAS 10g 10.1.2 and Oracle Developer Suite 10g 10.1.2 where applicable.

Section 1.3: Linking differences between Release 11i and Release 12

On UNIX and Linux, E-Business Suite user-exit code is now contained in its own FND-owned shared object, which is dynamically linked at runtime. Examples on Linux include $FND_TOP/bin/fndfmxit.so and $FND_TOP/bin/fndrwxit.so. There is no longer any need to build separate Forms and Reports runtime executables with the E-Business Suite user-exit objects statically linked.
In Release 12, the executables $ORACLE_HOME/bin/frmweb and $ORACLE_HOME/bin/rwrun are built by the standard OracleAS 10g 10.1.2 patching process. This is in contrast to Release 11i, which used f60webmx, ar60run, ar60runb and ar60rund executables with user-exit objects statically linked.

Section 1.4: Patching differences between Release 11i and Release 12

Patchsets are now installed using the Oracle Universal Installer on all platforms. One-off patches are now installed using the Oracle opatch utility. Opatch performs automatic conflict detection and various rollback options. Instructions are in the patch READMEs.
The opatch utility can also be used to generate a list of one-off patches applied, which can useful useful when reporting problems, requesting a one-off, or simply verifying that all the recommended one-offs have been applied. To generate the patch list, run the command opatch lsinventory -details. For more information about opatch, refer to My Oracle Support Knowledge Documents <224346.1> and <189489.1>.

Section 1.5: Client java code shipping differences between Release 11i and Release 12

Oracle E-Business Suite Release 12 does not use the default jar files shipped with the Forms product. Instead, it builds its own, although it should be noted that the individual class files are the same and the only difference is in the packaging.
For Release 11i, which used Oracle Developer 6i, the E-Business Suite Forms and EWT jar files (fndforms.jar, fndformsi18n, fndewt.jar, fndbalishare.jar ) were built using as the source the class files extracted under $ORACLE_HOME/forms/java. The OracleAS 10g 10.1.2 install does not extract the class files in this way, and in Release 12 the E-Business Suite jar files are built using $ORACLE_HOME/forms/java/frmall.jar and $ORACLE_HOME/jlib/ewt3.jar as the source, rather than the standalone class files.
In practical terms this means that E-Business Suite Release 12 can now utilize the same Forms 10.1.2 patches for client java code, and the patches will deliver a new set of the default Forms jar files rather than individual replacement class files. Where multiple client side java fixes are required, a merge will be necessary. However, conflict-checking by opatch ensures that the fixes are correctly merged.
Note: Oracle E-Business Suite Release 12 customers still have to run the extra manual step to generate the E-Business Suite Forms JAR files, as was the case in Release 11i. Also, the Forms servlet needs to be deployed to the 10.1.3 OC4J container, as described here.

Section 1.6: 32bit patches vs 64 bit patches

Forms and Reports is a 32 bit application. The patches that are available for 64 bit OS will also be applicable for 32 bit OS unless specified otherwise.

Section 2: Pre-Installation Steps

Step 2.1: Download Required Patches

Step 2.1.1: Download latest certified OracleAS patchset and Oracle E-Business Suite Interoperability Patch

Download the latest certified OracleAS 10g patchset. In addition, you will need the E-Business Suite/Forms Interoperability patch corresponding to the OracleAS 10g patchset you are installing. The number for the interoperability patch is given in the right-hand column.

Oracle Application Server 10g
Oracle Application Server 10g Patchset
Oracle Forms
Oracle Reports
Oracle E-Business Suite Interoperability Patch
OracleAS Patchset 10.1.2.3
10.1.2.3.0
10.1.2.3.0

* This is applicable only for 12.0.x customers. 12.1.x customers are requested to ignore this patch.

Step 2.1.2: Download Additional Patches

You will need to obtain certain additional Forms and Reports patches separately, depending on your OracleAS patchset and platform.
For the OracleAS 10.1.2.3.0 patchset on the Sun Solaris SPARC, HP-UX PA-RISC, HP-UX Itanium, IBM AIX, Linux, Linux x86-64, IBM: Linux on System z and Microsoft Windows Server 2003 platforms:

Sun Solaris SPARC
HP-UX PA-RISC
IBM AIX
HP-UX Itanium
Linux and Linux x86-64 Note 1
IBM: Linux on System z
Microsoft Windows Server 2003







Forms - Bundle Patch
Forms - Platform-Specific







Forms - C Patch



Reports - Platform-Specific












Reports - C Patch






Reports - Java Patch

Reports - Generic Patch


Note 1. Both Linux x86 and Linux x86-64 customers will need to download Linux x86 patches. Linux x86 patches are applicable to Linux x86-64 customers as well.

Note 2. 6995251 is applicable only to Linux x86-64 customers.

++ Windows MLR 12421182 replaces patches 11780669 and 7423007.

** These patches have additional pre-requisites, please follow the patch readme carefully and apply the required pre-requisite patches before applying the patch.

Ensure you review the README file for each individual patch before you apply it later in Step 3.3.

Step 2.2: Stop All Services

Stop all server processes that may be impacted by the OracleAS patchset. Log in to the application tier as the OS user who owns the application tier files, and stop the services using the command:
$ADMIN_SCRIPTS_HOME/adstpall.sh <APPS User>/<APPS password>

Step 2.3: Apply Prerequisite Technology Stack Patches

Step 2.3.1: For 12.0.x Customers

12.0.x customers are requested to download and apply the following techstack patches:

Step 2.3.2: For 12.1.x Customers

12.1.x customers who are already on 10.1.2.3 and are uptaking the additional one-off fixes are requested to download and apply the following patch:
  • Patch 8919489 - R12.TXK.B.Delta.3

Step 2.4: Pre-Installation Steps (HP-UX Itanium platform only)

Step 2.4.1: Change file permissions

The two files listed below do not have write permissions for Oracle Universal Installer to update, so their permissions must be changed as shown:
chmod u+w $ORACLE_HOME/jdk/jre/bin/IA64W/java_q4p

chmod u+w $ORACLE_HOME/jdk/bin/IA64W/java_q4p

Step 2.5: Pre-Installation Steps (IBM AIX platform only)

Step 2.5.1: Take backup of zip utility (Conditional)

If you are upgrading from 10.1.2.0.2 to 10.1.2.3 take backup of $ORACLE_HOME/bin/zip. This step is to make sure that we have the proper version of zip under ORACLE_HOME/bin. On AIX, we had seen a issue after upgrading AS tools home from 10.1.2.0.2 to 10.1.2.3. Zip version under $ORACLE_HOME/bin got downgraded from 2.3 to 2.2.
cd $ORACLE_HOME/bin

cp zip zip_ORIG

Step 2.6: Pre-Installation Steps (Windows platform only)

Step 2.6.1: Deinstall patches 5635164, 5689224 and 5563264 (Conditional)

Use the opatch 'rollback' command to deinstall patches 5635164, 5689224 and 5563264 from the 10.1.2.0.2 Oracle Home.
Skip this step (2.6.1) if either of these conditions apply:
  • You have already applied CPUApr07 patch or later for OracleAS 10g 10.1.2.0.2
  • You are not on OracleAS 10.1.2.0.2, as you will have performed this step during previous upgrades

Step 2.6.2: Download additional patches (Conditional)

If you installed Oracle E-Business Suite Release 12 using startCD 12.0.0.23 or higher, skip this step (2.6.2). Otherwise, you should download and apply patches 5872965 and 6080584 from My Oracle Support.

Step 2.7: Back Up OracleAS 10.1.2 ORACLE_HOME and Inventory folder

Oracle recommends that you make a backup of your existing environment before you install Oracle Application Server 10g Release 2 patchset 3 (10.1.2.3.0).This will enable you to restore your original environment if you encounter a problem with application of the patch, or need to remove the patch for some reason.
You are also advised to take a complete backup of the Inventory folder (either global or local) that contains the OracleAS 10.1.2 ORACLE_HOME inventory details.

Section 3: Installation Steps

Step 3.1: Install the Application Server Latest Certified Patchset (10.1.2.3.0)

The steps in this section will install the OracleAS 10g 10.1.2.3.0 patchset on all application tier nodes hosting Forms and Reports services.
Note: All references to "ORACLE_HOME" refer to the OracleAS 10.1.2 Oracle Home that contains the Forms and Reports 10g installation. Ensure that you are using same oraInventory that was created during Oracle E-Business Suite Release 12 installation.

Step 3.1.1: Unzip the Patchset

Unzip patch 5983622 into a temporary directory.

Step 3.1.2: Apply OracleAS 10g Release 2 Patchset 3 (10.1.2.3.0)

The following steps will apply the patchset.
Step 3.1.2.1: Execute runInstaller or setup.exe
Execute runInstaller (UNIX) or setup.exe (Windows) and choose "Oracle Application Server and Developer Suite 10g R2 Software Update 10.1.2.3.0" as the install option.
On Linux and UNIX:

If you have a Global Inventory, invoke the Installer by changing to the appropriate directory and running the command:
$ ./runInstaller

If you have a Local Inventory, invoke the Installer by changing to the appropriate directory running the command:
$ ./runInstaller -invPtrLoc <1012_ORACLE_HOME>/oraInst.loc

On Windows, invoke the setup.exe program with the following command:
<patch-top>/Disk1/setup.exe
Step 3.1.2.2: Supply the ias_admin default password
Supply the ias_admin default password 'secret' when prompted.
Note: You may see failures while executing OC4J configuration assistant as part of post install configuration steps. Please select Next to skip the configuration assistant. This action will skip the remaining configuration assistants, which is expected for Oracle E-Business Suite customers.
Step 3.1.2.3: Shut Down Services Started by OUI during 10.1.2.3 Patchset Installation
During OracleAS 10g patchset 10.1.2.3 installation, Oracle Universal Installer may have started some processes from the OracleAS 10.1.2 Oracle Home. Before proceeding further, ensure you shut down any processes started by the Installer.
Export ORACLE_HOME=<10.1.2 Oracle Home>
$ORACLE_HOME/opmn/bin/opmnctl stopall
$ORACLE_HOME/bin/emctl stop iasconsole
Do not source the environment using any of the Applications environment files.

Step 3.2: Install Forms Bundle Patch

  • Use opatch to install forms bundle patch 9593176 downloaded in Step 2.1.2. Use opatch version 1.0.0.0.63 or higher.
    • You can download the latest version of opatch via patch 6880880. Make sure to choose release 10.1.0.0.0 from the release dropdown list before downloading.
    • You may want to upgrade OUI version before upgrading opatch version. Follow the readme to install the OUI 10.1 upgrade patch6640838.
    • README of Bundle Patch is not applicable to E-Business Suite Customers. Follow the post installation instructions given in Section 4 after applying the patch.
Note: You can safely ignore conflicts against the following MLRs while applying Forms Bundle Patch:
List of MLRs: 7229760, 8217396, 8374931, 8920655, 8970798, 9044638, 9126011, 9295268, 9569336, 9727465, 9768296, 9876820.

Step 3.3: Install the Additional Patches

Use opatch to install each of the additional patches you downloaded in Step 2.1.2, in the same order as in the table, and following the instructions in the accompanying README. Use opatch version 1.0.0.0.63 or higher. You can download the latest version of opatch via patch 6880880.

Step 3.4: Download and apply 10.1.0.5 RSF fixes

Note:
  • You must select 10.1.0.5 from the Release dropdown list before downloading.
  • Windows Customers do not need to apply any of the patches listed in Step 3.4.
  • "IBM: Linux on System z" customers need to apply only 5261796 mentioned in Step 3.4.3 and skip all other patches.

Step 3.4.1: Download patch 3559326

Download patch 3559326 from My Oracle Support and apply to the OracleAS 10.1.2 Oracle Home.

Step 3.4.2: Download patch 5394728

Download patch 5394728 from My Oracle Support and apply to the OracleAS 10.1.2 Oracle Home.

Step 3.4.3: Download patch 5261796

Download patch 5261796 from My Oracle Support and apply to the OracleAS 10.1.2 Oracle Home.

Step 3.4.4: Download patch 5651245

Download patch 5651245 from My Oracle Support and apply to the OracleAS 10.1.2 Oracle Home.
Note: If you are upgrading from 10.1.2.0.2 version, please execute the following steps as applications file system owner before applying5651245.
touch $ORACLE_HOME/bin/genoccish; chmod +x $ORACLE_HOME/bin/genoccish

Step 3.4.5: Download patch 5123798 (HP-UX PA RISC and HP-UX Itanium platforms only)

Download patch 5123798 from My Oracle Support and apply to the OracleAS 10.1.2 Oracle Home.

Step 3.5: Download and apply patch 6400501 (Oracle11g Database customers only)

Customers who are running Oracle Database 11g need to download patch 6400501 for Database 10.1.0.5, and apply it to the OracleAS 10.1.2 Oracle Home. This one-off is originally applied as part of the 11g database upgrade, which is rolled back by the OracleAS 10.1.2.3 patchset.
Note: Windows customers need to apply patch 7379122 (10.1.2.3 CPU patch for October 2008) instead of 6400501.

Step 3.6: Download and apply oraparam.ini fix (IBM AIX, HP-UX PA RISC, and HP-UX Itanium platforms only)

There is an issue with the oraparam.ini file on some platforms. Download and apply the relevant patch to avoid any related issues.
  • IBM AIX customers need to download and apply patch 7458104 for OracleAS 10.1.2 Oracle Home
  • HP-UX PA-RISC customers need to download and apply patch 7518185 for OracleAS 10.1.2 Oracle Home
  • HP-UX Itanium customers need to download and apply patch 7518188 for OracleAS 10.1.2 Oracle Home

Step 3.7: Restore zip utility after upgrade (IBM AIX platforms only)

If you had performed the step 2.5, restore the zip executable.
cd $ORACLE_HOME/bin

mv zip_ORIG zip

Step 3.8: Apply the Oracle E-Business Suite Release 12 Interoperability Patch

Step 3.8.1: Enable Maintenance Mode from adadmin

Before applying the patch, you must enable Maintenance Mode:
  1. Run adadmin
  2. Select menu option 5 (Change Maintenance Mode)
  3. Select menu option 1 (Enable Maintenance Mode)

Step 3.8.2: Apply the Oracle E-Business Suite/Forms Interoperability Patch

Apply the patch driver from the Interoperability patch using AutoPatch.

Step 3.8.3: Disable Maintenance Mode from adadmin

After applying the patch, disable Maintenance Mode:
  1. Run adadmin
  2. Select menu option 5 (Change Maintenance Mode)
  3. Select menu option 2 (Disable Maintenance Mode)

Section 4. Post-Installation Steps


Step 4.1: Redeploy the new Forms EAR file

Redeploy the formsapp.ear file by following the instructions given in My Oracle Support Knowledge Document 397174.1, "Deploying a New Forms EAR File in Oracle Applications Release 12".
Note: "IBM: Linux on System z" customers need to apply patch 9955717 to fix issue with forms ear deployment.

Step 4.2: Rebuild Forms and Reports executables

Rebuild Forms and Reports executables:
cd $ORACLE_HOME/forms/lib32
Note: if this directory does not exist: cd $ORACLE_HOME/forms/lib
$ make -f ins_forms.mk install

cd $ORACLE_HOME/reports/lib32
Note: if this directory does not exist: cd $ORACLE_HOME/reports/lib
$ make -f ins_reports.mk install

Step 4.3: Regenerate JAR files

Step 4.3.1: Verify the JAR files have been rebuilt

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.

Step 4.3.2: Regenerate the JAR Files (if required)

If the timestamp is not current but the installation steps completed successfully, run the AD Administration Utility to regenerate the JAR files:
  1. Run the AD Administration Utility (adadmin)
  2. Select Generate Applications Files
  3. Generate Product JAR Files
Note: Do not opt to force the regeneration of all JAR files.
Verify that the fndforms.jar and fndewt.jar JAR files have been rebuilt by checking their timestamps again.

Step 4.4: Start All Services

Use the following command to start all services:
$ADMIN_SCRIPTS_HOME/adstrtal.sh

Step 4.5: Verify the Upgrade

To verify that your forms upgrade has been successful, use one or both of the methods below:

Step 4.5.1: Check "About Applications"

Log on to E-Business Suite as any user, launch any form, select "About Applications" from the Help menu, and confirm that the Forms version (under Forms Server) shows as 10.1.2.3.0.

Step 4.5.2: Run Forms compiler

Run the following command to display various component versions, and confirm that the Forms version shows as 10.1.2.3.0. This command requires the DISPLAY environment variable to be set correctly.
$ORACLE_HOME/bin/frmcmp help=y

Section 5. Known Issues


Step 5.1: "FRM-92150:WEB Client Version too new" error prior to applying One-Offs

On Unix platforms, trying to run Oracle E-Business Suite Release 12 with the OracleAS 10g 10.1.2.3 patch before application of the recommended one-off patches specified in section 2, may see error "FRM-92150:WEB Client Version too new", while launching forms .
To fix this problem on Linux, rebuild the shared libraries with the following commands:
cd $ORACLE_HOME/forms/lib
make -f ins_forms.mk sharedlib
To fix this problem on other UNIX platforms, use the commands:
cd $ORACLE_HOME/forms/lib32
make -f ins_forms.mk sharedlib
Note: If you have followed the instructions in this document, you will not see this problem because the recommended one-off patches relink the shared libraries. However, it is possible you may wish to run without the one-offs for testing or diagnostic purposes.

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

Step 5.3: Forms server issue with socket mode setup

Customers who are using forms in Socket Mode and also using some port scanning tool (e.g. nmap, Webkeeper) may see Forms Server spinning and does not spawn new frmweb process. The issue was reported on IBM AIX. Customers on IBM AIX can download and apply patch 9913966. If any customer needs this patch for any other platform, please log a Service Request with Oracle Support requesting the same.

Step 5.4: REP-1814: Report cannot be formatted. Object 'vertically' can never fit within 'PH_TX1'

Oracle E-Business Suite customers may experience following issue with forms and reports 10.1.2.3 on IBM AIX .
Postscript reports errored out with error REP-1814.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1814: Report cannot be formatted. Object 'vertically' can never fit within 'PH_TX1'.
Customers on IBM AIX can download and apply patch 6666795 to resolve this issue.


References:

Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12 [ID 437878.1]


Get Oracle Certifications for all Exams
Free Online Exams.com

No comments: