Monday, May 21, 2012

Query for Identifying correct trace file for request id

PROMPT IDENTIFY CONCURRENT REQUEST FILE
PROMPT From Bug.3211206
PROMPT Use the following query to identify the correct trace file:
PROMPT where "request" is the concurrent request id for the inventory transaction
PROMPT worker.
SELECT 'Request id: '||request_id ,
'Trace id: '||oracle_Process_id,
'Trace Flag: '||req.enable_trace,
'Trace Name:
'||dest.value||'/'||lower(dbnm.value)||'_ora_'||oracle_process_id||'.trc',
'Prog. Name: '||prog.user_concurrent_program_name,
'File Name: '||execname.execution_file_name|| execname.subroutine_name ,
'Status : '||decode(phase_code,'R','Running')
||'-'||decode(status_code,'R','Normal'),
'SID Serial: '||ses.sid||','|| ses.serial#,
'Module : '||ses.module
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 req.request_id = &request
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;


Enter value for request: 147794573
old  15: where req.request_id = &request
new  15: where req.request_id = 147794573

Request id: 147794573
Trace id: 2117828                        Trace Flag: Y
Trace Name:
/q02/app/oracle/oaqadb/oaqa_oaqadb/udump/oaqa_ora_2117828.trc
Prog. Name: Add/Delete Summary Accounts
File Name: GLSTPM
Status : Running-Normal
SID Serial: 1220,3413
Module : GLSTPM

Tuesday, May 1, 2012

Purge Concurrent Request and/or Manager Data Program

Purge Concurrent Request and/or Manager Data Program

 Use this program to delete:


    • request log files, concurrent manager log files, and report output files from your product directories maintained by the operating system
    • records (rows) from Application Object Library database tables that contain history information about concurrent requests and concurrent manager processes.
Use this program to compute performance statisics for each of the concurrent programs, if the Concurrent: Collect Request Statistics profile option is set to "Yes".

Report Options

Entity

All Purges records from database tables that record history information for concurrent requests, history information for concurrent managers, and purges request log files, manager log files, and report output files from the operating system.
Manager Purges records from database tables that record history information for concurrent managers, and purges manager log files from the operating system.
Request Purges records from database tables that record history information for concurrent requests, and purges request log files and report output files from the operating system.

Mode 

Age Enter the number of days for which you want to save concurrent request history, log files, and report output files. The purge program deletes all records older (in days) than the number you enter.
For example, if you enter "5", then all concurrent request history, log files, and report output files older than five days is purged.
Count Enter the number of (most recent) records for which you want to save concurrent request history, log file, and report output files. The purge program starts from the most recent records, retains the number you enter, and purges all remaining records.
For example, if you enter "5", then the five most recent concurrent request history records, request log files, manager log files, report output files are saved, and all remaining records are purged.

Mode Value 

Enter a value to define the number of days for Mode=Age or the number of records for Mode=Count. The valid values are 1 - 9999999.


User Name

Enter the application username whose concurrent request records and associated log files and report output files you wish to purge. Username has relevance when the Entity is either "Request" or "All". For example, if you enter JSMITH, then the program purges all request records, log files, and report output files associated with requests submitted by user JSMITH.

Oracle ID 

Enter the Oracle ID that concurrent programs connect to for which you want to purge concurrent request records, and associated log files and report output files. Oracle ID has relevance when the Entity is either "Request" or "All".

For example, if you enter AP1, then the program purges all request records, log files, and report output files associated with requests to run programs that connect to the AP1 Oracle ID.

Program Application

Select the application for which you want to purge concurrent request records, and associated log files and report output files. Program Application has relevance when the Entity is either "Request" or "All". For example, if you select Oracle Payables, then the program purges all request records, log files, and report output files associated with requests to run Oracle Payables programs.

Program 

Select the program for which you want to purge concurrent request records, and associated log files and report output files. Program has relevance when the Entity is either "Request" or "All".

For example, if you select Program X, then the purge program purges all request records, log files, and report output files associated with requests to run Program X.

Manager Application

Select the application associated with the concurrent manager for which you want to purge concurrent request records, and associated log files and report output files. Manager Application is used with the Manager option, and has different effects when Entity is set to "Request, and when Entity is set to "Manager" or "All".

    • When Entity is set to "Request", the program purges all request records, log files, and report output files associated with requests run by the concurrent manager named in the Manager option.
    • When Entity is set to either "Manager" or "All", in addition to the above, the program also purges all manager log files associated with the concurrent manager named in the Manager option. 

 

Manager

Select the concurrent manager for which you want to purge concurrent request records, and associated log files and report output files. Manager is used with the Manager Application option, and has different effects when Entity is set to "Request," and when Entity is set to "Manager" or "All".

    • When Entity is set to "Request", the program purges all request records, log files, and report output files associated with requests run by the concurrent manager named in the Manager option.
    • When Entity is set to either "Manager" or "All", in addition to the above, the program also purges all manager log files associated with the concurrent manager named in the Manager option.

Resp. Application

Select the application associated with the responsibility for which you want to purge concurrent request records, and associated log files and report output files. Responsibility Application is used with the Responsibility option, and has relevance when the Entity is either "Request" or "All".

Responsibility

Select the responsibility for which you want to purge concurrent request records, and associated log files and report output files. Responsibility has relevance when the Entity is either "Request" or "All". For example, if you select the System Administrator responsibility, then the program purges all request records, log files, and report output files associated with requests submitted by users operating under the System Administrator responsibility.

Report 

Select whether you want a report listing the number of records purged by the Purge Concurrent Request and/or Manager Data program. 

No        Run the program but do not generate a report. 

Yes       Run the program and generate a report.