ORA-13752: User "string" must be SYS or must have the
"ADMINISTER ANY SQL TUNING SET" privilege.
- 1 Answers
- 2957 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
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.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
ORA-26079: file "string" is not part of table string.string
ORA-26082: load of overlapping segments on table string.string is not allowed
ORA-16516: The current state is invalid for the attempted operation.
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
ORA-26084: direct path context already finished
ORA-26029: index string.string partition string initially in unusable state
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
IMG-02003: 2FF03 - incorrect color histogram feature specification
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-26028: index string.string initially in unusable state
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
IMP-00064: Definition of LOB was truncated by export
RMAN-05017: no copy of datafile number found to recover
