Default Reaction Chains

From zzat
Jump to: navigation, search

The following reaction chains exist in zztat on a default installation:

Chain Reaction Sequence Includes

Corrective

Action

Requires

zz$sys_helper

Comments
SESSION_RO MARK_SQL

SEND_SESSION_REPORT

No Yes If available, marks the offending SQL statement and produces a session report showing what the offending session was doing.
SESSION_RW MARK_SQL

SEND_SESSION_REPORT

KILL_SESSION

Yes Yes If available, marks the offending SQL statement, produces a session report and terminates the offending session.
SESSION_LATCH_RO MARK_SQL

LATCH_HISPEED_SAMPLE

SEND_LATCH_REPORT

No Yes If available, marks the offending SQL statement, collects high-speed samples on latch data (for more information on how zztat does this, refer this blog post) on produces a latch report which it sends out by email.
SESSION_LATCH_RW MARK_SQL

LATCH_HISPEED_SAMPLE

SEND_LATCH_REPORT

KILL_SESSION

Yes Yes Identical to SESSION_LATCH_RO but also terminates the offending session.
SESSION_MEMORY_RO MARK_SQL

SEND_PGA_REPORT_LIGHT

No Yes Marks the offending SQL statement if there is one and produces a less detailed version of the session's PGA memory usage.
SESSION_MEMORY_RW MARK_SQL

SEND_PGA_REPORT_LIGHT

KILL_SESSION

Yes Yes Identical to SESSION_MEMORY_RO but also terminates the offending session.
SESSION_MEMORY_FULL_RO MARK_SQL

SEND_PGA_REPORT_FULL

No Yes Marks the offending SQL statement if there is one and produces a highly detailed version of the session's PGA memory usage. It will also tell you which area exactly is consuming the memory and uses a mnemonic translation to present the data in human-readable form wherever possible.

This report goes a lot further than any other Oracle PGA memory diagnostics tool out there. More details will follow soon in a blog post.

SESSION_MEMORY_FULL_RW MARK_SQL

SEND_PGA_REPORT_FULL

KILL_SESSION

Yes Yes Identical to SESSION_MEMORY_FULL_RO but also terminates the offending session.
SESSION_MUTEX_RO MARK_SQL

MUTEX_HISPEED_SAMPLE

SEND_MUTEX_REPORT

No Yes If available, marks the offending SQL statement, collects high-speed samples on mutex data (for more information on how zztat does this, refer this blog post) on produces a mutex report which it sends out by email.
SESSION_MUTEX_RW MARK_SQL

MUTEX_HISPEED_SAMPLE

SEND_MUTEX_REPORT

KILL_SESSION

Yes Yes Identical to SESSION_MUTEX_RO but also terminates the offending session.
STANDARD_ALERTING SEND_EMAIL No No Standard alerting via email. Automatically falls back to sending email via the repository if the target can't send emails.
TABLESPACE_RO SEND_EMAIL No No Alerts via email if a tablespace runs full beyond the threshold.
TABLESPACE_RW SEND_EMAIL

ADD_DATAFILE

Yes Yes Automatically adds a datafile when the tablespace runs full beyond the threshold and sends an informative email.
VERBOSE_ALERTING WRITE_ALERT_LOG

SEND_EMAIL

No Yes Writes to the database alert log and sends alerts via email.

Notes:

  • Everything that uses emails has an automatic fall back to proxy emails through the repository if the target has not been configured to send emails. This includes standard email alerts as well as any reports sent via email.
  • The automatic datafile addition provided by TABLESPACE_RW must be configured first before this reaction chain can be added to a gauge.
  • Marked SQL statements are considered "interesting SQL" statement in the zztat framework and will get their execution statistics collected as part of the "Top SQL" automatically for as long as they are seen regularly in the database. How long they remain marked can be controlled via zz$manage.reaction_config.