Mechanisms to trace the document manager

What are the two mechanisms by which to trace the document manager? Explain them.

1. Set the debugging on by using profile option:
First Set profile option "Concurrent: Debug Flags" to TCTM1. This profile should only generate debugs when set at Site level as Document Manager can run in a different session. Secondly Bounce the Document Manager. Then Retry the Workflow to generate debugs. After generating debugs reset profile option "Concurrent: Debug Flags" to blank. At last check debug information in table
fnd_concurrent_debug_info

2. This can also be done by setting profile option “Initialization SQL Statement – Custom” against your username before reproducing the issue. The value of this profile will be set so as to enable trace using event 10046, level 12.
Enable tracing for document managers
This can be done by setting profile option “Initialization SQL Statement – Custom” against your username before reproducing the issue.......
Gather Stats and “Program - Optimizer [RGOPTM]”
Former cannot create any indexes but Stats will simply gather the stats against existing tables.......
FND Logging - oracle apps
Use FND Logging. At back Oracles FND Logging uses self reliant transaction to insert records in a table of name fnd_log_messages......
Post your comment