Monday 22 September 2014

JRE Plugin Upgrade to 1.7.0_21 in R12.1.3

Step 1 : Download Java RunTime  Update 21 (Java JRE 1.7.0_21) for Java Client upgrade from webpage mentioned below : (Java SE Runtime Environment 7u21)

 Windows x64
31.59 MB  
jre-7u21-windows-x64.exe
 Windows x86 Offline
30.2 MB  

Check current Jre version:

cat $FORMS_WEB_CONFIG_FILE|grep sun_plugin_version

sun_plugin_version=1.6.0_07

or.. check as below:

[appluat@erptest ~]$ grep -i plugin $CONTEXT_FILE
         <!-- JDK plugins -->
         <sun_plugin_ver oa_var="s_sun_plugin_ver">1.6.0_07</sun_plugin_ver>
         <sun_plugin_type oa_var="s_sun_plugin_type">jdk</sun_plugin_type>

·         Step 2 : Take the backup of the bellow files

Login to OS user appltest from PUTTY-

$ cd/u01/appltest/VIS/apps/apps_st/appl
$ . APPSVIS_erpdemo.env

$ cd /u01/appltest/VIS/inst/apps/VIS_erpdemo/appl/admin/
$ cp –rp VIS_erpdemo.xml VIS_erpdemo.xml-org_14_aug_2014

$ cd $COMMON_TOP
$ cp –rpwebapps webapps-org_14_aug_2014

$ cd $TNS_ADMIN
$ cp –rptnsnames.ora tnsnames.ora-org_14_aug_2014
$ cp –rplistener.ora listener.ora-org_14_aug_2014
  • Step 3 :Migrate the file to the TEST Application server location  $COMMON_TOP/webapps/oacore/util/jinitiator
Login to the putty using appltest user
$ cd /u01/appltest/VIS/apps/apps_st/appl
$ . APPSVIS_erpdemo.env
$ cd $COMMON_TOP/webapps/oacore/util/jinitiator
$ pwd
/u01/appltest/VIS/apps/apps/apps_st/comn/webapps/oacore/util/jinitiator

After that connect to the FTP session with appltest
and move the downloaded file to  ($COMMON_TOP/webapps/oacore/util/jinitiator)

/u01/appltest/VIS/apps/apps/apps_st/comn/webapps/oacore/util/jinitiator
location.

After that rename the jre file name on the same putty location

jre-7u21-windows-x64.exe  would be renamed j2se17021.exe

$ cd $COMMON_TOP/webapps/oacore/util/jinitiator
$ mv jre-7u21-windows-x64.exe  j2se17021.exe


  • Step 4 :Shut down the application services and Enable Maintenance Mode from adadmin utility.
Login to the application OS user (appltest) from PUTTY-
$ cd /u01/appltest/VIS/apps/apps_st/appl
$ . APPSVIS_erpdemo.env
$ cd $ADMIN_SCRIPTS_HOME
$ adstpall.sh apps/<apps_password>     ( i.e – adstpall.sh apps/apps )
$ ps –ef | grep FND | wc –l
When the output comes 1 then go with the next command
$ adadmin
Is this the correct APPL_TOP [Yes] ?[ TYPEENTER ]
Filename [adadmin.log] :[ TYPE ENTER ]
Do you wish to activate this feature [No] ?[ TYPE ENTER ]
Please enter the batchsize [1000] :[ TYPE ENTER ]
Is this the correct database [Yes] ?[ TYPE ENTER ]
Enter the password for your 'SYSTEM' ORACLE schema:[ TYPE THE DB system password ]
Enter the ORACLE password of Application Object Library [APPS] :[TYPE APPS PASSWORD]
1.    Generate Applications Files menu
   2.    Maintain Applications Files menu
   3.    Compile/Reload Applications Database Entities menu
   4.    Maintain Applications Database Entities menu
  5.    Change Maintenance Mode
   6.    Exit AD Administration
Enter your choice [6] :[ select 5 option ]
Please select an option:
  1.    Enable Maintenance Mode
 2.    Disable Maintenance Mode
   3.    Return to Main Menu
Enter your choice [3] :[ select 1 option ]
Enter your choice [3] :[ select 3 option ]
Enter your choice [6] :[ select 6 option ]

Step:5 Check Oracle_Home 10.1.2 version:

cd $ORACLE_HOME/config     ( this is 10.1.2 Oracle_Home)
[appltst@erptest ~]$ cd /u10/appltst/TEST/apps/tech_st/10.1.2/config
[appltst@erptest config]$ cat ias.properties |grep Version
Version=10.1.2.3.0

If you are on  Version=10.1.2.2.0 then you need upgrade it to 10.1.2.3.0
Follow below doc.
Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12 (Doc ID 437878.1)

Check forms server version:
$ORACLE_HOME/bin/frmcmp_batch|grep Forms| grep Version
Forms 10.1 (Form Compiler) Version 10.1.2.3.0 (Production)
Note: Several Forms 10.1.2.3.0 fixes have been consolidated in bundle patch 14825718. Customers are strongly recommended to uptake the bundle patch documented in Step 2.1.2. If customers are already on 10.1.2.3.0, follow instructions in Step 3.2 to apply the bundle patch.
If You are on Version=10.1.2.3.0 follow instructions in Step 3.2 to apply the bundle patch

You must upgrade OUI to the latest version before upgrading opatch version. Follow the README to install the OUI 10.1 upgrade patch 6640838.
While applying patch u may get pre requisite error for Operating system.
Sol:  go to Patch_top//cd/Disk1/install
Edit the oraparam.ini file with current Operating system details. Here I added redHat-5
add as below:
[Certified Versions]
Solaris=5.6,5.7,5.8,5.9
Linux=redhat-2.1AS,redhat-3,redhat-4,redhat-5
HPUX=B.11.11
Decunix=V5.1A,V5.1
AIX=5.1.0.0
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
Patch 6995251 is applicable only to Linux x86-64 customers. This patch must be applied before applying the latest forms bundle patch 14825718.

apply the latest forms bundle patch 14825718.

Before applying overlay patch 17303472, you must apply the latest forms bundle patch 14825718
(Patch 14825718 is the latest forms bundle patch that includes the JRE 7 fix from Patch14614795.)

Rebuild Forms and Reports Executables (Conditional)

Note: This step is not applicable for Windows Platform.

Source the environment (under $INST_TOP/ora/10.1.2) to point to the 10.1.2 Oracle Home before relinking 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

Regenerate JAR files

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.

  • Step 6 :Download JRE Upgrade Interoperability Patch Number 14837539 for 12.1 customers
  •  and Apply the same using adpatch options. Also check patch 4377566 applied or not, if not apply this patch also.
First check this patch is applied or not

$ cd /u01/appltest/VIS/apps/apps_st/appl
$ . APPSVIS_erpdemo.env
$ sqlplus apps/appspass                     ( if apps password is different please put that one )
On sql prompt please run the following command –
SQL>select bug_number from ad_bugs where bug_number=’14837539;
If you find any output (like 14837539 ) then please forget this patch and go with the step 6 otherwise go with the following process
Download above patch 14837539 for Linux x86-64 platform
Exit from SQL prompt type
SQL>exit
$ cd 14837539
$ adpatch
Is this the correct APPL_TOP [Yes] ?[ TYPE ENTER ]
Filename [adadmin.log] :   u14837539.log
Do you wish to activate this feature [No] ?[ TYPE ENTER ]
Please enter the batchsize [1000] :[ TYPE ENTER ]
Is this the correct database [Yes] ?[ TYPE ENTER ]
Enter the password for your 'SYSTEM' ORACLE schema:[ TYPE THE DB system password ]
Enter the ORACLE password of Application Object Library [APPS] :[TYPE APPS PASSWORD]
The default directory is [/home/appltest/14837539] :[TYPE APPS PASSWORD]
Please enter the name of your AutoPatch driver file :  u14837539.drv
Enter the number of parallel workers (30) :  20
After applying the patch please go with next step, if not please concern with any DBA.
  • Step 7:  Login to Application backend and Run the $FND_TOP/bin/txkSetPlugin.sh script against the web node of the application tier.
In the same $ prompt please run the following script (shtxkSetPlugin.sh will run autoconfig, if u want to skip autoconfig, edit the configuration file appsweb.cfg and CONTEXT_FILE abd FORMS_WEB_CONFIG_FILE manually) better run shtxkSetPlugin.sh
$ cd$FND_TOP/bin/
$ shtxkSetPlugin.sh 17021
The script will prompt you for the following values, if it does not find them automatically:
o    Location of APPSVIS_erpdemo.envfile, if not present in the default location $APPL_TOP
o    Location of the Auto-Config Context File.
o    Password for the APPS user in the database (If the correct value is returned by the script you may press the return key at the prompt).
Confirm jre upgraded in all configuration files :
[appltst@erptest ~]$ grep -i plugin $CONTEXT_FILE
         <!-- JDK plugins -->
         <sun_plugin_ver oa_var="s_sun_plugin_ver">1.7.0_21</sun_plugin_ver>
         <sun_plugin_type oa_var="s_sun_plugin_type">jdk</sun_plugin_type>

[appltst@erptest ~]$ cat $FORMS_WEB_CONFIG_FILE|grep sun_plugin_version
sun_plugin_version=1.7.0_21
  • Step 7 : Disable Maintenance Mode from adadmin and Start the Application services
$ adadmin
Is this the correct APPL_TOP [Yes] ?[ TYPE ENTER ]
Filename [adadmin.log] :[ TYPE ENTER ]
Do you wish to activate this feature [No] ?[ TYPE ENTER ]
Please enter the batchsize [1000] :[ TYPE ENTER ]
Is this the correct database [Yes] ?[ TYPE ENTER ]
Enter the password for your 'SYSTEM' ORACLE schema:[ TYPE THE DB system password ]
Enter the ORACLE password of Application Object Library [APPS] :[TYPE APPS PASSWORD]
1.    Generate Applications Files menu
   2.    Maintain Applications Files menu
   3.    Compile/Reload Applications Database Entities menu
   4.    Maintain Applications Database Entities menu
  5.    Change Maintenance Mode
   6.    Exit AD Administration
Enter your choice [6] :[ select 5 option ]
Please select an option:
  1.    Enable Maintenance Mode
 2.    Disable Maintenance Mode
   3.    Return to Main Menu
Enter your choice [3] :[ select 2 option ]
Enter your choice [3] :[ select 3 option ]
Enter your choice [6] :[ select 6 option ]

After disabling the maintenance mode then start the services.
$ adstrtal.sh apps/<apps_password>
$adopmnctl.sh status
You are running adopmnctl.sh version 120.6.12010000.5
Checking status of OPMN managed processes...
Processes in Instance: TRAIN_trn.trn.evosys.co.in
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |   15238 | Alive
OC4JGroup:default_group          | OC4J:forms         |   15169 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   15007 | Alive
HTTP_Server                              | HTTP_Server        |   14949 | Alive
adopmnctl.sh: exiting with status 0
If all the services are showing alive then go with next step.
  • Step 8 :Login to the application and open up any Oracle Form (It will automatically ask you for installing the new Java Plug-in 1.7.0_21).

  • Step 9 : Install the upgraded Java Plug-in for client machine and re-test the issue.

--------------------------------------------------------------------------------------------------------------------------

References


Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 [ID 393931.1]
                                                      https://blogs.oracle.com/stevenChan/entry/java_jre_1_7_04

Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12 (Doc ID 437878.1)

2 comments:

  1. Hi,

    I am trying to upgrade from JRE 1.6.0_07 to JRE 1.7.0_79. Application version is 12.1.3 and OS is AIX 6.1
    I followed each required step metion above and in doc id 393931.1 Also txkSetPlugin.sh completed successfully but the parameter s_sun_plugin_ver in context file still showing old JRE value i.e. 1.6.0_07 and forms are opening with JRE 6 only.

    Please suggest.

    Regards,
    Mohsin Shekh

    ReplyDelete
  2. Hi ,
    Thanks for the post , it is good , may i know why 10.1.0.5 RSF fixes and forms overlay patch were ignored in the doc id 437878.1

    ReplyDelete