Cause: The total number of HHCODE columns in the SLF file does not match the total in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The total number of dimensions for each HHCODE column in the SLF file does not match the total in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The total number of non-HHCODE columns in the SLF file does not match the total in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The HHCODE column name in the SLF file does not match the name in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The number of dimensions of HHCODE column in the SLF file does not match the number in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The maximum level of dimensions of HHCODE column in the SLF file does not match the maximum level in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The size of the HHCODE column in the SLF file does not match the size in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The null field of the HHCODE column in the SLF file does not match the null field in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The dimension name of the HHCODE column in the SLF file does not match the name in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The dimension number of the HHCODE column in the SLF file does not match the number in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The dimension level of the HHCODE column in the SLF file does not match the level in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The dimension lower bound of the HHCODE column in the SLF file does not match the lower bound in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The dimension upper bound of the HHCODE column in the SLF file does not match the upper bound inthe spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The column name in the SLF file does not match the name in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The null field of the column in the SLF file does not match the null field in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The column type in the SLF file does not match the type in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The precision field of the column in the SLF file does not match the precision field in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The scale field of the column in the SLF file does not match the scale field in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

Cause: The size of the column in the SLF file does not match the size in the spatial table. Either the spatial table definition was changed after the SLF file was created or the SLF file is being loaded into the wrong spatial table.

Action: Verify the SLF file is being loaded into the correct spatial table or regenerate the SLF file.

SDO-05020 no data found in SLF file (just header information)

Cause: During the conversion process, the writing SLF record process died.

Action: Re-create the SLF file verifying that the SLF data is written.

SDO-05200 line in 'string' was too complex to parse

Cause: Data in the control file exceeded maximum field limits.

Action: Document messages and contact Oracle Customer Support.

SDO-05201 insufficient number of fields in 'string'

Cause: There were fewer than 3 fields in the control file.

Action: Check the control file for accuracy.

SDO-05202 did not find the expected line or keyword in 'string'

Cause: Expected keyword or line was not found.

Action: Verify that the specified keywords are in the correct order.

SDO-05203 an invalid number of partition key columns was specified in 'string'

Cause: More than one partition key was specified in the named control file.

Action: Verify only one HHCODE is specified as the partition key in the named control file.

SDO-05204 HHCODE column is missing a dimension sequence in 'string'

Cause: When entering the spatial information into the named control file, a spatial sequence was left out.

Action: Verify that the sequence values for the dimensions are correct.

SDO-05205 file type keyword not found in 'string'

Cause: The required file type keyword in the named file is missing.

Action: Verify that the control file has the correct information.

SDO-05206 unexpected keyword or value found in 'string'

Cause: There was more than 1 field found in the control file.

Action: Check the control file for accuracy.

SDO-05207 'string' is an invalid file type specified in control file

Cause: The file type was spelled incorrectly. The only valid file types are BINARY and ASCII.

Action: Verify that the file type specified in the control file is correct.

SDO-05208 format keyword not found in 'string'

Cause: The required format keyword in named file is missing.

Action: Verify that the control file has the correct information.

SDO-05209 unexpected keyword or value found in 'string'

Cause: There were more than 2 fields found in the control file.

Action: Check the control file for accuracy.

SDO-05210 'string' is an invalid keyword specified in control file

Cause: The keyword FIXED was not found in control file.

Action: Verify that the keyword specified in the control file is correct.

SDO-05211 'string' is an invalid record length specified for the data file

Cause: Record length specified is invalid for given data file.

Action: Verify that the record length specified is correct.

SDO-05212 'string' is an invalid keyword specified in control file

Cause: The only valid keywords are DIMENSION and COLUMN.

Action: Verify that the file type specified in the control file is correct.

SDO-05213 'string' is an invalid keyword specified in control file

Cause: The missing keyword POSITION was not found in the control file.

Action: Verify that the keyword specified in the control file is correct.