-
What is Real-Time Database Operation Monitoring?
- A way of tracking a set of SQL statements
- Part of the tuning pack and subject to licence.
- Can find out where a SQL statement is current in the plan
-
In Real-Time Database Operation Monitoring, what is a database operation?
One or more SQL statements running in a single or concurrent sessions
-
In Real-Time Database Operation Monitoring, what are the two types of database operation?
- SIMPLE: A single SQL or PL/SQL database operation
- COMPOSITE: Multiple SQL PL/SQL database operations running in a single or concurrent sessions.
-
What is the main difference between 11g and 12c Real-Time Database Operation Monitoring
- In 11g it was only possible to monitor simple operation
- In 12c Real-Time Database Operations provide the ability to monitor composite operations
-
By default, when does Real-Time SQL Monitoring automatically start?
- When a SQL statement runs in parallel
- When 5 secs of CPU or IO has been consumed in a single session
-
From where can Real-Time SQL Monitoring information be accessed?
- EMCC
- Data Dictionary view
- DBMS_MONITOR package
-
What must the STATISTICS_LEVEL and CONTROL_MANAGEMENT_PACK_ACCESS level be set to to start Real-Time SQL Monitoring?
- STATISTICS_LEVEL: TYPICAL or ALL
- CONTROL_MANAGEMENT_PACK_ACCESS: DIAGNOSTIC+TUNING
-
How is a database operation identified in Real-Time SQL Monitoring
- An operation name
- An operation ID
-
Which view and which columns in that view identifying a Database Operation?
- V$SQL_MONITOR
- SQL_ID (SQL Statement ID)
- SQL_EXEC_START (Time of the sql execution start)
- SQL_EXEC_ID (The unique execution id)
-
How is a single statement monitored, how is monitoring of the statement stopped?
- Started: Using the hint /*+ MONITOR */
- Stopped: Using the hint /*+ NOMONITOR */
-
At what levels can Real-Time Database Operation Monitoring be done?
- Statement Level - /*+ (NO)MONITOR */
- Database Operation Level - DBMS_SQL_MONITOR.BEGIN|END_OPERATION
- System Level - All parallel and 5 secs of CPU or IO statements
-
What are the tasks to monitor a database operation in Real-Time SQL Monitoring?
- DBMS_SQL_MONITOR.BEGIN_OPERATION
- Run the operation
- DBMS_SQL_MONITOR.END_OPERATION
-
In DBMS_SQL_MONITOR.BEGIN_OPERATION, what does FORCE_TRACKING achieve?
- By default only parallel and 5 secs of CPU or IO statements are tracked, forced_tracking tracks all operations
- NO_FORCE_TRACKING is default
-
What is the syntax to begin a Real-Time SQL Monitoring?
- DBMS_SQL_MONITOR.BEGIN_OPERATION (
- dbop_name IN VARCHAR2,
- dbop_eid IN NUMBER := NULL,
- forced_tracking IN VARCHAR2 := NO_FORCE_TRACKING,
- attribute_list IN VARCHAR2 := NULL)
- RETURN NUMBER;
- What is the syntax to end a Real-Time SQL Monitoring?
- DBMS_SQL_MONITOR.END_OPERATION (
- dbop_name IN VARCHAR2,
- dbop_eid IN NUMBER := NULL,
- RETURN NUMBER;
-
How is a Real-Time SQL Monitoring report generated?
DBMS_SQL_MONITOR.REPORT_SQL_MONITOR
-
For which execution does DBMS_SQL_MONITOR.REPORT_SQL_MONITOR report?
The most recent
-
How can the state of an operation be determined?
From the STATUS column of V$SQL_MONITOR
-
What is the recommended method of viewing Real-Time SQL Monitoring reports?
EMCC
-
What tool can be used to find expensive SQL statements?
Real-Time SQL Monitoring
-
What tool can be used to compare current job execution with the previous executions?
Real-Time SQL Monitoring
|
|