Cause: An obsolete file mode token was used in the SQL*Loader control file

SQL*Loader-00264: File mode token string parsed but ignored

Question Posted / guest

1 Answers
2968 Views
I also Faced
E-Mail Answers

Answer Posted / guest

Cause: An obsolete file mode token was used in the
SQL*Loader control file. As of Release 1.1 of SQL*Loader,
the file-processing options string is used to control file
processing, rather than keywords like STREAM, RECORD, FIXED,
and VARIABLE.

Action: No action required. This message is informational.
Removing the obsolete keywords will eliminate the message
without changing the way in which the datafile is processed.

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

ORA-26084: direct path context already finished

1879

IMP-00064: Definition of LOB was truncated by export

6350

IMG-02003: 2FF03 - incorrect color histogram feature specification

1653

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

1563

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-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-00070: Lob definitions in dump file are inconsistent with database.

1700

ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2743

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.

2801

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

2687

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

2346

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

1901

NZE-28890: Entrust Login Failed

1812

[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