Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-22600: encountered 8.0.2 (Beta) VARRAY data that cannot
be processed
- 1 Answers
- 2803 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: Production Oracle8 (8.0.3 and beyond) encounters some
VARRAY data which was created and stored by Oracle8 8.0.2
(Beta 2). Production Oracle8 cannot understand or process
such VARRAY data.
Action: Delete the VARRAY data from the table by dropping
the table, deleting the rows, or nulling out the VARRAY
columns, and then re-insert the VARRAY data. There is no
provided script or tool to help automate this conversion.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
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-26028: index string.string initially in unusable state
ORA-26084: direct path context already finished
ORA-26082: load of overlapping segments on table string.string is not allowed
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-26095: unprocessed stream data exists
RMAN-05017: no copy of datafile number found to recover
IMP-00070: Lob definitions in dump file are inconsistent with database.
NZE-28890: Entrust Login Failed
ORA-26094: stream format error: input column overflow
ORA-16626: failed to enable specified object
ORA-16516: The current state is invalid for the attempted operation.
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?
