Source : Metalink : Note : 459892.1
This creates separate user log files for both the Java Layer (middle tier) and PL/SQL (database tier) layers.
I. Generate Debug Log Files From iStore Catalog (Customer UI)
1. Set required profile options
1.1. Set the 'OM: Debug Log Directory' profile at the site level to a directory that is writable by the database server. The profile value must be one of the directories listed in the utl_file_dir parameter.
Note: To find the utl_file_dir value set, the following query may be executed:
select value from v$parameter where name = 'utl_file_dir'
1.2. Set following profiles:
Profile Name | Level | Value |
OM: Debug Level | Site | 5 |
IBE: Enable Debug | User | Yes |
ASO : Enable ASO Debug | User | Yes |
FND: Debug Log Enabled | User | Yes |
FND: Debug Log Module | User | % |
FND: Debug Log Level | User | Statement |
FND: Debug Log Filename | User |
Note:
- If the 'FND: Debug Log Filename' and' OM: Debug Log Directory' profiles are set to the same directory, be sure to specify a unique file name identifier for the value entered in the 'FND: Debug Log Filename'. By default the log file created in 'OM: Debug Log Directory' will have filename format of IBE_
- Replace
2. Open a new browser window and replicate the issue in iStore.
3. Unset profiles 'OM: Debug Level', 'IBE: Enable Debug', 'ASO : Enable ASO Debug' and FND: Debug Log Enabled' to stop the debugging.
4. Upload the following log files:
The iStore pl/sql log file will be generated in the directory (located in the Database Tier) specified by the 'OM: Debug Log Directory' System Profile and has the syntax of IBE_
The iStore java layer log file will be generated based of value specified by the 'FND: Debug Log Filename' system profile (located in the Middle Tier).
II. Generate Debug Log Files For GUEST User
To generate the iStore debug log files while you are accessing the iStore Catalog (Customer UI) as the "GUEST" user, you will just need to append '?&log=t' (without the single quotes) to the end of the URL before the step you want to debug while you are the guest user.
There is no need to set all profiles from section II.
For example: http://
This will generate both log files for any actions done in the browser after that. It is not necessary to append the parameter again for that session.
Once you close the browser, it stops the debugging. If new browser is started and append the parameter again, it starts a new set of log files.
See section I step 4. for location of the debug log files. The username will be GUEST
III. Generate Debug Log File From the iStore Administration UI
A debug log file can be generated from the iStore Site Administration User Interface.
1.1. Login to the Application Forms and set the following System Profiles at the user level to the following values:
Profile Name | Level |
FND: Debug Log Enabled | Yes |
FND: Debug Log Module | % |
FND: Debug Log Level | Statement |
FND: Debug Log Filename |
2.2. Replicate issue in iStore Administration UI
0 Responses to "How to generate Debug Log Files for Oracle iStore R12?"
Post a Comment