Oracle Applications: Debugging Using Log Files

Oracle Applications: Debugging Using Log Files


Many a times we would need to go through the log to find out the cause of the problem. Below is one quicker and easier way to do.

1. Set the following profiles at user level
a) FND: Debug Log Enabled   'Yes'
b) FND: Debug Log Level     'Statement'
c) FND: Debug Log Module    '%'
Log off and re login now.

2.
a)  Run the following query and note its output as log_val_1.

    select max(log_sequence) from fnd_log_messages;
b)  Perform the test case now.
   Once the process completes run the below query again and note its output as
   log_val_2.
   select max(log_sequence) from fnd_log_messages;
c)  Run the following query to fetch the log messages.
  select log_sequence, module, message_text
  from fnd_log_messages
  where log_sequence between log_val_1 and log_val_2
  order by log_sequence;


Capturing FND Debug log for a concurrent program Run:

SELECT LOG.MODULE, LOG.MESSAGE_TEXT
FROM FND_LOG_MESSAGES LOG, FND_LOG_TRANSACTION_CONTEXT CON
WHERE CON.TRANSACTION_ID = <conc_request_id>
AND CON.TRANSACTION_TYPE = 'REQUEST'
AND CON.TRANSACTION_CONTEXT_ID = LOG.TRANSACTION_CONTEXT_ID
ORDER BY LOG.LOG_SEQUENCE


Analyzing Output Post Processing Manager log File

 In case where your BI/XML Publisher report errors out you may need to access the OPP file and look for errors. Here is how you get to the file.

#cd  $APPLCSF/$APPLLOG
#grep -i <conc_req_id> *OPP*.txt
Once you find the file
#cat xxOPPxx.txt |more

Genering FND Debug for Custom Packages

Below statement has to be used in your custom plsql packages so that debug statements are included in the FND Debug log when generated

fnd_log.string(fnd_log.LEVEL_STATEMENT, 'XX Module Name',' Statement to Log ');



Resolving Locks

select * from v$locked_object;

select * from dba_objects where object_id in (<pull from above query>)

select * from v$session where sid in (<pull for above queries>);

sql>alter system kill session 'sid, serial#';