Toad World® Forums

Wrong format of AUTOTRACE

SET AUTOTRACE ON;
SELECT * FROM dual;

With 13.2.0.162 (64bit) the output is:

DUMMY
-----
X
1 row selected.

Execution Plan
----------------------------------------------------------   0       SELECT STATEMENT Optimizer Mode=ALL_ROWS (Cost=2 Card=1 Bytes=2)
   1    0    TABLE ACCESS FULL SYS.DUAL (Cost=2 Card=1 Bytes=2)
Statistics
----------------------------------------------------------          0  recursive calls          0  spare statistic 11          0  spare statistic 15          0  spare statistic 24          0  commit cleanout failures: buffer being written          0  securefile direct read ops          0  securefile direct write ops          0  securefile inode read time          0  securefile uncompressed bytes          0  securefile bytes deduplicated          1  rows processed

With 13.1 the output is as expected:

DUMMY
-----
X    
1 row selected.

Execution Plan
----------------------------------------------------------
   0       SELECT STATEMENT Optimizer Mode=ALL_ROWS (Cost=2 Card=1 Bytes=2)
   1    0    TABLE ACCESS FULL SYS.DUAL (Cost=2 Card=1 Bytes=2)

Statistics
----------------------------------------------------------
          0  recursive calls
          0  spare statistic 11
          0  spare statistic 15
          0  spare statistic 24
          0  commit cleanout failures: buffer being written
          0  securefile direct read ops
          0  securefile direct write ops
          0  securefile inode read time
          0  securefile uncompressed bytes
          0  securefile bytes deduplicated
          1  rows processed

DB runs on Linux, might be a problem with line-endings?

Hi,

I've tested this both with 13.2.0.161 and 13.2.0.165 and the result is correct. My DB runs on a Linux as well, while the client is win7 64bit.

Dirk

Interresting, thanks Dirk!
My client is Win10 64bit with TOAD 13.2.0.165 64bit.

I can reproduce it with Oracle 10, 11 and 12.