Oracle Database Errors or Warnings from Error ORA-13769 to ORA-13778

SQLServerF1

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: 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: 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: 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: 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: 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: 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: 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: 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: 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

Above are list of Oracle Database Errors or Warnings from Error ORA-13769 to ORA-13778 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

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