ORA-13912: Critical threshold value is less than warning
threshold value.
- 1 Answers
- 2547 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: An attempt was made to call SET_THRESHOLD procedure
with the critical threshold value less than the warning
threshold value.
Action: Check the threshold values and reissue the statement.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26082: load of overlapping segments on table string.string is not allowed
NZE-28868: Peer certificate chain check failed.
ORA-26027: unique index string.string partition string initially in unusable state
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
IMP-00070: Lob definitions in dump file are inconsistent with database.
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26032: index string.string loading aborted after string keys
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?
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
ORA-26029: index string.string partition string initially in unusable state
ORA-26084: direct path context already finished
ORA-26028: index string.string initially in unusable state
ORA-26076: cannot set or reset value after direct path structure is allocated
