Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-34243: (MXDCL11) You can only use the string keyword
when defining a COMPOSITE.
- 1 Answers
- 3520 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: User supplied the COMPRESSED keyword when defining an
object that was not a COMPOSITE.
Action: If the intent is to create a compressed composite,
make sure that the object type is COMPOSITE. Otherwise,
remove the COMPRESSED keyword from the command string and rerun.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-26094: stream format error: input column overflow
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
RMAN-05017: no copy of datafile number found to recover
ORA-26027: unique index string.string partition string initially in unusable state
ORA-26028: index string.string initially in unusable state
ORA-26032: index string.string loading aborted after string keys
ORA-26079: file "string" is not part of table string.string
ORA-26082: load of overlapping segments on table string.string is not allowed
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.
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-16516: The current state is invalid for the attempted operation.
ORA-26095: unprocessed stream data exists
ORA-26029: index string.string partition string initially in unusable state
ORA-16627: No standby databases support the overall protection mode.
IMP-00064: Definition of LOB was truncated by export
