Document 778955.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Copyright (c) 2018, Oracle. All rights reserved.

How To Enable Diagnostics On The Help Menu And Gather A Forms Trace (Doc ID 778955.1)

In this Document

Goal
Solution
References

APPLIES TO:

Oracle Application Object Library - Version 11.5.4 to 12.0.6 [Release 11.5 to 12]
Information in this document applies to any platform.
Information in this document applies to any platform.
Oracle Applications 11i & R12 Help->Diagnostics

GOAL

This note explains how control the availability of help->diagnostics to the end user and create a trace file on a form.

SOLUTION

You will need to set 2 profile options, maybe 3 at the user level for one user to see diagnostics under the Help menu

Profile Options:

1· Hide Diagnostics Menu entry = No

This profile option controls the availability of the Diagnostics utility.

2. Utilities: Diagnostics = Yes

This profile Option determines whether a user can automatically use the
Diagnostics features. If Utilities:Diagnostics is set to No, then
users must enter the password for the APPS schema to use the Diagnostics
features.

3. Utilities:SQL Trace = Yes

Set this to yes if Help / Diagnostics / Trace / Trace with Binds and Waits
asks for the APPS Password.

Create trace file and run tkprof

Just before the step that will cause the issue, set trace using the following steps

a. NAV: Help / Diagnostics / Trace / Trace with Binds and Waits

b. Write down the trace file name or take a screen shot of the note that appears when you enable trace. This will allow the DBA to fine the
trace file easily

1. Perform the step that is causing the issue

2. Let the process complete

3. Turn off trace

4. The trace file will be located in the user_dump_dest directory.

Run the following SQL to check the location of user_dump_dest:

select value from v$parameter where name in 'user_dump_dest';

1 of 2 30-Apr-18 4:43 PM
Document 778955.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

5. TKPROF the trace file

tkprof trace_file_name.trc tkprof_file_name.txt sys=no explain=apps/<apps_password> sort='(prsela,exeela,fchela)'

6. Upload the following information to the SR

a. The RAW trace files generated by running the process

b. The TKPROF files generated

c. Information on Gather Stats: last time it ran on this schema with the degree of at least 30%, If possible run at 100% before gathering the
trace.

d. Precise Navigation in the forms to reproduce the issue.

Note:
You can also set the profile options at the responsibility level for more than one user or site level for all users. But remember Never give out
the Apps password, if you set profile option 1 above for a user or group of users also set profile option 2

REFERENCES

NOTE:245974.1 - FAQ - How to Use Debug Tools and Scripts for the VCP (aka APS) and EBS Applications
NOTE:274453.1 - Normal User Can Use The Diagnostics Features Without Entering The APPS Password
NOTE:743490.1 - Customization in Oracle Applications
Didn't find what you are looking for?

2 of 2 30-Apr-18 4:43 PM