Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / guest
Cause: To do a direct path load load when the front end and
back end of the database are on separate hardware systems,
the systems must be identical, using the same machine,
operating system, and character set. This error occurs when
SQL*Loader detects a difference between the systems that
will prevent a direct load from operating properly.
Action: Use a conventional path load for this configuration.
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
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-16627: No standby databases support the overall protection mode.
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26032: index string.string loading aborted after string keys
NZE-28868: Peer certificate chain check failed.
ORA-26028: index string.string initially in unusable state
NZE-28890: Entrust Login Failed
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26076: cannot set or reset value after direct path structure is allocated
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.
IMP-00070: Lob definitions in dump file are inconsistent with database.
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
IMP-00064: Definition of LOB was truncated by export
