Enterprise Scheduler Service and Jobs - Oracle Fusion Applications Administration Essentials - page 70

FND_SESSION_ID
--------------------------------------------------------------
E6D22A8416306FEDE043EFFC4B0A5001

Now we go to the user dump dest and look for the trace identifier:

E6D22A8416306FEDE043EFFC4B0A5001

[oracle@fadbhost trace]$ pwd
/u01/app/oracle/fadb/diag/rdbms/fadb/fadb/trace
[oracle@fadbhost trace]$ ls -ltr
*E6D22A8416306FEDE043EFFC4B0A5001*.trc
-rw-r----- 1 oracle dba 214970 Sep 22 00:51
fadb_ora_28686_E6D22A8416306FEDE043EFFC4B0A5001.trc
-rw-r----- 1 oracle dba 5422699 Sep 22 00:51
fadb_ora_28653_E6D22A8416306FEDE043EFFC4B0A5001.trc

Multiple trace files can be consolidated with the trcess command. The following
command accepts the client_id , session_id , service, action, or module:

trcsess output=test.txt clientid=weblogic_fa
*E6D22A8416306FEDE043EFFC4B0A5001*

Once the trace files are consolidated, the tkprof command can be used to find bot-
tlenecks in the database.

Troubleshoot warning or failed jobs

If a job is in the warning or failed state, the following checks can be made:

1. Make sure the Content Management server deployed on the CommonDomain

is running. Since ESS uses the Content Management server for all the jobs'
logs and output files, it is important that this server is running.

2. Run the following query to get an error message from the re-

quest_history table: