Action No action is necessarily required, because SQL*Loader uses only one of the lengths...

Check the log file under the heading “Len” in the table–description section to see which length was used. Adjusting the control file to produce uniform length specifications will remove the warning.
SQL*Loader–308
optional SQL string of column name must be in double quotes
Cause
A SQL string was found that was not quoted or in single quotes.
Action
Use double quotes for the SQL string, rather than single quotes.
SQL*Loader Messages
7 – 9
00400–00499: Columns
SQL*Loader–350
syntax error at line num
Cause
num identifies the line in the control file at which the error occurred. This message is followed by another of the form
Expecting str1, found str2
where str1 is a description of what SQL*Loader expected in the control file, and str2 is what was found. Then SQL*Loader displays the offending line from the control file, indicating the location of the error in the line by a carat (^) or an asterisk (*). An example follows:
SQL*Loader–350: Syntax error at line 28
Expecting column name, found keyword CHAR
col3 ENCLOSED BY ’”’, CHAR ENCLOSED ”’”,
Action
Compare the DDL syntax against the syntax diagrams in Oracle7 Server Utilities and make any necessary corrections.
00400–00499: Columns
SQL*Loader–401
end field position num must be greater than or equal to start num
Cause
The named field contains a ( start: end) clause in which end is less than start.
Action
Modify the clause so that end is greater than or equal to start.
SQL*Loader–402
unable to determine length of column name.name from specification Cause
The specified datatype does not have an implied length (for example, a numeric external or RAW datatype), it is not specified with delimiters, no length was specified, and a length cannot be determined from a
POSITION clause.
Action
If a POSITION clause is specified, adding an end location to it produces a length specification. This clause then has the form
POSITION(start:end)
A length can also specified after the datatype, as in
INTEGER EXTERNAL (6)
Finally, the field could be specified with delimiters, or the datatype changed to one that has an implied length.
7 – 10
Oracle7 Server Messages
00400–00499: Columns
SQL*Loader–403
referenced column name not present in table name
Cause
The named column is not present in the given table.
Action
Correct the column name or table name.
SQL*Loader–404
column name present more than once in table name
Cause
The named column is specified more than once in a single
INTO TABLE statement.
Action
Remove the extraneous column specification.
SQL*Loader–405
need termination delim with optional enclosure delim: column name.name
Cause
The named column was specified with an optional enclosure delimiter, but no termination delimiter. Enclosure delimiters can only be optional when termination delimiters are present.
Action
Specify a termination delimiter or make the enclosure delimiters non–optional.
SQL*Loader–406
if data is all generated, number to load cannot be ALL
Cause
When only generated data is loaded, a number to load must be given so SQL*Loader knows when to stop.
Action
Specify a number to load.
SQL*Loader–407
if data is all generated, number to skip is meaningless
Cause
When all data is generated, no file is read, and there are no records to skip.
Action
Remove the number to skip.
SQL*Loader–408
physical record stack overflow
Cause
An internal error has occurred.
Action
Contact customer support.
SQL*Loader Messages
7 – 11
00400–00499: Columns
SQL*Loader–409
number to skip must be table–level, not load–level on continued loads Cause
The SKIP parameter was specified on the command line or in the OPTIONS
statement, but the load was specified as continued with CONTINUE_LOAD.
When a multiple–table direct load is interrupted, it is possible that a different number of records were loaded into each table. As a result, the number of records to skip must be specified for each table when continuing the load. In this case, the load is specified as continued with the CONTINUE_LOAD
statement, and the number of records to skip is given in each
INTO TABLE statement.