Oracle 12c R2 Error Codes and Solution Suggestions from ORA-13700 to ORA-13900
- ORA-13700: Reserved for ADDM tracing.
- 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.
Cause: The start snapshot id and end snapshot id were identical.
Action: Provide different start and end snapshot ids.
- 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.
Cause: The parameter was not set before executing the ADDM.
Action: Set the parameter to a valid value and retry.
- 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.
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: 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: 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.
Cause: The parameter needs to be set before running the ADDM
Action: Set the parameter to a valid value and retry.
- 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.
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: 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-13713: Finding name “string” does not exist. Look in DBA_ADVISOR_FINDING_NAMES for all valid values
Cause: Attempt to refer to an advisor’s finding name that does not exist.
Action: Specify a valid value. The list of all valid values is in DBA_ADVISOR_FINDING_NAMES
Cause: The specified value of SQL_ID was not properly formatted.
Action: Specify a valid value consisting of a 13 character string with characters from ‘0’ to ‘9’ and from ‘a’ to ‘z’.
Cause: The specified value for a system parameter was not recognized by ADDM.
Action: Specify a value that appears in the NAME column of V$PARAMETER.
Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Diagnostic Package was disabled.
Action: Modify the parameter value if the Diagnostic Package License was purchased.
Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Tuning Package was disabled.
Action: Modify the parameter value if the Tuning Package License was purchased.
- ORA-13718: Tuning Package License or Real Application Testing Option is needed for using this feature.
Cause: The specified package license and option were not installed.
Action: Consider purchasing and installing either the missing package licence or option. If the tuning package license was purchased, then check the value of system parameter CONTROL_MANAGEMENT_PACK_ACCESS.
Cause: ADDM analysis was attempted on imported Automatic Workload Repository (AWR) snapshots with incompatible character set.
Action: Perform ADDM analysis using a database with the same version and character set as the original database.
Cause: Active Session History (ASH) dimension name provided was longer than the limit of 30 characters.
Action: Correct the dimension name and retry the operation.
Cause: Active Session History (ASH) dimension name provided was invalid.
Action: Correct the dimension name and retry the operation.
Cause: An invalid value was passed an input for a procedure argument.
Action: Pass a valid value to the procedure.
Cause: The string input value was too long for the specific procedure argument.
Action: Pass a valid value to the procedure.
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: “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.
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.
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.
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.
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.
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.
Cause: The user attempted to update an active SQL Tuning Set.
Action: Remove all reference to the SQL Tuning Set and retry the operation.
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.
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.
Cause: An attempt was made to execute an operation that is not supported from a physical standby database.
Action: Execute this operation from a primary database.
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.
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.
Cause: The user attempted to use an attribute element that is not allowed in a ranking measure.
Action: Check the attribute in the ranking measure and retry the operation.
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.
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.
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.
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.
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.
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.
Cause: The user attempted to access a baseline that does not exsit.
Action: Check the speelling of the baseline name and retry the operation.
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.
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.
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.
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.
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: 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
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.
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
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.
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.
Cause: The user attempted to test-execute or generate explain plans for a SQL workload using the automatic SQL tuning task.
Action: Verify the name of the tuning task and retry the operation.
- ORA-13782: The argument string to this API is only allowed for tasks created in a physical standby database.
Cause: “An attempt was made to pass an argument that is valid only for a physical standby database. “
Action: Remove the invalid argument and re-run the API.
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.
Cause: An attempt was made to accept SQL profiles for all statements in the input workload.
Action: Provide the object identifier corresponding to a statement in the workload and retry the operation.
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.
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.
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.
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.
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.
Cause: The user passed an invalid value for the time limit argument.
Action: Check the argument specified value and retry the operation.
Cause: An attempt was made to resume a task that was created for a single SQL statement. A task can be resumed only if it is used for a SQL Tuning Set.
Action: No action required.
Cause: An attempt was made to execute an operation from a physical standby database that requires a valid database link to access a primary database.
Action: Provide a valid database link to access a primary database.
Cause: An invalid metric to compare SQL performance was specified.
Action: Use execution statistics to compare the result of two executions and optimizer_cost to analyze performance of two explain plan actions.
Cause: An attempt was made to analyze the performance of a SQL workload using two executions that were generated using two different actions.
Action: check the name and type of task executions to analyze and retry the operation.
Cause: An insufficient number of valid task executions to analyze the performance of a SQL workload were specified.
Action: run the task to generate two executions of the same type and retry the operation.
Cause: An invalid problem type was specified to the SQL diagnosis advisor. Problem type should be one of the PROBLEM_TYPE_* defined in ‘admin/dbmsdiag.sql’.
Action: Specify valid problem type.
Cause: Invalid SQL Id specified for conversion.
Action: Specify valid SQL Id.
Cause: A call to GET_THRESHOLD procedure was made without a required parameter.
Action: Specify a valid value for this parameter.
Cause: No threshold was found with the specified threshold key.
Action: No action required.
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.
Cause: An invalid Oracle identifier was used as the value of the parameter.
Action: Specify the parameter conforming to the rules for Oracle identifiers.
Cause: An error occured while try to delete a SQL Tuning Base object.
Action: Look at the underlying error(s) on the error stack.
Cause: The wrong value was passed in for the parameter.
Action: Check the value and input the correct value.
Cause: An internal error was encountered.
Action: Check the alert log and report to Oracle Support Services.
Cause: An attempt was made to end a database operation that did not exist.
Action: Check if the database operation is being monitored.
Cause: The database operation name or execution ID did not match.
Action: Call the interface with the right database operation name and execution ID.
Cause: The database operation name provided was invalid.
Action: Supply a database operation name not exceeding 30 characters.
Cause: The database operation execution ID provided was invalid.
Action: Supply a database operation execution ID greater than 0.
Cause: No SQL text was provided to the create SQL profile or patch operation.
Action: Retry with properly specified SQL text.
Cause: No attributes were specified to the create SQL profile or patch operation.
Action: Retry with at least one hint specified.
Cause: One of the attributes within the SQL profile or patch was not properly specified.
Action: Retry with a fully specified SQL profile or patch.
Cause: A SQL profile or patch already exists with the name generated by the system.
Action: Retry the operation as the generated name is time sensitive.
Cause: A SQL profile or patch already exists with the name specified.
Action: Specify a different name or drop the existing SQL profile or patch.
Cause: A SQL profile or patch already exists for the given SQL statement and category.
Action: Drop or update the existing SQL profile or patch.
Cause: An invalid SQL profile or patch name was specified.
Action: Supply a name not exceeding 30 characters or look for the underlying error on the error message stack.
Cause: An invalid category name was specified.
Action: Supply a category name not exceeding 30 characters or look for the underlying error on the error message stack.
Cause: A SQL profile or patch name was specified that doesn’t exist.
Action: Verify the name of the SQL profile or patch.
Cause: A SQL profile or patch name was not provided as the from target of a clone SQL profile or patch operation.
Action: Provide the name of the SQL profile or patch being cloned.
Cause: An invalid attribute name was specified for an alter SQL profile or patch operation.
Action: Verify the name of the attribute.
Cause: An invalid attribute value was specified for an alter SQL profile or patch operation.
Action: Verify the attribute value.
Cause: An invalid HASH_VALUE was passed to a create SQL profile operation
Action: Verify the HASH_VALUE.
Cause: An invalid ADDRESS value was passed to a create SQL profile operation.
Action: Verify the ADDRESS value.
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.
Cause: A concurrent DDL operation was performed during a create or replace sql profile operation.
Action: Try operation again
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.
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
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
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
Cause: The supplied XML specification for the SQL profile did not adhere to the proper schema.
Action: Check the syntax and try again.
Cause: There are either multiple plans exist for the given value or the plan is not reproducible.
Action: Call Oracle Support.
Cause: The give plan does not exist.
Action: Check the available plans.
- ORA-13848: Database link provided for the task operation was different than the one used with task creation API.
Cause: All SQL tuning advisor APIs executed from a physical standby database are required to use the same database link.
Action: Retry the operation by providing the database link used for task creation.
Cause: Attempt to disable a client identifier tracing which was never enabled
Action: Supply correct client identifier
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
Cause: Attempt to disable a service-level tracing which was never enabled
Action: Supply correct service(module/action) name
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
Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance
Action: Supply correct service(module/action) name
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
Cause: Omitting service name while enabling/disabling tracing or aggregation
Action: Supply the service name
Cause: Module name is too long (exceeding 48 characters)
Action: Supply correct name
Cause: Action name is too long (exceeding 32 characters)
Action: Supply correct name
Cause: Action name is specified, but the module name is not
Action: Supply the module name
Cause: Service name is too long (exceeding 64 characters)
Action: Supply correct name
Cause: Attempt to enable a client identifier aggregation which has been already enabled
Action: Supply correct client identifier
Cause: Attempt to disable a client identifier statistics aggregation which was never enabled
Action: Supply correct client identifier
Cause: Attempt to disable a service-level statistics aggregation which was never enabled
Action: Supply correct service(module/action) name
Cause: Attempt to enable a service-level statistics aggregation which has been already enabled
Action: Supply correct service(module/action)
Cause: Attempt to enable/disable a service-level statistics aggregation without a module specification
Action: Supply module name
Cause: Omitting client identifier while enabling/disabling tracing or aggregation
Action: Supply the client identifier
Cause: Attempt to enable a database-level tracing which has been already enabled
Action: Disable and re-enable tracing with different bind/wait options
Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance
Action: No action required
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
Cause: Attempt to disable a database-level tracing which was never enabled
Action: No action required
Cause: Instance name is too long (exceeding 16 characters)
Action: Supply correct name
Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid.
Action: Specify a valid value for this parameter.