JamesSmyth
Member
Many-year user of PL/SQL Developer. Love it.
However, we think that it is enabling session tracing at the server. We have this off by default on the database, and the PL/SQL Developer appears to be the only client that is generating trace (UDUMP .trc files).
Is this something we can disable? Brief searches of the web and your site don't show anything.
Just to be clear, the documentation (and the UI, via lack of check-mark indicator) seems to imply that sessions are normally not set to enable SQL Trace. But that doesn't appear to be the case (again, database-wide only for PL/SQL Developer client session)
PL/SQL Developer
Version 7.1.5.1396
01.42643 - 5 user license
Windows Vista 6.0 Build 6001 (Service Pack 1)
Physical memory : 2,097,152 kB (978,708 available)
Paging file : 4,194,304 kB (3,821,228 available)
Virtual memory : 2,097,024 kB (1,829,216 available)
Using
OCI: version 9.2
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0
Thanks,
James
However, we think that it is enabling session tracing at the server. We have this off by default on the database, and the PL/SQL Developer appears to be the only client that is generating trace (UDUMP .trc files).
Is this something we can disable? Brief searches of the web and your site don't show anything.
Just to be clear, the documentation (and the UI, via lack of check-mark indicator) seems to imply that sessions are normally not set to enable SQL Trace. But that doesn't appear to be the case (again, database-wide only for PL/SQL Developer client session)
PL/SQL Developer
Version 7.1.5.1396
01.42643 - 5 user license
Windows Vista 6.0 Build 6001 (Service Pack 1)
Physical memory : 2,097,152 kB (978,708 available)
Paging file : 4,194,304 kB (3,821,228 available)
Virtual memory : 2,097,024 kB (1,829,216 available)
Using
OCI: version 9.2
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0
Thanks,
James
Last edited: