ORA-13616: The current user string has not been granted the ADVISOR privilege.

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-13615: The task or object string is greater than the maximum allowable length of 30 characters.

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-13614: The template string is not compatible with the current advisor.

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-13613: The requested operation is not supported for this advisor object.

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-13612: The recommendation action string,string is not valid for task string.

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-13611: The command string is not a valid advisor command.

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-13610: The directive string does not exist for task string.

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-13609: The specified task string must be executing to be cancelled or interrupted.

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-13608: The task or object name string is invalid.

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-13607: The specified task or object string already exists

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-13606: the specified task parameter element string is out of range for parameter string.

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-13605: The specified task or object string does not exist for the current user.

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-13604: The specified parameter string cannot be fetched as a SQL table.

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-13603: The specified parameter string cannot be fetched as a numeric value for task or object string.

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-13602: The specified parameter string is not valid for task or object string.

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-13601: The specified Advisor string does not exist.

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-13600: error encountered in Advisor string

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-13530: invalid TOPNSQL string, must be in the range (string, string)

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-13529: Error occurred when flushing AWR table group

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-13528: name (string) is already used by an existing baseline

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-13527: invalid baseline name

ORA-13527: invalid baseline name

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-13526: baseline (string) does not exist

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-13525: error with computing space usage for sysaux occupant

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-13524: error encountered while retrieving baseline information

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-13523: unable to allocate required space for return type

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-13521: Unregister operation on local Database id (string) not allowed

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-13520: Database id (string) not registered, Status = string

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-13519: Database id (string) exists in the workload repository

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-13518: Invalid database id (string)

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-13517: Baseline (id = string) does not exist

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-13516: AWR Operation failed: string

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-13515: Error encountered during Database Usage Statistics capture

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-13514: Metric Capture too close to last capture, group string

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-13511: invalid INTERVAL string, must be in the range (string, string)

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-13510: invalid RETENTION string, must be in the range (string, string)

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-13509: error encountered during updates to a AWR table

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-13506: operation failed due to invalid snapshot range (string, string)

ORA-13506: operation failed due to invalid snapshot range (string, string)

Cause: An attempt was made to perform operation with an invalid Start or End Snapshot Pair.

Action: Choose a valid Start or End Snapshot Pair.

ORA-13505: SYSAUX tablespace can not be made read only

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-13504: No SYSAUX datafile clause specified

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-13503: Creating SYSAUX tablespace with invalid attributes

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-13502: Cannot rename SYSAUX tablespace

ORA-13502: Cannot rename SYSAUX tablespace

Cause: An attempt to rename the SYSAUX tablespace failed.

Action: No action required.

ORA-13501: Cannot drop SYSAUX tablespace

ORA-13501: Cannot drop SYSAUX tablespace

Cause: Tried to drop SYSAUX tablespace

Action: None

ORA-13500: SYSAUX DATAFILE clause specified more than once

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-13499: %s

ORA-13499: %s

Cause: This is an internal Spatial error.

Action: Contact Oracle Support Services.

ORA-13498: %s

ORA-13498: %s

Cause: An error related to an external plugin was encountered in the GeoRaster component.

Action: Check the documentation for the external plugin, or contact the plugin provider and supply the exact error text.

ORA-13497: %s

ORA-13497: %s

Cause: This is an internal GeoRaster error.

Action: Contact Oracle Support Services. You may want to make sure the GeoRaster object is valid before you do so.

ORA-13485: error occurred during compression or decompression: string

ORA-13485: error occurred during compression or decompression: string

Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details.

Action: Check that the GeoRaster object is valid, that its metadata is valid for the specified compression format, and that valid parameters are passed into the compression or decompression operation.

ORA-13484: the file format and or or compression type is not supported

ORA-13484: the file format and or or compression type is not supported

Cause: The file format and or or compression type was not supported.

Action: Check the documentation for formats that are currently supported by GeoRaster.

ORA-13483: insufficient memory for the specified GeoRaster data

ORA-13483: insufficient memory for the specified GeoRaster data

Cause: There was insufficient memory to hold the specified GeoRaster data for this operation.

Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or reblock the GeoRaster data into smaller sized blocks. Check the documentation for details.

ORA-13482: GeoRaster object is not initialized for the image

ORA-13482: GeoRaster object is not initialized for the image

Cause: No GeoRaster object has been initialized for the specified image.

Action: Initialize a GeoRaster object to hold this image before loading it into the database. Check the documentation for details.

ORA-13481: the destination type is not supported

ORA-13481: the destination type is not supported

Cause: The specified destination type was not supported.

Action: Check the documentation for the destination types (such as FILE) supported by GeoRaster.

ORA-13480: the Source Type is not supported

ORA-13480: the Source Type is not supported

Cause: The specified source type was not supported.

Action: Check the documentation for the source types (such as FILE and HTTP) supported by GeoRaster.

ORA-13467: unsupported GeoRaster metadata specification: string

ORA-13467: unsupported GeoRaster metadata specification: string

Cause: The GeoRaster metadata specification is not supported.

Action: Check the documentation for the supported GeoRaster metadata specifications.

ORA-13466: format not appropriate for specified compression method

ORA-13466: format not appropriate for specified compression method

Cause: The operation failed because the GeoRaster object had an inappropriate type or format for the specified compression method. The GeoRaster type or format is not supported by the specified compression.

Action: Check the documentation for the appropriate GeoRaster types and formats for each compression method. Use SDO_GEOR.changeFormat to transform the GeoRaster object to an appropriate format, or apply another compression method.

ORA-13465: null or invalid table or column specification

ORA-13465: null or invalid table or column specification

Cause: The specified table or column did not exist, or the column was not a GeoRaster column.

Action: Make sure the specified table exists and the specified column is a GeoRaster column.

ORA-13464: error loading GeoRaster data: string

ORA-13464: error loading GeoRaster data: string

Cause: An internal error occurred while loading GeoRaster data into the database.

Action: Check the error message for details.

ORA-13463: error retrieving GeoRaster data: string

ORA-13463: error retrieving GeoRaster data: string

Cause: An internal error occurred while retrieving GeoRaster data from the database.

Action: Check the error message for details.

ORA-13462: invalid blocking specification

ORA-13462: invalid blocking specification

Cause: The specified blocking configuration was invalid.

Action: Block size must always be a power of 2.

ORA-13461: the interleaving type is not supported

ORA-13461: the interleaving type is not supported

Cause: The interleaving type of the GeoRaster object was not supported.

Action: Check the documentation for the interleaving types supported by GeoRaster. Use SDO_GEOR.changeFormat to transform the image to a supported interleaving type.

ORA-13460: GeoRaster metadata SRS error

ORA-13460: GeoRaster metadata SRS error

Cause: The referenced GeoRaster object had a zero model space SRID or the specified model space SRID was zero.

Action: Set or specify the model space SRID to be a nonzero number.