AutoTrace execution result description

AutoTrace execution result Description: statistical information of the SQL code www.2cto.com listen 299 recursive cballs 0 db block gets 2359 consistent gets 0 physical reads 0 redo size 410 bytes sent via SQL * Net to client 385 bytes encoded ed via SQL * Net from client 2 SQL * Net roundtrips to/from client 5 sorts (memory) 0 sorts (disk) 1 rows processed www.2cto.com the data is the execution status of this SQL statement. The following describes the meaning of each data item: the number of recursive calls generated when the recursive CALS recursive call is executed. This parameter has a great relationship with the number of times the data dictionary is accessed. In general, this parameter value is not very large. Db block getsDB-number of database blocks in the database buffer zone when INSERT, DELETE, UPDATE, select for update occurs. In a SELECT statement, the value is generally 0. Db block gets + consistent gets = logical io (as opposed to physical io ). consistent gets consistent read-in addition to the number of data blocks read from the database buffer during select for update, db block gets + consistent gets = logical io (as opposed to physical io) physical reads physical read-physical reads = physical io (as opposed to logical io) redo size redo log size-during SQL Execution, size of the redo log generated bytes sent via SQL * Net to client the number of bytes sent to the client through SQL * net bytes encoded ed via SQL * Net from clie Nt uses SQL * net to accept the number of bytes of the client. SQL * net roundtrips to/from clientSee how setting the arraysize affects SQL * Net roundtrips to/from client. sorts (memory) sorting in memory sorts (disks) cannot be performed in memory, note 1. The number of records required by the hard disk to assist rows processed result www.2cto.com with AutoTrace optimization. you can set timing to get the time used to execute the SQL statement. However, you cannot set the time as the only measurement of SQL Execution efficiency. This time will include some time consumption for AUTOTRACE, so this time is not just the time for SQL Execution. This time may be slightly different from the SQL Execution time, especially when SQL is relatively simple. 2. Determine the SQL efficiency by executing the number of logical reads in the SQL Execution status