【求助】并发请求日志在哪

mercedesaa

运行请求，查看日志的时候总是提示，说更详细的让去看并发请求日志
那，弱弱地问一句并发请求日志在哪~~
谢谢啦~~

纵横四海

提示什么？

lzjkevin

你是在查看 current request log 吗? 最好是有一个截图, 一般 log 的内容都是跟你在 current request 的 log 是一样的

mercedesaa

此请求完成时出错，并且产生下列完成消息: 在为并发请求 353080 运行 Oracle 报表管理系统时，并发管理器遇到了一个错误。

有关详情，请复查您的并发请求日志和（或）报表输出文件。

处理的起始日期为 16-AUG-2010 11:12:34, 结束日期为 16-AUG-2010 11:12:49. 您可以在请求日志或并发管理器日志中找到有关出错原因的详细资料。

里面提到的“请求日志或并发管理器日志”在哪里呢，不是form右下角的查看日志吧……那个特别不详细

谢谢谢谢啦~~

mercedesaa

我在应用开发员-并发-程序里把相关请求的“调试开关”“跟踪开关”设为显示之后，选了“是”，之后的日志就完整多了，但是我还是很想知道在系统里相关的日志是存在哪个文件里的

93326736

select a.log_sequence, module,A.message_text,A.*

from apps.fnd_log_messages A  where a.log_sequence between   &sequence 1  and &sequence 2

mercedesaa

93326736 发表于 2010/9/2 11:03
select a.log_sequence, module,A.message_text,A.*

from apps.fnd_log_messages A  where a.log_sequen ...

试了一下，不过不太明白，麻烦讲解下吧~谢谢啦

93326736

Applies to:
Oracle Inventory Management - Version: 11.5.10 to 12.1.3 - Release: 11.5 to 12.1
Information in this document applies to any platform.
FORM:RCVRCERC - Enter Receipts GUI
FORM:RCVTXERT - Enter Receiving Transactions GUI
FORM:RCVTXECO - Enter Corrections GUI
FORM:RCVTXERE - Enter Returns GUI
FORM:RCVSHESH - Maintain Shipments
FORM:RCVRCMUR - Match Unordered Receipts
EXECUTABLE:RVCTP - Receiving Transaction Processor
EXECUTABLE:RCVTPO - Receiving Transaction Manager

This note was last modified on 02-JUL-2010
Goal
What setup is required to create debug statements for Receiving activities in 11.5.10 and R12, and where will the debug information be located?


For 12.0 (if Patch 9184617 has been applied), please follow instructions in Note 1063222.1 12.0: Simple Debug Setup For Receiving Transaction Activity

  
For 11.5.6 - 11.5.9, please follow instructions in Note 431053.1 How to Generate Receiving Transaction Debug Statements in 11.5.6 - 11.5.9



Solution
A. IMPORTANT INFORMATION ABOUT DEBUG PROFILES
1. Profile values should ONLY be set at User Level.  Severe performance issues may occur if the Profiles are set at any other level.

If RCV: Processing Mode=Immediate or On-line: set Profiles for the person who will perform the transaction
If RCV: Processing Mode=Batch: set profiles for the person who will run Receiving Transaction Processor Concurrent Program


2. The Profiles that need to be set are based on data associated with the document for which the transaction is being processed. If there is any doubt, set all the Profiles.

3. To reduce the debug output, perform the transaction for one line if the error will occur when only one line is processed; if more than one line must be processed to reproduce the error, transact the minimum number of lines that will cause the error to occur.

4. Reset the Profiles after the transaction is processed so debug information is not logged unnecessarily.

5.  If Profile RCV: Processing Mode=On-line,determine if the problem also occurs when Profile RCV: Processing Mode=Immediate (or Batch).  

It is easier to setup and retrieve debug and trace files when Profile RCV: Processing Mode=Immediate or Batch.
For information about the different processing modes used for Receiving activities, please review Note 197860.1 (Explanation of RCV: Processing Modes, Pending Transactions and Destination Types).
6.  For RCV: Processing Mode=On-line, run the following sql just before processing the transaction:
select max(log_sequence) from fnd_log_messages
**this is not required, but this value may be used in the Section E sql script to reduce the sql output


B. SET PROFILES
Most Profile values can be changed by Users (Edit > Preferences > Profiles), but some Profile values must be changed using a System Administrator Responsibility (Profile > System). When using a System Administrator Responsibility to change Profile values, enter the UserID and select the Checkbox 'Profiles with No Values'.

1. All transactions:
a. RCV: Debug Mode=Yes
b. FND: Debug Log Enabled=Yes
c. FND: Debug Log Level=Statement
d. FND: Debug Log Module=po%

The FND Profile names above will not include the word "Debug" if $FND_TOP/patch/115/import/US/aflogpro.ldt is version 115.11. The absence or presence of the word "Debug" does not affect the debugging process so it is not necessary to apply a patch or change the Profile names.


2. Line to be transacted references an Item:
a. TP:INV Transaction processing mode=On-line
b. INV: Debug Trace=Yes
c. INV:Debug Level=11
d. INV: Debug file (Including the complete path)=<valid directory path plus file name>
**example: /usr/tmp/invdebug.log
**User must have write privilege to the specified directory, and it must be listed in results of this sql: select value from v$parameter where name = 'utl_file_dir';

3. RMA, DropShip Purchase Order or Internal Sales Order/Requisition:
a. OM: Debug Level = 5
b. OM: Debug Log Directory = <valid directory path>
**example: /usr/tmp
**User must have write privilege to the specified directory, and it must be listed in results of this sql: select value from v$parameter where name = 'utl_file_dir';

4. When trace is requested:
a.  RCV: Processing Mode=Immediate or Batch:
PO:Enable Sql Trace for Receiving Processor=Yes
b.  RCV: Processing Mode=On-line:
Profile 'Initialization SQL Statement Custom' per Note 564817.1 (How To Create Forms And Database Level Trace For Receiving)

5. If WMS/Mobile Apps will be used to perform the transaction, bounce the Mobile server.

6. User whose Profiles were set must log out of application, then log back in.


C. PROCESS TRANSACTION
Perform the activity that will cause the error to occur.


D. RESET PROFILES
1. Reset the Profiles to their original values.
2. User whose Profiles were reset must log out of application, then log back in.


E. PROVIDE DEBUG INFORMATION FOR EACH MODULE
1. All transactions (a or b, not both):
a. RCV: Processing Mode=Immediate or Batch:
     1) Upload Receiving Transaction Processor Request Log (View > Requests)
     2) Upload output from the following in Excel format, including Column Headings:
     select
     to_char (timestamp,'DD-MON-YY HH24:MI:SS'),
     SUBSTR (message_text,1,300),
     SUBSTR (module,1,80),
     log_sequence
     from fnd_log_messages
     WHERE trunc(timestamp) = trunc(sysdate)
     AND process_id = (SELECT os_process_id FROM
     fnd_concurrent_requests WHERE
     request_id = &p_request_id)
     AND module not like 'fnd%'
     ORDER BY log_sequence;
     **where p_request_id = the request id for the Receiving Transaction Processor Concurrent Request
-OR-
b. RCV: Processing Mode=On-line:
     1) max log_sequence was obtained prior to processing the transaction:
     Upload output from the following in Excel format, including Column Headings:
     select to_char (timestamp,'DD-MON-YY HH24:MI:SS'),
     SUBSTR (message_text,1,300),
     SUBSTR (module,1,80),
     log_sequence
     from apps.fnd_log_messages
     WHERE log_sequence > &max_log_sequence
     and user_id = (select user_id from fnd_user where
     user_name=upper('&UserName'))
     and module not like 'fnd%'
     **use the sql below if the max log_sequence was not obtained prior to processing the transaction
     -OR-
     2) max log_sequence was not obtained prior to processing the transaction:
     select to_char (timestamp,'DD-MON-YYYY HH24:MI:SS'),
     SUBSTR (message_text,1,300),
     SUBSTR (module,1,80),
     log_sequence
     from fnd_log_messages
     WHERE timestamp >= to_date('DD-MON-YYYY HH24:MI:00','DD-MON-YYYY HH24:MI:SS')
     AND timestamp <= to_date('DD-MON-YYYY HH24:MI:00','DD-MON-YYYY HH24:MI:SS')
     and module not like 'fnd%';
     **substitute appropriate date and time values for DD-MON-YYYY HH24:MI:00

2. Inventory (if INV Profiles were set):
Upload the file specified in Section B Step 2d.

3. Order Management (if OM Profiles were set):
Upload the files created in the directory path specified in Section B Step 3b.


F. PROVIDE TRACE
1. Identify the trace directory path:
SELECT value FROM v$parameter WHERE name ='user_dump_dest';

2. RCV: Processing Mode=Immediate or Batch:
a. Identify the Request ID from Receiving Transaction Processor Request Log:
View > Requests > Query for Receiving Transaction Processor
b. select oracle_process_id from fnd_concurrent_requests
where request_id = &request_id;
c. Find the trace file using oracle_process_id

3. RCV: Processing Mode=On-line:
In the directory identified in Section F Step 1, search for
a. files created during the time the transaction was processed and which contain references to 'rcv_transactions_interface'
-OR-
b. if database trace was taken per Section B Step 4b, files that contain the word 'RCVTRACE' (or other value specified for Section B Step 4b).