Oracle® Database PL/SQL Packages and Types Reference 11g Release 1 (11.1) Part Number B28419-01 |
|
|
View PDF |
The DBMS_WORKLOAD_REPOSITORY
package lets you manage the Workload Repository, performing operations such as managing snapshots and baselines.
See Also:
Oracle Database Performance Tuning Guide for more information about the "Automatic Workload Repository"The chapter contains the following topics:
Using DBMS_WORKLOAD_REPOSITORY
Examples
This section contains topics which relate to using the DBMS_WORKLOAD_REPOSITORY package.
This example shows how to generate an AWR text report with the DBMS_WORKLOAD_REPOSITORY
package for database identifier 1557521192, instance id 1, snapshot ids 5390 and 5391 and with default options.
-- make sure to set line size appropriately -- set linesize 152 SELECT output FROM TABLE( DBMS_WORKLOAD_REPOSITORY.AWR_REPORT_TEXT( 1557521192, 1, 5390, 5392) ) ;
You can call the DBMS_WORKLOAD_REPOSITORY
packaged functions directly as in the example, but Oracle recommends you use the corresponding supplied SQL script (awrrpt.sql
in this case) for the packaged function, which prompts the user for required information.
The DBMS_WORKLOAD_REPOSITORY
package defines an object and associated table type.
OBJECT Types
TABLE Types
This type shows the values of the metrics corresponding to a baseline.
Syntax
TYPE breakpoint_info AS OBJECT ( baseline_name VARCHAR2(64), dbid NUMBER NOT NULL, instance_number NUMBER NOT NULL, beg_time DATE NOT NULL, end_time DATE NOT NULL, metric_id NUMBER NOT NULL, metric_name VARCHAR2(64) NOT NULL, metric_unit VARCHAR2(64) NOT NULL, num_interval NUMBER NOT NULL, interval_size NUMBER NOT NULL, average NUMBER NOT NULL, minimum NUMBER NOT NULL, maximum NUMBER NOT NULL);
Fields
Table 146-1 RUNTIME_INFO Fields
Field | Description |
---|---|
baseline_name |
Name of the Baseline |
dbid |
Database ID for the snapshot |
instance_number | Instance number for the snapshot |
beg_time |
Begin time of the interval |
end_time |
End time of the interval |
metric_id |
Metric ID |
metric_name |
Metric name |
metric_unit |
Unit of measurement |
num_interval |
Number of intervals observed |
interval_size |
Interval size (in hundredths of a second) |
average |
Average over the period |
minimum |
Minimum value observed |
maximum |
Maximum value observed |
This type is used by the SELECT_BASELINE_METRICS Function.
Syntax
CREATE TYPE awr_baseline_metric_type_table AS TABLE OF awr_baseline_metric_type;
Table 146-2 DBMS_WORKLOAD_REPOSITORY Package Subprograms
Subprogram | Description |
---|---|
ASH_REPORT_HTML Function |
Displays the ASH report in HTML |
ASH_REPORT_TEXT Function |
Displays the ASH report in text |
AWR_DIFF_REPORT_HTML Function |
Displays the AWR Diff-Diff report in HTML |
AWR_DIFF_REPORT_TEXT Function |
Displays the AWR Diff-Diff report in text |
AWR_REPORT_HTML Function |
Displays the AWR report in HTML |
AWR_REPORT_TEXT Function |
Displays the AWR report in text |
AWR_SQL_REPORT_HTML Function |
Displays the AWR SQL Report in HTML format |
AWR_SQL_REPORT_TEXT Function |
Displays the AWR SQL Report in text format |
CREATE_BASELINE Functions & Procedures |
Creates a single baseline |
CREATE_BASELINE_TEMPLATE Procedures |
Creates a baseline template |
CREATE_SNAPSHOT Function and Procedure |
Creates a manual snapshot immediately |
DROP_BASELINE Procedure |
Drops a range of snapshots |
DROP_BASELINE_TEMPLATE Procedure |
Removes a baseline template that is no longer needed |
DROP_SNAPSHOT_RANGE Procedure |
Activates service |
MODIFY_SNAPSHOT_SETTINGS Procedures |
Modifies the snapshot settings |
MODIFY_BASELINE_WINDOW_SIZE Procedure |
Modifies the window size for the Default Moving Window Baseline |
RENAME_BASELINE Procedure |
Renames a baseline |
SELECT_BASELINE_METRICS Function |
Shows the values of the metrics corresponding to a baseline |
This procedure adds a colored SQL ID. If an SQL ID is colored, it will be captured in every snapshot, independent of its level of activities (so that it does not have to be a TOP
SQL
). Capture occurs if the SQL is found in the cursor cache at snapshot time.To uncolor the SQL, invoke the REMOVE_COLORED_SQL Procedure.
Syntax
DBMS_WORKLOAD_REPOSITORY.ASH_REPORT_HTML( sql_id IN VARCHAR2, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-3 ADD_COLORED_SQL Procedure Parameters
Parameter | Description |
---|---|
sql_id |
13-character external SQL ID |
dbid |
Optional dbid, defaults to Local DBID |
This table function displays the ASH Spot report in HTML.
Syntax
DBMS_WORKLOAD_REPOSITORY.ASH_REPORT_HTML( l_dbid IN NUMBER, l_inst_num IN NUMBER, l_btime IN DATE, l_etime IN DATE, l_options IN NUMBER DEFAULT 0, l_slot_width IN NUMBER DEFAULT 0, l_sid IN NUMBER DEFAULT NULL, l_sql_id IN VARCHAR2 DEFAULT NULL, l_wait_class IN VARCHAR2 DEFAULT NULL, l_service_hash IN NUMBER DEFAULT NULL, l_module IN VARCHAR2 DEFAULT NULL, l_action IN VARCHAR2 DEFAULT NULL, l_client_id IN VARCHAR2 DEFAULT NULL, l_plsql_entry IN VARCHAR2 DEFAULT NULL) RETURN awrrpt_html_type_table PIPELINED;
Parameters
Table 146-4 ASH_REPORT_HTML Parameters
Parameter | Description |
---|---|
l_dbid |
Database identifier |
l_inst_num |
Instance number |
l_btime |
The 'begin time' |
l_etime |
The 'end time' |
l_options |
Report level (currently not used) |
l_slot_width |
Specifies (in seconds) how wide the slots used in the "Top Activity" section of the report should be. This argument is optional, and if it is not specified the time interval between l_btime and l_etime is appropriately split into not more than 10 slots. |
l_sid |
Session ID (see Usage Notes) |
l_sql_id |
SQL ID (see Usage Notes) |
l_wait_class |
Wait class name (see Usage Notes) |
l_service_hash |
Service name hash (see Usage Notes) |
l_module |
Module name (see Usage Notes) |
l_action |
Action name (see Usage Notes) |
l_client_id |
Client ID for end-to-end backtracing (see Usage Notes) |
l_plsql_entry |
PL/SQL entry point (see Usage Notes) |
Return Values
The output will be one column of VARCHAR2(500)
.
Usage Notes
You can call the function directly but Oracle recommends you use the ashrpt.sql
script which prompts users for the required information.
The unspecified optional arguments are used to generate an ASH Reports that specify 'report targets' such as a SQL statement, or a session, or a particular Service/Module combination. These arguments are specified to restrict the ASH rows that would be used to generate the report. For example, to generate an ASH report on a particular SQL statement, such as SQL_ID 'abcdefghij123
' pass that sql_id
value to the l_sql_id
argument:
l_sql_id => 'abcdefghij123'
Any combination of those optional arguments can be passed in, and only rows in ASH that satisfy all of those 'report targets' will be used. If multiple 'report targets' are specified, AND
conditional logic is used to connect them. For example, to generate an ASH report on MODULE
"PAYROLL
" and ACTION
"PROCESS
", use the following predicate:
l_module => 'PAYROLL', l_action => 'PROCESS'
Valid SQL wildcards can be used in all the arguments that are of type VARCHAR2
.
Table 146-5 ASH_REPORT_HTML: Wildcards Allowed (or Not) in Arguments
Argument Name | Comment | Wildcard Allowed |
---|---|---|
l_sid |
Session ID (for example, V$SESSION.SID ) |
No |
l_sql_id |
SQL ID (for example, V$SQL.SQL_ID ) |
Yes |
l_wait_class |
Wait class name (for example, V$EVENT_NAME.WAIT_CLASS ) |
Yes |
l_service_hash |
Service name hash (for example, V$ACTIVE_SERVICES.NAME_HASH ) |
No |
l_module |
Module name (for example, V$SESSION.MODULE ) |
Yes |
l_action |
Action name (for example, V$SESSION.ACTION ) |
Yes |
l_client_id |
Client ID for end-to-end backtracing (for example, V$SESSION .CLIENT_IDENTIFIER ) |
Yes |
l_plsql_entry |
PL/SQL entry point (for example, "SYS .DBMS_LOB .*") |
Yes |
This table function displays the ASH Spot report in text.
Syntax
DBMS_WORKLOAD_REPOSITORY.ASH_REPORT_TEXT( l_dbid IN NUMBER, l_inst_num IN NUMBER, l_btime IN DATE, l_etime IN DATE, l_options IN NUMBER DEFAULT 0, l_slot_width IN NUMBER DEFAULT 0, l_sid IN NUMBER DEFAULT NULL, l_sql_id IN VARCHAR2 DEFAULT NULL, l_wait_class IN VARCHAR2 DEFAULT NULL, l_service_hash IN NUMBER DEFAULT NULL, l_module IN VARCHAR2 DEFAULT NULL, l_action IN VARCHAR2 DEFAULT NULL, l_client_id IN VARCHAR2 DEFAULT NULL, l_plsql_entry IN VARCHAR2 DEFAULT NULL) RETURN awrrpt_text_type_table PIPELINED;
Parameters
Table 146-6 ASH_REPORT_TEXT Parameters
Parameter | Description |
---|---|
l_dbid |
Database identifier |
l_inst_num |
Instance number |
l_btime |
The 'begin time' |
l_etime |
The 'end time' |
l_options |
Report level (currently not used) |
l_slot_width |
Specifies (in seconds) how wide the slots used in the "Top Activity" section of the report should be. This argument is optional, and if it is not specified the time interval between l_btime and l_etime is appropriately split into not more than 10 slots. |
l_sid |
Session ID (see Usage Notes) |
l_sql_id |
SQL ID (see Usage Notes) |
l_wait_class |
Wait class name (see Usage Notes) |
l_service_hash |
Service name hash (see Usage Notes) |
l_module |
Module name (see Usage Notes) |
l_action |
Action name (see Usage Notes) |
l_client_id |
Client ID for end-to-end backtracing (see Usage Notes) |
l_plsql_entry |
PL/SQL entry point (see Usage Notes) |
Return Values
The output will be one column of VARCHAR2(80)
.
Usage Notes
You can call the function directly but Oracle recommends you use the ashrpt.sql
script which prompts users for the required information.
The unspecified optional arguments are used to generate an ASH Reports that specify 'report targets' such as a SQL statement, or a session, or a particular Service/Module combination. These arguments are specified to restrict the ASH rows that would be used to generate the report. For example, to generate an ASH report on a particular SQL statement, such as SQL_ID 'abcdefghij123
' pass that sql_id value to the l_sql_id
argument:
l_sql_id => 'abcdefghij123'
Any combination of those optional arguments can be passed in, and only rows in ASH that satisfy all of those 'report targets' will be used. If multiple 'report targets' are specified, AND
conditional logic is used to connect them. For example, to generate an ASH report on MODULE
"PAYROLL
" and ACTION
"PROCESS
", use the following predicate:
l_module => 'PAYROLL', l_action => 'PROCESS'
Valid SQL wildcards can be used in all the arguments that are of type VARCHAR2
.
Table 146-7 ASH_REPORT_TEXT: Wildcards Allowed (or Not) in Arguments
Argument Name | Comment | Wildcard Allowed |
---|---|---|
l_sid |
Session ID (for example, V$SESSION.SID ) |
No |
l_sql_id |
SQL ID (for example, V$SQL.SQL_ID ) |
Yes |
l_wait_class |
Wait class name (for example, V$EVENT_NAME.WAIT_CLASS ) |
Yes |
l_service_hash |
Service name hash (for example, V$ACTIVE_SERVICES.NAME_HASH ) |
No |
l_module |
Module name (for example, V$SESSION.MODULE ) |
Yes |
l_action |
Action name (for example, V$SESSION.ACTION ) |
Yes |
l_client_id |
Client ID for end-to-end backtracing (for example, V$SESSION.CLIENT_IDENTIFIER ) |
Yes |
l_plsql_entry |
PL/SQL entry point (for example, "SYS .DBMS_LOB .*") |
Yes |
This table function displays the AWR Compare Periods report in HTML.
Syntax
DBMS_WORKLOAD_REPOSITORY.AWR_DIFF_REPORT_HTML( dbid1 IN NUMBER, inst_num1 IN NUMBER, bid1 IN NUMBER, eid1 IN NUMBER, dbid2 IN NUMBER, inst_num2 IN NUMBER, bid2 IN NUMBER, eid2 IN NUMBER) RETURN awrdrpt_text_type_table PIPELINED;
Parameters
Table 146-8 AWR_DIFF_REPORT_HTML Parameters
Parameter | Description |
---|---|
dbid 1 |
1st database identifier |
inst_num 1 |
1st instance number |
bid 1 |
1st 'Begin Snapshot' ID |
eid 1 |
1st 'End Snapshot' ID |
dbid 2 |
2nd database identifier |
inst_num 2 |
2nd instance number |
bid 2 |
2nd 'Begin Snapshot' ID |
eid 2 |
2nd 'End Snapshot' ID |
Return Values
The output will be one column of VARCHAR2(500)
.
Usage Notes
You can call the function directly but Oracle recommends you use the awrddrpt.sql
script which prompts users for the required information.
This table function displays the AWR Compare Periods report in text.
Syntax
DBMS_WORKLOAD_REPOSITORY.AWR_DIFF_REPORT_TEXT( dbid1 IN NUMBER, inst_num1 IN NUMBER, bid1 IN NUMBER, eid1 IN NUMBER, dbid2 IN NUMBER, inst_num2 IN NUMBER, bid2 IN NUMBER, eid2 IN NUMBER) RETURN awrdrpt_text_type_table PIPELINED;
Parameters
Table 146-9 AWR_DIFF_REPORT_TEXT Parameters
Parameter | Description |
---|---|
dbid 1 |
1st database identifier |
inst_num 1 |
1st instance number |
bid 1 |
1st 'Begin Snapshot' ID |
eid 1 |
1st 'End Snapshot' ID |
dbid 2 |
2nd database identifier |
inst_num 2 |
2nd instance number |
bid 2 |
2nd 'Begin Snapshot' ID |
eid 2 |
2nd 'End Snapshot' ID |
Return Values
The output will be one column of VARCHAR2(500)
.
Usage Notes
You can call the function directly but Oracle recommends you use the awrddrpt.sql
script which prompts users for the required information.
This table function displays the AWR report in HTML.
Syntax
DBMS_WORKLOAD_REPOSITORY.AWR_REPORT_HTML( l_dbid IN NUMBER, l_inst_num IN NUMBER, l_bid IN NUMBER, l_eid IN NUMBER, l_options IN NUMBER DEFAULT 0) RETURN awrrpt_text_type_table PIPELINED;
Parameters
Table 146-10 AWR_REPORT_HTML Parameters
Parameter | Description |
---|---|
l_dbid |
Database identifier |
l_inst_num |
Instance number |
l_bid |
The 'Begin Snapshot' ID |
l_eid |
The 'End Snapshot' ID |
l_options |
A flag to specify to control the output of the report. Currently, Oracle supports one value:
|
Return Values
The output will be one column of VARCHAR2(150)
.
Usage Notes
You can call the function directly but Oracle recommends you use the awrrpt.sql
script which prompts users for the required information.
This table function displays the AWR report in text.
Syntax
DBMS_WORKLOAD_REPOSITORY.AWR_REPORT_TEXT( l_dbid IN NUMBER, l_inst_num IN NUMBER, l_bid IN NUMBER, l_eid IN NUMBER, l_options IN NUMBER DEFAULT 0) RETURN awrrpt_text_type_table PIPELINED;
Parameters
Table 146-11 AWR_REPORT_TEXT Parameters
Parameter | Description |
---|---|
l_dbid |
Database identifier |
l_insT_num |
Instance number |
l_bid |
The 'Begin Snapshot' ID |
l_eid |
The 'End Snapshot' ID |
l_options |
A flag to specify to control the output of the report. Currently, Oracle supports one value:
|
Return Values
The output will be one column of VARCHAR2(80)
.
Usage Notes
You can call the function directly but Oracle recommends you use the awrrpt.sql
script which prompts users for the required information.
This table function displays the AWR SQL Report in HTML format.
Syntax
DBMS_WORKLOAD_REPOSITORY.AWR_SQL_REPORT_HTML( l_dbid IN NUMBER, l_inst_num IN NUMBER, l_bid IN NUMBER, l_eid IN NUMBER, l_sqlid IN VARCHAR2, l_options IN NUMBER DEFAULT 0) RETURN awrrpt_html_type_table PIPELINED;
Parameters
Table 146-12 AWR_SQL_REPORT_HTML Parameters
Parameter | Description |
---|---|
l_dbid |
Database identifier |
l_inst_num |
Instance number |
l_bid |
The 'Begin Snapshot' ID |
l_eid |
The 'End Snapshot' ID |
l_sqlid |
SQL ID of statement to be analyzed |
l_options |
A flag to specify to control the output of the report. Currently, not used. |
Return Values
The output will be one column of VARCHAR2(500)
.
Usage Notes
You can call the function directly but Oracle recommends you use the awrsqrpt.sql
script which prompts users for the required information.
This table function displays the AWR SQL Report in text format.
Syntax
DBMS_WORKLOAD_REPOSITORY.AWR_SQL_REPORT_TEXT( l_dbid IN NUMBER, l_inst_num IN NUMBER, l_bid IN NUMBER, l_eid IN NUMBER, l_sqlid IN VARCHAR2, l_options IN NUMBER DEFAULT 0) RETURN awrrpt_text_type_table PIPELINED;
Parameters
Table 146-13 AWR_SQL_REPORT_TEXT Parameters
Parameter | Description |
---|---|
l_dbid |
Database identifier |
l_inst_num |
Instance number |
l_bid |
The 'Begin Snapshot' ID |
l_eid |
The 'End Snapshot' ID |
l_sqlid |
SQL ID of statement to be analyzed |
l_options |
Flag to specify to control the output of the report. Currently, not used. |
Return Values
The output will be one column of VARCHAR2(120)
.
Usage Notes
You can call the function directly but Oracle recommends you use the awrsqrpt.sql
script which prompts users for the required information.
This function and procedure creates a baseline.
Syntax
DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE( start_snap_id IN NUMBER, end_snap_id IN NUMBER, baseline_name IN VARCHAR2, dbid IN NUMBER DEFAULT NULL, expiration IN NUMBER DEFAULT NULL); DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE( start_snap_id IN NUMBER, end_snap_id IN NUMBER, baseline_name IN VARCHAR2, dbid IN NUMBER DEFAULT NULL, expiration IN NUMBER DEFAULT NULL) RETURN NUMBER; DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE( start_time IN DATE, end_time IN DATE, baseline_name IN VARCHAR2, dbid IN NUMBER DEFAULT NULL, expiration IN NUMBER DEFAULT NULL); DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE( start_time IN DATE, end_time IN DATE, baseline_name IN VARCHAR2, dbid IN NUMBER DEFAULT NULL, expiration IN NUMBER DEFAULT NULL); RETURN NUMBER;
Parameters
Table 146-14 CREATE_BASELINE Function & Procedure Parameters
Parameter | Description |
---|---|
start_snap_id |
Start snapshot sequence number for the baseline' |
end_snap_id |
End snapshot sequence number for the baseline |
start_time |
Start time for the baseline' |
end_time |
End time for the baseline |
baseline_name |
Name of baseline. |
dbid |
Database Identifier for baseline. If NULL , this takes the database identifier for the local database. Defaults to NULL . |
expiration |
Expiration in number of days for the baseline. If NULL , then expiration is infinite, meaning do not drop baseline ever. Defaults to NULL . |
Exceptions
An error will be returned if this baseline name already exists in the system.
The snapshot range that is specified for this interface must be an existing pair of snapshots in the database. An error will be returned if the inputted snapshots do not exist in the system.
Examples
This example creates a baseline (named 'oltp_peakload_bl
') between snapshots 105 and 107 for the local database:
EXECUTE DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE (start_snap_id => 105, end_snap_id => 107, baseline_name => 'oltp_peakload_bl');
If you query the DBA_HIST_BASELINE
view after the CREATE
BASELINE
action, you will see the newly created baseline in the Workload Repository.
This procedure specifies a template for how they would like baselines to be created for future time periods.
Syntax
Specifies a template for generating a baseline for a single time period in the future.
DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATE( start_time IN DATE, end_time IN DATE, baseline_name IN VARCHAR2, template_name IN VARCHAR2, expiration IN NUMBER, dbid IN NUMBER DEFAULT NULL);
Specifies a template for creating and dropping baseline based on repeating time periods:
DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATE( day_of_week IN VARCHAR2, hour_in_day IN NUMBER, duration IN NUMBER, start_time IN DATE, end_time IN DATE, baseline_name_prefix IN VARCHAR2, template_name IN VARCHAR2, expiration IN NUMBER, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-15 CREATE_BASELINE_TEMPLATE Procedure Parameters
Parameter | Description |
---|---|
start_time |
Start Time for the baseline to be created' |
end_time |
End Time for the baseline to be created |
baseline_name |
Name of baseline to be created |
template_name |
Name for the template |
expiration |
Expiration in number of days for the baseline. If NULL , then expiration is infinite, meaning do not drop baseline ever. Defaults to NULL |
dbid |
Database Identifier for baseline. If NULL , this takes the database identifier for the local database. Defaults to NULL . |
day_of_week |
Day of week that the baseline should repeat on. Specify one of the following values: SUNDAY , MONDAY , TUESDAY , WEDNESDAY , THURSDAY , FRIDAY , SATURDAY . |
hour_in_day |
Value of 0-23 to specify the Hour in the Day the baseline should start |
duration |
Duration (in number of hours) after hour in the day that the baseline should last |
baseline_name_prefix |
Name for baseline prefix. When creating the baseline, the name of the baseline will be the prefix appended with the date information. |
This function and procedure create snapshots.In the case of the function, the snapshot ID is returned.
Syntax
DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT( flush_level IN VARCHAR2 DEFAULT 'TYPICAL'); DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT( flush_level IN VARCHAR2 DEFAULT 'TYPICAL') RETURN NUMBER;
Parameters
Table 146-16 CREATE_SNAPSHOT Parameters
Parameter | Description |
---|---|
flush_level |
Flush level for the snapshot is either 'TYPICAL ' or 'ALL ' |
Examples
This example creates a manual snapshot at the TYPICAL
level:
EXECUTE DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT();
If you query the DBA_HIST_SNAPSHOT
view after the CREATE_SNAPSHOT
action, you will see one more snapshot ID added to the Workload Repository.
This procedure drops a baseline.
Syntax
DBMS_WORKLOAD_REPOSITORY.DROP_BASELINE( baseline_name IN VARCHAR2, cascade IN BOOLEAN DEFAULT FALSE, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-17 DROP_BASELINE Parameters
Parameter | Description |
---|---|
baseline_name |
Name of baseline to drop from the system |
cascade |
If TRUE , the pair of snapshots associated with the baseline will also be dropped. Otherwise, only the baseline is removed. |
dbid |
Database Identifier for baseline. If NULL , this takes the database identifier for the local database. Defaults to NULL . |
Examples
This example drops the baseline 'oltp_peakload_bl
' without dropping the underlying snapshots:
EXECUTE DBMS_WORKLOAD_REPOSITORY.DROP_BASELINE ( baseline_name => 'oltp_peakload_bl');
If you query the DBA_HIST_BASELINE
view after the DROP_BASELINE
action, you will see the specified baseline definition is removed. You can query the DBA_HIST_SNAPSHOT
view to find that the underlying snapshots are left intact.
This procedure removes a template that is no longer needed.
Syntax
DBMS_WORKLOAD_REPOSITORY.DROP_BASELINE_TEMPLATE( template_name IN VARCHAR2, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-18 DROP_BASELINE_TEMPLATE Procedure Parameters
Parameter | Description |
---|---|
template_name |
Name of the template to remove |
dbid |
Database Identifier for baseline. If NULL , this takes the database identifier for the local database. Defaults to NULL . |
This procedure drops a range of snapshots.
Syntax
DBMS_WORKLOAD_REPOSITORY.DROP_SNAPSHOT_RANGE( low_snap_id IN NUMBER, high_snap_id IN NUMBER dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-19 DROP_SNAPSHOT_RANGE Procedure Parameters
Parameter | Description |
---|---|
low_snap_id |
Low snapshot id of snapshots to drop. |
high_snap_id |
High snapshot id of snapshots to drop. |
dbid |
Database id (default to local DBID. |
Examples
This example drops the range of snapshots between snapshot id 102 to 105 for the local database:
EXECUTE DBMS_WORKLOAD_REPOSITORY.DROP_SNAPSHOT_RANGE(102, 105);
If you query the dba_hist_snapshot
view after the Drop Snapshot
action, you will see that snapshots 102 to 105 are removed from the Workload Repository.
This procedure controls three aspects of snapshot generation.
The INTERVAL
setting affects how often snapshots are automatically captured.
The RETENTION
setting affects how long snapshots are retained in the Workload Repository.
The number of SQL captured for each Top criteria. If the user manually specifies a value for Top N SQL, the AWR SQL collection will use the user-specified number for both automatic and manual snapshots.
There are two overloads. The first takes a NUMBER
and the second takes a VARCHAR2
for the topnsql
argument. The differences are described under the Parameters description.
Syntax
DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS( retention IN NUMBER DEFAULT NULL, interval IN NUMBER DEFAULT NULL, topnsql IN NUMBER DEFAULT NULL, dbid IN NUMBER DEFAULT NULL); DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS( retention IN NUMBER DEFAULT NULL, interval IN NUMBER DEFAULT NULL, topnsql IN VARCHAR2, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-20 MODIFY_SNAPSHOT_SETTINGS Procedure Parameters
Parameter | Description |
---|---|
retention |
New retention time (in minutes). The specified value must be in the range of MIN_RETENTION (1 day) to MAX_RETENTION (100 years).
If If NOTE: The retention setting must be greater than or equal to the window size of the ' |
interval |
New interval setting between each snapshot, in units of minutes. The specified value must be in the range MIN_INTERVAL (10 minutes) to MAX_INTERVAL (1 year).
If If |
topnsql |
|
dbid |
Database identifier in AWR for which to modify the snapshot settings. If NULL is specified, the local dbid will be used. Defaults to NULL . |
Examples
This example changes the interval
setting to one hour and the retention
setting to two weeks for the local database:
EXECUTE DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS( interval => 60, retention => 20160);
If you query the DBA_HIST_WR_CONTROL
table after this procedure is executed, you will see the changes to these settings.
This procedure modifies the window size for the Default Moving Window Baseline.
Syntax
DBMS_WORKLOAD_REPOSITORY.MODIFY_BASELINE_WINDOW_SIZE( window_size IN NUMBER, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-21 MODIFY_BASELINE_WINDOW_SIZE Procedure Parameters
Parameter | Description |
---|---|
window_size |
New Window size for the default Moving Window Baseline, in number of days. |
dbid |
Database ID (default to local DBID) |
Usage Notes
The window size must be less than or equal to the AWR retention setting. If the window size needs to be greater than the retention setting, the MODIFY_SNAPSHOT_SETTINGS Procedures can be used to adjust the retention setting.
This procedure removes a colored SQL ID. After a SQL is uncolored, it will no longer be captured in a snapshot automatically, unless it makes the TOP
list.
Syntax
DBMS_WORKLOAD_REPOSITORY.ASH_REPORT_HTML( sql_id IN VARCHAR2, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-22 REMOVE_COLORED_SQL Procedure Parameters
Parameter | Description |
---|---|
sql_id |
13-character external SQL ID |
dbid |
Optional dbid, defaults to Local DBID |
This procedure renames a baseline.
Syntax
DBMS_WORKLOAD_REPOSITORY.RENAME_BASELINE( old_baseline_name IN VARCHAR2, new_baseline_name IN VARCHAR2, dbid IN NUMBER DEFAULT NULL);
Parameters
Table 146-23 RENAME_BASELINE Procedure Parameters
Parameter | Description |
---|---|
old_baseline_name |
Old baseline name |
new_baseline_name |
New baseline name |
dbid |
Database ID (default to local DBID) |
This table function shows the values of the metrics corresponding to a baseline. The table function will return an object of the AWR_BASELINE_METRIC_TYPE Object Type.
Syntax
DBMS_WORKLOAD_REPOSITORY.SELECT_BASELINE_METRICS( baseline_name IN VARCHAR2, dbid IN NUMBER DEFAULT NULL, instance_num IN NUMBER DEFAULT NULL) RETURN awr_baseline_metric_type_table PIPELINED;
Parameters
Table 146-24 SELECT_BASELINE_METRICS Procedure Parameters
Parameter | Description |
---|---|
baseline_name |
Name of the baseline for which we would like to view metrics |
dbid |
Database Identifier for baseline. If NULL , then use the database identifier for the local database. Defaults to NULL . |
instance_num |
Instance for which number the user wants to see statistics. If NULL , show statistics for the local instance. Defaults to NULL . |