Print Thread
About dbms_trace data analysis in test window
#56390 04/25/17 01:47 PM
Joined: Jun 2003
Posts: 71
Russia
A
Albert Offline OP
Member
OP Offline
Member
A
Joined: Jun 2003
Posts: 71
Russia
Hello!
When we go to a trace tab after execution of the statement we can see that PSD runs such query for EVERY line of trace (table plsql_trace_events):

SQL Query
select text from sys.dba_source
where type = :unit_type
and owner = :unit_owner
and name = :unit_name
and line = :unit_line

It is extremally slow

Thank you


There are 10 types of people: those who know binary and those who don't
Re: About dbms_trace data analysis in test window
Albert #56394 04/26/17 08:15 AM
Joined: Aug 1999
Posts: 22,221
Member
Offline
Member
Joined: Aug 1999
Posts: 22,221
To obtain some more diagnostic information, can you modify the shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory or in the %APPDATA%\PLSQL Developer directory (e.g. C:\Users\<User>\AppData\Roaming\PLSQL Developer).


Marco Kalter
Allround Automations
Re: About dbms_trace data analysis in test window
Marco Kalter #56429 05/08/17 04:43 PM
Joined: Jun 2003
Posts: 71
Russia
A
Albert Offline OP
Member
OP Offline
Member
A
Joined: Jun 2003
Posts: 71
Russia
Hello, Marco
I've send the debug file to the mailbox support@allroundautomations.com
in addition
Such behaviour we can see in case of code profiling too (see trace file)
Thank you



There are 10 types of people: those who know binary and those who don't

Moderated by  support 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.4
(Release build 20200307)
Responsive Width:

PHP: 7.1.33 Page Time: 0.027s Queries: 14 (0.009s) Memory: 2.5056 MB (Peak: 3.0429 MB) Data Comp: Off Server Time: 2024-05-20 19:51:17 UTC
Valid HTML 5 and Valid CSS