In this Document
| Purpose |
| Troubleshooting Steps |
| General Performance |
| AWR Generation |
| AWR Interpretation |
| Buffer Busy Contention |
| Cache Buffers Chains Latch Contention |
| Connection Timeouts: Errors ORA-3135/ORA-3136 |
| Disk I/O |
| Enqueue/Locks |
| High Numbers of Child Cursors/High Cursor Version Counts |
| Hung database |
| Latches |
| Library Cache |
| Log File Sync |
| Mutex Contention |
| Operating System (OS) |
| Slow Database |
| SQL Tuning |
| SYSAUX$ Issues |
| TKProf Runtime Errors |
| Upgrade |
| Virtual Circuit Waits |
| 'WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!' |
| References |
This article provides a central point for Performance Troubleshooting advice.
This articles supercedes :
The following articles can help with the interpretation of diagnostics to troubleshoot various issues:
To troubleshoot the failure to collect AWR snapshots or reports, See:
How to troubleshoot performance issues using AWR snapshots or reports, See:
To troubleshoot issues where Buffers have become Busy due to concurrent access, see:
To troubleshoot issues caused by contention due to multiple sessions waiting to read the same block, see:
To troubleshoot issues caused by Connection Timeouts when errors such as ORA-3135 or ORA-3136 are seen, see:
For issues related to Disk Input/Ouput (IO),refer to :
For locking issues refer to :
When a SQL statement is executed, Oracle will try to match that statement up with an existing identical statement that has already been executed and attempt to reuse the stored parsed representation of it (which is stored within a cursor structure in the library cache). If the existing information in the cursor for that statement cannot be used, a new version of that statement will be created and used instead. If lots of versions of a particular statement are created, Oracle has to search through the versions to determine which (if any) can be shared. In extreme circumstances, this can cause mutex contention and other issue that degrade the database performance. In order to troubleshoot these issues and determine the cause, see:
To troubleshoot cases where the database appears to have hung, refer to :
To troubleshoot issues where there is contention on 'cache buffers chains' latches see:
For issues related to contention in the Library Cache
To troubleshoot issues where 'log file sync' is a primary cause of session wait activity, see:
For issues related to Mutex contention, refer to :
To troubleshoot Operating System (OS) related issues see:
To troubleshoot occasions where the database appears to be running more slowly than normal, refer to :
For issues with individual queries, refer to the following troubleshooting documents:
To troubleshoot issues related to upgrading a database see:
To troubleshoot issues when the database detects that a waiter has waited for a resource for longer than a particular threshold and he message "WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!" appears in the alert log, See:
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/18914315/viewspace-741879/ ,如需转载,请注明出处,否则将追究法律责任。