Sunday, September 11, 2011

Oracle EBS r12 troubleshooting & useful notes

1. Canceling of concurrent Request Gives “the concurrent manager process that was running this request has exited abnormally “
Some times we get a Request from customers that they are unable to cancel the request because of this error

“the concurrent manager process that was running this request has exited abnormally .The ICM will mark this request as completed with error.”"

How to navigate :
Tried to Cancel a concurrent request. Used the “Cancel Request” button from the Administer > Concurrent > Manager form.

Got the following message:

Request xxxxxx can no longer be cancelled. The Concurrent Manager Process that was running this request has exited abnormally. The ICM will mark this request as completed with error.

This can be safely done while managers are up and running with little care

1) Backup fnd_concurrent_requests table

2) SQL> UPDATE fnd_concurrent_requests
SET phase_code = ‘C’, status_code = ‘X’
WHERE Request_id=&request_id

Here Request id is the request which we want to cancel….

3) Commit


2. Oracle EBS r12 Diagnostic Tests.

To execute a diagnostic test for,
Log File Test
DBC Parameter Test
Class Path Test
Java Run-Time Environment Version Test
Java System Property Report test

Go to 'system administrator' responsibility--->Under 'System Administration: Diagnostics'--->Click 'Diagnostic Test'-->Here run all tests under application "HTML Platform".

In the Report output under 'View Reports' tab you can see the result of the above tests. For example it includes, what the current guest username is set to and if it is successfully authenticated (this is displayed in the value "Diagnostic Test Executed By" in the report output).

3. what is the usage & Contents of .dbc file in 11i/R12

dbc is the database connect descriptor file that stores database connection information used by application tier to connect to the database.
The file is found in $FND_TOP/secure directory also called as FND_SECURE.

Location of .dbc file in 11i is: $FND_TOP/SECURE OR $FND_SECURE

Location of .dbc file in R12 is: $INST_TOP/appl/fnd/12.0.0/secure

If we interpret .dbc file it contains the following,

GUEST_USER_PWD – Guest username & password
APPL_SERVER_ID – Used to Identify the Databse by Server ID, this ID is also stored in SERVER_ID column of FND_NODES table.
GWYUID – APPLSYSPUB user name and password
DBhostname - DB server name
dbport - Database Listener Port number

Other than these, the following are some other parameters with their default values, these are related to the Performance,



4. How to drop/delete an application user

We can only deactivate or end-date the application user in Oracle EBS using the application front end. While we cannot delete an application user, but if you try to delete it from the database then it might crash the system and more over it is not supported by oracle.

To deactivate or end-date the application user you can use any one of the following methods,

Method I:
Login to Oracle Applications – Goto System Administrator responsibility – Under 'Security' – User – Define – Search user name – then you can give end date in the Effectives Date To column.

Method II:

It's always recommended to use the above method to end-date/deactivate application user.
Even though the following method is not supported by oracle support, End-dating the user from backend database is also possible with the following steps, This is also mentioned in Note 1039608.6

Login as 'APPS' database user. Then take a backup of fnd_user table just in case if any issue comes then you can restore this table instead of the whole database restore.


SQL>update fnd_user set end_date='27-JUL-2011' where user_name like ‘%%’;


5. How to know the Oracle Ebusiness Suite 11i / r12 application URL?

select home_url from apps.icx_parameters;


grep -i login $APPL_TOP/admin/Context_name.xml


6. fnd_install_processes & ad_deferred_jobs tables

When a patch is applied using adpatch it will ask number of workers. These workers are used to run some task like executing some perl scripts, running sql scripts, etc.

If u check in the patch log file before assigning any job to workers the two tables fnd_install_processes and ad_deferred_jobs are created.
After the job is finished the tables are dropped automatically. The following is the purpose of these tables,

fnd_install_processes – This table is used to store the information about the job given to the worker. It will insert a row for each worker when it assigned a job.

ad_deferred_jobs – this table is used to store the information about the deferred jobs (jobs failed to run).

7. Steps to manually stage r12 software

make a directory stage
in that (mkdir stage)

copy the start cd (mkdir startCD) -> startCD
copy the Tools-Disk1(mkdir oraiAS) ->oraiAS
copy the RDBMS Disk1 (mkdir oraDB) -> oraDB
copy the Databases disk1,disk2,disk3,disk4 (mkdir oraAppDB) ->oraAppDB
copy the APPL_TOP dis1 and 2 to (mkdir oraApps) -> oraApps

The automatic staging command is,

perl d:\mnt\cdrom\Disk1\rapidwiz\
The stage script message informs you that you may either stage all the Rapid Installcomponents, or selected components only.

8. Oracle Applications Current Patchsets Comparison Utility (Script to Analyze)

The program ( compares the currently installed patchsets and family packs to the most recently available ones generated by Oracle Development.

NOTE: The program is frequently updated by the Oracle development team with the latest patchsets data in it.
So, this means that you need to get the latest version to get an up-to-date report.

*Download the latest script from:
*Also refer to metalink note ID 139684.1 for latest updates and how to run this program, the steps to run this program is compiled in short form.

This program utilizes direct database connectivity or the applptch.txt file for 10.7-11.0. For 11i and R12, it utilizes a combination of tables such as AD_BUGS and AD_APPLIED_PATCHES to create the installed patch list. If the 11i release does not use these AD tables (11.5.4 or lower and have not applied 11i.AD.E or higher) it still supports using applptch.txt for 11i.

Setup Requirements:
Must have connectivity to EBS database via sql*net with $TWO_TASK set
Source $APPL_TOP/APPSxx.env file or just setup database env such as ORACLE_HOME and TWO_TASK

Running the Patchsets Comparison Tool:

•11i - $ . $APPL_TOP/APPSORA.env
•R12 - $ . $APPL_TOP/APPS{sid}_{machine}.env
Note: As long as you can connect with sqlplus and $TWO_TASK, the script should have the access it needs.

Usage: $ [connect=11i_login/pwapplptch=/path/applptch.txt] [-h] [silent=y] default is n, [htmlout=file]

Example Help:
$ -h

Example Html Output in Silent Mode:
$ ./ applptch=/applptch_11i.txt htmlout=Report.html silent=y

$ ./ connect=apps/apps_password_here htmlout=xxReport.html

Columns in The Output of script:
Baseline Version: This is the baseline release version that come with EBS release
Running Version: This is The Current High Level Code running on instance..or currrent patch level
Latest AvailableStatus: THis Is the Latest Patches Available from The ORACLE for that module…

Platform Specific Issues:
--> Get to the drive where the appl_top is.
C:> D:
Make a tmp directory on that drives root.
D:> mkdir tmp (this is where the patchset lists get created)

--> cd to the APPL_TOP path and then execute the envshell to setup the env variables.
D:\> cd D:\apps\visappl
D:\apps\visappl> envshell
A new window spawns with the correct env settings, use it for next step

-->Start the MKS SHELL,
D:\apps\visappl> sh

--> Run the patchsets program from the APPL_TOP/admin/ directory
$ cd /admin/VIS
$ ./ applptch=applptch.txt

NOTE: Download the script from:

NOTE: Also you can get this script from metalink note : Oracle Applications Current Patchset Comparison Utility – [ID 139684.1]