Page History
...
Several SQL tab findings exist to help the user. The SQL tab has the following findings:■
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Anchor | ||||
|---|---|---|---|---|
|
The result table for a sort operation could not be completed in memory and was performed on a temporary tablespace.
Table 12-42 Sorts Performed on Disk
...
| Description |
|---|
| What to do |
...
| next | In the Activity tab, examine temporary tablespace overtime I/O consumption for the statement, and the programs activating the statement. |
| Advice |
...
To reduce the I/O consumption for the sort operation, consider the following solutions: |
...
|
...
|
...
|
...
|
| Anchor | ||||
|---|---|---|---|---|
|
Some of the executions for the statement were not run in parallel; they worked serially. Oracle has reached the threshold of the MAX_PARALLEL_SERVERS and was not able to allocate parallel processes for the statement.
...
■ Set PARALLEL_AUTOMATIC_TUNING parameter in INIT.ORA to TRUE. This will make Oracle use more sophisticated algorithms in determining the number of PQ processes for each session.
| Anchor | ||||
|---|---|---|---|---|
|
Your statement has spent much of its In Oracle time waiting for a remote query to complete.
...
For example: the TNSNAMES.ORA configuration file and in the LISTENER.ORA configuration file in the Oracle database server.
| Anchor | ||||
|---|---|---|---|---|
|
Statement I/O is spent on scattered I/O (usually representing a full scan) on the index specified in the Object column.
...
Findings refer to the whole statement - not to a specific execution plan. If a step does not exist in the selected execution plan (unless this is due to an index overhead), switch to another plan and locate the relevant step.
| Anchor | ||||
|---|---|---|---|---|
|
Statement I/O is spent on sequential I/O (usually representing a range scan) on the index specified in the Object column. If the statement is DML and the index is not used in the execution plans, then the I/O represents the index maintenance overhead, caused by fetching the index blocks for update to memory.
...