Oracle7 Server Messages
00500-00599: File I/O and Operating System
SQL*Loader-500 unable to open file name
| Cause: | SQL*Loader could not open the named file. | |
| Action: | Check the operating system messages below this one in the log file. | |
SQL*Loader-501 unable to read file name
| Cause: | SQL*Loader could not read the named file. | |
| Action: | Check the operating system messages below this one in the log file. | |
SQL*Loader-502 unable to open log file for write name
| Cause: | SQL*Loader could not open the named file. | |
| Action: | Check that the file location is specified correctly and that write privileges for the file have been granted. | |
SQL*Loader-503 error appending extension to file name
| Cause: | SQL*Loader could not append the default extension to create the filename. The given name could be too long or contain illegal characters. | |
| Action: | Check the specified filename. | |
SQL*Loader-504 error skipping records in file name
| Cause: | SQL*Loader could not open the file or could not read from it. | |
| Action: | Check that the file is where it is expected and that read access has been granted. | |
SQL*Loader-506 unable to open bad file name
| Cause: | SQL*Loader could not open the named file. | |
| Action: | Check the errors below it in the log file for more information. | |
SQL*Loader-507 unable to open discard file name
| Cause: | SQL*Loader could not open the named file. | |
| Action: | Check the errors below this message in the log file for more information. | |
SQL*Loader-510 physical record in datafile name is longer than the maximum num
| Cause: | The datafile has a physical record that is too long. | |
| Action: | Use CONCATENATE or CONTINUEIF. Break up the physical records. | |
SQL*Loader-511 unable to initialize read functions
| Cause: | SQL*Loader could not initialize the read functions. | |
| Action: | Check the errors below this message in the log file for more information. | |
SQL*Loader-512 unable to free read buffer
| Cause: | An internal error has occurred. | |
| Action: | Contact customer support. | |
SQL*Loader-513 unable to close file name
| Cause: | SQL*Loader could not close the named file. | |
| Action: | Check the errors below this message in the log file for more information. | |
SQL*Loader-514 error getting elapsed time
| Cause: | SQL*Loader could not get the elapsed time from the system. | |
| Action: | No action required. | |
SQL*Loader-515 error getting CPU time
| Cause: | SQL*Loader could not get the CPU time from the system. | |
| Action: | No action required. | |
SQL*Loader-516 control file name has no contents
| Cause: | The named file was found to be empty. | |
| Action: | Check that the intended file was referenced and that it is not empty. | |
SQL*Loader-517 error decomposing filename name
| Cause: | SQL*Loader could not break down the filename into its component parts. | |
| Action: | Check the filename for illegal characters. | |
SQL*Loader-518 error reassembling filename name
| Cause: | SQL*Loader could not put the filename back together again from
its components. | |
| Action: | Check the filename for illegal characters. | |
SQL*Loader-519 error num writing to filename name
| Cause: | SQL*Loader could not write to the named file. The error number displayed in the message is the one returned by the C language FWRITE function. More information can be obtained by accessing a C language reference manual for
the system. | |
| Action: | Check that the file's location is where it is expected to be and that write privileges on it have been granted. Be sure that adequate disk space is available and that the disk quota is not exceeded. | |