Sunday 11 March 2012

ORA-13769: Snapshots string and string do not exist.

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-13768: Snapshot ID must be between string and string.

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-13767: End snapshot ID must be greater than or equal to begin snapsho ID.

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-13766: A ranking measure is required.

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-13765: Value string is illegal for a result limit.

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-13764: Value string is illegal as a result percentage.

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-13763: illegal ranking attribute string

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-13762: The string ranking measure is invalid.

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-13761: invalid filter

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-13759: User string cannot remove reference string .

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-13758: SQL Tuning Set string owned by user string is in use.

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-13757: SQL Tuning Set string owned by user string is active.

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-13756: Cannot update attribute string .

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-13755: invalid SQL Tuning Set name

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-13754: SQL Tuning Set string does not exist for user string .

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-13753: SQL Tuning Set string already exists for user string .

ORA-13753: SQL Tuning Set string already exists for user string .

Cause: The user attempted to create a or SQL Tuning or Set using a name that already exists for that owner.

Action: Change the name of the SQL Tuning Set and retry the operation.

ORA-13752: User string must be SYS or must have the ADMINISTER ANY SQL TUNING SET privilege.

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-13751: SQL Tuning Set string does not exist for owner string or user string does not have permission to access the SQL Tuning Set .

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-13750: User string has not been granted the ADMINISTER SQL TUNING SET privilege.

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-13712: Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version string do not match the database version string .

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 ? or rdbms or admin or awrrpt and ? or rdbms or admin or ashrpt on these snapshots to analyze the data in them.

ORA-13711: Some snapshots in the range (string, string( are missing key statistics.

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-13710: Parameter string must have a higher value than parameter string . The values supplied were string and string respectively.

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-13709: Required parameter string must be set before execution.

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-13708: Some snapshots in the range (string, string( were purged before the analysis was complete.

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-13707: Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.

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 or 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-13706: Invalid value string specified for parameter string in string analysis mode.

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-13705: There was a instance shutdown or startup between the snapshots in the range (string, string(.

ORA-13705: There was a instance shutdown or 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 or startup in between them.

ORA-13704: Invalid value string specified for parameter string .

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-13703: The snapshot pair (string, string( for database_id string and instance_id string are not found in the current repository.

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-13702: Snapshot IDs specified by the range (string, string( are equal.

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-13701: Snapshot pair (string, string( seems to be specified in reverse order.

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-13699: Advisor feature is not currently implemented.

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-13644: The user string is invalid.

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-13643: The task can not be interrupted or cancelled.

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-13642: The specified string string provided for string cannot be converted to a date. The acceptable date format is string.

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-13641: Task cannot be interrupted yet. You may cancel it instead.

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-13640: The current operation was cancelled because it timed out, and was not in interruptible mode.

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-13639: The current operation was interrupted because it timed out.

ORA-13639: The current operation was interrupted because it timed out.

Cause: The task or object operation timed out.

Action: None

ORA-13638: The user interrupted the current operation.

ORA-13638: The user interrupted the current operation.

Cause: The user signaled an interrupt during a task or object operation.

Action: None

ORA-13637: Executing or modifying task string is disallowed until the task is reset to its initial state.

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-13636: The specified value provided for parameter string is not valid for this advisor.

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-13635: The value provided for parameter string cannot be converted to a number.

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-13634: The task string needs to be reset before being re-executed.

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-13633: The task string was interrupted and needs to be resumed.

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-13632: The user cancelled the current operation.

ORA-13632: The user cancelled the current operation.

Cause: The user signaled a cancel during a task or object operation.

Action: None

ORA-13631: The task string contains no execution results.

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-13630: The task string contains execution results and cannot be executed.

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-13629: The task or object string is being used by another operation.

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-13628: Insufficient privileges to access the task belonging to the specified user

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-13627: Setting of parameter string is disallowed until the task is reset.

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

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-13625: %s is an invalid advisor object type.

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-13624: The task string is executing and cannot be deleted or modified.

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

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-13622: invalid recommendation annotation

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-13621: The task_or object string is marked as a template and cannot perform the requested 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-13620: The task or object string is read-only and cannot be deleted or modified.

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-13619: The procedure argument string is greater than the maximum allowable length of string characters.

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-13618: The specified value is not a valid value for procedure argument string.

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-13617: The specified task string already executing

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.