SQL*Loader-00251: Sort devices are not used by SQL*Loader
Answer Posted / guest
Cause: The SQL*Loader control file contains a SORTDEVT
statement. SQL*Loader ignores this clause.
Action: No action required. This is an informational message.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
ORA-26029: index string.string partition string initially in unusable state
ORA-26027: unique index string.string partition string initially in unusable state
RMAN-05017: no copy of datafile number found to recover
NZE-28868: Peer certificate chain check failed.
ORA-26028: index string.string initially in unusable state
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-16516: The current state is invalid for the attempted operation.
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
ORA-26032: index string.string loading aborted after string keys
IMP-00064: Definition of LOB was truncated by export
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?
[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table
ORA-26079: file "string" is not part of table string.string
ORA-26030: index string.string had string partitions made unusable due to: