Output Post Processor (OPP) in Oracle Applications R12 and 11i

What is Output Post Processor?

Concurrent Processing now uses the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests.Post-processing actions are actions taken on

concurrent request output. An example of a post-processing action is that used in Concurrent Processing support of XML Publisher.

If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running

the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

OPP runs as a service that can be managed through Oracle Applications Manager (OAM) from the System Activity page (Navigation: Applications Dashboard > Applications

Service (from the dropdown list) > Go).

How to Increase the number of Output Post Processors?
1.Log on to Applications with “System Administrator” responsibility.
2.Navigate to Concurrent -> Manager -> Define.
3.Query for the “Output Post Processor” service.
4.Click on “Work Shifts” and increase the number of processes

How to get OPP manager log file location?

$APPLCSF/log/<SID>/FNDOPP####.txt OR
1,System Administrator > Concurrent > Manager > Administer
2,Search for ‘Output Post Processor’
3,Click the ‘Processes’ button .
4,Click the Manager Log button. This will open the ‘OPP’
Upload the OPP log file.

In some cases, Output Post Processor is not start up and it shows Actual and Target are showing different values when we query for Output Post Processor.
The log files shows that no error message.In this case apply the following possible solution for starting the OPP.

1. Shutdown the internal manager by using adcmctl.sh stop apps/apps
2. Make sure there is no FNDLIBR processe running:
$ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR
3. If there is any FNDLIBR processe please kill it $ kill -9 pid
4. Run cmclean.sql script as document from Note 134007.1
5. Restart the internal manager by using adcmctl.sh start apps/apps

or How to kill and start Output Post Processor (OPP) Background:
This article explains how to kill OPP and restart the same

Solution:
1,System Administator > Concurrent > Manager > Administer
2,Query "Output Post Processor" -> Processes button
Get the sytem id of "Output Post Processor"
3,ps -ef|grep [system id]
4,kill -9 [system id] in Unix
5,System Administator > Concurrent > Manager > Administer
6,Query "Output Post Processor" -> Restart button

Fixing Output Post-processor actions failed issues in EBS R12

Environment: Oracle EBS 12.1.3, Oracle Database 11gR2, RedHat Linux5
Symptoms:

Users unable to open the out files.

Concurrent requests failed with “Post-processing of request failed error message”

One or more post-processing actions failed. Consult the OPP service log for details.

No further attempts will be made to post-process this request.

Cause:

The concurrent manager process was able to successfully invoke the Output Post-Processor (OPP) but encountered a timeout as the OPP takes longer than the value

assigned to complete the job.

Solution:

1,Increase the value of profile Concurrent: OPP Response Timeout . Bounce Apache and retest.
2,If the issue still exists, perform the following steps.
3,Increase the number of Output Post Processors as follows:
4,Increase the number of processes for Output Post Processor.
5,Additionally, ensure there is a setting of oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5 under Parameters.

For more details Please check metalink I.E oracle.support

Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout [ID 352518.1]
Ouput Post Processing Fails Due To java.lang.ThreadDeath [ID 427233.1]
Why Does OPP Intermittently Completes With Warnings and Error 'java.lang.OutOfMemoryError'? [ID 978495.1]

To know more this post is very nice http://knoworacleappsdba.blogspot.in/2012/07/all-about-output-post-processor-opp-in.html

How to start the Output Post Processing (OPP) in 11i
At least one OPP process active in the system. The concurrent processing uses the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests. For example, post-processing action is that used in publishing concurrent requests with XML Publisher.

Actually when you have submit a request with XML Publisher template specified as a layout for the concurrent request output. Once finishes the concurrent manager concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output

To activate the OPP follow these setps

The Profile Option "Concurrent: GSM Enabled" must be set to Y

Then:
1. Login to Apps with sysadmin responsibility
2. Navigate to: Concurrent -> Managers -> Define
3. Query for
Manager = 'Output Post Processor%'
or Short Name = FNDCPOPP
4. Check the checkbox "Enable" .
5. Click on 'Work Shifts button
6. see Work Shift of the OPP and
Set Processes = 1
and Parameters = oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
and Sleep Second = 30
7. Save

How to restart Oracle Apps 11i OPP via non unix command

It can be done using adcmctl.sh script only and there is no specific script for OPP. You can restart it from the application via (System Administrator responsibility > Concurrent > Manager > Administer), select "Output Post Processor" and click on the "Restart" button.

OPP Issue while generating the XML Output in apps 11i

Problem Description:
1, Few XML type concurrent programs taking long time and completed with warning OPP log file registered below error
Caused by: java.lang.ThreadDeath
2, CPU utilization taking 100% constantly while running the concurrent programs.

Cause
The java.lang.ThreadDeath error indicates that the Output Post Processor has reached its processing timeout.

Solution
The following configuration changes are recommended to optimize the environment for these type of reports:
1. Increase the value of the Concurrent: OPP Timeout profile option to 10800 seconds.

2. Enable the scalability feature of XML Publisher:

1. Login as SYSADMIN
2. Responsibility: XML Publisher Administrator
3. Function: Administration
4. Set the following properties:
5. Temporary Directory
6. Use XML Publisher's XSLT processor: True
7. Enable scalable feature of XSLT processor: True -- By default it’s false
8. Enable XSLT runtime optimization: True

> After changing the value also the problem still exist. As per the SR suggestion, we increased the java heap size from 1024M to 2048M.

a. Bring down the concurrent managers.

b. Use the Update statement below, for example:
update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

c. Bring concurrent managers up again

Please check below note's from oracle support

427233.1 :Output Post Processing Fails Due To java.lang.ThreadDeath
1268217.1: Output Post Processor (OPP) Log Contains Error “java.lang.OutOfMemoryError: Java heap space"
1266368.1: Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError"
978495.1: Why Does OPP Intermittently Completes With Warnings and Error 'java.lang.OutOfMemoryError'?
352518.1 :Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout
364547.1 :Troubleshooting Oracle XML Publisher For The Oracle E-Business Suite

R12.1.X File system:

R12.1.X File system:
======================

How to apply patch while you are in the middle of ADPATCH

How to apply patch while you are in the middle of ADPATCH
=================================================

1. Using the adctrl utility, shutdown the workers.
a. adctrl
b. Select option 3 "Tell worker to shutdown/quit"
2. Backup the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema
a. sqlplus applsys/<password>
b. create table fnd_Install_processes_back
as select * from fnd_Install_processes;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes_back;
select count(*) from fnd_Install_processes;
3. Backup the AD_DEFERRED_JOBS table.
a. sqlplus applsys/<password>
b. create table AD_DEFERRED_JOBS_back
as select * from AD_DEFERRED_JOBS;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;
4. Backup the .rf9 files located in $APPL_TOP/admin/<SID>/restart directory.
At this point, the adpatch session should have ended and the cursor should
be back at the Unix prompt.
a. cd $APPL_TOP/admin/<SID>
b. mv restart restart_back
c. mkdir restart
5. Drop the FND_INSTALL_PROCESSES table and the AD_DEFERRED_JOBS table.
a. sqlplus applsys/<password>
b. drop table FND_INSTALL_PROCESSES;
c. drop table AD_DEFERRED_JOBS;
6. Apply the new patch.
7. Restore the .rf9 files located in $APPL_TOP/admin/<SID>/restart_back
directory.
a. cd $APPL_TOP/admin/<SID>
b. mv restart restart_<patchnumber>
c. mv restart_back restart
8. Restore the FND_INSTALL_PROCESSES table which is owned by the APPLSYS
schema.
a. sqlplus applsys/<password>
b. create table fnd_Install_processes
as select * from fnd_Install_processes_back;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes;
select count(*) from fnd_Install_processes_back;
9. Restore the AD_DEFERRED_JOBS table.
a. sqlplus applsys/<password>
b. create table AD_DEFERRED_JOBS
as select * from AD_DEFERRED_JOBS_back;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;
10. Re-create synonyms
a. sqlplus apps/apps
b. create synonym AD_DEFERRED_JOBS for APPLSYS.AD_DEFERRED_JOBS;
c. create synonym FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;
11. Start adpatch, it will resume where it stopped previously.

How to apply patch while you are in the middle of patching:

=============================================
Summary

Sometimes when you are in the middle of applying a patch you may get adworkers errors or you can find out that a patch is missing.

So you need to apply a second patch (which solves the problem) in the middle of a running patch.

1. Use adctrl (option 3) to tell all the existing workers to QUIT

2. Use adctrl (option 5) to tell managers that all workers have QUIT. (Adpatch session ends!)

3. Backup tables applsys.ad_deferred_jobs and applsys.fnd_install_processes.
Login as APPLSYS user and execute:
ALTER "TABLE" applsys.ad_deferred_jobs "RENAME" TO ad_deferred_jobs_old;
ALTER "TABLE" applsys.fnd_install_processes "RENAME" TO fnd_install_processes_old;
ALTER "INDEX" applsys.ad_deferred_jobs_u1 "RENAME" TO ad_deferred_jobs_u1_old;
ALTER "INDEX" applsys.fnd_install_processes_u1 "RENAME" TO fnd_install_processes_u1_old;
4. Go to $APPL_TOP/admin/SID/ for example $APPL_TOP/admin/TEST/ and rename the existing directory "restart"

$mv restart restart.old

5. Use adpatch to apply the second/other patch.

6. Login as APPLSYS and revert back to the original tables, ad_deferred_jobs and fnd_install_processes
ALTER "TABLE" applsys.ad_deferred_jobs_old "RENAME" TO ad_deferred_jobs;
ALTER "TABLE" applsys.fnd_install_processes_old "RENAME" TO fnd_install_processes;
ALTER "INDEX" applsys.ad_deferred_jobs_u1_old "RENAME" TO ad_deferred_jobs_u1;
ALTER "INDEX" applsys.fnd_install_processes_u1_old "RENAME" TO fnd_install_processes_u1;
CREATE SYNONYM FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;
CREATE SYNONYM AD_DEFERRED_JOBS FOR APPLSYS.AD_DEFERRED_JOBS;
7. Replace the original restart directory:

cd $APPL_TOP/admin/SID/ for example $APPL_TOP/admin/TEST/
mv restart restart_new
mv restart.old restart

8. Run adpatch to continue the first patch (with continue session?Yes)

9. Use adctrl (option 2, will change status to “Fixed/Restart”) to restart the failed workers for first patch

What to do if a worker fails during adpatch application on R12:

=====================================================================

In a different window constantly monitor the patch worker using adctrl command.

1. set the application environment file of R12

2. run adctrl

check the status of the worker using option 1 [Show worker status].

If a worker fails.

1. Check adwork01.log [check the failed worker number] file under $APPL_TOP/admin//log directory for details about the error.

2. Fix the issue mentioned in worker file.

3. Use Option 2 [Tell worker to restart a failed job] to restart the failed job in adctrl window.

4. If the issue is fixed properly the worker will start and complete the job and your adpatch will continue executing.

Sometimes, you need to restart all the workers and exit the adpatch session and restart it from the failed location will do your job.

OACORE fails to start after increasing the JVM processes in Oracle R12

OACORE fails to start after increasing the JVM processes in Oracle R12:
========================================================

Issue: OACORE processes are not starting.

Recent changes: Increased the JVM processes in the context file.
Error:
adoacorectl.sh: exiting with status 206
Solution:

1) Stop the middle tier processes:

adopmnctl.sh stop

2) Kill any runaway/zombie processes.

3) Remove the following jms lock files:

$ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence/forms_default_group_1/jms.state.lock,

$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/jms.state.lock

$ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/oafm_default_group_1jms.state.lock

4) Restart middle tier:
adopmnctl.sh start

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

Executing service control script:
/u01/applR12/inst/apps/TEST_linuxerp1/admin/scripts/adoacorectl.sh start
script returned:
****************************************************

You are running adoacorectl.sh version 120.13

Starting OPMN managed OACORE OC4J instance ...

adoacorectl.sh: exiting with status 204

adoacorectl.sh: check the logfile /u01/applR12/inst/apps/TEST_linuxerp1/logs/appl/admin/log/adoacorectl.txt for more information ...

[applerp@linuxerp1 scripts]$ adopmnctl.sh status

You are running adopmnctl.sh version 120.6

Checking status of OPMN managed processes...

Processes in Instance: TEST_linuxerp1.linuxerp1.orasol.com
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |   12478 | Alive
OC4JGroup:default_group          | OC4J:forms         |   12394 | Alive
OC4JGroup:default_group          | OC4J:oacore        |     N/A | Down
HTTP_Server                      | HTTP_Server        |   12147 | Alive

adopmnctl.sh: exiting with status 0

adopmnctl.sh: check the logfile /u01/applR12/inst/apps/TEST_linuxerp1/logs/appl/admin/log/adopmnctl.txt for more information ...

[applerp@linuxerp1 scripts]$

Error Stack when trying to stop:

Executing service control script:
/u01/applR12/inst/apps/TEST_linuxerp1/admin/scripts/adoacorectl.sh stop
script returned:
****************************************************

You are running adoacorectl.sh version 120.13

Stopping OPMN managed OACORE OC4J instance ...

adoacorectl.sh: exiting with status 150

adoacorectl.sh: check the logfile /u01/applR12/inst/apps/TEST_linuxerp1/logs/appl/admin/log/adoacorectl.txt for more information ...

Solution:
=> Stop application services
=> Clear contents of the persistence directory
=> Start application services

[applerp@linuxerp1 scripts]$ cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore

[applerp@linuxerp1 oacore]$ ls
application-deployments config persistence tldcache
[applerp@linuxerp1 oacore]$ rm -rf persistence/
You have new mail in /var/spool/mail/applerp
[applerp@linuxerp1 oacore]$ mkdir persistence

[applerp@linuxerp1 scripts]$ adopmnctl.sh status

You are running adopmnctl.sh version 120.6

Checking status of OPMN managed processes...

Processes in Instance: TEST_linuxerp1.linuxerp1.orasol.com
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |   13872 | Alive
OC4JGroup:default_group          | OC4J:forms         |   13804 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   13723 | Alive
HTTP_Server                      | HTTP_Server        |   13671 | Alive

adopmnctl.sh: exiting with status 0

adopmnctl.sh: check the logfile /u01/applR12/inst/apps/TEST_linuxerp1/logs/appl/admin/log/adopmnctl.txt for more information ...

[applerp@linuxerp1 scripts]$

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

adoacorectl.sh: exiting with status 150
Error:

[oracle@svrebsal2 scripts]$ ./adoacorectl.sh stop
You are running adoacorectl.sh version 120.13
Stopping OPMN managed OACORE OC4J instance ...

adoacorectl.sh: exiting with status 206

(OR)

adoacorectl.sh: exiting with status 150

Solution :

stop all R12 procs

rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/*
rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/*
rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence/*

start all service again (Start the oc4j using opmnctl startall)

++++++1177323.1, 1313955.1,1557461.1+++++++++

OACORE fails to start after increasing the JVM processes in Oracle R12

Issue: OACORE processes are not starting.

Recent changes: Increased the JVM processes in the context file.

Error:

adoacorectl.sh: exiting with status 206

Solution:

1) Stop the middle tier processes:

adopmnctl.sh stop

2) Kill any runaway/zombie processes.

3) Remove the following jms lock files:

$ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence/forms_default_group_1/jms.state.lock,

$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/jms.state.lock

$ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/oafm_default_group_1jms.state.lock

4) Restart middle tier:
adopmnctl.sh start

----------------------
\
SOLUTION:

To implement the solution, the recommendation is to:
1. $FF_TOP/bin/FFXBCP APPS/passwd 0 Y -W %% %%
2. sqlplus APPS/passwd @$FF_TOP/patch/115/sql/ffgenwrap.sql

This will recompile all formulas, then regenerate the formula wrappers. It is not recommended to
skip 1.
-----------------

Solution

1) Oracle Fast Formulas can be compiled in bulk with the following command:

$FF_TOP/bin/FFXBCP <appsuser>/<appspassword> 0 Y %% %%

Example:
$FF_TOP/bin/FFXBCP apps/apps 0 Y %% %%

NOTE: 0 = zero

2) Or Groups of Formulae may be compiled. For example 'VERTEX':

$FF_TOP/bin/FFXBCP apps/apps 0 Y %% %VERTEX%

3) Formulas can also be compiled through the Oracle Payroll application by running the concurrent process Bulk Compile of Formulas.

Navigate: Processes and Reports -> Submit Processes and Reports
Select Bulk Compile of Formulas
How To Compile Oracle Fast Formulas (Doc ID 155737.1)

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

adoafmctl.sh: exiting with status 204
One of our site i need to change SERVER IP address in Oracle application r12 on linux 5.

I changed IP address on both server ( we have two server 1. db server 2. application server)

after changing the server IP when we are trying to start application service, application service ended with below error message:
adoafmctl.sh: exiting with status 204

Cause: Server IP address change

Solution:
Step:
1. logon to application server with applmgr user
2. go to $INST_TOP
3. stop application services ($ cd $INST_TOP/admin/scripts )
4. delete following files
rm -rf $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/*
rm -rf $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/*
rm -rf $INST_TOP/ora/10.1.3/j2ee/forms/persistence/*

4. execute autoconfig on application tier
$cd $INST_TOP/admin/scripts
$. ./autoconfig {hit enter}

5. start all application services
6. re-test the issue

----------------------------------------------------------------------------
Unable to start oafm using adstrtal.sh. Running adoafmctl.sh ends with timeout.

You are running adoafmctl.sh version 120.6.12000000.3
Starting OPMN managed OAFM OC4J instance ...
adoafmctl.sh: exiting with status 152
adoafmctl.sh: check the logfile
/opt/apphcm/inst/apps/SID_machine/logs/appl/admin/log/adoafmctl.txt for more information

adoafmctl.txt showing:

ias-component/process-type/process-set:
default_group/oafm/default_group/
Error
--> Process (index=1,uid=349189076,pid=15039)
time out while waiting for a managed process to start
Log:
/opt/apphcm/inst/apps/SID_machine/logs/ora/10.1.3/opmn/default_group~oafm~default_group~1
07/31/09-09:14:28 :: adoafmctl.sh: exiting with status 152
================================================================================
07/31/09-09:14:40 :: adoafmctl.sh version 120.6.12000000.3
07/31/09-09:14:40 :: adoafmctl.sh: Checking the status of OPMN managed OAFM OC4J instance
Processes in Instance: SID_machine.machine.domain
-------------------+--------------------+---------+---------
ias-component | process-type | pid | status
-------------------+--------------------+---------+---------
default_group | oafm | N/A | Down

CAUSE
Existing JSP Tag Library Cache content was preventing the TLD Cache for the mapviewer app from initialising correctly.

Solution:

=======To implement the solution, please execute the following steps:

Clear the TLD cache:

- stop all middle tier services

- Delete/backup the file:

$COMMON_TOP/_TldCache

- start all middle tier services

How to Find component Version in Oracle Apps 11i/R12:

Find component Version in Apps 11i/R12:

Q. How to find Apps Version (11i/R12/12i).
A. Connect to database as user apps
SQL> select release_name from apps.fnd_product_groups;
Output like 12.0.4 or 11.5.10.2

Q. Web Server/Apache or Application Server in Apps 11i/R12
A. Log in as Application user, set environment variable and run below query$IAS_ORACLE_HOME/Apache/Apache/bin/httpd -version
Output for 11i should be like
Server version: Oracle HTTP Server Powered by Apache/1.3.19 (Unix)
Server built: Jan 26 2005 11:06:44 (iAS 1.0.2.2.2 rollup 5)

Output for R12 should be like
Server version: Oracle-Application-Server-10g/10.1.3.0.0Oracle-HTTP-Server
Server built: Dec 4 2006 14:44:38

Q. Forms & Report version (aka developer 6i) in 11i
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/f60run | grep Version | grep Forms

output like
Forms 6.0 (Forms Runtime) Version 6.0.8.25.2 (Production)
Check fourth character in version 25 which means Forms 6i patchset 16 (25-9)

.
Q. Forms & Report version in R12/12i
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/rwrun | grep Release

Output should be like
Report Builder: Release 10.1.2.2.0
You can safely ignore warnings

Q. Database Version in 11i/R12/12i
A. Go to database section below.

Q. Oracle Jinitiator in 11i/R12/12i
A. Log in as Application user, set environment variable and run below query
grep jinit_ver_comma $CONTEXT_FILE

(Default is Java Plug-In for R12/12i )

Q. Oracle Java Plug-in in 11i/R12/12i
A. Log in as Application user, set environment variable and run below query
grep plugin $CONTEXT_FILE
Q. File Version on file system
adident Header <filename>
or
strings <file_name> | grep Header

Here adident is AD Utility (Oracle Apps) and strings is Unix utility

Q. Version of pld file
*.pld are source code of *.pll which are inturn source of *.plx. *.pll is in $AU_TOP/resource and to find its version check

adident Header $AU_TOP/resource/<filename>.pll
IGSAU012.pll:
$Header IGSAU012.pld 115.1.115100.1 2004/04/01 05:40:18 appldev ship $

or
strings $AU_TOP/resource/<filename>.pll | grep -i header

FDRCSID(‘$Header: IGSAU012.pld 115.1.115100.1 2004/04/01 05:40:18 appldev ship $’);

Q. OA Framework Version
A.http:// hostname.domainName:port/OA_HTML/OAInfo.jsp (Only for 11i)

A. Log in as Application user, set environment variable and run below query

adident Header $FND_TOP/html/OA.jsp
adident Header $OA_HTML/OA.jsp

output for both should look like
$Header OA.jsp 115.60 2006/03/31 00:47:28 atgops1 noship $

120.21 means OA Framework Version (coming soon..)
115.60 means OA Framework Version (coming soon..)
115.56 means OA Framework Version (coming soon..)
115.36 means OA Framework Version 5.7
115.27 means OA Framework Version 5.6E
115.26 means OA Framework Version 5.5.2E

Q. Discoverer Version for 11i (3i or 4i)
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/disc4ws | grep -i Version

Q. Discoverer Version for 11i or R12 (10g AS)
Check under Application Server Section as 10g AS Discoverer is on standalone

Q. Workflow Version with Apps
A. Connect to Database as apps user
SQL> select TEXT Version from WF_RESOURCES where NAME = ‘WF_VERSION’;
Output like 2.6.0 means workflow version 2.6.0

Version for Fusion Middleware Component

Identity Management component Version/Release Number

A. Oracle Single Sign On
Connect to database which holds SSO repository
SQL>select version from orasso.wwc_version$;

B. Oracle Internet Directory

There are two component in OID (Software/binaries & Schema/database)

>>> To find software/binary version

$ORACLE_HOME/bin/oidldapd -version
output should look like

oidldapd: Release 10.1.4.0.1 – Production on mon jul 14 14:14:21 2008
Copyright (c) 1982, 2006 Oracle. All rights reserved.

>>> To find Schema Version/ database use

ldapsearch -h <hostname> -p <port> -D “cn=orcladmin” -w “<password>” -b “” \
-s base “objectclass=*” orcldirectoryversion

and output should be like

version: 1
dn:
orcldirectoryversion: OID 10.1.4.0.1

or run following query in database
SQL> select attrval from ods.ds_attrstore where entryid = 1 and attrname = ‘orcldirectoryversion’;

Output should be like OID 10.1.4.0.1

C. Application Server

1. Oracle Application Server 10g Rel 3 (10.1.3.X)
cat $ORACLE_HOME/config/ias.properties | grep Version

Version=10.1.3.0.0

2. For Oracle Application Server 10.1.2 (Prior to Oracle WebLogic Server)
If application server is registered in database (Portal, Discoverer) check from database
SQL> select * from ias_versions;
or
SQL>select * from INTERNET_APPSERVER_REGISTRY.SCHEMA_VERSIONS;

D. AOC4J (Oracle Container for J2EE)
Set ORACLE_HOME
cd $ORACLE_HOME/j2ee/home
java -jar oc4j.jar -version

E. Oracle Portal
SQL> select version from portal.wwc_version$;

Database Component

I) Oracle Database

To find database version
SQL> select * from v$version;
or
All component version in database

$ORACLE_HOME/OPatch/opatch lsinventory -detail

DATABASE ARCHITECTURE

DATABASE ARCHITECTURE :
===============================================

Differnces between 9i,10g,11g databases

Differnces between 9i,10g,11g:

===================

9i: The improvement in Oracle 9i aims at improved optimization of conventional business applications:

1: System fault recovery

2: Disaster recovery

3: online changes in schema

4: Flashback Query

10g: There are several hundred feature differences between the 9i and 10g versions:

1: Oracle Enterprise Manager (OEM) in 10g completely redesigned

2: The imp utility on the Data Pump has been replaced with impdp

3: Automatic Database Diagnostic Monitor (ADDM)

4: introduced Automatic Storage Management (ASM)

5: Scheduling package dbms_job is replaced by the dbms_scheduler package

6: Introduction of backup compression by RMAN

11g: The design of 11g implemented this through creation of automated storage, automated memory management and creation of intelligent tuning advisors.

1: Automatic memory tuning

2: Automated load balancing in storage

3: Automated Diagnostic Repository

4: Load balancing utilities

5: File group repository

R12.2.2 Patching Steps

R12.2.2 Patching Steps:
==================

In Oracle Apps R12.2 what will happen when we run adop phase=prepare ??

1. Checks that the environment is set to the run APPL_TOP.

2. Checks whether to perform a cleanup, which will be needed if the user failed to invoke cleanup after the cutover phase of a previous online patching cycle.

3. Checks to see if the database is prepared for online patching:

Checks that the FILE_EDITION environment variable value is set to ‘run
Checks to see if enough space is available in the database (SYSTEM tablespace should have minimum of 25 GB of
free space and APPS_TS_SEED tablespace should have minimum of 5 GB of free space)
4. Checks the file system, using the TXK script $AD_TOP/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl.
This script checks for the file system space, database connections, Apps/System/Weblogic Passwords,
Contextfile Validation and so on

5. Produces a report showing information about the most important tablespaces is generated.
This report is created in $APPL_TOP/admin/$TWO_TASK/out.

6. Checks for the existence of the “Online Patching In Progress” (ADZDPATCH) concurrent program.
This program prevents certain predefined concurrent programs from being started, and as such needs to be active
while a patching cycle is in progress.

7. Invokes the TXK script $AD_TOP/patch/115/bin/txkADOPPreparePhaseSynchronize.pl to synchronize the patches which have been applied to the run appltop.

8. Checks the database for the existence of a patch edition, and creates one if it does not find one

A patch edition is created in the database.
All code objects in the patch edition begin as pointers to code objects in the run edition.
Code objects in the patch edition begin as lightweight “stub objects” that point to the actual object definitions,
which are inherited from earlier editions. Stub objects consume minimal space, so the database
patch edition is initially very small in size.
As patches are applied to the patch edition, code objects are actualized (have a new definition created) in that edition.
9. Calls the $AD_TOP/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl script again to confirm that the
database connection to the patch edition is working.

R12.2 Cloning for E-Business Suite :

==============================================

R12.2 follows new process of Cloning on Application Tier, it requires selective Components’ backup and Clone from Source FS1 to Target FS1, Target FS1 (RUN fs) to Target FS2 (PATCH fs)
We will cover Single node Apps Tier Cloning in this thread, DB Tier cloning is same as 11i/R12.1

Gather before starting R12.2 Full Cloning process
• Make sure you have enough space available at Source for Backup and Restore/recovery/cloning at Target
• Decide on naming convention like ORACLE_SID, Target System Base directory , Target System Instance Home Directory, Display Value, Port pools, UTL_FILE_DIR
• We will require Apps User password and Weblogic AdminServer password while running adcfgclone.plappsTier
• Maintain snapshot information
Log in to each Application Tier node as the APPLMGR user, and
run "Update current view snapshot" in AD Administration.
• OS Version and requirement should match between Source and Target
• Apply latest AD, Autoconfig and latest Rapid clone patches

High level Steps to perform R12.2 Full cloning

• Run adpreclone.pl on db tier
• Take backup of Database Tier using RMAN or conventional process including RDBMS_TOP
• Restore/recover DB Tier using adcfgclone.pl dbTier
• Run adpreclone.pl on db tier and apps tier (RUN_BASE) using respective users
echo $FILE_EDITION  This should have output “run”
As of Release 12.2, the adpreclone.pl process on the Application Tier creates a complete compressed archive of the Oracle Fusion Middleware and its components as follows:
o A compressed archive of the Oracle WebLogic Server home, Oracle Web Tier Utilities home, Oracle Common Utilities home and the Oracle E-Business Suite home:
<COMMON_TOP>/clone/FMW/FMW_Home.jar
o A compressed archive of the Oracle E-Business Suite Weblogic domain:
<COMMON_TOP>/clone/FMW/WLS/EBSdomain.jar
o The Oracle E-Business Suite Weblogic domain's configuration template:
<COMMON_TOP>/clone/FMW/WLS/plan/moveplan.xml
o A compressed archive of the Oracle Web Tier/Oracle HTTP Server configuration instance:
<COMMON_TOP>/clone/FMW/OHS/ohsarchive.jar
o The Oracle HTTP Server configuration instance's configuration template:
<COMMON_TOP>/clone/FMW/OHS/moveplan.xml
• For FULL Cloning we require backup of
o <APPL_TOP>
o <COMMON_TOP>
o <OracleAS Tools 10.1.2 ORACLE_HOME>

• Restore backup taken above at target

• Run adcfgclone.pl on apps Tier as show below
cd /u01/app/appdi/DR122I/fs1/EBSapps/comn/clone/bin
./adcfgclone.pl appsTier
Do you want to add a node (yes/no) [no] :
Target System File Edition type [run] :
Provide the values required for creation of the new APPL_TOP Context file.
Target System Hostname (virtual or normal) [<ServerName>] :
Target System Database SID : DR122I
Target System Database Server Node [<ServerName>] :
Target System Database Domain Name [<DomainName>] :
Target System Base Directory : /u01/app/appdi/DR122I
Target System Instance Home Directory [/u01/app/appdi/DR122I] : /u01/app/appdi/DR122I
Target System Instance Top set to /u01/app/appdi/DR122I/fs1/inst/apps/DR122I_<ServerName>
Do you want to preserve the Display [<ServerName>:0.0] (y/n) : n
Target System Display [nsmltcstrg02:0.0] : nsmltcstrg02:2.0
Target System Root Service [enabled] :
Target System Web Administration [enabled] :
Target System Web Entry Point Services [enabled] :
Target System Web Application Services [enabled] :
Target System Batch Processing Services [enabled] :
Target System Other Services [enabled] :
Target System Port Pool [0-99] : 12
Choose a value which will be set as APPLPTMP value on the target node [1] :
….
…
..
- 100% completed

Completed Apply...
….
…
..
Do you want to startup the Application Services for DR122I? (y/n) [n] : y
….
…
..
All enabled services for this node are started.

adstrtal.sh: Exiting with status 0
• Now we need to Clone RUN FS to PATCH FS
• Source Environment variable file at newly cloned RUN File System
• Run adpreclone.pl on RUN File system
• Copy Run File system to patch file system under FS2 (Assuming FS2 as Patch file system)
• Run adcfgclone.pl appsTier on Patch File System
cd <COMMON_TOP>/clone/bin

adcfgclone.pl appsTier
Enter the APPS password :
Enter the Weblogic AdminServer password :
Do you want to add a node (yes/no) [no] :
Target System File Edition type [run] : patch
Target System Port Pool [0-99] : 13
Choose a value which will be set as APPLPTMP value on the target node [1] :
….
…
..
| 100% completed

Completed Apply...
Looking for incomplete CLONE record in ad_adop_session_patches table
The CLONE record status is BACKUP-FMW-HOME

Updating incomplete CLONE record to COMPLETED
• Create soft link at $HOME for users to source FS1 or FS2 Environment
• This concludes Full Standard Cloning process for E-Business Suite Release 12.2

NOTE:
If you are trying to reclone or ORACLE_HOME already registered in Inventory - you may need ot unregister ORACLE HOMEs before Cloning you can execute the following command to unregister or detach that Oracle Home:
$ ./runInstaller -detachhome
ORACLE_HOME=<Oracle Home Location>
For Example:
$ cd $FMW_HOME/oracle_common/oui/bin
$ ./runInstaller –detachhome
ORACLE_HOME=<Oracle Home Location>
In addition to the un registration process, ensure to delete the FMW_HOME directory structure.

OR

For de-registering <FMW_HOME>/Oracle_EBS-app1:
<FMW_HOME>/Oracle_EBS-app1/oui/bin/detachHome.sh -jreLoc
<FMW_HOME>/Oracle_EBS-app1/jdk
For re-registering <FMW_HOME>/Oracle_EBS-app1:
<FMW_HOME>/Oracle_EBS-app1/oui/bin/attachHome.sh -jreLoc
<FMW_HOME>/Oracle_EBS-app1/jdk

Webogic Admin Challenges and Issues

Madhusappsdba

What is best way to problem handling?

As a Middleware Admin there are many troubles in daily jobs, whenever a problem occurs, You must understand the problem, identify that is it a known or unknown. If it is known issue there could be workaround for that it can be done with knowledge management. As part of best practices you must maintain a issues and their resolutions as Knowledge Management Database KMDB.

Problem can be understood with the following simple Questions that make you clarity about which area, what could be the reason for the issue.

What do we know?
What do we need to know?
What should we do?

Remember that every problem there must be solution or possible alternative solutions. You need to have enough knowledge to resolve the issue with wisdom. Wisdom gives you the right path to reach right decision to solve the issue.

Problem solving strategy: Problem || Analysis Data -> Information -> Knowledge -> Wisdom || Solution

Problem vs Issue

Problem that happen accidentally due to any reasons, such as network not in sync, Database server might overloaded or anything. An issue can be transformed into problem when it is not identified in time and not resolved. A problem that need to fix immediately. The impact of the problem can be Life threatening. To make more simple, fever is an issue it can be resolved by pills, Heart Attack is a major Life threatening it is not solved immediately there could be huge loss.

To explore on middleware if you encounter more troubles more you learn. At the same time remember that your Client always wishes that business will run uninterruptedly. You give the 99.9999%

Bottom line, When the problem is not in Middleware environment then don't play the name blame game. Try to give your best for support the solution providing team.

Love issues, which make you to learn more about the subject. Enjoy with issues, troubles, you will be enlighted with your problem skills so.......... dear smart WLA rock with them!!!

1. Port Conflict Issue:

While configuring a new WebLogic instance and starting it, that might be get an issue like : "Port already in use". There could be many reasons for this one.
1. on the same machine multiple standalone instances might be running one of the instance already used that port which you have given for new configuration.
2. apache might be running with the same port.
3. middleware might be running on the same machine with same port
On Solaris Operating environment we have 2 options:
1. using pfiles command
netstat –na|grep <port> --> identify port in use

pfiles <pid>|grep -i sockname |grep port --> look for every java process is initialized by startWebLogic.sh or startManagedWebLogic.sh

2. Another way costly one (Third party package) to find the process that is using particular port is :
lsof -i tcp:<Port_number>
This Linux command lsof works for that user to where this command is executed by the user.
3. Best way is perl script using a method it will check only standard ports which are used by the system.

getservbyport(int port_number, const char *protocol_name) 

Sample perl script goes as follows:

#!/usr/bin/perl
($name, $aliases, $port_number, $protocol_name) = getservbyport(7001, "tcp");
print "Name = $name\n";
print "Aliases = $aliases\n";
print "Port Number = $port_number\n";
print "Protocol Name = $protocol_name\n";

2. Config.xml Repository Issue

When I copy pasted few of the JMS Queue related configurations from existing WLS config.xml to newly created WLS Domain's config.xml. I got stuck the control at following line in the WebLogic Server logs.
<Jul 28, 2008 12:08:26 PM EDT> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at /path/
Sol: Verify all the lines in the config.xml file there might be missing any xml tags missing. I have missed out one line need to correct it now it is working fine.

3. Multicast Failure

while running the managed server on a remote server getting the following exception:

<Jul 31, 2008 4:16:16 AM EDT> <Error> <Cluster> <BEA-000109> <An error occurred while sending multicast message: java.net.SocketException: Socket is closed

java.net.SocketException: Socket is closed

at java.net.DatagramSocket.send(DatagramSocket.java:577)

Sol:
1. check for the ping happening between the cluster involved machines.
2. Verify the Multicast IP with the MulticastTest with multiple ips and with ports then use which is communicating the message between two participants.

AppMachine 1:

$ java utils.MulticastTest -n app1 -a 237.0.0.5 -p 9999

WebMachine 2:

$ java utils.MulticastTest -n app2 -a 237.0.0.5 -p 9999

The messages must exchange between them... otherwise check with Network team.
3. Multcast heart beat can be visible by the following command line:

java weblogic.cluster.MulticastMonitor <multicastIP> <port> mydomain mycluster

4. Application not accessable

While accessing the application url after Web App deployment.
<Aug 19, 2008 10:58:07 AM EDT> <Error> <HTTP> <BEA-101017><[ServletContext(id=29754737,name=webapp1,context-path=/contextpath)] Root cause of ServletException.
java.lang.StackOverflowError
Sol: Check the classpath it is the communication gap between Servlet and an EJB

5. Editing the WLS password
New password is given in boot.properties when server is in offline.

The Admin server started but while starting the managed instances got the following error:
<Aug 22, 2008 8:21:54 AM EDT> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
********************************************************
The WebLogic Server did not start up properly.
Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
************************************************************
Sol: Resolved by editing in boot.properties, startManagedWebLogic.sh files for the new password in 'CLEARTEXT' pattern and rename ldap folder in the Managedserver instance folder present in the domain folder.
While starting up the server instance boot.properties will be encrypted and re-written back. after this ldap folder will be generated in the domain directory for the Managed instance where new file will be created with instance name with extention as .ldif
Apache Plug-in configuration
While configuring the Apache using the instructions given in the following link :

6. Deployment Error

Module Name: apollo, Error: [HTTP:101179][HTTP] Error occurred while parsing descriptor in Web application "/domainpath/application.war" [Path="/source_code_path", URI="applicaiton.war"
org.xml.sax.SAXParseException: Element type "local-path" must be followed by either attribute specifications, ">" or "/>".
Sol:
Check the Deployment Descriptors (here weblogic.xml) edit as per the given Line.

7. JNDI Issue

While deploying application which is having multiple JMS Queues getting as:
data couldn't be saved. The exception is : Error while doSenderQueueLookUp for :QUEUEJNDIUnable to resolve 'QUEUEJNDI' Resolved
Sol:
Please verify the Persistance Store is connected to Connection Pool.

8. New managed server Configuration issue

Here I am with set of errors when newly configuring WebLogic 9.2 MP3 managed server and adding to a webcluster. The managed server when started first time shown the following :
1. BEA-000362
2. BEA-000386
On Solaris box:
<Mar 30, 2009 2:56:49 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.net.UnknownHostException: mywebhostname.com: myhostname.com
        at java.net.InetAddress.getAllByName0(InetAddress.java:1128)
        at java.net.InetAddress.getAllByName0(InetAddress.java:1098)
        at java.net.InetAddress.getAllByName(InetAddress.java:1061)On

On Linux box:
<Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Unable to open initial replica url: http://myadminhost.com:7001/bea_wls_management_internal2/wl_management
weblogic.ldap.EmbeddedLDAPException: Unable to open initial replica url: http://myadminhost.com:7001/bea_wls_management_internal2/wl_management
        at weblogic.ldap.EmbeddedLDAP.getInitialReplicaFromAdminServer(EmbeddedLDAP.java:1319)
        at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:221)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.FileNotFoundException: Response: '500: Internal Server Error' for url: 'http://myadminhost.com:7001/bea_wls_management_internal2/wl_management'
        at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:472)
        at weblogic.ldap.EmbeddedLDAP.getInitialReplicaFromAdminServer(EmbeddedLDAP.java:1296)
        at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:221)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        Truncated. see log file for complete stacktrace

Solution/Work around:BEA-000362
First thing you need to ensure on your configuration, double check your config.xml file assigned IP or VIP or domain name is correct or not. On the other hand we need to investigate for the network communication happening or not with the hostnames given in the config.xml. ping from managed server box to admin server hosting dns. And also check the /etc/hosts updated with the new host dns. Some times DNS table entries not updated in WAN domains may cause this issue.
BEA-000386
Check for the hostname of the managed server listen-address given one and hosting dns/ip is matching or not using the WebLogic console(this could be a time taking process).
   Unix aware guy always prefer grep on config.xml :)

Session Replication issues on Web-Tier cluster
BEA-101310
Web server failed to perform batched update for replicated sesionsohh my god!!!

BEA-000117
Received a stale replication request
Whenever you encounter this error code in your logs you need to check following:
1. Network connectivity between the cluster member hosting machines.
2. Check all the member servers are alive in that cluster.

BEA-090870

Security issue while starting Admin Server

Exception:

####<Oct 28, 2010 3:38:41 AM PDT> <Error> <Security> <Unknown> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1288262321492> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError.
weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)

The workaround is suggested as 'Please login to the Database and then run the below SQL file to execute different queries mentioned in this file:
Suppose Database User Login is “weblogic” then login to Database with this credential and run the script under

$BEA_HOME\wlserver_10.3\server\lib\rdbms_security_store_oracle.sqlThen restart your AdminServer'.

BEA-000337 - Stuck Thread** You can use wise step using jps -v|grep [instance]
First step you need to take thread dump (kill -3 for Unix, CTRL+Break for Windows) make sure one of thread dump analyzer is opend use any thread dump analyzer.
Check the logs where the STUCK found, Check the timing when it came first time, how much time it exceeded configured time? If that time interval seconds exceeded for more than 10 mins and threadpool doesnot have idle threads then stop that WebLogic server instances.
WebLogic 9.2 MP3 Managed Server cannot start !!??!!
On Red Hat Linux 2.4 the WebLogic managed Server could not start. Tried many times kill the process and start no luck! memory is in comfortable range. CPU don't have load, Network connectivity is also verified, Good condition. WebLogic server log is not writing about why it is not able to start the server instance.
Finally checked uptime for that box. It is more than a year ago started, thought that rebooting machine might helps.

BEA-000388 -
JVM called WLS shutdown hook. The server will force shutdown now

Issue:

The WebLogic server got shutdown with the following error stack found in the server standard out log files:

####<Sep 7, 2012 3:14:20 PM IST> <Notice> <WebLogicServer> <Ncorp-PLM-08> <Ncorp-PLM-08-AgileServer> <Thread-1> <<WLS Kernel>> <> <> <1347011060768> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>

####<Sep 7, 2012 3:14:20 PM IST> <Alert> <WebLogicServer> <Ncorp-PLM-08> <Ncorp-PLM-08-AgileServer> <Thread-1> <<WLS Kernel>> <> <> <1347011060768> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>

####<Sep 7, 2012 3:14:20 PM IST> <Notice> <WebLogicServer> <Ncorp-PLM-08> <Ncorp-PLM-08-AgileServer> <Thread-1> <<WLS Kernel>> <> <> <1347011060771> <BEA-000365> <Server state changed to FORCE_SUSPENDING>

The following could be possible Cause and we have the workaround solution as:

I have the following suggestion for you for the below error:

1) It seems like some component is sending the wrong signal to the JVM and this issue is occurring. JVM monitors and catches OS signals, like: CTRL +C event, Log off event, shutdown event.When JVM catches one of the stated above signals, it shutdowns all java processes.

Please try these possible solutions of this problem:

· Specify -Xrs parameter in the JAVA startup arguments and start the admin server

· -Xrs

· Note: -Xrs is a non-standard option developed by Sun Microsystems for their HotSpot JVM. BEA JRockit continues to support this option; however the BEA JRockit non-standard option -XnoHup provides the same functionality. -Xrs reduces usage of operating-system signals by the JVM. If the JVM is run as a service (for example, the servlet engine for a web server), it can receive CTRL_LOGOFF_EVENT but should not initiate shutdown since the operating system will not actually terminate the process. To avoid possible interference such as this, the -Xrs command-line option does not install a console control handler, implying that it does not watch for or process CTRL_C_EVENT, CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, or CTRL_SHUTDOWN_EVENT Operation.

2) If the issue recurs again even after trying the above option then can you please apply the following JAVA_OPTION:

· Depending on the JVM version, it may be possible to get a thread dump before the process exits

· HotSpot supports the command-line option -XX:+ShowMessageBoxOnError

· The corresponding JRockit option is -Djrockit.waitonerror

· While the JVM< goes down, it may prompt the user: "Do you want to debug the problem?"

· This pauses the JVM, thereby creating an opportunity to generate a thread dump (a stack trace of every thread in the JVM), attach a debugger, or perform some other debugging activity.

BEA-160192

<BEA-160192> <While upgrading weblogic.xml, encountered "max-in-memory-sessions" param "session-param". This param is unknown and will be removed>

This eror you can see in your weblogic logs, Because the deployment descriptor weblogic.xml is not updated with the latest DTD defined for weblogic 11g.

To resolve this do setWLSEnv.sh and run the following and it will convert it to compatable to WebLogic 11g. But as this is template the basic xml will need to be amended with the 11g DTD and then build script creating the correct file out of it -

java weblogic.DDConverter -d . <<ear/warfile or webapp/ear directory>>

How to apply patch while you are in the middle of ADPATCH=================================================