Erreurs ORA 13600 à 13871 Cause et Action
LISTE CODE ERREURS ORACLE.
|
ORA-13600
|
ORA-13600: error encountered in Advisor string
|
|
Cause
|
An error occurred in the Advisor. This message will be followed by a second message giving more details about the nature of the error.
|
|
Action
|
See the Advisor documentation for an explanation of the second error message.
|
|
ORA-13601
|
ORA-13601: The specified Advisor string does not exist.
|
|
Cause
|
The user specified an advisor name that has not be defined in the advisor repository.
|
|
Action
|
Correct the advisor name and retry the operation.
|
|
ORA-13602
|
ORA-13602: The specified parameter string is not valid for task or object string.
|
|
Cause
|
The user attempted to access a task parameter that does not exist for the specified advisor object. The parameter may be misspelled or the user has selected a parameter that is not
supported by the particular advisor.
|
|
Action
|
Validate the parameter name and retry the operation.
|
|
ORA-13603
|
ORA-13603: The specified parameter string cannot be fetched as a numeric value for task or object string.
|
|
Cause
|
The user attempted to retrieve a string parameter as a numeric value.
|
|
Action
|
Check the datatype for the task parameter and retry the operation.
|
|
ORA-13604
|
ORA-13604: The specified parameter string cannot be fetched as a SQL table.
|
|
Cause
|
The user attempted to retrieve a non-table parameter as a table name.
|
|
Action
|
Check the datatype for the task parameter and retry the operation.
|
|
ORA-13605
|
ORA-13605: The specified task or object string does not exist for the current user.
|
|
Cause
|
The user attempted to reference an advisor task or object using a name that does not exist in the Advisor repository.
|
|
Action
|
Adjust the name and retry the operation.
|
|
ORA-13606
|
ORA-13606: the specified task parameter element string is out of range for parameter string.
|
|
Cause
|
The user attempted to reference an invalid parameter element.
|
|
Action
|
Adjust the element offset and retry the operation.
|
|
ORA-13607
|
ORA-13607: The specified task or object string already exists
|
|
Cause
|
The user attempted to create the specified task or object using a name that already exists in the Advisor repository. Task names must be unique to the database user.
|
|
Action
|
Adjust the name and retry the operation.
|
|
ORA-13608
|
ORA-13608: The task or object name string is invalid.
|
|
Cause
|
The user attempted to specify a task name that contains invalid characters or an invalid wildcard specifier.
|
|
Action
|
Adjust the name and retry the operation.
|
|
ORA-13609
|
ORA-13609: The specified task string must be executing to be cancelled or interrupted.
|
|
Cause
|
The user attempted to cancel or interrupt a task that is not currently executing.
|
|
Action
|
Check the status of the task and retry the operation.
|
|
ORA-13610
|
ORA-13610: The directive string does not exist for task string.
|
|
Cause
|
The user attempted to access a task directive that does not exist.
|
|
Action
|
Validate the directive and retry the operation.
|
|
ORA-13611
|
ORA-13611: The command string is not a valid advisor command.
|
|
Cause
|
The user attempted to specify a command that does not exist.
|
|
Action
|
Validate the command and retry the operation.
|
|
ORA-13612
|
ORA-13612: The recommendation action string,string is not valid for task string.
|
|
Cause
|
The user attempted to access a recommendation action that does not exist in the task.
|
|
Action
|
Validate the recommendation-action and retry the operation.
|
|
ORA-13613
|
ORA-13613: The requested operation is not supported for this advisor object.
|
|
Cause
|
The user attempted to perform an operation that is not supported for the particular advisor or task type.
|
|
Action
|
Validate the task or object and retry the operation.
|
|
ORA-13614
|
ORA-13614: The template string is not compatible with the current advisor.
|
|
Cause
|
The user attempted to create a new task or object using an existing task or object that was not created by the same advisor.
|
|
Action
|
Validate the template and retry the operation.
|
|
ORA-13615
|
ORA-13615: The task or object string is greater than the maximum allowable length of 30 characters.
|
|
Cause
|
The user attempted to create a new task or object using a name that is too long.
|
|
Action
|
Shorten the name and retry the operation.
|
|
ORA-13616
|
ORA-13616: The current user string has not been granted the ADVISOR privilege.
|
|
Cause
|
The user attempted an advisor operation that requires privilege.
|
|
Action
|
Adjust the user"s privileges and retry the operation.
|
|
ORA-13617
|
ORA-13617: The specified task string already executing
|
|
Cause
|
The user attempted to execute a task that is currently executing.
|
|
Action
|
Wait for the task to finish before attempting any further task activities.
|
|
ORA-13618
|
ORA-13618: The specified value is not a valid value for procedure argument string.
|
|
Cause
|
The user executed a procedure but failed to provide correct values for the argument.
|
|
Action
|
Correct the procedure arguments and retry the operation.
|
|
ORA-13619
|
ORA-13619: The procedure argument string is greater than the maximum allowable length of string characters.
|
|
Cause
|
The user attempted to pass a character argument that is too long.
|
|
Action
|
Shorten the specified character argument and retry the operation.
|
|
ORA-13620
|
ORA-13620: The task or object string is read-only and cannot be deleted or modified.
|
|
Cause
|
The user attempted to perform an operation that will update or delete a read-only task or object.
|
|
Action
|
Adjust the READ_ONLY property for the object and retry the operation.
|
|
ORA-13621
|
ORA-13621: The task_or object string is marked as a template and cannot perform the requested operation.
|
|
Cause
|
The user attempted perform an unsupported operation on a task or object that is identified as a template.
|
|
Action
|
Choose a different object and retry the operation.
|
|
ORA-13622
|
ORA-13622: invalid recommendation annotation
|
|
Cause
|
The user attempted to mark a recommendation using an invalid annotation. Valid annotation actions are ACCEPT, REJECT and IGNORE.
|
|
Action
|
Correct the action and retry the operation.
|
|
ORA-13623
|
ORA-13623: The recommendation string is not valid for task string.
|
|
Cause
|
The user attempted to access a recommendation that does not exist in the task.
|
|
Action
|
Validate the recommendation and retry the operation.
|
|
ORA-13624
|
ORA-13624: The task string is executing and cannot be deleted or modified.
|
|
Cause
|
The user attempted to access a task that currently executing.
|
|
Action
|
Wait for the task to complete and retry the operation.
|
|
ORA-13625
|
ORA-13625: %s is an invalid advisor object type.
|
|
Cause
|
The user has specified an invlaid object type.
|
|
Action
|
Refre to dba_advisor_object_types for all valid object types
|
|
ORA-13626
|
ORA-13626: The specified object string is not valid for task string.
|
|
Cause
|
The user specified an non-existent object for the task
|
|
Action
|
Choose a different object and retry the operation.
|
|
ORA-13627
|
ORA-13627: Setting of parameter string is disallowed until the task is reset.
|
|
Cause
|
The user attempted to set the value of a parameter before the task was reset. This parameter cannot be changed until the task is reset.
|
|
Action
|
Reset the task and retry the operation.
|
|
ORA-13628
|
ORA-13628: Insufficient privileges to access the task belonging to the specified user
|
|
Cause
|
The user could not access dba_* views.
|
|
Action
|
Retry operation as owner of the task or after granting new privileges.
|
|
ORA-13629
|
ORA-13629: The task or object string is being used by another operation.
|
|
Cause
|
The user attempted to access a task or object that is locked by another session.
|
|
Action
|
Wait for the task or object activity to complete and retry the operation.
|
|
ORA-13630
|
ORA-13630: The task string contains execution results and cannot be executed.
|
|
Cause
|
The user attempted to execute a task that already contains execution results.
|
|
Action
|
Reset the task to its initial state and retry the operation.
|
|
ORA-13631
|
ORA-13631: The task string contains no execution results.
|
|
Cause
|
The user attempted to create a report or script from a task that has not successfully completed an execution.
|
|
Action
|
Execute the task and then retry the operation
|
|
ORA-13632
|
ORA-13632: The user cancelled the current operation.
|
|
Cause
|
The user signaled a cancel during a task or object operation.
|
|
Action
|
None
|
|
ORA-13633
|
ORA-13633: The task string was interrupted and needs to be resumed.
|
|
Cause
|
The user attempted to execute a task that was interrupted.
|
|
Action
|
Resume the execution of the task via the RESUME_TASK API.
|
|
ORA-13634
|
ORA-13634: The task string needs to be reset before being re-executed.
|
|
Cause
|
The task must be in an inital state to be executed.
|
|
Action
|
Reset the task to its initial state and retry the operation.
|
|
ORA-13635
|
ORA-13635: The value provided for parameter string cannot be converted to a number.
|
|
Cause
|
A numeric parameter was incorrectly supplied in string form.
|
|
Action
|
Retry by supplying valid numeric value.
|
|
ORA-13636
|
ORA-13636: The specified value provided for parameter string is not valid for this advisor.
|
|
Cause
|
The user supplied an invalid parameter value.
|
|
Action
|
Retry by supplying valid value.
|
|
ORA-13637
|
ORA-13637: Executing or modifying task string is disallowed until the task is reset to its initial state.
|
|
Cause
|
The user attempted to execute or modify the task that is in not in its INITIAL state.
|
|
Action
|
Reset the task and retry the operation.
|
|
ORA-13638
|
ORA-13638: The user interrupted the current operation.
|
|
Cause
|
The user signaled an interrupt during a task or object operation.
|
|
Action
|
None
|
|
ORA-13639
|
ORA-13639: The current operation was interrupted because it timed out.
|
|
Cause
|
The task or object operation timed out.
|
|
Action
|
None
|
|
ORA-13640
|
ORA-13640: The current operation was cancelled because it timed out, and was not in interruptible mode.
|
|
Cause
|
The task or object operation timed out.
|
|
Action
|
None
|
|
ORA-13641
|
ORA-13641: Task cannot be interrupted yet. You may cancel it instead.
|
|
Cause
|
The user attempted to interrupt a task that has not reached interruptible mode.
|
|
Action
|
Wait until the task reaches interruptible mode, or cancel the task execution.
|
|
ORA-13642
|
ORA-13642: The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
|
|
Cause
|
The user supplied a date value in an incorrect format.
|
|
Action
|
Retry by supplying valid value.
|
|
ORA-13643
|
ORA-13643: The task can not be interrupted or cancelled.
|
|
Cause
|
Request to interrupt or cancel task execution can not be granted because the task has not reached the appropriate mode.
|
|
Action
|
User should wait for a few seconds and try again.
|
|
ORA-13644
|
ORA-13644: The user "string" is invalid.
|
|
Cause
|
Invalid user name specified to advisor framework
|
|
Action
|
User should specify a correct, case-sensitive, name
|
|
ORA-13699
|
ORA-13699: Advisor feature is not currently implemented.
|
|
Cause
|
The user attempted to execute an unsupported advisor operation.
|
|
Action
|
Verify the availability of the operation.
|
|
ORA-13701
|
ORA-13701: Snapshot pair [string, string] seems to be specified in reverse order.
|
|
Cause
|
The start snapshot id was greater than the end snapshot id.
|
|
Action
|
Swap the start and end snapshot ids.
|
|
ORA-13702
|
ORA-13702: Snapshot IDs specified by the range [string, string] are equal.
|
|
Cause
|
The start snapshot id and end snapshot id were identical.
|
|
Action
|
Provide different start and end snapshot ids.
|
|
ORA-13703
|
ORA-13703: The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
|
|
Cause
|
The snapshot ids or the database id or the instance id was invalid or the specified snapshots have already been purged.
|
|
Action
|
Set valid snapshot ids and retry.
|
|
ORA-13704
|
ORA-13704: Invalid value "string" specified for parameter "string".
|
|
Cause
|
The parameter was not set before executing the ADDM.
|
|
Action
|
Set the parameter to a valid value and retry.
|
|
ORA-13705
|
ORA-13705: There was a instance shutdown/startup between the snapshots in the range [string, string].
|
|
Cause
|
Instance was shut down and restarted between the two specified snapshots.
|
|
Action
|
Specify start and end snapshot ids that does not have a shutdown/startup in between them.
|
|
ORA-13706
|
ORA-13706: Invalid value "string" specified for parameter "string" in "string" analysis mode.
|
|
Cause
|
The parameter was not set to an acceptable value for this particular mode of analysis.
|
|
Action
|
Set the parameter to a valid value and retry.
|
|
ORA-13707
|
ORA-13707: Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.
|
|
Cause
|
Either the start or the end snaphots was missing or purged or had encountered errors while creating them.
|
|
Action
|
Verify that AWR is done taking these two snapshots, or Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the start/end snapshots. Use the ERROR_NUMBER column in that view
together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that has
valid start and end snapshots.
|
|
ORA-13708
|
ORA-13708: Some snapshots in the range [string, string] were purged before the analysis was complete.
|
|
Cause
|
One or both of the snapshots have been purged from AWR.
|
|
Action
|
Verify that the AWR auto purging is not trying to purge these snapshots and re-run ADDM.
|
|
ORA-13709
|
ORA-13709: Required parameter "string" must be set before execution.
|
|
Cause
|
The parameter needs to be set before running the ADDM
|
|
Action
|
Set the parameter to a valid value and retry.
|
|
ORA-13710
|
ORA-13710: Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
|
|
Cause
|
Invalid interaction between two parameter values.
|
|
Action
|
Set at least one of the values so the value of the first parameter is higher than the value of the second parameter.
|
|
ORA-13711
|
ORA-13711: Some snapshots in the range [string, string] are missing key statistics.
|
|
Cause
|
Some AWR tables encountered errors while creating one or more snapshots in the given range. The data present in one or more of these missing tables is necessary to perform an ADDM
analysis.
|
|
Action
|
Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the given snapshot range. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason
for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that does not include any incomplete snapshots.
|
|
ORA-13712
|
ORA-13712: Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
|
|
Cause
|
ADDM analysis can only be performed on AWR snapshots taken in the current release.
|
|
Action
|
One can still generate AWR and ASH reports using ?/rdbms/admin/awrrpt and ?/rdbms/admin/ashrpt on these snapshots to analyze the data in them.
|
|
ORA-13750
|
ORA-13750: User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege.
|
|
Cause
|
The user attempted an SQL Tuning Set operation that requires a specific privilege.
|
|
Action
|
Adjust the user"s privileges and retry the operation.
|
|
ORA-13751
|
ORA-13751: "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".
|
|
Cause
|
The user attempted to access a SQL Tuning Set that does not exist or the user does have permission to access the SQL Tuning Set
|
|
Action
|
Check the existence of the "SQL Tuning Set" or adjust the user"s privileges and retry the operation.
|
|
ORA-13752
|
ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
|
|
Cause
|
The attempted to create a SQL Tuning Set in another schema without having the right privilege.
|
|
Action
|
Connect as SYS or adjust the user"s privilege and retry the operation.
|
|
ORA-13753
|
ORA-13753: "SQL Tuning Set" "string" already exists for user "string".
|
|
Cause
|
The user attempted to create a "\SQL Tuning"\ Set using a name that already exists for that owner.
|
|
Action
|
Change the name of the SQL Tuning Set and retry the operation.
|
|
ORA-13754
|
ORA-13754: "SQL Tuning Set" "string" does not exist for user "string".
|
|
Cause
|
The user attempted to access a SQL Tuning Set that does not exist.
|
|
Action
|
Check the speelling of the SQL Tuning Set name and retry the operation.
|
|
ORA-13755
|
ORA-13755: invalid "SQL Tuning Set" name
|
|
Cause
|
The user attempted to specify a SQL Tuning Set name that is invalid. A name must not contain wildcards and its length must be less than 30 characters.
|
|
Action
|
Adjust the name and retry the operation.
|
|
ORA-13756
|
ORA-13756: Cannot update attribute "string".
|
|
Cause
|
The user attempted to update an attribute element that cannot be modified. The only string attributes that can be updated are MODULE, ACTION, PARSING_SCHEMA_NAME, PRIORITY, and OTHER.
|
|
Action
|
Adjust the attribute name and retry the operation.
|
|
ORA-13757
|
ORA-13757: "SQL Tuning Set" "string" owned by user "string" is active.
|
|
Cause
|
The user attempted to update an active SQL Tuning Set.
|
|
Action
|
Remove all reference to the SQL Tuning Set and retry the operation.
|
|
ORA-13758
|
ORA-13758: "SQL Tuning Set" "string" owned by user "string" is in use.
|
|
Cause
|
The user attempted to modify a SQL Tuning Set or to add a reference to a SQL Tuning Set which is in use.
|
|
Action
|
Wait until the end of the previous operation and retry.
|
|
ORA-13759
|
ORA-13759: User "string" cannot remove reference "string".
|
|
Cause
|
The user attempted to remove a SQL Tuning Set reference that does not exist. The user might not own the reference.
|
|
Action
|
Check the reference ID and the reference owner and retry the operation.
|
|
ORA-13761
|
ORA-13761: invalid filter
|
|
Cause
|
The user attempted to select data from a data source using an invalid filter. A filter is a WHERE clause on data source content.
|
|
Action
|
Correct the filter and retry the operation.
|
|
ORA-13762
|
ORA-13762: The string ranking measure is invalid.
|
|
Cause
|
The user attempted to select data from a data source using an invlaid ranking measure. A ranking measure must represent a valid numerical expression.
|
|
Action
|
Correct the ranking measure and retry the operation.
|
|
ORA-13763
|
ORA-13763: illegal ranking attribute "string"
|
|
Cause
|
The user attempted to use an attribute element that is not allowed in a ranking meseare.
|
|
Action
|
Check the attribute in the ranking meseare and retry the operation.
|
|
ORA-13764
|
ORA-13764: Value "string" is illegal as a result percentage.
|
|
Cause
|
The user attempted to select data from a SQL Tuning Set using an invalid result percentage. The result percentage must be between 0 and 1.
|
|
Action
|
Correct the result percentage value and retry the operation.
|
|
ORA-13765
|
ORA-13765: Value "string" is illegal for a result limit.
|
|
Cause
|
The user attempted to select data from a SQL Tuning Set using an invalid result limit. A result limit must be a positive interger.
|
|
Action
|
Correct the result limit value and retry the operation.
|
|
ORA-13766
|
ORA-13766: A ranking measure is required.
|
|
Cause
|
The user attempted to select data from a SQL Tuning Set using a percentage argument without specifying a ranking measure.
|
|
Action
|
Add a ranking measure or remove the percentage argument and retry the operation.
|
|
ORA-13767
|
ORA-13767: End snapshot ID must be greater than or equal to begin snapsho ID.
|
|
Cause
|
The user attempted to select data from the workload repository using an invalid snaphot ID range.
|
|
Action
|
Adjust the snapshot ID range and retry the operation.
|
|
ORA-13768
|
ORA-13768: Snapshot ID must be between string and string.
|
|
Cause
|
The user attempted to select data from the workload repository using a snaphot ID which does not exist.
|
|
Action
|
Adjust the snapshot ID and retry the operation.
|
|
ORA-13769
|
ORA-13769: Snapshots string and string do not exist.
|
|
Cause
|
The user attempted to select data from the workload repository using snapshots that do not exist.
|
|
Action
|
Check the snapshot identifiers and retry the operation.
|
|
ORA-13770
|
ORA-13770: Baseline "string" does not exist.
|
|
Cause
|
The user attempted to access a baseline that does not exsit.
|
|
Action
|
Check the speelling of the baseline name and retry the operation.
|
|
ORA-13771
|
ORA-13771: cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
|
|
Cause
|
Unexpected error from DBMS_LOCK.REQUEST.
|
|
Action
|
This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services.
|
|
ORA-13772
|
ORA-13772: unexpected deadlock on "SQL Tuning Set" "string" owned by user "string"
|
|
Cause
|
Unexpected error from DBMS_LOCK.REQUEST
|
|
Action
|
This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services.
|
|
ORA-13773
|
ORA-13773: insufficient privileges to select data from the cursor cache
|
|
Cause
|
The user attempted to perform an operation without having the appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE.
|
|
Action
|
Adjust the user"s privileges and retry the operation.
|
|
ORA-13774
|
ORA-13774: insufficient privileges to select data from the workload repository
|
|
Cause
|
The user attempted to perform an operation without having the appropriate privileges on views DBA_HIST_BASELINE, DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND,
DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT.
|
|
Action
|
Adjust the user"s privileges and retry the operation.
|
|
ORA-13775
|
ORA-13775: inconsistent datatype in input cursor
|
|
Cause
|
The user attempted to load a SQL Tuning Set using an invalid input cursor. All rows in the cursor must match type SQLSET_ROW.
|
|
Action
|
Check the rows type in the cursor and retry the operation.
|
|
ORA-13776
|
ORA-13776: User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
|
|
Cause
|
The user attempted to read a SQL tuning set belonging to someone else without having SELECT privilege on the DBA views
|
|
Action
|
User should be granted the privilege or only access his own STS
|
|
ORA-13777
|
ORA-13777: invalid list of attribute names
|
|
Cause
|
The user specified an attribute element that is not valid. The only attributes that can be selected are NULL, BASIC, TYPICAL, ALL or a comma separated list of the names including
EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN.
|
|
Action
|
Adjust the attribute list and retry the operation.
|
|
ORA-13778
|
ORA-13778: no new name or owner specified for "SQL Tuning Set"
|
|
Cause
|
The user attempted to call remap_stgtab_sqlset without specifying either a new SQL tuning set name or a new SQL tuning set owner
|
|
Action
|
Specify at least one or the other argument as non-NULL
|
|
ORA-13779
|
ORA-13779: invalid load option
|
|
Cause
|
The user attempted to call load_sqlset with a load option that is different than INSERT, UPDATE and MERGE.
|
|
Action
|
Adjust the load option and retry the operation.
|
|
ORA-13780
|
ORA-13780: SQL statement does not exist.
|
|
Cause
|
The user attempted to tune a SQL statement that does not exist.
|
|
Action
|
Verify the sql_id and the plan hash value of the statement and retry the operation.
|
|
ORA-13783
|
ORA-13783: invalid tuning scope
|
|
Cause
|
The user attempted to specify a tuning task scope that is invalid. The possible values are LIMITED or COMPREHENSIVE.
|
|
Action
|
Check the scope value and retry the operation.
|
|
ORA-13784
|
ORA-13784: cannot accept SQL profiles for all statements in the "SQL Tuning Set"
|
|
Cause
|
The user attempted to accept SQL profiles for all statements in a SQL Tuning Set.
|
|
Action
|
Provide the object identifier corresponding to a statement in the SQL Tuning Set and retry the operation.
|
|
ORA-13785
|
ORA-13785: missing target object for tuning task "string"
|
|
Cause
|
The user attempted to perform an operation on a task without specifying a target object or by using an invalid object identifier.
|
|
Action
|
Check the identifier of the object and retry the operation.
|
|
ORA-13786
|
ORA-13786: missing SQL text of statement object "string" for tuning task "string"
|
|
Cause
|
The user attempted to accept SQL profile for an object that has not a SQL text associated to it.
|
|
Action
|
Check the identifier of the object and retry the operation.
|
|
ORA-13787
|
ORA-13787: missing SQL profile for statement object "string" for tuning task "string"
|
|
Cause
|
The user attempted to accept a SQL profile for an object that has not a SQL profile associated to it.
|
|
Action
|
Check the identifier of the object and retry the operation.
|
|
ORA-13788
|
ORA-13788: invalid recommendation type
|
|
Cause
|
The user passed an invalid recommendation type in the rec_type argument to script_tuning_task. Possible values are ALL or any subset of a comma-separated list of PROFILES, STATISTICS
and INDEXES.
|
|
Action
|
Check the rec_type arg and retry the operation.
|
|
ORA-13789
|
ORA-13789: invalid process action
|
|
Cause
|
The user passed an invalid action to process a SQL statement. Possible value is any subset of a comma-seperated list of EXECUTE and EXPLAIN_PLAN.
|
|
Action
|
Check the action argument and retry the operation.
|
|
ORA-13790
|
ORA-13790: invalid value for time limit
|
|
Cause
|
The user passed an invalid value for the time limit argument.
|
|
Action
|
Check the argument specified value and retry the operation.
|
|
ORA-13791
|
ORA-13791: cannot resume a tuning task created to tune a single statement
|
|
Cause
|
The user attempted to resume a tuning task that was created to tune a single SQL statement. A task can be resumed only if it is used to tune a SQL Tuning Set.
|
|
Action
|
No action required.
|
|
ORA-13797
|
ORA-13797: invalid SQL Id specified, string
|
|
Cause
|
Invalid SQL Id specified for conversion.
|
|
Action
|
Specify valid SQL Id.
|
|
ORA-13798
|
ORA-13798: Parameter string cannot be NULL.
|
|
Cause
|
A call to GET_THRESHOLD procedure was made without a required parameter.
|
|
Action
|
Specify a valid value for this parameter.
|
|
ORA-13799
|
ORA-13799: threshold not found
|
|
Cause
|
No threshold was found with the specified threshold key.
|
|
Action
|
No action required.
|
|
ORA-13800
|
ORA-13800: concurrent DDL failure on SQL repository objects
|
|
Cause
|
A SQL repository object was the target of two concurrent DDL operations.
|
|
Action
|
Check the current state of the object and retry the operation that failed.
|
|
ORA-13801
|
ORA-13801: invalid value for SQLTUNE_CATEGORY parameter
|
|
Cause
|
An invalid Oracle identifier was used as the value of the parameter.
|
|
Action
|
Specify the parameter conforming to the rules for Oracle identifiers.
|
|
ORA-13802
|
ORA-13802: failed to purge SQL Tuning Base entry from sql$
|
|
Cause
|
An error occured while try to delete a SQL Tuning Base object.
|
|
Action
|
Look at the underlying error(s) on the error stack.
|
|
ORA-13825
|
ORA-13825: missing SQL statement text for create SQL profile
|
|
Cause
|
No SQL text was provided to the create SQL profile operation.
|
|
Action
|
Retry with properly specified SQL text.
|
|
ORA-13826
|
ORA-13826: empty SQL profile not allowed for create or update SQL profile
|
|
Cause
|
No attributes were specified to the create SQL profile operation.
|
|
Action
|
Retry with at least one hint specified.
|
|
ORA-13827
|
ORA-13827: null or zero length attribute specified in SQL profile collection
|
|
Cause
|
One of the attributes within the SQL profile was not properly specified.
|
|
Action
|
Retry with a fully specified SQL profile.
|
|
ORA-13828
|
ORA-13828: generated SQL profile name string already exists
|
|
Cause
|
A SQL profile already exists with the name generated by the system.
|
|
Action
|
Retry the operation as the generated name is time sensitive.
|
|
ORA-13829
|
ORA-13829: SQL profile named string already exists
|
|
Cause
|
A SQL profile already exists with the name specified.
|
|
Action
|
Specify a different name or drop the existing SQL profile.
|
|
ORA-13830
|
ORA-13830: SQL profile with category string already exists for this SQL statement
|
|
Cause
|
A SQL profile already exists for the given SQL statement and category.
|
|
Action
|
Drop or update the existing SQL profile.
|
|
ORA-13831
|
ORA-13831: SQL profile name specified is invalid
|
|
Cause
|
An invalid SQL profile name was specified.
|
|
Action
|
Look for the underlying error on the error message stack.
|
|
ORA-13832
|
ORA-13832: category name specified is invalid
|
|
Cause
|
An invalid category name swas pecified.
|
|
Action
|
Look for the underlying error on the error message stack.
|
|
ORA-13833
|
ORA-13833: SQL profile named string doesn"t exist
|
|
Cause
|
A SQL profile name was specified that doesn"t exist.
|
|
Action
|
Verify the name of the SQL profile.
|
|
ORA-13834
|
ORA-13834: name of SQL profile to be cloned must be provided
|
|
Cause
|
A SQL profile name was not provided as the from target of a clone SQL profile operation.
|
|
Action
|
Provide the name of the SQL profile being cloned.
|
|
ORA-13835
|
ORA-13835: invalid attribute name specified
|
|
Cause
|
An invalid attribute name was specified for an alter SQL profile operation.
|
|
Action
|
Verify the name of the attribute.
|
|
ORA-13836
|
ORA-13836: invalid attribute value specified
|
|
Cause
|
An invalid attribute value was specified for an alter SQL profile operation.
|
|
Action
|
Verify the attribute value.
|
|
ORA-13837
|
ORA-13837: invalid HASH_VALUE
|
|
Cause
|
An invalid HASH_VALUE was passed to a create SQL profile operation
|
|
Action
|
Verify the HASH_VALUE.
|
|
ORA-13838
|
ORA-13838: invalid ADDRESS value
|
|
Cause
|
An invalid ADDRESS value was passed to a create SQL profile operation.
|
|
Action
|
Verify the ADDRESS value.
|
|
ORA-13839
|
ORA-13839: V$SQL row doesn"t exist with given HASH_VALUE and ADDRESS.
|
|
Cause
|
A HASH_VALUE and ADDRESS combination passed to the create SQL profile operation doesn"t coorespond to an existing V$SQL entry.
|
|
Action
|
Verify the HASH_VALUE and ADDRESS in V$SQL.
|
|
ORA-13840
|
ORA-13840: Concurrent DDL Error in create SQL profile operation.
|
|
Cause
|
A concurrent DDL operation was performed during a create or replace sql profile operation.
|
|
Action
|
Try operation again
|
|
ORA-13841
|
ORA-13841: SQL profile named string already exists for a different signature/category pair
|
|
Cause
|
A SQL profile already exists with the name specified under a different signature/category pair so it cannot be replaced, even with FORCE specified.
|
|
Action
|
Specify a different name or drop the existing SQL profile.
|
|
ORA-13842
|
ORA-13842: no SELECT privilege on DBA_SQL_PROFILES
|
|
Cause
|
A user has tried to perform an operation that requires SELECT privileges on the DBA_SQL_PROFILES view.
|
|
Action
|
Either perform the operation as another user or get the privilege
|
|
ORA-13843
|
ORA-13843: no SQL profile with name like "string" exists for category like "string"
|
|
Cause
|
A user tried to perform an operation by specifying a profile name/ category filter that did not target any profiles
|
|
Action
|
Try a different filter after checking the profile name/category
|
|
ORA-13844
|
ORA-13844: no new SQL profile name or category specified.
|
|
Cause
|
A user called remap_stgtab_sqlprof without specifying new values for the sql profile name or category. At least one is required.
|
|
Action
|
Specify either a new profile name, or a new category, or both
|
|
ORA-13850
|
ORA-13850: Tracing for client identifier string is not enabled
|
|
Cause
|
Attempt to disable a client identifier tracing which was never enabled
|
|
Action
|
Supply correct client identifier
|
|
ORA-13851
|
ORA-13851: Tracing for client identifier string is already enabled
|
|
Cause
|
Attempt to enable a client identifier tracing which has been already enabled
|
|
Action
|
Supply correct client identifier, or disable and re-enable tracing with different bind/wait options
|
|
ORA-13852
|
ORA-13852: Tracing for service(module/action) string is not enabled
|
|
Cause
|
Attempt to disable a service-level tracing which was never enabled
|
|
Action
|
Supply correct service(module/action) name
|
|
ORA-13853
|
ORA-13853: Tracing for service (module/action) string is already enabled
|
|
Cause
|
Attempt to enable a service-level tracing which has been already enabled
|
|
Action
|
Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options
|
|
ORA-13854
|
ORA-13854: Tracing for service(module/action) string on instance string is not enabled
|
|
Cause
|
Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance
|
|
Action
|
Supply correct service(module/action) name
|
|
ORA-13855
|
ORA-13855: Tracing for service (module/action) string on instance string is already enabled
|
|
Cause
|
Attempt to enable a service-level tracing which has been already enabled on a specific instance
|
|
Action
|
Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options
|
|
ORA-13856
|
ORA-13856: Service name must be specified
|
|
Cause
|
Omitting service name while enabling/disabling tracing or aggregation
|
|
Action
|
Supply the service name
|
|
ORA-13857
|
ORA-13857: Invalid module name
|
|
Cause
|
Module name is too long (exceeding 48 characters)
|
|
Action
|
Supply correct name
|
|
ORA-13858
|
ORA-13858: Invalid action name
|
|
Cause
|
Action name is too long (exceeding 32 characters)
|
|
Action
|
Supply correct name
|
|
ORA-13859
|
ORA-13859: Action cannot be specified without the module specification
|
|
Cause
|
Action name is specified, but the module name is not
|
|
Action
|
Supply the module name
|
|
ORA-13860
|
ORA-13860: Invalid service name
|
|
Cause
|
Service name is too long (exceeding 64 characters)
|
|
Action
|
Supply correct name
|
|
ORA-13861
|
ORA-13861: Statistics aggregation for client identifier string is already enabled
|
|
Cause
|
Attempt to enable a client identifier aggregation which has been already enabled
|
|
Action
|
Supply correct client identifier
|
|
ORA-13862
|
ORA-13862: Statistics aggregation for client identifier string is not enabled
|
|
Cause
|
Attempt to disable a client identifier statistics aggregation which was never enabled
|
|
Action
|
Supply correct client identifier
|
|
ORA-13863
|
ORA-13863: Statistics aggregation for service(module/action) string is not enabled
|
|
Cause
|
Attempt to disable a service-level statistics aggregation which was never enabled
|
|
Action
|
Supply correct service(module/action) name
|
|
ORA-13864
|
ORA-13864: Statistics aggregation for service (module/action) string is already enabled
|
|
Cause
|
Attempt to enable a service-level statistics aggregation which has been already enabled
|
|
Action
|
Supply correct service(module/action)
|
|
ORA-13865
|
ORA-13865: Module name must be specified
|
|
Cause
|
Attempt to enable/disable a service-level statistics aggregation without a module specification
|
|
Action
|
Supply module name
|
|
ORA-13866
|
ORA-13866: Client identifier must be specified
|
|
Cause
|
Omitting client identifier while enabling/disabling tracing or aggregation
|
|
Action
|
Supply the client identifier
|
|
ORA-13867
|
ORA-13867: Database-wide SQL tracing is already enabled
|
|
Cause
|
Attempt to enable a database-level tracing which has been already enabled
|
|
Action
|
Disable and re-enable tracing with different bind/wait options
|
|
ORA-13868
|
ORA-13868: Instance-wide SQL tracing on instance string is not enabled
|
|
Cause
|
Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance
|
|
Action
|
No action required
|
|
ORA-13869
|
ORA-13869: Instance-wide SQL tracing on instance string is already enabled
|
|
Cause
|
Attempt to enable an instance-level tracing which has been already enabled on a specific instance
|
|
Action
|
Disable and re-enable tracing with different bind/wait options
|
|
ORA-13870
|
ORA-13870: Database-wide SQL tracing is not enabled
|
|
Cause
|
Attempt to disable a database-level tracing which was never enabled
|
|
Action
|
No action required
|
|
ORA-13871
|
ORA-13871: Invalid instance name
|
|
Cause
|
Instance name is too long (exceeding 16 characters)
|
|
Action
|
Supply correct name
|