12C ORA-错误汇总19

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.
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-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-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-00600: internal error, arguments [string] [string] [string] [string] [string]
Cause: An internal XAD error occurred.
Action: Contact Oracle Support.
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-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-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
36-2 Oracle Database Error Messages
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-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-02001: unrecognized punctuation symbol "string"
Cause: An illegal punctuation character was encountered.
Action: Remove the illegal character.
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-02003: unrecognized character: string
Cause: An input character that is neither an alpha, digit, or punctuation was
encountered.
Action: Remove the character.
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-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-02006: script line too long
Cause: a line longer than 500 bytes was encountered
Action: break the line up into shorter lines
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-03002: end position (number) <= 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-03003: absolute end(number) - start(number) != fieldlength (number) for field
string
KUP-00552 to KUP-11024 36-3
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/end position(s) specified match the length of
the field.
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-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-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-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-03008: OCI error getting column parameters.
Cause: An error occurred while trying to obtain column parameters.
Action: Contact Oracle Support.
KUP-03009: OCI error getting column name.
Cause: An error occurred while trying to obtain column name.
Action: Contact Oracle Support.
KUP-03010: OCI error getting database column type.
Cause: An error occurred while trying to obtain database column type.
Action: Contact Oracle Support.
KUP-03011: OCI error getting database column size.
Cause: An error occurred while trying to obtain database column size.
Action: Contact Oracle Support.
KUP-03012: OCI error getting database column precision.
Cause: An error occurred while trying to obtain database column precision.
Action: Contact Oracle Support.
KUP-03013: OCI error getting database column scale.
Cause: An error occurred while trying to obtain database column scale.
Action: Contact Oracle Support.
KUP-03014: OCI error getting datetime fsprecision.
36-4 Oracle Database Error Messages
Cause: An error occurred while trying to obtain a datetime column precision
value."
Action: Contact Oracle Support.
KUP-03015: OCI error getting datetime lfprecision.
Cause: An error occurred while trying to obtain database column precision.
Action: Contact Oracle Support.
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-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-03018: invalid date mask "string" specified for column string
Cause: The date mask for the specified column is invalid.
Action: None
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-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-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-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-03023: string for TERMINATED BY or ENCLOSED BY clause for record is
longer than maximum number
Cause: The string value for a TERMINATED BY or ENCLOSED BY clause is
longer than the maximum number of bytes allowed. If the character set of the data
file is different than the character set of the database, the string will be converted
to the character set of the data file. If the length of the converted string is too large,
then this error will also be returned.
Action: Use shorter delimiters in the data file and the access parameters.
KUP-03024: string for TERMINATED BY or ENCLOSED BY clause for column
string is longer than maximum number
KUP-00552 to KUP-11024 36-5
Cause: The string value for a TERMINATED BY or ENCLOSED BY clause for the
columns is longer than the maximum number of bytes allowed. If the character set
of the data file is different than the character set of the database, the string will be
converted to the character set of the data file. If the length of the converted string
is too large, then this error will also be returned.
Action: Use shorter delimiters in the data file and the access parameters.
KUP-03025: For CSV format files, field string is not delimited.
Cause: The comma-delimited value (CSV) format files did not have all delimited
fields. CSV format files must have all delimited fields so that the access driver can
process the fields.
Action: Make all of the fields delimited or remove the CSV specification and retry.
KUP-03026: For FIELD NAMES, field string is not delimited.
Cause: The data files with a FIELD NAMES record did not have all delimited
fields. Data files with a FIELD NAMES record must have all delimited fields so
that the access driver can process the field names.
Action: Make all of the fields delimited and retry.
KUP-03027: NULLIF at field level not allowed with NO NULLIF for field string.
Cause: The field had both NULLIF and NO NULLIF specified. You must specify
one or the other.
Action: Remove one of the specifications and retry.
KUP-03028: Field name string in field list does not match the name of any table
column.
Cause: The ALL FIELDS OVERRIDE THESE clause was specified and there was a
field name in the field list in the access parameters that did not match the name of
a column in the table definition. Only names that match the name of columns in
the table may be specified in the field list.
Action: Verify that the correct names are used for the columns in the table and for
the fields in the field list.
KUP-03029: Invalid value specified for parameter string.
Cause: The access parameter contained an invalid value for the parameter
specified in the error message.
Action: Update the access parameters to have a valid value.
KUP-03995: LOCAL TIME ZONE not allowed with DATE_FORMAT TIME
Cause: LOCAL can only be specified with TIMESTAMP, not with TIME.
Action: Remove LOCAL or change TIME to TIMESTAMP and try the operation
again.
KUP-03996: multiple DATE_FORMAT string masks specified at table level for table
string
Cause: Multiple date format masks were specified for the listed datetime or
interval data type at the table level for the listed table.
Action: Remove one of the datetime mask specifications and try the operation
again.
KUP-03997: invalid DATE_FORMAT string mask ("string") specified for table string
Cause: The date format mask for listed datetime type for the specified table was
invalid.
36-6 Oracle Database Error Messages
Action: Fix the mask and try the operation again.
KUP-03998: error number formatting KUP message number
Cause: error occured while attempting to format a KUP message.
Action: contact Oracle support.
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-04000: error initializing I/O state for file string
Cause: An unexpected error occurred while preparing the file.
Action: Contact Oracle Support Services.
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-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-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-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-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-04018: partial record at end of file string
Cause: An incomplete record was found at the end of the file.
Action: Verify the file is not corrupt or missing data.
KUP-04019: illegal length found for VAR record in file string
Cause: A record in a VAR file has an length field with either no numeric
characters in it or with non numeric characters in it.
Action: Verify the records in the file have the correct length specified for them.
KUP-04020: found record longer than buffer size supported, number, in string
(offset=number)
KUP-00552 to KUP-11024 36-7
Cause: a record in the data source was longer than the maximum data size
supported. The number reported is the maximum supported size of a record.
Action: None
KUP-04021: field formatting error for field string
Cause: There was an error trying to find the contents of the specified field in a
record.
Action: This message should be followed by another message containing more
specific information about the cause of the error.
KUP-04022: field start is before start of record
Cause: The position of the start of a field is before the start of a record. This can
occur if a negative number is used to indicate the relative start of a field.
Action: Verify that the definition of the layout of fields in the data file is correct.
KUP-04023: field start is after end of record
Cause: This can happen when specifying either absolute or relative positioning
for a field.
Action: Verify that the definition of the layout of fields in the data file is correct. If
it is valid for fields at the end of the record to be missing, use the MISSING FIELD
VALUES ARE NULL clause in the access parameters.
KUP-04024: field end is before field start
Cause: The end of the field comes after the start of the field. This can happen if
the field is defined with a relative start position and an absolute end position.
Action: Verify that the definition of the layout of fields in the data file is correct.
KUP-04025: field extends beyond end of record
Cause: This can happen when specifying either absolute or relative positioning
for a field.
Action: Verify that the definition of the layout of fields in the data file is correct.
KUP-04026: field too long for datatype
Cause: The character field in the record is larger than the maximum length
specified.
Action: Make sure the definition of the layout of the fields in the data file is
correct. Also make sure the correct maximum size was specified for a character
datatype.
KUP-04027: file name check failed: string
Cause: The check of the filename failed. These checks are platform specific, but
they can include verifying that there are no hard links in the file path, the file is not
a soft link, the file specification includes a parent reference ("../" on Unix), or the
file was modified between the time the check was made and the file was opened.
Action: Use a file location that does not violate any of the checks.
KUP-04028: conversion of character length to a number failed
Cause: The character length portion of the field could not be converted to a
number. This message is followed by another message with information on why
the conversion failed.
Action: Make sure the data is correct. Also verify the datatypes specified for the
fields are correct.
36-8 Oracle Database Error Messages
KUP-04029: numeric field overflowed
Cause: An attempt to convert a character string to number failed because the
value of the number in the string was too large.
Action: None
KUP-04030: invalid numeric data
Cause: An attempt to convert a character string to a number failed because
non-numeric characters were found.
Action: None
KUP-04031: empty filename specified for LOB file in column string
Cause: The field in the data file that was supposed to contain the name of a LOB
file was empty.
Action: Correct the data so that it contains a valid file name.
KUP-04032: internal error string while parsing field string:
Cause: An internal error occurred while parsing a field.
Action: Contact Oracle support.
KUP-04035: beginning enclosing delimiter not found
Cause: The beginning enclosure was not found for a field that is enclosed by
delimiters.
Action: Verify that the data is correct. Also verify that the correct enclosing
delimiters were specified and whether the enclosing delimiter should be optional.
KUP-04037: terminator not found
Cause: The terminator for the field is missing.
Action: Verify that the records are formatted correctly.
KUP-04038: internal error: string
Cause: an unexpected error condition was detected.
Action: contact Oracle customer support
KUP-04039: unexpected error while trying to find file string in string
Cause: An error occurred while trying to find path containing the file.
Action: This message should be followed by another message with more
information about the error.
KUP-04040: file string in string not found
Cause: The file was not found in the directory specified
Action: Verify the correct file and directory names were specified.
KUP-04041: error generating full file name for string in string
Cause: Unexpected error occurred while trying to form a file name.
Action: None
KUP-04043: table column not found in external source: string
Cause: A column in the external table was not found in the access parameters that
define the contents of the data source.
Action: Verify that the external table is defined correctly and that the abstract
parameters are also correct.
KUP-00552 to KUP-11024 36-9
KUP-04044: error positioning file string
Cause: An attempt to position a file to an absolute file offset failed.
Action: See messages that follow for more information.
KUP-04045: unexpected OCI status string
Cause: An OCI call returned a status that cannot be handled.
Action: Contact Oracle support.
KUP-04047: error parsing record from external data source
Cause: An error occurred while trying to extract a record from the data source.
Action: Look in the log file for more messages about the error.
KUP-04048: internal error parsing record from external data source
Cause: An unexpected or unhandled error occurred while getting a record from
the data source
Action: Contact Oracle support.
KUP-04049: record number discarded from file string
Cause: Informational message displayed whenever the WHEN clause has been
satisfied. If a DISCARD file has been specified for the operation, the record will be
written to that file.
Action: None
KUP-04050: error while attempting to allocate number bytes of memory
Cause: d by insufficient memory.
Action: Reconnect to the instance and retry the operation.
KUP-04051: error processing column string in row number for datafile string
Cause: an error occurred while trying to convert the data from the data file into
the type of a column in the external table.
Action: See messages that follow for more details.
KUP-04052: error processing column string in a row for datafile string
Cause: an error occurred while trying to convert the data from the data file into
the type of a column in the external table.
Action: See messages that follow for more details.
KUP-04053: record number number
Cause: This message identifies a record number in a file for a record that had an
error. The message preceding this one contains information about the error and the
name of the file.
Action: None
KUP-04054: internal error: invalid bad row number identified for bad column
number
Cause: This is an internal error.
Action: Contact Oracle support.
KUP-04055: column string is both a field in the data file and a column transform
Cause: The specified column was in the list of fields in the data file and in the list
of column transforms. The column should be in one list or the other, but not both.
36-10 Oracle Database Error Messages
Action: Determine whether the value for the field in the data file or the value for
the field in the column transform should be loaded in to the table. If the value for
the data file is to be loaded, then remove the column transform. If the value for the
column transform is to be loaded, then rename the field in the data file so that it
does not match the name of a field in the table.
KUP-04056: internal error: OCI error while fetching record: number
Cause: An OCI error occurred while processing the granule.
Action: Contact Oracle support.
KUP-04057: internal error: OCI error while fetching record.
Cause: An OCI error occurred while processing the granule.
Action: Contact Oracle support.
KUP-04058: unrecoverable error occurred, operation aborted.
Cause: An unrecoverable error occurred during processing.
Action: See preceding error messages for more information.
KUP-04059: found EOF in length portion of VARIABLE record in file string
Cause: The record parser was looking for the size portion of a file a record format
of VARIABLE. It found EOF before finding all the bytes for the length.
Action: Correct the corruption in the file.
KUP-04060: field string referenced by lobfile column string not found
Cause: The LOBFILE transform for the named column referenced a field for either
the directory object portion or the name portion of the LOBFILE. However, that
field did not exist anywhere in the definition of the data file.
Action: Verify that the LOBFILE clause is specified correctly. Also verify that the
field definitions for the data file are correct.
KUP-04061: directory object string specified for LOBFILE column string is not valid
Cause: The column being loaded from a LOBFILE specified the directory object
containing the LOBFILE through another field in the data file. In this case, the
LOBFILE clause in the access parameters must specify a list of all directory objects
that will be used for this field. This error occurs because a field contains the name
of a directory object that is not in this list.
Action: Verify that the data file contains the correct directory object and verify
that the list of valid directory objects in the LOBFILE clause for this column is
complete.
KUP-04062: no data source specified
Cause: No location for the data source of the external table was specified when
the external table was created. An empty string is not valid.
Action: Specify the name of the data source in the LOCATION clause when
creating an external table.
KUP-04063: unable to open log file string OS error string
Cause: An attempt to open the log file failed.
Action: Specify a different log file or use NO LOGFILE to disable logging.
KUP-04064: fatal error during initialization
Cause: An unexpected error occurred while initializing access to an external table.
KUP-00552 to KUP-11024 36-11
Action: Contact Oracle support.
KUP-04065: error processing LOBFILE for field string
Cause: An error occured while opening or reading a LOBFILE for a column in a
row.
Action: See message in log file for more information about the error.
KUP-04066: error initializing access to external table source
Cause: An error occurred while attempting to retrieve information about a data
source.
Action: See messages preceding this one for more information about the error.
KUP-04067: internal error allocating handle type string
Cause: An attempt to create an internal object failed.
Action: Contact Oracle support.
KUP-04068: internal error fetching attribute string
Cause: An attempt to fetch information about an internal object failed.
Action: Contact Oracle support.
KUP-04069: error fetching data for external table
Cause: An error occurred while atempting to fetch data from an external table.
Action: See messages the precede this one for more information.
KUP-04070: field string referenced by column transform string not found
Cause: The column transform for the named column references a field that did
not exist anywhere in the definition of the data file.
Action: Verify that the column transform clause is specified correctly. Also verify
that the field definitions for the data file are correct.
KUP-04071: record discarded from file string
Cause: Informational message displayed whenever the WHEN clause has been
satisfied. If a DISCARD file has been specified for the operation, the record will be
written to that file. The record number in the source data file is not known because
multiple servers are loading from the file.
Action: None
KUP-04072: error writing to file string
Cause: An error occurred while attempting to write to the named file.
Action: See messages that follow this message for more information about the
error.
KUP-04073: record ignored because all referenced fields are null for a record
Cause: A record was rejected because all fields in the data file referenced by the
query were NULL.
Action: None
KUP-04074: no write access to directory object string
Cause: The user does not have write access to the directory object used for a log,
bad or reject file.
Action: None
36-12 Oracle Database Error Messages
KUP-04075: no read access to directory object string
Cause: The user does not have read access to the directory object used for a data
file.
Action: None
KUP-04076: file name cannot contain a path specification: string
Cause: The name of a data file, log file, bad file or reject file contains a path
specification.
Action: Use the name of a directory object to indicate where the file should be
stored.
KUP-04077: unknown format specifier in file name string
Cause: A format specifier is a percent sign followed by a character. The percent
sign and character are replaced by a value depending on the character. This error
occurs when the character following the percent sign is not defined to have a
value.
Action: See the documentation for information on valid format specifiers. If the
file to be opened needs to have a percent sign in its name then use two pecent
signs. They will get replaces by a single percent sign in the resulting file name.
KUP-04078: invalid file name specified: string
Cause: Attempt to parse the file name failed.
Action: Specify a valid file name.
KUP-04079: error fetching list of valid directories
Cause: An attempt to retrieve a list of valid directories that can be used by the
user to open files failed. See messages that follow for more information.
Action: Contact Oracle support. As a workaround try specifing no log file, no
discard files and no bad files.
KUP-04080: directory object string not found
Cause: The directory object specified for an input file or a log, bad or discard file
does not exist in the database or the user has no privileges to access this directory.
Action: None
KUP-04081: field string used in concatenation for column string is not a character
type
Cause: The specified field was part of a concatenation of strings used to create the
value for the names column. However, the field was not of a character datatype.
Only character fields may be used as part of concatenating fields.
Action: Verify the correct field was used in the CONCAT clause. Also verify that
the correct datatype is specified for the field in the field list.
KUP-04082: error converting field string for LOBFILE column string
Cause: The LOBFILE column had either its directory object name or filename
specified by a field in the data file and that field needed to be converted to the
server's character set before it could be used. This message indicates that an
attempt to convert the field failed.
Action: Verify that the data file has the correct value for the fields. Also verify that
the correct character set was specified for the data file.
KUP-04083: no directory object specified in LOBFILE clause for column string
KUP-00552 to KUP-11024 36-13
Cause: There was no directory object specified for the LOB files used to populate
the named column and no default directory was specified for the external table.
Action: Either specify a directory name, or the name of a data field containing the
name of the directory object that contains the files.
KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID
column.
Cause: A query of an external table of type ORACLE_DATAPUMP tried to
reference the ROWID column. The ORACLE_DATAPUMP access driver does not
support ROWIDs.
Action: Remove the ROWID from the query. If that is not possible, create a table
in the database with the same columns as the external table, copy the data from
the external table into the newly created table, and use that new table for the
query.
KUP-04085: duplicate directory object string and file string specified for unload
Cause: A CREATE TABLE AS SELECT statement was executed for an external
table of type ORACLE_DATAPUMP and the same directory object and filename
combination was specified multiple times.
Action: Issue the CREATE TABLE AS SELECT command again but make sure the
combination of directory objects and filenames is unique.
KUP-04086: length of file name exceeds platform maximum of number
Cause: The length of a filename is longer than the maximum length supported by
Oracle on the server platform.
Action: Verify that the name is correct. If so, use a shorter file name.
KUP-04087: no execute access to directory object string
Cause: Execute access to the directory object used for a preprocessor file was not
granted.
Action: Grant execute privilege on the directory object or specify a different
directory which already has execute privilege enabled.
KUP-04088: data sampling is not supported by this access driver
Cause: A query of an external table requested a sample of the data returned. The
access driver for the external table does not support sampling.
Action: Do not try to use sampling for this external table.
KUP-04089: column transform string is not the name of a table column
Cause: The specified column was in the list of column transforms but a column by
that name does not exist in the table
Action: Verify that the correct name was specified in the column transform.
KUP-04090: big endian byte order mark found when little endian expected in string
Cause: A big endian byte order mark was found at the beginning of the specified
file and either the access parameters specified the data was in little endian order or
the byte order mark for a previous file was little endian.
Action: The file needs to be loaded separately. If a byte order was specified in the
access parameters, make sure it is changed to be big endian.
KUP-04091: little endian byte order mark found when big endian expected in string
36-14 Oracle Database Error Messages
Cause: A little endian byte order mark was found at the beginning of the specified
file and either the access parameters specified the data was in big endian order or
the byte order mark for a previous file was big endian.
Action: The file needs to be loaded separately. If a byte order was specified in the
access parameters, make sure it is changed to be little endian.
KUP-04092: attempt to audit directory object string returned internal error number
Cause: An error occurred while attempting to enable auditing for the specified
directory object.
Action: Contact Oracle Support Services.
KUP-04093: error processing the FIELD NAMES record in data file string
Cause: An error occurred while processing the FIELD NAMES record for the data
file.
Action: See the messages that preceed this one for more details. Fix the error and
retry the operation.
KUP-04094: preprocessing cannot be performed if Database Vault is installed
Cause: The Database Vault option did not permit the execution a program from
an Oracle directory object.
Action: If preprocessing must be performed, then the Database Vault option must
not be installed.
KUP-04095: preprocessor command string encountered error "string"
Cause: The specified preprocessor command encountered an error during
execution.
Action: Verify that the preprocessor command along with any arguments are
correct.
KUP-04096: Warning: lobfile column transform ignored with PREPROCESSOR
option.
Cause: The specified column was in the list of lobfile column transforms but the
PREPROCESSOR option was also specfied. The PREPROCESSOR option does not
work in conjuction with lobfile column transforms.
Action: Do not use column transforms with the PREPROCESSOR option.
KUP-04097: RECORDS clause specified without a record format
Cause: The RECORDS clause was part of the external table access parameters but
no record format type was provided.
Action: If the RECORDS clause is used, then it must be followed by one of the
VARIABLE, FIXED, or DELIMITED BY clauses.
KUP-04098: empty field name for field number in the FIELD NAMES record in data
file
Cause: The field name for the listed field number in the FIELD NAMES record
was empty.
Action: Specify a valid field name in the data file and retry the operation.
KUP-04099: Missing one or more field names in the FIELD NAMES record in the
data file. Found number fields, there should be number fields.
Cause: One or more field names was not listed in the FIELD NAMES record.
However, it was listed in the access parameter list for the external table.
KUP-00552 to KUP-11024 36-15
Action: Include all field names in the data file and retry the operation.
KUP-04100: record rejected in file string
Cause: A record in the data file was not loaded into the table because of an error
while finding fields in the record. See the previous error for more information. The
record will be written to the BAD file, if one is being used. The record number in
the source data file is not known because multiple servers are loading from the
file.
Action: None
KUP-04101: record number rejected in file string
Cause: A record in the data file was not loaded into the table because of an error
while finding fields in the record. See the previous error for more information. The
record will be written to the BAD file, if one is being used.
Action: None
KUP-04102: record number discarded from file string
Cause: Informational message displayed whenever the WHEN clause has been
satisfied. If a DISCARD file has been specified for the operation, the record will be
written to that file.
Action: None
KUP-04103: error converting zoned decimal field to number for string
Cause: An error occurred converting a zoned decimal number to an Oracle
number.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04104: zoned decimal field has bad values for string
Cause: A zoned decimal number has an invalid format.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04105: zoned decimal to number conversion caused overflow for string
Cause: A zoned decimal number could not be converted to an Oracle number
because the number is too big for an oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04106: precision for zoned decimal number is too large for string
Cause: The precision of a zoned decimal number is larger than the precision that
can be stored in an Oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04107: substring of field string for column string is not a character type
Cause: A substring was specified for a field that which is not a character datatype.
Only character fields may be used when specifying the substring transform.
Action: Verify the correct field was used in the STARTOF clause. Also verify that
the correct datatype is specified for the field in the field list.
KUP-04108: unable to reread file string
Cause: The query that is executing requires that a data source for an external table
be read multiple times. However, the data source is a sequential device that cannot
be reread. Examples of this type of data source is a tape or pipe.
36-16 Oracle Database Error Messages
Action: There are a few ways around this problem. One is to rewrite the query so
that the external table is referenced only once. Another option is to move the data
source to a rereadable device such as a disk file. A third option is to load the data
for the external table into a temporary table and change the query to reference the
temporary table.
KUP-04109: specified path for directory object "string" is invalid
Cause: The default directory or a directory object specified for an input data file
or an output dump, log, bad or discard file contains an invalid path name.
Action: Specify a valid path name for the directory object.
KUP-04116: Field name stringstringstring in the FIELD NAMES record in the data
file is too long.
Cause: The field name exceeded the maximum of 30 characters.
Action: Specify at most 30 characters.
KUP-04117: Field name stringstringstring was not found in the access parameter
field list or table.
Cause: The listed field name in the FIELD NAMES record of the data file was not
found in the access parameter field list or in the table columns. The next error
message, if any, lists the name of the data file where the error was found.
Action: Verify that the field name in the FIELD NAMES record is correct. If that is
correct, verify that the external table is defined correctly and that the access
parameter field list is also correct.
KUP-04118: operation "string", location "string"
Cause: This message provides information about the previous messages.
Action: Refer to the help for the previous message for more information.
KUP-04119: Error number opening directory for wild card search: string
Cause: An error occured while trying to open a directory to look for files that
match a wild card specification.
Action: See messages that follow for more details.
KUP-04120: Error number fetching count of files for wild card search in directory
string
Cause: An error occured while trying to retrieve the count of files matching a wild
card specification in the directory
Action: See messages that follow for more details.
KUP-04121: Error number fetching file names for wild card search in directory string
Cause: An error occured while trying to retrieve the names of files matching a
wild card specification in the directory
Action: See messages that follow for more details.
KUP-04122: Error number finishing wild card search in directory string
Cause: An error occured while trying to finish a search for files that match a wild
card specification the directory. matching a wild card specification in the directory
Action: See messages that follow for more details.
KUP-05001: Shift based character sets not supported with CSV format files
Cause: CSV is being used with a shift based chararcter set.
KUP-00552 to KUP-11024 36-17
Action: Either use a non-shift based cahracter set or do not use CSV format files.
KUP-05002: There are no matching files for any file specification in the LOCATION
clause.
Cause: One or more file specifications including wild cards were specified in the
LOCATION clause, but none of the files matched any of the specifications.
Action: Check to make sure that the file specifications are correct and that one or
more files match the file specifications and then try the operation again.
KUP-05003: Warning: There are no matching files for this specification.
Cause: No matching files were found for the LOCATION clause specification
listed in the previous error message.
Action: No action is required. However, if you expected the LOCATION clause
specification to match one or more files, check the specification and the files in the
directory to make sure that they are correct. If needed, try the operation again.
KUP-05004: Warning: Intra source concurrency disabled because parallel select was
not requested.
Cause: Intra source concurrency can only be used when parallel select has been
requested.
Action: No action is required this message is informational.
KUP-05005: Warning: Intra source concurrency disabled because a field of type
RECNUM exists.
Cause: Intra source concurrency cannot be used with RECNUM fields.
Action: No action is required this message is informational.
KUP-05006: Warning: Intra source concurrency disabled because a complex
terminator string is being used.
Cause: Intra source concurrency cannot be used with terminators where
replicated substrings in the terminator could cause ambiguity during record
parsing.\n\n"
Action: No action is required this message is informational.
KUP-05007: Warning: Intra source concurrency disabled because the preprocessor
option is being used.
Cause: Intra source concurrency cannot be used with the PREPROCESSOR
option.
Action: No action is required this message is informational.
KUP-05008: Warning: Intra source concurrency disabled because the input data is in
DELIMITED record format and the characterset is neither fixed width nor UTF8.
Cause: Intra source concurrency cannot be used with the DELIMITED record
format if the characterset is neither fixed width or UTF8.
Action: No action is required this message is informational.
KUP-05009: Warning: Intra source concurrency disabled because the input data is in
VARIABLE record format.
Cause: Intra source concurrency cannot be used with the VARIABLE record
format.
Action: No action is required this message is informational.
36-18 Oracle Database Error Messages
KUP-05010: Warning: Intra source concurrency disabled because the input data is in
CSV format with embedded record delimiters/terminators.
Cause: Intra source concurrency cannot be used with the CSV record format that
has embedded record delimiters/terminators.
Action: No action is required this message is informational.
KUP-11000: file truncated error
Cause: A truncated file was used for the load operation.
Action: Verify unload operation completed successfully.
KUP-11001: files not from the same unload operation
Cause: Files used for the load operation were not from the same unload
operation.
Action: Verify the files used are from the same unload operation.
KUP-11002: unable to read data chunk string
Cause: A read or seek to this data chunk was not possible. This chunk may not
have existed.
Action: Verify the files used for the load operation are correct.
KUP-11003: bad data encountered while reading from file string
Cause: There was a datatype conversion error while attempting to convert the
data in the data file to match the datatype of a column in the external table. The
message that follows this one displays the name of the column and the start of the
data for the column that could not be converted. The row containing the bad data
is rejected and not included as a row in the external table.
Action: If the row containing the bad data should not be filtered out, then modify
the definition of the external table so that the datatypes of the columns match the
datatypes of the fields in the data file.
KUP-11004: requested version string not supported by ORACLE_DATAPUMP
Cause: This database version (defaulted to COMPATIBLE if not user-specified)
was not supported by ORACLE_DATAPUMP external table access driver. Note:
Database versions before 9.2 were not supported.
Action: Specify a supported version and rerun the operation.
KUP-11005: error seeking in file: string
Cause: An attempt to seek to the specified position in file failed.
Action: Review the error message. Resolve the problem and retry the the
operation. Contact Oracle Support Services if the problem cannot be resolved.
KUP-11006: file truncated error in string
Cause: A truncated or incomplete file was used for the load operation.
Action: Verify unload operation completed successfully.
KUP-11007: conversion error loading table string.string
Cause: A row could not be loaded into the table because there was a conversion
error for one or more columns in a row.
Action: See the message that follows for more information about the row that
could not be loaded. To avoid this error, make sure the definition of the table being
loaded matches the definition of the table being unloaded.
KUP-00552 to KUP-11024 36-19
KUP-11008: conversion error loading table string.string partition string
Cause: A row could not be loaded into the table because there was a conversion
error for one or more columns in a row.
Action: See the message that follows for more information about the row that
could not be loaded. To avoid this error, make sure the definition of the table being
loaded matches the definition of the table being unloaded.
KUP-11009: data for row: string
Cause: A conversion error occurred while loading data into a table. The message
shows values for the field in the row that had the conversion error.
Action: None. This is only an informational message.
KUP-11010: unable to open at least one dump file for fetch
Cause: None of the files in the LOCATION clause can be opened for a fetch on an
external table.
Action: A fetch operation on an external table in SQL mode requires that at least
one file could be opened. Check that the directory object and file names to the
dump files are correct.
KUP-11011: the following file is not valid for this load operation
Cause: This file could not be used for this load operation. See the following
message for more information.
Action: Verify all the files in the LOCATION clause are from the same unload
operation and that the unload was successful.
KUP-11012: file string in string already exists
Cause: The specified file could not be used for this unload because that would
mean overwriting an existing file.
Action: Specify a file that does not currently exist.
KUP-11013: internal number in header in file string is not valid
Cause: The specified file could not be used for this operation because the internal
number in the header was not valid.
Action: If the dump files were transferred over, verify the transfer operation was
done correctly.
KUP-11014: internal metadata in file string is not valid
Cause: The specified file could not be used for this operation because the internal
metadata stored in this file does not match the metadata stored in the first file
piece set.
Action: Verify all the files in the LOCATION clause are the correct dump files to
use.
KUP-11015: error in unloading or loading data
Cause: An error has occurred in a stream unload or load operation.
Action: Contact Oracle Support Services.
KUP-11016: database version in file string is not valid
Cause: The specified file could not be used for this fetch because its database
version was not compatible with the database version in the other files in the
LOCATION clause.
36-20 Oracle Database Error Messages
Action: Verify all the files in the LOCATION clause were populated with
compatible database versions.
KUP-11017: file string not found
Cause: The file was not found.
Action: Verify the correct file (path and file name) was specified.
KUP-11018: file string not a valid dump file
Cause: This file did not have the correct file format. It could not be used for an
external table fetch operation.
Action: Verify this file is from a SQL mode external table populate operation and
that the operation was successful.
KUP-11019: the following file is not valid for this fetch operation
Cause: A file could not be used for this fetch. See the following message for more
information.
Action: Verify all the files in the LOCATION clause are from successful populate
operations. If the files were generated from various populate operations, then
verify that those were done with common attributes such as with the same tables
and compatible database versions.
KUP-11020: header in file string may not contain correct information
Cause: The header may be corrupted.
Action: Contact Oracle Support Servicess.
KUP-11021: header in file string has an incompatible version number
Cause: A dump file was specified for a load operation whose version number is
incompatible with the dump file version currently produced by the Oracle server
on the system. Usually this message indicates that the dump file was produced by
a newer version of the Oracle server.
Action: Load this dump file using the same version of the Oracle server that
created the file.
KUP-11022: specified file name "string" is invalid
Cause: The file name specified for a dump or log file was invalid or null.
Action: Specify a valid file name for the dump or log file.
KUP-11023: specified path for directory object "string" is invalid
Cause: The default directory or a directory object specified for a dump or log file
contained an invalid path name or was null.
Action: Specify a valid path name for the directory object.
KUP-11024: This external table can only be accessed from within a Data Pump job.
Cause: An attempt was made to access a temporary external table that was
created by Data Pump to be used internally during the execution of an export or
import job.
Action: None


UDE-00001 to UDE-00054 7 3
UDE-00001: user requested cancel of current operation
Cause: User has requested a cancellation of current job.
Action: No action is needed.
UDE-00002: invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
UDE-00003: all allowable logon attempts failed
Cause: Attempts were repeatedly made to log on with an invalid username or
password.
Action: Shut down the utility, then restart and retry with a valid username and
password.
UDE-00004: operation generated ORACLE error number
Cause: The operation unexpectedly produced the specified error. Refer to the
description of that error for more information.
Action: s.
UDE-00005: unexpected End-Of-File encountered while reading input
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to export is being redirected, check the file for errors.
UDE-00006: failed to allocate memory of size number
Cause: Unable to allocate the necessary memory.
Action: Record the messages that follow and report this to Oracle Customer
Support as an Export internal bug.
UDE-00007: attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Worldwide Support
UDE-00010: multiple job modes requested, string and string.
Cause: Multiple job modes were specified.
Action: Specify only one valid mode, then retry.
UDE-00011: parameter string is incompatible with parameter string
Cause: An invalid combination of parameters was specified.
37-2 Oracle Database Error Messages
Action: Refer to documentation for the set of valid modes, then retry.
UDE-00012: table mode exports only allow objects from one schema
Cause: Multiple schemas were selected for export.
Action: Retry export specifying only one schema.
UDE-00013: internal expdp error.
Cause: Fatal internal Data Pump client error.
Action: Contact Oracle Customer Support
UDE-00014: invalid value for parameter, 'string'.
Cause: Could not parse the specified parameter or parameter value.
Action: Refer to documentation for valid parameter values.
UDE-00015: invalid context or job state for parameter, 'string'.
Cause: Invalid job state or context for specified parameter.
Action: Refer to documentation for correct parameter usage.
UDE-00016: 'string' parameter requires a value.
Cause: Parameter was specified without a value.
Action: Refer to documentation for correct parameter usage.
UDE-00017: Data Pump job is already executing.
Cause: Incorrect Data Pump job state for requested operation.
Action: Refer to documentation for correct usage.
UDE-00018: Data Pump client is incompatible with database version string
Cause: The Export utility is at a higher version than the database version and is
thereby incompatible.
Action: Use the same version of Export utility as the database.
UDE-00019: 'string' parameter list is too long.
Cause: Requested parameter list exceeds 4000 character maximum.
Action: Reduce the specified number of parameter values and rerun.
UDE-00020: Data Pump client is incompatible with Data Pump API.
Cause: The Export utility is at a higher version than the Data Pump server and is
thereby incompatible.
Action: Use the same version of Export utility as the server.
UDE-00050: Unable to setup parameter processing.
Cause: An unexpected error occurred during parameter manager initialization.
Action: Record the messages that follow and report this to Oracle Customer
Support as an Export internal bug.
UDE-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.
Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'
Action: Record the accompanying messages and report this as an Export internal
error to Oracle customer support.
UDE-00052: incorrect Data Pump client for operation: string
Cause: Export client attempted to attach to import job.
UDE-00001 to UDE-00054 37-3
Action: Use appropriate client when attaching to an existing job
UDE-00053: unrecognized client command 'string'
Cause: Invalid interactive client command.
Action: Refer to documentation for valid client commands.
UDE-00054: Deprecated Legacy Mode parameter 'string' specified at or on: string
Cause: The Legacy Mode parameter specified has no corresponding Data Pump
mapping.
Action: Review the location referred to in the error message ( (either 'Command
Line', 'Parameter File', or 'Environment Variable') and remove the parameter.
37-4 Oracle Database Error Messages


UDI-00001 to UDI-00054 8 3
UDI-00001: user requested cancel of current operation
Cause: User has requested a cancellation of current job.
Action: No action is needed.
UDI-00002: invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
UDI-00003: all allowable logon attempts failed
Cause: Attempts were repeatedly made to log on with an invalid username or
password.
Action: Shut down the utility, then restart and retry with a valid username and
password.
UDI-00004: operation generated ORACLE error number
Cause: The operation unexpectedly produced the specified error. Refer to the
description of that error for more information.
Action: s.
UDI-00005: unexpected End-Of-File encountered while reading input.
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to import is being redirected, check the file for errors.
UDI-00006: failed to allocate memory of size number
Cause: Unable to allocate the necessary memory.
Action: Record the messages that follow and report this to Oracle Customer
Support as an Import internal bug.
UDI-00007: attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Customer Support
UDI-00010: multiple job modes requested, string and string.
Cause: Invalid job mode was specified.
Action: Specify only one valid mode, then retry.
UDI-00011: parameter string is incompatible with parameter string
Cause: An invalid combination of parameters was specified.
38-2 Oracle Database Error Messages
Action: Refer to documentation for the set of valid modes, then retry.
UDI-00012: table mode imports only allow objects from one schema
Cause: Multiple schemas were selected for import.
Action: Retry import specifying only one schema.
UDI-00013: internal impdp error.
Cause: Fatal internal Data Pump client error.
Action: Contact Oracle Customer Support.
UDI-00014: invalid value for parameter, 'string'
Cause: Could not parse the specified parameter or parameter value.
Action: Refer to documentation for valid parameter values.
UDI-00015: invalid context or job state for parameter, 'string'.
Cause: Invalid job state or context for specified parameter.
Action: Refer to documentation for correct parameter usage.
UDI-00016: 'string' parameter requires a value.
Cause: Parameter was specified without a value.
Action: Refer to documentation for correct parameter usage.
UDI-00017: Data Pump job is already executing.
Cause: Incorrect Data Pump job state for requested operation.
Action: Refer to documentation for correct usage.
UDI-00018: Data Pump client is incompatible with database version string
Cause: The Import utility is at a higher version than the database version and is
thereby incompatible.
Action: Use the same version of Import utility as the database.
UDI-00019: 'string' parameter list is too long.
Cause: Requested parameter list exceeds 4000 character maximum.
Action: Reduce the specified number of parameter values and rerun.
UDI-00020: Data Pump client is incompatible with Data Pump API.
Cause: The Export utility is at a higher version than the Data Pump server and is
thereby incompatible.
Action: Use the same version of Export utility as the server.
UDI-00050: unable to setup parameter processing.
Cause: An unexpected error occurred during parameter manager initialization.
Action: Record the messages that follow and report this to Oracle Customer
Support as an Import internal bug.
UDI-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.
Cause: Import was unable to set NLS_NUMERIC_CHARACTERS to '.,'
Action: Record the accompanying messages and report this as an Import internal
error to Oracle Customer Support.
UDI-00052: incorrect Data Pump client for operation: string
Cause: Import client attempted to attach to export job.
UDI-00001 to UDI-00054 38-3
Action: Use appropriate client when attaching to an existing job
UDI-00053: unrecognized client command 'string'
Cause: Invalid interactive client command.
Action: Refer to documentation for valid client commands.
UDI-00054: Deprecated Legacy Mode parameter 'string' specified at or on: string
Cause: The Legacy Mode parameter specified has no corresponding Data Pump
mapping.
Action: Review the location referred to in the error message ( (either 'Command
Line', 'Parameter File', or 'Environment Variable') and remove the parameter.
38-4 Oracle Database Error Messages


DBV-00200 to DBV-00201 9 3
DBV-00200: Block, DBA number, already marked corrupt
Cause: The block was previously corrupted. It has been marked as corrupt by the
Oracle database server.
Action: If the block is not currently allocated to a database object, then no action is
required. If the block is allocated, then the options and required action depend on
the type and nature of the object which owns the block. To repair an allocated
block, perform block or file media recovery.
DBV-00201: Block, DBA number, marked corrupt for invalid redo application
Cause: The block was marked corrupt by the Oracle database server for invalid
redo application, ex: media recovery of a NOLOGGING object or direct loaded
data.
Action: If the block is not currently allocated to a database object, then no action is
required. If the block is allocated, then the object will need to be rebuilt, or data to
be reloaded.
39-2 Oracle Database Error Messages
40
NID-00001 to NID-00604 40-1
NID-00001 to NID-00604 0 4
NID-00001: Illegal command line syntax - parse error = (number)
Cause: Illegal operand on command line.
Action: Remove illegal operand.
NID-00002: Parse error: string
Cause: An error was encountered while parsing the command line.
Action: Remove offending operand.
NID-00010: Password:
Cause: Password was not specified in command line.
Action: Type password at this prompt.
NID-00100: Cannot open datafile "string"
Cause: The specified datafile could not be opened.
Action: Ensure that the specified datafile exists and is writable.
NID-00101: LOGFILE (string) not accessible
Cause: The specified log file could not be opened.
Action: Specify a log file that is writable.
NID-00102: Garbled target string
Cause: The supplied connect string could not be parsed. The connect string does
not have the correct format.
Action: Refer to Oracle9i Database Concepts.
NID-00103: Missing password in connect string "string"
Cause: Could not find the password in the supplied connect string. The connect
string does not have the correct format.
Action: Refer to Oracle9i Database Concepts.
NID-00104: Need to specify TARGET connection parameter in command line
Cause: The mandatory parameter TARGET was not specified.
Action: Specify TARGET=<username>/<password> when invoking this utility.
NID-00105: Need to specify "LOGFILE=<logfile>" when using APPEND=YES
option
Cause: The APPEND parameter was specified without a LOGFILE.
Action: Specify APPEND=YES only when LOGFILE is also specified.
40-2 Oracle Database Error Messages
NID-00106: LOGIN to target database failed with Oracle error: string
Cause: An Oracle error was reported while attempting to log in to the target
database.
Action: Follow the actions for the specified Oracle error.
NID-00107: File I/O error on datafile "string" during string operation
(number/string)
Cause: An operating system error was reported while performing the specified
operation in the specified file.
Action: Verify the datafile and check for operating system errors.
NID-00109: DBNAME string length number exceeds maximum length of number
Cause: The specified new database name exceeded the maximum size.
Action: Specify a shorter, valid name.
NID-00110: Cannot use REVERT and specify a database name at the same time
Cause: Conflicting options were specified in the command line.
Action: Choose only one of the options.
NID-00111: Oracle error reported from target database while executing string string
Cause: An Oracle error was reported when executing an OCI operation.
Action: Follow the actions for the specified Oracle error.
NID-00112: unsupported connection mode
Cause: A mode different than SYSDBA or SYSBACKUP was specified for the
connection to the target.
Action: Specify only AS SYSDBA or AS SYSBACKUP.
NID-00113: Error reading answer - aborting
Cause: Response caused an error.
Action: Retry the operation.
NID-00114: Must specify new database name when SETNAME is used
Cause: SETNAME=YES was specified but no DBNAME was provided.
Action: Specify DBNAME or remove the SETNAME=YES option.
NID-00115: Database should be mounted
Cause: The database was not mounted.
Action: Mount the database.
NID-00120: Database should be mounted exclusively
Cause: The database was started in parallel mode. To change the DBID, the
database must be mounted exclusively.
Action: Shut down the database and start it in exclusive mode.
NID-00121: Database should not be open
Cause: The database was open. To change the DBID, the database must be
mounted exclusively.
Action: Shutdown the database and mount it in exclusive mode.
NID-00122: Database should have no offline immediate datafiles
NID-00001 to NID-00604 40-3
Cause: The database has one or more datafiles that are in OFFLINE IMMEDIATE
mode.
Action: Drop the datafiles or recover them and bring them online.
NID-00123: Magic number for datafile "string" is incorrect
Cause: Block 0 header has an incorrect magic number for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
NID-00124: Mismatched dbid for datafile string, expected number, found number
Cause: The dbid of the datafile does not match the 'old' DBID or the 'new' DBID.
Action: Verify that this datafile belongs to the database. You may need to restore a
backup of the datafile.
NID-00125: Database should have no disabled datafiles
Cause: The database has one or more datafiles that are disabled.
Action: Drop the datafiles or recover them and bring them online.
NID-00126: Database should have no datafiles in unknown state
Cause: The database has one or more datafiles that are in an unknown state.
Action: Drop the datafiles or recover them and bring them online.
NID-00127: All online files in the database must have the same checkpoint SCN
Cause: The database has one or more datafiles that have a checkpoint SCN that
does not match the database checkpoint SCN.
Action: Restart the database and shut it down cleanly, then retry the operation.
NID-00128: Cannot revert change of database, change not in progress
Cause: The REVERT option was used, but the control file does not show that a
change of DBID was in progress.
Action: Do not use the REVERT option, or possibly restore the control file that
was in place when the utility was started.
NID-00129: Invalid DBID for datafile "string", expecting number, found number
Cause: A datafile header shows a different DBID from the rest of the database
files.
Action: Ensure that the file belongs to this database.
NID-00130: Mismatched CHECKPOINT_CHANGE# in datafile "string", expecting
string, found string
Cause: The datafile header does not match information in the control file.
Action: Revert the change, open the database, and verify that all datafiles are
consistent. Then, shut down the database and retry the operation.
NID-00131: Control file is not current
Cause: A non-current control file is currently mounted.
Action: Perform necessary actions to make the control file current and retry.
NID-00132: CHECKPOINT_CHANGE# in datafile "string": string in the future of
controlfile: string
Cause: The checkpoint in the datafile header is ahead of the checkpoint in the
control file.
Action: Make the database consistent and retry.
40-4 Oracle Database Error Messages
NID-00133: Database should have only consistent datafiles
Cause: The database has one or more datafiles that are marked FUZZY in the
control file.
Action: Restart the database and shut down consistently, then retry the operation.
NID-00134: Datafile "string" is not consistent
Cause: The datafile is marked as fuzzy in its header.
Action: Restart the database and shut down cleanly, then retry the operation.
NID-00135: There are number active threads
Cause: is that the database crashed the last time it was shut down.
Action: Ensure that all threads are closed before retrying the operation. Start and
open the database to perform crash recovery, then shut down with the NORMAL
or IMMEDIATE options to close it cleanly. Finally, try running the utility again.
NID-00137: All datafiles that are not dropped should be readable
Cause: The database had one or more files that could not be read.
Action: Restore the missing files and retry the operation.
NID-00138: Block verification failed for datafile string (number)
Cause: Block header checksum yields a nonzero value for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
NID-00139: Mismatched dbname for datafile string, expected string, found string
Cause: The dbname of the datafile does not match the 'old' dbname or the 'new'
dbname.
Action: Verify that this datafile belongs to the database. You may need to restore a
backup of the datafile.
NID-00140: Specified database name string does not match previous name used
string
Cause: This is a continuation of a failed attempt. However in the failed attempt,
the database name is different than the one used in the last attempt.
Action: Retry the command using the original database name.
NID-00141: No database name specified, previous attempt used string
Cause: This is a continuation of a failed attempt. However, in the failed attempt, a
database name was provided.
Action: Retry the command using the original database name.
NID-00142: Only changing database name, previous attempt changed dbid to
number
Cause: This is a continuation of a failed attempt. However, in the failed attempt,
the database id was also being changed.
Action: Retry the command removing SETNAME=YES.
NID-00143: Mismatched controlfile string
Cause: A controlfile did not have the correct status.
Action: Shutdown the database, remove the mismatched controlfile, mount the
database, and retry the operation.
NID-00144: New name for database string is the same as current name string
NID-00001 to NID-00604 40-5
Cause: The specified name is the same as the current name of the database.
Action: Specify a different name or do not use the DBNAME option.
NID-00145: nls subsystem initialization failure for product=string, facility=string
Cause: The NLS product/facility error message file could not be located or
properly initialized.
Action: Check that the error message directory and file(s) have been properly
installed.
NID-00300: Connected to database string (DBID=number)
Cause: Informational message.
Action: No action required.
NID-00301: Datafile string - dbid changed, wrote new name
Cause: Informational message.
Action: No action required.
NID-00302: Datafile string - dbid changed
Cause: Informational message.
Action: No action required.
NID-00303: Datafile string - wrote new name
Cause: Informational message.
Action: No action required.
NID-00304: Datafile string - reverted
Cause: Informational message.
Action: No action required.
NID-00305: Datafile string - already changed
Cause: Informational message.
Action: No action required.
NID-00306: Datafile string - no revert needed
Cause: Informational message.
Action: No action required.
NID-00307: Control File string - dbid changed, wrote new name
Cause: Informational message.
Action: No action required.
NID-00308: Control File string - dbid changed
Cause: Informational message.
Action: No action required.
NID-00309: Control File string - wrote new name
Cause: Informational message.
Action: No action required.
NID-00310: Control File string - reverted
Cause: Informational message.
40-6 Oracle Database Error Messages
Action: No action required.
NID-00311: Control File string - modified
Cause: Informational message.
Action: No action required.
NID-00312: Connected to server version string
Cause: Informational message.
Action: No action required.
NID-00315: Operation already in progress, continuing
Cause: Informational message.
Action: No action required.
NID-00320: Operation cancelled at user request
Cause: Informational message.
Action: No action required.
NID-00321: Proceeding with operation
Cause: Informational message.
Action: No action required.
NID-00330: The following datafiles are offline immediate:
Cause: Informational message.
Action: No action required.
NID-00331: The following datafiles are disabled:
Cause: Informational message.
Action: No action required.
NID-00332: The following datafiles are in unknown state:
Cause: Informational message.
Action: No action required.
NID-00333: Cannot read the header of the following datafiles:
Cause: Informational message.
Action: No action required.
NID-00334: The following datafiles are not checkpointed to string:
Cause: Informational message.
Action: No action required.
NID-00335: The following datafiles are not consistent:
Cause: Informational message.
Action: No action required.
NID-00336: The following datafiles are offline clean:
Cause: Informational message.
Action: No action required.
NID-00337: The following datafiles are read-only:
NID-00001 to NID-00604 40-7
Cause: Informational message.
Action: No action required.
NID-00338: Control Files in database:
Cause: Informational message.
Action: No action required.
NID-00350: string (number) string
Cause: Informational message.
Action: No action required.
NID-00351: string (number)
Cause: Informational message.
Action: No action required.
NID-00352: string (number), error: number
Cause: Informational message.
Action: No action required.
NID-00353: string
Cause: Informational message.
Action: No action required.
NID-00354: Instance shut down
Cause: Informational message.
Action: No action required.
NID-00370: Change database ID of database string? (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00371: Change database name of database string to string? (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00372: Change database ID and database name string to string? (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00373: Revert changes for database string (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00390: These files must be writable by this utility.
Cause: Informational message.
Action: No action required.
NID-00395: Reverting database name from string to string
Cause: Informational message.
Action: No action required.
40-8 Oracle Database Error Messages
NID-00396: Reverting database ID from number to number
Cause: Informational message.
Action: No action required.
NID-00397: Changing database name from string to string
Cause: Informational message.
Action: No action required.
NID-00398: Changing database ID from number to number
Cause: Informational message.
Action: No action required.
NID-00400: DBNEWID - Completed with errors.
Cause: Informational message.
Action: No action required.
NID-00401: Must finish REVERT changes before attempting any database
operation.
Cause: Informational message.
Action: No action required.
NID-00402: Must finish change or REVERT changes before attempting any
database operation.
Cause: Informational message.
Action: No action required.
NID-00403: DBNEWID - Completed with validation errors.
Cause: Informational message.
Action: No action required.
NID-00404: DBNEWID - Completed succesfully.
Cause: Informational message.
Action: No action required.
NID-00405: Reversion of database name and database ID failed.
Cause: Informational message.
Action: No action required.
NID-00406: Reversion of database name failed.
Cause: Informational message.
Action: No action required.
NID-00407: Reversion of database ID failed.
Cause: Informational message.
Action: No action required.
NID-00410: Reversion of database changes failed during validation - database is
intact.
Cause: Informational message.
Action: No action required.
NID-00001 to NID-00604 40-9
NID-00415: Change of database name and database ID failed.
Cause: Informational message.
Action: No action required.
NID-00416: Change of database name failed.
Cause: Informational message.
Action: No action required.
NID-00417: Change of database ID failed.
Cause: Informational message.
Action: No action required.
NID-00420: Change of database name and ID failed during validation - database is
intact.
Cause: Informational message.
Action: No action required.
NID-00421: Change of database name failed during validation - database is intact.
Cause: Informational message.
Action: No action required.
NID-00422: Change of database ID failed during validation - database is intact.
Cause: Informational message.
Action: No action required.
NID-00425: Database name restored to string.
Cause: Informational message.
Action: No action required.
NID-00426: Database ID for database string restored to number.
Cause: Informational message.
Action: No action required.
NID-00430: Database is ready to be open or shut down.
Cause: Informational message.
Action: No action required.
NID-00431: DBNEWID - Reversion completed.
Cause: Informational message.
Action: No action required.
NID-00435: Database name changed to string.
Cause: Informational message.
Action: No action required.
NID-00436: Modify parameter file and generate a new password file before
restarting.
Cause: Informational message.
Action: No action required.
NID-00440: Database ID for database string changed to number.
40-10 Oracle Database Error Messages
Cause: Informational message.
Action: No action required.
NID-00441: All previous backups and archived redo logs for this database are
unusable.
Cause: Informational message.
Action: No action required.
NID-00442: Database has been shutdown, open database with RESETLOGS option.
Cause: Informational message.
Action: No action required.
NID-00450: Succesfully changed database name and ID.
Cause: Informational message.
Action: No action required.
NID-00451: Succesfully changed database name.
Cause: Informational message.
Action: No action required.
NID-00452: Succesfully changed database ID.
Cause: Informational message.
Action: No action required.
NID-00480: Database is intact - database is ready to be open or shut down.
Cause: Informational message.
Action: No action required.
NID-00481: DBNEWID - Cancelled.
Cause: Informational message.
Action: No action required.
NID-00482: Database is not aware of previous backups and archived logs in
Recovery Area.
Cause: Because the database id was changed, previous backups and archived
redo logs in recovery area are not managed by this database.
Action: This is the informational message only.
NID-00490: LOG being redirected to STDERR due to errors.
Cause: Could no write message to log file.
Action: None
NID-00500: Keyword Description (Default)
Cause: Informational message.
Action: No action required.
NID-00501: ----------------------------------------------------
Cause: Informational message.
Action: No action required.
NID-00502: TARGET Username/Password (NONE)
NID-00001 to NID-00604 40-11
Cause: Informational message.
Action: No action required.
NID-00503: DBNAME New database name (NONE)
Cause: Informational message.
Action: No action required.
NID-00504: LOGFILE Output Log (NONE)
Cause: Informational message.
Action: No action required.
NID-00505: REVERT Revert failed change NO
Cause: Informational message.
Action: No action required.
NID-00506: SETNAME Set a new database name only NO
Cause: Informational message.
Action: No action required.
NID-00507: APPEND Append to output log NO
Cause: Informational message.
Action: No action required.
NID-00508: HELP Displays these messages NO
Cause: Informational message.
Action: No action required.
NID-00600: Internal Error - [number] [number] [number] [number]
Cause: This is the generic internal error number for program exceptions. This
indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
NID-00601: Internal Error - [number] [string] [number] [number]
Cause: This is the generic internal error number for program exceptions. This
indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
NID-00602: Could not allocate number bytes for "string"
Cause: Memory allocation failed.
Action: Free memory at the operating system level and retry operation.
NID-00603: No datafiles found in database
Cause: Controlfile has not datafiles recorded
Action: Report as a bug - the first argument is the internal error number
NID-00604: No control files found in database
Cause: Instance has no control files recorded
Action: Report as a bug - the first argument is the internal error number
40-12 Oracle Database Error Messages
41
DGM-16900 to DGM-17032 41-1
DGM-16900 to DGM-17032 1 4
DGM-16900: Unable to initialize client
Cause: The client could not be initialized.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16901: Unable to initialize environment
Cause: The database environment could not be allocated and initialized.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16902: Unable to allocate handle
Cause: The database handle could not be allocated.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16903: Unable to connect to database using string
Cause: The Data Guard command-line interface (DGMGRL) was unable to
connect to the database using the specified connect identifier.
Action: Check the connect identifier and ensure the instance or host is reachable.
DGM-16904: Unable to set attribute
Cause: The server attributes could not be set.
Action: Check additional error messages.
DGM-16905: Failed.
Cause: The command failed to execute.
Action: Check additional error messages.
DGM-16906: Unable to accept commands: no memory
Cause: No memory was available for the attempted operation.
Action: Check your system and retry the command.
DGM-16909: Fatal error - quitting...
Cause: A fatal error was encountered.
Action: See additional error messages and/or contact Oracle Support Services.
DGM-16910: Unable to issue command to server
Cause: Command could not be issued to the server.
Action: See additional error messages and/or contact Oracle Support Services.
DGM-16912: Unrecognized command "string", try "help"
41-2 Oracle Database Error Messages
Cause: An unrecognized command was issued.
Action: Try again using a valid command.
DGM-16916: Missing site name, try "help"
Cause: The site name is missing from the command.
Action: Try the command again using correct syntax.
DGM-16934: start up instance "string" of database "string"
Cause: The operation completed successfully and requires a restart of the
specified instance. DGMGRL was unable to restart the instance.
Action: Start the specified instance manually.
DGM-16943: connect to instance "string" of database "string"
Cause: The operation required DGMGRL to connect to a specific instance to
complete, but DGMGRL could not automatically connect to the given instance.
Action: Connect to the specified instance and issue the command again.
DGM-16944: Failover succeeded, new primary is "string"
Cause: The failover command completed successfully."
Action: No action is required.
DGM-16945: Syntax error before or at "string"
Cause: The command could not be processed because of a syntax error in the
named token.
Action: Try the command again using valid syntax.
DGM-16948: Unable to switchover, primary database is still "string"
Cause: The switchover operation could not be executed due to the errors reported
with this error message. The primary role has not been changed.
Action: Correct the errors and try the SWITCHOVER command again.
DGM-16949: Object "string" was not found
Cause: The named object was not found.
Action: Try the command again using a valid database name.
DGM-16951: Unable to failover
Cause: The failover operation could not be executed due to the errors reported
with this error message.
Action: Correct the errors and try the FAILOVER command again.
DGM-16952: Configuration details cannot be determined by DGMGRL
Cause: The broker configuration could not be found.
Action: 1) The Data Guard broker process (DMON) could not be contacted. Verify
that the DMON process is running. 2) No broker configuration currently exists.
You must create one. 3) You are connected to a standby database in the broker
configuration that has either been disabled or deleted. While the standby is in this
state, the details of the broker configuration are not available on the standby
database. Connect to the primary database and reissue the command. 4) You are
connected to a database in the broker configuration that must be reinstated or
reinstantiated. While in this state, details of the broker configuration are not
available. Either reinstate or reinstantiate the database and reissue the command,
or connect to the primary database and reissue the command.
DGM-16900 to DGM-17032 41-3
DGM-16953: XML document is too long
Cause: The length of the XML document exceeded the internal limit.
Action: This is an internal error. Contact Oracle Support Services.
DGM-16954: Unable to open and lock the Observer configuration file
Cause: The Observer configuration file cannot be opened or cannot be locked for
exclusive access.
Action: Make sure the Observer has the correct operating system privileges to
write the file and there is no other Observer that is using the same file. Try the
command again.
DGM-16959: No response from broker server process
Cause: No response was received from the broker server process (DMON).
Action: The Data Guard broker process (DMON) is not available. Verify that the
DMON process is running and retry the command.
DGM-16960: Status not available
Cause: The status could not be retrieved.
Action: The Data Guard broker process (DMON) is not available. Verify that the
DMON process is running and retry the command.
DGM-16979: Unable to log on to the primary or standby database as SYSDBA
Cause: The username/password used by the observer to log on to the primary
database and Fast-Start Failover target standby database does not have valid
SYSDBA credentials.
Action: Make sure the primary database and Fast-start failover target database are
using a remote login password file. Make sure the SYSDBA password is the same
at both databases and that the SYSDBA password is used in the CONNECT
command. Start the observer again.
DGM-16991: Two or more resources have the name "string"
Cause: The named resource exists on more than one site.
Action: Use the ON SITE clause and reissue the command.
DGM-16999: Instance "string" was not found
Cause: The named instance could not be found.
Action: Try the command again using a valid instance name.
DGM-17000: Two or more instances have the name "string"
Cause: The named instance exists on more than one database.
Action: Use the ON DATABASE clause and reissue the command.
DGM-17002: Primary database cannot be removed
Cause: The named database to be removed is the primary database.
Action: Remove the broker configuration instead.
DGM-17007: Unsupported platform, observer cannot start
Cause: The Observer was started on an operating system that does not support
multi-threading.
Action: Start the Observer on an operating system that supports multi-threading.
DGM-17009: New primary database "string" is opening...
41-4 Oracle Database Error Messages
Cause: The Data Guard broker is opening the specified new primary database.
The new primary database is ready to accept transactions once it is open.
Action: None
DGM-17016: failed to retrieve status for database "string"
Cause: DGMGRL could not retrieve the StatusReport property from the given
database and thus could not report the database status.
Action: See accompanying messages for details.
DGM-17017: unable to determine configuration status
Cause: The Data Guard broker could not execute a health check at the moment, so
the configuration status could not be determined.
Action: See accompanying messages for details.
DGM-17023: far sync instance "string" was not found
Cause: A far sync instance with the given name was not found in the
configuration.
Action: Try the command again using a valid far sync instance name. If the name
refers to a database, use the corresponding database command syntax instead.
DGM-17025: database "string" was not found
Cause: A database with the given name was not found in the configuration.
Action: Try the command again using a valid database name. If the name refers to
a far sync instance, use the corresponding far sync instance command syntax
instead.
DGM-17027: Recovery Appliance "string" was not found
Cause: A database with the given name was not found in the configuration.
Action: Try the command again using a valid database name. If the name refers to
a far sync instance, use the corresponding far sync instance command syntax
instead.
DGM-17032: Wildcard string not supported for this command
Cause: The wildcard string was specified instead of an object name.
Action: Supply an object name instead of the wildcard string and retry the
command.
42
DIA-48001 to DIA-51705 42-1
DIA-48001 to DIA-51705 2 4
DIA-48001: internal error code, arguments: [string], [string], [string], [string],
[string], [string], [string], [string]
Cause: This is the generic internal error number for program exceptions.This
indicated that a process encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number.
DIA-48002: thread terminated by fatal error
Cause: The thread was in an unrecoverable state.
Action: Examine the thread trace file for more information.
DIA-48003: out of process memory when trying to allocate string bytes
(string,string)
Cause: Operating system process private memory was exhausted.
Action: None
DIA-48004: unable to allocate string bytes of shared memory
("string","string","string","string")
Cause: More shared memory is needed than was allocated in the shared pool.
Action: Reduce your use of shared memory or increase the amount of available
shared memory.
DIA-48007: name is already used by an existing product type
Cause: An attempt was made to define a product type with the same name as an
already defined product type.
Action: Use the already existing product type with the specified name, or use a
different name for the product type.
DIA-48008: id is already used by an existing product type
Cause: An attempt was made to define a product type with the same id as an
already defined product type.
Action: Choose a different name for the product type.
DIA-48100: error encountered when attempting to open a file
Cause: There was an error encountered when attempting to open a file with the
ADR file interface.
Action: Check that the specified directory name, file name, and open options are
valid.
DIA-48101: error encountered when attempting to read a file [string] [string] [string]
42-2 Oracle Database Error Messages
Cause: There was an error encountered when attempting to read a file with the
ADR file interface.
Action: Check the specified arguments to the read interface.
DIA-48102: encountered the end-of-file when reading the file
Cause: The ADR file interface encountered the end-of-file when reading the file.
Action: Handle the end of file condition.
DIA-48103: error encountered when attempting to write a file [string] [string]
[string]
Cause: There was an error encountered when attempting to write a file with the
ADR file interface.
Action: Check the specified arguments to the write interface.
DIA-48104: read mismatch on blocks requested and returned, [string], [string]
Cause: There was a mismatch between the number of blocks requested for
reading and the number of blocks actually returned.
Action: Check the file to make sure there are no partial blocks.
DIA-48105: write mismatch on blocks requested and returned, [string], [string]
Cause: There was a mismatch between the number of blocks requested for writing
and the number of blocks actually written.
Action: Check that there is enough space left on the device to write the requested
number of blocks.
DIA-48106: error initializing the ADR string object
Cause: There was an error encountered during the initialization of one of the ADR
file objects.
Action: Check the validity of the specified directory name and file name.
DIA-48107: invalid Bfile input, [string]
Cause: An invalid Bfile was passed into the routine to convert the bfile into a file
handle.
Action: Verify the contents of the specified Bfile.
DIA-48108: invalid value given for the diagnostic_dest init.ora parameter
Cause: The value given for the diagnostic_dest directory is not a valid directory.
Either the directory does not exist or the process does not have read/write
privileges on the directory.
Action: Use a value for diagnostic_dest that is a valid directory with the proper
read and write privileges.
DIA-48109: invalid lock mode for file descriptor, [string]
Cause: The lock mode associated with the file descriptor was invalid in the
context of the routine.
Action: Verify that a file is not trying to obtain multiple locks and that the file is
holding a lock when attempting to release the lock.
DIA-48110: error encountered while attempting to get a file lock [string] [string]
Cause: There was an error encountered while trying to get a file lock.
Action: Check the state of the file and operating system.
DIA-48001 to DIA-51705 42-3
DIA-48111: error encountered while attempting to release a file lock [string]
Cause: There was an error encountered while trying to release a file lock.
Action: Check the state of the file and operating system.
DIA-48112: invalid flags for open file, string
Cause: Invalid flags were passed in to the open file routine.
Action: Check to see if the flags are a valid combination.
DIA-48113: unable to write to stream file because of out of space condition
Cause: The system is unable to write the requested number of bytes to a stream
file. This is due to an out of space condition. The additional information shows
how many bytes were not written.
Action: Check that there is enough space left on the device to write the requested
number of bytes.
DIA-48114: error encountered when attempting to close a file
Cause: There was an error encountered when attempting to close a file with the
ADR file interface.
Action: Check the validity of the file descriptor.
DIA-48115: error encountered while seeking a file position
Cause: There was an error encountered while seeking a position in a file.
Action: Check that the requested file position falls within the file boundaries.
DIA-48116: error enountered when attempting to create a directory [string]
Cause: There was an error encountered when attempting to create a directory.
Action: Check the directory name.
DIA-48117: error encountered when attempting to remove a directory [string]
Cause: There was an error encountered when attempting to remove a directory.
Action: Check the directory name.
DIA-48118: error encountered with list directory [string]
Cause: There was an error with listing the elements of a directory.
Action: Check the state of the operating system.
DIA-48119: error encountered when attempting to remove a file [string] [string]
Cause: There was an error encountered when attempting to remove a file with the
ADR file interface.
Action: Check the directory name and file name.
DIA-48120: error encountered when attempting to retrieve the file size [strin

再分享一下我老师大神的人工智能教程吧。零基础！通俗易懂！风趣幽默！还带黄段子！希望你也加入到我们人工智能的队伍中来！https://www.cnblogs.com/captainbed