Answer Posted / guest
Cause: The mask option <clause> was passed to a UTL_PG
conversion routine, but is not supported by UTL_PG. The
<clause> can be: USAGE IS POINTER USAGE IS INDEX USAGE IS
COMP-1 USAGE IS COMP-2 POINTER
Action: Remove the <clause> from the mask options parameter
in the PL/SQL call to UTL_PG.
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-26030: index string.string had string partitions made unusable due to:
ORA-26094: stream format error: input column overflow
NZE-28890: Entrust Login Failed
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
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-26084: direct path context already finished
IMG-02003: 2FF03 - incorrect color histogram feature specification
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?
ORA-26032: index string.string loading aborted after string keys
ORA-26029: index string.string partition string initially in unusable state
IMP-00070: Lob definitions in dump file are inconsistent with database.
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26076: cannot set or reset value after direct path structure is allocated