Enabling and Getting Trace file of a concurrent request

-
1) Enable Trace of a concurrent request:

Please enable trace on the concurrent program using the following steps: 
Go to Sysadmin > Concurrent > Program > Define 
Query the concurrent program 
Check the trace box to enable trace 


2) Fatching the trace file location:


The following query helps to identify the Trace file path location for a particular Concurrent Request

Pass the request id as parameter 

SQL Code:


SELECT
    req.request_id
    ,req.logfile_node_name node
    ,req.oracle_Process_id
    ,req.enable_trace
    ,dest.VALUE||'/'||LOWER(dbnm.VALUE)||'_ora_'||oracle_process_id||'.trc' trace_filename
    ,prog.user_concurrent_program_name
    ,execname.execution_file_name
    ,execname.subroutine_name
    ,phase_code
    ,status_code
    ,ses.SID
    ,ses.serial#
    ,ses.module
    ,ses.machine
    FROM
    fnd_concurrent_requests req
    ,v$session ses
    ,v$process proc
    ,v$parameter dest
    ,v$parameter dbnm
    ,fnd_concurrent_programs_vl prog
    ,fnd_executables execname
    WHERE 1=1
    AND req.request_id = &request --Request ID
    AND req.oracle_process_id=proc.spid(+)
    AND proc.addr = ses.paddr(+)
    AND dest.NAME='user_dump_dest'
    AND dbnm.NAME='db_name'
    AND req.concurrent_program_id = prog.concurrent_program_id
    AND req.program_application_id = prog.application_id
    AND prog.application_id = execname.application_id
    AND prog.executable_id=execname.executable_id:  


Comments

Post a Comment

Popular posts from this blog

RMAN backup Status (Remaining Time and Percentage)

-
On Running a huge database backup we often need to know the status of backup. 1) How much backup is taken. 2) How much is remain. 3) Estimate time to complete the backup. After lot of search i find out this amazing query below. col dbsize_mbytes for 99,999,990.00 justify right head "DBSIZE_MB" col input_mbytes for 99,999,990.00 justify right head "READ_MB" col output_mbytes for 99,999,990.00 justify right head "WRITTEN_MB" col output_device_type for a10 justify left head "DEVICE" col complete for 990.00 justify right head "COMPLETE %" col compression for 990.00 justify right head "COMPRESS|% ORIG" col est_complete for a20 head "ESTIMATED COMPLETION" col recid for 9999999 head "ID" select recid , output_device_type , dbsize_mbytes , input_bytes/1024/1024 input_mbytes , output_bytes/1024/1
Read more

EBS R12.2 Autoconfig Failed. Resolved

-
Hi, Please do the following and retest the issue: Due to the method required for "cleaning out" / "re-synchronizing" the following tables, it is EXPECTED / REQUIRED that the Applications have been shutdown. The only thing running should be the Database Tier. Note: A full backup should also be taken before any testing begins. Test the following steps in a development instance, and then migrate accordingly once the desired result is confirmed: 1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables in the EBS env: sqlplus applsys/pwd create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files; create table fnd_nodes_bk as select * from fnd_nodes; create table adop_valid_nodes_bk as select * from adop_valid_nodes; 2. Truncate the following tables: truncate table fnd_oam_context_files; truncate table fnd_nodes; truncate table adop_valid_nodes; 3. Run AutoConfig on the DB tier
Read more

Cleaning nodes in EBS databae.

-
Cleaning EBS nodes with EXEC FND_CONC_CLONE.SETUP_CLEAN; . EBSapps.env run   $ sqlplus apps/<PASSWORD> SQL> create table fnd_nodes_22ep14 as select * from fnd_nodes; SQL> exec fnd_conc_clone.setup_clean; PL/SQL procedure successfully completed. SQL> commit; Commit complete. After that run autoconfig in below order to populate the FND TABLES properly. 1) Stop application services ( optional but  recommended )  2) Run autoconfig on dbTier 3) Run autoconfig on appTier
Read more