Loading in 2 Seconds...
Loading in 2 Seconds...
Why is that LOV in the screen not returning me desired value?. Debugging LOV In a EBS screen, the LOV in this form does not bring back any records (in D2K) ?. Find the trace file location On the SQL*Plus run to find trace directory select value from v$parameter where name like 'user_dump_dest'.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Find the trace file locationOn the SQL*Plus run to find trace directoryselect value from v$parameter where name like 'user_dump_dest'
Use help/diagnostics to enable trace
Set trace with binds and waits, using help menu. Using the “binds” option, you will get to see value of the variables in SQL.
Go to database machine, to the trace directory, and ensure that you can access that trace file on the DB Server
You will be shown the path & name of the trace file
Now for test case, enter value in LOV field, and tab out to initiate SQL behind the LOV on that field. By doing so, this SQL that retrieves data for LOV will get written into the trace file
Inside the trace file, you can see the SQL and its bind values`
The trace files shows the SQL that was executed
For each SQL statement, you will also see the variable values in the trace file
:1 equates to Bind#0:2 equates to Bind#1Hence you can construct the exact SQL that screen is running
Extract the SQL with its Bind Variable Value so that it can be run offline in SQL*Plus Session
Yes, you can but :-Trace file gives you the bind variable valuesThe record group might have been altered programmatically or by Forms Personalization or from CUSTOM.pll. Hence using this technique, you get the end product SQL statement
You might be requested to develop a report that prints the data that is displayed from a screen. In this case, you can nick the SQL’s that screen uses, fine tune them for performance, and your report is almost ready.
You may wish to know the list of inserts/updates & deletes that are taking place from a screen, during data entry.
You may also wish to find out the SQL Statements/Cursors that are executed/fetched for validations.