Answer Posted / guest
Cause: Each byte of a zoned decimal field must have a valid
value based on the character set encoding used. ASCII-based
zoned decimals must follow the formats specified in the VAX
Architecture Reference Manual. EBCDIC-based zoned decimals
must follow the formats specified in the ESA/390 Principles
of Operations, version 8.1.
Action: Check the SQL*Loader control file's specifications
against the log file to ensure that the field location was
specified correctly. Check the contents of the field.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 1 No |
Post New Answer View All Answers
IMP-00064: Definition of LOB was truncated by export
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-26029: index string.string partition string initially in unusable state
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26095: unprocessed stream data exists
ORA-26084: direct path context already finished
ORA-16516: The current state is invalid for the attempted operation.
IMG-02003: 2FF03 - incorrect color histogram feature specification
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
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-26032: index string.string loading aborted after string keys
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-26082: load of overlapping segments on table string.string is not allowed
ORA-16627: No standby databases support the overall protection mode.
ORA-26027: unique index string.string partition string initially in unusable state