Page History
...
Several Activity tab findings exist in the table to help the user. These findings are available in Service Caller and Web Transactions entities.
The Activity tab has the following findings:■ Slow
...
...
...
...
...
| Anchor | ||||
|---|---|---|---|---|
|
The statement is identified with a high average time in the chosen context. By tuning the statement, you may improve the application response time.
...
■ Check the Binds tab for possible offensive values resulting in differing execution plans and performance.
| Anchor | ||||
|---|---|---|---|---|
|
The J2EE Caller Service in the chosen context, spent a high amount of its resources on performing disk related full scans on the referenced object.
...
■ Move the objects to another tablespace with a higher block size.
| Anchor | ||||
|---|---|---|---|---|
|
The J2EE Caller Service in the chosen context, spent much of its In Oracle time waiting for the Redo Log events.
...
Whenever the Log Buffer Space and Log File Sync events occur together, consider changing the hidden LOG_I/O_SIZE parameter.
| Anchor | ||||
|---|---|---|---|---|
|
The J2EE Caller Service in the chosen context, spent much of its In Oracle time waiting for database buffer events.
...
DBWR processes or DBWR_I/O_SLAVES. Increase the buffer cache size.
| Anchor | ||||
|---|---|---|---|---|
|
The J2EE Caller Service in the chosen context, spent much of its In Oracle time waiting for the waiting on sort or hash operations performed on a temporary tablespace.
...
Run a statement with statistics_level=all. Click the Run and Compare tab. Examine LAST_TEMPSEG_SIZE and MAX_TEMPSEG_SIZE in the extended section of the run results. Change the SORT_AREA_SIZE to a higher value.
| Anchor | ||||
|---|---|---|---|---|
|
The statement is identified as a major consumer of the selected J2EE Caller's Oracle resources. By tuning the statement, you may improve the application response time.
...