15 DBMS_ADDM
The DBMS_ADDM
package facilitates the use of Advisor functionality regarding the Automatic Database Diagnostic Monitor.
Note:
A multitenant container database is the only supported architecture in Oracle Database 21c and later releases. While the documentation is being revised, legacy terminology may persist. In most cases, "database" and "non-CDB" refer to a CDB or PDB, depending on context. In some contexts, such as upgrades, "non-CDB" refers to a non-CDB from a previous release.
This chapter contains the following topics:
See Also:
-
Oracle Real Application Clusters Administration and Deployment Guide for more information about "Automatic Workload Repository in Oracle Real Application Clusters Environments"
-
Oracle Database Performance Tuning Guide for more information about "Automatic Performance Diagnostics"
15.1 DBMS_ADDM Security Model
The DBMS_ADDM
package runs with the caller's permission, not the definer's, and then applies the security constraints required by the DBMS_ADVISOR
package.
See Also:
The DBMS_ADVISOR package for more information about "Security Model".
15.2 Summary of DBMS_ADDM Subprograms
The table in this topic lists and describes the DBMS_ADDM subprograms.
Table 15-1 DBMS_ADDM Package Subprograms
Subprogram | Description |
---|---|
Creates an ADDM task for analyzing in database analysis mode and executes it |
|
Creates an ADDM task for analyzing in instance analysis mode and executes it. |
|
Creates an ADDM task for analyzing a subset of instances in partial analysis mode and executes it |
|
Produces a Compare Period ADDM report comparing the performance of a capture to a replay |
|
Produces a Compare Period ADDM report for a database-wide performance comparison |
|
Produces a Compare Period ADDM report for an instance-level performance comparison |
|
Produces a Compare Period ADDM report comparing the performance of a replay to another replay |
|
Deletes an already created ADDM task (of any kind) |
|
Deletes a finding directive |
|
Deletes a parameter directive |
|
Deletes a segment directive |
|
Deletes a SQL directive |
|
Creates a plain text, user-readable report for the failed tasks registered in the |
|
Returns a string containing the SQL text of an ASH query identifying the rows in ASH with impact for the finding |
|
Retrieves the default text report of an executed ADDM task |
|
Creates a directive to limit reporting of a specific finding type. |
|
Creates a directive to prevent ADDM from creating actions to alter the value of a specific system parameter |
|
Creates a directive to prevent ADDM from creating actions to "run Segment Advisor" for specific segments |
|
Creates a directive to limit reporting of actions on specific SQL |
|
Produces a real-time report of ADDM activity |
|
Re-executes the tasks registered in the |
15.2.1 ANALYZE_DB Procedure
This procedure creates an ADDM task for analyzing in database analysis mode and executes it.
Syntax
DBMS_ADDM.ANALYZE_DB ( task_name IN OUT VARCHAR2, begin_snapshot IN NUMBER, end_snapshot IN NUMBER, read_only_type_override IN VARCHAR2, db_id IN NUMBER := NULL);
Parameters
Table 15-2 ANALYZE_DB Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task to be created. |
|
Number of the snapshot that starts the analysis period. |
|
Number of the snapshot that ends the analysis period. |
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
|
Database ID for the database you to analyze. By default, this is the database currently connected. |
Return Values
The name of the created task is returned in the task_name
parameter. It may be different from the value that is given as input (only in cases that name is already used by another task).
Examples
To create an ADDM task in database analysis mode and execute it, with its name in variable tname
:
var tname VARCHAR2(60); BEGIN :tname := 'my_database_analysis_mode_task'; DBMS_ADDM.ANALYZE_DB(:tname, 1, 2); END
To see a report:
SET LONG 100000 SET PAGESIZE 50000 SELECT DBMS_ADDM.GET_REPORT(:tname) FROM DUAL;
Note that the return type of a report is a CLOB
, formatted to fit line size of 80.
15.2.2 ANALYZE_INST Procedure
This procedure creates an ADDM task for analyzing in instance analysis mode and executes it.
Syntax
DBMS_ADDM.ANALYZE_INST ( task_name IN OUT VARCHAR2, begin_snapshot IN NUMBER, end_snapshot IN NUMBER, cdb_type_override IN VARCHAR2, read_only_type_override IN VARCHAR2, instance_number IN NUMBER := NULL, db_id IN NUMBER := NULL);
Parameters
Table 15-3 ANALYZE_INST Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task to be created |
|
Number of the snapshot that starts the analysis period |
|
Number of the snapshot that ends the analysis period |
|
Overrides the type of
CDB that ADDM determines for doing analysis. The possible values are:
|
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
|
Number of the instance to analyze. By default it is the instance currently connected |
|
Database ID for the database you to analyze. By default, this is the database currently connected |
Return Values
The name of the created task is returned in the task_name
parameter. It may be different from the value that is given as input (only in cases that name is already used by another task).
Usage Notes
On single instance systems (when not using Oracle RAC) the resulting task is identical to using the ANALYZE_DB
procedure.
Examples
To create an ADDM task in instance analysis mode and execute it, with its name in variable tname
:
var tname VARCHAR2(60); BEGIN :tname := 'my_instance_analysis_mode_task'; DBMS_ADDM.ANALYZE_INST(:tname, 1, 2); END
To see a report:
SET LONG 100000 SET PAGESIZE 50000 SELECT DBMS_ADDM.GET_REPORT(:tname) FROM DUAL;
Note that the return type of a report is a CLOB
, formatted to fit line size of 80.
15.2.3 ANALYZE_PARTIAL Procedure
This procedure creates an ADDM task for analyzing a subset of instances in partial analysis mode and executes it.
Syntax
DBMS_ADDM.ANALYZE_PARTIAL ( task_name IN OUT VARCHAR2, instance_numbers IN VARCHAR2, begin_snapshot IN NUMBER, end_snapshot IN NUMBER, cdb_type_override IN VARCHAR2, read_only_type_override IN VARCHAR2, db_id IN NUMBER := NULL);
Parameters
Table 15-4 ANALYZE_PARTIAL Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task to be created |
|
Comma separated list of instance numbers to analyze |
|
Number of the snapshot that starts the analysis period |
|
Number of the snapshot that ends the analysis period |
|
Overrides the type of
CDB that ADDM determines for doing analysis. The possible values are:
|
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
|
Database ID for the database you to analyze. By default, this is the database currently connected |
Return Values
The name of the created task is returned in the task_name
parameter. It may be different from the value that is given as input (only in cases that name is already used by another task).
Examples
To create an ADDM task in partial analysis mode and execute it, with its name in variable tname
:
var tname VARCHAR2(60); BEGIN :tname := 'my_partial_analysis_modetask'; DBMS_ADDM.ANALYZE_PARTIAL(:tname, '1,2,3', 1, 2); END
To see a report:
SET LONG 100000 SET PAGESIZE 50000 SELECT DBMS_ADDM.GET_REPORT(:tname) FROM DUAL;
Note that the return type of a report is a CLOB
, formatted to fit line size of 80.
15.2.4 COMPARE_CAPTURE_REPLAY_REPORT Function
This function produces a Compare Period ADDM report comparing the performance of a capture to a replay.
The AWR data must reside in the same database, but it can originate from different databases. The function generates a report in either XML or HTML(Active Report) format.
Syntax
DBMS_ADDM.COMPARE_CAPTURE_REPLAY_REPORT ( replay_id IN NUMBER, cdb_type_override IN VARCHAR2, read_only_type_override IN VARCHAR2, report_type IN VARCHAR2 := 'HTML') RETURN CLOB;
Parameters
Table 15-5 COMPARE_CAPTURE_REPLAY_REPORT Function Parameters
Parameter | Description |
---|---|
|
Replay ID to use as the base period. The base period is the baseline period to compare in order to determine improvement or regression. |
|
Overrides the type of
CDB that ADDM determines for doing analysis. The possible values are:
|
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
|
|
Return Values
A CLOB
containing a compare period ADDM report
15.2.5 COMPARE_DATABASES Function
This function produces a Compare Period ADDM report comparing the performance of a database over two different time periods or the performance of two different databases over two different time periods.
The AWR data must reside in the same database, but it can originate from different databases. The function generates a report in either XML or HTML(Active Report) format.
Syntax
DBMS_ADDM.COMPARE_DATABASES ( base_dbid IN NUMBER := NULL, base_begin_snap_id IN NUMBER, base_end_snap_id IN NUMBER, comp_dbid IN NUMBER := NULL, comp_begin_snap_id IN NUMBER, comp_end_snap_id IN NUMBER, cdb_type_override IN VARCHAR2, read_only_type_override IN VARCHAR2, report_type IN VARCHAR2 := 'HTML') RETURN CLOB;
Parameters
Table 15-6 COMPARE_DATABASES Function Parameters
Parameter | Description |
---|---|
|
Database id ( |
|
Begin AWR snapshot ID of the base period. |
|
End AWR snapshot ID of the base period. |
|
Database id ( |
|
Begin AWR snapshot ID of the comparison period |
|
End AWR snapshot ID of the comparison period |
|
Overrides the type of
CDB that ADDM determines for doing analysis. The possible values are:
|
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
|
|
Return Values
A CLOB
containing a compare period ADDM report
15.2.6 COMPARE_INSTANCES Function
This function produces a Compare Period ADDM report comparing the performance of a single instance over two different time periods or the performance of two different instances over two different time periods.
The AWR data must reside in the same database, but it can originate from different databases. The function generates a report in either XML or HTML(Active Report) format.
Syntax
DBMS_ADDM.COMPARE_INSTANCES ( base_dbid IN NUMBER := NULL, base_instance_id IN NUMBER, base_begin_snap_id IN NUMBER, base_end_snap_id IN NUMBER, comp_dbid IN NUMBER := NULL, comp_instance_id IN NUMBER, comp_begin_snap_id IN NUMBER, comp_end_snap_id IN NUMBER, cdb_type_override IN VARCHAR2, read_only_type_override IN VARCHAR2, report_type IN VARCHAR2 := 'HTML') RETURN CLOB;
Parameters
Table 15-7 COMPARE_INSTANCES Function Parameters
Parameter | Description |
---|---|
|
Database id ( |
|
Instance number of the database instance to include from the base period |
|
Begin AWR snapshot ID of the base period. |
|
End AWR snapshot ID of the base period. |
|
Database id ( |
|
Instance number of the database instance to include from the comparison period |
|
Begin AWR snapshot ID of the comparison period |
|
End AWR snapshot ID of the comparison period |
|
Overrides the type of
CDB that ADDM determines for doing analysis. The possible values are:
|
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
|
|
Return Values
A CLOB
containing a compare period ADDM report
15.2.7 COMPARE_REPLAY_REPLAY_REPORT Function
This function produces a Compare Period ADDM report comparing the performance of a replay to another replay.
The AWR data must reside in the same database, but it can originate from different databases. The function generates a report in either XML or HTML(Active Report) format.
Syntax
DBMS_ADDM.COMPARE_CAPTURE_REPLAY_REPORT ( replay_id1 IN NUMBER, replay_id2 IN NUMBER, cdb_type_override IN VARCHAR2, read_only_type_override IN VARCHAR2, report_type IN VARCHAR2 := 'HTML') RETURN CLOB;
Parameters
Table 15-8 COMPARE_REPLAY_REPLAY_REPORT Function Parameters
Parameter | Description |
---|---|
|
Replay ID to use as the base period. The base period is the baseline period to compare in order to determine improvement or regression. |
|
Replay ID to use as the comparison period. The comparison period is the period to compare to the base period in order to determine improvement or regression. |
|
Overrides the type of
CDB that ADDM determines for doing analysis. The possible values are:
|
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
|
|
Return Values
A CLOB
containing a compare period ADDM report
15.2.8 DELETE Procedure
This procedure deletes an already created ADDM task (of any kind). For database analysis mode and partial analysis mode this deletes the local tasks associated with the main task.
Syntax
DBMS_ADDM.DELETE ( task_name IN VARCHAR2);
Parameters
Table 15-9 DELETE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task to be deleted |
Examples
BEGIN DBMS_ADDM.DELETE ('my_partial_analysis_mode_task'); END
15.2.9 DELETE_FINDING_DIRECTIVE Procedure
This procedure deletes a finding directive.
Syntax
DBMS_ADDM.DELETE_FINDING_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2);
Parameters
Table 15-10 DELETE_FINDING_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
15.2.10 DELETE_PARAMETER_DIRECTIVE Procedure
This procedure deletes a parameter directive. This removes a specific system directive for parameters. Subsequent ADDM tasks are not affected by this directive.
Syntax
DBMS_ADDM.DELETE_PARAMETER_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2);
Parameters
Table 15-11 DELETE_PARAMETER_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
Examples
BEGIN DBMS_ADDM.DELETE_PARAMETER_DIRECTIVE (NULL,'my Parameter directive'); END;
15.2.11 DELETE_SEGMENT_DIRECTIVE Procedure
This procedure deletes a segment directive.
Syntax
DBMS_ADDM.DELETE_SEGMENT_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2);
Parameters
Table 15-12 DELETE_SEGMENT_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
15.2.12 DELETE_SQL_DIRECTIVE Procedure
This procedure deletes a SQL directive.
Syntax
DBMS_ADDM.DELETE_SQL_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2);
Parameters
Table 15-13 DELETE_SQL_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
15.2.13 FAILED_AUTO_TASKS_REPORT Function
This function creates a plain text, user-readable report for the failed tasks registered in the DBA_ADDM_PENDING_AUTOTASKS
views.
Syntax
DBMS_ADDM.FAILED_AUTO_TASKS_REPORT(
instance_number IN NUMBER :=NULL,
begin_snapshot IN NUMBER :=NULL,
end_snapshot IN NUMBER :=NULL,
dbid IN NUMBER :=NULL)
Parameters
Table 15-14 FAILED_AUTO_TASKS_REPORT Function Parameters
Parameter | Description |
---|---|
|
Instance number for the tasks to be reported. |
|
Earliest begin snapshot ID for the tasks to be reported. |
|
Latest end snapshot ID for the tasks to be reported. |
|
Database ID for the tasks to be reported. |
15.2.14 GET_ASH_QUERY Function
The function returns a string containing the SQL text of an ASH query identifying the rows in ASH with impact for the finding.
For most types of findings this identifies the exact rows in ASH corresponding to the finding. For some types of findings the query is an approximation and should not be used for exact identification of the finding's impact or the finding's specific activity.
Syntax
DBMS_ADDM.GET_ASH_QUERY ( task_name IN VARCHAR2, finding_id IN NUMBER) RETURN VARCHAR2;
Parameters
Table 15-15 GET_ASH_QUERY Function Parameters
Parameter | Description |
---|---|
|
Name of the task |
|
ID of the finding within the task |
Return Values
A VARCHAR
containing an ASH query identifying the rows in ASH with impact for the finding
15.2.15 GET_REPORT Function
This function retrieves the default text report of an executed ADDM task.
Syntax
DBMS_ADDM.GET_REPORT ( task_name IN VARCHAR2) RETURN CLOB;
Parameters
Table 15-16 GET_REPORT Function Parameters
Parameter | Description |
---|---|
|
Name of the task |
Examples
Set long 1000000 Set pagesize 50000 SELECT DBMS_ADDM.GET_REPORT('my_partial_analysis_mode_task') FROM DUAL;
15.2.16 INSERT_FINDING_DIRECTIVE Procedure
This procedure creates a directive to limit reporting of a specific finding type. The directive can be created for a specific task (only when the task is in INITIAL
status), or for all subsequently created ADDM tasks (such as a system directive).
Syntax
DBMS_ADDM.INSERT_FINDING_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2, finding_name IN VARCHAR2, min_active_sessions IN NUMBER := 0, min_perc_impact IN NUMBER := 0);
Parameters
Table 15-17 INSERT_FINDING_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
|
Name of an ADDM finding to which this directive applies. All valid findings names appear in the |
|
Minimal number of active sessions for the finding. If a finding has less than this number, it is filtered from the ADDM result. |
|
Minimal number for the "percent impact" of the finding relative to total database time in the analysis period. If the finding's impact is less than this number, it is filtered from the ADDM result. |
Examples
A new ADDM task is created to analyze a local instance. However, it has special treatment for 'Undersized SGA' findings. The result of GET_REPORT
shows only an 'Undersized SGA' finding if the finding is responsible for at least 2 average active sessions during the analysis period, and this constitutes at least 10% of the total database time during that period.
var tname VARCHAR2(60); BEGIN DBMS_ADDM.INSERT_FINDING_DIRECTIVE( NULL, 'Undersized SGA directive', 'Undersized SGA', 2, 10); :tname := 'my_instance_analysis_mode_task'; DBMS_ADDM.ANALYZE_INST(:tname, 1, 2); END;
To see a report containing 'Undersized SGA' findings regardless of the directive:
SELECT DBMS_ADVISOR.GET_TASK_REPORT(:tname, 'TEXT', 'ALL') FROM DUAL;
15.2.17 INSERT_PARAMETER_DIRECTIVE Procedure
This procedure creates a directive to prevent ADDM from creating actions to alter the value of a specific system parameter. The directive can be created for a specific task (only when the task is in INITIAL
status), or for all subsequently created ADDM tasks (such as a system directive).
Syntax
DBMS_ADDM.INSERT_PARAMETER_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2, parameter_name IN VARCHAR2);
Parameters
Table 15-18 INSERT_PARAMETER_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
|
Specifies the parameter to use. Valid parameter names appear in |
Examples
A new ADDM task is created to analyze a local instance. However, it has special treatment for all actions that recommend modifying the parameter 'sga_target
'. The result of GET_REPORT
does not show these actions.
var tname varchar2(60); BEGIN DBMS_ADDM.INSERT_PARAMETER_DIRECTIVE( NULL, 'my Parameter directive', 'sga_target'); :tname := 'my_instance_analysis_mode_task'; DBMS_ADDM.ANALYZE_INST(:tname, 1, 2); END;
To see a report containing all actions regardless of the directive:
SELECT DBMS_ADVISOR.GET_TASK_REPORT(:tname, 'TEXT', 'ALL') FROM DUAL;
15.2.18 INSERT_SEGMENT_DIRECTIVE Procedure
This procedure creates a directive to prevent ADDM from creating actions to "run Segment Advisor" for specific segments. The directive can be created for a specific task (only when the task is in INITIAL
status), or for all subsequently created ADDM tasks (such as a system directive).
Syntax
DBMS_ADDM.INSERT_SEGMENT_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2, owner_name IN VARCHAR2, object_name IN VARCHAR2 := NULL, sub_object_name IN VARCHAR2 := NULL);
DBMS_ADDM.INSERT_SEGMENT_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2, object_number IN NUMBER);
Parameters
Table 15-19 INSERT_SEGMENT_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
|
Specifies the owner of the segment/s to be filtered. A wildcard is allowed in the same syntax used for "like" constraints. |
|
Name of the main object to be filtered. Again, wildcards are allowed. The default value of |
|
Name of the part of the main object to be filtered. This could be a partition name, or even sub partitions (separated by a '.'). Again, wildcards are allowed. The default value of |
|
Object number of the |
Examples
A new ADDM task is created to analyze a local instance. However, it has special treatment for all segments that belong to user SCOTT
. The result of GET_REPORT
does not show actions for running Segment advisor for segments that belong to SCOTT
.
var tname VARCHAR2(60); BEGIN DBMS_ADDM.INSERT_SEGMENT_DIRECTIVE(NULL, 'my Segment directive', 'SCOTT'); :tname := 'my_instance_analysis_mode_task'; DBMS_ADDM.ANALYZE_INST(:tname, 1, 2); END;
To see a report containing all actions regardless of the directive:
SELECT DBMS_ADVISOR.GET_TASK_REPORT(:tname, 'TEXT', 'ALL') FROM DUAL;
15.2.19 INSERT_SQL_DIRECTIVE Procedure
This procedure creates a directive to limit reporting of actions on specific SQL. The directive can be created for a specific task (only when the task is in INITIAL
status), or for all subsequently created ADDM tasks (such as a system directive).
Syntax
DBMS_ADDM.INSERT_SQL_DIRECTIVE ( task_name IN VARCHAR2, dir_name IN VARCHAR2, sql_id IN VARCHAR2, min_active_sessions IN NUMBER := 0, min_response_time IN NUMBER := 0);
Parameters
Table 15-20 INSERT_SQL_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the task this directive applies to. If the value is |
|
Name of the directive. All directives must be given unique names. |
|
Identifies which SQL statement to filter. A valid value contains exactly 13 characters from '0' to '9' and 'a' to 'z'. |
|
Minimal number of active sessions for the SQL. If a SQL action has less than this number, it is filtered from the ADDM result. |
|
Minimal value for response time of the SQL (in microseconds). If the SQL had lower response time, it is filtered from the ADDM result. |
Examples
A new ADDM task is created to analyze a local instance. However, it has special treatment for SQL with id 'abcd123456789'. The result of GET_REPORT
shows only actions for that SQL (actions to tune the SQL, or to investigate application using it) if the SQL is responsible for at least 2 average active sessions during the analysis period, and the average response time was at least 1 second.
var tname VARCHAR2(60); BEGIN DBMS_ADDM.INSERT_SQL_DIRECTIVE( NULL, 'my SQL directive', 'abcd123456789', 2, 1000000); :tname := 'my_instance_analysis_mode_task'; DBMS_ADDM.ANALYZE_INST(:tname, 1, 2); END;
To see a report containing all actions regardless of the directive:
SELECT DBMS_ADVISOR.GET_TASK_REPORT(:tname, 'TEXT', 'ALL') FROM DUAL;
15.2.20 REAL_TIME_ADDM_REPORT Function
This function produces a real-time ADDM report for ADDM-related activity for the last five minutes. In an Oracle Real Application Clusters (Oracle RAC) environment, the function assumes that executing SQL over GV$
is possible.
Syntax
DBMS_ADDM.REAL_TIME_ADDM_REPORT ( cdb_type_override IN VARCHAR2, read_only_type_override IN VARCHAR2) RETURN CLOB;
Parameters
Table 15-21 REAL_TIME_ADDM_REPORT Function Parameters
Parameter | Description |
---|---|
|
Overrides the type of
CDB that ADDM determines for doing analysis. The possible values are:
|
|
Overrides the type of
CDB ADDM determines for analysis. The possible values are:
|
Return Values
CLOB
containing a real-time ADDM report
15.2.21 REEXECUTE_FAILED_AUTO_TASKS Procedure
This procedure re-executes the tasks registered in the DBA_ADDM_PENDING_AUTOTASKS
views.
This API can be called from both the CDB and PDB level. The user specifies the range for the snapshots or a time interval. The duration of the re-execution is time constrained by a user-specified parameter or a default value. Once a task has executed successfully, its corresponding row is removed from the DBA_ADDM_PENDING_AUTOTASKS
view.
Syntax
DBMS_ADDM.REXECUCUTE_FAILED_AUTO_TASKS(
instance_number IN NUMBER :=NULL,
begin_snapshot IN NUMBER :=NULL,
end_snapshot IN NUMBER :=NULL,
dbid IN NUMBER :=NULL,
time_budget_in_sec IN NUMBER :=NULL,
max_attempts IN NUMBER :=NULL);
Parameters
Table 15-22 REEXECUTE_FAILED_AUTO_TASKS Function Parameters
Parameter | Description |
---|---|
|
Instance number for the tasks to be re executed. |
|
Earliest begin snapshot ID for the tasks to be re executed. |
|
Latest end snapshot ID for the tasks to be re executed. |
|
Database ID for the tasks to be re executed. |
|
Forced time out to run the procedure after exiting. |
|
Maximum number of attempts to re execute a task. |