Page History

Accessing Access the Database Platform Window

...

Multiple execution plans are presented in some cases such as if there are bind variables associated with a statement. Oracle examines the content of the bind variables and the associated table statistics and may determine that one execution plan may be more efficient than another depending on the value of the bind variable. When appropriate, multiple execution plans display on the SQL window where you can compare execution statistics and drill down to the explain plan SQL to determine why one explain plan is preferable. 

...

Set the Time Range

For the Activity and Statistics tabs, you can select the time period using the Date list and calendar settings at the top right of the window.

...

Set a Relative Time Period

Use the Date list to select a relative time period; options range from “Last 5 Minutes” to “Last 2 Weeks." If you select a time period of less than 30 minutes, then the UI will auto-refresh and retrieve the latest historical data at the end of the collector aggregation interval.

...

Set an Absolute Time Range

Use the calendar controls to select an absolute time range. Set the dates (in the form “YYYY-MM-DD HH:MI:SS”) and click Go to display data for this range.

...

View Historical Performance Data on the Activity window

The AppDynamics for Databases Activity window is the default window for the Database Platform. Most monitoring activities are reported here. The Activity window displays historical performance data that is retrieved from the repository.

...

• Executions: the number of SQL statements that were executed during that time period.
• In database: the total time spent executing those statements during that time period.

...

Set the View on the Activity Window

Click View on the Activity tab to change what appears in the Displayed rows section. The SQL View is the default.

...

For Oracle only. Wait state analysis is improved by the addition of a Wait Time chart as displayed, which allows you to see at a glance what functions are causing wait states in your environment and whether or not the time they consume is problematic.

...

View Historical %CPU Consumption

If, when you configured the AppDynamics for Databases collector, you enabled the Host Collector, then historical %CPU consumption metrics are available for the server hosting the monitored database.

...

ViewUp-to-the-Second Performance (Current window)

The AppDynamics for Databases Current window is the workspace where you can see an up-to-the-second view of performance. Rather than reading from the historical repository, the Current window connects directly to the monitored instance and requests current information using SQL queries.

...