I summarized a list of (ORA) oracle error codes list with cause and
action, use browser find (CTRL+F) to get your desire error code, cause and
possible action.
Oracle
Database Error Messages (ORA-19000 - ORA-23290)
Her are the complete list of ORA error codes link
ORA-19001:
Invalid storage option specified
Cause: An invalid storage option was
specified for the XMLType.
Action: Supply a valid storage option.
ORA-19002:
Missing XMLSchema URL
Cause: A XML schema URL must be
specified in the storage option.
Action: Specify a URL for the
XMLSchema.
ORA-19003:
Missing XML root element name
Cause: A root element in the
XMLSchema must be specified if the XML schema is given.
Action: Specify a root element in the
XML schema.
ORA-19004:
Duplicate XMLType OBJECT RELATIONAL storage option
Cause: A duplicate storage option for
the XMLType column was specified
Action: Specify a single storage
option for an XMLType column
ORA-19005:
Duplicate XMLType LOB storage option
Cause: A duplicate storage option for
the XMLType column was specified
Action: Specify a single storage
option for an XMLType column
ORA-19006:
XMLType TYPE storage option not appropriate for storage type
Cause: The TYPE option can only be
used in case of OBJECT RELATIONAL storage option
Action: Remove the TYPE option or
specify an OBJECT RELATIONAL storage for the XMLType column
ORA-19007:
Schema string does not match expected string.
Cause: The given XML document
conformed to a different schema than expected.
Action: Insert/Update only the XML
documents that conform to that particular schema.
ORA-19008:
Invalid version of the XMLType
Cause: An invalid version of the
XMLType was found.
Action: This is possible due to data
corruption or an internal error or running an older client against a newer
version of the database. Make sure that the version of the client can
understand the XMLType in the database.
ORA-19009:
Missing XMLSchema keyword
Cause: The XMLSchema keyword is
missing
Action: Specify the XMLSchema URL and
element name.
ORA-19010:
Cannot insert XML fragments
Cause: XML fragments got from
extractNode cannot be inserted into the database.
Action: Convert the fragment into a
proper XML document before insertion.
ORA-19011:
Character string buffer too small
Cause: The string result asked for is
too big to return back
Action: Get the result as a lob
instead
ORA-19012:
Cannot convert XML fragment to the required datatype
Cause: A conversion to a datatype was
requested which cannot be performed
Action: The XMLType may contain
fragments and other elements which cannot be converted to the appropriate
datatype.
ORA-19013:
Cannot create VARRAY columns containing XMLType
Cause: An attempt was made to create
a VARRAY column which contains a XMLType
Action: You cannot store VARRAYs
containing XMLTypes in tables. Use nested tables instead
ORA-19015:
Invalid XML tag identifier (string)
Cause: An invalid XML identifer was
detected during XML generation
Action: Fix the offending tag to not
contain characters or symbols that are not allowed by the XML specification
ORA-19016:
attributes cannot occur after element specifications
Cause: Attributes specified using the
"@" identifier can only occur before any other element definition
when creating XML
Action: Change the order of the types
so that the attributes occur in the begining
ORA-19017:
Attributes can only be simple scalars
Cause: Attribute values can only be
simple scalar values
Action: Use only simple datatypes for
attribute values
ORA-19018:
Invalid character in XML tag 'string'
Cause: A tag name was found to have
an invalid XML character during XML generation.
Action: Rewrite the query so that the
generated XML tag, corresponding to a column name or alias, contains only valid
characters.
ORA-19019:
Invalid context passed to DBMS_XMLGEN.GETXML
Cause: The value of context passed to
GETXML was invalid.
Action: Rewrite the query so that the
value of context passed to GETXML is valid.
ORA-19020:
invalid dereference of XMLType columns
Cause: An attempt was made to
dereference the attributes of an XMLType column which is not part of a base
table
Action: You can only dereference the
attributes of a base table XMLType column
ORA-19023:
The first argument to UPDATEXML operator has to be an XMLTYPE
Cause: The first argument passed to
the update value operator was not an XMLTYPE.
Action: Rewrite the query so that the
first argument to the UPDATEXML operator is XMLTYPE.
ORA-19024:
Cursor expression must be named
Cause: The value of context passed to
GETXML was invalid.
Action: Rewrite the query so that the
value of context passed to GETXML is valid.
ORA-19025:
EXTRACTVALUE returns value of only one node
Cause: Given XPath points to more
than one node.
Action: Rewrite the query so that
exactly one node is returned.
ORA-19026:
EXTRACTVALUE can only retrieve value of leaf node
Cause: Given XPath does not point to
a leaf node.
Action: Rewrite the query so that a
leaf node is returned.
ORA-19028:
Invalid ADT parameter passed to toObject() function
Cause: The object passed as ADT
parameter to sys.XMLType.toObject() is not the same type, or a super-type, of
the mapped type.
Action: Pass an object of the correct
type to toObject().
ORA-19029:
Cannot convert the given XMLType to the required type
Cause: The passed in XMLType could
not be convert to the required type
Action: Binary XMLtype instances or
other objects cannot be converted to the required object or collection types.
ORA-19030:
Method invalid for non-schema based XML Documents.
Cause: The method can be invoked on
only schema based xmltype objects.
Action: Don't invoke the method for
non schema based xmltype objects.
ORA-19031:
XML element or attribute string does not match any in
type string.string
Cause: The passed in XML tag does not
match any in the object type
Action: Pass a valid canonical XML
that can map to the given object type
ORA-19032:
Expected XML tag string got string
Cause: When converting XML to object,
a wrong tag name was present
Action: Pass a valid canonical XML
that can map to the given object type
ORA-19033:
schema specified in the XML document does not match the schema parameter
Cause: When creating schema-based
XML, the schema specified in the XML document is different from the schema
passed in as the 'schema' parameter.
Action: Change the schema parameter to
match the schema specified in the XML document.
ORA-19034:
Type not supported during schema generation
Cause: The object type contained a
type that is not supported for schema generation.
Action: Use a different type or do not
generate a schema.
ORA-19035:
Invalid select item of the query in newContextFromHierarchy()
Cause: The query does not have a
number select item followed by an XMLType select item only.
Action: Make sure the result set of
the query used in the newContextFromHierarchy() must have only two selected
items: the first item must be number type and the second item must be XMLType.
ORA-19036:
Invalid query result set in newContextFromHierarchy()
Cause: The result set of the query
used in the newContextFromHierarchy() does not have the same property as the
result set generated by a CONNECT BY query.
Action: Make sure the query used in
newContextFromHierarchy() is a CONNECT BY query or the query returns the result
set have the same property as the result set generated by a CONNECT BY query.
ORA-19037:
XMLType result can not be a fragment
Cause: The select item of the query
in newContextFromHierarchy() is an XML fragment.
Action: Make sure the select item of the
query in newContextFromHierarchy() is NOT an XML fragment
ORA-19038:
Invalid opertions on query context
Cause: SetMaxRows, SetSkipRows,
SetRowTagName opertions are applied to a query context created from
newContextFromHierarchy().
Action: SetMaxRows, SetSkipRows,
SetRowTagName opertions can not be applied to a query context created from
newContextFromHierarchy().
ORA-19039:
Keyword string reserved for future use
Cause: The keyword is reserved for
future use as a builtin function.
Action: Change the name mentioned
above to a different one.
ORA-19040:
Element string does not match expected string.
Cause: The given XML document had a
different root element than expected.
Action: Insert/Update only the XML
documents that conform to that particular schema and element.
ORA-19041:
Comment data cannot contain two consecutive '-'s
Cause: The given comment string
expression has two consecutive '-'s.
Action: Modify comment string to
eliminate one or both of the consevutive '-'s.
ORA-19042:
Enclosing tag string cannot be xml in any case combination
Cause: The given enclosing tag
matched 'xml' in some case combination
Action: Modify the enclosing tag so
that it is not xml in any case combination.
ORA-19043:
Multiply nested XMLROOT function disallowed
Cause: An XMLROOT function has an
operand that is also an XMLROOT function.
Action: Modify the query so that there
are no multiply nested XMLROOT functions.
ORA-19044:
character length specified for XMLSerialize is too small.
Cause: An XMLSerialize function was
called with a type of character type (e.g. VARCHAR2(27)), and the length
specified (27 in the example) was too small.
Action: Modify the query so that the
character length specified is larger.
ORA-19045:
character set id specified for XMLSerialize not valid
Cause: An XMLSerialize function was
called with an invalid value for the caracter set id.
Action: Modify the query so that the
character set id is valid.
ORA-19100:
PASSING or RETURNING keyword expected
Cause: The keyword PASSING or
RETURNING was missing.
Action: Specify the PASSING or
RETURNING keyword.
ORA-19101:
CONTENT keyword expected
Cause: The keyword CONTENT was
missing.
Action: Specify the CONTENT keyword.
ORA-19102:
XQuery string literal expected
Cause: The string literal containing
the XQuery expression was missing.
Action: Specify the XQuery expression
as a string literal.
ORA-19103:
VALUE keyword keyword
Cause: The keyword VALUE was missing.
Action: Specify the VALUE keyword.
ORA-19104:
invalid XQueryX: missing attribute string
Cause: The XQueryX expression was not
assigned the expected attribute.
Action: Specify a valid XQueryX.
ORA-19105:
invalid XQueryX: expected text node - got string
Cause: The XQueryX expression did not
contain a text node as expected.
Action: Specify a valid XQueryX.
ORA-19106:
invalid XQueryX: expected string - got string
Cause: The XQueryX expression did not
contain the node as expected.
Action: Specify a valid XQueryX.
ORA-19107:
invalid XQueryX - unsupported construct - string
Cause: The given XQuery expression contains
an unsupported construct.
Action: Specify a valid XQueryX.
ORA-19108:
WHITESPACE keyword expected
Cause: The keyword WHITESPACE was
missing.
Action: Specify the WHITESPACE
keyword.
ORA-19109:
RETURNING keyword expected
Cause: The keyword RETURNING was
missing.
Action: Specify the RETURNING keyword.
ORA-19110:
unsupported XQuery expression
Cause: The program specified an
XQuery expression that is not supported.
Action: Rewrite the XQuery with a
expression that is supported.
ORA-19111:
error during evaluation of the XQuery expression
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19112:
error raised during evaluation: string
Cause: The error function was called
during evaluation of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19113:
trace function called during evaluation: string
Cause: The trace function was called
during evaluation of the XQuery expression.
Action: Check the log file for the
trace message.
ORA-19114:
XPST0003 - error during parsing the XQuery expression: string
Cause: An error occurred during the
parsing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19115:
too many context items specified
Cause: More than one context item was
specified as input to the XMLQuery function.
Action: Specify a single context item
for the XMLQuery function.
ORA-19116:
too many xmlspace declarations
Cause: The query prolog contained
multiple xmlspace declarations.
Action: Remove the duplicate xmlspace
declarations.
ORA-19117:
XQST0070 - invalid redefinition of predefined namespace prefix 'string'
Cause: The given predefined namespace
was being redefined in a namespace declaration.
Action: Remove the namespace
declaration that redefines the predefined namespace prefix.
ORA-19118:
XQST0066 - duplicate default namespace definition - string
Cause: More than one default
namespace declaration used the given namespace URI.
Action: Remove the duplicate default
namespace definition.
ORA-19121:
duplicate attribute definition - string
Cause: More than one attribute with
the same name.
Action: Remove the duplicate attribute
definition.
ORA-19122:
unsupported XQuery declaration
Cause: The program specified an
XQuery declaration that is not supported.
Action: Rewrite the XQuery with a
declaration that is supported.
ORA-19123:
FORG0003: fn:zero-or-one() called with a sequence containing more than one item
Cause: sequence with more than one
item was passed into fn:zero-or-one() function
Action: correct input argument to
fn:zero-or-one() function
ORA-19124:
FORG0004: fn:one-or-more() called with a sequence containing no items
Cause: sequence containing no items
was passed into fn:one-or-more() function
Action: correct input argument to
fn:one-or-more() function
ORA-19125:
FORG0005: fn:exactly-one() called with a sequence containing zero or more than
one item
Cause: sequence containing zero or
more than one item was passed into fn:exactly-one() function
Action: correct input argument to
fn:exactly-one() function
ORA-19126:
XQuery extension expression contains neither a pragma that is recognized by the
implementation nor an expression enclosed in curly braces
Cause: No expression was enclosed in
curly braces for the extension expression or the pragma content was not
recognized.
Action: Correct inputs to extension
expression.
ORA-19127:
XQST0067: XQST0067: A static error is raised if a Prolog contains more than one
construction declaration
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19128:
XQST0068: A static error is raised if a Prolog contains more than one
boundary-space declaration
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19129:
XQST0069: A static error is raised if a Prolog contains more than one empty
order declaration
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19130:
XQST0070: A static error is raised if the predefined namespace prefix xml or
xmlns is redeclared by a namespace declaration or namespace declaration
attribute
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19131:
XQST0071: A static error is raised if the namespace declaration attributes of a
direct element constructor do not have distinct names
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19132:
XQDY0072: It is a dynamic error if the result of the content expression of a
computed comment constructor contains two adjacent hyphens or ends with a
hyphen
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19133:
XQST0073: It is a static error if the graph of module imports contains a cycle
(that is, if there exists a sequence of modules M1 ... Mn such that each Mi
imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a
common namespace
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19134:
XQDY0074: It is a dynamic error if the value of the name expression in a
computed element constructor cannot be converted to an expanded QName (for
example, because it contains a namespace prefix not found in statically known
namespaces.)
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error message
for the possible causes.
ORA-19135:
XQST0075: An implementation that does not support the Validation Feature must
raise a static error if it encounters a validate expression
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19136:
XQST0076: It is a static error if a collation subclause in an order by clause
of a FLWOR expression does not identify a collation that is present in
statically known collations
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19137:
XQST0079: It is a static error if an extension expression contains neither a
pragma that is recognized by the implementation nor an expression enclosed in
curly braces
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19138:
The target type of a cast or castable expression must be an atomic type that is
in the in-scope schema types and is not xs:NOTATION or xs:anyAtomicType,
optionally followed by the occurrence indicator "?"; otherwise a
static error is raised
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19139:
XPST0081: It is a static error if a QName used in a query contains a namespace
prefix that cannot be expanded into a namespace URI by using the statically
known namespaces
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19140:
XPST0083: It is a static error if the target type of a cast expression or
constructor function is xs:QName or a type derived from xs:QName or
xs:NOTATION, and the argument of the cast expression or constructor function is
not a string literal
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error message
for the possible causes.
ORA-19141:
XQDY0084: It is a dynamic error if the element validated by a validate
statement does not have a top-level element declaration in the in-scope element
declarations, if validation mode is strict
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19142:
FONC0001 = FONC0001: undefined context item
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19143:
XQTY0086: It is a type error if the typed value of a copied element or
attribute node is namespace-sensitive when construction mode is preserve and
copy-namespaces mode is no-preserve
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19145:
XQST0087: It is a static error if the encoding specified in a Version
Declaration does not conform to the definition of EncName specified in [XML
1.0]
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19146:
XQST0088: It is a static error if the literal that specifies the target
namespace in a module import or a module declaration is of zero length
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19147:
XQST0089: It is a static error if a variable bound in a for clause of a FLWOR
expression, and its associated positional variable, do not have distinct names
(expanded QNames)
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error message
for the possible causes.
ORA-19148:
XQST0090: It is a static error if a character reference does not identify a
valid character in the version of XML that is in use
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19149:
XQDY0091: An implementation may raise a dynamic error if an xml:id error, as
defined in [XML ID], is encountered during construction of an attribute named
xml:id
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19150:
XQDY0092: An implementation may raise a dynamic error if a constructed
attribute named xml:space has a value other than preserve or default
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19151:
XQST0093: It is a static error to import a module M1 if there exists a sequence
of modules M1 ... Mi ... M1 such that each module directly depends on the next
module in the sequence (informally, if M1 depends on itself through some chain
of module dependencies.)
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19152:
FOCH0001 = FOCH0001: codepoint not valid
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19153:
FOCH0002: unsupported collation
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19154:
FOCH0003: unsupported normalization form
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19155:
FOCH0004: collation does not support collation units
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19156:
FODC0001: no context document
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19157:
FODC0002: error retrieving resource
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19158:
FODC0004: invalid argument to fn:collection()
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19159:
FODC0005: invalid argument to fn:doc
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19160:
XPST0003 - syntax error: invalid variable name string
Cause: The given XQuery variable does
not begin with the '$' sign
Action: Fix the variable name to start
with the "$" sign.
ORA-19161:
XPTY0004 - XQuery type mismatch: invalid argument type 'string' for
function 'string'
Cause: The type of the argument that
was passed to the given function was not valid.
Action: Fix the argument to be of a
type supported by the given function.
ORA-19162:
XPTY0004 - XQuery type mismatch: invalid argument types 'string', 'string'
for function 'string'
Cause: The type of the arguments that
were passed to the given function was not valid.
Action: Fix the arguments to be of a
type appropriate for the given function.
ORA-19163:
XPTY0004 - XQuery type mismatch: argument type mismatch: expected - 'string'
got - 'string' for function 'string'
Cause: The type of the arguments that
were passed to the given function was not valid.
Action: Fix the arguments to be of a
type appropriate for the given function.
ORA-19164:
XQST0085 - It is a static error if the namespace URI in a namespace declaration
attribute is a zero-length string, and the implementation does not support [XML
Names 1.1].
Cause: There was a zero-length URI in
namespace declaration.
Action: Fix the namespace declaration.
ORA-19165:
FONS0003: no prefix defined for namespace
Cause: There was a zero-length URI in
namespace declaration.
Action: Fix the namespace declaration.
ORA-19166:
FONS0003: FONS0004: no namespace found for prefix
Cause: There was a zero-length URI in
namespace declaration.
Action: Fix the namespace declaration.
ORA-19167:
FONS0005: base uri not defined in the static context
Cause: There was a zero-length URI in
namespace declaration.
Action: Fix the namespace declaration.
ORA-19168:
FORG0002: invalid argument to fn:resolve-uri()
Cause: There was a zero-length URI in
namespace declaration.
Action: Fix the namespace declaration.
ORA-19169:
FORG0006: invalid argument type in 'string'
Cause: There was a zero-length URI in
namespace declaration.
Action: Fix the namespace declaration.
ORA-19171:
FORG0007: invalid argument to aggregate function
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19172:
FORG0008: both arguments to fn:dateTime have a specified timezone
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19173:
FORG0009: error in resolving a relative URI against a base URI in
fn:resolve-uri
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19174:
FORX0001: invalid regular expression flags
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19175:
FORX0002: invalid regular expression
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19176:
FORX0003: regular expression matches zero-length string
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19177:
FORX0004: invalid replacement string
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19178:
FOTY0001: type error
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19179:
FOTY0011: Type error. Context item is not a node
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19180:
FOTY0012: argument node does not have a typed value
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19181:
FOTY0014: type exception
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19182:
FORT0001: invalid number of parameters
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19183:
FOTY0002: type definition not found
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19184:
FOTY0021: invalid node type
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19185:
FOAR0002: numeric operation overflow/unflow
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19186:
FOCA0001: input value too large for decimal
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19187:
FOCA0002: invalid lexical value
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19188:
FOCA0003: input value too large for integer
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19189:
FOCA0005: NaN supplied as float/double value
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19190:
FOER0000: Unidentified error
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19191:
FOAR0001: division by zero
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19192:
XQST0047: It is a static error if multiple module imports in the same Prolog
specify the same target namespace
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19193:
XQST0045: It is a static error if the function name in a function declaration
is in one of the following namespaces: http://www.w3.org/XML/1998/namespace,
http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance,
http://www.w3.org/2005/04/xpath-functions,
http://www.w3.org/2005/04/xpath-datatypes
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19194:
XQDY0026: It is a dynamic error if the result of the content expression of a
computed processing instruction constructor contains the string
"?>"
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19200:
Invalid column specification
Cause: All input arguments must be
valid columns
Action: Specify a valid list of
columns
ORA-19201:
Datatype not supported
Cause: The particular datatype is not
supported in the XMLGEN operator
Action: Specify only supported
datatypes as arguments to the XMLGEN operator
ORA-19202:
Error occurred in XML processingstring
Cause: An error occurred when
processing the XML function
Action: Check the given error message
and fix the appropriate problem
ORA-19203:
Error occurred in DBMS_XMLGEN processingstring
Cause: An error occurred when
processing the DBMS_XMLGEN functions
Action: Check the given error message
and fix the appropriate problem
ORA-19204:
Non-scalar value 'string' is marked as XML attribute
Cause: Only scalar values (i.e.
values which are not of object or collection type) can be marked as XML
attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was
prefixed with '@'
Action: Remove the '@' sign, or make
the value a scalar.
ORA-19205:
Attribute 'string' qualifies a non-scalar value in the select list
Cause: The attribute immediately
follows a value of object or collection type in the select list or type
definition.
Action: Remove the '@' sign, or make
the previous value a scalar.
ORA-19206:
Invalid value for query or REF CURSOR parameter
Cause: The queryString argument
passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.
Action: Rewrite the query so that the
queryString argument is a valid query or REF CURSOR.
ORA-19207:
scalar parameter string of XMLELEMENT cannot have an alias.
Cause: The scalar parameter to
XMLELEMENT has been qualified with an alias.
Action: Remove the AS clause of the
scalar element.
ORA-19208:
parameter string of function string must be
aliased
Cause: The indicated parameter of the
XML generation function has not been aliased, although it is an expression.
Action: Specify an alias for the
expression using the AS clause.
ORA-19209:
invalid or unsupported formatting argument
Cause: An invalid or unsupported
formatting argument was supplied
Action: Change the formatting argument
to legal supported values
ORA-19210:
column 'string', specified to be a key or update column for
DBMS_XMLSTORE, does not not exist in table 'string'
Cause: The column specified using
setKeyColumn()/setUpdateColumn() did not exist in the table.
Action: Change the column specified to
be a column in the table
ORA-19211:
column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must
be of scalar type
Cause: The column specified using
setKeyColumn() was a non-scalar type column.
Action: Change the column specified to
be a scalar column in the table
ORA-19212:
no key columns specified before call to DBMS_XMLSTORE.updateXML()
Cause: No columns were specified as
key columns before the call to DBMS_XMLSTORE.updateXML.
Action: Use
DBMS_XMLSTORE.setKeyColumn() to specify key columns
ORA-19221:
XPST0001 - XQuery static context component string not
initialized
Cause: An unitialized static context
component was encountered during the static analysis of the expression.
Action: initialize the given static
context.
ORA-19222:
XPDY0002 - XQuery dynamic context component string not
initialized
Cause: An unitialized dynamic context
component was encountered during the evaluation of the expression.
Action: Initialize the particular
dynamic context component.
ORA-19223:
XPST0003 - syntax error in XQuery expression
Cause: The given XQuery expression
contains syntax errors.
Action: Fix the syntax error in the
XQuery expression.
ORA-19224:
XPTY0004 - XQuery static type mismatch: expected - string got
- string
Cause: The expression could not be
used because it's static type is not appropriate for the context in which it
was used.
Action: Fix the expression to be of
the required type or add appropriate cast functions around the expression.
ORA-19225:
XPST0005 - XQuery static type error: expected non empty type got empty sequence
Cause: The static type assigned to an
expression other than the () expression must not be the empty type.
Action: Fix the expression so it does
not return empty sequences.
ORA-19226:
XPTY0006 - XQuery dynamic type mismatch: expected string got string
Cause: The expression could not be
used because it's dynamic type did not match the required type as specified by
XQuery sequencetype matching rules.
Action: Fix the expression to return
the expected type or use appropriate cast functions.
ORA-19227:
XPTY0007 - fn:data function is applied to a node (type (string)) whose
type annotation denotes a complex type with non-mixed complex content.
Cause: The input node for atomization
contained a type annotation that denoted a complex type with non-mixed complex
content.
Action: Fix the input expression to
fn:data to be a node that does not contain non-mixed complex content.
ORA-19228:
XPST0008 - undeclared identifier: prefix 'string' local-name 'string'
Cause: The given identifier refers to
either a type name, function name, namespace prefix, or variable name that is
not defined in the static context.
Action: Fix the expression to remove
the identifier, or declare the appropriate variable, type, function or
namespace.
ORA-19229:
XQST0009 - schema import not supported
Cause: A schema import was
encountered in the query.
Action: remove the schema import.
ORA-19230:
XPST0010 - unsupported axis string
Cause: An unsupported axis was
encountered in the given expression.
Action: Remove the unsupported axis
from the expression.
ORA-19232:
XQST0012 - imported schemas violate validity rules
Cause: The imported schemas did not
satisfy the conditions for schema validity specified in the XMLSchema
specification.
Action: Fix the imported schemas to
satisfy the validity rules.In particular, the definitions must be valid,
complete, and unique -- that is, the pool of definitions must not contain two
or more schema components with the same name and target namespace.
ORA-19233:
XQST0013 - invalid pragma
Cause: A pragma was specified whose
contents are invalid.
Action: Specify the pragma with the
correct contents.
ORA-19234:
XQST0014 - invalid or unsupported must-understand extension
Cause: The must-understand extension
specified was either invalid or unsupported.
Action: remove the unsupported
must-understand extension or fix the error.
ORA-19235:
XQST0015 - unsupported must-understand extension
Cause: The XQuery flagger was enabled
and the query contained a must-understand extension.
Action: remove the unsupported
must-understand extension.
ORA-19236:
XQST0016 - module declaration or import not supported
Cause: The given query had a module
declaration or module import.
Action: Remove the import module or
module declaration.
ORA-19237:
XPST0017 - unable to resolve call to function - string:string
Cause: The name and arity of the
function call given could not be matched with any in-scope function in the
static context.
Action: Fix the name of the function
or the number of parameters to match the list of in-scope functions.
ORA-19238:
XPTY0018 - It is a type error if the result of the last step in a path expression
contains both nodes and atomic values
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19239:
XPTY0019 - It is a type error if the result of an step (other than the last
step) in a path expression contains an atomic value
Cause: The step expression returned a
sequence containing an atomic value.
Action: Fix the path expression to
return only nodes.
ORA-19240:
XPTY0020 - context item must be node in an axis expression
Cause: The context item that was used
in the axis epression is not a node.
Action: Change the context item to be
a node.
ORA-19241:
XPDY0021 - cast to type string failed
Cause: The value inside a cast
expression could not be cast to the required type.
Action: Fix the input to the cast
expression to be of a castable type.
ORA-19242:
XQST0022 - namespace declaration attribute must be a literal
Cause: The namespace declaration
attribute was not a literal string.
Action: Fix the namespace declaration
to be a literal string.
ORA-19243:
XQTY0023 - invalid document node content in element constructor
Cause: The content sequence in an
element constructor contained a document node.
Action: Change the content of the
element constructor so that it does not contain a document node.
ORA-19244:
XQTY0024 - invalid attribute node in element constructor
Cause: The content sequence in an
element constructor contained an attribute node following a node that was not
an attribute node.
Action: Change the content sequence of
the element constructor so that it does not contain the attribute node.
ORA-19245:
XQDY0025 - duplicate attribute name string
Cause: The content sequence of the
element constructor contained more than one attribute that had the same name.
Action: Remove the duplicate
attributes.
ORA-19246:
validation failed - element string not found in in-scope
element declarations
Cause: The validation mode was strict
and the element-constructor contained an element name that was not present in
the in-scope element declarations.
Action: Fix the validation mode to be
lax or import the schema definition that contains the required element
declaration.
ORA-19247:
XQDY0027 - validation error
Cause: An error was encountered
during the validation of the expression.
Action: Fix the validation error.
ORA-19248:
XQTY0028 - invalid node in document constructor
Cause: The content sequence in a
document constructor contained either a document or an attribute node.
Action: Fix the content so it does not
contain any of the above node types.
ORA-19249:
XQDY0029 - value does not match facet of the target type
Cause: The input value to a cast
expression did not satisfy the facets of the target type.
Action: Fix the value to conform to
the facets of the target type.
ORA-19250:
XQTY0030 - too many values to validate expression
Cause: The argument of a validate
expression returned more than one element or document node.
Action: Fix the argument of the
validate expression to return a single element or document node.
ORA-19251:
XQST0031 - unsupported query version
Cause: The query version specified in
the prolog was not supported.
Action: Supply the version of the
query that is supported.
ORA-19252:
XQST0032 - too many declarations for base URI
Cause: The query prolog contained multiple
declarations for the base URI.
Action: Remove the duplicate
definitions for the base URI.
ORA-19253:
XQST0033 - too many declarations for namespace prefix string
Cause: The query prolog contained
multiple declarations for the same namespace prefix.
Action: Remove the duplicate
definitions for the namespace prefix.
ORA-19254:
XQST0034 - too many declarations for function string
Cause: The query module contained
more than one function, either declared or imported, which have the same
expanded QName.
Action: Remove the duplicate function
definitions.
ORA-19255:
XQST0035 - too many declarations of string in imported schemas
Cause: Two schemas were imported that
defined the same name in the same symbol space and in the same scope.
Action: Fix the schema imports to
remove the name conflict.
ORA-19256:
XQST0036 - missing type definitions in imported module
Cause: A module was imported, which
contains references to type names that are not defined in the in-scope type
definitions inside the module.
Action: Fix the module definintion to
include the in-scope type definition.
ORA-19257:
XQST0037 - function or variable string in module already
defined
Cause: A module being imported
contained the function or variable that is already declared in the static context
of the importing module.
Action: Remove the conflicting
declarations.
ORA-19258:
XQST0038 - unsupported or duplicate default collation specified
Cause: The query prolog prolog either
specified more than one default collation or the collation specified was not
supported.
Action: Remove the duplicate
definition or specify a supported collation.
ORA-19259:
XQST0039 - duplicate parameter name string in function
declaration
Cause: The function declaration
contained more than one parameter with the same name.
Action: Fix the function declaration
to remove the duplicate parameters.
ORA-19260:
XQST0040 - invalid namespace node in element constructor
Cause: The content sequence in an
element constructor contained a namespace node node following a node that was not
a namespace node.
Action: Remove the namespace node in
the element constructor.
ORA-19261:
XQDY0041 - non empty URI in QName
Cause: The name expression in a
computed processing instruction or computed namespace constructor returned a
QName whose URI part was not empty.
Action: Fix the processing instruction
or computed namespace constructor to return the QName with an empty URI part.
ORA-19262:
XQST0042 - namespace constructor not inside an element constructor
Cause: The enclosing expression of a
computed namespace constructor was not a computed element constructor.
Action: Fix the namespace constructor
to be inside an element constructor.
ORA-19263:
XQST0043 - duplicate namespace prefix string
Cause: Two or more computed namespace
constructors within the same computed element constructor attempted to bind the
same namespace prefix.
Action: Remove the duplicate namespace
definitions.
ORA-19264:
XQDY0044 - invalid namespace in attribute constructors
Cause: A computed attribute
constructor returned a QName that is in the pre-defined XML namespace
(corresponding to namespace prefix xmlns).
Action: Change the namespace for the
computed attribute constructor.
ORA-19265:
XQST0045 - invalid or unknown prefix string in function
declaration
Cause: The declared function name in
a function declaration had no namespace prefix or had one of the predefined
namespace prefixes other than local.
Action: Fix the function declaration
to have the correct prefix.
ORA-19266:
XQST0046 - invalid URI
Cause: The given URI contained a
lexical form that was not valid according to the definition of xs:anyURI in XML
Schema.
Action: Fix the URI.
ORA-19267:
module string not found
Cause: The module with the given
target URI could not be found.
Action: Fix the prolog to import only
available modules.
ORA-19268:
XQST0048 - namespace string does not match target
namespace string
Cause: The module contained a
function or variable whose namespace did not match the target namespace of the
module.
Action: Fix the namespace of the
function or variable to match the target namespace of the module.
ORA-19269:
XQST0049 - variable string defined multiple times
Cause: The module defined or imported
the same variable multiple times.
Action: Fix the import or the module
definition to remove duplicate definitions.
ORA-19270:
XPDY0050 - treat failed - expected string got string
Cause: The type of the operand to the
treat expression did not match the required type.
Action: Fix the input operand to be of
the correct type.
ORA-19271:
XPST0051 - invalid atomic type definition
Cause: The QName used as an
AtomicType in a SequenceType was not defined in the in-scope type definitions
as an atomic type.
Action: Use the correct atomic type
name.
ORA-19272:
XQDY0052 - invalid atomic value in attribute or element constructor
Cause: The content of the element or
attribute constructor included an atomic value that could not be cast into a
string.
Action: Fix the content to contain
atomic values that can be cast to a string.
ORA-19273:
XQST0053 - empty string in namespace declaration
Cause: An empty string was used in a
namespace declaration.
Action: Fix the namespace declaration
to have a non-empty string.
ORA-19274:
XQST0054 - variable initialization failed due to circularity
Cause: A circular definition was encountered
when the variable was initialized.
Action: Remove the circularity in the
initialization.
ORA-19275:
XQST0055 - schema path string not found in list of in-scope
schema definitions
Cause: The ElementTest specified a
schema path that could not be found in the list of in-scope schema definitions.
Action: Include the appropriate schema
that can be used to resolve the ElementTest.
ORA-19276:
XPST0005 - XPath step specifies an invalid element/attribute name: (string)
Cause: The XPath step specified invalid
element or attribute name that did not match any nodes according to the input
XML schema or structure.
Action: Correct the element or
attribute name as the name may be mis-spelled.
ORA-19277:
XPST0005 - XPath step specifies an item type matching no node: (string)
Cause: The XPath step specified an
item type that did not match any nodes according to the input XML schema or
structure.
Action: Correct the item type
defintion as node of such type does not exit in the input XML schema or
structure.
ORA-19278:
Invalid value: (string) for type: (string)
Cause: The value was invalid for the
type.
Action: Correct the value or change
the type.
ORA-19279:
XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got
multi-item sequence
Cause: The XQuery sequence passed in
had more than one item.
Action: Correct the XQuery expression
to return a single item sequence.
ORA-19280:
XQuery dynamic type mismatch: expected atomic value - got node
Cause: A node was passed in to the
expression where an atomic value was expected.
Action: Correct the XQuery expression
to return an atomic value.
ORA-19281:
XQST0055 - It is a static error if a Prolog contains more than one
copy-namespaces declaration
Cause: The query prolog contained
multiple copy-namespaces declarations.
Action: Remove the duplicate
copy-namespaces declarations.
ORA-19282:
XQST0068 - It is a static error if a Prolog contains more than one xmlspace
declaration
Cause: The query prolog contained
multiple xmlspace declarations.
Action: Remove the duplicate xmlspace
declarations.
ORA-19283:
XQST0031 - It is a static error if the version number specified in a version
declaration is not supported by the implementation.
Cause: The query contained a version
declaration not supported by this implementation.
Action: Change the version declaration
to 1.0 which is the version supported by this implementation.
ORA-19284:
Encoding specification in version declaration not supported
Cause: The query contained an
encoding specification.
Action: Remove the encoding
specification.
ORA-19285:
FODC0002 - error retrieving resource
Cause: The URI provided could not be
resolved to a valid resource.
Action: Provide a valid URI for a
resource.
ORA-19286:
XPST0017 - unable to resolve call to function - string
Cause: The name and arity of the
function call given could not be matched with any in-scope function in the
static context.
Action: Fix the name of the function
or the number of parameters to match the list of in-scope functions.
ORA-19287:
XPST0017 - invalid number of arguments to function - string:string
Cause: The name and arity of the
function call given could not be matched with any in-scope function in the
static context.
Action: Fix the name of the function
or the number of parameters to match the list of in-scope functions.
ORA-19288:
XPST0017 - invalid number of arguments to function - string
Cause: The name and arity of the
function call given could not be matched with any in-scope function in the
static context.
Action: Fix the name of the function
or the number of parameters to match the list of in-scope functions.
ORA-19289:
XQST0034 - function string:string declared or defined
multiple times
Cause: Multiple functions declared or
imported by a module had the same expanded QName and the same number of arguments.
Action: Fix the function declaraction
or definition to remove duplicates.
ORA-19290:
XQST0069 - more than one empty order declaration declared in the prolog
Cause: A prolog had more than one
empty order declaration.
Action: Fix the prolog to have just
one empty order declaration.
ORA-19291:
XPST0081 - specified QName cannot be expanded into a namespace URI
Cause: The namespace prefix of the
QName could not be expanded into a namespace URI by using the statically known
namespaces.
Action: Use a namespace prefix that
can be resolved into a namespace URI from the statically known namespaces.
ORA-19292:
XQST0057: It is a static error if a schema import binds a namespace prefix but
does not specify a target namespace other than a zero-length string
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19293:
XQST0058: It is a static error if multiple schema imports specify the same
target namespace
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19294:
XQST0059: It is a static error if an implementation is unable to process a
schema or module import by finding a schema or module with the specified target
namespace
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19295:
XQST0060: It is a static error if the name of a function in a function
declaration is not in a namespace (expanded QName has a null namespace URI)
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19296:
XQDY0061: It is a dynamic error if the operand of a validate expression is a
document node whose children do not consist of exactly one element node and
zero or more comment and processing instruction nodes, in any order
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19297:
XQDY0064: It is a dynamic error if the value of the name expression in a
computed processing instruction constructor is equal to "XML" (in any
combination of upper and lower case
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19298:
XQST0065: A static error is raised if a Prolog contains more than one ordering
mode declaration
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19299:
XQST0066: A static error is raised if a Prolog contains more than one default
element/type namespace declaration, or more than one default function namespace
declaration
Cause: An error occurred during the
processing of the XQuery expression.
Action: Check the detailed error
message for the possible causes.
ORA-19300:
Error occurred in uri processingstring
Cause: An error occurred when
processing the URL
Action: Check the given error message
and fix the appropriate problem
ORA-19320:
Host name not specified in HTTP URL
Cause: A host name was not specified
in the HTTP url
Action: Specify a host name in the
HTTP url when creating the URL string
ORA-19321:
Could not open HTTP connection to host (string): port (string)
Cause: A HTTP connection could not be
opened to the host
Action: Specify a valid host name and
port to connect to
ORA-19322:
An error occurred while reading from host (string): port (string)
Cause: An error occurred while
reading from the HTTP host
Action: Specify a valid host name and
port to read from
ORA-19323:
Invalid url string
Cause: The URL must be a valid URL
string
Action: Specify a valid url string
ORA-19330:
Type 'string'.'string' not installed. Please install the type
before using the CREATE_DBURI operator
Cause: The type required for the
CREATE_DBURI operator has not been installed correctly.
Action: Read the installation notes to
install the type correctly.
ORA-19331:
Last argument to CREATE_DBURI operator must be a column
Cause: The final argument to the
CREATE_DBURI operator must be a column to which the reference is being created.
Action: Specify a valid column name in
the query.
ORA-19332:
Invalid column in the CREATE_DBURI operator
Cause: The argument to the
CREATE_DBURI operator can only be a column.
Action: Specify a valid column name
for the operator
ORA-19333:
Invalid flags for the CREATE_DBURI operator
Cause: The flags argument given to
the DBURI operator is invalid
Action: Specify a valid flag value
(TEXT) for the DBURI operator
ORA-19334:
Invalid column specification for CREATE_DBURI operator
Cause: All columns must be valid and
pointing to the same table or view
Action: Specify valid list of columns
that are from the same table or view.
ORA-19335:
Invalid format type object
Cause: An invalid format type object
was specified for the XML function
Action: Specify a valid format type
object
ORA-19336:
Missing XML root element
Cause: The XML being generated does
not have an enclosing root element.
Action: The XML generated must have a
root element
ORA-19361:
ONLINE option not allowed with this type of index
Cause: The ONLINE option was
specified to validate the structure of a system-generated metadata index
Action: The ONLINE option can not be
used with system-generated metadata indexes such as an LOB index, an IOT Top
index, an Index on Clusters etc., Run query without using the ONLINE option.
ORA-19371:
invalid update option
Cause: The user attempted to call
load_sqlset with an update option that is different than REPLACE and
ACCUMULATE.
Action: Adjust the update option and
retry the operation.
ORA-19372:
invalid update condition
Cause: The user attempted to call
load_sqlset with an invalid update condition.
Action: Check the update condition
(e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation.
ORA-19373:
invalid staging table or tablespace
Cause: The user attempted to create a
staging table and specified an invalid staging table (or one that already
exists) or tablespace
Action: Check the arguments and try
again.
ORA-19374:
invalid staging table
Cause: The user specified an invalid
staging table to one of the pack, unpack, or remap stgtab routines, or the user
does not have the correct privileges on the staging table
Action: Provide a correct staging
table or grant the appropriate privileges
ORA-19375:
no CREATE TABLE privilege on schema "string"
Cause: The user tried to create a
staging table when he is missing the CREATE TABLE privilege on the specified
schema.
Action: Grant the privilege to the
user and retry
ORA-19376:
no privileges on tablespace provided or tablespace is offline
Cause: The user tried to create a
staging table on a tablespace on which he does not have any space allocated, or
it is offline
Action: Allocate space on the
tablespace, bring it online, and retry
ORA-19377:
no "SQL Tuning Set" with name like "string" exists
for owner like "string"
Cause: The user specified a filter to
a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS
schema or the staging table, respectively
Action: Provide a different filter
after checking the state of the system
ORA-19378:
invalid mode
Cause: The user specified an invalid
mode argument to the capture function.
Action: Provide a mode argument that
was defined in the dbmssqlt file
ORA-19379:
invalid time_limit or repeat_interval
Cause: The user specified a NULL
value for either the time_limit or the repeat_interval, or a repeat_interval
that is greater than the time_limit
Action: Provide a non-null value and
make sure time_limit >= repeat_interval
ORA-19380:
invalid plan filter
Cause: The user specified an invalid
filter for the plan when calling the select_sqlset table function.
Action: Adjust the the filter to be
one of the following values and retry the operation: MAX_ELAPSED_TIME,
MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED
LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED.
ORA-19381:
cannot create staging table in SYS schema
Cause: The user attempted to create a
staging table in the sys schema
Action: Create the table in another
schema.
ORA-19384:
cannot pack into staging table from previous version
Cause: An attempt was made to perform
a pack operation on a staging table from a previous version.
Action: Create a staging table in the
current version and retry the operation.
ORA-19385:
staging table is empty
Cause: An attempt was made to perform
an operation on an empty staging table.
Action: Check the staging table to
make sure that it has rows.
ORA-19386:
target object already exists for tuning task "string"
Cause: An attempt was made to set a
target object for a tuning task when one had already been set.
Action: Create a new task if another
target object is needed.
ORA-19387:
"SQL Tuning Set" "string" belongs to another tuning
task
Cause: The user attempted to tune a
task-managed SQL Tuning Set belonging to one task within the scope of another
task.
Action: Check the SQL Tuning Set and
retry the operation.
ORA-19388:
operation not supported for "SQL Tuning Set" type
Cause: The attempted operation was
unsupported for the type of the given SQL Tuning Set.
Action: Check the SQL Tuning Set and
retry the operation.
ORA-19400:
System type conflict with object SYS.string
Cause: The user had an object with
the same name as one of the system types. The system types were not initialized
properly.
Action: Remove the conflicting object
and rerun migration.
ORA-19500:
device block size string is invalid
Cause: the device block size returned
by sequential I/O OSD is invalid
Action: If the block size was set by
using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then
the specified block size must be changed. If no PARMS option was specified on
the ALLOCATE CHANNEL command, then this is an internal error that should be
reported to Oracle.
ORA-19501:
read error on file "string", block number string (block
size=string)
Cause: read error on input file
Action: check the file
ORA-19502:
write error on file "string", block number string (block
size=string)
Cause: write error on output file
Action: check the file
ORA-19503:
cannot obtain information on device, name="string",
type="string", parms="string"
Cause: call to get device information
returned an error
Action: check device name, type and
parameters
ORA-19504:
failed to create file "string"
Cause: call to create file returned
an error
Action: check additional messages,
check access permissions
ORA-19505:
failed to identify file "string"
Cause: call to identify the file
returned an error
Action: check additional messages, and
check if the file exists
ORA-19506:
failed to create sequential file, name="string", parms="string"
Cause: call to create the sequential
file returned an error
Action: check additional messages,
check access permissions
ORA-19507:
failed to retrieve sequential file, handle="string",
parms="string"
Cause: call to retrieve the
sequential file returned an error
Action: check additional messages, and
check if the file exists
ORA-19508:
failed to delete file "string"
Cause: call to delete the file
returned an error
Action: check additional messages
ORA-19509:
failed to delete sequential file, handle="string",
parms="string"
Cause: call to delete the sequential
file returned an error
Action: check additional messages
ORA-19510:
failed to set size of string blocks for file "string"
(block size=string)
Cause: call to resize the file
returned an error
Action: check additional messages
ORA-19511:
Error received from media manager layer, error text: string
Cause: An error occurred in the media
management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery
Manager.
Action: If the text of message 19511 does not provide enough
information to resolve the problem, then you should contact the vendor of the
media management software.
ORA-19512:
file search failed
Cause: Recovery manager or Oracle
Server attempted to discover files that matched the specified pattern but
failed.
Action: Check errors on the error
stack for an explanation why the search for files could not be successfully
executed.
ORA-19513:
failed to identify sequential file
Cause: Unable to identify the
sequential file.
Action: Check additional messages, and
check if the file exists on media.
ORA-19525:
tempfile for the clone database must be renamed
Cause: Opening a clone database
failed because Oracle server forces the tempfile to be renamed, in order to
avoid overwriting the primary tempfile.
Action: Rename the tempfiles manually
or automatically by using the DB_FILE_NAME_CONVERT initialization parameter.
ORA-19526:
only one location allowed for parameter string
Cause: A list of default locations
was provided in an Oracle-managed files parameter.
Action: Edit the parameter to include
a single location.
ORA-19527:
physical standby redo log must be renamed
Cause: The CLEAR LOGFILE command was
used at a physical standby database. This command cannot be used at a physical
standby database unless the LOG_FILE_NAME_CONVERT initialization parameter is
set. This is required to avoid overwriting the primary database's log files.
Action: Set the LOG_FILE_NAME_CONVERT
initialization parameter.
ORA-19528:
redo logs being cleared may need access to files
Cause: The redo logs are being
cleared. This procedure may need the files this operation is being applied to.
Action: Wait for the redo logs to be
cleared.
ORA-19529:
Pattern string in initialization parameter string has
an Oracle Managed Files file name.
Cause: An attempt was made to convert
a database file name to an Oracle Managed Files file name using DB_FILE_NAME_CONVERT
or LOG_FILE_NAME_CONVERT initialization parameter. This was not a valid
operation.
Action: Retry the operation with a
pattern template instead of a full Oracle Managed Files file name.
ORA-19550:
cannot use backup/restore functions while using dispatcher
Cause: Attempted to use
backup/restore functions while connected to the dispatcher in a shared server.
This is not allowed because the device that is used for backup and restore must
remain allocated to a single process.
Action: Connect directly to the
instance then re-execute the backup or restore function.
ORA-19551:
device is busy, device type: string, device name: string
Cause: The indicated device could not
be allocated because it is allocated to another session, or no device was named,
or all devices of the requested type are busy.
Action: Either attempt to allocate
another device or wait until the required device is no longer busy.
ORA-19552:
device type string is invalid
Cause: The device type indicated is
invalid.
Action: Supply a correct device type
and retry the allocation.
ORA-19553:
device name string is invalid
Cause: The device name indicated is
invalid.
Action: Supply a correct device name
and retry the allocation.
ORA-19554:
error allocating device, device type: string, device name: string
Cause: The specified device could not
be allocated.
Action: One or more other messages
should be displayed to help pinpoint the cause of the error. Correct the error
and retry the allocation.
ORA-19555:
invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
Cause: The value of parameter
LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.
Action: Specify a correct value for
parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter
LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.
ORA-19556:
required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
Cause: The destination for parameter
LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The
destination was deferred automatically when an ALTER SYSTEM command for
parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing
LOG_ARCHIVE_DUPLEX_DEST parameter destination.
Action: Change the destination value for
the LOG_ARCHIVE_DUPLEX_DEST parameter.
ORA-19557:
device error, device type: string, device name: string
Cause: An error occurred in the
platform-specific device code
Action: One or more other messages
should be displayed to help pinpoint the cause of the error. Correct the error
and retry the allocation.
ORA-19558:
error de-allocating device
Cause: The specified device could not
be de-allocated.
Action: One or more other messages
should be displayed to help pinpoint the cause of the error. Correct the error
and retry the allocation.
ORA-19559:
error sending device command: string
Cause: An error occurred while
sending the indicated command to the session device.
Action: One or more other messages
should be displayed to help pinpoint the cause of the error. Correct the error
and retry the allocation.
ORA-19560: string is
not a valid device limit
Cause: An invalid type of device
limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT.
Action: Use one of the documented
limits: KBYTES, READRATE, or PARALLEL.
ORA-19561: string requires
a DISK channel
Cause: The attempted command requires
that a DISK device channel be allocated to the session, but a non-DISK device
was found.
Action: Deallocate the current device
and allocate a DISK channel, then then retry the command.
ORA-19562:
file string is empty
Cause: The indicated file, which is
an archived log, control file, or datafile was found to be empty during a copy,
backup, or scan] operation.
Action: Ensure that the correct files
are being specified for the copy or backup operation.
ORA-19563: string header
validation failed for file string
Cause: When opening the file to be
placed in a copy or backup set, to be inspected, or used as the target for an
incremental restore, its header was not recognized as a valid file header for a
file of the indicated type (datafile, archived log, or control file) belonging
to the current database.
Action: Ensure that the correct files
are being specified for the copy or backup operation.
ORA-19564:
error occurred writing string bytes at block number string
Cause: An error occurred while
writing to a file.
Action: One or more other messages
should be displayed to help pinpoint the cause of the error. Correct the error
if possible, then retry the copy, backup, or restore operation.
ORA-19565:
BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
Cause: An attempt was made to specify
duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization
parameter was not enabled.
Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE
in the INIT.ORA file, or do not specify duplexing to sequential devices.
ORA-19566:
exceeded limit of string corrupt blocks for file string
Cause: The user specified limit of
allowable corrupt blocks was exceeded while reading the specified datafile for
a datafile copy or backup.
Action: None. The copy or backup
operation fails. The session trace file contains detailed information about
which blocks were corrupt.
ORA-19567:
cannot shrink file string because it is being backed up or
copied
Cause: An ALTER statement attempted
to reduce the size of the indicated file while the same file is being backed up
or copied.
Action: Retry the resize after the
backup or copy is complete.
ORA-19568:
a device is already allocated to this session
Cause: A device cannot be allocated
to a session if another device is already allocated.
Action: Deallocate the current device
ORA-19569:
no device is allocated to this session
Cause: An operation was attempted
which requires a device to be allocated to the current session, and there is no
device allocated.
Action: Allocate a device then retry
the operation.
ORA-19570:
file number string is outside valid range of 1 through string
Cause: A file number used in a copy,
backup, or restore operation is not valid for the current database.
Action: Specify a valid file number.
ORA-19571: string RECID string STAMP string not
found in control file
Cause: The input file specified for a
copy or backup operation could not be opened because the record describing the file
is not found in the control file.
Action: Specify a correct RECID/STAMP
and retry the copy or backup.
ORA-19572:
cannot process file string, file is being being resized
Cause: The input file specified for a
copy or backup operation could not be opened because the file is being resized.
Action: Wait for the resize to
complete then retry the copy or backup.
ORA-19573:
cannot obtain string enqueue for datafile string
Cause: The file access enqueue could
not be obtained for a file specified in a backup, copy or restore operation. If
the enqueue type shown is 'shared', then the file is the input file for a
backup or copy. If the type is 'exclusive', then the file is the output file
for a datafile copy or restore which is attempting to overwrite the currently
active version of that file - in this case, the file must be offline or the
database must be closed. If the type is 'read-only', then you are attempting to
back up or copy this file while the database is in NOARCHIVELOG mode.
Action: Wait until the conflicting
operation is complete, then retry the copy or backup. If the database is in
NOARCHIVELOG mode, then all files being backed up must be closed cleanly.
ORA-19574:
output file name must be specified
Cause: This type of copy or restore
requires an output file name.
Action: Specify an output file name
and retry the copy.
ORA-19575:
expected string blocks in file string, found string
Cause: During a backup, restore,
copy, or scan operation, the indicated file did not contain as many blocks as
were indicated in the file header.
Action: The input copy or backup piece
is probably corrupt. If another backup or copy exists of the file that is being
restored, then the corrupt file can be deleted from the recovery catalog and
the operation can be restarted.
ORA-19576:
datafile string not defined in control file
Cause: The specified file number was
not found in the control file.
Action: Specify a correct file number
and retry the operation.
ORA-19577:
file string is MISSING
Cause: A COPYDATAFILECOPY, RESTOREDATAFILETO
or PROXYRESTOREDATAFILE function specified a file number but no output file
name, indicating that the output file name should be taken from the control
file. However, the control file entry for this file indicates that it was
created for a file that was present in the data dictionary but not named during
the last CREATE CONTROLFILE statement, so the name in the control file cannot
be used for restoration.
Action: Either specify an output file
name or issue a SQL RENAME command to enter a valid name for this file in the
control file.
ORA-19578:
end of volume while duplexing to sequential files, backup piece incomplete
Cause: An end of volume (EOV)
condition was detected while duplexing to sequential files, and this condition
cannot be handled currently.
Action: Before retrying the backup,
make sure the backup pieces will fit in the volume, or disable duplexing.
ORA-19579:
archived log record for string not found
Cause: No archived log record
corresponding to input file could be found in the control file.
Action: Specify a valid archived log
file name and retry the operation.
ORA-19580: string conversation
not active
Cause: A backup or restore operation
was attempted before a conversation was started.
Action: Start a conversation then
retry the operation.
ORA-19581:
no files have been named
Cause: An attempt was made to proceed
from the file naming phase to the piece processing phase of a backup or restore
conversation before any files have been specified for backup or restore.
Action: Specify some files then retry
the operation.
ORA-19582:
archived log file header validation for string failed
Cause: Archived log file header is
corrupt and could not be validated.
Action: Provide a valid archived log
file and retry the operation.
ORA-19583:
conversation terminated due to error
Cause: An error occurred which forced
the termination of the current backup or restore conversation.
Action: There should be other error
messages to help identify the cause of the problem. Correct the error and begin
another conversation.
ORA-19584:
file string already in use
Cause: The indicated file, which was
specified as the target for a copy, restore, or delete operation is already in
use by the database.
Action: Specify a different name and
retry the operation.
ORA-19585:
premature end of volume on piece string
Cause: While creating the indicated
backup piece, an end-of-volume condition was encountered before all of the
backup set control data was written to the backup piece. This is most likely a
media error, because the amount of backup set control data is very small in
relation to the total amount of data in a backup set.
Action: Retry the piece with a larger
piece of output media.
ORA-19586: string k-byte
limit is too small to hold piece directory
Cause: The user-specified limit of
k-bytes per backup piece is not enough to hold the backup set control data.
Action: Use the SETLIMIT procedure to
increase the k-byte limit and retry the operation.
ORA-19587:
error occurred reading string bytes at block number string
Cause: An error occurred while
reading from a file.
Action: One or more other messages
should be displayed to help pinpoint the cause of the error. Correct the error
then retry the copy, backup, or restore operation.
ORA-19588: string RECID string STAMP string is
no longer valid
Cause: The indicated record has been
marked as deleted. This indicates that the corresponding file has either been
overwritten by another copy or restore, or that the copy was 'consumed' by a
SWITCHTOCOPY operation.
Action: If you know the name of the
file you wish to copy, then inspect it and then retry the copy specifying the
new RECID.
ORA-19589: string is
not a snapshot or backup control file
Cause: The control file that is the
source for a backup or copy operation is not a snapshot or backup control file.
Action: Specify the name of a snapshot
or backup control file.
ORA-19590:
conversation already active
Cause: You tried to begin a backup or
restore conversation, but another conversation is already active in this
session.
Action: Either continue the current
conversation, or call BACKUPCANCEL or RESTORECANCEL to end the current
conversation before starting a new one.
ORA-19591:
backup aborted because job time exceeded duration time
Cause: You tried to backup with
duration option and the time provided was not sufficient to complete the
backup.
Action: Adjust the duration time and
re-run the command. Or run the backup command without duration option.
ORA-19592:
wrong string conversation type
Cause: You attempted to specify a
type of file to be backed-up or restored, but the current conversation cannot
process this type of file. For example, you specified an archived log to be
included in a datafile backup set. The specified file will not be included in
the backup or restore operation.
Action: No action required - the
conversation is still active, and more files can be specified.
ORA-19593:
datafile number string already included as string
Cause: This datafile is already
specified for inclusion in this backup or restore conversation. A backup or
restore conversation may process only a single instance of a datafile.
Action: No action required - the
conversation is still active, and more files can be specified.
ORA-19594:
control file already included as string
Cause: The control file is already
specified for inclusion in this backup or restore conversation. A backup or
restore conversation may process only a single instance of the control file.
Action: No action required - the
conversation is still active, and more files can be specified.
ORA-19595:
archived log string already included in backup conversation
Cause: The indicated archived log has
already been specified for inclusion in this backup conversation.
Action: No action required - the
conversation is still active, and more files can be specified.
ORA-19596:
SPFILE already included
Cause: The SPFILE is already
specified for inclusion in this backup or restore conversation. A backup or
restore conversation may process only a single instance of the SPFILE.
Action: No action required - the
conversation is still active, and more files can be specified.
ORA-19597:
file string block size string does not match
set block size of string
Cause: A file was specified for
inclusion in a backup set but it has a logical block size different from the
rest of the files in the backup set. All files in a backup set must have the
same logical block size.
Action: Specify a file that has the
same block size as the rest of the files in the backup set. The conversation is
still active and more files can be specified.
ORA-19598:
can not backup SPFILE because the instance was not started with SPFILE
Cause: A backup command requested a
backup of the SPFILE, but no SPFILE was used to startup the instance.
Action: Create an SPFILE and re-start
the instance using the SPFILE.
ORA-19599:
block number string is corrupt in string string
Cause: A corrupt block was found in a
control file, archived log, or backup piece that is being read for a backup or
copy. Corruption shall not be tolerated in control files, archived logs, or
backup pieces.
Action: None. The copy or backup
operation fails. Note that in the case of a backup set, the conversation is
still active and the piece may be retried.
ORA-19600:
input file is string string (string)
Cause: This message identifies the
input file for a failed copy operation. Both the file number and name (if the
name has been determined) are shown. For a datafile, the file number refers to
the datafile's absolute file number as shown in the DBA_DATA_FILES view. For a
datafile copy, the file number refers to the copy's control file record number
as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log,
the file number refers to the log's control file record number as shown in the
RECID column of the V$ARCHIVED_LOG view.
Action: See other error message.
ORA-19601:
output file is string string (string)
Cause: This message identifies the
output file for a failed copy operation. The fields are as described in message
19600. When creating a new datafile copy, its control file record number may
not have been determined when the message is printed. In that case, the record
number shown is zero.
Action: See other error message.
ORA-19602:
cannot backup or copy active file in NOARCHIVELOG mode
Cause: You tried to copy or backup a
file that was not closed cleanly, and the database was in NOARCHIVELOG mode.
This is not allowed because when restored, the file will require redo
application before it is usable, and redo is not currently being saved beyond
the contents of the online redo logs.
Action: Take the tablespace offline
clean or close the database and retry the copy or backup.
ORA-19603:
cannot backup or copy active file with KEEP .. UNRECOVERABLE option
Cause: The user tried to copy or
backup a file that was not closed cleanly, with KEEP .. UNRECOVERABLE option.
This is not allowed because when restored, the file will require redo
application before it is usable, and redo will not be saved because of KEEP ..
UNRECOVERABLE option.
Action: Take the tablespace offline
cleanly, or close the database and retry the copy or backup.
ORA-19604:
conversation file naming phase is over
Cause: A call was made to specify a
file to be backed up or restored after the first backup piece has been
processed.
Action: You cannot specify more files
to be processed during a backup or restore conversation after the first backup
piece has been processed. If more files must be specified, you must begin a new
conversation.
ORA-19605:
input file name must be specified
Cause: The input file name was not
specified for a control file copy operation.
Action: Specify an input file name and
retry the operation.
ORA-19606:
Cannot copy or restore to snapshot control file
Cause: A control file copy or restore
operation specified the name of the snapshot control file as the output file.
It is not permitted to overwrite the snapshot control file in this manner.
Other methods are available to create the snapshot control file.
Action: Specify a different file name
and retry the operation. If this is a restore, then the restore conversation
remains active and more files may be specified.
ORA-19607: string is
an active control file
Cause: A control file copy, restore,
or backup specified the name of a control file named in the INIT.ORA file as
the input or output file.
Action: Specify a different file name
and retry the operation. If this is a backup or restore conversation, then the
conversation remains active and more files may be specified.
ORA-19608: string is
not a backup piece
Cause: The specified file is not a
backup piece produced by the DBMS_BACKUP_RESTORE package. Either the first
block of the backup piece is corrupt or this file is not a backup piece.
Action: Specify a different file name
and retry the operation.
ORA-19609: string is
from different backup set: stamp string count string
Cause: The specified file is not from
the backup set which is currently being processed. It is part of a different
backup set. The identification of the set containing this piece is shown.
Action: Specify the correct backup
piece and retry the operation.
ORA-19610:
directory block string is corrupt
Cause: The indicated directory block
failed checksum validation. This backup piece is unusable.
Action: Supply another copy of the
same backup piece, or terminate the restore conversation.
ORA-19611:
backup piece out of order. Expected string but found string
Cause: This backup piece is out of
sequence.
Action: Supply the correct backup
piece.
ORA-19612:
datafile string not restored due to string
Cause: The indicated file could not
be restored, because all of its data blocks were not found in the backup piece.
Action: The restore conversation
remains active, and the current piece must be re-processed. If the failure
cannot be resolved by re-processing the current piece, then the restore
conversation must be cancelled.
ORA-19613:
datafile string not found in backup set
Cause: The indicated file could not
be restored, because it is not in this backup set. If the file number is zero,
then this refers to the control file.
Action: This message is issued when
the directory from the first backup piece is read and one or more files named
for restoration were not found. The restore conversation is still active, but
no data has been read and you must supply the first backup piece of a backup
set that contains all of the requested files.
ORA-19614:
archived log thread string sequence string not
found in backup set
Cause: The indicated archived log
file was named explicitly for restoration but is not contained in this backup
set.
Action: This message is issued when
the directory from the first backup piece is read and one or more files named
for restoration were not found. The restore conversation is still active, but
no data has been read and you must supply the first backup piece of a backup
set that contains all of the requested files.
ORA-19615:
some files not found in backup set
Cause: Some files that were specified
for restoration were not found in the backup set directory. Message 19613 or
19614 is issued for each file that was not found.
Action: See the instructions for
message 19613.
ORA-19616:
output file name must be specified if database not mounted
Cause: A datafile restore specified
no target file name, but the database is not mounted. The database must be
mounted when no target file name is specified, so that the target file name can
be obtained from the control file.
Action: The restore conversation
remains active. If you wish to restore datafiles without their target file
names, then mount the database before continuing. Otherwise, a target file name
must be specified on all datafile restoration calls.
ORA-19617:
file string contains different RESETLOGS data
Cause: The indicated file contains
RESETLOGS data which is different from the archived log files which are already
included in the backup set. All archived log files in a backup set must have
the same RESETLOGS data.
Action: The restore conversation
remains active, and you may continue to specify archived log files for
inclusion in the backup set.
ORA-19618:
cannot name files after RESTOREVALIDATE has been called
Cause: A call was made to specify a
file to restore from a backup set, but a previous call to RESTOREVALIDATE has
already been made.
Action: You must cancel and restart
the conversation if you wish to specify files to restore.
ORA-19619:
cannot call RESTOREVALIDATE after files have been named
Cause: RESTOREVALIDATE was called
after some files had already been specified for restoration.
Action: You must cancel and restart
the conversation if you wish to call RESTOREVALIDATE.
ORA-19620: string is
not of string type
Cause: When opening the file to be
placed in a copy or backup set, to be inspected, or used as the target for an
incremental restore, its header was not recognized as a valid file header for a
file of the indicated type (datafile, archived log, or control file) belonging
to the current database.
Action: The indicated file cannot be
processed. Ensure that the correct files are being specified for the copy or
backup operation.
ORA-19621:
archived log range has already been specified
Cause: A range of logs has already
been specified. Only one SCN range may be specified per conversation.
Action: The restore conversation
remains active and more logs may be specified by thread and sequence number, if
desired.
ORA-19622:
archived log thread string sequence string not
restored due to string
Cause: The indicated file could not
be restored, because all of its data blocks were not found in the backup piece.
Action: The restore conversation
remains active, and the current piece must be re-processed. If the failure
cannot be resolved by re-processing the current piece, then the restore
conversation must be cancelled.
ORA-19623:
file string is open
Cause: A SWITCHTOCOPY operation
specified a datafile copy whose parent datafile is open.
Action: Take the owning tablespace
offline or close the database, then retry the operation.
ORA-19624:
operation failed, retry possible
Cause: A backup, restore or image
copy operation failed with an I/O error. If the source of the I/O error can be
corrected, then the operation may be retried.
Action: This message is used by
recovery manager to decide whether or not to retry the operation.
ORA-19625:
error identifying file string
Cause: A file specified as input to a
copy or backup operation, or as the target for an incremental restore, could
not be identified as an Oracle file. An OS-specific error accompanies this
error to help pinpoint the problem.
Action: Specify an different file and
retry the operation.
ORA-19626:
backup set type is string - can not be processed by this
conversation
Cause: The data in the backup set is
not compatible with the current conversation.
Action: Either supply the first piece
from a backup set that matches the current conversation or start a new restore
conversation which can process this backup set.
ORA-19627:
cannot read backup pieces during control file application
Cause: This is a control file restore
conversation, which is using the offline range information from one or more
control files to update datafile checkpoint data. Backup sets are not used
during this type of conversation.
Action: The conversation is still
active and more control files may be applied.
ORA-19628:
invalid SCN range
Cause: The starting SCN for
RESTOREREDOLOGRANGE is greater than the ending SCN.
Action: Specify a starting SCN which
is less than or equal to the ending SCN.
ORA-19629:
no files in specified archived log SCN range
Cause: This backup set contains no
files in the specified range.
Action: Either supply a backup set
that contains files in the correct range or start a new conversation and
specify a range which will select some files from this backup set.
ORA-19630:
end of volume encountered while copying backup piece
Cause: While copying a backup piece
from the OS native file system to an output device, the output device
encountered end-of-volume.
Action: The copy fails. This could
happen if a tape was used which is not large enough to hold the entire backup
piece.
ORA-19631:
archived log record contains no file name
Cause: This archived log record
represents a switch into an active log that took place without archiving its
prior contents. The prior contents of the log file are lost.
Action: Specify the RECID of an
archived log record that contains a file name. Fixed view v$archived_log can be
used to examine the archived logs.
ORA-19632:
file name not found in control file
Cause: The name passed to GETFNO was
not found in the control file.
Action: Supply a valid file name.
ORA-19633:
control file record string is out of sync with recovery
catalog
Cause: The control file record
describing the file to be deleted in a call to DELETEBACKUPPIECE,
DELETEDATAFILECOPY, PROXYDELETE or DELETEARCHIVEDLOG does not match the
validation data supplied by recovery manager.
Action: contact Oracle support
ORA-19634:
file name required for this function
Cause: The FNAME or HANDLE parameter
was not specified for DELETEPIECE, DELETEDATAFILECOPY, DELETEREDOLOG or
PROXYDELETE.
Action: Specify the FNAME or HANDLE
parameter when calling these functions.
ORA-19635:
input and output file names are identical: string
Cause: Identical input and output
file names were specified for a datafile copy operation.
Action: Specify an output file name
which is different from the input file name.
ORA-19636:
archived log thread string sequence string already
included
Cause: The indicated archived log has
already been specified for inclusion in this restore conversation. A restore
conversation may process only one copy of any archived log.
Action: No action required - the
conversation is still active, and more files can be specified.
ORA-19637:
BACKUPPIECECREATE requires file name when using DISK device
Cause: The session device is
currently allocated to disk, and so a file name is required.
Action: Supply a file name and retry
the operation.
ORA-19638:
file string is not current enough to apply this incremental
backup
Cause: The checkpoint of the target
for this incremental backup is less than the start of the incremental backup.
If this backup were applied, then any changes made between the datafile
checkpoint and the start of the incremental backup could be lost.
Action: Supply a backup set that can
be applied and retry the operation.
ORA-19639:
file string is more current than this incremental backup
Cause: The checkpoint of the target
for this incremental backup is greater than or equal to the checkpoint of the
file in the incremental backup set. This backup cannot advance the checkpoint
of the target file, so there is no point in applying it.
Action: Supply a backup set that can
be applied and retry the operation.
ORA-19640:
datafile checkpoint is SCN string time string
Cause: This message identifies the
datafile checkpoint for a datafile that was too old to take an incremental
backup from, or the target of an incremental restore that could not be applied.
Action: See other error message.
ORA-19641:
backup datafile checkpoint is SCN string time string
Cause: This message identifies the
checkpoint of a datafile in an incremental backup set that could not be applied.
Action: See other error message.
ORA-19642:
start SCN of incremental backup is string
Cause: This message identifies the
starting SCN of an incremental backup that could not be applied.
Action: See other error message.
ORA-19643:
datafile string: incremental-start SCN is too recent
Cause: The incremental-start SCN
which was specified when starting an incremental datafile backup is greater
than the datafile checkpoint SCN, which could cause some blocks to be missed.
Action: Specify a smaller incremental-start
SCN.
ORA-19644:
datafile string: incremental-start SCN is prior to RESETLOGS
SCN string
Cause: The incremental-start SCN
which was specified when starting an incremental datafile backup is less than
the RESETLOGS SCN.
Action: Specify a larger incremental-start
SCN.
ORA-19645:
datafile string: incremental-start SCN is prior to creation
SCN string
Cause: The incremental-start SCN
which was specified when starting an incremental datafile backup is less than
the datafile's creation SCN.
Action: Specify a larger
incremental-start SCN.
ORA-19646:
cannot change size of datafile string from string to string
Cause: Restore needs to adjust the
size of the file as indicated, but the file size adjustment failed.
Action: Examine the other messages
which should be present to indicate the cause of the failure.
ORA-19647:
non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
Cause: BACKUPSETDATAFILE was called
with a non-zero backup_level and a FALSE incremental indication.
Action: Either set incremental to TRUE
or change backup_level to zero.
ORA-19648:
datafile string: incremental-start SCN equals checkpoint SCN
Cause: The incremental-start SCN
which was specified when starting an incremental datafile backup is equal to
the datafile's checkpoint SCN. Since an incremental backup can only be applied
to a datafile whose checkpoint SCN is between the backup set incremental-start
SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no
datafile that this backup set could ever be applied to.
Action: Specify a smaller
incremental-start SCN. NOTE that this message will usually only be encountered
by the user while taking an incremental backup with Recovery Manager. Recovery
Manager should intercept all usual cases of this error and simply ignore the
incremental backup for this file. So, if you do encounter this error, please
report it to Oracle Support.
ORA-19649:
offline-range record RECID string STAMP string not
found in file string
Cause: APPLYOFFLINERANGE was called
with a RECID/STAMP which was not found in the indicated control file. This
probably means that the specified control file is no longer the same control
file that Recovery Manager thinks it is.
Action: Specify the RECID/STAMP of a
record that exists in the control file copy.
ORA-19650:
Offline-range record RECID string STAMP string in
file string has SCN string
Cause: This messages identifies the
offline-clean SCN from the indicated offline-range record in the indicated
file.
Action: See other error message.
ORA-19651:
cannot apply offline-range record to datafile string: SCN mismatch
Cause: APPLYOFFLINERANGE cannot apply
an offline-range record to a target datafile unless the datafile's checkpoint
SCN exactly matches the offline-clean SCN in the specified offline-range
record.
Action: Specify an offline-range
record whose offline-clean SCN matches the target datafile's checkpoint.
ORA-19652:
cannot apply offline-range record to datafile string: file is fuzzy
Cause: The target datafile for an
APPLYOFFLINERANGE call is fuzzy.
Action: Specify a target datafile that
is closed cleanly.
ORA-19653:
cannot switch to older file incarnation
Cause: SWITCHTOCOPY was called with a
datafile copy for a datafile that was dropped prior to the time this control
file was backed up.
Action: Restore and mount an earlier
control file. It is acceptable to use a control file that was backed up prior
to the creation of the specified datafile.
ORA-19654:
must use backup control file to switch file incarnations
Cause: This SWITCHTOCOPY operation is
attempting to switch incarnations of a datafile, but the currently mounted
control file is not a backup control file.
Action: Restore and mount a backup
control file.
ORA-19655:
cannot switch to incarnation with different RESETLOGS data
Cause: This SWITCHTOCOPY operation is
attempting to switch to a datafile which comes from a different RESETLOGS
version of the database.
Action: Either restore a backup
control file that was taken from the same database version as the target
datafile copy, or switch to a different datafile copy.
ORA-19656:
cannot backup, copy, or delete online log string
Cause: The indicated log file is an
active log. You can only backup, copy, or delete archived logs.
Action: The indicated log file cannot
be processed - select another file.
ORA-19657:
cannot inspect current datafile string
Cause: The file being inspected is
already part of the currently mounted database.
Action: None - the file is already
part of the database.
ORA-19658:
cannot inspect string - file is from different RESETLOGS
Cause: The RESETLOGS data in the log
file being inspected does not match that in the currently mounted control file.
Action: The indicated file cannot be
processed - inspect another file.
ORA-19659:
incremental restore would advance file string past RESETLOGS
Cause: This incremental backup cannot
be applied to the specified datafile, because the datafile is from an earlier
incarnation of the database, and its checkpoint would be advanced too far to be
recoverable in the current incarnation of the database.
Action: This incremental cannot be
applied to this datafile. If you wish to recover the file to the RESETLOGS SCN
so that the database can be opened with the RESETLOGS option, then you must use
redo-log recovery, not incremental restore, to continue recovering this file.
ORA-19660:
some files in the backup set could not be verified
Cause: A restore conversation was
made to verify all the files in a backup set, and the files which were printed
in messages 19661 or 19662 could not be verified because corrupt blocks for
those files were found in the backup set.
Action: Unless the damage to the
backup set can be repaired, the indicated files cannot be restored from this
backup set.
ORA-19661:
datafile string could not be verified
Cause: Some data blocks for the
indicated datafile were corrupt in the backup set.
Action: Unless the damage to the
backup set can be repaired, the indicated datafile cannot be restored from this
backup set.
ORA-19662:
archived log thread string sequence string could
not be verified
Cause: Some data blocks for the
indicated archived log were corrupt in the backup set.
Action: Unless the damage to the
backup set can be repaired, the indicated archived log cannot be restored from
this backup set.
ORA-19663:
cannot apply current offline range to datafile string
Cause: An attempt was made to apply
the current offline range to the specified datafile, but the datafile is either
not current enough or is not at the correct SCN to apply the offline range.
Action: The datafile remains
unchanged.
ORA-19664:
file type: string, file name: string
Cause: This message is issued to
identify the file which is the subject of an error.
Action: None - this is an
informational message. There should be other Oracle messages explaining the
cause of the error.
ORA-19665:
size string in file header does not match actual file size
of string
Cause: The size of the file as
indicated in the file header does not match the true size of the file. The two
differing sizes are shown in units of logical blocks.
Action: This file is not usable - it
has most likely been truncated.
ORA-19666:
cannot do incremental restore of the control file
Cause: The control file was included
in an incremental restore conversation
Action: If you wish to restore the
control file, you must do a full restore of the control file
ORA-19667:
cannot do incremental restore of datafile string
Cause: The backup of the datafile is
a full backup
Action: If you wish to restore the
datafile, you must do a full restore of the datafile
ORA-19668:
cannot do full restore of datafile string
Cause: The backup of the datafile is
an incremental backup
Action: If you wish to restore the
datafile, you must do an incremental restore of the datafile
ORA-19669:
proxy copy functions cannot be run on DISK channel
Cause: A proxy copy procedure was
called, but the device which is allocated to the current session has type DISK.
Action: Allocate a non-DISK channel
and retry the operation. Note that proxy copy requires a 3rd-party media
management software product that supports the this backup/restore feature.
ORA-19670:
file string already being restored
Cause: A proxy restore function has
already named this file as a restore destination.
Action: Use a different file name. If
this message occurs during a recovery manager job, then this is an internal
error in recovery manager, and you should contact Oracle support.
ORA-19671:
media management software returned invalid proxy handle
Cause: During a proxy backup or
restore, the media management software returned an invalid file handle.
Action: This is an internal error in
the media management software which is linked with Oracle to provide
backup/restore services. Contact the media management software vendor.
ORA-19672:
media management software returned invalid file status
Cause: During a proxy backup or
restore, the media management software returned an invalid file status.
Action: This is an internal error in
the media management software which is linked with Oracle to provide
backup/restore services. Contact the media management software vendor.
ORA-19673:
error during proxy copy of file string
Cause: During a proxy backup or
restore, an error occurred while copying this file, but other files may have
been copied successfully.
Action: There should be other errors
on the error stack which explain why the file could not be successfully copied.
ORA-19674:
file string is already being backed up with proxy copy
Cause: Recovery manager attempted to
back up the specified file with proxy copy, but the file is already being
backed up by another recovery manager job.
Action: Wait until the other recovery
manager backup of this file is complete, then retry the backup.
ORA-19675:
file string was modified during proxy copy
Cause: A proxy backup of the
specified file failed because the file was brought on-line or otherwise
modified while the proxy backup was in progress. This file was off-line or
read-only when the backup began, so the file was not put into hot-backup mode,
therefore no modifications are permitted while the backup is in progress.
Action: Take another backup of this
file.
ORA-19676:
one or more files failed during proxy backup or restore
Cause: During a proxy backup or
restore, errors were encountered while processing some files. The files for
which no error messages are shown were processed successfully.
Action: Examine the messages regarding
the specific files to determine the cause of the problems.
ORA-19677:
RMAN configuration name exceeds maximum length of string
Cause: The configuration name string
exceeds maximum length.
Action: Supply a correct configuration
name and retry the function.
ORA-19678:
RMAN configuration value exceeds maximum length of string
Cause: The configuration value string
exceeds maximum length.
Action: Supply a correct configuration
value and retry the operation.
ORA-19679:
RMAN configuration number string is outside valid range of 1
through string
Cause: An invalid RMAN Configuration
number was specified.
Action: Specify a correct datafile
number and retry the operation.
ORA-19680:
some blocks not recovered. See trace file for details
Cause: Some blocks are not recovered
during block media recovery.
Action: See trace files for details of
the problem.
ORA-19681:
block media recovery on control file not possible
Cause: file number 0 specified in
block media recovery
Action: check file number
ORA-19682:
file string not in block media recovery context
Cause: Internal error
Action: None
ORA-19683:
real and backup block size of file string are unequal
Cause: block size changed between
backup & real file
Action: use right backup
ORA-19684:
block media recovery failed because database is suspended
Cause: Database is suspended,
probably by an ALTER SYSTEM SUSPEND statement
Action: Execute ALTER SYSTEM RESUME
then retry block media recovery
ORA-19685:
SPFILE could not be verified
Cause: Some data blocks for the
SPFILE were corrupt in the backup set.
Action: Unless the damage to the
backup set can be repaired, the SPFILE cannot be restored from this backup set.
ORA-19686:
SPFILE not restored due to string
Cause: The indicated file could not
be restored, because some of its data blocks were not found in the backup
piece.
Action: Unless the damage to the
backup set can be repaired, the SPFILE cannot be restored from this backup set.
ORA-19687:
SPFILE not found in backup set
Cause: The SPFILE could not be
restored, because it is not in this backup set.
Action: This message is issued when
the directory from the first backup piece is read and one or more files named
for restoration were not found in the piece. You must supply the first backup
piece of a backup set that contains the requested file.
ORA-19688:
control file AUTOBACKUP format(string) for string does
not have %F
Cause: control file AUTOBACKUP format
must contain %F for the device.
Action: Change control file format
using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE
TO .
ORA-19689:
cannot have more than one %F in control file AUTOBACKUP format(string)
for string
Cause: control file AUTOBACKUP format
contains more than one %F for the device.
Action: Change control file format
using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE
TO .
ORA-19690:
backup piece release string incompatible with Oracle
release string
Cause: The backup piece was created
by incompatible software.
Action: Either restart with a
compatible software release or create another backup using the current release.
ORA-19691: string is
from different database: id=string, name=string
Cause: The database name or database
id in backup piece header does not match the one in control file.
Action: Supply the correct backup
piece belonging to this database.
ORA-19692:
missing creation stamp on piece string
Cause: The backup piece doesn't have
information about creation stamp.
Action: Supply another backup piece
which is created by oracle 9i or later version.
ORA-19693:
backup piece string already included
Cause: This backup piece was already
specified for inclusion in the restore conversation. A restore conversation may
process only a single instance of a backup piece.
Action: Remove the specified duplicate
backup piece in restore steps and restart the conversation.
ORA-19694:
some changed blocks were not found in the change tracking file
Cause: A backup or copy found that
some changed blocks had not been recorded in the change tracking file. The
details of which files and blocks are affected will be in an Oracle trace file.
Action: This indicates that there is a
problem with the change tracking feature. Disable change tracking and re-start
the backup.
ORA-19695:
fixed table X$KRBMSFT has not been populated
Cause: This is an internal error. The
fixed table X$KRBMAFT was not populated using the function
DBMS_BACKUP_RESTORE.SEARCHFILES.
Action: Internal error - contact
Oracle Customer Support.
ORA-19696:
control file not found in backup set
Cause: The control file could not be
restored because it is not in this backup set.
Action: This message is issued when
the directory from the first backup piece is read and one or more files named
for restoration were not found in the piece. You must supply the first backup
piece of a backup set that contains the requested file.
ORA-19697:
standby control file not found in backup set
Cause: The standby control file could
not be restored because it is not in this backup set.
Action: This message is issued when
the directory from the first backup piece is read and one or more files named
for restoration were not found in the piece. You must supply the first backup
piece of a backup set that contains the requested file.
ORA-19698: string is
from different database: id=string, db_name=string
Cause: Catalog failed because the
database id in file header does not match the one in control file.
Action: Supply the correct file
belonging to this database.
ORA-19699:
cannot make copies with compression enabled
Cause: Datafile copies with
compression are not supported.
Action: If the function
DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called outside RMAN, then the
incompatible values are being passed for the parameters DOCOMPRESS and IMAGCP.
If this message occurs during an RMAN job, then this is an internal error in
RMAN, and you should contact Oracle support.
ORA-19700:
device type exceeds maximum length of string
Cause: The device type indicated is invalid.
Action: Supply a correct device type
and retry the allocation.
ORA-19701:
device name exceeds maximum length of string
Cause: The device name indicated is
invalid.
Action: Supply a correct device name
and retry the allocation.
ORA-19703:
device command string exceeds maximum length of string
Cause: The device command string
exceeds maximum length.
Action: Correct the command and retry
the operation.
ORA-19704:
file name exceeds maximum length of string
Cause: The specified file name, which
was a parameter to a copy, backup, or restore operation, exceeds the maximum
file name length for this operating system.
Action: Retry the operation with a
shorter file name.
ORA-19705:
tag value exceeds maximum length of string characters
Cause: During a backup or copy
operation, the user supplied a tag value too long to fit in the file header.
Action: Supply a shorter tag and retry
the operation.
ORA-19706:
invalid SCN
Cause: The input SCN is either not a
positive integer or too large.
Action: Check the input SCN and make
sure it is a valid SCN.
ORA-19707:
invalid record block number - string
Cause: The input number is either
negative or too large.
Action: Check the input record block
number and make sure it is a valid number clauses in the create database statement.
ORA-19708:
log destination exceeds maximum length of string characters
Cause: When starting a restore
conversation, the user specified a log restore destination longer than the
port-specific maximum.
Action: Supply a shorter destination
and retry the operation.
ORA-19709:
numeric parameter must be non-negative integer
Cause: A numeric parameter to an
DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.
Action: Supply a valid numeric
parameter.
ORA-19710:
unsupported character set string
Cause: When the target database is
not mounted, RMAN sets the target database character set to the value specified
in the users environment.
Action: Specify a valid character set
in the environment. This is usually done via the NLS_LANG environment variable.
ORA-19711:
cannot use RENORMALIZEALLFILENAMES while database is open
Cause: An attempt was made to
re-normalize all the file names in the control file while the database is open.
Action: Close the database before
using the RENORMALIZEALLFILENAMES procedure.
ORA-19712:
table name exceeds maximum length of string
Cause: The table name string exceeds
maximum length.
Action: Retry the operation with a
shorter table name.
ORA-19713:
invalid copy number: string
Cause: The copy number is not in a
valid range or you have reached maximum limit.
Action: Report the error and other
information to support.
ORA-19714:
length for generated name longer than string
Cause: The specified format exceeds
the maximum length for the piece name.
Action: Change the format to create
shorter piece names.
ORA-19715:
invalid format string for generated name
Cause: A restricted format or
undefined format was used incorrectly.
Action: Change the format specified in
the additional information by removing the restricted format.
ORA-19716:
error processing format string to generate name for backup
Cause: There were errors while
processing the format to generate name for backup.
Action: Change the format.
ORA-19717:
for non-OMF search the pattern must be specified
Cause: The procedure
DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the
parameter OMF was set to FALSE.
Action: Either specify the pattern or
set the parameter OMF to TRUE.
ORA-19718:
length for command id longer than string
Cause: The specified command id
exceeds the maximum length for command id.
Action: Supply a shorter command id
and retry the operation.
ORA-19719:
length for operation name longer than string
Cause: The specified operation name
exceeds the maximum length for operation name.
Action: Supply a shorter operation
name and retry the operation.
ORA-19720:
Error occurred when converting an OCI number into an SCN
Cause: This is most likely caused by
an invalid SCN number that came from an external file, such as an export file.
Action: See other errors on the error
stack to look for the source of the problem.
ORA-19721:
Cannot find datafile with absolute file number string in
tablespace string
Cause: Can not find one of the
datafile that should be in the Pluggable Set.
Action: Make sure all datafiles are
specified via import command line option or parameter files.
ORA-19722:
datafile string is an incorrect version
Cause: The datafile is an incorrect
version. It contains either less or more changes then the desired version.
Action: Make sure the right datafiles
are transported. Make sure the datafile is copied while its tablespace is read
only.
ORA-19723:
Cannot recreate plugged in read-only datafile string
Cause: The datafile is plugged in
read only. It can not recreated.
Action: Use ALTER DATABASE RENAME FILE
command instead.
ORA-19724:
snapshot too old: snapshot time is before file string plug-in
time
Cause: The snapshot SCN is before the
SCN at which the referred datafile is plugged into the database.
Action: retry the query.
ORA-19725:
can not acquire plug-in enqueue
Cause: There maybe another
"ALTER DATABASE RESET COMPATIBILITY" command issued concurrently,
preventing this process from acquiring the plug-in enqueue.
Action: retry the operation.
ORA-19726:
cannot plug data [string] at level string into database
running at compatibility level string
Cause: Some of the data in the
pluggable set requires a compatibility level higher than what is currently
allowed by the database. The string in square bracket is the name of the
compatibility type associated with the data.
Action: Raise the
"compatible" init.ora parameter and retry the operation.
ORA-19727:
cannot plug data [string] at level string into database
running Oracle string
Cause: Some of the data in the
pluggable set requires a compatibility level higher than the release level of
the Oracle executable. The string in square bracket is the name of the
compatibility type associated with the data.
Action: Upgrade Oracle and retry the
operation.
ORA-19728:
data object number conflict between table string and
partition string in table string
Cause: The non-partitioned table has
the same data object number as one of the partitions in the partitioned table.
One can not exchange the table with the partition in this case.
Action: Use "alter table move
partition" command to move the offending partition, so that the partition
will get a new data object number. Retry the operation then.
ORA-19729:
File string is not the initial version of the plugged in
datafile
Cause: The file is not the initial
version of the plugged in datafile.
Action: Use the correct initial
version of the plugged in datafile.
ORA-19730:
can not convert offline plugged-in datafile string
Cause: As part of making a tablespace
read-write, we need to convert datafiles that are plugged in read-only. The
file must be online.
Action: Online the datafile and retry
the operation.
ORA-19731:
cannot apply change to unverified plugged-in datafile string
Cause: Recovery was not able to
verify the referred datafile according to information in the control file.
Before encountering this change vector for this file, somehow recovery did not
encounter the file conversion redo that is supposed to verify the file. This
may happen due to corrupted or incorrect control file used for media recovery.
Action: Use the correct control file
and continue recovery.
ORA-19732:
incorrect number of datafiles for tablespace string
Cause: d by a user editing the export
file.
Action: Use the correct export file
and retry the operation.
ORA-19733:
COMPATIBLE parameter needs to be string or greater
Cause: The COMPATIBLE initialization
parameter is not high enough to allow the operation. Allowing the command would
make the database incompatible with the release specified by the current
COMPATIBLE parameter.
Action: Shutdown and startup with a
higher compatibility setting.
ORA-19734:
wrong creation SCN - control file expects converted plugged-in datafile
Cause: When a tablespace is plugged
into a database, the tablespace is initially read-only. Oracle converts the
header of the plugged-in datafiles (assign them a new creation SCN) when the
tablespace is first made read-write. This error occurs when the creation SCN in
the file header is different from the creation SCN in the control file, possibly
because this is the initial version of plugged-in datafile.
Action: Either restore the converted
datafile or continue recovering the datafile.
ORA-19735:
wrong creation SCN - control file expects initial plugged-in datafile
Cause: When a tablespace is plugged
into a database, the tablespace is initially read-only. Oracle converts the
header of the plugged-in datafiles (assign them a new creation SCN) when the
tablespace is first made read-write. This error occurs when the creation SCN in
the file header is different from the creation SCN in the control file,
possibly because this is the converted datafile.
Action: Either restore the initial
version of the plugged-in datafile, or continue database recovery, which will
recover the control file.
ORA-19736:
can not plug a tablespace into a database using a different national character
set
Cause: Oracle does not support
plugging a tablespace into a database using a different national character set.
Action: Use import/export or
unload/load to move data instead.
ORA-19738:
cannot find language information for character set: 'string'
Cause: The compatibility check failed
because a character set name that was provided is not valid.
Action: Correct the character set name
and retry.
ORA-19740:
text is longer than string
Cause: The specified text exceeds the
maximum length for text.
Action: Supply a shorter text and
retry the operation.
ORA-19750:
change tracking file: 'string'
Cause: This message reports the name
of a file involved in other messages.
Action: See associated error messages
for a description of the problem.
ORA-19751:
could not create the change tracking file
Cause: It was not possible to create
the change tracking file.
Action: Check that there is sufficient
disk space and no conflicts in file names and try to enable block change
tracking again.
ORA-19752:
block change tracking is already enabled
Cause: The ALTER DATABASE ENABLE
BLOCK CHANGE TRACKING command was issued, but block change tracking is already
turned on for this database.
Action: None, this is an informative
message only.
ORA-19753:
error writing to change tracking file
Cause: An I/O error occurred while
writing to the change tracking file.
Action: There will be other messages
on the error stack that show details of the problem.
ORA-19754:
error reading from change tracking file
Cause: An I/O error occurred while
reading from the change tracking file.
Action: There will be other messages
on the error stack that show details of the problem.
ORA-19755:
could not open change tracking file
Cause: The change tracking file could
not be opened.
Action: There will be other messages
on the error stack that show details of the problem.
ORA-19756:
corrupt block number string found in change tracking file
Cause: The specified block number is
corrupt in the change tracking file.
Action: There will be other messages
on the error stack that show details of the problem. There will also be a trace
file that contains a complete dump of the corrupt block.
ORA-19757:
could not resize change tracking file to string blocks
Cause: An error occurred while trying
to change the size of the change tracking file.
Action: There will be other messages
on the error stack that show details of the problem.
ORA-19758:
failed to enable/disable block change tracking: out of SGA memory
Cause: out of SGA memory
Action: Increase SGA and restart the
instance.
ORA-19759:
block change tracking is not enabled
Cause: A command was entered that
requires block change tracking to be enabled, but block change tracking is not
enabled.
Action: None, this is an informative
message only.
ORA-19760:
error starting change tracking
Cause: Change tracking is enabled,
but a problem was encountered while enabling the change tracking subsystem in
this instance. The alert log and the trace file from the CTWR process will
contain more information about the error.
Action: Examine the trace and alert
files. Correct the error if possible, otherwise disable change tracking.
ORA-19761:
block size string is not valid for change tracking file
Cause: While opening the specified
change tracking file, it was found that the file header did not contain a valid
logical block size. This probably means that the file is corrupt.
Action: If the file can be repaired,
do so, otherwise disable and re-enable change tracking to re-initialize the
file.
ORA-19762:
invalid file type string
Cause: An invalid file type was found
in the change tracking file. Some other file was put in place of the change
tracking file, or the file is corrupt.
Action: Disable then re-enable change
tracking.
ORA-19763:
compatibility version string is higher than maximum
allowed: string
Cause: The compatibility version in
the change tracking file is greater than what can be used by the current
release of Oracle. This can happen when you upgrade, use change tracking with a
new release, then downgrade.
Action: Disable then re-enable change
tracking.
ORA-19764:
database id string does not match database id string in
control file
Cause: The change tracking file is
not the correct one for this database. This can happen when the database ID for
this database has been changed.
Action: Disable then re-enable change
tracking.
ORA-19765:
mount id string does not match mount id string in
control file
Cause: d by having a change tracking
file that cannot be consistently updated by all instances.
Action: In RAC, ensure that the name
specified for the change tracking file truly represents the same disk location
for all nodes in the cluster. Disable then re-enable change tracking.
ORA-19766:
missing CHANGE keyword
Cause: Syntax error.
Action: Use the correct syntax:
ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19767:
missing TRACKING keyword
Cause: Syntax error.
Action: Use the correct syntax:
ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19768:
USING clause only valid with ENABLE CHANGE TRACKING
Cause: The USING clause was specified
with DISABLE CHANGE TRACKING
Action: Correct the statement.
ORA-19769:
missing FILE keyword
Cause: Syntax error.
Action: Use the correct syntax:
ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19770:
invalid change tracking file name
Cause: The USING clause was specified
with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.
Action: Specify the change tracking
file name, or omit the USING clause to allow Oracle to create a default name
for the change tracking file.
ORA-19771:
cannot rename change tracking file while database is open
Cause: The ALTER DATABASE RENAME FILE
command was used to rename the change tracking file, and the database is open
by one or more instances. The database must be mounted, and not open, to rename
the change tracking file.
Action: Close the database and reissue
the command.
ORA-19772:
change tracking file name exceeds limit of string characters
Cause: The name specified for the
change tracking file is too long.
Action: Specify a shorter change
tracking file name.
ORA-19773:
must specify change tracking file name
Cause: No file name was specified
with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the
DB_CREATE_FILE_DEST parameter was not set.
Action: Either specify a file name, or
set the DB_CREATE_FILE_DEST parameter.
ORA-19776:
PROXY restore to ASM disk group "string" is not supported.
Cause: An attempt was made to proxy
restore a file to ASM disk group using RMAN command. This is not supported.
Action: Use a different file name and
reissue RMAN command.
ORA-19777:
ASM file string cannot be proxy backed up.
Cause: An attempt was made to proxy
backup a ASM file. This is not supported.
Action: Use a different file name and
reissue RMAN command.
ORA-19779:
could not obtain resilvering status for change tracking file
Cause: An error occurred while
obtaining the mirror resilvering status of the change tracking file.
Action: Refer to other error messages
shown for additional details of the problem.
ORA-19800:
Unable to initialize Oracle Managed Destination
Cause: The name given for an Oracle
managed files destination cannot be initialized.
Action: , if possible, and retry the
command or use a different name for destination.
ORA-19801:
initialization parameter DB_RECOVERY_FILE_DEST is not set
Cause: An attempt was made to create
a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There
are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n
parameter was specified using a LOCATION attribute whose value was
DB_RECOVERY_FILE_DEST and an archived log file creation was attempted. 2)
STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose
value was DB_RECOVERY_FILE_DEST and an archived log file creation was
attempted.
Action: Specify a valid destination
for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER
SYSTEM SET command.
ORA-19802:
cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
Cause: There are two possible cause
for this error: 1) The DB_RECOVERY_FILE_DEST parameter was in use when no
DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching
initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST
with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use.
Action: Correct the dependency
parameter definitions and retry the command.
ORA-19803:
Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)
Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE
specified was not valid.
Action: Specify a valid number within
the range.
ORA-19804:
cannot reclaim string bytes disk space from string limit
Cause: Oracle cannot reclaim disk
space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.
Action: There are five possible
solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider
changing RMAN retention policy. 3) Consider changing RMAN archived log deletion
policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete
files from recovery area using RMAN.
ORA-19805:
RECID string of string was deleted to reclaim
disk space
Cause: The file described by the
record in control file was deleted in order to reclaim disk space from flash
recovery area for other operations.
Action: Wait and try again.
ORA-19806:
cannot make duplex backups in recovery area
Cause: Duplex backup to recovery area
is not supported.
Action: Remove duplex option and try
again.
ORA-19808:
recovery destination parameter mismatch
Cause: The value of parameters
DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all
instances. instance. All databases must have same recovery destination
parameters.
Action: Check DB_RECOVERY_FILE_DEST
and DB_RECOVERY_FILE_DEST_SIZE values in all instances.
ORA-19809:
limit exceeded for recovery files
Cause: The limit for recovery files
specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.
Action: The error is accompanied by
19804. See message 19804 for further details.
ORA-19810:
Cannot create temporary control file string in
DB_RECOVERY_FILE_DEST
Cause: An attempt was made to create
a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.
Action: Retry the operation with a new
file name.
ORA-19811:
cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
Cause: An attempt was made to 1)
Create a backup piece or image copy in the recovery area with KEEP option. 2)
Update the KEEP attributes of an existing backup piece or image copy in the
recovery area.
Action: Reissue RMAN command without
KEEP options.
ORA-19812:
cannot use string without DB_RECOVERY_FILE_DEST
Cause: There are three possible cause
for this error: 1) The indicated parameter was in use when no
DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization
parameter. 2) An attempt was made to set indicated the parameter with the ALTER
SYSTEM command when no DB_RECOVERY_FILE_DEST was in use. 3) An attempt was made
to clear DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated
parameter was in use.
Action: Eliminate any incompatible
parameter definitions.
ORA-19813:
cannot have unavailable file string in DB_RECOVERY_FILE_DEST
Cause: An attempt was made to change
a backup piece or image copy in recovery area to UNAVAILABLE.
Action: Correct and resubmit the RMAN
command. Do not use messages 19814; it is used for simulating crash.
ORA-19815:
WARNING: string of string bytes is string%
used, and has string remaining bytes available.
Cause: DB_RECOVERY_FILE_DEST is
running out of disk space.
Action: One of the following:
1. Add disk
space and increase DB_RECOVERY_FILE_DEST_SIZE.
2. Backup
files to tertiary device using RMAN.
3. Consider
changing RMAN retention policy.
4. Consider
changing RMAN archived log deletion policy.
5. Delete
files from recovery area using RMAN.
ORA-19816:
WARNING: Files may exist in string that are not known to
database.
Cause: One of the following events
caused this:
1. A
database crash happened during file creation.
2. A backup
control file was restored.
3. The control
file was re-created.
4.
DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.
Action: Use RMAN command CATALOG
RECOVERY AREA to re-catalog any such files. If the file header is corrupted,
then delete those files using an OS utility. Do not use messages 19817; it is
used for simulating lock failure Do not use messages 19818; it is used for
space reclamation before backup Do not use messages 19819; it is used to
disable clearing file name
ORA-19830:
error from target database: string
Cause: This error should be followed
by other errors indicating the cause of the problem.
Action: No action required.
ORA-19831:
incompatible string.string.string.string DBMS_BACKUP_RESTORE
package: string.string.string.string required
Cause: This version of database was
incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in
the database.
Action: If the database has been
upgraded from an earlier version, ensure that the catxxxx.sql script has been
run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary.
ORA-19851:
OS error while managing auxiliary database string
Cause: An OS error was received while
managing the automatic auxiliary instance.
Action: Check the accompanying errors.
ORA-19852:
error creating services for auxiliary instance string (error string)
Cause: An error was received while
managing the services of the auxiliary instance.
Action: Check the accompanying errors.
ORA-19853:
error preparing auxiliary instance string (error string)
Cause: An error was received while
managing the automatic auxiliary instance.
Action: Check the accompanying errors.
ORA-19854:
error obtaining connect string from target
Cause: Could not obtain the connect
string from the target database
Action: Check the accompanying errors.
ORA-19860:
piece validation cannot be performed more than once
Cause: The user attempted to validate
a list of backup pieces more than once. Validation may only be performed once
for a given validation conversation.
Action: Do not attempt to validate the
pieces more than once.
ORA-19861:
additional backup pieces cannot be validated in this conversation
Cause: The user tried to add new
pieces to the list of files being validated after the validation had already
been performed. In a validation conversation, the list can only be validated
once.
Action: Add all the backup pieces to
the list before validating, or start a new validation conversation for the
remaining pieces.
ORA-19862:
backup pieces must be validated before accessing results
Cause: The user tried to get
validation results for backup pieces before the pieces were actually validated.
Action: Validate the pieces before
trying to access the results.
ORA-19863:
device block size string is larger than max allowed: string
Cause: The user specified a device
BLKSIZE that is larger than the device BLKSIZE specified during compressed
backup.
Action: Change the device BLKSIZE to
be smaller than the maximum allowed.
ORA-19865:
Backup piece string has no data
Cause: No data was returned for the
specified backup piece.
Action: This normally indicates a
problem with the media management software which is linked with Oracle to
provide backup and restore services. Contact the media management software
vendor.
ORA-19866:
error writing file header for datafile string
Cause: During a block recovery, the
header of the datafile could not be updated.
Action: Contact Oracle Support
Services.
ORA-19870:
error while restoring backup piece string
Cause: This error should be followed
by other errors indicating the cause of the problem.
Action: See other errors actions.
ORA-19873:
cannot apply this backup section to file string
Cause: RMAN cannot restore a
multi-section backup to the indicated file, because this section is not a
backup of this file, or the file was not prepared correctly for this restore.
Action: If this error occurs while
running RMAN, then it is an internal error and you should contact Oracle
support.
ORA-19874:
cannot finish multi-section restore to file string
Cause: During a multi-section
restore, the file being restored is not a file in which a multi-section restore
is in progress.
Action: If this error occurs while
running RMAN, then it is an internal error and you should contact Oracle
support.
ORA-19875:
multi-section restore not complete for file string
Cause: While completing a
multi-section restore, it was found that all required sections for this file
were not correctly applied.
Action: If this error occurs while
running RMAN, then it is an internal error and you should contact Oracle
support.
ORA-19880:
Corrupted space header for datafile string, block string
Cause: When reading the space header
block to use Unused Block Optimization for the backup of the datafile, the
space header block had corrupted information.
Action: The corrupt space header must
be fixed before Unused Block Optimization can be used for this file. Note that
you should fix the corruption in any case because it will affect the
availability of the data in the file, beyond just taking backups.
ORA-19881:
Corrupted space bitmap for datafile string, block string
Cause: When reading a space bitmap
block to use Unused Block Optimization for the backup of the datafile, the
space bitmap block had corrupted information.
Action: The corrupt space bitmap must
be fixed before Unused Block Optimization can be used for this file. Note that
you should fix the corruption in any case because it will affect the
availability of the data in the file, beyond just taking backups.
ORA-19882:
datafile string checkpoint string is ahead of
space bitmap datafile string checkpoint string
Cause: When checkpointing the
datafile containing the space bitmaps for the datafile being backed up in order
to use Unused Block Optimization, the checkpoint of the datafile containing the
space bitmaps did not advance.
Action: Examine the trace and alert
files for possible causes. Fix underlying problem to use Unused Block
Optimization for datafile's backup.
ORA-19883:
Unused Block Optimization stopped for datafile string
Cause: Accompanying errors detail the
problem that prevented Unused Block Optimization from being used.
Action: See accompanying errors for
appropiate action.
ORA-19900:
RESETLOGS must be specified after recovery to new incarnation
Cause: Recovery was done to an
incarnation after changing the destination incarnation using RMAN's RESET
DATABASE command.
Action: Open the database with the
RESETLOGS option.
ORA-19901:
database needs more recovery to create new incarnation
Cause: Recovery was done to an
incarnation after changing the destination incarnation using RMAN's RESET
DATABASE command, but one or more of the recovered datafiles still belongs to
the parent incarnation. This usually happens when recovery is ended before any
logs from the desired incarnation have been applied.
Action: Continue recovery.
ORA-19902:
incarnation key string not found
Cause: The specified incarnation was
not found in the control file.
Action: Resubmit request with known
incarnation key. To see which incarnations are available for this target
database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
ORA-19903:
test recovery not allowed when recovering to new incarnation
Cause: Either a new incarnation was
set using RMAN's RESET DATABASE command for a control file that was CURRENT, or
the control file is from a prior incarnation. As recovery to a new incarnation
requires changing the control file, test recovery is not allowed.
Action: Perform actual recovery or
RESET DATABASE to incarnation that was last opened using the control file to do
test recovery.
ORA-19904:
test recovery not allowed for datafile string
Cause: The specified datafile has
been restored from a backup that was taken before the last RESETLOGS.
Recovering this datafile will require a file header update that is incompatible
with test recovery.
Action: Perform actual recovery.
ORA-19905:
log_archive_format must contain %s, %t and %r
Cause: log_archive_format is missing
a mandatory format element. Starting with Oracle 10i, archived log file names
must contain each of the elements %s(sequence), %t(thread), and %r(RESETLOGS
ID) to ensure that all archived log file names are unique.
Action: Add the missing format
elements to log_archive_format.
ORA-19906:
recovery target incarnation changed during recovery
Cause: While a media recovery was
active, a new incarnation was detected by the server due to inspection or
cataloging of archived logs or backup files.
Action: If you want recovery to use
the new incarnation, restart recovery. This is the most common action on a
standby database when RESETLOGS is done in primary. If you do not want recovery
to use the new incarnation, change the recovery destination using RMAN's RESET
DATABASE TO INCARNATION command. To see which incarnations
are available for this target database, query V$DATABASE_INCARNATION or use
RMAN's LIST INCARNATION command.
ORA-19907:
recovery time or SCN does not belong to recovered incarnation
Cause: A point-in-time recovery to an
SCN or time stamp prior to the last RESETLOGS was requested.
Action: Either change the specified
recovery time/SCN, or change the recovery destination using RMAN's RESET
DATABASE command.
ORA-19908:
datafile string has invalid checkpoint
Cause: The specified datafile has an
invalid checkpoint.
Action: Restore the datafile from a
backup.
ORA-19909:
datafile string belongs to an orphan incarnation
Cause: Either the specified datafile
was restored from a backup that was taken during a period of time that has
already been discarded by a RESETLOGS operation, or Oracle cannot identify
which database incarnation the file belongs to. The alert log contains more
information.
Action: Restore a backup of this file
that belongs to either the current or a prior incarnation of the database. If
you are using RMAN to restore, RMAN will automatically select a correct backup.
ORA-19910:
can not change recovery target incarnation in control file
Cause: The RESET DATABASE TO
INCARNATION command was used while the database is open. This is not allowed.
Action: Close the database then
re-issue the command.
ORA-19911:
datafile string contains future changes at the incarnation
boundary
Cause: The file did not hit end
backup marker redo during recovery at the incarnation boundary, hence may
contain changes discarded by new incarnation.
Action: Use older backup of the file
and then re-issue the command.
ORA-19912:
cannot recover to target incarnation string
Cause: The control file is not in the
recovery path of the target incarnation, and does not contain enough
information as to how to recover to the target incarnation.
Action: Restore the latest control
file from the target incarnation and retry.
ORA-19913:
unable to decrypt backup
Cause: A backup piece could not be
decrypted. This message is accompanied with another message that indicates the
name of the encrypted backup that could not be restored. The reason could be
either that an invalid password was entered, or that, when using transparent
decryption, the database external security device is not open.
Action: If password-based restore was
enabled for this backup, then supply the correct password using the RMAN SET
DECRYPTION command. If transparent restore was enabled for this backup, then
ensure that the database external security device is open.
ORA-19914:
unable to encrypt backup
Cause: RMAN could not create an
encrypted backup. This message will be accompanied by other messages that give
more details about why the encrypted backup could not be created. The most
common reason for this message is that you are trying to create a backup that
can be transparently decrypted, and the database external security device is
not open.
Action: If the external security
device is not open, then open it. If the external security device is not
configured, then the only type of encrypted backup that you can create is a
password-based backup.
ORA-19915:
unable to encrypt pre-10.2 files
Cause: An RMAN encrypted backup was
requested, but this backup includes one or more archived logs that were
generated by an older release of Oracle. These archived logs cannot be
encrypted.
Action: Back up the older logs without
encryption. Logs created with Oracle release 10.2 and greater can be encrypted.
ORA-19916: string
Cause: An error occurred when
processing user request.
Action: Do not use message 19917; it
is used internally for testing purpose. Do not use message 19918; it is an
internal event used by encryption.
ORA-19919:
encrypted backups to tertiary storage require Oracle Secure Backup
Cause: RMAN was configured to create
encrypted backups, but the channel is neither a DISK channel nor an Oracle
Secure Backup channel.
Action: Allocate a DISK channel or an
Oracle Secure Backup channel to use backup encryption.
ORA-19921:
maximum number of string rows exceeded
Cause: The maximum number of rows in
the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded.
Action: Close some of existing and
unused RMAN connections and sessions.
ORA-19922:
there is no parent row with id string and level string
Cause: RMAN tried to add a new
V$RMAN_STATUS row, but the parent row did not exist.
Action: This is an internal error.
Contact Oracle Support.
ORA-19923:
the session for row with id string is not active
Cause: RMAN tried to update an
V$RMAN_STATUS row but the process which owns this row died.
Action: This is an internal error.
Contact Oracle Support.
ORA-19924:
there are no row with id string
Cause: RMAN tried to update an
V$RMAN_STATUS row, but the row don't exist.
Action: This is an internal error.
Contact Oracle Support.
ORA-19926:
Database cannot be converted at this time
Cause: Another CONVERT DATABASE
operation is already in progress.
Action: Retry CONVERT DATABASE command
later.
ORA-19927:
CONVERT DATABASE operation cannot proceed
Cause: An error occurred earlier
during CONVERT DATABASE operation.
Action: Retry CONVERT DATABASE
command.
ORA-19930:
file string has invalid checkpoint SCN string
Cause: When opening the file to be
placed in a copy or backup set, to be inspected, the file header was not
recognized as a valid header because it contained a invalid checkpoint SCN. The
indicated file cannot be processed.
Action: Ensure that the correct files
are being specified for the catalog or backup operation.
ORA-19931:
file string has invalid creation SCN string
Cause: When opening the file to be
placed in a copy or backup set, to be inspected, the file header was not
recognized as a valid header because it contained a invalid creation SCN. The
indicated file cannot be processed.
Action: Ensure that the correct files
are being specified for the catalog or backup operation.
ORA-19932:
control file is not clone or standby
Cause: The operation failed because
the control file was not mounted as standby or clone.
Action: Mount the database as standby
or clone and retry.
ORA-19941:
invalid blocksize in cross platform datafile string
Cause: Blocksize in header of
datafile copy being converted at target was invalid. Either datafile has not
been made read/write with compatibility 10.0 or greater at source database or
datafile copy is corrupted.
Action: Make a new datafile copy taken
after tablespace has been made read/write with compatibility 10.0 at source
database and retry conversion.
ORA-19942:
datafile copy string not created with compatibility 10.0 or
greater
Cause: The specified datafile copy to
be converted at the target was not produced after making the tablespace in
read/write mode with compatibility 10.0 or greater at the source database.
Action: Make a new datafile copy taken
after tablespace has been made read/write with compatibility 10.0 at source
database and retry conversion.
ORA-19943:
The current database incarnation changed during backup
Cause: The backup failed because the
current database incarnation was changed during the backup. One of the
following events caused this incarnation change:
- The
database was opened using ALTER DATABASE OPEN RESETLOGS statement.
- RMAN
command RESET DATABASE TO INCARNATION was issued.
- If this
happened on physical standby database, then redo apply has applied redo data
from a new database incarnation.
Action: Re-try the backup.
ORA-19951:
cannot modify control file until DBNEWID is completed
Cause: An operation requiring to
modify the control file was attempted, but a NID change is in progress.
Action: Wait until NID completes
before attempting the operation.
ORA-19952:
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.
ORA-19953:
database should not be open
Cause: The database was open. To
change the DBID, the database must be mounted exclusively.
Action: Shut down the database and
mount it in exclusive mode.
ORA-19954:
control file is not current
Cause: The operation failed because a
non-current, non-standby control file was mounted.
Action: Make the control file current
and retry.
ORA-19955:
only one open thread is allowed to change the DBID
Cause: The operation failed because
there were active threads in the database. The most likely 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.
ORA-19956:
database should have no offline immediate datafiles
Cause: The operation failed because
the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.
Action: Drop the datafiles or recover
them and bring them online.
ORA-19957:
database should have no datafiles in unknown state
Cause: The operation failed because
the database had one or more datafiles that were in an unknown state.
Action: Drop the datafiles or recover
them and bring them online.
ORA-19958:
potential deadlock involving DIAG process
Cause: DIAG requested a control file
operation that may lead to a deadlock
Action: Try last operation later when
the control file is released
ORA-19960:
Internal use only
Cause: NID usage
Action: None
ORA-19999:
skip_row procedure was called
Cause: The skip_row procedure was
called which raises this error
Action: Skip_row should only be called
within a trigger or a procedure called by a trigger.
ORA-20000: string
Cause: The stored procedure
'raise_application_error' was called which causes this error to be generated.
Action: Correct the problem as
described in the error message or contact the application administrator or DBA
for more information.
ORA-21300:
objects option not installed
Cause: The objects option is not
installed at this site. object types and other object features are, therefore,
unavailable.
Action: Install the objects option.
The objects option is not part of the Oracle Server product and must be
purchased separately. Contact an Oracle sales representative if the objects
option needs to be purchased.
ORA-21301:
not initialized in object mode
Cause: This function requires the OCI
process to be initialized in object mode.
Action: Specify OCI_OBJECT mode when
calling OCIInitialize().
ORA-21500:
internal error code, arguments: [string], [string], [string],
[string], [string], [string], [string], [string]
Cause: This is the generic error
number for the OCI environment (client-side) internal errors. This indicates
that the OCI environment has encountered an exceptional condition.
Action: Report as a bug - the first
argument is the internal error number.
ORA-21501:
program could not allocate memory
Cause: The operating system has run
out of memory.
Action: Take action to make more
memory available to the program.
ORA-21503:
program terminated by fatal error
Cause: A program is in an
unrecoverable error state.
Action: Report as a bug.
ORA-21520:
database server driver not installed
Cause: User attempted to access a
database server through an object-mode OCI environment but the necessary driver
for supporting such access to the database server is not installed or linked
in.
Action: Check if the driver
corresponding to the database server has been installed/linked in and entered
in the server driver table.
ORA-21521:
exceeded maximum number of connections in OCI (object mode only)
Cause: User exceeded the maximum
number of connections (255) that can be supported by an OCI environment in
object mode.
Action: Close some of existing and
unused connections before opening more connections.
ORA-21522:
attempted to use an invalid connection in OCI (object mode only)
Cause: User attempted to use an
invalid connection or a connection that has been terminated in an OCI
environment (object mode), or user attempted to dereference a REF obtained from
a connection which has been terminated.
Action: Ensure that the connection
exists and is still valid.
ORA-21523:
functionality not supported by the server (object mode only)
Cause: User attempted to use a
functionality that the server does not support.
Action: Upgrade the server
ORA-21524:
object type mismatch
Cause: The object type of the object
is different from what is specified.
Action: Check the type of the object
and correct it.
ORA-21525:
attribute number or (collection element at index) string violated
its constraints
Cause: Attribute value or collection
element value violated its constraint.
Action: Change the value of the
attribute or collection element such that it meets its constraints. The
constraints are specified as part of the attribute or collection element's
schema information.
ORA-21526:
initialization failed
Cause: The initialization sequence
failed. This can happen, for example, if an environment variable such as
NLS_DATE_FORMAT is set to an invalid value.
Action: Check that all NLS environment
variables are well-formed.
ORA-21527:
internal OMS driver error
Cause: A process has encountered an
exceptional condition. This is the generic internal error number for Oracle
object management services exceptions.
Action: Report this as a bug to Oracle
Support Services.
ORA-21560:
argument string is null, invalid, or out of range
Cause: The argument is expecting a
non-null, valid value but the argument value passed in is null, invalid, or out
of range. Examples include when the LOB/FILE positional or size argument has a
value outside the range 1 through (4GB - 1), or when an invalid open mode is
used to open a file, etc.
Action: Check your program and correct
the caller of the routine to not pass a null, invalid or out-of-range argument
value.
ORA-21561:
OID generation failed
Cause: The handles passed in may not
be valid
Action: Check the validity of the env,
svc handles
ORA-21600:
path expression too long
Cause: The path expression that is
supplied by the user is too long. The path expression is used to specify the
position of an attribute in an object. This error occurs when one of the
intermediate elements in the path expression refers to an attribute of a
built-in type. Thus, the OCI function cannot proceed on to process the rest of
the elements in the path expression.
Action: User should pass in the
correct path expression to locate the attribute.
ORA-21601:
attribute is not an object
Cause: The user attempts to perform
an operation (that is valid only for an object) to an attribute of a built-in
type. An example of such an illegal operation is to dynamically set a null
structure to an attribute of a built-in type.
Action: User should avoid performing
such operation to an attribute of built-in type.
ORA-21602:
operation does not support the specified typecode
Cause: The user attempts to perform
an operation that does not support the specified typecode.
Action: User should use the range of
valid typecodes that are supported by this operation.
ORA-21603:
property id [string] is invalid
Cause: The specified property id is
invalid.
Action: User should specify a valid
property id. Valid property ids are enumerated by OCIObjectPropId.
ORA-21604:
property [string] is not a property of transient or value instances
Cause: Trying to get a property which
applies only to persistent objects.
Action: User should check the lifetime
and only get this property for persistent objects.
ORA-21605:
property [string] is not a property of value instances
Cause: Trying to get a property which
applies only to persistent and transient objects.
Action: User should check the lifetime
and only get this property for persistent and transient objects.
ORA-21606:
can not free this object
Cause: Trying to free an object that
is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified.
Action: Either flush the persistent
object or set the flag to OCI_OBJECTFREE_FORCE
ORA-21607:
memory cartridge service handle not initialized
Cause: Attempt to use the handle
without initializing it.
Action: Initialize the memory
cartridge service handle.
ORA-21608:
duration is invalid for this function
Cause: Attempt to use a duration not
valid for this function.
Action: Use a valid duration - a
previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION.
For callout duration or external procedure duration, use
OCIExtProcAllocCallMemory.
ORA-21609:
memory being resized without being allocated first
Cause: Attempt to resize memory
without allocating it first.
Action: Allocate the memory first before
resizing it.
ORA-21610:
size [string] is invalid
Cause: Attempt to resize memory with
invalid size.
Action: Pass in a valid size (must be
a positive integer).
ORA-21611:
key length [string] is invalid
Cause: Attempt to use an invalid key
length.
Action: Key length is invalid and
valid range is 0 to 64
ORA-21612:
key is already being used
Cause: Attempt to use a key that is
already used.
Action: Use a new key that is not yet
being used.
ORA-21613:
key does not exist
Cause: Attempt to use a non-existent
key
Action: Use a key that already exists.
ORA-21614:
constraint violation for attribute number [string]
Cause: Constraints on the attribute
were violated
Action: Correct the value (of the
attribute) so that it satisfies constraints
ORA-21615:
copy of an OTS (named or simple) instance failed
Cause: see following message
Action: Check that no attribute value
violates constraints.
ORA-21700:
object does not exist or is marked for delete
Cause: User attempted to perform an
inappropriate operation to an object that is non-existent or marked for delete.
Operations such as pinning, deleting and updating cannot be applied to an
object that is non-existent or marked for delete.
Action: User needs to re-initialize
the reference to reference an existent object or the user needs to unmark the
object.
ORA-21701:
attempt to flush objects to different servers
Cause: User attempted to flush
objects to different servers in one function call. These objects are obtained
by calling a callback functions provided by the program.
Action: User should avoid performing
such operation.
ORA-21702:
object is not instantiated or has been de-instantiated in cache
Cause: User attempted to perform an
inappropriate operation to a transient object that is not instantiated in the
object cache. Operations that cannot be applied to a not-instantiated transient
object include deleting or pinning such an object.
Action: User should check their code
to see if they are performing such an operation without instantiating the
object first, or performing such an operation after the allocation duration of
the object has expired.
ORA-21703:
cannot flush an object that is not modified
Cause: See the error message.
Action: The object should not be
flushed.
ORA-21704:
cannot terminate cache or connection without flushing first
Cause: See the error message.
Action: The transaction should be
aborted or committed before terminating the cache or connection.
ORA-21705:
service context is invalid
Cause: The service context that is
supplied by the user is not valid.
Action: User needs to establish the
service context.
ORA-21706:
duration does not exist or is invalid
Cause: The duration number that is
supplied by the user is not valid.
Action: User needs to establish the
duration or use a correct predefined duration.
ORA-21707:
pin duration is longer than allocation duration
Cause: The pin duration supplied by
the user is longer than the allocation duration. This affects operations such
as pinning and setting default parameters.
Action: User should use a shorter pin
duration or use the null duration.
ORA-21708:
inappropriate operation on a transient object
Cause: User attempted to perform an
inappropriate operation on a transient object. Operations that cannot be
applied to a transient object include flushing and locking.
Action: User should avoid performing
such operation on a transient object.
ORA-21709:
cannot refresh an object that has been modified
Cause: User attempted to refresh an
object that has been marked for delete, update or insert (new).
Action: User should unmark the object
before refreshing it.
ORA-21710:
argument is expecting a valid memory address of an object
Cause: The object memory address that
is supplied by the user is invalid. The user may have passed in a bad memory
address to a function that is expecting a valid memory address of an object.
Action: User should pass in a valid
memory address of an object to the function.
ORA-21779:
duration not active
Cause: User is trying to use a
duration that has been terminated.
Action: User should avoid performing
such operation.
ORA-21780:
Maximum number of object durations exceeded.
Cause: This typically happens if
there is infinite recursion in the PL/SQL function that is being executed.
Action: User should alter the
recursion condition in order to prevent infinite recursion.
ORA-22053:
overflow error
Cause: This operation's result is
above the range of Oracle number.
Action: Decrease the input value(s) so
that the result is in the range of Oracle number.
ORA-22054:
underflow error
Cause: This operation's result is
below the range of Oracle number.
Action: Increase the input value(s) so
that the result is in the range of Oracle number.
ORA-22055:
unknown sign flag value [string]
Cause: Signed flag used is not
OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED.
Action: Use either OCI_NUMBER_SIGNED
or OCI_NUMBER_UNSIGNED as sign flag.
ORA-22056:
value [string] is divided by zero
Cause: Given value is divied by zero.
Action: Modify divisor value to be
non-zero.
ORA-22057:
bad integer length [string]
Cause: The length of the integer (ie
number of bytes) to be converted to or from an Oracle number is invalid.
Action: Use integer length 1, 2, 4 or
8 bytes only.
ORA-22059:
buffer size [string] is too small - [string] is needed
Cause: The buffer to hold the
resulting text string is too small.
Action: Provide a buffer of the
required size.
ORA-22060:
argument [string] is an invalid or uninitialized number
Cause: An invalid or uninitialized
number is passed in.
Action: Use a valid number. To
initialize number call OCINumberSetZero().
ORA-22061:
invalid format text [string]
Cause: The numeric format string for
converting characters to or from an Oracle number is invalid.
Action: Use valid format string as
documented in OCI Programmer's Guide.
ORA-22062:
invalid input string [string]
Cause: The text string for converting
to numbers is invalid.
Action: Use a valid input string as
documented in OCI Programmer's Guide.
ORA-22063:
reading negative value [string] as unsigned
Cause: Attempt to convert a negative
number to an unsigned integer.
Action: Use the sign flag ORLTSB to
convert a signed number.
ORA-22064:
invalid NLS parameter string [string]
Cause: The NLS parameter string for
converting characters to or from an Oracle number is invalid.
Action: Use valid format string as
documented in OCI Programmer's Guide.
ORA-22065:
number to text translation for the given format causes overflow
Cause: Rounding done due to the given
string format causes overflow.
Action: Change the string format such
that overflow does not occur.
ORA-22130:
buffer size [string] is less than the required size [string]
Cause: The size of the buffer into
which the hexadecimal REF string is to be written is too small.
Action: Provide a buffer of the
required size.
ORA-22131:
hexadecimal string length is zero
Cause: The given hexadecimal string
length must be greater than zero.
Action: Specify a length greater than
zero.
ORA-22132:
hexadecimal string does not correspond to a valid REF
Cause: The given hexadecimal string
is invalid.
Action: Provide a valid hexadecimal
string which was previously returned by a call to OCIRefToHex().
ORA-22140:
given size [string] must be in the range of 0 to [string]
Cause: The given resize size is
invalid.
Action: Ensure that the given size is
in the required range.
ORA-22141:
given size [string] must be even in UTF-16 environment
Cause: The given resize size is odd.
In a UTF-16 environment, all characters are 2 bytes in length.
Action: Ensure that the given size is
even.
ORA-22150:
variable-length array has not been initialized
Cause: An un-initialized
variable-length array is being operated upon.
Action: Initialize the variable-length
array prior to calling this function.
ORA-22151:
cannot resize non-zero variable-length array to zero elements
Cause: Trying to resize a non-zero
variable-length array to 0 elements.
Action: Specify a non-zero size.
ORA-22152:
destination variable-length array is not initialized
Cause: The variable-length array on
the right-hand-side of an assignment or the destination array of an append is
not initialized.
Action: Initialize the destination
variable-length array prior to calling this function.
ORA-22153:
source variable-length array is not initialized
Cause: The variable-length array on
the left-hand-side of an assignment or the source array of an append is not
initialized.
Action: Initialize the destination
variable-length array prior to calling this function.
ORA-22160:
element at index [string] does not exist
Cause: Collection element at the
given index does not exist.
Action: Specify the index of an
element which exists.
ORA-22161:
type code [string] is not valid
Cause: Given type code is not valid.
Action: Use one of the typecodes
enumerated in OCITypeCode.
ORA-22162:
element at index [string] has been previously deleted
Cause: Trying to delete a
non-existent collection element.
Action: Check for the existence of the
element prior to calling this function.
ORA-22163:
left hand and right hand side collections are not of same type
Cause: Left hand and right side
collections are not of same type.
Action: Ensure that the same
collection type is passed for both left hand and right hand side of this
function.
ORA-22164:
delete element operation is not allowed for variable-length array
Cause: Trying to delete an element of
a variable-length array.
Action: Ensure that the collection is
not a variable-length array prior to calling this function.
ORA-22165:
given index [string] must be in the range of [string] to [string]
Cause: Given index is not in the
required range.
Action: Ensure that the given index is
in the required range.
ORA-22166:
collection is empty
Cause: Given collection is empty.
Action: Test if collection is empty
prior to invoking this function.
ORA-22167:
given trim size [string] must be less than or equal to [string]
Cause: Given trim size is greater
than the current collection size.
Action: Ensure that the given size is
less than or equal to the collection size prior to calling this function.
ORA-22275:
invalid LOB locator specified
Cause: There are several causes: (1)
the LOB locator was never initialized; (2) the locator is for a BFILE and the
routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a
BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update
the LOB in a trigger body -- LOBs in trigger bodies are read only; (5) the
locator is for a BFILE/BLOB and the routine expects a CLOB/NCLOB locator; (6)
the locator is for a CLOB/NCLOB and the routine expects a BFILE/BLOB locator;
Action: For (1), initialize the LOB
locator by selecting into the locator variable or by setting the LOB locator to
empty. For (2),(3), (5) and (6)pass the correct type of locator into the
routine. For (4), remove the trigger body code that updates the LOB value.
ORA-22276:
invalid locator for LOB buffering
Cause: There are several causes: (1)
the locator was never enabled for buffering (2) it is not an updated locator
but is being used for a write/flush operation
Action: For (1) enable the locator for
buffering; (2) ensure that only an updated locator is used for a LOB update
operation
ORA-22277:
cannot use two different locators to modify the same LOB
Cause: LOB buffering is enabled and
an attempt was made to modify the LOB using two different LOB locators.
Action: When using LOB buffering,
modify the LOB through one LOB locator only.
ORA-22278:
must update the LOB only through the LOB buffers
Cause: LOB buffering is enabled for
this LOB and there are buffers for this LOB in the buffer pool. Thus, updating
the LOB through means other than the LOB buffers is not allowed.
Action: Update the LOB through the LOB
buffers using the locator that has LOB buffering enabled. If this operation is
required, buffers associated with this LOB should either be flushed as
necessary or buffering should be disabled. Once this is done, reissue the
command.
ORA-22279:
cannot perform operation with LOB buffering enabled
Cause: The operation attempted is not
allowed when LOB buffering is enabled.
Action: If the operation is required,
LOB buffering should not be used. In this case, flush buffers associated with
the input LOB locator as necessary, disable buffering on the input LOB locator
and reissue the command.
ORA-22280:
no more buffers available for operation
Cause: There are two causes: (1) All
buffers in the buffer pool have been used up by previous operations (2) Attempt
to flush a LOB without any previous buffered update operations.
Action: For (1), flush the LOB(s)
through the locator that is being used to update the LOB. For (2), write to the
LOB through a locator enabled for buffering before attempting to flush buffers.
ORA-22281:
cannot perform operation with an updated locator
Cause: The input locator has
buffering enabled and was used to update the LOB value through the LOB
buffering subsystem. The modified buffer has not been flushed since the write
that was performed by the the input locator; thus, the input locator is
considered an updated locator. Updated locators cannot be the source of a copy
operation. Only one locator per LOB may be used to modify the LOB value through
the LOB buffering subsystem.
Action: Depending on whether the
modifications made through the input locator to the LOB buffering subsystem
should be written to the server, either flush the buffer to write the
modifications, or, disable buffering on the locator to discard the
modifications. Then, reissue the command.
ORA-22282:
non-contiguous append to a buffering enabled LOB not allowed
Cause: The buffered write operation
has an input offset value more than one byte or character past the end of the
LOB.
Action: Specify an input offset value
which is exactly one character or byte greater than the length of the LOB that
you are attempting to update through a buffered write operation.
ORA-22283:
filename contains characters that refer to parent directory
Cause: Filename contains a path
"../" which references a parent directory
Action: Ensure that the filename does
not contain characters which reference a parent directory.
ORA-22285:
non-existent directory or file for string operation
Cause: Attempted to access a
directory that does not exist, or attempted to access a file in a directory
that does not exist.
Action: Ensure that a system object
corresponding to the specified directory exists in the database dictionary, or
make sure the name is correct.
ORA-22286:
insufficient privileges on file or directory to perform string operation
Cause: The user does not have the
necessary access privileges on the directory alias and/or the file for the
operation.
Action: Ask the database/system
administrator to grant the required privileges on the directory alias and/or
the file.
ORA-22287:
invalid or modified directory occurred during string operation
Cause: The directory alias used for
the current operation is not valid if being accessed for the first time, or has
been modified by the DBA since the last access.
Action: If you are accessing this
directory for the first time, provide a valid directory name. If you have been
already successful in opening a file under this directory before this error
occured, then close the file and retry the operation with a valid directory
alias as modified by your DBA. Oracle recommends that directories should be
modified only during quiescent periods.
ORA-22288:
file or LOB operation string failed string
Cause: The operation attempted on the
file or LOB failed.
Action: See the next error message in
the error stack for more detailed information. Also, verify that the file or
LOB exists and that the necessary privileges are set for the specified
operation. If the error still persists, report the error to the DBA.
ORA-22289:
cannot perform string operation on an unopened file or LOB
Cause: The file or LOB is not open
for the required operation to be performed.
Action: Precede the current operation
with a successful open operation on the file or LOB.
ORA-22290:
operation would exceed the maximum number of opened files or LOBs
Cause: The number of open files or
LOBs has reached the maximum limit.
Action: Close some of the opened files
or LOBs and retry the operation.
ORA-22291:
Open LOBs exist at transaction commit time
Cause: An attempt was made to commit
a transaction with open LOBs at transaction commit time.
Action: Close the LOBs before
committing the transaction.
ORA-22292:
Cannot open a LOB in read-write mode without a transaction
Cause: An attempt was made to open a
LOB in read-write mode before a transaction was started.
Action: Start a transaction before
opening the LOB in read-write mode. Ways to start a transaction include issuing
a SQL DML or SELECT FOR UPDATE command. Opening hte LOB in read-only mode does
not require a transaction.
ORA-22293:
LOB already opened in the same transaction
Cause: An attempt was made to open a
LOB that already is open in this transaction.
Action: Close the LOB before
attempting to re-open it.
ORA-22294:
cannot update a LOB opened in read-only mode
Cause: An attempt was made to write
to or update a LOB opened in read-only mode.
Action: Close the LOB and re-open it
in read-write mode before attempting to write to or update the LOB.
ORA-22295:
cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
Cause: An attempt was made to bind
data more than 4000 bytes of data to both LOB and LONG columns in the same
insert or update statement. You can bind more than 4000 bytes of data to either
a LONG column or one or more LOB columns but not both.
Action: Bind more than 4000 bytes of
data to either the LONG column or one or more LOB columns but not both.
ORA-22296:
invalid ALTER TABLE option for conversion of LONG datatype to LOB
Cause: An attempt was made to specify
ALTER TABLE options which are disallowed during conversion of LONG datatype to
LOB. The only ALTER TABLE options allowed during conversion of LONG datatype to
LOB are the default clause and LOB storage clause for the column being
converted to LOB.
Action: Remove the disallowed options.
ORA-22297:
warning: Open LOBs exist at transaction commit time
Cause: An attempt was made to commit
a transaction with open LOBs at transaction commit time.
Action: This is just a warning. The
transaction was commited successfully, but any domain or functional indexes on
the open LOBs were not updated. You may want to rebuild those indexes.
ORA-22298:
length of directory alias name or file name too long
Cause: The length of directory alias
name or file name given for a BFILE is too long.
Action: Use a shorter alias or file
name.
ORA-22303:
type "string"."string" not found
Cause: The user is trying to obtain
information for a type that cannot be found.
Action: Check that the schema is
correct and that the type has been created correctly.
ORA-22304:
input type is not an object type
Cause: The user is trying to obtain
the supertype information for a non-object type.
Action: Pass in only an object type.
ORA-22305:
attribute/method/parameter "string" not found
Cause: Type element with the given
name is not found in the type.
Action: Check to make sure that the
type element exists.
ORA-22306:
type "string"."string" already exists
Cause: The user is trying to create a
type that already exists.
Action: Check to make sure that the
type has not been created prior to this.
ORA-22307:
operation must be on a user-defined type
Cause: attempt to perform an
operation that is allowed only on a user-defined type, and the type is not a
user-defined type.
Action: Check to make sure that only
user-defined types are being operated on.
ORA-22308:
operation not allowed on evolved type
Cause: An attempt was made to replace
a type whose attribute definition been been altered.
Action: Submit ALTER TYPE ADD/DROP
statement instead of ALTER TYPE REPLACE.
ORA-22309:
attribute with name "string" already exists
Cause: The user is attempting to
create an object type where more than one attributes have the same name.
Action: Check to make sure that all
attribute names are unique.
ORA-22310:
ALTER TYPE error. Refer to table "string"."string"
for errors
Cause: An invalid alter type
statement was submitted.
Action: Correct the errors listed in
specified table and resubmit statement.
ORA-22311:
type for attribute "string" does not exist
Cause: The type of the attribute does
not exist.
Action: No types were created/modified
for this DDL transaction. Redo the DDL transaction and add the creation of the
attribute's type in the DDL transaction.
ORA-22312:
must specify either CASCADE or INVALIDATE option
Cause: An attempt was made to alter a
type which has a dependent type or table without specifying the CASCADE or
INVALIDATE option.
Action: Resubmit the statement with
either the CASCADE or INVALIDATE option. Specify CASCADE if you want to cascade
the type change to dependent types and tables; otherwise, specify INVALIDATE to
invalidate all dependents.
ORA-22313:
cannot use two versions of the same type "string"
Cause: The version of this type
conflicts with the version of this type used by another library that was linked
in with the application. An application may only use one version of a type.
Action: Check that the libraries being
linked with this application and use the same versions of the type.
ORA-22314:
method information mismatch in ALTER TYPE
Cause: The number of methods or the
method signature do not match that of the original type declaration. This is
not supported.
Action: Make sure the method signature
stay identical for the previously declared method. Do not drop existing
methods.
ORA-22315:
type "string" does not contain a map or order function
Cause: The input type does not
contain a map or order function so one cannot be returned.
Action: Add a map or order function to
the type or catch this error.
ORA-22316:
input type is not a collection type
Cause: The user is trying to obtain
information for collection types on a non-named collection type.
Action: Use a named collection type
for the function.
ORA-22317:
typecode number is not legal as a number type
Cause: The user is trying to use a
number typecode that is not valid.
Action: Use only
OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL,
OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or
OCI_TYPECODE_DECIMAL.
ORA-22318:
input type is not an array type
Cause: The user is trying to obtain
the number of elements for a non-array type.
Action: Pass in only a named
collection type which is an array.
ORA-22319:
type attribute information altered in ALTER TYPE
Cause: The type attribute information
does not match that of the original type declaration when altering type.
Attributes cannot be altered during ALTER TYPE. Only new methods can be added.
Action: Check that all type
alterations are legal.
ORA-22320:
missing user version string
Cause: The VERSION option is
specified without a user version string.
Action: Resubmit the statement with
the version string following the VERSION keyword.
ORA-22321:
method does not return any result
Cause: OCITypeResult() was called on
a method that does not return any results.
Action: Check that you are passing in
the correct method descriptor, or that your method creation was done correctly.
ORA-22322:
error table "string"."string" has incorrect
structure
Cause: The specified error table does
not have the expected table structure.
Action: Execute the
DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure to create an error table,
then resubmit the statement using the new error table.
ORA-22323:
error table "string"."string" does not exist
Cause: The error table does not
exist.
Action: Resubmit the statement with a
correct error table name.
ORA-22324:
altered type has compilation errors
Cause: The use of the ALTER TYPE
statement caused a compilation error.
Action: Correct the error reported and
resubmit the statement.
ORA-22326:
cannot change a type to FINAL if it has subtypes
Cause: An attempt was made to change
a type with subtypes to FINAL.
Action: Drop all subtypes of the
target type before changing it to FINAL.
ORA-22327:
cannot change a type to NOT INSTANTIABLE if it has dependent tables
Cause: An attempt was made to change
a type with dependent tables to NOT INSTANTIABLE.
Action: Drop all dependent tables of
the target type and resubmit the statement.
ORA-22328:
object "string"."string" has errors. string
Cause: Altering the target type
causes errors in its dependent object.
Action: Correct the problem in the
dependent object and resubmit the statement.
ORA-22329:
cannot alter a non-object type
Cause: An attempt was made to execute
ALTER TYPE on a non-object type.
Action: Drop the non-object type
first, then re-create it as an object type.
ORA-22330:
cannot alter a type that is not valid
Cause: An attempt was made to perform
ALTER TYPE on an invalid type.
Action: Use the CREATE OR REPLACE TYPE
command to modify the type.
ORA-22331:
cannot alter an incomplete type
Cause: An attempt was made to perform
ALTER TYPE on an incomplete type.
Action: Use CREATE TYPE to completely
define the original type before executing the ALTER TYPE.
ORA-22332:
a dependent object in schema "string" has errors. string
Cause: Altering the target type
causes errors in its dependent object.
Action: Correct the problem in the
dependent object and resubmit the statement.
ORA-22333:
cannot reset type "string"."string" due to invalid
dependent types and tables
Cause: An attempt was made to reset
the type version with invalid dependent types and tables.
Action: Use the ALTER TYPE COMPILE
statement to compile all invalid dependent types and use the ALTER TABLE
UPGRADE INCLUDING DATA to upgrade all the dependent tables then resubmit the
statement.
ORA-22334:
cannot reset type "string"."string".
Dependent tables must be upgraded to latest version
Cause: An attempt was made to reset
the type version when the data in the dependent table has not been upgraded to
the latest type version.
Action: Use the ALTER TABLE UPGRADE
INCLUDING DATA statement to upgrade the data in the dependent tables then
resubmit the statement.
ORA-22335:
The client cannot work with an altered type
Cause: A pre 8.2 client has requested
a type that has been altered on the server.
Action: Only 8.2 or higher clients
could access altered types
ORA-22336:
table contained 8.0 image format, must specify INCLUDING DATA
Cause: One of the following: 1) An
attempt was made to alter a type with a dependent table in 8.0 image format and
the NOT INCLUDING TABLE DATA option was specified. 2) An attempt was made to
upgrade a table in 8.0 image format with the NOT INCLUDING DATA option
specified.
Action: Resubmit the statement with
INCLUDING DATA option.
ORA-22337:
the type of accessed object has been evolved
Cause: The type of the accessed
object has been altered and the client's object is based on an earlier type
definition.
Action: The user needs to exit
application and modify application to accommodate the type change. From
SQL/PLUS, reconnect and resubmit statement.
ORA-22338:
must specify CASCADE INCLUDING DATA when altering the final property
Cause: An attempt was made to alter
the final property of a type with dependent table(s) without specifying the
CASCADE INCLUDING DATA . option.
Action: Resubmit the statement with
the CASCADE INCLUDING DATA option.
ORA-22339:
cannot alter to not final since its attribute column is substitutable
Cause: An attempt was made to alter a
type to not final when its embedded attribute is defined as substitutable in
some tables. Note, this is a restriction in 9.0 version because when a type is
altered to not final, column of that type is set to not substitutable at all
levels; thus, it is an error if one of its embedded attribute column is already
marked substitutable.
Action: Recreate the table and specify
NOT SUBSTITUTABLE AT ALL LEVELS for all columns of non final type. Then
resubmit the ALTER TYPE statement.
ORA-22340:
cannot string type "string"."string".
Dependent tables must be upgraded to latest version
Cause: An attempt was made to reset
the version, drop or alter a type when the data in dependent table has not been
upgraded to the latest version.
Action: Use the ALTER TABLE UPGRADE
INCLUDING DATA statement to upgrade the data in the dependent tables then
resubmit the statement.
ORA-22341:
cannot assign supertype instance to subtype
Cause: An attempt was made to assign
or copy a supertype instance to a container (destination) that can only hold a
subtype instance.
Action: Make sure the runtime type of
the source of the assignment or copy is the same type as the destination or is
a subtype of the destination type
ORA-22342:
dependent VARRAY column exceeds the maximum inline column size
Cause: An attempt was made to alter a
type (add or modify attribute) which causes the size of its dependent VARRAY
column to exceed the maximum inline column size. However, the VARRAY column was
not specified to be stored as LOB at the table level when the table was
created.
Action: Specify the VARRAY column to
be stored as LOB at the table level when the table is created.
ORA-22343:
Compilation error for type invalidated by ALTER TYPE
Cause: Compilation failed for a type
which was invalidated by ALTER TYPE. We throw this error and rollback the
compilation effort so that the user may be able to fix whatever is causing the
compilation error and try again. It is important that we do not chnage status
here and modify the dependency information as this will affect the creation of
versions.
Action: Check what is causing teh
compilation error and correct it and try again.
ORA-22344:
can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT
FINAL change
Cause: An attempt was made to specify
CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change.
Action: Specify CONVERT TO
SUBSTITUTABLE option only for ALTER TYPE NOT FINAL change.
ORA-22345:
recompile type string.string before attempting this
operation
Cause: An attempt was made to perform
an operation which requires the specified datatype to be valid, but the
datatype is invalid
Action: Recompile the specified type
and retry the operation
ORA-22346:
Type has cyclical dependency. Should use CASCADE option
Cause: An attempt was made to alter a
type which has a cyclical dependency, with invalidate option.
Action: Give CASCADE option instead of
INVALIDATE
ORA-22347:
No changes to type specified for ALTER TYPE
Cause: The ALTER TYPE does not
contain any changes to the type.
Action: If any change is required for
the type, modify the ALTER TYPE to specify the change. Else no need for the
ALTER.
ORA-22369:
invalid parameter encountered in method string
Cause: An invalid parameter is being
passed to this method of SYS.AnyType ,SYS.AnyData or SYS.AnyDataSet
Action: Check the parameters being
passed to this method and make sure that the parameters are allowed.
ORA-22370:
incorrect usage of method string
Cause: This method of SYS.AnyType or
SYS.AnyData or SYS.AnyDataSet is being used inappropriately.
Action: Check the documentation for
correct usage.
ORA-22371:
Table contains data of type string.string, version string,
which does not exist
Cause: Some of the older versions of
the type may have got deleted because one or more of the types it were
referencing was dropped.
Action: These data could not be read
as the whole ADT. Read the data at individual scalar attribute level.
ORA-22372:
Event for type dictionary upgrade
Cause: This is an internally used
event for type dictionary upgrades from 8.0 to 8.1.
Action: None
ORA-22373:
Older version hashcode encountered
Cause: An older version HC is
encountered when creating a new version hahscode. Currently this is handled
internally.
Action: None
ORA-22600:
encountered 8.0.2 (Beta) VARRAY data that cannot be processed
Cause: Production Oracle8 (8.0.3 and
beyond) encounters some VARRAY data which was created and stored by Oracle8
8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY
data.
Action: Delete the VARRAY data from the
table by dropping the table, deleting the rows, or nulling out the VARRAY
columns, and then re-insert the VARRAY data. There is no provided script or
tool to help automate this conversion.
ORA-22601:
pickler TDS context [string] is not initialized
Cause: Attempt to use the pickler TDS
context without initializing it.
Action: Use OCIPicklerTdsCtxInit to
initialize the context.
ORA-22602:
pickler TDS handle [string] is not well-formed
Cause: Attempt to use the pickler TDS
handle without initializing/ constructing it.
Action: Use OCIPicklerTdsInit to
initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to
generate the TDS before its attributes can be accessed.
ORA-22603:
cannot add an attribute to the already generated TDS handle
Cause: Attempt to add an attribute to
the already constructed TDS.
Action: Use a TDS handle that is
initialized but not yet constructed.
ORA-22604:
TDS handle already generated
Cause: Attempt to geneate TDS that is
already genearated.
Action: Use a TDS handle that is
initialized but not yet generated.
ORA-22605:
FDO handle [string] is not initialized
Cause: Attempt to use an
uninitialized FDO handle.
Action: Use OCIPicklerFdoInit to
initialize FDO handle".
ORA-22606:
pickler image handle [string] is not well-formed
Cause: Attempt to use the image
handle without initializing/ constructing it.
Action: Use OCIPicklerImageInit to
initialize the handle before it is constructed. Use OCIPicklerImageGenerate to
generate the image before its attributes can be accessed.
ORA-22607:
image handle already generated
Cause: Attempt to geneate image that
is already genearated.
Action: Use a image handle that is
initialized but not yet generated.
ORA-22608:
cannot add an attribute to the already generated image handle
Cause: Attempt to add an attribute to
the already constructed image.
Action: Use a image handle that is
initialized but not yet constructed.
ORA-22609:
error string during initialization of FDO
Cause: Error during FDO
initialization.
Action: Take an action based on the
specified error.
ORA-22610:
error while adding a scalar to the image handle
Cause: Error while adding a scalar
attribute to the image handle
Action: Make sure image handle is
initialized before adding scalar
ORA-22611:
TDS version is not recognized
Cause: Incorrect TDS handle is passed
Action: Make sure image handle is
initialized with the correct TDS
ORA-22612:
TDS does not describe a collection TDS
Cause: collection construct/access
routines are being on an image but the TDS does not describe that a collection
TDS
Action: Make sure a collection TDS is
used before invoking collection routines on the image handle
ORA-22613:
buflen does not match the size of the scalar
Cause: buflen is incorrect
Action: Make sure buflen is correct
and matches the size of the scalar
ORA-22614:
error while construction the collection in the image
Cause: Error during the construction
of collection
Action: Make sure image handle is
initialized and OCIPicklerImageCollBegin is called to begin collection
ORA-22615:
attribute is not a collection
Cause: collection routine is invoked
upon a non-collection attribute
Action: Make sure attribute is a
collection
ORA-22616:
image is not of Oracle 8.1 format
Cause: The function being invoked is
applicable only for 8.1 images
Action: Make sure image is of 8.1
format
ORA-22617:
error while accessing the image handle collection
Cause: Error while accessing
collection in the image handle
Action: Make sure image is initialized
correctly and the collection is constructed properly.
ORA-22618:
attribute is a BAD NULL in the image handle
Cause: attribute in question is
probably the attribute of a null embedded image
Action: Make sure attribute number is
valid or it is NULL or NOT NULL.
ORA-22619:
all collection elements have already been accessed
Cause: Accessing a collection element
after all the collection elements are already accessed
Action: This function should not be
invoked any more.
ORA-22620:
buffer size too small to hold the value
Cause: Buffer size is not enough to
hold the value. Most likely while doing the character set conversion, a bigger
buffer is needed.
Action: Pass in a bigger buffer. If
the client character set format differs from that of server, doing the
conversion may result in 4X expansion.
ORA-22621:
error transfering an object from the agent
Cause: Any error returned from
pickler routines on the agent side.
Action: Contact Oracle Support.
ORA-22625:
OCIAnyData is not well-formed
Cause: Attempt to use the OCIAnyData
without initializing constructing it.
Action: Use OCIAnyDataBeginConstruct
to initialize the handle before it is adding attributes. Use
OCIAnyDataEndConstruct to complete the construction. Or use OCIAnyDataConvert
to do the construction. MAke sure it is properly constructed before accessing
attributes.
ORA-22626:
Type Mismatch while constructing or accessing OCIAnyData
Cause: Type supplied is not matching
the type of the AnyData. If piece wise construction or access is being
attempted, the type supplied is not matching the type of the current attribute.
Action: Make sure the type supplied
matches the type of object to to be constucted or accessed.
ORA-22627:
tc [string] must be that of object/varray/nested table
Cause: Type code is not that of
object/varray/nested table
Action: Make sure the type code is
OCI_TYPECODE_OBJECT or OCI_TYPECODE_VARRAY or OCI_TYPECODE_TABLE
ORA-22628:
OCIAnyData already constructed
Cause: Attempt to add attributes to
OCIAnyData that is already constructed.
Action: Use the OCIAnyData that is
initialized but not yet constructed.
ORA-22629:
OCIAnyData is null
Cause: Attempting an operation that
is not valid on null OCIAnyData
Action: Make sure OCIAnyData is not
null.
ORA-22630:
attribute [string] is null or it is not well-formed
Cause: Passing an attribute that is
null or not well-formed
Action: Make sure the attribute is not
null or is well-formed.
ORA-22631:
attribute [string] is is not well-formed or does not match the type
Cause: Passing an attribute that is
not well-formed or does not match the input type.
Action: Make sure the attribute is
well-formed and matches the type specified.
ORA-22632:
AnyDataSet parameter is not valid for the current operation
Cause: The AnyDataSet parameter is
null or it is somehow invalid for the current operation.
Action: Check the documentation for
the current operation.
ORA-22633:
Error freeing AnyDataSet
Cause: AnyDataSet that is passed in
may not be valid.
Action: Check all the AnyDataSet
parameters.
ORA-22634:
Error adding new instance to AnyDataSet
Cause: Current instance in the AnyDataSet
has not been fully constructed.
Action: Make sure that the current
instance is fully constructed before adding new instance.
ORA-22800:
invalid user-defined type
Cause: An attempt was made to use an
incomplete type as a constructor.
Action: Complete the type definition
before using it in a query.
ORA-22801:
invalid object row variable
Cause: The specified object row
variable is not available in the scope of name resolution.
Action: Verify the specified object
row variable is correct, or use an object row variable visible in scope.
ORA-22803:
object type contains zero attributes
Cause: An attempt was made to create
or specify a column or constructor of an object type that has no attributes.
Only object types that have at least one attribute are allowed in this context.
Action: specify a valid object type
ORA-22804:
remote operations not permitted on object tables or user-defined type columns
Cause: An attempt was made to perform
queries or DML operations on remote object tables or on remote table columns
whose type is one of object, REF, nested table or VARRAY.
Action: None
ORA-22805:
cannot insert NULL object into object tables or nested tables
Cause: An attempt was made to insert
a NULL object into an object table or a Nested Table.
Action: Ensure that a non-NULL object
is inserted into the table or insert an object with attributes whose values are
NULL.
ORA-22806:
not an object or REF
Cause: An attempt was made to extract
an attribute from an item that is neither an object nor a REF.
Action: Use an object type or REF type
item and retry the operation.
ORA-22807:
cannot resolve to a scalar type or a collection type
Cause: Invalid use of a non-scalar
(for example, object type) item.
Action: Change the item's data type
and retry the operation.
ORA-22808:
REF dereferencing not allowed
Cause: An attempt was made to access
an object type's attributes by dereferencing a REF item.
Action: Make the item an object type
instead of a REF to an object type.
ORA-22809:
nonexistent attribute
Cause: An attempt was made to access
a non-existent attribute of an object type.
Action: Check the attribute reference
to see if it is valid. Then retry the operation.
ORA-22810:
cannot modify object attributes with REF dereferencing
Cause: An attempt was made to modify
the attributes an object by dereferencing a REF column in an UPDATE statement.
Action: Update the table containing
the object that the REF points to, or change the REF column to an object type
column.
ORA-22812:
cannot reference nested table column's storage table
Cause: An attempt to access the
nested table column's storage table is not allowed in the given context.
Action: Issue the statement against
the parent table containing the nested table column.
ORA-22813:
operand value exceeds system limits
Cause: Object or Collection value was
too large. The size of the value might have exceeded 30k in a SORT context, or
the size might be too big for available memory.
Action: Choose another value and retry
the operation.
ORA-22814:
attribute or element value is larger than specified in type
Cause: Value provided for the object
type attribute or collection element exceeded the size specified in the type
declaration.
Action: Choose another value and retry
the operation.
ORA-22816:
unsupported feature with RETURNING clause
Cause: RETURNING clause is currently
not supported for object type columns, LONG columns, remote tables, INSERT with
subquery, and INSTEAD OF Triggers.
Action: Use separate select statement
to get the values.
ORA-22817:
subquery not allowed in the default clause
Cause: An attempt was made to use a
subquery in the column default clause expression.
Action: Remove the subquery from the
default clause.
ORA-22818:
subquery expressions not allowed here
Cause: An attempt was made to use a
subquery expression where these are not supported.
Action: Rewrite the statement without
the subquery expression.
ORA-22819:
scope of input value does not correspond to the scope of the target
Cause: An attempt to operate on a REF
value scoped to a different table than the expected one
Action: Use a ref which is scoped to
the expected table and retry the operation
ORA-22826:
cannot construct an instance of a non instantiable type
Cause: An attempt was made to use a
non instantiable type as a constructor.
Action: None
ORA-22828:
input pattern or replacement parameters exceed 32K size limit
Cause: Value provided for the pattern
or replacement string in the form of VARCHAR2 or CLOB for LOB SQL functions
exceeded the 32K size limit.
Action: Use a shorter pattern or
process a long pattern string in multiple passes.
ORA-22833:
Must cast a transient type to a persistent type
Cause: An attempt was made to use the
transient type in the query result.
Action: Cast the transient type to a
structurally equivalent persistent type.
ORA-22835:
Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string,
maximum: string)
Cause: An attempt was made to convert
CLOB to CHAR or BLOB to RAW, where the LOB size was bigger than the buffer
limit for CHAR and RAW types. Note that widths are reported in characters if
character length semantics are in effect for the column, otherwise widths are
reported in bytes.
Action: Do one of the following:
1. Make the
LOB smaller before performing the conversion, for example, by using SUBSTR on
CLOB
2. Use
DBMS_LOB.SUBSTR to convert CLOB to CHAR or BLOB to RAW.
ORA-22837:
Relational hint or keyword is disallowed for user-level DML
Cause: An attempt was made to use
relational hint or keyword in user- level DML.
Action: Avoid using DML with relational
hint or keyword.
ORA-22839:
Direct updates on SYS_NC columns are disallowed
Cause: An attempt was made to update
SYS_NC columns directly.
Action: Avoid direct updates on SYS_NC
columns.
ORA-22850:
duplicate LOB storage option specificed
Cause: A LOB storage option (CHUNK,
PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX, SECUREFULE/BASICFILE,
[A]SYNC) was specified more than once.
Action: Specify all LOB storage
options only once.
ORA-22851:
invalid CHUNK LOB storage option value
Cause: The specified CHUNK LOB
storage option value must be an integer.
Action: Choose an appropriate integer
value and retry the operation.
ORA-22852:
invalid PCTVERSION LOB storage option value
Cause: The specified PCTVERSION LOB
storage option value must be an integer.
Action: Choose an appropriate integer
value and retry the operation.
ORA-22853:
invalid LOB storage option specification
Cause: A LOB storage option was not
specified
Action: Specify one of CHUNK,
PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX, [A]SYNC or DATA SYNC as
part of the LOB storage clause.
ORA-22854:
invalid option for LOB storage index
Cause: A valid LOB store index option
was not specified.
Action: Specify one of (INITRANS,
MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index.
ORA-22855:
optional name for LOB storage segment incorrectly specified
Cause: The optional name for LOB
storage segment was specified with multiple columns in the column list.
Action: Specify each column LOB
storage only with optional name(s).
ORA-22856:
cannot add columns to object tables
Cause: An attempt was made to add
columns to an object table. Object tables cannot be altered to add columns
since its definition is based on an object type.
Action: Create a new type with
additional attributes, and use the new type to create an object table. The new
object table will have the desired columns.
ORA-22857:
cannot modify columns of object tables
Cause: An attempt was made to alter
the object table by modifing existing columns. An object table cannot be
altered to modify existing columns since it is based on an object type. The
table definition must be in sync with the corresponding type.
Action: Create a new type with the
desired attribute types and use it to create an object table. The new object
table will have the desired columns.
ORA-22858:
invalid alteration of datatype
Cause: An attempt was made to modify
the column type to object, REF, nested table, VARRAY or LOB type.
Action: Create a new column of the
desired type and copy the current column data to the new type using the
appropriate type constructor.
ORA-22859:
invalid modification of columns
Cause: An attempt was made to modify
an object, REF, VARRAY, nested table, or LOB column type.
Action: Create a new column of the
desired type and copy the current column data to the new type using the
appropriate type constructor.
ORA-22860:
object type expected
Cause: An attempt was made to create
an object table using a non- object type, or to create a column that is a REF
to a non-object type.
Action: Use a valid object type in the
table or column definition.
ORA-22861:
invalid user-defined type
Cause: An attempt was made to create
a column or object table of a non- existent type.
Action: Specify a valid type in the
table or column definition.
ORA-22862:
specified object identifier doesn't match existing object identifier
Cause: An attempt was made to specify
an object identifier for the type that does not match the existing identifier
of the incomplete type of the same name.
Action: Specify the correct object
identifier or leave it out of the statement.
ORA-22863:
synonym for datatype string.string not allowed
Cause: A synonym specification for a
datatype is not supported
Action: do not use the synonym for the
datatype
ORA-22864:
cannot ALTER or DROP LOB indexes
Cause: An attempt was made to ALTER
or DROP a LOB index.
Action: Do not operate directly on the
system-defined LOB index. Perform operations on the corresponding LOB column.
ORA-22865:
more than one column specified
Cause: An attempt was made to specify
multiple columns where only one is allowed.
Action: Specify a single column and
retry the operation.
ORA-22868:
table with LOBs contains segments in different tablespaces
Cause: An attempt was made to drop a
tablespace which contains the segment(s) for the LOB columns of a table but
does not contain the table segment.
Action: Find table(s) with LOB columns
which have non-table segments in this tablespace. Drop these tables and reissue
drop tablespace.
ORA-22869:
depth of type dependency hierarchy exceeds maximum limit
Cause: The type dependency hierarchy
was structured to have depth greater than 1024.
Action: Re-structure the type
dependency hierarchy to a shorter depth.
ORA-22870:
ALTER TYPE with REPLACE option a non-object type
Cause: attempt to perform ALTER TYPE
with REPLACE option a non-object type
Action: drop the non-object type
first, then re-create it as an object type
ORA-22871:
ALTER TYPE with REPLACE is not allowed for pure incomplete types
Cause: An attempt to perform ALTER
TYPE with REPLACE option for a pure incomplete type
Action: Completely define the original
type, before using the ALTER TYPE with REPLACE option.
ORA-22872:
OID INDEX clause not allowed on tables with primary key based object
identifiers
Cause: An attempt to create an OID
INDEX on a table with primary key based object identifiers.
Action: Remove the OID INDEX clause
ORA-22873:
primary key not specified for primary key based object table
Cause: An attempt to create a primary
key based object table without specifying a primary key
Action: Specify a primary key and
retry the operation
ORA-22874:
attribute "string" is not part of the type "string"
Cause: Attribute specified in the
user_defined clause is not an attribute of the REF type
Action: Ensure that the name specified
in the user_defined clause is the name of a valid attribute of the REF type
ORA-22875:
cannot drop primary key of an object table whose object identifier is primary
key based
Cause: An attempt to drop the primary
key of an object table which has a primary key based object identifier
Action: Remove the drop primary key
clause
ORA-22876:
this user-defined type is not allowed or it cannot be used in this context
Cause: An attempt to create a kind of
user-defined type which is not allowed, or an attempt to create table columns
or use default constructor with a type on which these are not supported.
Action: Ensure that the type is
permitted in this context.
ORA-22877:
invalid option specified for a HASH partition or subpartition of a LOB column
Cause: One or more invalid options
were encountered while parsing the physical attributes of a LOB partition or
subpartition. Either the LOB partition is in a table partitioned using the HASH
method, or the LOB subpartition is in a table subpartitioned using the HASH
method. TABLESPACE is the only valid option for a HASH partition or
subpartition.
Action: Remove the invalid option(s).
ORA-22878:
duplicate LOB partition or subpartition specified
Cause: An attempt was made to specify
a partition or subpartition that has already been specified for the LOB column.
Action: Remove the duplicate
specification.
ORA-22879:
cannot use the LOB INDEX clause for partitioned tables
Cause: An attempt was made to specify
a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned
table.
Action: Remove the LOB INDEX clause.
ORA-22880:
invalid REF
Cause: An invalid REF was accessed.
Action: Modify the REF and retry the
operation.
ORA-22881:
dangling REF
Cause: The object corresponding to
the REF that was accessed does not exist.
Action: Ensure that the REF value is
pointing to an existing object.
ORA-22882:
object creation failed
Cause: The object cannot be created
in the database.
Action: Check to see if the object
table exists and the object size is not too big. Then retry the operation.
ORA-22883:
object deletion failed
Cause: The object could not be
deleted from the database.
Action: Check to see if the object
table exists.Then retry the operation.
ORA-22884:
object modification failed
Cause: The object could not be
modified in the database.
Action: Check to see if the object
table exists and the object size is not too big. Then retry the operation.
ORA-22885:
cannot get REF to a non-persistent object
Cause: An attempt was made to get a
REF for something other than an object in an object table. REFs can only be
taken for objects in object tables.
Action: Rewrite the query to obtain
REF values from object tables.
ORA-22886:
scoped table "string" in schema "string" is
not an object table
Cause: The scoped table specified for
a REF column is not an object table.
Action: Ensure that the scoped table
is an object table.Then retry the operation.
ORA-22887:
type of REF column is not the same as that of its scoped table
Cause: The type specified for the REF
column and the type specified for the scope table are different.
Action: Ensure that the types of a REF
column and its scoped table are the same.
ORA-22888:
duplicate SCOPE clauses for a REF column
Cause: Multiple SCOPE clauses were
specified for a single REF column.
Action: Remove the duplicate SCOPE
clauses and retry the operation.
ORA-22889:
REF value does not point to scoped table
Cause: An attempt was made to insert
a REF value that does not point to the scoped table.
Action: Ensure that the REF values
point to the scoped table.
ORA-22890:
cannot specify name for REF column constraint
Cause: An attempt was made to specify
a constraint name for a constraint on a REF column.
Action: Remove the constraint name and
retry the operation.
ORA-22891:
cannot have multiple columns in REF constraint
Cause: An attempt was made to specify
multiple columns in a single REF constraint.
Action: Specify separate constraints
for each column and retry the operation.
ORA-22892:
scoped table "string" does not exist in schema "string"
Cause: The scoped table specified for
a REF column does not exist.
Action: Ensure that the scoped table
exists and retry the operation.
ORA-22893:
constraint can be specified only for REF columns
Cause: The constraint specified does
not apply to non-REF columns.
Action: Remove the constraint and
retry the operation.
ORA-22894:
cannot add constraint on existing unscoped REF columns of non-empty tables
Cause: An attempt was made to add a
constraint to existing unscoped REF columns of a table which contains one or
more rows.
Action: Remove the constraint
specification or add the constraint after emptying the table.
ORA-22895:
referenced table "string" in schema "string"
is not an object table
Cause: The referenced table specified
for a REF column is not an object table.
Action: Ensure that the referenced
table is an object table.Then retry the operation.
ORA-22896:
cannot have both scope and referential constraint on REF column "string"
Cause: REF column has both a
referential and a scope constraint. A referential constraint implies a scope
constraint.
Action: Remove either the referential
or scope constraint and then retry the operation.
ORA-22897:
no scope clause specified for user-defined REF column "string"
Cause: User-defined REF column does
not have a scope constraint.
Action: Specify a scope constraint for
the user-defined REF column and retry the operation.
ORA-22898:
existing scope clause on "string" points to a table other than
the one mentioned in the referential constraint
Cause: Table mentioned in the
referential integrity constraint is different from the scope table of the REF
column.
Action: Specify the scope table of the
REF column in the referential integrity constraint and then retry the
operation.
ORA-22899:
cannot specify both scope and rowid constraint on ref column
Cause: An attempt was made to specify
both a scope and a rowid constraint on a REF column.
Action: Remove either the rowid or
scope constraint and then retry the operation.
ORA-22900:
the SELECT list item of THE subquery is not a collection type
Cause: The THE subquery must SELECT a
nested table or VARRAY item.
Action: change the subquery to SELECT
a nested table or VARRAY item.
ORA-22901:
cannot compare VARRAY or LOB attributes of an object type
Cause: Comparison of VARRAY or LOB
attributes of an object type was attempted in the absence of a MAP or ORDER
method.
Action: Define a MAP or ORDER method
for the object type.
ORA-22902:
CURSOR expression not allowed
Cause: CURSOR on a subquery is
allowed only in the top-level SELECT list of a query.
Action: None
ORA-22903:
MULTISET expression not allowed
Cause: MULTISET expressions are
allowed only inside a CAST to a nested table or VARRAY type.
Action: put the MULTISET(subquery)
expression inside a CAST to a nested table or VARRAY type.
ORA-22904:
invalid reference to a nested table column
Cause: invalid use of a nested table
column
Action: remove invalid reference to
the nested table column
ORA-22905:
cannot access rows from a non-nested table item
Cause: attempt to access rows of an
item whose type is not known at parse time or that is not of a nested table
type
Action: use CAST to cast the item to a
nested table type
ORA-22906:
cannot perform DML on expression or on nested table view column
Cause: Attempted to perform a DML on
an expression or on a nested table view column where a nested table column of a
base table is expected.
Action: Only nested table column of a
base table is allowed in the DML.
ORA-22907:
invalid CAST to a type that is not a nested table or VARRAY
Cause: Attempted to CAST to a type
that is not a nested table or VARRAY
Action: Re-specify CAST to a nested
table or VARRAY type.
ORA-22908:
reference to NULL table value
Cause: The evaluation of the THE
subquery or nested table column resulted in a NULL value implying a NULL table
instance. The THE subquery or nested table column must identify a single
non-NULL table instance.
Action: Ensure that the evaluation of
the THE subquery or nested table column results in a single non-null table
instance. If happening in the context of an insert statement where the THE
subquery is the target of an insert, then ensure that an empty nested table
instance is created by updating the nested table column of the parent table's
row specifying an empty nested table constructor.
ORA-22909:
exceeded maximum VARRAY limit
Cause: The total number of elements
used in VARRAY construction exceeds the specified VARRAY limit.
Action: Don't use the more than the
specified limit of elements for VARRAY construction.
ORA-22910:
cannot specify schema name for nested tables
Cause: Table name was qualified with
schema name in the nested table column's (or attribute's) storage clause.
Action: Re-specify the nested table
item's storage clause without the schema name qualification. By default, the
storage table for the nested table item is created in the same schema as the
containing table.
ORA-22911:
duplicate storage specification for the nested table item
Cause: The storage clause is
specified more than once for the NESTED TABLE column.
Action: Remove the duplicate storage
specification.
ORA-22912:
specified column or attribute is not a nested table type
Cause: The storage clause is
specified for a column or attribute that is not a nested table column or
attribute.
Action: Specify a valid nested table
column or attribute.
ORA-22913:
must specify table name for nested table column or attribute
Cause: The storage clause is not
specified for a nested table column or attribute.
Action: Specify the nested table
storage clause for the nested table column or attribute.
ORA-22914:
DROP of nested tables not supported
Cause: Attempted to DROP a nested
table.
Action: nested tables cannot be
explicitly dropped. nested tables can only be dropped by dropping their
containing parent table.
ORA-22915:
cannot ALTER a nested table's storage table to ADD/MODIFY columns
Cause: any such change.
Action: Columns cannot be added or
modified for a nested table's storage table. You must alter the parent table's
nested table column to
ORA-22916:
cannot do an exact FETCH on a query with Nested cursors
Cause: Exact FETCH on a query was
specified which is not allowed if the query returns any cursors.
Action: Do not use an exact FETCH.
ORA-22917:
use VARRAY to define the storage clause for this column or attribute
Cause: Not using VARRAY to define
storage clause for VARRAY column or attribute.
Action: Specify VARRAY before the
column storage clause and resubmit statement.
ORA-22918:
specified column or attribute is not a VARRAY type
Cause: Attemp to define a VARRAY
storage clause for a column or attribute which is not VARRAY type.
Action: Specify VARRAY storage clause
for a VARRAY column or attribute.
ORA-22919:
dangling REF error or lock object failed for no wait request
Cause: The error could be one of the
following. The object corresponding to the REF does not exist or the object was
locked by another user and the lock with nowait request failed.
Action: Ensure that the REF value is
pointing to an existing object or issue a lock request without the nowait option.
ORA-22920:
row containing the LOB value is not locked
Cause: The row containing the LOB
value must be locked before updating the LOB value.
Action: Lock the row containing the
LOB value before updating the LOB value.
ORA-22921:
length of input buffer is smaller than amount requested
Cause: The buffer length is not big
enough to hold the amount of data requested.
Action: Verify that the number of
bytes/characters specified in the input amount parameter is not bigger than the
number of bytes specified in the input buffer length parameter. Allocate more
space for the input buffer if necessary.
ORA-22922:
nonexistent LOB value
Cause: The LOB value associated with
the input locator does not exist. The information in the locator does not refer
to an existing LOB.
Action: Repopulate the locator by
issuing a select statement and retry the operation.
ORA-22923:
amount of data specified in streaming LOB write is 0
Cause: Trying to write LOB value via
the streaming mechanism (i.e. unlimited write) but the input amount of data to
stream was specified as 0. Thus, the user is trying to write 0 bytes to the LOB
value.
Action: Write more than 0 bytes to the
LOB value.
ORA-22924:
snapshot too old
Cause: The version of the LOB value
needed for the consistent read was already overwritten by another writer.
Action: Use a larger version pool.
ORA-22925:
operation would exceed maximum size allowed for a LOB value
Cause: Trying to write too much data
to the LOB value. LOB size is limited to 4 gigabytes.
Action: Either start writing at a
smaller LOB offset or write less data to the LOB value.
ORA-22926:
specified trim length is greater than current LOB value's length
Cause: The input length for which to
trim the LOB value to is greater than the current length of the LOB value.
Action: May not need to trim the LOB
value because it's already smaller than the trim length specified. Or, if
trimming the LOB value really is required, use a smaller trim length.
ORA-22927:
invalid LOB locator specified
Cause: There are several causes: (1)
the LOB locator was never initialized; (2) the locator is for a BFILE and the
routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a
BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update
the LOB in a trigger body -- LOBs in trigger bodies are read only.
Action: For (1), initialize the LOB
locator by selecting into the locator variable or by setting the LOB locator to
empty. For (2) and (3), pass the correct type of locator into the routine. For
(4), remove the trigger body code that updates the LOB value.
ORA-22928:
invalid privilege on directories
Cause: An attempt was made to grant
or revoke an invalid privilege on a directory.
Action: Only CREATE, DELETE, READ,
WRITE and EXECUTE privileges can be granted or revoked on directories. Do not
grant or revoke other privileges.
ORA-22929:
invalid or missing directory name
Cause: The required directory name is
invalid or missing.
Action: Specify a valid name.
ORA-22930:
directory does not exist
Cause: Attempt to access a directory
that does not exist.
Action: Make sure the name is correct.
ORA-22933:
cannot change object with type or table dependents
Cause: Attempt to replace, drop or
rename an object with type or table dependents.
Action: Drop depending objects or use
FORCE option if available.
ORA-22936:
cannot replace a system predefined type
Cause: An attempt was made to replace
a system predefined type.
Action: Use other names for newly
created system types.
ORA-22950:
cannot ORDER objects without MAP or ORDER method
Cause: an object type must have a MAP
or ORDER method defined for all comparisons other than equality and inequality
comparisons.
Action: Define a MAP or ORDER method
for the object type
ORA-22951:
NULL returned by ORDER method
Cause: ORDER method used to compare
two object values returned NULL which is not allowed.
Action: Redefine the ORDER method to
not return a NULL.
ORA-22952:
Nested Table equality requires a map method on the element ADT
Cause: Nested Table equality was
tried where the element ADT did not have a map method defined on it.
Action: Define a map method on the
element ADT..
ORA-22953:
Cardinality of the input to powermultiset exceeds maximum allowed
Cause: The cardinality of the input
nested table to the powermultiset should not exceed 32 elements
Action: Reduce the number of elements
to the input.
ORA-22954:
This multiset operation is not supported for this element type.
Cause: The multiset operation
attempted was not supported for the nested table element type.
Action: Use a supported element type.
ORA-22955:
The cardinality parameter is not within the allowed limits
Cause: The cardinality parameter has
to be greater than 1 and less than or equal to the cardinality of the input.
Action: Give a valid cardinality
value.
ORA-22956:
The set contains no elements
Cause: An empty set was given as
input to the powermultiset function.
Action: Give a non-empty set as input
ORA-22957:
NULL is an invalid input to powermultiset and COLLECT functions
Cause: NULL was given as input to the
powermultiset or COLLECT function.
Action: Give a non-null value as input
ORA-22958:
This operation is not allowed in check constraints or triggers
Cause: An invalid operation is used
in a check constraint or trigger
Action: Do not use the operation
ORA-22970:
name does not correspond to an object view
Cause: Either the expression is not a
view name or the name specified does not correspond to an object view.
Action: Replace the expression with
the name of an object view.
ORA-22971:
invalid datatype for PRIMARY KEY-based object identifier
Cause: When creating an object view,
the datatype of an expression in the WITH OBJECT OID clause is not allowed for
PRIMARY KEY-based OID.
Action: Replace the expression with
one of appropriate scalar datatype.
ORA-22972:
NULL value not allowed in PRIMARY KEY-based object identifier
Cause: A value constituting the
PRIMARY KEY-based object identifier is NULL.
Action: Ensure the expressions in
MAKE_REF system function or attributes in the WITH OBJECT OID clause of an
object view do not evaluate to NULL.
ORA-22973:
size of object identifier exceeds maximum size allowed
Cause: Size of the PRIMARY KEY-based
object identifier of an object view exceeds the maximum size of 4000 bytes.
Action: Specify fewer or smaller
PRIMARY KEY attributes in the WITH object OID clause when creating the object
view.
ORA-22974:
missing WITH OBJECT OID clause
Cause: WITH OBJECT OID clause is not
specified when creating an object view.
Action: Specify the WITH OBJECT OID
clause.
ORA-22975:
cannot create a PRIMARY KEY-based REF to this object view
Cause: The object view specified in
the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A
PRIMARY KEY-based REF cannot be created for such a view.
Action: Specify an object view that
has a PRIMARY KEY-based object identifier in the MAKE_REF function.
ORA-22976:
incorrect number of arguments to MAKE_REF
Cause: Number of arguments for
MAKE_REF is different from the number of PRIMARY KEY attributes of the object
view.
Action: Specify all the necessary
arguments for MAKE_REF.
ORA-22977:
missing or invalid attribute
Cause: Either the attribute name is
missing in the WITH OBJECT OID clause or it is invalid.
Action: Specify a valid attribute of
the object type of the object view.
ORA-22978:
only simple attribute name is allowed in the WITH OBJECT OID clause
Cause: Attempted to specify a Nested
attribute in the WITH OBJECT OID clause.
Action: Specify a top-level attribute
of the object type of the object view.
ORA-22979:
cannot INSERT object view REF or user-defined REF
Cause: Attempt to insert an object
view REF or user-defined REF in a REF column created to store system generated
REF values"
Action: Make sure the REF to be
inserted is not from an object view or from a user-defined REF column
ORA-22980:
must specify a set of attributes for the WITH OBJECT OID clause
Cause: The WITH OBJECT OID DEFAULT
clause was used, but the underlying view or table does not have a OID.
Action: Specify attributes for the
WITH OBJECT OID clause to create a primary key based object identifier for the
object view.
ORA-22981:
must specify a table/view having system generated OID
Cause: The super-view is based on a
table/view having the system generated OID and the sub-view must also be based
on a similar table/view.
Action: Specify table/view having
system generated OID and retry the the operation.
ORA-22982:
cannot create sub-view under this view
Cause: The view derives its OID from
a table/view having primary key based OID and sub-views cannot be created under
such views.
Action: Specify view having system
generated OID or a view created with the specification of attributes in the
WITH OBJECT ID clause and retry the operation.
ORA-22983:
not a user-defined REF
Cause: Attempt to use a system
generated REF value where a user-defined REF value should be used.
Action: Make sure the REF value is
user-defined.
ORA-22984:
view query cannot contain references to a super view
Cause: The query defining the view
contains references to a super-view of the view being created.
Action: Make sure that the view query
does not reference a super-view.
ORA-22990:
LOB locators cannot span transactions
Cause: A LOB locator selected in one
transaction cannot be used in a different transaction.
Action: Re-select the LOB locator and retry
the operation.
ORA-22991:
insufficient space allocated for argument string
Cause: The data to be returned in the
argument is greater than the amount of space allocated for the argument.
Action: Allocate more space for the
argument.
ORA-22992:
cannot use LOB locators selected from remote tables
Cause: A remote LOB column cannot be
referenced.
Action: Remove references to LOBs in
remote tables.
ORA-22993:
specified input amount is greater than actual source amount
Cause: (1) For LOB write, the amount
of data received is different from the amount that was indicated would be sent.
(2) For LOB copy and loadfromfile, the end of the source LOB/FILE value was
reached before the specified input amount was copied/loaded.
Action: (1) will happen when using OCI's
piecewise mechanism with polling or with a callback function. Modify the code
either to send the amount specified or to pass 0 as the input amount so that
any amount of data can be sent. (2) will happen if the specified input amount
is too large for the source LOB/FILE given the starting source offset. Either
decrease the starting source offset, or decrease the amount to copy/load.
ORA-22994:
source offset is beyond the end of the source LOB
Cause: The source offset for a LOB
COPY or LOB LOADFROMFILE is beyond the end of the source LOB.
Action: Check the length of the LOB
and then adjust the source offset.
ORA-22995:
TABLESPACE DEFAULT option is invalid in this context
Cause: TABLESPACE DEFAULT option can
be specified for LOB columns only in the following contexts:
- at the
table level for a partitioned table
- at the
partition level for a composite partition. An attempt was made to use the
TABLESPACE DEFAULT option in a different context.
Action: Remove the TABLESPACE DEFAULT
option.
ORA-22996:
NEXT extent size is smaller than LOB chunksize
Cause: An attempt was made to create
or alter a LOB segment so that its NEXT extent size was less than the LOB
chunksize
Action: Specify a NEXT extent size
that is greater than or equal to the LOB chunksize
ORA-22997:
VARRAY | OPAQUE stored as LOB is not specified at the table level
Cause: An attempt was made to specify
a VARRAY|OPAQUE column to be stored as LOB at the
partition/subpartition/template level. However the VARRAY|OPAQUE column was not
specified to be stored as LOB at the table level when the table was created.
Action: Specify the VARRAY | OPAQUE
column to be stored as LOB at the table level when the table is created.
Alternatively, do not specify the VARRAY | OPAQUE column to be stored as LOB at
the partition/subpartition/template level if it is not specified at the table
level when the table is created.
ORA-22998:
CLOB or NCLOB in multibyte character set not supported
Cause: A CLOB or NCLOB in a
fixed-width or varying-width multibyte character set was passed to a SQL
character function which does not support multibyte LOB data.
Action: Use DBMS_LOB functions such as
DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR()
ORA-22999:
CLOB or NCLOB data may have been corrupted
Cause: CLOB or NCLOB contains invalid
character data. One possible cause is that the wrong csid was specified for the
external file when calling DBMS_LOB.LOADCLOBFROMFILE or
DBMS_XSLPROCESSOR.READ2CLOB to load CLOB or NCLOB data from external files.
Action: Reload the CLOB/NCLOB data
with the correct csid specified for the external file.
ORA-23290:
This operation may not be combined with any other operation
Cause: ALTER TABLE RENAME
COLUMN/CONSTRAINT operation was given in conjunction with another ALTER TBALE
Operation. This is not allowed.
Action: Ensure that RENAME
COLUMN/CONSTRAINT is the only operation specified in the ALTER TABLE.
