Oracle7 Server Messages
00300-00399: DDL Parsing
SQL*Loader-303 non-hex character encountered where hex char expected
| Cause: | A non-hexadecimal character was found in a hexadecimal string. | |
| Action: | Change it to the intended hexadecimal character. | |
SQL*Loader-304 illegal combination of non-alphanumeric characters
| Cause: | The control file contains a combination of non-alphanumeric characters that SQL*Loader does not recognize. For example, the combination != is recognized as "not equal", but the combination =! is not valid. | |
| Action: | Remove the unrecognized characters from the control file. | |
SQL*Loader-305 more than one end of file character encountered
| Cause: | The file contains multiple end-of-file marks. | |
| Action: | Remove the excess end-of-file characters. | |
SQL*Loader-306 token longer than max allowable length of num characters
| Cause: | The control file contains a single word or combination of characters (a token) that is longer than the maximum permissible value. The maximum possible value is shown. This error could result from missing spaces, so that multiple tokens are joined. | |
| Action: | Check that the proper control file is being executed. Separate tokens, if joined, or shorten the token. | |
SQL*Loader-307 Warning: conflicting lengths num1 and num2 specified for column name
| Cause: | The control file specifies two different lengths for the named column. There are three ways to specify the length of a field: | |
- with the POSITION keyword: POSITION(1:3)
- with the length specifier: CHAR(6)
- with the implied length of a datatype; for example, INTEGER
A conflict could occur between any two of these specifications (or among all three, but only two are shown).
A common cause of this error is the specification of some numeric datatype, such as INTEGER, when the numeric external form is intended (INTEGER EXTERNAL). The external form consists of character data, so it is considerably longer than the numeric form, which consists of binary data.
| 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-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. | |