KUP-04017: OS message: string

KUP-04017: OS message: string

Cause: An error occurred. This message contains the message associated with this error that was returned by the operating system. The message displayed before this one should indicate the operation that failed.

Action: none

KUP-04016: unknown SLF status code number

KUP-04016: unknown SLF status code number

Cause: Internal component SLF returned an unknown error code.

Action: Contact Oracle support.

KUP-04015: internal SLF error

KUP-04015: internal SLF error

Cause: Internal component SLF encountered an internal error.

Action: Contact Oracle support.

KUP-04014: invalid SLF parameter

KUP-04014: invalid SLF parameter

Cause: An invalid parameter was passed in a call to internal component SLF.

Action: Contact Oracle support.

KUP-04013: other system error

KUP-04013: other system error

Cause: Internal component SLF was unable to complete an operation because of a system error.

Action: The message displayed before this message describes the operation that was being performed when the error occurred.

KUP-04012: file length is too large for output field

KUP-04012: file length is too large for output field

Cause: Size of a file is too large.

Action: Break the file up into smaller files.

KUP-04011: file system is full

KUP-04011: file system is full

Cause: An operation on a file failed because the file system is full. The message preceding this one contains the name of the file.

Action: Free space on the file system or move the file to a different file system.

KUP-04010: file does not exist

KUP-04010: file does not exist

Cause: A file operation failed because a file does not exist. The message preceding this message contains the name of the file.

Action: Verify that the correct file name was specified.

KUP-04009: invalid SLF handle

KUP-04009: invalid SLF handle

Cause: An internal error caused a data structure associated with the file to become corrupt.

Action: Contact Oracle support.

KUP-04008: access to file denied

KUP-04008: access to file denied

Cause: Acess to a file was denied. The file is named in the message preceding this one.

Action: See the message that follows for more information. Verify that the correct files are being used and that the appropriate access is allowed to those files.

KUP-04007: end of file reached

KUP-04007: end of file reached

Cause: The end of file was reached for a file. The file is named in the message preceding this one.

Action: See the message that follows this one for more information.

KUP-04006: file operation failed

KUP-04006: file operation failed

Cause: An operation on a file failed. The file is named in the message preceeding this one.

Action: See subsequent message for more information about the error.

KUP-04005: file operation successful

KUP-04005: file operation successful

Cause: A file oepration succeeded.

Action: None

KUP-04004: error while reading file string

KUP-04004: error while reading file string

Cause: An error occurred while reading the specified file.

Action: See the error that follows to determine the action to be taken.

KUP-04003: error while closing file string

KUP-04003: error while closing file string

Cause: An error occurred while closing the specified file.

Action: See the error that follows to determine the action to be taken.

KUP-04002: error getting file size for file string

KUP-04002: error getting file size for file string

Cause: An error occurred while retrieving the number of bytes in the specified file.

Action: See the error that follows to determine the action to be taken.

KUP-04001: error opening file string

KUP-04001: error opening file string

Cause: An error occurred while attempting to open the specified file. This message should be followed by another message with more information about the error.

Action: See the error that follows to determine the action to be taken.

KUP-04000: error initializing IO state for file string in string

KUP-04000: error initializing IO state for file string in string

Cause: An unexpected error occurred while preparing the file.

Action: Contact Oracle support.

KUP-03999: error occurred while processing a date format: ORA-number: string

KUP-03999: error occurred while processing a date format: ORA-number: string

Cause: Error converting a date format string into an internal representation.

Action: Verify that the date format strings specified in the access parameters are valid.

KUP-03022: lob data could not be found for field string

KUP-03022: lob data could not be found for field string

Cause: The field specified in the data source that contains the name of the lob file for the record could not be identified.

Action: none

KUP-03021: clause references unknown field string

KUP-03021: clause references unknown field string

Cause: A WHEN, NULLIF or DEFAULTIF clause referenced a field that doesn t exist in the data file.

Action: none

KUP-03020: empty delimiter specified for record

KUP-03020: empty delimiter specified for record

Cause: An empty delimiter string was specified for a record delimiter.

Action: Specify the string used to delimiter records.

KUP-03019: directory object not specified in LOBFILE clause for field string

KUP-03019: directory object not specified in LOBFILE clause for field string

Cause: A LOBFILE clause was specified for the field, but no directory object was specified. When no directory object is specified, then the default directory specified for the external table is used, but no default directory was specified.

Action: Specify a directory object in the LOBFILE clause or specify a default directory for the external table.

KUP-03018: invalid date mask string specified for column string

KUP-03018: invalid date mask string specified for column string

Cause: The date mask for the specified column is invalid.

Action: none

KUP-03017: length specified for VARIABLE records must be greater than 0

KUP-03017: length specified for VARIABLE records must be greater than 0

Cause: A record format of VARIABLE was specified with a length of 0.

Action: none

KUP-03016: length specified for FIXED records must be greater than 0

KUP-03016: length specified for FIXED records must be greater than 0

Cause: A record format of FIXED was specified with a length of 0.

Action: none

KUP-03015: OCI error getting datetime lfprecision.

KUP-03015: OCI error getting datetime lfprecision.

Cause: An error occurred while trying to obtain database column precision.

Action: Contact Oracle Support.

KUP-03014: OCI error getting datetime fsprecision.

KUP-03014: OCI error getting datetime fsprecision.

Cause: An error occurred while trying to obtain a datetime column precision value.

Action: Contact Oracle Support.

KUP-03013: OCI error getting database column scale.

KUP-03013: OCI error getting database column scale.

Cause: An error occurred while trying to obtain database column scale.

Action: Contact Oracle Support.

KUP-03012: OCI error getting database column precision.

KUP-03012: OCI error getting database column precision.

Cause: An error occurred while trying to obtain database column precision.

Action: Contact Oracle Support.

KUP-03011: OCI error getting database column size.

KUP-03011: OCI error getting database column size.

Cause: An error occurred while trying to obtain database column size.

Action: Contact Oracle Support.

KUP-03010: OCI error getting database column type.

KUP-03010: OCI error getting database column type.

Cause: An error occurred while trying to obtain database column type.

Action: Contact Oracle Support.

KUP-03009: OCI error getting column name.

KUP-03009: OCI error getting column name.

Cause: An error occurred while trying to obtain column name.

Action: Contact Oracle Support.

KUP-03008: OCI error getting column parameters.

KUP-03008: OCI error getting column parameters.

Cause: An error occurred while trying to obtain column parameters.

Action: Contact Oracle Support.

KUP-03007: end position (number) is less than start position (number) for range

KUP-03007: end position (number) is less than start position (number) for range

Cause: A byte range specified a start position that comes after the end position.

Action: Verify the start and end positions are correctly specified.

KUP-03006: error initializing handle for character set string

KUP-03006: error initializing handle for character set string

Cause: Error attempting to retrieve information for the character set.

Action: Verify that the character set name is valid.

KUP-03005: relative end (number) specified does not match fieldlen(number) for field string

KUP-03005: relative end (number) specified does not match fieldlen(number) for field string

Cause: The number of bytes specified by the relative end position for the field does not match the number of bytes in the datatype.

Action: Correct either the datatype length or the relative end position.

KUP-03004: absolute end (number) specified with relative start (number) for field string

KUP-03004: absolute end (number) specified with relative start (number) for field string

Cause: The position of field was specified with a relative start and an absolute end.

Action: Use relative end with relative start

KUP-03003: absolute end(number) -start(number) = fieldlength (number) for field string

KUP-03003: absolute end(number) -start(number) = fieldlength (number) for field string

Cause: The number of bytes occupied by the field as specified by the starting offset and ending offset of the field is not the same as the number of bytes specified for the datatype of the field.

Action: Verify the absolute begin or end position(s) specified match the length of the field.

KUP-03002: end position (number) lamp;lt;lamp;nbsp;= start position (number) for field: string

KUP-03002: end position (number) lamp;lt;lamp;nbsp;= start position (number) for field: string

Cause: Error in specifying position for the specified field in the access parameters.

Action: Check that the specified end position is greater than the specified start position.

KUP-03001: fatal error during library cache pre-loading

KUP-03001: fatal error during library cache pre-loading

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

KUP-02006: script line too long

KUP-02006: script line too long

Cause: a line longer than 500 bytes was encountered

Action: break the line up into shorter lines

KUP-02005: token too big

KUP-02005: token too big

Cause: A token longer than 1000 bytes was encountered

Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token.

KUP-02004: quoted string too big

KUP-02004: quoted string too big

Cause: A quoted string longer than 2000 bytes was encountered.

Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string.

KUP-02003: unrecognized character: string

KUP-02003: unrecognized character: string

Cause: An input character that is neither an alpha, digit, or punctuation was encountered.

Action: Remove the character.

KUP-02002: unexpected end of input file reached

KUP-02002: unexpected end of input file reached

Cause: This is probably caused by failure to supply the closing quote for a quoted string.

Action: Correct the input.

KUP-02001: unrecognized punctuation symbol string

KUP-02001: unrecognized punctuation symbol string

Cause: An illegal punctuation character was encountered.

Action: Remove the illegal character.

KUP-02000: wrong message file version (msg number not found)

KUP-02000: wrong message file version (msg number not found)

Cause: The kupxx.msb file is not the correct version.

Action: Check that the installation was done correctly.

KUP-01008: the bad identifier was: string

KUP-01008: the bad identifier was: string

Cause: This is an informational message indicating the identifier token that caused a syntax error.

Action: none

KUP-01007: at line number column number

KUP-01007: at line number column number

Cause: This is an informational message indicating the line and column where a syntax error was detected.

Action: none

KUP-01006: error signalled during parse of access parameters

KUP-01006: error signalled during parse of access parameters

Cause: An error was signalled during parsing of the access parameters.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

KUP-00601: fatal XAD error

KUP-00601: fatal XAD error

Cause: A fatal error has occurred.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

KUP-00600: internal error, arguments (string( (string( (string( (string( (string(

KUP-00600: internal error, arguments (string( (string( (string( (string( (string(

Cause: An internal XAD error occurred.

Action: Contact Oracle Support.

KUP-00562: unknown escape sequence

KUP-00562: unknown escape sequence

Cause: An unknown escape sequence was specified to the parser. An escape sequence is a backslash followed by a character.

Action: Consult documentation for list of allowable control characters.

KUP-00561: invalid length for binary integer field string

KUP-00561: invalid length for binary integer field string

Cause: An integer field was specified with an invalid length. The only supported lengths for binary integer fields are 1, 2, 4, and 8.

Action: none

KUP-00554: error encountered while parsing access parameters

KUP-00554: error encountered while parsing access parameters

Cause: The parser detected a syntax error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

KUP-00552: internal XAD package failed to load

KUP-00552: internal XAD package failed to load

Cause: An error was encountered while attempting to initialize the XAD package.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

SQL*Loader-03120: Resumable parameters ignored -- current session not resumable

SQL*Loader-03120: Resumable parameters ignored -- current session not resumable

Cause: Current session is not resumable.

Action: Must specify RESUMABLE=TRUE to enable resumable session in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect. 24 UP-00550: parser package failed to load Cause: Attempt to load parser package returned an error indication. Action: This message should be accompanied by other error message(s) indicating the cause of the error.

SQL*Loader-02050: Multibyte character error.

SQL*Loader-02050: Multibyte character error.

Cause: Text specified by POSITION or terminated by newlines is invalid.

Action: Edit the SQL*Loader control file or the data file to fix alignment of column.

SQL*Loader-02026: the load was aborted because SQL Loader cannot continue.

SQL*Loader-02026: the load was aborted because SQL Loader cannot continue.

Cause: The load cannot continue. See the error message before this * message for the cause of the error.

Action: See the action for the error message that precedes this one.