ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly
used in hash expre\ssion.
Answer Posted / guest
Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed
in hash expression\s.
Action: Recreate the cluster and remove the offending keywords.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-16627: No standby databases support the overall protection mode.
ORA-26094: stream format error: input column overflow
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.
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
ORA-26027: unique index string.string partition string initially in unusable state
ORA-26076: cannot set or reset value after direct path structure is allocated
IMP-00064: Definition of LOB was truncated by export
ORA-26079: file "string" is not part of table string.string
NZE-28890: Entrust Login Failed
ORA-26095: unprocessed stream data exists
IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
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?
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26028: index string.string initially in unusable state