POSTED BY ABHIJIT RAY ⋅ AUGUST 15, 2012 ⋅ LEAVE A COMMENT

FILED UNDER FND: DEBUG LOG, FND_LOG_MESSAGES

Whenever an OAF page throws an error it is very difficult to get to the bottom of the error as the messages are quite cryptic and doesn’t clearly mention the root cause of the error. The following steps will show you how to get a trace of the OAF page error so that the issue can be analyzed.

Step 1: Change the profile option values

Responsibility: System Administrator

Navigation: Profile > System

Change the values of the following Profile Options:

FND: Debug Log Enabled = Yes
FND: Debug Log Filename for Middle-Tier = NULL
FND: Debug Log Level = Statement
FND: Debug Log Module = icx% (Set as per the module name)

Save the changes on the profile option values.

Step 2: Remove the old logs on FND_LOG_MESSAGES table

truncate table APPLSYS.FND_LOG_MESSAGES

Step 3: Bounce Apache

Bounce Apache/Web server. You can check this article to do so.

When you log in to Oracle you will see the following message on the home page,

Step 4: Reproduce the error

Now reproduce the error on the OAF page by following the exact steps.

Step 5: Query the error log in FND_LOG_MESSAGES table

After the error has been reproduced query the table FND_LOG_MESSAGES.

select * from APPLSYS.FND_LOG_MESSAGES

Now the error messages can be seen in the table and the error can be diagnosed.

How to generate logs for tracing OAF page errors