O2I-00126: You must specify an INTYPE file with
SCHEMA_NAMES=FROM_INTYPE
Answer Posted / guest
Cause: The option SCHEMA_NAMES=FROM_INTYPE requests that
schema names be written to the OUTTYPE file as given in the
INTYPE file. However, an INTYPE file was not specified.
Action: Either supply the name of an INTYPE file, or specify
the SCHEMA_NAMES option ALWAYS or IF_NEEDED.
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-16627: No standby databases support the overall protection mode.
ORA-26032: index string.string loading aborted after string keys
ORA-26079: file "string" is not part of table string.string
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
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.............
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
RMAN-05017: no copy of datafile number found to recover
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-16626: failed to enable specified object
ORA-26028: index string.string initially in unusable state
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-26027: unique index string.string partition string initially in unusable state
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-26084: direct path context already finished