Cause: The end of the logical record was encountered before the end of a v

SQL*Loader-00640: Variable length field was truncated.

Question Posted / guest

1 Answers
3654 Views
I also Faced
E-Mail Answers

Answer Posted / guest

Cause: The end of the logical record was encountered before
the end of a variable length field. The length of each
variable-length field is embedded in the field, so
SQL*Loader knows that more data should have been present.

Action: Check the data for inadvertent truncation and verify
the SQL*Loader control file specifications against the log
file; the field may be starting in the wrong place.

Please add more information about this Error

Is This Answer Correct ?

0 Yes

0 No

Post New Answer View All Answers

Please Help Members By Posting Answers For Below Questions

[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

2680

IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1563

when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

2174

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?

2670

ORA-26028: index string.string initially in unusable state

3802

ORA-26027: unique index string.string partition string initially in unusable state

6703

invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity

3322

ORA-26079: file "string" is not part of table string.string

1896

ORA-16627: No standby databases support the overall protection mode.

3933

ORA-26076: cannot set or reset value after direct path structure is allocated

1901

ORA-26082: load of overlapping segments on table string.string is not allowed

1717

ORA-26029: index string.string partition string initially in unusable state

2097

IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2687

ORA-26032: index string.string loading aborted after string keys

2057

RMAN-05017: no copy of datafile number found to recover

2346