Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i

1. Download the JRE Plug-in interoperability patch - 6863618

2. Download the Sun JRE Plug-in -

1. jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe

or

2. jre-6u12-windows-i586-p.exe

3. Rename the JRE Plug-in and Place it on Webserver

jre-1_5_0_17-windows-i586-p.exe

X means current updated version,

Example

jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe

If you have more then one apps node, need to place all nodes.

4. Shutdown Apps tier

5. Place the JRE 5 Plug-in on the Web Application Tier

Use FTP or WINSCP Tool

Move the jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe file to the web application tier and place it in all apps nodes

$COMMON_TOP/util/jinitiator


6. Enable Maintenance Mode

We have forms 18 patchset, so that i applied following patch for JRE upgrade, If you have less then forms patch 18, first you should upgrade forms 18 or later. If you have forms 19 or later please follow the metalink note id: 290807.1

Developer 6i Patchset 18 Users

Developer 6i Patchset 18 (6.0.8.27.x) users must apply the forms focus fix patches 7362389 and 5884875.


7. Apply Prerequisite Patche 7362389

Note: Just follow the patch readme.

8. Apply Prerequisite Patch 5884875

Note: Just follow the patch readme.


8. Apply JRE Interoperability Patch - 6863618 - Use adpatch

Apply the Patch Driver

If you are upgrading to the JRE native plug-in for the first time, please apply the interop patch using AutoPatch.

Multiple Application-Tier Web Server Nodes

If you have multiple web application tier server nodes, repeat the steps above to apply the patch driver in the JRE Interoperability Patch against all other web application tier server nodes.

9 . Run below script on command prompt

Run the txkSetPlugin.sh script from the //fnd/bin/ directory, against the web node of your middle tier, where is the directory in which you unzipped this patch.

Run the txkSetPlugin.sh Script

$txkSetPlugin.sh 15017
It will ask following input from you, please provide right path.

/u01/oracle/appltestAPPSORA.env
/u01/oracle/appltest/admin/DBA_oraappsdba.xml
Password for the APPS user in the database :apps

Example:
[applmgr@testoraapps bin]$ txkSetPlugin.sh 15017
/u01/oracle/testappl/fnd/11.5.0/bin

Starting interoperability upgrade script...

Sending logfile output to:
/u01/oracle/testappl/admin/log/txkSetPlugin.log
Using the context file:
/u01/oracle/testappl/admin/u01_oraappsu01.xml
Using APPLSYS file:
/u01/oracle/testappl/APPSu01_oraappsu01.env
Enter the password for the Oracle database APPS user [APPS] : apps

Using /u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/bin/java to execute java programs

Getting J2SE parameter values...

Copy oaj2se.exe to html dir...

Copying /u01/oracle/u01comn/util/jinitiator/j2se15017.exe to /u01/oracle/u01comn/html/oaj2se.exe ...

Backing up the Application Context File...

Backing up /u01/oracle/testappl/admin/u01_oraappsu01.xml to /u01/oracle/testappl/admin/u01_oraappsu01.xml.prej2se15017
Using APPSWEB file /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg
Backing up the appsweb file...
Backing up /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg to /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg.prej2se15017
Updating XML context file with new parameters...
Updated Plug-in type to jdk
Updated JInitiator version name to 1.5.0_17
Updated JInitiator mimetype to 1.5.0_17
Updated JInitiator classid to CAFEEFAC-0015-0000-0017-ABCDEFFEDCBA
Updated J2SE mimetype to 1.5.0_17
Updated J2SE Classid to CAFEEFAC-0015-0000-0017-ABCDEFFEDCBA

The log file for this session is located at: /u01/oracle/testappl/admin/u01_oraappsu01/log/04280720/adconfig.log

AutoConfig is configuring the Applications environment...

AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /u01/oracle/testappl
Classpath : /u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/jre/lib/rt.jar:/u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/lib/dt.jar:/u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/lib/tools.jar:/u01/oracle/u01comn/java/appsborg2.zip:/u01/oracle/u01comn/java

Using Context file : /u01/oracle/testappl/admin/u01_oraappsu01.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Configuring templates from all of the product tops...
Configuring AD_TOP........COMPLETED
Configuring FND_TOP.......COMPLETED
Configuring ICX_TOP.......COMPLETED
Configuring IEO_TOP.......COMPLETED
Configuring ABM_TOP.......COMPLETED
Configuring EAM_TOP.......COMPLETED
Configuring CSD_TOP.......COMPLETED
Configuring IGC_TOP.......COMPLETED

AutoConfig completed successfully.
Upgrading j2se15017 for Oracle Workflow...
Oracle Workflow upgraded successfully...
Done


10. Disable Maintenance Mode

11. Startup your apps nodes

11. Login apps, first it will take time to download for JRE.



Reverting to a Previous JRE Plug-in/JInitiator Version

If you wish to revert back to previously installed version of JRE to be used in your Application, please re-install the required version by re-running the txkSetPlugin script with the appropriate parameters. This will automatically overwrite the JRE parameters in the configuration files.

To revert back to a version of JInitiator, you must also run the txkSetPlugin script with the appropriate parameters and not the old jinit.sh or jinit.cmd scripts that were used for JInitiator upgrades previously. Using JInitiator 1.3.1.28 as an example the command would be;

UNIX Users

$ txkSetPlugin.sh 13121



Reference:

Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
Doc ID: 290807.1

After Cloning DB Tier Service Name Shows PROD Name

After Cloning DB Tier, Service Name shows like this. This wrong, So we need do the folloing steps.

Error Message:

sql > show parameter service

service_names string UAT, SYS$APPLSYS.WF_CONTROL.PROD.DOYENSYS.COM

Solutions:

Step 1: Bounce the Apps Tier.

Then Go to respective Directory.

/UAT/oracle/uatappl/fnd/11.5.0/patch/115/sql

$ ls -lrt wfctqrec.sql

-----wfctqrec.sql

step 2:
SQL> sqlplus apps/passwd

SQL> @wfctqrec.sql applsys passwd

Step 3: Bounce the DB and Listener in Both RAC Nodes

Setp 4: Start Both Nodes and Listener

Step 5: Now check the show parameter service, It shows


After finishing above tasks, its changed.

sql > show parameter service
service_names string UAT, SYS$APPLSYS.WF_CONTROL.UAT.DOYENSYS.COM

OR

sql > show parameter service
service_names string UAT

The listener failed to spawn the Service Manager process.

Error:

Concurrent Manager Output Post Processor unable to UP

The following error shows the ICM.log

Could not contact Service Manager FNDSM_orauat2_UAT. The TNS alias could not be located, the listener process on orauat2 could not be contacted, or the listener failed to spawn the Service Manager process.

Process monitor session started : 01-APR-2009 05:39:38Could not contact Service Manager FNDSM_orauat2_UAT. The TNS alias could not be located, the listener process on orauat2 could not be contacted, or the listener failed to spawn the Service Manager process.



Cause:

Here my one of the db instance is down(UAT1), so apps listener is try to check the UAT1 instacne. Buit its not able to connect that database. so that it will throug like this error.

UAT=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(POR1521)) (CONNECT_DATA=
(SERVICE_NAME=UAT)
(INSTANCE_NAME=UAT1)
)
)


UAT1=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT1521)) (
CONNECT_DATA=
(SERVICE_NAME=UAT)
(INSTANCE_NAME=UAT1)
)
)


UAT1_FO=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT1) ) )


UAT2= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )


Solutions

If its PCP enable node, please check the TNS entry.

So, Please chenge the instacne name UAT1 to UAT2. Then try to check the Concurrent Manager.


UAT= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )


UAT1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )


UAT1_FO= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT1) ) )


UAT2= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2)


Now, Ping the all the tns names
tnsping UAT
tnsping UAT2
tnsping FNDSM_orauat2.doyensys.com_DEV
tnsping FNDSM_orauat1.doyensys.com_DEV
tnsping FNDSM_orauat1_DEV

Moving Oracle DataBase Control files

Change the Control file Location of current palce to another place.


Existing initTEST.ora file Location.

SQL>select name from v$controlfile;

/oracle/product/10.1.4/oradata/control01.ctl,
/oracle/product/10.1.4/oradata/control02.ctl,
/oracle/product/10.1.4/oradata/control03.ctl

Note:
Change the control file to following order to existing initTEST.ora file.
If you using spfile, just create the init file and change the controlfile patch and shutdown the database.

cd $ORACLE_HOME/dbs/initTEST.ora

/oracle/product/10.1.4/oradata/control01.ctl,
/oracle/product/10.1.4/oradata/controlfile/controlfile
/ctlbkp/oracle/controlfile/control03.ctl

1. Bounce the Database
2. Change the controlfile new path in inittest.ora
3. Now move all the controlfile form respective place to new place, use MV command.
4. Now startup the Database
5. SQL> show parameter control or put below sql query.
6. Again create the spfile from pfile.


SQL> select name from v$controlfile;

/oracle/product/10.1.4/oradata/control01.ctl
/oracle/product/10.1.4/oradata/controlfile/control02.ctl
/ctlbkp/oracle/controlfile/control03.ctl

How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows

Action Plan for Migrate.

1 Take a cold backup and export full db or important schema
2 Take a backup of 10g binaries (Oracle Home)
3 Take a control file backup using command
Alter database backup controlfile to trace;
4 Take a backup of init.ora file
5 Prepare the current oracle directory structure
6 Clone Prod to Prod (32 bit O/S)
7 Install 64 bit Win O/S
8 Create existing oracle directory structure
9 Install 10g (10.2.0.1 Base) oracle binaries(Software Only),Upgrade 10.2.0.4 If you use exp/imp install with database
10 Please follow the Scenario 1 or 2 or 3


Scenario 1:


Oracle 10.2.0.1(32 Bit) to Oracle 10.2.0.1(64 Bit)

1. Install Oracle 10.2.0.1.0 64bit, on Windows 2003 64bit (either AMD64 or EM64T processors).
2. The same directory structure was used for both machines.
NOTE: If a different directory structure will be used, then you will need to recreate the controlfiles, before starting the migration process.

Alter database backup controlfiles to trace;

3. Copy the Database files from the 32bit machine, to the 64bit machine.
(Datafiles, Logfiles, Controlfiles, init.ora, tnsnames.ora, listener.ora, etc...)

4. Create the Oracle service on the 64bit system, using the ORADIM command.

(Eg, oradim –new –sid orcl –startmode auto –pfile

6.Run Sqlplus

sqlplus '/as sysdba'

SQL> startup upgrade

SQL>@$Oracle_Home\rdbms\admin\utlip.sql

SQL>@$Oracle_Home\rdbms\admin\utlrp.sql

SQL> shut immediate

SQL>startup

SQL>select name,platform_name,open_mode from v$database;


Scenario 2:


Oracle 10.2.0.1(32 Bit) to Oracle 10.2.0.4(64 Bit)


1. Install Oracle 10.2.0.1.0 64bit, on Windows 2003 64bit (either AMD64 or EM64T processors).

2. If you wish to apply a patchset, you can do that now. For this test, the 10.2.0.4 patchset was applied to the 64bit installation.

3. The same directory structure was used for both machines.
NOTE: If a different directory structure will be used, then you will need to recreate the controlfiles, before starting the migration process.

Alter database backup controlfile to trace;

4. Copy the Database files from the 32bit machine, to the 64bit machine.
(Datafiles, Logfiles, Controlfiles, init.ora, tnsnames.ora, listener.ora, etc..)

5. Create the Oracle service on the 64bit system, using the ORADIM command.
(Eg, oradim –new –sid orcl –startmode auto –pfile
6.Run Sqlplus

sqlplus '/as sysdba'

SQL> startup upgrade

SQL>@$Oracle_Home\rdbms\admin\utlip.sql

SQL>@$Oracle_Home\rdbms\admin\catupgrd.sql

SQL>@$Oracle_Home\rdbms\admin\utlrp.sql

SQL> shut immediate

SQL>startup

SQL>select name,platform_name,open_mode from v$database;


Note: 403522.1:- How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows


Scenario 3:

Steps to migrate 32 bit oracle 9i database to 64 bit 10g database:

1, Make backups of 32 bit 10g database.
Cold backup, export.

You need to have export file for migration. You can use user system to export entire database.

2, Install 64 bit Oracle 10g.

3, Create required tablespace, users etc.

4, Import 10g export dump file to 10g (from user=user1 to user=user1).


Steps

CONN sys/password@SID_NAME AS SYSDBA

1. Create Schema Name

2. ALTER USER U_NAME IDENTIFIED BY PASSWD ACCOUNT UNLOCK;
GRANT CREATE ANY DIRECTORY TO ;

3. CREATE OR REPLACE DIRECTORY DIR_NAME AS '/u05/oradata/';

4. GRANT READ, WRITE ON DIRECTORY DIR_NAME TO SCHEMA_NAME;

step:2

Schema Exports/Imports

expdp USER_NAME/PASSWD@SID_NAME schemas=SCHEMA_NAME directory=DIR_NAME dumpfile=INV.dmp logfile=EXPINV.log

impdp USER_NAME/PASSWD@SID_NAME schemas=SCHEMA_NAME directory=DIR_NAME dumpfile=INV.dmp logfile=IMPINV.log


Full Database Exports/Imports

expdp sys/password@SID_NAME full=Y directory=DIR_NAME dumpfile=FULLDB.dmp logfile=FULLDB10G.log

impdp sys/password@SID_NAME full=Y directory=DIR_NAME dumpfile=FULLDB.dmp logfile=FULLDB10G.log

Enterprise Manager DST Problem

Purpose

OEM agent suddently not running for daylight saving time changes.


Problem:

$ ./emctl start agent

Oracle Enterprise Manager 10g Release 10.2.0.1.0.

Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.

Starting agent ..... failed.

The agentTZRegion value in /oracle/app/em/agent10g/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.

If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository.

Consult the log files in: /oracle/app/em/agent10g/sysman/log


Solutions:

Download the Patch 5632264 for the latest version for your platform, DO NOT APPLY IT with opatch but:

Manually replace the oracore [/zoneinfo/timez*.dat] files in the Central Agent ORACLE_HOME:
Agent ORACLE_HOME

- backup the initial oracore files $ORACLE_HOME/oracore/[/zoneinfo/timez*.dat]

- replace the oracore [/zoneinfo/timez*.dat] files in the Central Agent ORACLE_HOME with the oracore [/zoneinfo/timez*.dat] files extracted from the patch


- ./emctl resetTZ agent

Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Updating /oracle/oracle/agent10g/sysman/config/emd.properties...
Successfully updated /oracle/oracle/agent10g/sysman/config/emd.properties.
Login as the em repository user and run the script:
exec mgmt_target.set_agent_tzrgn('oradiscprod.amestruetemper.com:3872','US/Eastern')
This can be done for example by logging into sqlplus and doing
SQL> exec mgmt_target.set_agent_tzrgn('oradiscprod.amestruetemper.com:3872','US/Eastern')

- start the Central Agent

./emctl start agent
./emctl status agent


Reference:
Enterprise Manager DST Quick Fix Guide: 418792.1

Oracle Apps DBA: Using srvctl to Manage your 10g RAC Database

Oracle Apps DBA: Using srvctl to Manage your 10g RAC Database