Oracle 11g Error Codes and Solution Suggestions from ORA-13500 to ORA-13700

Posted on by Fatih Acar

Oracle 11g Error Codes and Solution Suggestions from ORA-13500 to ORA-13700

ORA-13500: SYSAUX DATAFILE clause specified more than once
Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause.
Action: Specify at most one SYSAUX DATAFILE clause.
ORA-13501: Cannot drop SYSAUX tablespace
Cause: Tried to drop SYSAUX tablespace
Action: None
ORA-13502: Cannot rename SYSAUX tablespace
Cause: An attempt to rename the SYSAUX tablespace failed.
Action: No action required.
ORA-13503: Creating SYSAUX tablespace with invalid attributes
Cause: An attempt to create the SYSAUX tablespace with invalid attributes.
Action: Create SYSAUX tablespace with ONLINE, PERMANENT, EXTENT MANAGEMENT LOCAL, SEGMENT SPACE MANAGEMENT AUTO attributes.
ORA-13504: No SYSAUX datafile clause specified
Cause: If Create Database has the datafile clause, then SYSAUX datafile clause has to be specified, unless using OMF.
Action: Specify the SYSAUX datafile clause.
ORA-13505: SYSAUX tablespace can not be made read only
Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX tablespace must remain read write for database operation.
Action: Leave SYSAUX tablespace read write.
ORA-13506: operation failed due to invalid snapshot range (string, string)
Cause: An attempt was made to perform operation with an invalid Start/End Snapshot Pair.
Action: Choose a valid Start/End Snapshot Pair.
ORA-13509: error encountered during updates to a AWR table
Cause: An update error occurred during OCI operation due to an underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13510: invalid RETENTION string, must be in the range (string, string)
Cause: The user has specified a RETENTION setting that is not in the supported range of (MIN, MAX).
Action: Choose a valid RETENTION setting and retry the operation.
ORA-13511: invalid INTERVAL string, must be in the range (string, string)
Cause: The user has specified a INTERVAL setting that is not in the supported range of (MIN, MAX).
Action: Choose a valid INTERVAL setting and retry the operation.
ORA-13514: Metric Capture too close to last capture, group string
Cause: The metric capture cannot be executed because it is too close to the last capture (within 1 centi-second).
Action: add some delay and reissue command to retry.
ORA-13515: Error encountered during Database Usage Statistics capture
Cause: Error occurred during OCI operation due to underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13516: AWR Operation failed: string
Cause: The operation failed because AWR is not available. The possible causes are: AWR schema not yet created; AWR not enabled; AWR schema not initialized; or database not open or is running in READONLY or STANDBY mode.
Action: check the above conditions and retry the operation.

ORA-13517: Baseline (id = string) does not exist
Cause: The operation failed because the specified baseline ID does not exist in the Workload Repository.
Action: check the baseline id and retry the operation.
ORA-13518: Invalid database id (string)
Cause: The operation failed because the specified database ID does not exist in the Workload Repository.
Action: check the database id and retry the operation.
ORA-13519: Database id (string) exists in the workload repository
Cause: The operation failed because the specified database ID already exists in the Workload Repository.
Action: check the database id and retry the operation.
ORA-13520: Database id (string) not registered, Status = string
Cause: The operation failed because the specified database ID was not registered in the Workload Repository properly.
Action: check the status of database id and retry the operation.
ORA-13521: Unregister operation on local Database id (string) not allowed
Cause: The operation failed because the local database ID cannot be unregistered from the Workload Repository.
Action: check the database id and retry the operation.
ORA-13523: unable to allocate required space for return type
Cause: Out of memory to allocate the space for the return variable for an external procedure.
Action: Try operation again.
ORA-13524: error encountered while retrieving baseline information
Cause: A read error occurred during the OCI operation to retrieve the baseline information
Action: Check associated error. Correct problem and retry the operation.
ORA-13525: error with computing space usage for sysaux occupant
Cause: Error occurred during OCI operation due to underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13526: baseline (string) does not exist
Cause: The operation failed because the specified baseline name does not exist in the Workload Repository.
Action: check the baseline name and retry the operation.
ORA-13527: invalid baseline name
Cause: The operation failed because the specified baseline name is invalid.
Action: check the baseline name and retry the operation.
ORA-13528: name (string) is already used by an existing baseline
Cause: The operation failed because the specified baseline name already exists in the Workload Repository.
Action: check the baseline name and retry the operation.
ORA-13529: Error occurred when flushing AWR table group
Cause: An error occurred during the flushing of a table group. Because of the error in the group, we are unable to flush this table.
Action: Check the error associated with the table group.
ORA-13530: invalid TOPNSQL string, must be in the range (string, string)
Cause: The user has specified a TOPNSQL setting that is not in the supported range of (MIN, MAX).
Action: Choose a valid TOPNSQL setting and retry the operation.
ORA-13531: SQL Text was purged from AWR before the operation completed
Cause: A SQL was purged from AWR before the operation completed.
Action: Retry the operation.
ORA-13532: SQL ID [string] already exists
Cause: The operation failed because the specified SQL ID already existed in the repository.
Action: Check the SQL ID and retry the operation.
ORA-13533: invalid SQL ID
Cause: The operation failed because the specified SQL ID was invalid.
Action: Check the SQL ID and retry the operation.
ORA-13534: Current SQL count(string) reached maximum allowed (string)
Cause: The operation failed because the maximum allowed colored SQL was exceeded.
Action: Check the count for colored SQL.
ORA-13535: name (string) is already used by an existing baseline template
Cause: The operation failed because the specified baseline template name already existed in the Workload Repository.
Action: Check the baseline template name and retry the operation.
ORA-13536: baseline template (string) does not exist
Cause: The operation failed because the specified baseline template name did not exist in the Workload Repository.
Action: Check the baseline template name and retry the operation.
ORA-13537: invalid input for create baseline template (string, string)
Cause: Invalid input was specified for the create baseline template routine.
Action: Check the argument displayed in the error message text.
ORA-13538: invalid value for baseline expiration (string)
Cause: An invalid value was specified for the expiration of a baseline. The expiration is specified in number of days, and the expiration must be at least one day.
Action: Check the value for expiration.
ORA-13539: invalid input for modify baseline window size (string, string)
Cause: Invalid input was specified for the modify baseline window size routine.
Action: Check the argument displayed in the error message text.
ORA-13540: operation not allowed on system moving window baseline (string)
Cause: The requested operation was not allowed on the system moving window baseline.
Action: Retry the operation with another baseline name.
ORA-13541: system moving window baseline size (string) greater than retention (string)
Cause: The system moving window baseline size must be less than the retention setting. The specified window size or retention violate this.
Action: Check the moving window baseline size or retention.
ORA-13542: baseline ID (string) does not exist
Cause: The operation failed because the specified baseline ID did not exist in the Workload Repository.
Action: Check the baseline ID and retry the operation.
ORA-13543: error encountered while retrieving baseline template information
Cause: A read error occurred during the OCI operation to retrieve the baseline template information.
Action: Check associated error. Correct problem and retry the operation.
ORA-13544: error encountered while automatically generating a baseline
Cause: An error occurred while automatically generating a baseline based on the template information.
Action: Look in the trace file for more error information.
ORA-13545: invalid baseline template name
Cause: The operation failed because the specified baseline template name was an invalid identifier.
Action: Check the baseline template name and retry the operation.
ORA-13546: Error encountered during maintenance of Adaptive Thresholds
Cause: Error occurred during OCI operation due to underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13547: Unable to drop baseline since it is in use by string
Cause: The system is not able to drop the baseline since the baseline is in use by a functionality that depends on its existence.
Action: Note the name of the functionality using the baseline, and check if the functionality still needs the baseline.
ORA-13548: Unable to find valid snapshot IDs for the inputted baseline time range
Cause: The system is not able to find valid snapshot IDs for the inputted time range while attempting to create a baseline.
Action: Check that the inputted time range has at least two valid snapshots. The dba_hist_snapshot displays the snapshot id and time information.
ORA-13549: invalid input for create baseline with time range (string)
Cause: Invalid time input was specified for the create baseline routine.
Action: Check the argument displayed in the error message text.
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: 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: 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: 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: 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: 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: 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: 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: The specified name string is invalid.
Cause: An attempt was made to specify a name for a task, object, execution or directive instance, which contained invalid characters or an invalid wildcard specifier.
Action: Adjust the name and retry the operation.
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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: string 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: 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: 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: 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: 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: 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: The most recent execution of task string contains no 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: The user cancelled the current operation.
Cause: The user signaled a cancel during a task or object operation.
Action: None
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: 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: 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: 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: 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: The user interrupted the current operation.
Cause: The user signaled an interrupt during a task or object operation.
Action: None
ORA-13639: The current operation was interrupted because it timed out.
Cause: The task or object operation timed out.
Action: None
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: 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: 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: 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: The user “string” is invalid.
Cause: Invalid user name specified to advisor framework
Action: User should specify a correct, case-sensitive, name
ORA-13645: The specified execution string does not exist for this task.
Cause: You attempted to reference an advisor task execution using a name that did not exist.
Action: Adjust the name and retry the operation.
ORA-13646: The specified execution string already exists
Cause: You attempted to perform a new execution using a name that already exists for the specified task. Execution names must be unique within the same task.
Action: Adjust the name and retry the operation.
ORA-13647: Setting of parameter string is disallowed during task execution.
Cause: You attempted to set the value of a parameter while the task was being executed. This parameter cannot be changed until the task finishes its execution.
Action: Verify the status of the task and retry the operation.
ORA-13648: The specified execution type does not exist for this advisor.
Cause: You attempted to use an advisor task execution type using a name that did not exist.
Action: Adjust the name and retry the operation.
ORA-13649: The type of execution is not specified for this advisor or task.
Cause: You attempted to execute a task for a multi-execution task advisor without specifying the type of execution to perform.
Action: Set the execution type and retry the operation.
ORA-13650: The specified object does not exist for this execution.
Cause: You attempted to associate an object to a task execution that id not contain the object.
Action: Adjust the execution name and object ID, and then retry the operation.
ORA-13651: The specified list of execution parameters is invalid.
Cause: The list did not include pairs of (parameter_name, parameter_value) where every parameter is a valide task parameter. Duplicates are not allowed.
Action: Adjust the content of the list, and then retry the operation.
ORA-13652: Cannot set execution parameters for this advisor
Cause: You attempted to set execution parameters for an advisor that did not support multiple executions of its tasks.
Action: Adjust the property of the advisor, and then retry the operation.
ORA-13653: The directive with definition id string was not found.
Cause: An invalid directive identifier was specified to advisor framework.
Action: User should specify a correct identifier number and retry the operation.
ORA-13654: The directive with instance id of string was not found.
Cause: An invalid instance identifier was specified to advisor framework.
Action: User should specify a correct instance identifier number and retry the operation.
ORA-13655: The directive document contains a syntax error and cannot be loaded.
Cause: An attempt was made to load an XML-based directive that does not conform to the documented DTD.
Action: Reformat the directive according the documented DTD.
ORA-13656: The parameter was not found in directive string.
Cause: The specified parameter name could not be located within the directive XML document.
Action: Verify the existence of the parameter in the specified directive.
ORA-13657: The filter Xpath specification has invalid syntax.
Cause: The specified filter could not be compiled within the directive XML document.
Action: Verify the syntax of the filter and retry the operation.
ORA-13658: The specified directive already has an instance
Cause: An attempt was made to create multiple instances of a directive when not permitted
Action: Verify the parent directive identifier and the instance name.
ORA-13659: A directive with domain “string” and name “string” already exists for advisor string.
Cause: The specified directive is not unique among the directives.
Action: Choose a directive name and domain that is distinct for the associated advisor.
ORA-13660: A directive instance with the name “string” already exists.
Cause: The specified directive instance is not unique among instances for this directive.
Action: Choose an instance name that is distinct for the associated directive.
ORA-13661: A directive instance with the name “string” was not found.
Cause: An attempt was made to update or delete a non-existent directive instance.
Action: Verify the parent directive identifier and the instance name.
ORA-13662: The specified value provided for parameter string is not valid for this task.
Cause: The supplied parameter value was not valid for the current task configuration.
Action: Retry by supplying valid value. Check the current task configuration.
ORA-13663: The task string contains no results for execution string.
Cause: An attempt was made to create a report or script from an execution that had not been successfully completed.
Action: Run a new execution and then retry the operation.
ORA-13664: A task-managed “SQL Tuning Set” already exists for task “string“.
Cause: An attempt was made to create a task-managed SQL Tuning Set for a task that already had one.
Action: Create a new task to use a different SQL Tuning Set.
ORA-13665: Execution names are not correctly ordered.
Cause: The supplied execution names were not properly ordered by execution start date.
Action: Retry by supplying a valid order.
ORA-13666: Task ID string does not exist.
Cause: The supplied task ID was invalid.
Action: Check the task ID and try again.
ORA-13667: Execution ID string does not exist.
Cause: The supplied execution ID was invalid.
Action: Check the execution ID and try again.
ORA-13668: The current operation was aborted because it was blocking another session.
Cause: The task or object operation interrupted itself when it detected that it was blocking some other session.
Action: Retry the operation when the conflicting operations are not running.
ORA-13669: Execution provided has type “string“, expected “string“.
Cause: An execution was provided whose type did not match the one expected by the API.
Action: Check the execution name, and try again.
ORA-13670: No execution of type string exists for task provided.
Cause: No execution of the required type existed for the given advisor task.
Action: Check the task, and try again.
ORA-13699: Advisor feature is not currently implemented.
Cause: An attempt was made to execute an unsupported advisor operation.
Action: Verify the availability of the operation.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.