Oracle EBS RCV模块日志收集方法
2014-08-28 14:21
330 查看
Collecting RCV Debug files & logs in IMMEDIATE mode
1. Set the following profiles at the user level before proceeding further.
Profile Value Comments
RCV:Debug Mode Yes
RCV:Processing mode Immediate
PO:Enable Sql Trace for Receiving Processor Yes
FND:Log Enabled Yes
FND:Log Level Statement
FND:Log Module po% In small case
INV:Debug Level 11
INV:Debug Trace Yes
INV:Debug file utl_file_dir/newfilename To get utl_file_dir, use the following sql :
select value from v$parameter where name ='utl_file_dir';
2. Bounce the mobile port if the transaction is done thru mobile. Logout and relogin to the application.
3. Perform the problematic transaction.
=> Note down the concurrent request id of the Receiving Transaction Processor that gets launched.
4. Once RTP completes, get the o/p of the following in .xls format.
select module, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message_text
from fnd_log_messages
where timestamp > sysdate - 2/24
and process_id = ( select os_process_id from fnd_concurrent_requests where request_id = &request_id)
and module like 'po%'
Pass the concurrent request_id from step 3.
5. Sql trace file will get generated under udump folder.
Use the following sql to get the udump path.
SELECT value FROM v$parameter WHERE name ='user_dump_dest' ;
select oracle_process_id from fnd_concurrent_requests
where request_id = &p_request_id
Pass the concurrent request_id from step 3.
Now search for the file names *< output of previous query >* under the udump folder.
6. Other files to be uploaded:
a) Inv log file.
b) rcv11i o/p.
c) Appscheck for PO & INV
Collecting RCV Debug files & logs in BATCH mode
1. Set the following profiles at the user level before proceeding further.
Collecting RCV Debug files & logs in ONLINE mode
1. Set the following profiles at the user level before proceeding further.
1. Set the following profiles at the user level before proceeding further.
Profile Value Comments
RCV:Debug Mode Yes
RCV:Processing mode Immediate
PO:Enable Sql Trace for Receiving Processor Yes
FND:Log Enabled Yes
FND:Log Level Statement
FND:Log Module po% In small case
INV:Debug Level 11
INV:Debug Trace Yes
INV:Debug file utl_file_dir/newfilename To get utl_file_dir, use the following sql :
select value from v$parameter where name ='utl_file_dir';
2. Bounce the mobile port if the transaction is done thru mobile. Logout and relogin to the application.
3. Perform the problematic transaction.
=> Note down the concurrent request id of the Receiving Transaction Processor that gets launched.
4. Once RTP completes, get the o/p of the following in .xls format.
select module, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message_text
from fnd_log_messages
where timestamp > sysdate - 2/24
and process_id = ( select os_process_id from fnd_concurrent_requests where request_id = &request_id)
and module like 'po%'
Pass the concurrent request_id from step 3.
5. Sql trace file will get generated under udump folder.
Use the following sql to get the udump path.
SELECT value FROM v$parameter WHERE name ='user_dump_dest' ;
select oracle_process_id from fnd_concurrent_requests
where request_id = &p_request_id
Pass the concurrent request_id from step 3.
Now search for the file names *< output of previous query >* under the udump folder.
6. Other files to be uploaded:
a) Inv log file.
b) rcv11i o/p.
c) Appscheck for PO & INV
Collecting RCV Debug files & logs in BATCH mode
1. Set the following profiles at the user level before proceeding further.
Profile | Value | Comments |
RCV:Debug Mode | Yes | |
RCV:Processing mode | Batch | |
PO:Enable Sql Trace for Receiving Processor | Yes | |
FND:Log Enabled | Yes | |
FND:Log Level | Statement | |
FND:Log Module | po% | In small case |
INV:Debug Level | 11 | |
INV:Debug Trace | Yes | |
INV:Debug file | utl_file_dir/newfilename | To get utl_file_dir, use the following sql : select value from v$parameter where name ='utl_file_dir'; |
2. Bounce the mobile port if the transaction is done thru mobile. Logout and relogin to the application. 3. Get the dumps of rcv_headers_interface & rcv_Transactions_interface for the transaction before running the Receiving Transaction Processor (RTP) Please give the output in .xls format, say rti_before_rtp.xls & rhi_before_rtp.xls => Note down the group_id. 4. Run 'Receiving Transaction Processor' by passing the group_id from step 3. => Note down the concurrent request id of the Receiving Transaction Processor that gets launched. 5. Once RTP completes, get the o/p of the following in .xls format. select module, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message_text from fnd_log_messages where timestamp > sysdate - 2/24 and process_id = ( select os_process_id from fnd_concurrent_requests where request_id = &request_id) and module like 'po%' Pass the concurrent request_id from step 4. 6. Get the dumps of rcv_headers_interface & rcv_Transactions_interface transaction after RTP run. Please give the output in .xls format, say rti_after_rtp.xls & rhi_after_rtp.xls 7. Sql trace file will get generated under udump folder. Use the following sql to get the udump path. SELECT value FROM v$parameter WHERE name ='user_dump_dest' ; select oracle_process_id from fnd_concurrent_requests where request_id = &p_request_id; Pass the concurrent request_id from step 4. Now search for the file names *< output of previous query >* under the udump folder. 8. Other files to be uploaded: a) Inv log file. b) rcv11i o/p. c) Appscheck for PO & INV |
1. Set the following profiles at the user level before proceeding further.
Profile | Value | Comments |
RCV:Debug Mode | Yes | |
RCV:Processing mode | Online | |
FND:Log Enabled | Yes | |
FND:Log Level | Statement | |
FND:Log Module | po% | In small case |
INV:RPC Time Out | 1000 | |
INV:Debug Level | 11 | |
INV:Debug Trace | Yes | |
INV:Debug file | utl_file_dir/newfilename | To get utl_file_dir, use the following sql : select value from v$parameter where name ='utl_file_dir'; |
Initialization SQL Statement - Custom | Begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SETTRACEFILE_IDENTIFIER='||''''||'123456'||''''||' EVENTS='||''''||'10046TRACE NAME CONTEXT FOREVER, LEVEL 12'||'''');End; | Pls type the above in a single line |
2. Bounce the mobile port if the transaction is done thru mobile. Logout and relogin to the application. 3. Run SELECT MAX(LOG_SEQUENCE) FROM FND_LOG_MESSAGES; => Note down this value : value 1 4.Perform the transaction that is failing. Wait till you get the error message. 5. Run SELECT MAX(LOG_SEQUENCE) FROM FND_LOG_MESSAGES; => Note down this value : value 2 6. Pls get the o/p of the following query in .xls format select module, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message_text from fnd_log_messages where log_sequence between < value1 > and < value2 > ; 7. Sql trace file will get generated under udump folder. Use the following sql to get the udump path. SELECT value FROM v$parameter WHERE name ='user_dump_dest' ; Nowsearch in this udump folder for all files having the string '123456' inthe file name & upload all such files. 8. Other files to be uploaded: a) Inv log file. b) rcv11i o/p. c) Appscheck for PO & INV |
相关文章推荐
- Oracle EBS RCV模块日志收集方法
- Oracle EBS Shipping(WSH)模块日志收集方法
- Oracle EBS Shipping(WSH)模块日志收集方法
- Oracle EBS OM(Order Management)模块日志收集方法
- Oracle EBS SQL Trace日志收集的方法
- Oracle EBS SQL Trace日志收集的方法
- Oracle EBS各个模块日志收集的方法[Index]
- Oracle EBS各个模块日志收集的方法
- Oracle EBS各个模块日志收集的方法
- Oracle EBS各个模块日志收集的方法
- Oracle EBS WIP模块Debug Log收集方法
- Oracle EBS Inventory模块日志的收集
- Oracle EBS SQL Trace日志收集的方法
- oracle非归档模式下面的日志文件被意外的破坏的恢复方法
- oracle 误删除日志文件后的处理方法!
- 收集在不同的Oracle版本中取得當前SCN的方法
- EXCEL 数据导入ORACLE的方法汇总(收集)
- ORACLE用户常用数据字典的查询使用方法(转载收集)
- ORACLE 归档日志打开关闭方法
- Oracle日志损坏后的恢复方法