Article - CS66532
How to identify the source of a problematic SQLs and blocking database sessions in Windchill
Modified: 30-May-2023
Applies To
- FlexPLM 9.1 F000 to 12.0.0.1
- Windchill PDMLink 9.1 to 13.0
Description
- How to identify the origination of problem SQLs, or SQLs which block other database sessions?
- Top CPU SQLs
- Top elapsed time SQLs
- Top execution SQLs
- Top slow SQLs which show performance problem or take long time to run
- Database blockers which locked some resources and leads to other DML requests pending
- How to identify the source of a hung database transaction or long row lock?
- To address issues like:
- Many queue entries always run in Executing status, because of database blockers
- Request gets spinning due to DB Locks
- ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
This is a printer-friendly version of Article 66532 and may be out of date. For the latest version click CS66532