Article - CS66532

How to identify the source of a problematic SQLs and blocking database sessions in Windchill

Modified: 31-May-2021   

Applies To

  • Windchill PDMLink 9.1 F000 to
  • Windchill ProjectLink 9.1 F000 to
  • Pro/INTRALINK 8.x + 9.1 F000 to
  • Windchill PDM Essentials 9.1 F000 to
  • PTC Arbortext Content Manager 9.1 F000 to
  • FlexPLM 9.1 F000 to


  • 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 PDF version of Article 66532 and may be out of date. For the latest version click