In special situations, the Oracle Database generates too many child cursors for particular SQL-IDs. This results in high CPU load on the DB server, coming from heavy mutex access. This is visible as mutex wait events.
The lecture will show how this situation arises, how the DBA can try to quick-fix it and how long-term solutions can be found.
Additionally, we will have a closer look on the Oracle internal situation: Why does the DB use mutexes here, and how?