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.
Her are the
complete list of ORA error codes link
ORA-42301:
only COMPILE, READ ONLY, READ WRITE clause may be specified for an Editioning
view
Cause: ALTER VIEW statement with a
clause other then COMPILE, READ ONLY, READ WRITE was issued against an
Editioning view, which is the only clause supported for such views.
Action: Avoid specifying clauses other
than COMPILE, READ ONLY, READ WRITE when issuing ALTER VIEW statement against
Editioning views.
ORA-42302:
definition of an Editioning view may not refer to remote tables
Cause: An attempt was made to create
an Editioning view referring to remote tables, which is not supported.
Action: Do not create an Editioning
view if you want the view to refer to a remote table.
ORA-42303:
duplicate column reference in a definition of an Editioning view
Cause: An attempt was made create an
Editioning view referencing the same column of a base table more than once,
which is not supported.
Action: Do not create an Editioning
view if you have multiple columns referring to the same column of the base
table.
ORA-42304:
base table and the Editioning view must belong to the same schema
Cause: An attempt was made to create
an Editioning view in a schema different from that of the base table.
Action: Create an Editioning view in
the same schema as the base table.
ORA-42305:
only an Editioning view may replace an Editioning view
Cause: An attempt was made to replace
an Editioning view with a view which is not an Editioning view or vice versa.
Action: Ensure that either both or
neither of the views involved are Editioning views.
ORA-42306:
a CrossEdition trigger may not be created on an Editioning view
Cause: An attempt was made to create
a CrossEdition trigger on an Editioning view, which is not supported.
Action: Instead of creating a
CrossEdition trigger on an Editioning view, create it on the Editioning view's
underlying table.
ORA-42307:
columns of an Editioning view may only refer to base table columns
Cause: An attempt was made to define
an Editioning view containing a column referring to an entity other than a base
table column (for example, a PL/SQL function without a parameter), which is not
supported.
Action: Ensure that every column of an
Editioning view refers to a column of a base table.
ORA-42308:
view string.string is already in read-only mode
Cause: An attempt was made to set a
read-only table in read-only mode.
Action: This DDL can only be executed
on a read/write view.
ORA-42309:
view string.string is already in read/write mode
Cause: An attempt was made to set a
read/write view in read/write mode.
Action: This DDL can only be executed
on a read-only view.
ORA-42310:
Implementation restriction: this operation is only permitted on Editioning
views
Cause: The view being altered was not
an Editioning view. In this release, an ALTER VIEW READ ONLY, or ALTER VIEW
READ WRITE operation is only permitted on Editioning views.
Action: Ensure that the view is an
Editioning view.
ORA-42311:
This operation is only permitted on views with compilation erros
Cause: ALTER VIEW READ ONLY and ALTER
VIEW READ WRITE is not permitted on views which has compilation errors.
Action: Resolve the compilation
errors.
ORA-42399:
cannot perform a DML operation on a read-only view
Cause: An attempt was made to insert,
delete, or update row(s) of a view created with read-only option. DML
operations on such views are explicitly prohibited.
Action: Perform the desired DML
operation on the view's underlying base table or issue ALTER VIEW ... READ
WRITE command to make the view updatable.
ORA-43750:
invalid or illegal combination of COMMIT WRITE options
Cause: invalid or illegal combination
of options provided to COMMIT WRITE SQL statement.
Action: Provide a valid combination of
options for COMMIT WRITE statement
ORA-43751:
invalid value for parameter string
Cause: invalid or illegal value
provided for parameter.
Action: Provide a valid value for the
parameter
ORA-43807:
indexes on ORA_ROWSCN not allowed
Cause: An attempt was made to create
an index that refers to the ORA_ROWSCN pseudo-column, either directly or in an
expression.
Action: Do not use ORA_ROWSCN to
define an index on a table.
ORA-43851:
LOB feature unsupported below compatible 11.0.0
Cause: An 11g LOB feature was
specified when the RDBMS is operating at a compatible setting lower than
"11.0.0".
Action: Upgrade the RDBMS compatible
setting to "11.0.0" or higher to enable the desired new features.
ORA-43852:
SECUREFILE and BASICFILE cannot be used together
Cause: SECUREFILE and BASICFILE were
both specified.
Action: Modify the SQL statement to
specifiy only one of SECUREFILE or BASICFILE.
ORA-43853:
SECUREFILE lobs cannot be used in non-ASSM tablespace "string"
Cause: SECUREFILE lobs require ASSM
Action: Specify an ASSM tablespace for
SECUREFILE lobs.
ORA-43854:
use of a BASICFILE LOB where a SECUREFILE LOB was expected
Cause: A BASICFILE LOB was used in a
SQL statement or in a call where a SECUREFILE LOB was expected.
Action: Convert the LOB to a
SECUREFILE LOB or don't use this keyword or call.
ORA-43856:
Unsupported object type for SECUREFILE LOB operation
Cause: A SECUREFILE Lob operation was
issued on an unsupported object type.
Action: Don't use this function for
BASICFILE LOBs.
ORA-43857:
Parameter Error
Cause: Attempt to modify a LOB with
an invalid parameter.
Action: Fix paramters and retry the
operation.
ORA-43883:
SECUREFILE LOBs delta update invalid operation
Cause: Invalid delta update operation
was issued on LOB. This includes operation beyond LOB length; move operation
with destination offset inside move interval.
Action: Check operation parameters for
validity.
ORA-44001:
invalid schema
Cause: The schema for the given
schema name did not exist.
Action: Provide a valid schema name.
ORA-44002:
invalid object name
Cause: The input parameter string was
not a qualified SQL identifier of an existing SQL object.
Action: Make sure the string matches an existing SQL object that is
accessible by the current schema.
ORA-44003:
invalid SQL name
Cause: The input parameter string was
not a valid simple SQL name.
Action: Check with the DBMS_ASSERT
spec to verify that the parameter string is a valid simple SQL name.
ORA-44004:
invalid qualified SQL name
Cause: The input parameter string was
not a valid qualified SQL name.
Action: Check with the DBMS_ASSERT
spec to verify that the parameter string is a valid qualified SQL name.
///////////////////////////////////////////////////////////////////////////
Reserving 44101 - 44200 for UTL_MAIL errors
///////////////////////////////////////////////////////////////////////////
ORA-44101:
invalid priority
Cause: The priority level given by
the user was invalid.
Action: See UTL_MAIL for valid
priority values and change the priority parameter accordingly.
///////////////////////////////////////////////////////////////////////////
Reserving 44201 - 44300 for Shared Cursor (KKS) errors
///////////////////////////////////////////////////////////////////////////
ORA-44203:
timeout waiting for lock on cursor
Cause: A timeout occured while
waiting for a cursor to be compiled. This is usually caused by the SQL parse
requiring access to system resources which are locked by concurrently executing
sessions.
Action: Investigate possible causes of
resource contention. If neccessary, contact support for additional information
on how to diagnose this problem.
///////////////////////////////////////////////////////////////////////////
Reserving 44301 - 44320 for DBMS_SERVICES errors
///////////////////////////////////////////////////////////////////////////
ORA-44301:
NULL service name is not permitted
Cause: The service name argument was
found to be NULL.
Action: Provide a non-NULL service
name.
ORA-44302:
NULL network name is not permitted
Cause: The network name argument was
found to be NULL.
Action: Provide a non-NULL network
name.
ORA-44303:
service name exists
Cause: This service name was already
in existence.
Action: Provide a new unique service
name.
ORA-44304:
service string does not exist
Cause: The specified service was not
in existence.
Action: Provide a valid service name.
ORA-44305:
service string is running
Cause: The specified service was
running.
Action: This message is informational
only.
ORA-44306:
service name exceeds maximum length of string
Cause: The service name was too long.
Action: Use a shorter service name.
ORA-44307:
network name too long
Cause: The network name, excluding
the domain, was too long.
Action: Use a shorter network name.
ORA-44310:
maximum number of services exceeded
Cause: The maximum number of services
has been reached.
Action: None
ORA-44311:
service string not running
Cause: The specified service was not
running.
Action: This message is informational
only.
ORA-44312:
database closed
Cause: The database was closed.
Action: Open the database and retry
the operation.
ORA-44313:
instance name invalid
Cause: The instance name argument was
not valid.
Action: Provide a valid instance name.
ORA-44314:
network name already exists
Cause: The network name was already
in existence.
Action: Use an alternate network name.
ORA-44315:
all service attributes null
Cause: All attributes specified were
null.
Action: At least one attribute must be
non-null.
ORA-44316:
invalid argument
Cause: Invalid argument supplied.
Action: Supply a valid argument.
ORA-44317:
database open read-only
Cause: The database is open
read-only.
Action: Close the database and reopen
it read/write before trying again.
ORA-44318:
exceeded maximum SERVICE_NAMES length
Cause: The total length of all
running service network names exceeded the maximum allowable length.
Action: Stop another service to start
this one.
ORA-44321:
cannot read command line from trace file string
Cause: Trace file could not be read.
Action: Make sure trace file exists
and contains valid raw trace data.
ORA-44322:
invalid file name 'string'
Cause: A NULL or zero length file
name was specified.
Action: Correct the file name to be a
nonzero length string.
ORA-44323:
negative 'number' to string option
Cause: The given count was a
nonpositive number.
Action: Provide a positive count
number.
ORA-44324:
no argument to string option
Cause: Count number was missing for
the option.
Action: Provide a count number to the
option.
ORA-44325:
no entry points found in trace file string
Cause: The given trace symbol was not
found.
Action: None
ORA-44326:
no argument to string option
Cause: argument to
-[un]trace option was missing.
Action: Provide
argument to -[un]trace option.
ORA-44327:
no argument to string option
Cause: argument to
the option was missing.
Action: Provide
argument to the option.
ORA-44328:
unsupported version number: string
Cause: Version of the trace file was
not supported.
Action: Provide supported version of
trace file.
ORA-44403:
invalid value specified for flag parameter
Cause: Mutually exclusive values were
specified for the flag parameter.
Action: Internal error. Contact Oracle
Support Services.
ORA-44404:
upicui2 client function requires Oracle server of 10.2 or higher
Cause: A 10.2 or higher client is
being used with an older Oracle server.
Action: Use an Oracle server with the
same version as the client.
ORA-44411:
Invalid ACL: START_DATE cannot be larger than END_DATE for all ACE
Cause: The END_DATE was smaller than
the START_DATE in one of the ACE's in this ACL.
Action: Set all END_DATE to be larger
than or equal to the START_DATE in each of the ACE's in this ACL.
ORA-44412:
Invalid ACL: Cyclic ACL inheritance is not allowed
Cause: A cycle was formed by ACL
inheritance.
Action: Check the ACL inheritance and
break the cycle by removing some ACL inheritance.GG function exceeds system
limits.
ORA-44413:
Invalid ACL: Security class of parent ACL must be an ancestor of security class
of child ACL
Cause: Security class of parent ACL
was not an ancestor of security class of child ACL
Action: Change the security class of
parent ACL to be an ancestor of security class of child ACL.
ORA-44414:
Invalid ACL: Parent ACL 'string' does not exist
Cause: The path to the parent ACL was
not a valid resource.
Action: Change the parent ACL of this
resource or create the parent ACL at the specified location.
ORA-44415:
Invalid ACL: Undefined privileges
Cause: An undefined privilege was
found in an ACE in the ACL.
Action: Make sure the privilege is
defined in the security class as specified in the ACL.
ORA-44416:
Invalid ACL: Unresolved principal 'string'
Cause: An unresolved principal is
found in an ACE in the ACL.
Action: Make sure the principal is a
valid user or role in the system.
ORA-44417:
Invalid ACL: Invalid ACLID
Cause: The specified ACLID did not
point to a valid ACL document.
Action: Make sure the ACLID points to
a valid ACL document.
ORA-44421:
cannot DISALLOW NONSCHEMA without a SCHEMA clause
Cause: If no SCHEMA clause (explicit
schema or ANYSCHEMA) was specified, nonschema data cannot be disallowed.
Action: Remove DISALLOW NONSCHEMA or
add some SCHEMA clause.
ORA-44422:
nonschema XML disallowed for this column
Cause: An attempt was made to insert
nonschema based XML documents in a binary XML column that disallows nonschema
data.
Action: Insert only schema-based
documents or alter the column to ALLOW NONSCHEMA data.
ORA-44423:
XML Schema registered for BINARY cannot be used for CLOB/OBJ-REL
Cause: An attempt was made to use a
XML Schema registered for binary usage as part of a CLOB or OBJ-REL clause.
Action: Specify a schema registered
for CLOB or OBJ-REL use. Else specify BINARY XML storage for column.
ORA-44424:
BINARY XML storage requires XML Schema registered for BINARY usage
Cause: An attempt was made to specify
BINARY XML storage using an XML schema not registered for BINARY.
Action: Specify a schema registered
for BINARY usage. Else specify CLOB or OBJ-REL storage for column.
ORA-44501:
QMEL: Too much concurrency.
Cause: Too much concurrency
Action: Transient error, try again.
ORA-44502:
QMEL: Lock not found.
Cause: Lock not found
Action: Check arguments
ORA-44503:
QMEL: Lock Denied.
Cause: Lock denied
Action: None
ORA-44504:
Resource Locked by Implicit Lock
Cause: The resource is locked by an
implicit lock
Action: Implicit locks are normally
caused by NFS locks. Refer to XDB Protocol guide for removing/obtaining
information about implicit locks.
ORA-44505:
QMEL: Invalid arguments.
Cause: Arguments to QMEL are not
correct.
Action: None
ORA-44700:
Language 'string' is not a valid language for a translation
Cause: Invalid language.
Action: The language must conform to
IETF RFC 3066.
ORA-44701:
Language not found for translation
Cause: The document had multiple
translations and one of them did not have the xml:lang attribute.
Action: All translations must have the
xml:lang attribute when multiple translations are present.
ORA-44702:
Multiple translations found for language 'string'
Cause: The document had multiple
translations for a language.
Action: The document must contain only
one translation per language for every translated element.
ORA-44703:
Multiple source language translations found
Cause: The document had multiple
source language translations.
Action: The document must contain only
one source language translation for every translated element.
ORA-44704:
XPath 'string' does not uniquely identify a translated element
Cause: The given XPath pointed to
multiple translated elements.
Action: The given XPath must uniquely
identify a translated element.
ORA-44705:
Must have xdb:maxOccurs='1' for translated elements
Cause: The value of xdb:maxOccurs was
not '1' for a translated element.
Action: The value of xdb:maxOccurs
must be '1' for a translated element.
ORA-44706:
Must have xsd:maxOccurs='unbounded' for translated elements
Cause: The value of xsd:maxOccurs was
not 'unbounded' for a translated element.
Action: The value of xsd:maxOccurs
must be 'unbounded' for a translated element.
ORA-44707:
No source language translation found
Cause: The document had no source
language translation for a translated element.
Action: The document must contain
exactly one source language translation for every translated element.
ORA-44708:
Translations not supported for object relational storage
Cause: The storage type of the schema
was object relational.
Action: Register the schema with
storage type as clob or binary xml.
ORA-44709:
Invalid schema definition for translated element
Cause: The schema definition for a
translated element was invalid.
Action: A translated element must be a
complex type with simple content which is a restriction or extension of
xs:string.
ORA-44710:
Malformed XLIFF document: string
Cause: The XLIFF document was
malformed.
Action: Fix the error and try again.
ORA-44711:
XPath refers to an untranslatable element
Cause: XPath pointed to an
untranslatable element.
Action: XPath for this operation must
refer to a translatable element.
ORA-44712:
Invalid XPath in XLIFF document used for merging
Cause: XPath within trans-unit/id
attribute was invalid.
Action: XPath within trans-unit/id
attribute must point to a set of translations, not to a particular translation.
ORA-44713:
XPath does not select all translations
Cause: XPath did not select all
translations for a particular element.
Action: XPath must point to a set of
translations, not to a particular translation.
ORA-44730:
XML Index string is not usable at the moment
Cause: The async XML Index could not
be used since ORACLE is not open for query.
Action: Try the same query again when
ORACLE is open for query, or use NO_XMLINDEX_REWRITE hint.
ORA-44731:
Path string cannot be removed from the repository XML Index
Cause: The repository XML Index
indexed one of the parent folders of the resource identified by given path.
Action: Try removing the parent folder
from the repository XML Index.
ORA-44732:
Path string cannot be removed from the repository XML Index
Cause: The repository XML Index did
not index the resource identified by given path.
Action: Try removing a resource that
is indexed by the repository XML Index.
ORA-44733:
The repository XML Index cannot be dropped directly
Cause: DROP INDEX could not be used
on the repository XML Index.
Action: Try using
DBMS_XDB_ADMIN.DROPREPOSITORYXMLINDEX.
ORA-44751:
XML schema enumeration index is out of range
Cause: The enumeration item
corresponding to the enumeration index could not be found in the XML schema.
Action: If the XML schema has been
evolved, try restarting the client that performed the evolution.
ORA-44752:
New element 'string' in complex type 'string' has the same
qualified name as another element
Cause: The new element that was added
to a complex type by in-place XML schema evolution had the same qualified name
as another element in the same complex type or in one of its ancestor complex
types.
Action: Try adding an element with a
different qualified name.
ORA-44753:
Change to minOccurs attribute of element 'string' is illegal
Cause: The value of attribute
minOccurs on an element could not be increased by in-place XML schema
evolution.
Action: Do not increase the value of
attribute minOccurs.
ORA-44754:
Change to maxOccurs attribute of element 'string' is illegal
Cause: The value of attribute
maxOccurs on an element could not be decreased by in-place XML schema
evolution.
Action: Do not decrease the value of
attribute maxOccurs.
ORA-44755:
Change to complexType property of element 'string' is illegal
Cause: The complexType property on an
element could not be changed by in-place XML schema evolution.
Action: Do not change the complexType
property.
ORA-44756:
Change to SQLType attribute of element 'string' is illegal
Cause: The SQLType property on an
element in a binary XML schema could not be changed by in-place XML schema
evolution.
Action: Do not change the SQLType
property.
ORA-44800:
Number of classifiers cannot be NULL
Cause: The num_classifiers argument
was found to be NULL.
Action: Provide a non-NULL num_classifiers.
ORA-44801:
NULL classifier list not permitted
Cause: The wlm_classifiers argument
was found to be NULL.
Action: Provide a non-NULL
wlm_classifiers.
ORA-44802:
No new plan (classifier list) has been submitted
Cause: No new plan was created before
submission.
Action: Create a new plan, followed by
adding classifier & PC lists.
ORA-44803:
Plan is in transition (about to be activated)
Cause: New plan was attempted to be
created before activating the current plan.
Action: Completely submit the current
plan and activate it.
ORA-44804:
Plan is not created yet
Cause: A new plan was not created
before submitting the Classifier and Performance Class lists.
Action: Call dbms_wlm.create_plan
first to create the plan.
ORA-44805:
No classifier is present
Cause: The classifier list contained
no classifiers.
Action: Check the syntax of the
classifier list.
ORA-44806:
Extra classifiers are present in list
Cause: More classifiers were present
in the list than specified.
Action: Only include the number of
classifiers less than or equal to num_classifiers mentioned in
dbms_wlm.create_plan.
ORA-44807:
Peformance Class name is too large
Cause: The Performance Class name was
larger than 32 bytes.
Action: Rename the Performance Class
to fit within 32 bytes.
ORA-44808:
Work Request Class name is too large
Cause: The Work Request Class name
was larger than 32 bytes.
Action: Rename the Work Request Class
to fit within 32 bytes.
ORA-44809:
No expression is present for classifier
Cause: This classifiers contained no
expression. It should contain one more more expressions.
Action: Check syntax in the classifier
list.
ORA-44810:
No parameter is present for expression
Cause: This expression contained no
paramaters or attribute values. It should contain one or more attribute values.
Attributes can be SERVICE, MODULE, ACTION, PROGRAM or USER.
Action: Check syntax in the classifier
list.
ORA-44811:
Service name is too large
Cause: The service name mentioned in
the parameter list was too large.
Action: Check the service name.
ORA-44812:
Module name is too large
Cause: The module name mentioned in
the parameter list was too large.
Action: Check the module name.
ORA-44813:
Action name is too large
Cause: The action name mentioned in
the parameter list was too large.
Action: Check the action name.
ORA-44814:
Program name is too large
Cause: The program name mentioned in
the parameter list was too large.
Action: Check the program name.
ORA-44815:
User name is too large
Cause: The user name mentioned in the
parameter list was too large.
Action: Check the user name.
ORA-44816:
Number of Performance Classes is less than specified
Cause: The number of Performance
Classes submitted were less than what was specified.
Action: Submit the full list of
Performance Classes.
ORA-44817:
Classifier list is too large
Cause: The length of the classifier
list was greater than 2048 bytes.
Action: Break the list into two lists
before submission.
ORA-44818:
General failure
Cause: There was an unknown failure.
Action: Contact Oracle Support Services.
ORA-44819:
Execution of this WLM function is denied
Cause: Either a WLM plan was being
loaded from another instance, or the strict order of the PL/SQL calls for
loading WLM plan was not followed.
Action: Check if another session is
also concurrently trying to load a WLM plan. If that is not true, check the
order in which you are making these PL/SQL calls to load your WLM plan.
ORA-44820:
Number of Work Request Classes is less than specified
Cause: The number of Work Request
Classes submitted were less than what was specified.
Action: Submit the full list of Work
Request Classes.
ORA-44821:
Number of classifiers is too large
Cause: A very large number ( >
1024) of classifiers were requested.
Action: Submit a smaller ( < 1024)
number of classifiers. ///////////////////////////////////////////////////////////////////////////
44901 - 44950 reserved for XML DB LINKS related error codes.
///////////////////////////////////////////////////////////////////////////
ORA-44901:
Unable to resolve symbolic link "string"
Cause: The system is unable to
resolve the specified symbolic link.
Action: Check the definition of the
symbolic link to ensure that this refers to a valid resource.
ORA-44902:
Too many steps in resolving symbolic link "string"
Cause: This error is raised when the
system is unable to fully resolve a path with symbolic links within a
reasonable number of steps. It could be due to cycles in definitions of
symbolic links or very long chains of symbolic links to symbolic links.
Action: Remove any cycles in symbolic
link definitions. If there are no cycles, reduce the length of chains of
symbolic links to symbolic links.
ORA-44903:
Cannot create hard link to specified resource
Cause: The system cannot create a
hard link to the specified resource.
Action: Check the configuration
parameter(s) to verify the restrictions on creating hard links to folder or
non-folder resources.
ORA-44904:
target path in document link exceeds maximum length
Cause: Target path length exceeds the
maximum which can be stored to disk.
Action: Reduce target path to smaller
length
ORA-44905:
extended link type not supported
Cause: XLink type attribute is
extended.
Action: Remove extended link, or
replace with simple link.
ORA-44906:
unable to resolve target in document link
Cause: target path does not resolve
to valid resource.
Action: check validity of target path.
ORA-44907:
can not delete with incoming hard document links
Cause: there is a hard document link
with this resource as the target.
Action: query DOCUMENT_LINKS view to
see which resource has a hard link to this resource. Change the document link
in the source resource accordingly.
ORA-44908:
found a loop in XInclude elements while expanding string
Cause: There is a loop in XInclude
elements within the document.
Action: Remove the loop in XInclude
elements.
ORA-44909:
href attribute is required within XInclude element
Cause: The href attribute is missing
within XInclude element.
Action: Add the href attribute.
ORA-44910:
xpointer not supported within XInclude element
Cause: The xpointer attribute is
specified within XInclude element.
Action: Remove the xpointer attribute.
ORA-44911:
exceeded maximum depth of nested xinclude expansion
Cause: The depth of nested xinclude
expansion has exceeded system limit.
Action: Reduce the depth of nested
xinclude expansion.
ORA-44912:
invalid or unsupported xpath expression string
Cause: The specified xpath is either
invalid or unsupported in this context.
Action: Change the xpath expression.
ORA-44913:
error while processing XInclude string
Cause: There was an error while
processing the specified XInclude.
Action: Ensure that the XInclude
attributes are correct.
RA-46000:
Invalid option to enable Extensible Data Security
Cause: Input value was not a valid
option to enable XDS.
Action: Use a valid option to enable
XDS.
ORA-46001: string is
not valid for Extensible Data Security policies
Cause: An illegal argument value was
used with DBMS_RLS to enable XDS.
Action: Use DBMS_XDS to enable XDS.
ORA-46002:
Privilege "string" is not valid in Data Security Document for
"string"
Cause: An invalid privilege was
specified in the Data Security Document.
Action: Correct the privilege element
in the document.
ORA-46003:
Column "string" is not valid in Data Security Document for
"string"
Cause: An invalid column was
specified in the Data Security Document.
Action: Correct the column element in
the document.
///////////////////////////////////////////////////////////////////////////
46050 - 46099 Reserved for eXtensible Security Sessions (XSS) ///////////////////////////////////////////////////////////////////////////
ORA-46051:
Invalid XS user specified
Cause: An invalid extensible security
user was specified.
Action: Check the user name and
execute the function or procedure again.
ORA-46052:
Invalid Session ID specified
Cause: An invalid extensible security
session ID was specified.
Action: Check the session ID and
execute the function or procedure again.
ORA-46053:
Invalid Cookie specified
Cause: An invalid extensible security
session cookie was specified.
Action: Check the session cookie and
execute the function or procedure again.
ORA-46054:
Invalid Namespace specified
Cause: An invalid extensible security
application namespace was specified.
Action: Check the namespace and
execute the function or procedure again.
ORA-46055:
Invalid Role specified
Cause: An invalid extensible security
role was specified.
Action: Check the role and execute the
function or procedure again.
ORA-46056:
Invalid Namespace or Attribute specified
Cause: An invalid extensible security
application namespace or attribute was specified.
Action: Check the namespace and
attribute, and execute the function or procedure again.
ORA-46057:
Namespace already exists
Cause: The specified extensible
security application namespace was already in existence.
Action: Execute the function or
procedure with a different namespace.
ORA-46058:
Invalid attribute specified
Cause: An invalid extensible security
application namespace attribute was specified.
Action: Check the attribute, and execute
the function or procedure.
ORA-46059:
Invalid ACL identifier specified
Cause: The specified ACL identifier
is invalid.
Action: Check the ACL identifier, and
execute the function or procedure again with a valid ACL ID.
ORA-46060:
Username not specified
Cause: Extensible security Username
was not specified.
Action: Execute the function or
procedure with a username.
ORA-46061:
Session ID not specified
Cause: Extensible security Session ID
was not specified.
Action: Execute the function or
procedure with a session ID.
ORA-46062:
Namespace not specified
Cause: Extensible security
Application namespace was not specified.
Action: Execute the function or
procedure with a namespace.
ORA-46063:
Not attached to XS session
Cause: Not attached to an Extensible
security session.
Action: Attach to a XS session and
execute the function or procedure.
ORA-46064:
Attribute name not specified
Cause: Extensible security
Application namespace attribute name was not specified.
Action: Execute the function or
procedure with an attribute name.
ORA-46065:
Attribute value not specified
Cause: Extensible security
Application namespace attribute value was not specified.
Action: Execute the function or
procedure with an attribute value.
ORA-46066:
Inactivity Timeout not specified
Cause: Extensible security session
inactivity timeout was not specified.
Action: Execute the function or
procedure with an inactivity timeout value.
ORA-46067:
Cookie not specified
Cause: Extensible security session
cookie was not specified.
Action: Execute the function or
procedure with a cookie value.
ORA-46068:
Role not specified
Cause: Extensible security Role was
not specified.
Action: Execute the function or
procedure with a Role value.
ORA-46070:
Insufficient privileges
Cause: An attempt was made to execute
an Extensible security session function or procedure without the appropriate
privilege.
Action: Ask the administrator to
perform the operation or to grant the appropriate privilege.
ORA-46071:
Error occurred while executing the event handler
Cause: An error or exception was
returned by the error handling function invoked as part of the current
operation.
Action: Check the trace files to
identify the source of the error in the event handling function. Attempt the
operation again after the error has been resolved.
ORA-46072:
Column width too small
Cause: The size of the column or
variable used to store the output of this function or procedure is too small.
Action: Increase the size of the
column or variable and try again.
ORA-46073:
Cookie already exists
Cause: The specified Extensible
security session cookie was used by another Extensible security session.
Action: Execute the function or
procedure with a different cookie.
ORA-46074:
session ID mismatch
Cause: The specified session ID does
not match the attached session ID.
Action: Execute the function or
procedure without a session ID or with a matching attached session.
ORA-46075:
Already attached to a lightweight user session
Cause: The current database session
is already attached to a lightweight user session.
Action: Detach from the current
lightweight user session before attaching to the new lightweight user session.
ORA-46076:
The specified name string is too long
Cause: The length of the name is
longer than allowable limits.
Action: Please try again with a new
name with a length smaller than the allowable length. Please refer to the
documentation to identify the maximum name length for the current operation.
ORA-46077:
Length of value too large
Cause: The specified attribute value is
too large.
Action: Execute the function or
procedure again with a smaller attribute value.
ORA-46078:
Invalid event type specified
Cause: The event type specified is
invalid.
Action: Reattempt the operation with
an invalid event type. ///////////////////////////////////////////////////////////////////////////
46100 - 46149 Reserved for eXtensible Security Security Class (XSC)
///////////////////////////////////////////////////////////////////////////
ORA-46101:
Circular definition for aggregate privilege string in security
class string
Cause: Definition of an aggregate
privilege contained itself.
Action: Fix the aggregate privilege
definition.
ORA-46102:
Privilege string aggregated in security class string is
not found
Cause: Definition of an aggregate
privilege contained a privilege that is not defined in this or parent security
classes.
Action: Fix the aggregate privilege
definition.
ORA-46103:
Circular definition for security class string
Cause: Security class definition
inherited from itself through circular definition.
Action: Fix the security class
definition.
ORA-46104:
Security class string cannot inherit from base security
classes
Cause: Definition of a security class
specified an internal base security class as a parent security class.
Action: Remove the internal base
security class from the "inherits-from" list.
ORA-46105:
Unable to load security class string
Cause: The specified security class
did not exist.
Action: Create resource for the
security class.
ORA-46106:
Missing parent security class for security class string
Cause: The specified security class
did not have any parent security class.
Action: Add a parent security class
using "inherits-from" tag.
ORA-46107:
Unable to load security class for privilege string:string
Cause: The specified privilege did
not exist.
Action: Create a security class
resource for the privilege.
ORA-46108:
Invalid security class targetNamespace or name.
Cause: The security class
targetNamespace attribute was either null or was longer than 4000 characters. Or,
the security class name attribute was either null or was longer than 1024
characters.
Action: Provide valid targetNamespace
and name attributes.
///////////////////////////////////////////////////////////////////////////
46250 - 46350 Reserved for Database Auditing
///////////////////////////////////////////////////////////////////////////
ORA-46250:
Invalid value for argument 'string'
Cause: Input value was not valid for
the procedure.
Action: Use a valid option.
ORA-46251:
Value for argument 'string' out of range
Cause: Input value was out of range.
Action: Use a value within allowed
range.
ORA-46252:
Cannot complete the operation, overlapping job already exists
Cause: Cleanup job already existed
which spanned the given audit trail type.
Action: Drop the existing job.
ORA-46253:
Cannot complete the operation, overlapping property already exists
Cause: The property already exists
which spans the given audit trail type.
Action: Clear the existing property.
ORA-46254:
'string' already exists
Cause: The value being set already
existed.
Action: Delete the existing entry.
ORA-46255:
Incorrect job name specified
Cause: The job did not exist or was
not created by DBMS_AUDIT_MGMT package.
Action: Create the job using
DBMS_AUDIT_MGMT package.
ORA-46256:
Internal error: Audit Table not partitioned
Cause: Invalid operation on a non
partitioned table.
Action: Contact Oracle Support
Services.
ORA-46257:
Property 'string' cannot be cleared
Cause: The property could not be
cleared.
Action: None. The property can only be
set or reset.
ORA-46258:
Cleanup not initialized for the audit trail
Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP
was not called for the erroring audit trail.
Action: Invoke the procedure,
DBMS_AUDIT_MGMT.INIT_CLEANUP.
ORA-46260:
Error during audit trail cleanup
Cause: The audit trail cleanup
operation could not be completed.
Action: Check the UNIX error number
for a possible operating system error. If there is no error, contact Oracle
Support Services.
ORA-46261:
Error during audit trail cleanup, internal error
Cause: The audit trail cleanup could
not be completed because of an internal error.
Action: Contact Oracle Support
Services.
ORA-46262:
Audit table(s) cannot be moved to 'string' tablespace
Cause: The tablespace was either
unavailable or did not have enough space to accomodate the audit table being
moved.
Action: Make sure that the tablespace
is online and has enough space for the audit tables being moved.
ORA-46263:
The audit trail is already initialized for cleanup
Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP
was already invoked for the audit trail type.
Action: None
ORA-46264:
Error during DBMS_AUDIT_MGMT operation
Cause: Could not complete the
operation.
Action: Check the PL/SQL error stack
for a possible error. If there is no error, contact Oracle Support Services.
ORA-47000:
Factor Type string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47001:
Factor Type string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47002:
error creating Factor Type string, string
Cause: An unexpected error occurred
creating the factor type
Action: Please review the definition
and retry the operation
ORA-47003:
error deleting Factor Type string, string
Cause: An unexpected error occurred
deleting the factor type
Action: Please review the definition
and retry the operation
ORA-47004:
error updating Factor Type string, string
Cause: An unexpected error occurred updating
the factor type
Action: Please review the definition
and retry the operation
ORA-47005:
error renaming Factor Type string, string
Cause: An unexpected error occurred
renaming the factor type
Action: Please review the definition
and retry the operation
ORA-47020:
Factor string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47021:
Factor string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47022:
error creating Factor string, string
Cause: An unexpected error occurred
creating the factor
Action: Please review the definition
for accuracy and retry the operation
ORA-47023:
error deleting Factor string, string
Cause: An unexpected error occurred
deleting the factor
Action: Please review the definition
for accuracy and retry the operation
ORA-47024:
error updating Factor string, string
Cause: An unexpected error occurred
updating the factor
Action: Please review the definition
for accuracy and retry the operation
ORA-47025:
Factor Link already exists for string and string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47026:
error creating Factor Link for string and string, string
Cause: An unexpected error occurred
creating the factor link
Action: Please review the definition
for accuracy and retry the operation
ORA-47027:
Factor Link does not exist for string and string
Cause: The factor link referenced
does not exist
Action: Please review the definition
for accuracy and retry the operation
ORA-47028:
error deleting Factor Link for string and string, string
Cause: An unexpected error occurred
deleting the factor link
Action: Please review the definition
for accuracy and retry the operation
ORA-47040:
Identity string for Factor string already
defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47041:
Identity string for Factor string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47042:
error creating Identity string for Factor string, string
Cause: An unexpected error occurred
creating the identity
Action: Please review the definition
for accuracy and retry the operation
ORA-47043:
error deleting Identity string for Factor string, string
Cause: An unexpected error occurred
deleting the identity
Action: Please review the definition
for accuracy and retry the operation
ORA-47044:
error updating Identity string for Factor string, string
Cause: An unexpected error occurred
updating the identity
Action: Please review the definition
for accuracy and retry the operation
ORA-47060:
Identity map for Identity string.string, Factor Link string, string already
defined for operation string on string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47061:
Identity map for Identity string.string, Factor Link string, string not
found for operation string on string
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47062:
error creating Identity map for Identity string.string,
Factor Link string, string already defined for
operation string on string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47063:
error deleting Identity map for Identity string.string,
Factor Link string, string already defined for
operation string on string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47080:
code string already defined in group string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47081:
code string not found in group string
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47100:
Command Rule string already defined for string.string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47101:
Command Rule string not found for string.string
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47102:
error creating Command Rule string for string.string, string
Cause: An unexpected error occurred
creating the command rule
Action: Please review the definition
for accuracy and retry the operation
ORA-47103:
error deleting Command Rule string for string.string, string
Cause: An unexpected error occurred
deleting the command rule
Action: Please review the definition
for accuracy and retry the operation
ORA-47104:
error updating Command Rule string for string.string, string
Cause: An unexpected error occurred
updating the command rule
Action: Please review the definition
for accuracy and retry the operation
ORA-47105:
invalid object owner string for command string
Cause: The object owner is invalid
for this command
Action: Choose an object owner other
than SYS or a wildcard for this command
ORA-47120:
Document string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47121:
Document string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47140:
Factor expression string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47141:
Factor expression string not found
Cause: The object being requested
does not exists
Action: Choose an object name that
exists and retry the operation
ORA-47160:
Factor link string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47161:
Factor link string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47180:
Integration Policy for OLS Policy string is already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47181:
Integration Policy for OLS Policy string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47182:
Label algorithm string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47183:
error creating Integration Policy for OLS Policy string, string
Cause: An unexpected error occurred
creating the integration policy
Action: Please review the definition
for accuracy and retry the operation
ORA-47184:
error updating Integration Policy for OLS Policy string, string
Cause: An unexpected error occurred
updating the integration policy
Action: Please review the definition
for accuracy and retry the operation
ORA-47185:
error deleting Integration Policy for OLS Policy string, string
Cause: An unexpected error occurred
deleting the integration policy
Action: Please review the definition
for accuracy and retry the operation
ORA-47200:
Integration Policy Factor already defined for Factor string and
Policy string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47201:
Integration Policy Factor not found for Factor string and
Policy string
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47202:
error creating Integration Policy Factor for factor string and
policy string, string
Cause: An unexpected error occurred
creating the integration policy factor
Action: Please review the definition
for accuracy and retry the operation
ORA-47203:
error deleting Integration Policy Factor for factor string and
policy string, string
Cause: An unexpected error occurred
deleting the integration policy factor
Action: Please review the definition
for accuracy and retry the operation
ORA-47220:
Label string for Identity string.string under
OLS Policy string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name and
retry the operation
ORA-47221:
Label string for Identity string.string under
OLS Policy string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47222:
error creating Label string for Identity string.string under
OLS Policy string, string
Cause: An unexpected error occurred
creating the identity label
Action: Please review the definition
for accuracy and retry the operation
ORA-47223:
error deleting Label string for Identity string.string under
OLS Policy string, string
Cause: An unexpected error occurred
deleting the identity label
Action: Please review the definition
for accuracy and retry the operation
ORA-47240:
Realm string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47241:
Realm string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47242:
error creating Realm string, string
Cause: An unexpected error occurred
creating the realm
Action: Please review the definition
for accuracy and retry the operation
ORA-47243:
error deleting Realm string, string
Cause: An unexpected error occurred
deleting the realm
Action: Please review the definition
for accuracy and retry the operation
ORA-47244:
error updating Realm string, string
Cause: An unexpected error occurred
updating the realm
Action: Please review the definition
for accuracy and retry the operation
ORA-47245:
error renaming Realm string, string
Cause: An unexpected error occurred
renaming the realm
Action: Please review the definition
for accuracy and retry the operation
ORA-47260:
Realm Authorization to string for Realm string already
defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47261:
Realm Authorization to string for Realm string not
found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47262:
error creating Realm Authorization to string for Realm string, string
Cause: An unexpected error occurred
creating the realm authorization
Action: Please review the definition
for accuracy and retry the operation
ORA-47263:
error deleting Realm Authorization to string for Realm string, string
Cause: An unexpected error occurred
deleting the realm authorization
Action: Please review the definition
for accuracy and retry the operation
ORA-47264:
error updating Realm Authorization to string for Realm string, string
Cause: An unexpected error occurred
updating the realm authorization
Action: Please review the definition
for accuracy and retry the operation
ORA-47280:
Realm Object string,string.string already
defined in Realm string
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47281:
Realm Object string,string.string not found in
Realm string
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47282:
error adding Realm Object string,string.string to
Realm string, string
Cause: An unexpected error occurred
creating the realm object
Action: Please review the definition
for accuracy and retry the operation
ORA-47283:
error deleting Realm Object string,string.string from
Realm string, string
Cause: An unexpected error occurred
deleting the realm object
Action: Please review the definition
for accuracy and retry the operation
ORA-47284:
error adding Realm Object string.string. string is
not a valid object type
Cause: The specified object type is
not valid.
Action: Enter a valid object type for
the specified object name, or enter "%" and all objects with the
specified name and the specified owner will be added to the realm.
ORA-47290:
error creating VPD policy for Realm string, string
Cause: An unexpected error occurred
creating the VPD policy
Action: Please review the definition
for accuracy and retry the operation
ORA-47300:
Role already string defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47301:
Role string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47302:
error creating Role string, string
Cause: An unexpected error occurred
creating the role
Action: Please review the definition
for accuracy and retry the operation
ORA-47303:
error deleting Role string, string
Cause: An unexpected error occurred
deleting the role
Action: Please review the definition
for accuracy and retry the operation
ORA-47304:
error updating Role string, string
Cause: An unexpected error occurred
updating the role
Action: Please review the definition
for accuracy and retry the operation
ORA-47305:
Rule Set violation on string (string)
Cause: An operation that was
attempted failed due to a rule set violation
Action: Ensure you have sufficient
privileges for this operation retry the operation
ORA-47320:
Rule string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47321:
Rule string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47322:
error creating Rule string, string
Cause: An unexpected error occurred
creating the rule
Action: Please review the definition
for accuracy and retry the operation
ORA-47323:
error deleting Rule string, string
Cause: An unexpected error occurred
deleting the rule
Action: Please review the definition
for accuracy and retry the operation
ORA-47324:
error updating Rule string, string
Cause: An unexpected error occurred
updating the rule
Action: Please review the definition
for accuracy and retry the operation
ORA-47340:
Rule Set string already defined
Cause: The object with this name
exists already
Action: Choose a unique object name
and retry the operation
ORA-47341:
Rule Set string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47342:
error creating Rule Set string, string
Cause: An unexpected error occurred
creating the rule set
Action: Please review the definition
for accuracy and retry the operation
ORA-47343:
error deleting Rule Set string, string
Cause: An unexpected error occurred
deleting the rule set
Action: Please review the definition
for accuracy and retry the operation
ORA-47344:
error updating Rule Set string, string
Cause: An unexpected error occurred
updating the rule set
Action: Please review the definition
for accuracy and retry the operation
ORA-47360:
Rule string already added to Rule Set string
Cause: The object with this name
exists already
Action: Choose a unique object name and
retry the operation
ORA-47361:
Rule string not associated to Rule Set string
Cause: The rule specified is not
associated to the rule set
Action: Please review the definition
for accuracy and retry the operation
ORA-47362:
error adding Rule string to Rule Set string, string
Cause: An unexpected error occurred
adding the rule to the rule set
Action: Please review the definition
for accuracy and retry the operation
ORA-47363:
error deleting Rule string from Rule Set string, string
Cause: An unexpected error occurred
deleting the rule to the rule set
Action: Please review the definition
for accuracy and retry the operation
ORA-47381:
OLS Policy string not found
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47382:
OLS Policy Label string not found for policy string
Cause: The object being requested
does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47383:
error capturing the session state information
Cause: An internal error occurred
capture the session state
Action: Please retry the operation if
possible
ORA-47390:
failed to audit event, string
Cause: An internal error auditing the
operation
Action: Please retry the operation if
possible
ORA-47391:
attempt to set Factor string violates Rule Set string
Cause: An attempt to set the factor
violated the associated rule set
Action: Please check to ensure you
have the ability to set the factor
ORA-47392:
Factor string cannot be set
Cause: The attempt to set the factor
is not allowed
Action: This factor cannot be set so
there is no corrective action
ORA-47393:
Factor string value not allowed
Cause: The value being assigned to
the factor is not allowed
Action: None
ORA-47394:
Factor assignment rule set not defined
Cause: The rule set being associated
to the factor does not exist
Action: Please review the definition
for accuracy and retry the operation
ORA-47395:
error returned by Factor string evaluation expression string
Cause: The factor retrieval method
resulted in an error
Action: Please review the retrieval
method definition for accuracy and correct it as required
ORA-47396:
error returned by Factor string validation expression string
Cause: The factor retrieval method
resulted in an invalid value based on
Action: Please review the factor
definition and correct it as required
ORA-47397:
incorrect identified by value for Factor string
Cause: The factor identified by value
is incorrect
Action: Please review the factor
definition and correct it as required
ORA-47398:
multiple identities defined for Factor string
Cause: The factor has duplicate
identities defined
Action: Please review the factor
definition and correct it as required
ORA-47399:
incorrect labeled by value for Factor string
Cause: The factor labeled by value is
incorrect
Action: Please review the factor
definition and correct it as required
ORA-47400:
Command Rule violation for string on string
Cause: An operation that was
attempted failed due to a command rule violation
Action: Ensure you have sufficient
privileges for this operation retry the operation
ORA-47401:
Realm violation for string on string.string
Cause: An operation that was
attempted failed due to a realm protection
Action: Ensure you have sufficient
privileges for this operation retry the operation
ORA-47402:
incorrect evaluation options value for Factor string
Cause: The factor evaluations options
value is incorrect
Action: Please review the factor
definition and correct it as required
ORA-47403:
NULL returned by Factor string evaluation expression string
Cause: The factor evaluated to a NULL
value
Action: Please review the factor
definition and correct it as required
ORA-47404:
NULL trust level for Factor string
Cause: The factor has a NULL trust
level
Action: Please review the factor
definition and correct it as required
ORA-47405:
negative trust level for Factor string
Cause: The factor has a negative
trust level
Action: Please review the factor
definition and correct it as required
ORA-47406:
ALWAYS AUDIT option set for Factor string
Cause: The factor audit option is set
to always audit
Action: No action required
ORA-47407:
ALWAYS AUDIT option set for Rule Set string
Cause: The rule set audit option is
set to always audit
Action: No action required
ORA-47408:
Realm violation for the EXECUTE command
Cause: A realm violation has occurred
for a realm-protected stored procedure.
Action: In order to invoke the
realm-protected procedure, you must have GRANT privileges to execute the
procedure, or you must be authorized to operate in the procedure's realm.
ORA-47409:
Command Rule violation for the EXECUTE command
Cause: A command rule violation
occurred when trying to perform the EXECUTE command for a stored procedure
protected by a command rule.
Action: Ask the Database Vault
administrator to perform the operation or remove the command rule for the
protected stored procedure.
ORA-47901:
OLS policy not specified
Cause: An OLS policy name is required
for this operation
Action: Specify a policy name and
retry the operation
ORA-47902:
OLS policy label not specified
Cause: An OLS policy label is
required for this operation
Action: Specify a policy label and
retry the operation
ORA-47903:
OLS policy label string not found for policy string
Cause: The policy label being
requested does not exist
Action: Choose an object name that
exists and retry the operation
ORA-47904:
OLS session label does not exist
Cause: The policy label specified
does not exist
Action: Choose a valid policy label
and retry the operation
ORA-47905:
OLS policy label string is not allowed for policy string
Cause: The policy label specified is
not valid for this policy
Action: Choose a valid policy label
for this policy and retry the operation
ORA-47906:
OLS policy label not specified for identity string.string under
policy string
Cause: The policy label is required
for this operation
Action: Choose a valid policy label
for this policy and retry the operation
ORA-47920:
Authorization failed for user string to perform this operation
Cause: The operation attempted is not
allowed for this user
Action: Please ensure you have
privileges to perform this operation
ORA-47921:
error adding host string to domain string, string
Cause: An error occurred adding the
host specified to the domain specified
Action: Please review the host and
domain definition and correct it as required
ORA-47922:
error removing host string to domain string, string
Cause: An error occurred removing the
host specified to the domain specified
Action: Please review the host and
domain definition and correct it as required
ORA-47950:
no value defined for required parameter string
Cause: The operation requires a value
for this parameter
Action: Please specify the missing
parameter and retry the operation
ORA-47951:
invalid input value or length for parameter 'string'
Cause: The value specified for this
parameter is invalid or too large
Action: Please specify the a valid
parameter and retry the operation
ORA-47985:
password same as or similar to user
Cause: The password specified similar
to the user account name and therefore insecure
Action: Please specify the more
complex password and retry the operation
ORA-47986:
password length must be 8 characters or more
Cause: The password specified is too
short and therefore insecure
Action: Please specify a password with
more characters and retry the operation
ORA-47987:
password is too simple
Cause: The password specified can be
guessed based on dictionary terms and therefore insecure
Action: Please specify a password that
is not based on dictionary terms and retry the operation
ORA-47988:
password should contain at least one numeric and one alphabetic character
Cause: The password does not contain
at least one numeric and one alphabetic character
Action: Please specify a password with
at least one numeric and one alphabetic character and retry the operation
ORA-47989:
password should differ by at least 3 characters
Cause: The password specified does
not differ from the previous one by more than 3 characters
Action: Please specify a password that
differs from the previous one by more than 3 characters and retry the operation
ORA-47999:
internal Database Vault error: string Error: string
Cause: An internal Database Vault
framework error occurred.
Action: Contact Oracle Customer
Support.
ORA-48001:
internal error code, arguments: [string], [string], [string],
[string], [string], [string], [string], [string]
Cause: This is the generic internal
error number for program exceptions. This indicated that a process encountered
an exceptional condition.
Action: Report as a bug - the first
argument is the internal error number.
ORA-48002:
thread terminated by fatal error
Cause: The thread was in an
unrecoverable state.
Action: Examine the thread trace file
for more information.
ORA-48003:
out of process memory when trying to allocate string bytes (string,string)
Cause: Operating system process
private memory was exhausted.
Action: None
ORA-48004:
unable to allocate string bytes of shared memory ("string","string","string","string")
Cause: More shared memory is needed
than was allocated in the shared pool.
Action: Reduce your use of shared
memory or increase the amount of available shared memory.
ORA-48100:
error encountered when attempting to open a file
Cause: There was an error encountered
when attempting to open a file with the ADR file interface.
Action: Check that the specified
directory name, file name, and open options are valid.
ORA-48101:
error encountered when attempting to read a file [string] [string]
[string]
Cause: There was an error encountered
when attempting to read a file with the ADR file interface.
Action: Check the specified arguments
to the read interface.
ORA-48102:
encountered the end-of-file when reading the file
Cause: The ADR file interface
encountered the end-of-file when reading the file.
Action: Handle the end of file
condition.
ORA-48103:
error encountered when attempting to write a file [string] [string]
[string]
Cause: There was an error encountered
when attempting to write a file with the ADR file interface.
Action: Check the specified arguments
to the write interface.
ORA-48104:
read mismatch on blocks requested and returned, [string], [string]
Cause: There was a mismatch between
the number of blocks requested for reading and the number of blocks actually
returned.
Action: Check the file to make sure
there are no partial blocks.
ORA-48105:
write mismatch on blocks requested and returned, [string], [string]
Cause: There was a mismatch between
the number of blocks requested for writing and the number of blocks actually
written.
Action: Check that there is enough
space left on the device to write the requested number of blocks.
ORA-48106:
error initializing the ADR string object
Cause: There was an error encountered
during the initialization of one of the ADR file objects.
Action: Check the validity of the
specified directory name and file name.
ORA-48107:
invalid Bfile input, [string]
Cause: An invalid Bfile was passed
into the routine to convert the bfile into a file handle.
Action: Verify the contents of the
specified Bfile.
ORA-48108:
invalid value given for the diagnostic_dest init.ora parameter
Cause: The value given for the
diagnostic_dest directory is not a valid directory. Either the directory does
not exist or the process does not have read/write privileges on the directory.
Action: Use a value for
diagnostic_dest that is a valid directory with the proper read and write
privileges.
ORA-48109:
invalid lock mode for file descriptor, [string]
Cause: The lock mode associated with
the file descriptor was invalid in the context of the routine.
Action: Verify that a file is not
trying to obtain multiple locks and that the file is holding a lock when
attempting to release the lock.
ORA-48110:
error encountered while attempting to get a file lock [string] [string]
Cause: There was an error encountered
while trying to get a file lock.
Action: Check the state of the file
and operating system.
ORA-48111:
error encountered while attempting to release a file lock [string]
Cause: There was an error encountered
while trying to release a file lock.
Action: Check the state of the file
and operating system.
ORA-48112:
invalid flags for open file, string
Cause: Invalid flags were passed in
to the open file routine.
Action: Check to see if the flags are
a valid combination.
ORA-48113:
unable to write to stream file because of out of space condition
Cause: The system is unable to write
the requested number of bytes to a stream file. This is due to an out of space
condition. The additional information shows how many bytes were not written.
Action: Check that there is enough
space left on the device to write the requested number of bytes.
ORA-48114:
error encountered when attempting to close a file
Cause: There was an error encountered
when attempting to close a file with the ADR file interface.
Action: Check the validity of the file
descriptor.
ORA-48115:
error encountered while seeking a file position
Cause: There was an error encountered
while seeking a position in a file.
Action: Check that the requested file
position falls within the file boundaries.
ORA-48116:
error enountered when attempting to create a directory [string]
Cause: There was an error encountered
when attempting to create a directory.
Action: Check the directory name.
ORA-48117:
error encountered when attempting to remove a directory [string]
Cause: There was an error encountered
when attempting to remove a directory.
Action: Check the directory name.
ORA-48118:
error encountered with list directory [string]
Cause: There was an error with
listing the elements of a directory.
Action: Check the state of the
operating system.
ORA-48119:
error encountered when attempting to remove a file [string] [string]
Cause: There was an error encountered
when attempting to remove a file with the ADR file interface.
Action: Check the directory name and
file name.
ORA-48120:
error encountered when attempting to retrieve the file size [string] [string]
Cause: There was an error encountered
when attempting to retrieve the file size with the ADR file interface.
Action: Check the directory name and file
name.
ORA-48121:
error with opening the ADR stream file [string] [string]
Cause: An error was encountered when
attempting to open an ADR stream file.
Action: Check the rest of the error
stack for details of the actual error that was encountered.
ORA-48122:
error with opening the ADR block file [string] [string]
Cause: An error was encountered when
attempting to open an ADR block file.
Action: Check the rest of the error
stack for details of the actual error that was encountered.
ORA-48123:
error encountered when attempting to flush a file
Cause: There was an error encountered
when attempting to flush a file with the ADR file interface.
Action: Check the state of the file.
ORA-48124:
device full encountered during write to a file
Cause: The device full error was
encountered during the write to a file.
Action: Check the amount of free space
on the device.
ORA-48125:
illegal identifier length, argn:string, len:string, lim:string
Cause: An input identifier was passed
in that has a length that is greater than the max length.
Action: Make sure the input
indentifier has a length that is less than the max length.
ORA-48126:
attempting to create a file that already exists
Cause: The client attempted to create
a file that already exists.
Action: Either remove the file or
check if it is okay if the file already exists.
ORA-48127:
attempting to open a file that does not exist
Cause: An attempt was made to open a
file that does not exist.
Action: Either create the file or
check why the file does not exist.
ORA-48128:
opening of a symbolic link is disallowed
Cause: An error was encountered when
attempting to open a file that is a symbolic link. Users are not allowed to
open symbolic links.
Action: Check the specified file name.
ORA-48129:
invalid input for the full path specification
Cause: Input was incorrectly
specified for the full path specification, or the default extension may have
been incorrectly specified. Or an empty string was passed in for the full path.
Action: Check that the full path
string is non-NULL. If you want to specify a relative path from ADR Home for
the full path specification, then use '' instead of the actual
path to ADR Home. For ADR Base, use ''.
ORA-48130:
invalid lock parameters for get file lock [string]
Cause: Invalid lock parameters passed
in for the get file lock routine. The user must pass in file as the lock type.
Or, there is a lock mode mismatch. Exclusive locks are not allowed in read-only
mode, and shared locks are not allowed in write-only mode.
Action: Check that correct lock type
is specified and that the correct lock mode is requested for the file given its
open flags.
ORA-48131:
error encountered when attempting to tell the file position
Cause: An error was encountered when
attempting to tell the file position using the ADR file interface.
Action: Check the directory and file
name of the file along with the open state.
ORA-48132:
requested file lock is busy, [string] [string]
Cause: The requested file lock is
busy because another process is holding the file lock.
Action: Try to get the file lock again
at a later time.
ORA-48133:
file descriptor has already been opened [string] [string]
Cause: The specified file descriptor
has already been opened.
Action: Do not open a file that has
previously been opened, or check your code to make sure you are cleaning up a
file descriptor that is being reused correctly.
ORA-48134:
invalid file descriptor state for operation, string, string, string
Cause: The state of the file
descriptor was invalid for the requested operation. An example is that a file
was opened for read, but a write operation to the file was requested.
Action: Check the state of the file
descriptor and make sure it matches the operation.
ORA-48135:
uninitialized file descriptor
Cause: The specified file descriptor
is uninitialized.
Action: Make sure the file descriptor
is initialized before passing it into the routine.
ORA-48136:
directory already exists [string]
Cause: Operation failed because the
specified directory already exists.
Action: Remove the directory or ignore
this error.
ORA-48137:
uninitialized file handle
Cause: The specified file handle is
uninitialized.
Action: Make sure the file handle is
initialized before passing it into the routine.
ORA-48138:
invalid directory name input for client address
Cause: An invalid directory name was
specified as part of the address path specification.
Action: Check that the directory name
is non-NULL and that the directory name length does not exceed the maximum
length.
ORA-48139:
invalid input to ADR initialization routine
Cause: There was an invalid input to
the ADR initialization routine.
Action: Check the length of the ADR
base, product ID, and instance ID input arguments.
ORA-48140:
the specified ADR Base directory does not exist [string]
Cause: The specified ADR Base
Directory does not exist.
Action: Check that the specified ADR
Base Directory is a valid path name and that the directory exists.
ORA-48141:
error creating directory during ADR initialization [string]
Cause: Error encountered when
creating a directory during the initialization of the ADR subsystem.
Action: Check the input arguments to
the ADR initialization routine and the state of the operating system.
ORA-48142:
invalid permissions input for change permissions
Cause: Invalid permissions passed
into change permissions routine.
Action: Check the value of the
permissions input.
ORA-48143:
error changing permissions for a file
Cause: Error encountered while
changing the permissions for a file
Action: Check the specified directory and
file and the state of the operating system.
ORA-48144:
error encounted while performing standard file I/O
Cause: Error encountered while
performing standard file I/O
Action: Check the validity of standard
in, out, and error.
ORA-48145:
invalid seek location, [string], [string]
Cause: Invalid seek location
specified for routine.
Action: Check the validity of
specified seek location.
ORA-48146:
missing read, write, or exec permission on directory during ADR initialization
[string] [string]
Cause: Error encountered when
checking if the process has read, write, and exec privileges on directories
needed by the ADR subsystem. This error occurs during the initialization of the
ADR subsystem.
Action: Check the input arguments to
the ADR initialization routine and the state of the operating system. Ensure
that the user has the proper permissions on the ADR directories.
ORA-48147:
invalid home location specification for ADR, [string], [string],
[string]
Cause: Invalid read or write home
location specification for ADR.
Action: An invalid home was specified
for the ADR Read or Write Home location.
ORA-48148:
error encountered when attempting to move a file
Cause: There was an error encountered
when attempting to move a file with the ADR file interface.
Action: Check the directory name and
file name.
ORA-48149:
error encountered when attempting to copy a file
Cause: There was an error encountered
when attempting to copy a file with the ADR file interface.
Action: Check the directory name and
file name.
ORA-48150:
error encountered with set current working directory
Cause: There was an error with
setting the current working directory.
Action: Check the path used, or the
state of the operating system.
ORA-48151:
error getting operating system time for a file
Cause: Error encountered while
getting the operating system time for a file.
Action: Check the specified directory
and file and the state of the operating system.
ORA-48152:
lock table is full
Cause: Lock table is full - too many
locks granted
Action: Try again later
ORA-48153:
error encountered when getting ADR base directory default
Cause: There was an error encountered
when attempting to get the ADR base directory default value.
Action: Check your environment to see
if the $ORACLE_BASE and $ORACLE_HOME environment variables are set.
ORA-48154:
reached end of file for alert log
Cause: The end of file was reached
for reading the Alert Log. There are no more messages to read in the Alert Log.
Action: Do not read from the Alert Log
ORA-48155:
error encountered when read alert log [string]
Cause: There was an error encountered
when attempting to read a message from the Alert Log.
Action: Check the error message and
the contents of the alert message.
ORA-48156:
Alert log purge has occurred - retry operation
Cause: The purge of the alert log has
occurred.
Action: Retry the operation.
ORA-48157:
null input to ADR initialization
Cause: There was an null input to the
ADR initialization routine.
Action: Check the ADR base, product
ID, and instance ID input arguments.
ORA-48158:
invalid input for ADR base directory
Cause: An invalid input was passed in
for the ADR base directory name. The ADR base directory name is either NULL or
too long of a string.
Action: Check the ADR base directory
input argument.
ORA-48159:
invalid input for ADR product type
Cause: An invalid input was passed in
for the ADR product type. The ADR product type is out of bounds.
Action: Check the ADR product type
input argument.
ORA-48160:
invalid input for ADR product id
Cause: An invalid input was passed in
for the ADR product id. The ADR product id is either NULL or too long of a
string.
Action: Check the ADR product id input
argument.
ORA-48161:
invalid input for ADR instance id
Cause: An invalid input was passed in
for the ADR instance id. The ADR instance id is either NULL or too long of a
string.
Action: Check the ADR instance id
input argument.
ORA-48162:
string buffer too small to hold input, [string], [string], [string]
Cause: The string buffer is too small
to copy an input string into.
Action: Check the size of the string
buffer and the input string. Look in the argument for the location in the code
where the error occurs.
ORA-48163:
error concatenating directory onto path, [string], [string], [string]
Cause: Error encountered while concatenating
a directory onto a path name.
Action: Check the error returned by
the OS and the size of the input and output buffers.
ORA-48164:
error concatenating file onto path, [string], [string], [string]
Cause: Error encountered while
concatenating a directory onto a path name.
Action: Check the error returned by
the OS and the size of the input and output buffers.
ORA-48165:
user missing read, write, or exec permission on specified ADR Base directory [string]
Cause: The specified ADR Base
Directory does not have the correct permissions.
Action: Check the read, write, and
exec permissions on the specified ADR Base Directory
ORA-48166:
error with opening ADR block file because file does not exist [string] [string]
Cause: An error was encountered with
opening an ADR block file because the file does not exist.
Action: Check the existence of the ADR
Block File.
ORA-48167:
invalid argument for checking ADR initialization
Cause: Invalid arguments were
specified for the routine to check ADR initialization.
Action: Check the inputs to the ADR
initialization routine.
ORA-48168:
the ADR sub-system is not initialized
Cause: The ADR subsystem has not been
initialized. The requested operation cannot be performed.
Action: Check the usage of the call to
the ADR services. The ADR sub-system must be initialized for the call to work.
ORA-48169:
incorrect arguments to ADR deferred initialization
Cause: There are incorrect arguments
to the ADR deferred initialization.
Action: Check the input arguments. It
could be possible that the product is not set up for deferred initialization.
ORA-48170:
unable to lock file - already in use
Cause: the file is locked by another
process, indicating that it is currently in use by another process
Action: determine which process
legitimately owns this file.
ORA-48171:
unable to get share lock - file not readable
Cause: share lock request was made on
a file not open for read access.
Action: file must be open read-only or
read-write to get a share lock.
ORA-48172:
unable to find a valid ADR base
Cause: Unable to find a valid ADR
base. We tried the ORACLE_BASE, ORACLE_HOME, home, and tmp directories, but
none of the directories exist for read/write access.
Action: Check the validity of the
ORACLE_BASE, ORACLE_HOME, home, and tmp directories.
ORA-48173:
error checking directory existence during ADR initialization [string]
Cause: Error encountered when
checking directory existence during the initialization of the ADR subsystem.
Either the diag or product type directory does not exist underneath the ADR
base.
Action: The directory in the error
message must exist in order for ADR initialization to succeed. Make sure the
directories exist.
ORA-48174:
error encountered with get current working directory
Cause: There was an error with
getting the current working directory.
Action: Check the state of the
operating system or the size of the path buffer.
ORA-48175:
the path name must not contain the string '..'.
Cause: The specified path name
contains '..'.
Action: Correct the path name and
retry the operation.
ORA-48176:
error translating a path name into its full path name
Cause: An error was encountered when
translating a path name into its full path name.
Action: Check the inputted path name
to make sure it is a valid relative path.
ORA-48177:
file name with full path information [string] not allowed
Cause: Input was incorrectly
specified for the file name. The inputted file name is greater than the maximum
length, or the file name has path information. In this case, the file name
should not have any path information. The path information should be specified
in a separate argument.
Action: Check that the string for the
file name is not too long and does not have path information.
ORA-48178:
error encountered while reading an ADR block file during ADR initialization [string]
Cause: An error was encountered while
reading an ADR block file during the initialization of the ADR subsystem.
Action: Check the state of the file
system.
ORA-48179:
OS file synchronization failure
Cause: OS command to synchronize the
changes to a file with the operating system failed.
Action: Check the state of the file
system and the amount of free space left on your device.
ORA-48180:
OS open system call failure
Cause: OS open system call failed.
The system failed to open or create a file in the requested mode.
Action: Check the OS error code
ORA-48181:
OS write system call failure
Cause: OS write system call failed.
The system failed to write to a file.
Action: Check the OS error code
ORA-48182:
OS read system call failure
Cause: OS read system call failed.
The system failed to read to a file.
Action: Check the OS error code
ORA-48183:
OS close system call failure
Cause: OS close system call failed.
The system failed to close a file.
Action: Check the OS error code
ORA-48184:
OS seek system call failure
Cause: OS seek system call failed.
The system failed to seek to a position in a file.
Action: Check the OS error code
ORA-48185:
OS file size system call failure
Cause: OS file size call failed. The
system failed to retrieve the file size for a file.
Action: Check the OS error code
ORA-48186:
OS check file exists system call failure
Cause: OS check file exists system
call failed. The system failed to perform the check file exists command for a
file.
Action: Check the OS error code
ORA-48187:
specified directory does not exist
Cause: The specified directory does
not exist.
Action: Check the directory name.
ORA-48188:
user missing read, write, or exec permission on specified directory
Cause: The user does not have valid
permissions on the specified directory. The user is missing either the read,
write, or execute permission.
Action: Check the permissions of the
specified directory.
ORA-48189:
OS command to create directory failed
Cause: The OS command to create a
directory failed.
Action: Check the error number
associated with the create directory failure.
ORA-48190:
OS unlink system call failure
Cause: OS unlink system call failed.
The system failed to perform unlink on the specified file.
Action: Check the OS error code
ORA-48191:
user missing read or write permission on specified file
Cause: The user does not have valid
permissions on the specified file. The user is missing either the read or write
permission.
Action: Check the permissions of the
specified file.
ORA-48192:
OS command to move a file failed
Cause: The OS command to move a file
failed.
Action: Check the error number
associated with the move file.
ORA-48193:
OS command to open a directory failed
Cause: The OS command to open a
directory failed.
Action: Check the OS error associated
with the open directory failure.
ORA-48194:
OS command to close a directory failed
Cause: The OS command to close a
directory failed.
Action: Check the OS error associated
with the close directory failure.
ORA-48195:
OS command to remove a directory failed
Cause: The OS command to remove a
directory failed.
Action: Check the OS error associated
with the remove directory failure.
ORA-48196:
OS command to release advisory lock failed
Cause: The OS command to release the
advisory lock failed
Action: Check the OS error associated
with the release advisory lock failure.
ORA-48197:
OS command to get the file status failed
Cause: The OS command to get the file
status failed. This could be because the file is not open or file descriptor is
invalid.
Action: Check the OS error associated
with the get file status failure.
ORA-48198:
OS command to change the file permissions failed
Cause: The OS command to change the
file permissions failed.
Action: Check the OS error associated
with the failure.
ORA-48199:
OS command to copy a file failed
Cause: The OS command to copy a file
failed.
Action: Check the error number
associated with the copy file.
ORA-48200:
Illegal Input Argument [string]
Cause: An illegal argument was passed
in.
Action: Fix the call.
ORA-48201:
Field Length Exceeds Maximum [string] [string] [string]
Cause: An illegal field length was
used.
Action: Fix the call.
ORA-48202:
Illegal Identifier [string] [string]
Cause: Illegal identifier specified.
Action: Use a valid identifier.
ORA-48203:
Illegal Data Type [string]
Cause: Illegal data type specified.
Action: Use a valid data type.
ORA-48204:
Illegal Identifier Length [string] [string] [string]
Cause: The input identifier is too
long.
Action: Specify a shorter identifier.
ORA-48205:
Record Length too Big [string] [string] [string]
Cause: The sum of the maximum lengths
of all fields exceeds the maximum record length that is supported.
Action: Remove or shorten some of the
fields.
ORA-48206:
Ilegal Number of Fields [string] [string] [string]
Cause: The number of fields specified
exceeds the supported maximum.
Action: Remove some of the fields in
the relation.
ORA-48207:
Illegal Field Name [string]
Cause: The field name is invalid.
Action: Specify a valid field name.
ORA-48208:
Duplicate Fields
Cause: The list of fields specified
contains a duplicate field.
Action: Remove the duplicate field.
ORA-48209:
Relation Already Exists
Cause: The relation already exists.
Action: Remove the relation.
ORA-48210:
Relation Not Found
Cause: The relation was not found.
Action: Either specify a valid
relation name or create one with that name.
ORA-48211:
Illegal Access Mode [string] [string]
Cause: The supplied access mode is
not recognized.
Action: Supply a valid mode.
ORA-48212:
Open Record Access Not Done
Cause: The open record access call
was not performed.
Action: The open record access call is
required before attempting this call.
ORA-48213:
Incorrect Access Mode for Operation [string] [string]
Cause: The relation was opened in a
mode not compatibile with the attempted operation being done.
Action: Reopen the relation in the
correct mode.
ORA-48214:
Sequence Overflow [string] [string] [string]
Cause: The sequence number will
exceed the system maximum.
Action: Reset the sequence number.
ORA-48215:
Sequence Invalid Operation [string] [string]
Cause: The specified sequence
operation is not valid.
Action: Specify a valid operation.
ORA-48216:
Field Len Exceeds Max Field Length [string] [string] [string]
[string]
Cause: The field length specified
exceeds the defined maximum for the field.
Action: Supply a smaller field length.
ORA-48217:
Out of Space on Device
Cause: The storage subsystem is out
of space.
Action: Add more space to the storage
subsystem.
ORA-48218:
Duplicate Key Name [string] [string]
Cause: The key name already exists.
Action: Specify a different key name.
ORA-48219:
Key Name Doesn't Match Any Existing Key
Cause: The key name provided doesn't
match an existing key.
Action: Specify a key name that
exists.
ORA-48220:
Too Many Keys Defined [string] [string]
Cause: A key is trying to be created
that exceeds the maximum number of keys supported.
Action: Drop another key.
ORA-48221:
Key Exceeds Maximum Allowed Length [string] [string] [string]
Cause: The sum of the lengths of the
fields in the key exceeds the maximum length supported.
Action: Remove one or more fields from
the key.
ORA-48222:
Predicates/Order By Not Allowed
Cause: A predicate or order by can
not be added after fetch has started.
Action: Put the predicate or order by
call before the first fetch.
ORA-48223:
Interrupt Requested - Fetch Aborted - Return Code [string]
Cause: User interrupt has occurred.
Action: None
ORA-48224:
DDL has occurred since parse - reparse [string] [string] [string]
Cause: Another session has performed
a DDL (i.e. add field, create key, drop key) that prevents this session from
being to continue.
Action: Call open record access again.
ORA-48225:
No More Space in Order By Buffer
Cause: The order by buffer size is
not sufficient for the number of rows.
Action: Increase the order by buffer
size specified.
ORA-48226:
No Fetch in Progress
Cause: An attempt to perform update
or delete has occurred without a fetch.
Action: You must first perform a
fetch.
ORA-48227:
Invalid Relation File - [string] [string] [string] [string]
Cause: The AMS file is invalid or
corrupt.
Action: Do a repair relation
ORA-48228:
Missing Define Call [string]
Cause: A call to define was not
performed before doing a fetch.
Action: Call the define service before
fetch.
ORA-48229:
Invalid Relation Handle Provided [string] [string]
Cause: An invalid or corrupt relation
handle was used.
Action: Possible memory corruption.
ORA-48230:
Expression arguments must match types
Cause: Incorrect type semantics for
fields in the predicate.
Action: Correct the predicate.
ORA-48231:
Predicate syntax error
Cause: A syntax error exists in the
predicate string.
Action: Correct the predicate.
ORA-48232:
Debug command syntax error [string]
Cause: An invalid debug command has
been specified.
Action: Correct the debug command.
ORA-48233:
Invalid Field Handle [string] [string] [string]
Cause: The field handle is invalid.
Action: Possible memory corruption.
ORA-48238:
Invalid Surrogate Length Specified [string] [string]
Cause: An invalid length during
create field was specified
Action: Specify a correct length
ORA-48239:
Invalid Predicate Handle Provided [string] [string]
Cause: An invalid or corrupt relation
handle was used.
Action: Possible memory corruption.
ORA-48240:
Field is NOT NULL but NULL value supplied
Cause: A field [%s] declared to not
allow nulls contains a null value.
Action: Specify a correct value
ORA-48242:
Fields that are NOT NULL can not use surrogates
Cause: NOT NULL fields can not have
surrogates specified.
Action: Either remove the constraint
or the surrogate.
ORA-48243:
Additional Fields must be declared nulls allowed
Cause: A field can not be added to a
relation that is defined NOT NULL
Action: Do not specify NOT NULL
ORA-48244:
Purge for Retention can't be called while in an Query
Cause: A query is already running -
purge for retention can't be invoked
Action: Fix call sequence
ORA-48245:
Attempt to Update/Delete when at EOF
Cause: The fetch operation is
positioned at EOF - can not update/delete
Action: Do not call update/delete
after fetch has returned EOF
ORA-48246:
Illegal Operation on External Relation
Cause: An illegal call was made using
an external relation
Action: Do not perform the API Call
ORA-48247:
Predicate Conversion Error string
Cause: A time conversion failed
Action: Fix the input
ORA-48248:
Function string type check error; ityp = string typ
= string arg = string
Cause: Invalid inputs to the
specified function
Action: Change the inputs
ORA-48251:
Failed to open relation due to following error
Cause: See error below in the error
stack
Action: See error below in the error
stack
ORA-48252:
Relation does not require migration
Cause: Relation on disk is compatible
with the current code
Action: Don't run the migration
services
ORA-48258:
AMS Corrupt Page Found - Rebuild Relation
Cause: A corrupted page has been
found.
Action: Do a rebuild of the relation
ORA-48259:
AMS Relation not Created Correctly
Cause: Create relation failed
Action: Recreate the relation
ORA-48300:
Incident Record Already Exists
Cause: trying to create an incident
that already exists
Action: retry operation with new
incident ID
ORA-48301:
An Invalid Incident ID was specified
Cause: the specified incident ID was
invalid
Action: retry operation with correct
incident ID
ORA-48302:
Incident Directory does not exist
Cause: the incident directory was not
found
Action: retry operation with a
different incident ID
ORA-48303:
Exceeded max Incident Sequence Value
Cause: the maximum supported incident
sequence value was exceeded
Action: reset incident sequence and
retry operation
ORA-48304:
incident staging file not found
Cause: the incident staging file is
missing
Action: retry with a different
incident ID
ORA-48305:
incident ID range is too large
Cause: the maximum incident sequence
value was exceeded
Action: retry operation with a smaller
range
ORA-48309:
illegal incident state transition, [string] to [string]
Cause: the incident cannot be moved
to the new state
Action: retry operation with a valid
incident status
ORA-48310:
Incident string staging file not found
Cause: the incident staging file does
not exist
Action: retry operation with a valid
incident ID
ORA-48311:
Invalid field name [string]
Cause: the specified field name is
invalid
Action: retry operation with a valid
field name
ORA-48312:
Sweep incident string staging file failed
Cause: the sweep action of incident
staging file failed
Action: check the incident ID and
retry
ORA-48313:
Updates not allowed on ADR relation [string] of Version=string
Cause: Update operations not supportd
on this version of ADR relation
Action: check ADR version and retry
ORA-48314:
Invalid ADR Control parameter [string]
Cause: the specified control
parameter is invalid
Action: check parameter and reissue
command
ORA-48315:
ADR unavailable
Cause: the ADR directory is not
available
Action: enable ADR and retry operation
ORA-48316:
relation [string] unavailable or cannot be created
Cause: the ADR relation is not
available
Action: check ADR directory and retry
operation
ORA-48317:
ADR Relation [string] of version=string is obsolete
Cause: the version of ADR relation is
too old and not supported
Action: check the ADR version and
retry
ORA-48318:
ADR Relation [string] of version=string cannot be supported
Cause: the version of ADR relation is
too new and cannot be supported
Action: need to use a newer release to
access the ADR
ORA-48319:
Update operation on ADR relation [string] not allowed
Cause: updates to foreign ADR
relation cannot be supported
Action: verify ADR location and
reissue command
ORA-48320:
Too many incidents to report
Cause: the result set of incidents is
too large to handle
Action: use a predicate to reduce the
number of incidents and retry
ORA-48321:
ADR Relation [string] not found
Cause: the required ADR relation is
missing, ADR may be corrupted
Action: check ADR directory and retry
ORA-48322:
Relation [string] of ADR V[string] incompatible with V[string]
tool
Cause: the tool version is
incompatible with the ADR version
Action: use another version of tool
and retry
ORA-48323:
Specified pathname [string] must be inside current ADR home
Cause: file outside of ADR home not
allowed as incident file
Action: check the file name and retry
ORA-48324:
Incompatible staging file encountered
Cause: sweep incident failed because
staging file is incompatible
Action: check the incident ID and
version of ADR and retry
ORA-48400:
ADRCI initialization failed
Cause: The ADR Base directory does
not exist
Action: Either create an ADR Base
directory or point to an existing one
ORA-48401:
SET command requires arguments
Cause: No arguments are input for the
SET command
Action: Input the arguments
ORA-48402:
Variable is not defined
Cause: No substitution value is
input.
Action: Input the substitution value
following after the variable name.
ORA-48403:
DEFINE or UNDEFINE command has no arguments
Cause: DEFINE and UNDEFINE command
need users to input the substitution variable name.
Action: Input the vairable name follow
after the DEFINE or UNDEFINE
ORA-48404:
RUN or @ command has no arguments
Cause: RUN and @ commands need users
to input script filename
Action: Input script filename after
RUN and @ commands
ORA-48405:
The option in the command is invalid
Cause: The option is not allowed in
the command
Action: Check the command syntax
ORA-48406:
ECHO or TERMOUT status must be set to ON or OFF
Cause: the status of ECHO ann TERMOUT
commands must be ON or OFF
Action: input ON or OFF
ORA-48407:
DESCRIBE and QUERY commands need at least relation name argument
Cause: This is no relation name is
input as argument
Action: Need users to input at least
the relation name
ORA-48408:
The incident number exceeds the maximum number [string]
Cause: The input incident number
exceeds the maximum number
Action: Input less incidents
ORA-48409:
The ADR homes exceeds the maximum number [string]
Cause: The input ADR homes number
exceeds the maximum number
Action: Input less ADR home string
ORA-48410:
The trace path exceeds the maximum number [string]
Cause: The input trace path exceeds
the maximum number
Action: Input less trace path
ORA-48411:
The trace files exceeds the maximum number [string]
Cause: The input trace file path
number exceeds the maximum number
Action: Input less trace file path
ORA-48412:
The parameters exceeds the maximum number [string]
Cause: The input paramter number
exceeds the maximum number
Action: Input less parameter number or
increase the upper bound
ORA-48413:
The number of orderby fields exceeds maximum number [string]
Cause: The orderby field number
exceeds the maximum number
Action: Input less fields
ORA-48414:
The string in the execution option exceeds maximum length [string]
Cause: The string length is too long
Action: Divid the commands into two
sets or use adrci scripts.
ORA-48415:
Syntax error found in string [string] at column [string]
Cause: Parsing error found in the
user input string
Action: Validate the input string
ORA-48419:
Illegal arguments
Cause: The input argument is illegal
Action: Check the input arguments and
make sure it is not null
ORA-48421:
Predicate string in the command must be single or double quoted
Cause: The predicate string is not
single or double quoted
Action: Put single or double quotes
around the predicate string
ORA-48423:
IMPORT command must have a filename
Cause: File name is missing from the
command
Action: Input the import file name
after the IMPORT keyword
ORA-48424:
SHOW TRACE command needs argument
Cause: SHOW TRACE command needs
arguments
Action: Input arguments
ORA-48426:
The initialization filename is too long
Cause: The initialization filename
length exceeds the maximum length
Action: This is really an internal
setting parameter of the ADRCI, report it as a bug. Alternatively move the
initialization file to the current working directory
ORA-48428:
Input command string exceeds max length [string]
Cause: The current command string is
too long and exceeds the limit
Action: Input less characters
ORA-48429:
Variable name [string] is an invalid identifier
Cause: The substitution variable name
is not a valid identifier
Action: Input the valid identifier
defined by ADRCI
ORA-48431:
Must specify at least one ADR home path
Cause: The command syntax requires at
least one ADR home path to be input
Action: Check the command syntax and
input the home path
ORA-48432:
The ADR home path [string] is not valid
Cause: The adr home user inputs is
not valid, which may due to the path does not exist.
Action: Check if the input home path
exists
ORA-48433:
Unknown help topic
Cause: The input topic is unknown
Action: Check if the topic is vaild
ORA-48434:
No DDE commands are input
Cause: No DDE commands are input
Action: Input a DDE command
ORA-48435:
Input a trace file
Cause: Show trace expects a trace
file
Action: Input a trace file
ORA-48436:
File [string] does not exist
Cause: the file does not exist
Action: Validate the trace file name
ORA-48437:
No IPS commands are input
Cause: No IPS commands are input
Action: Input a IPS command
ORA-48438:
[string] is not a valid number
Cause: The input number is not valid
Action: Check the input number
ORA-48439:
The input path name exceeds the maximum length [string]
Cause: The input path name is too
long
Action: Report as a bug to change the
limit
ORA-48440:
Variable [string] is already defined
Cause: The variable name is defined
previously
Action: Use another variable name
ORA-48441:
The function parameter number exceeds the maximum number [string]
Cause: The function parameter number
exceeds the maximum number
Action: Report it as bug to change the
maximum number
ORA-48442:
The control parameter number exceeds the maximum number [string]
Cause: The control parameter number
exceeds the maximum number
Action: Report it as bug to change the
maximum number
ORA-48443:
Trace Record type appears in the middle of the path
Cause: The trace record cannot be in
the middle of the path
Action: Validate the input
ORA-48444:
The single "." and "*" cannot appear in the middle of the
path
Cause: The single "." and
"*" appears in the middle of the path
Action: Validate the input
ORA-48445:
Path expression only supports one bucket dump type
Cause: The path expression only
supports one bucket dump"
Action: Change the path expresison
syntax
ORA-48446:
The command needs path input
Cause: No path is input as a
parameter
Action: Input the path
ORA-48447:
The input path [string] does not contain any ADR homes
Cause: The input path does not
contain ADR homes
Action: Validate the path
ORA-48448:
This command does not support multiple ADR homes
Cause: There are multiple homes in
the current adr setting.
Action: Use command SET HOMEPATH to set
a single home
ORA-48449:
Tail alert can only apply to single ADR home
Cause: There are multiple homes in
the current setting
Action: Use command SET HOMEPATH to
set a single home
ORA-48457:
ADRCI core dumped
Cause: It is adrci internal error.
Action: Report to Oracle
ORA-48458:
"show incident" failed due to the following errors
Cause: There could be a bug or users
do not have the access permission
Action: Report to Oracle if the errors
are not due to ADR permission settings
ORA-48459:
"describe" command only supports one ADR home path
Cause: Multiple ADR home paths in the
command
Action: put one ADR home path
ORA-48460:
The home path [string] is not valid
Cause: The input home path is not
valid home path
Action: Verify the homepath
ORA-48461:
"describe" failed due to the following errors
Cause: Underlying code failed
Action: If it is not due to permission
issue, report to Oracle
ORA-48462:
Fatal error encountered in [string]
Cause: Fatal error encountered
Action: Report to Oracle
ORA-48463:
The value buffer reached the maximum length [string]
Cause: The value buffer is full
Action: Report to Oracle
ORA-48464:
The predicate buffer reached the maximum length [string]
Cause: The predicate buffer is too
small
Action: Report to Oracle
ORA-48465:
The specified type [string] is undefined
Cause: The purge type specified is
undefined
Action: Check the type name
ORA-48466:
Internal failure, the report context is not initialized
Cause: Internal problem failure.
Action: Report to Oracle
ORA-48467:
"string" for the keyword "string" is not a
valid number
Cause: The keyword value is not a
valid number
Action: Check the value
ORA-48468:
"string" is not a valid keyword
Cause: The keyword is not defined for
the command
Action: Check the available keywords
ORA-48469:
Keyword "string" cannot be duplicated
Cause: The command can only allow one
key with the name
Action: Remove one keyword name from
the command
ORA-48470:
Unknown "string" command
Cause: The command is not valild
Action: Use help manual to check the
command syntax
ORA-48472:
Invalid product name
Cause: The product name provided does
not exist
Action: Specify a product name, see
HELP SHOW BASE
ORA-48473:
Internal failure, unknown return code [string]
Cause: Internal program failure
Action: Report to Oracle
ORA-48474:
Syntax error specifying product, must not be NULL
Cause: The product clause is being
used, but no product name is provided
Action: Supply the product name
ORA-48475:
[string] is not a valid timestamp
Cause: The input timstamp string is
not in valid format
Action: None
ORA-48476:
Cannot write the results out to a file, please check if the environment
variable TMPDIR is set or the current directory is not writable
Cause: The current path may not be
writable
Action: If the current path is writable,
report to Oracle
ORA-48477:
The input path does not contain any valid ADR homes
Cause: The input path does not
contain any valid ADR homes
Action: Check the path if it is valid
ORA-48478:
No alert messages are created
Cause: No alert messages are created
Action: No action
ORA-48479:
No HM runs are created
Cause: There is no hm runs
Action: No action
ORA-48480:
No incidents are created
Cause: There is no incident
Action: No action
ORA-48481:
Report is not available
Cause: The requested report does not
exist"
Action: Check the report ID
ORA-48482:
Report is not generated
Cause: The requested report is not
ready to be generated
Action: Check the report ID
ORA-48483:
Spooling failed, it may be because the spool file cannot be created due to a
permission issue
Cause: The spooling filename may not
be valid or the file cannot be created
Action: Check the permissions of the
target directory and verify the filename
ORA-48484:
Run script failed, it may be because the script file does not exist
Cause: The script file may not exist
Action: Check if the script file exist
ORA-48485:
The file exceeds the maximum length [string]
Cause: The filename is too long
Action: Report to Oracle
ORA-48486:
The file [string] exceeds the maximum length [string]
Cause: The filename is too long
Action: Report to Oracle
ORA-48487:
The internal predicate string exceeds the maximum length [string]
Cause: The predicate string exceeds
the maximum length
Action: Report to Oracle
ORA-48488:
The predicate string exceeds the maximum length [string]
Cause: The input predicate string
exceeds the maximum length
Action: Report to Oracle
ORA-48489:
The input exceeds the maximum length [string]
Cause: The input exceeds the maximum
length
Action: Report to Oracle
ORA-48490:
The field number exceeds the maximum number [string]
Cause: The input field number exceeds
the maximum number
Action: Input less field names
ORA-48491:
The program name is too long, exceeds the maximum length [string]
Cause: the program name length
exceeds the maximum length setting
Action: Report to Oracle
ORA-48492:
The report component name is not defined
Cause: the report component name does
not exist
Action: Check the component name to
ensure it is registered
ORA-48493:
Sweep command needs parameters
Cause: sweep command needs parameter
Action: Check the syntax of the
command
ORA-48494:
ADR home is not set, the corresponding operation cannot be done
Cause: The adr home is not set in the
current adrci session
Action: Set the adr home using the
adrci command "set base" and "set homepath"
ORA-48495:
Interrupt requested
Cause: User requested to interrupt
the current action
Action: No action is needed
ORA-48496:
"string" is a mandatory keyword for the command
Cause: The keyword is not specified
for the command
Action: Input the keyword
ORA-48497:
"string" is an invalid product type
Cause: The product type is not
registered
Action: Check the product type
ORA-48499:
The value of the keyword "string" exceeds the maximum
length string
Cause: The keyword value is too long
Action: Check the limit and input
again
ORA-48500:
File Write Error [string] [string]
Cause: Number of bytes written
differs from number requested. Possibly due to out of disk space.
Action: Ensure sufficient disk space.
ORA-48501:
File Read Error [string] [string]
Cause: Number of bytes read differs
from number requested. Possibly due due to corrupted file.
Action: Recreate the file.
ORA-48502:
Invalid Command Line - Missing Required Elements
Cause: Missing required command line
arguments.
Action: Review the help message and
supply the required arguments.
ORA-48503:
Invalid Parameter Specified
Cause: Invalid input parameter
supplied.
Action: Review the help message and
correct the invalid input parameter.
ORA-48504:
Relation Parameter Must be Specified
Cause: Relation parameter must be
specified during adrexp.
Action: Supply the relation parameter.
ORA-48505:
File Parameter Must be Specified
Cause: File parameter must be
specified during adrimp.
Action: Supply the file parameter.
ORA-48506:
Existing Relation at different version than export [string] [string]
Cause: Attempting to import into an
existing relation and the schema version of that relation differs from the
schema of the relation that was exported.
Action: Drop the existing relation if
you still wish to import the relation.
ORA-48507:
Predicate Not Allowed during Import
Cause: The predicate option is not
allowed during adrimp.
Action: Remove the predicate
arguement.
ORA-48508:
Export File Version [string] Can Not be Used by Import [string]
Cause: The version of the export file
is not able to be read by this version of adrimp.
Action: Rerun the export using the
current version of adrexp.
ORA-48509:
Error occurred during operation. See the following errors
Cause: An underlying error has occurred.
Action: Review and correct the
underlying error.
ORA-48510:
Can not export an in memory relation
Cause: In memory relations can not be
exported.
Action: Pick a different relation.
ORA-48600:
HM run with name [string] already exists
Cause: The specified run name already
existed.
Action: Specify different run name and
re-run the check
ORA-48615:
Parameter [string] value not specified
Cause: Run was invoked without
specifying the parameter and its value
Action: Specify the needed parameter
and its value
ORA-48800:
"string" for the keyword "string" is not in
the right format of timestamp
Cause: The value format is not right
Action: Check the format ADRCI
supports
ORA-48801:
The option "string" is duplicated
Cause: The option has been specified
more than once
Action: Check the input
ORA-48802:
The options "string" and "string" are mutual
exclusive
Cause: These two options cannot be
specified together
Action: Only specify one of them
ORA-48803:
The keyword "string" is not defined for this command
Cause: The keyword is invalid
Action: Check the valid keywords for
the command
ORA-48804:
The command needs at least one file input
Cause: No files are specified to view
Action: Input the files
ORA-48805:
BEGIN BACKUP issued already - must do an END BACKUP first
Cause: A begin backup was already
issued.
Action: Issue END BACKUP
///////////////////////////////////////////////////////////////////////////
ORA-48900:
Illegal Input Argument [string]
Cause: The input argument is invalid
Action: Check the input parameter
ORA-48906:
Parser context is not valid
Cause: The parser context is not
initlialized
Action: Call the initialization
routine first before using the context
ORA-48907:
The end of file is reached
Cause: The end of file is raeched
Action: Handle the end of file
ORA-48908:
No trace files are found
Cause: This is no file in the
navigator context, either it is done with parsing, or no file is pushed
Action: Check if the file is added to
the context
ORA-48909:
Scan context is not initialized
Cause: The scan context is not
initialized
Action: call the initliazation routine
of the scan context
ORA-48912:
The specified trace filename is too long
Cause: The resulting trace filename
length exceeds the maximum length
Action: Use a smaller trace filename
suffix or move ADR higher in the directory hierarchy
ORA-48913:
Writing into trace file failed, file size limit [string] reached
Cause: An attempt was made to write
into a trace file that exceeds the trace's file size limit
Action: increase the trace's file size
limit.
ORA-48914:
File position is not in right format
Cause: The file positon format is not
right
Action: Check if the file format
string is the right one
ORA-48928:
The predicate exceeds the max limit string
Cause: The predicate is too long,
exceeds the max limit
Action: Use a shorter predicate
ORA-48929:
The trace record size exceeded the max size that can be read [string]
Cause: A trace record is too large to
be read by the ADR viewer
Action: Report to Oracle
ORA-48930:
Cannot allocate memory for processing traces
Cause: A memory allocation request
failed
Action: Report to Oracle
ORA-48934:
invalid input for the file name identifier
Cause: An invalid input was given for
the file name indentifier. The file name is not allowed to have slashes ('', '/')
and is not allowed to refer to the parent directory using the '..' characters.
Action: Check the file name and
provide a valid input.
ORA-49315:
Invalid incident type specified [string]
Cause: The specified incident type is
not defined in this ADR.
Action: Specify an available incident
type.
ORA-49404:
No such package [string]
Cause: The specified package does not
exist.
Action: Specify an existing package.
ORA-49405:
Cannot change package name [string] [string]
Cause: Attempted to change package name
after package generation.
Action: Use current name, or create a
new package with the desired name.
ORA-49406:
Undefined configuration parameter specified [string]
Cause: The specified configuration
parameter was not found in ADR.
Action: Specify an existing parameter.
Re-populate parameters if necessary.
ORA-49407:
No unpacking history in this home
Cause: No packages were unpacked into
this home.
Action: Verify the current home.
Unpack a package if necessary.
ORA-49408:
Invalid home specified [string]
Cause: An invalid ADR_HOME was
specified.
Action: Verify that the directory
exists, and has the correct structure.
ORA-49409:
Incremental package provided when complete expected
Cause: No packages were unpacked into
this home.
Action: Provide a complete package, or
use FORCE option.
ORA-49410:
Not an IPS package
Cause: The specified file was not an
IPS package.
Action: Verify that the file is a
valid zip file with expected contents.
ORA-49412:
Package ID does not match existing ID [string] [string]
Cause: The package ID in package file
did not match previously unpacked packages.
Action: Use the correct location for
unpacking the package.
ORA-49413:
Package name does not match existing name [string] [string]
Cause: The package name in package
file did not match previously unpacked packages.
Action: Use the correct location for
unpacking the package.
ORA-49414:
Package sequence later than expected [string] [string]
Cause: The package sequence in
package file was later than expected.
Action: Apply packages in correct
order, or use FORCE option.
ORA-49415:
Package sequence earlier than expected [string] [string]
Cause: The package sequence in
package file was earlier than expected.
Action: Apply packages in correct
order, or use FORCE option.
ORA-49416:
Earlier package sequence applied with FORCE option [string] [string]
Cause: An earlier package sequence
was applied using the FORCE option.
Action: Apply a complete sequence
which is later than any already applied, or use FORCE option to apply an
incremental package.
ORA-49417:
Cannot modify already generated package
Cause: Attempted to change package
attributes after package generation.
Action: Create a new package with the
desired name.
ORA-49420:
Package too large [string] [string]
Cause: The package is too large.
Action: Remove some files or incidents
from the package, or try using incremental mode.
ORA-49421:
Maximum number of package files generated [string]
Cause: The command generated the
maximum number of package files.
Action: Remove some files or incidents
from the package, or use incremental mode to generate additional files.
ORA-49423:
File outside ADR not allowed
Cause: The specified file is not
within the ADR directory structure.
Action: Specify a file inside ADR.
ORA-49424:
Directory outside ADR not allowed
Cause: The specified directory is not
within the ADR directory structure.
Action: Specify a directory inside
ADR.
ORA-49425:
File inside ADR not allowed
Cause: The specified file is within
the ADR directory structure.
Action: Specify a file outside ADR.
ORA-49426:
Directory inside ADR not allowed
Cause: The specified directory is
within the ADR directory structure.
Action: Specify a directory outside
ADR.
ORA-49427:
No such file or file not accessible [string]
Cause: The specified file does not
exist or cannot be accessed.
Action: Create the file or verify file
permissions.
ORA-49428:
No such directory or directory not accessible [string]
Cause: The specified directory does
not exist or cannot be accessed.
Action: Create the directory or verify
directory permissions.
ORA-49429:
File already exists and OVERWRITE option not specified [string]
Cause: The client attempted to create
a file that already exists.
Action: Either remove the file or use
the OVERWRITE option.
ORA-49430:
No such problem [string]
Cause: The specified problem does not
exist.
Action: Specify a problem that exists
in this repository.
ORA-49431:
No such incident [string]
Cause: The specified incident does
not exist.
Action: Specify an incident that
exists in this repository.
ORA-49432:
Problem not part of package [string]
Cause: The specified problem is not
included in the package.
Action: Specify a problem that is
included in the package.
ORA-49433:
Incident not part of package [string]
Cause: The specified incident is not
included in the package.
Action: Specify an incident that is
included in the package.
ORA-49434:
Invalid date format
Cause: An invalid format was used to
specify a date
Action: Specify the date in a
supported format.
ORA-49435:
Flood-controlled incident not allowed here [string]
Cause: A flood-controlled incident
cannot be included in a package
Action: Specify an incident that is
not flood-controlled
ORA-49436:
Date conversion error [string]
Cause: An invalid format was used to
specify a date
Action: Specify the date in a
supported format.
ORA-49440:
Warnings while unpacking package, details in file string
Cause: There were some non-fatal
errors when unpacking a package
Action: Review the specified unpacking
log file
ORA-49441:
Warnings while finalizing package, details in file string
Cause: There were some non-fatal
errors when finalizing a package
Action: Review the specified finalize
log file
ORA-49450:
Non-zero return code from archiving utility [string] [string]
Cause: The archiving utility (zip/unzip)
returned a warning or error.
Action: Verify that the file and
directory exist and are readable, and that the file is a valid zip file.
ORA-49451:
Archive file structure error [string] [string]
Cause: The archiving utility
(zip/unzip) returned an error indicating that the archive file structure is
incorrect.
Action: Verify that the file was
transferred correctly and that the file is a valid zip file.
ORA-49452:
Archiving utility out of memory [string] [string]
Cause: The archiving utility (zip/unzip)
returned an error indicating that it was unable to allocate enough memory.
Action: Check for operating system
limitations on process memory usage.
ORA-49453:
Invalid command invoking archiving utility [string] [string]
Cause: The archiving utility (zip/unzip)
was invoked with an invalid command line, or with invalid options.
Action: Verify that there are no
operating system settings affecting the behavior of the archiving utility..
ORA-49454:
Archive is missing or empty [string] [string]
Cause: The specified archive does not
exist, or is empty.
Action: Check if the specified archive
exists.
ORA-49455:
Archive I/O failed [string] [string]
Cause: An attempt to create, write to
or read from an archive failed.
Action: Verify that operating system
I/O operations are working correctly.
ORA-49456:
Operation failed due to insufficient disk space [string] [string]
Cause: An operation on an archive
failed due to insufficient disk space.
Action: Verify that there is
sufficient disk space. Check for operating system quotas or other restrictions.
/////////////////////////////////////////////////////////////////////////
Errors 49500 - 49599 reserved for Incident Meter Errors
/////////////////////////////////////////////////////////////////////////
ORA-49601:
syntax error: found "string": expecting one of: "string"
etc..
Cause: Syntax error discovered when
processing event speciifcation
Action: Enter correct event
specification
ORA-51001:
check [string] not found in HM catalog
Cause: checker name might have been misspelled
Action: retry running check with
proper checker name
ORA-51003:
run parameters not formatted correctly
Cause: Run parameters were given in a
wrong format
Action: Correct the run params text
and try again
ORA-51004:
Check doesn't take any input params
Cause: run params were passed to the
check, which doesn't take any inputs
Action: don't pass any run params and
try again
ORA-51006:
unexpected delimter ';' in the run params text
Cause: run params were not properly
formatted.
Action: correct the run params format
and try again
ORA-51007:
parameter [string] not registered with this check
Cause: Wrong inputs were given to
this check.
Action: correct the run params and try
the check again
ORA-51008:
parameter [string] value is not a proper number
Cause: the given parameter value is a
not a proper number
Action: correct the run params and try
again
ORA-51025:
check name should be non NULL value
Cause: NULL value was passed for
check name
Action: give a proper check name and
retry again
ORA-51035:
invalid timeout value
Cause: User specified an invalid
timeout value
Action: None
ORA-51102:
cannot change priority of a critical failure string
Cause: An attempt was made to change
priority of a failure with CRITICAL priority.
Action: No action is required.
ORA-51103:
cannot change priority of a closed failure string
Cause: An attempt was made to change
priority of a closed failure.
Action: No action is required.
ORA-51105:
cannot change priority of a failure to CRITICAL
Cause: An attempt was made to change
priority of a failure to CRITICAL.
Action: No action is required.
ORA-51106:
check failed to complete due to an error. See error below
Cause: While executing the check, an
unexpected error occured.
Action: Check the errors below and try
rerunning the check.
ORA-51107:
failures are changing too rapidly - retry command
Cause: Failures were added or closed
during a Data Recovery Advisor command.
Action: Retry the command.
ORA-51108:
unable to access diagnostic repository - retry command
Cause: A lock or timeout error
occurred when trying to read failure or repair data from the Automatic
Diagnostic Repository.
Action: Retry the command.
ORA-51109:
repair script file is too large
Cause: Data Recovery Advisor
generated a repair script file that was too large.
Action: Retry the command with fewer
failures selected.
ORA-51110:
buffer size [string] is too small - [string] is needed
Cause: An internal buffer was too
small.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-51111:
failure revalidation timed out
Cause: Data Recovery Manager was
unable to revalidate all failures before timing out.
Action: Increase timeout and retry the
command.
ORA-51190:
Internal error [string], [string] from DBMS_IR
Cause: An unexpected error occurred
while executing a routine in the DBMS_IR package.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-51191:
Too many files opened
Cause: Data Recovery Advisor
attempted to open too many files using the DBMS_IR package.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-51192:
File not open
Cause: Data Recovery Advisor
attempted to read or write from a file that was not open.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-51193:
invalid parameter value
Cause: An invalid parameter value was
supplied in a call to the DBMS_IR package.
Action: Fix the parameter value and
retry the call.
ORA-51303:
illegal check mask value specified
Cause: An illegal check mask value
was specified.
Action: Specify one of the following
legal values: COLUMN_CHECKS, ROW_CHECKS, REFERENTIAL_CHECKS, or ALL.
ORA-51316:
No check meta-data found on specified table string
Cause: No check meta-data was found
for the object
Action: Table may not exist or no
checks currently defined for the table
ORA-53000:
document type "string" is invalid
Cause: An invalid document type was
specified.
Action: See the ORDDCM_DOCUMENT_TYPES
view for a list of valid document types.
ORA-53001:
and tag values are null
Cause: An invalid attribute was found
in the private dictionary document. The values specified by the and
tags were null.
Action: A private attribute definition
must contain either a non-null value or a non-null
value. Correct the values and try the operation again. See
the private dictionary schema (ordcmpv.xsd) listed in the Oracle Multimedia
documentation for more information.
ORA-53002:
document name "string" already inserted
Cause: The specified document name
was found in the repository.
Action: Specify a unique document name
and try again. See the ORDDCM_DOCUMENTS view for a list of document names.
ORA-53003:
document string does not exist
Cause: The specified document name
was not found in the repository.
Action: Correct the value and try
again. See the ORDDCM_DOCUMENTS view for a list of documents in the repository.
ORA-53004:
The value of tag "string" is invalid.
Cause: An invalid value for the
tag was found in the dictionary document.
Action: Correct the value and try
again. The value of the tag must either be a value defined by DICOM
or an Oracle extension. See the data type schema (ordcmdt.xsd) listed in the
Oracle Multimedia documentation for a list of valid tag values.
ORA-53005:
tag references found in document: string
Cause: The delete operation failed
because some tags in the dictionary document were being referenced by the
listed document.
Action: To perform the delete
operation, follow these steps:
1. Export
the listed referencing document.
2. Delete
the listed referencing document.
3. Remove
the referencing tags from the exported document.
4. Insert
the updated document into the repository.
5. Repeat
the delete operation.
ORA-53006:
wild card characters are not allowed in tags
Cause: A tag
containing wild card characters 'x' or 'X' was found in the dictionary
document.
Action: Remove the wild card
characters from tag and try again. See the Oracle Multimedia
documentation for information about the private dictionary schema
(ordcmpv.xsd).
ORA-53007:
The document type STANDARD_DICTIONARY is not loaded.
Cause: The standard dictionary
document was not found.
Action: Load the standard dictionary
document (ordcmsd.xml). This is an installation error. Contact Oracle Support
Services.
ORA-53008:
The tag value is not a registered schema.
Cause: The schema URL specified by
the value of the tag was not a registered Oracle XML DB
schema.
Action: Specify a registered schema
URL value. See the ALL_XML_SCHEMAS view for a list of registered schemas. See
the Oracle XML DB Developers's Guide for information about registering schemas. See the Oracle
Multimedia documentation for information about the mapping document schema
(ordcmmp.xsd).
ORA-53009:
cannot find the tag value in the metadata schema
Cause: The value of the
tag was not found in the metadata schema specified by the
value of the tag.
Action: Correct the value and try
again. You can either specify a valid value for the tag
or clear the value of the tag. See the Oracle Multimedia
documentation for information about the mapping document schema (ordcmmp.xsd).
ORA-53010:
The value of the tag is null.
Cause: A null tag was
found in the dictionary document.
Action: Correct the value and try
again. If the value of the tag is null, then the value of the
tag must be set to true. See the Oracle Multimedia
documentation for information about the standard dictionary schema
(ordcmsd.xsd) and the private dictionary schema (ordcmpv.xsd).
ORA-53011:
cannot find the tag value in the metadata schema
Cause: The value of the
tag was not found in the metadata schema specified by the value of the
tag.
Action: Correct the value and try
again. You can either specify a valid value for the tag or
clear the value of the tag. See the Oracle Multimedia
documentation for information on the mapping document schema (ordcmmp.xsd).
ORA-53012:
cannot find the tag value in the metadata schema
Cause: The value of the
tag was not found in the metadata schema specified by the
value of the tag.
Action: Correct the value and try
again. You can either specify a valid value for the tag
or clear the value of the tag. See the Oracle Multimedia
documentation for information about the mapping document schema (ordcmmp.xsd).
ORA-53013:
cannot find the value: string in the
dictionaries
Cause: The value of the specified
tag was not found in the standard or private
dictionaries.
Action: Correct the tag and/or the
definer name value and try again. The value of the tag
must refer to a tag and definer name specified in the data dictionaries.
ORA-53014:
The runtime preference table is not empty
Cause: The function was unable to
process due to an internal error.
Action: Contact Oracle Support
Services.
ORA-53015:
An internal dictionary attributes table is empty
Cause: This document could not be
processed due to an internal error.
Action: Contact Oracle Support
Services.
ORA-53016:
null input argument: string
Cause: The function was unable to
process due to an internal error
Action: Contact Oracle Support
Services.
ORA-53017:
The installation file string has an incorrect document type
Cause: An incorrect document type was
specified for this file during installation. The function was unable to process
due to an internal error.
Action: Contact Oracle Support
Services.
ORA-53018:
document string contains an unsupported encrypt action
attribute
Cause: The operation failed because
an unsupported encrypt action
Action: Change the value of the action
attribute to none, remove or replace
ORA-53019:
cannot delete installation document: string
Cause: The document could not be
deleted because it was an installation document.
Action: See the ORDDCM_DOCUMENTS view
for a list of the documents in the repository.
ORA-53020:
invalid external reference in the constraint document: string
Cause: The referenced external rule
or macro could not be found in the repository.
Action: Insert the referenced
documents first and try again.
ORA-53021:
cannot insert a rule or macro string that was already inserted
Cause: The rules or macros existed in
the repository.
Action: Insert a new rule or macro.
ORA-53022:
rules or macros in the constraint document string do not exist
Cause: The rules or macros did not
exist in the repository.
Action: Delete or update an existing
rule or macro.
ORA-53023:
cannot delete or update a referenced rule or macro string
Cause: Because the rules or macros
were referenced by other rules or macros, they could not be deleted or updated.
Action: Delete the referencing rules
or macros first and try again.
ORA-53024:
error processing constraint document: string
Cause: An error occurred while
processing the constraint document.
Action: If the error described in the
message can be corrected, do so; otherwise, contact Oracle Support Services.
ORA-53025:
invalid constraint document: string
Cause: The constraint document was
invalid.
Action: Correct the error described in
the message and try again.
ORA-53026:
failed to insert the constraint string to the database
Cause: An error occurred while trying
to insert the constraint document into the database.
Action: Contact Oracle Support
Services.
ORA-53031:
cannot delete dictionary document: string
Cause: The delete operation failed.
Action: The delete operation for
dictionary documents is not supported. Use the updateDocument or use the
insertDocument procedure to make changes to dictionary documents.
ORA-53032:
The default preference document cannot be found.
Cause: The delete operation failed
due to an internal error.
Action: When a user-defined preference
document is deleted, the default values are restored from the Oracle default
preference document. The default preference document is loaded during installation.
If this document cannot be found, it is an unrecoverable error. Contact Oracle
Support Services.
ORA-53033:
The default UID Definition document cannot be found.
Cause: The delete operation failed
due to an internal error.
Action: When a user-defined UID
Definition document is deleted, the default values are restored from the Oracle
default UID Definition document. The default UID Definition document is loaded
during installation. If this document cannot be found, it is an unrecoverable
error. Contact Oracle Support Services.
ORA-53035:
The rows for the mapping document (string) do not exist.
Cause: The delete operation failed
due to an internal error.
Action: Contact Oracle Support
Services.
ORA-53036:
An internal table for the mapping document (string) is empty.
Cause: The function failed due to an
internal error.
Action: Contact Oracle Support
Services.
ORA-53037:
invalid range tag, string must be less than
string
Cause: The operation failed because
an invalid range tag was specified.
Action: Correct the value and try the
operation again.
ORA-53038:
The data type name for the specified tag cannot be found.
Cause: The function failed due to an
internal error.
Action: Contact Oracle Support
Services.
ORA-53039:
user-defined preference document: string already exists
Cause: The insert operation failed
because only one user-defined preference document was allowed.
Action: To change an existing
user-defined preference document, follow these steps:
1. Export
the existing user-defined document.
2. Delete
the existing user-defined document.
3. Make
changes to the exported document.
4. Insert
the updated document. To add a new user-defined preference document, follow
these steps:
1. Delete
the existing user-defined document.
2. Insert
the new document.
ORA-53040:
user-defined UID definition document: string already exists
Cause: The insert operation failed
because only one user-defined UID definition document was allowed.
Action: To change an existing
user-defined UID definition document, follow these steps:
1. Export
the existing user-defined document.
2. Delete
the existing user-defined document.
3. Make
changes to the exported document.
4. Insert
the updated document. To add a new user-defined UID definition document, follow
these steps:
1. Delete
the existing user-defined document.
2. Insert
the new document.
ORA-53041:
The tag value for a replace action attribute is null.
Cause: The operation failed because a
null tag value was found for a replace action attribute in the anonymity
document
Action: Either add a non-null tag
value for each replace action attribute
ORA-53042:
tag string is referenced by document: string
Cause: The insert operation failed
because the specified tag in the dictionary document was being referenced by
the listed document.
Action: To perform the insert
operation, follow these steps
1. Export
the listed document.
2. Delete
the listed document.
3. Remove
the specified tag from the exported document.
4. Insert
the updated document.
5. Repeat
the insert operation.
ORA-53043:
tag string is referenced by unknown document
Cause: The operation failed because a
tag in the specified dictionary document was being referenced by another
document in the repository.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53044:
invalid tag: string
Cause: The operation failed because
the specified tag was invalid.
Action: The tag must match the regular
expression ([0-9a-fA-FxX]{8}). Correct the tag format and try the operation
again. See the dictionary schemas (ordcmsd.xsd, ordcmpv.xsd) listed in the
Oracle Multimedia documentation for more information.
ORA-53045:
invalid tag: string
Cause: The operation failed because
the specified tag was invalid.
Action: The tag must match the regular
expression ([0-9a-fA-F]{8}). Correct the tag format and try the operation
again. See the dictionary schemas (ordcmsd.xsd, ordcmpv.xsd) listed in the
Oracle Multimedia documentation for more information.
ORA-53046:
tag: string collides with existing tag: string in
document: string
Cause: The operation failed because
the specified tag collided with
Action: Tag collisions are not allowed
in the dictionary documents. Correct the specified tag in the document and try
the operation again.
ORA-53047:
internal error: string
Cause: This document could not be
processed due to an internal error.
Action: Contact Oracle Support
Services.
ORA-53048:
definer name DICOM is not allowed in a private dictionary
Cause: The operation failed because
the definer name DICOM was found in the private dictionary.
Action: Correct the definer name and
try the operation again.
ORA-53049:
unsupported tag value: string
Cause: The operation failed because
the value of the specified tag was not supported.
Action: Only simple tags that match
the regular expression [0-9A-F]{8}(\(.*\))? are allowed in the
tag. For example: 00080096(DICOM), 00080096 and so on.
Correct the tag format and try the operation again. See the schemas
ordcmdt.xsd, ordcmmp.xsd, and ordcman.xsd listed in the Oracle Multimedia
documentation for more information.
ORA-53050:
The data model is being edited by another user.
Cause: The operation failed because
the data model was being edited by another user. An exclusive lock could not be
acquired for the lock - ORD_DATA_MODEL_LOCK.
Action: The data model can be edited
by only one administrator at a time.
ORA-53051:
no editDataModel session found
Cause: The operation failed because
there was no editDataModel session.
Action: Call the editDataModel
procedure first and try the operation again.
ORA-53052:
lock release returned error: string
Cause: The operation succeeded, but
an error occurred while releasing the lock - ORD_DATA_MODEL_LOCK.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53053:
lock request error: string
Cause: The operation failed because
an exclusive lock could not be acquired for the lock - ORD_DATA_MODEL_LOCK.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53054:
An editDataModel session already exists.
Cause: The editDataModel procedure
was called more than once in the same session.
Action: Continue the insert or delete
operations, call rollbackDataModel to rollback the data model changes, or call
publishDataModel to publish the data model changes.
ORA-53055:
empty data model table
Cause: The operation failed because
the data model table was empty.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53056:
unrecognized preference parameter name: string
Cause: The operation failed because
the parameter name was invalid.
Action: Correct the value and try the
operation again. See the preference schema (ordcmpf.xsd) listed in the Oracle
Multimedia documentation for more information.
ORA-53057:
invalid preference parameter value: string
Cause: The operation failed because
the parameter value was invalid.
Action: Correct the value and try the
operation again. See the preference schema (ordcmpf.xsd) listed in the Oracle
Multimedia documentation for more information.
ORA-53058:
The value:string is not a simple tag.
Cause: The operation failed because
the value of the specified tag contained wild card
characters 'x' or 'X'.
Action: Only simple tags that match
the regular expression [0-9A-F]{8}(\(.*\))? are allowed in the
tag. For example: 00080096(DICOM), 00080096 and so on.
Correct the tag format and try the operation again. See the schemas
ordcmdt.xsd, ordcmmp.xsd, and ordcman.xsd listed in the Oracle Multimedia documentation
for more information.
ORA-53059:
The value: string has a null definer
name.
Cause: The operation failed because
the value of the specified tag had a null definer name.
Action: Only simple tags that match
the regular expression [0-9A-F]{8}(\(.*\))? are allowed in the
tag. For example: 00080096(DICOM), 00080096 and so on.
Either specify a definer name using the correct format or remove the definer
name and try again. See the schemas ordcmdt.xsd, ordcmmp.xsd, and ordcman.xsd
listed in Oracle Multimedia documentation for more information.
ORA-53060: string is
not a standard attribute tag
Cause: The operation failed because
the specified standard dictionary attribute tag did not have an even group
number.
Action: A standard dictionary
attribute tag represents a two-byte hexadecimal number (group number followed
by element number) and must match the regular expression
[0-9a-fA-FxX]{3}[02468aceACExX]{1}[0-9a-fA-FxX]{4}. Correct the attribute tag
format and try the operation again.
ORA-53061:
document name string contains reserved prefix - ORD
Cause: The operation failed because
the specified document name contained the ORD prefix that is reserved for
Oracle Multimedia documents.
Action: Remove the ORD prefix from the
document name and try the operation again.
ORA-53062:
invalid model name: string
Cause: The operation failed because
the specified model name was invalid.
Action: The model name DEFAULT is the
only value that is supported in this release. Remove the model name or replace
it with the value DEFAULT and try the operation again.
ORA-53100:
The repository data model is in invalid state.
Cause: Error detected while loading
the data model from the repository.
Action: Contact Oracle Support
Services.
ORA-53111:
The repository data model is not loaded.
Cause: The operation failed because
the ord_dicom.setDataModel procedure was not called to load the repository data
model.
Action: Call the
ord_dicom.setDataModel procedure first and try the operation again.
ORA-53112:
unable to load repository: string
Cause: The ord_dicom.setDataModel
procedure failed to load the repository due to the listed error.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53122:
invalid document type : string
Cause: The ord_dicom.setDataModel
procedure failed to load the repository because an invalid document type was
found.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53124:
cannot find VR number for data type: string
Cause: The VR number for the listed
data type could not be found in the lookup table.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53125:
invalid range tag: string
Cause: The ord_dicom.setDataModel
procedure failed to load the repository because an invalid range tag was found
in the dictionary table.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53126:
assertion failure: string
Cause: The operation failed because
an assertion error had occurred.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-53200:
Argument string is null.
Cause: The argument was expecting a
non-null value, but the value of the passed argument was null.
Action: Check your program and ensure
that the caller of the routine does not pass a null argument value.
ORA-53201:
Argument string is null or invalid.
Cause: The argument was expecting a
non-null, valid value, but the value of the passed argument was null or
invalid.
Action: Check your program and ensure
that the caller of the routine does not pass a null or invalid argument value.
ORA-53202:
internal error, argument [string]
Cause: The internal argument was
invalid.
Action: Contact Oracle Support
Services.
ORA-53203:
security violation
Cause: A possible security violation
was detected.
Action: Check the alert log and trace
file for more information.
ORA-53210:
unable to read empty DICOM object
Cause: There was no data in the
specified DICOM object.
Action: See the Oracle Multimedia
documentation for information about loading DICOM object data into the
database.
ORA-53211:
unable to read invalid ORDDicom object
Cause: The value of the source
attribute or the extension attribute of the ORDDicom object was null.
Action: See the Oracle Multimedia
documentation for information about creating a valid ORDDicom object.
ORA-53212:
unable to read invalid ORDImage object: attribute string is
null
Cause: The ORDImage object was
invalid.
Action: See the Oracle Multimedia
documentation for information about creating a valid ORDImage object.
ORA-53213:
cannot access DICOM data with invalid source type
Cause: An invalid source type was
stored in the source attribute of the ORDDicom object.
Action: See the Oracle Multimedia
documentation for information about the supported source types for DICOM data.
ORA-53214:
cannot access DICOM image data with invalid source type
Cause: An invalid source type was
stored in the source attribute of the ORDImage object.
Action: See the Oracle Multimedia
documentation for information about the supported source types for DICOM image
data.
ORA-53215:
cannot access ORDDataSource object with invalid source type
Cause: An invalid source type was
stored in the ORDDataSource object. Or, an error occurred while trying to
retrieve a BFILE while the object status was local.
Action: See the Oracle Multimedia
documentation for information about the supported source types.
ORA-53216:
cannot export the ORDDataSource object with an external source
Cause: The source of the
ORDDataSource object was not local.
Action: Import the data before calling
the export procedure. Or, get the data directly from the external source.
ORA-53217:
The source LOB locator is null.
Cause: The source BLOB locator or
BFILE locator was null.
Action: Correct the statement to pass
an initialized LOB locator.
ORA-53230:
unable to write to an invalid destination ORDDicom object
Cause: The value of the source
attribute or the extension attribute of the destination ORDDicom object was
null.
Action: See the Oracle Multimedia
documentation for information about constructing a valid ORDDicom object.
ORA-53231:
unable to write to a nonlocal destination ORDDicom object
Cause: The source attribute of the
destination ORDDicom object was not local.
Action: See the Oracle Multimedia
documentation for information about constructing a local ORDDicom object.
ORA-53232:
unable to write to an invalid destination ORDImage object
Cause: The value of the source
attribute of the destination ORDImage object was null.
Action: See the Oracle Multimedia
documentation for information about constructing a valid ORDImage object.
ORA-53233:
unable to write to a nonlocal destination ORDImage object
Cause: The source attribute of the
destination ORDImage object was not local.
Action: See the Oracle Multimedia
documentation for information about constructing a local ORDImage object.
ORA-53234:
The destination BLOB locator is null.
Cause: The destination BLOB locator
was null.
Action: Correct the statement to pass
an initialized BLOB locator.
ORA-53250:
Mapping document does not exist.
Cause: The specified mapping document
did not exist.
Action: Check the installed mapping
documents, and correct the statement to pass the name of an installed mapping
document.
ORA-53251:
Anonymity document does not exist.
Cause: The specified anonymity
document did not exist.
Action: Check the installed anonymity
definition documents, and correct the statement to pass the name of an
installed anonymity definition document.
ORA-53252:
Constraint does not exist.
Cause: The specified constraint did
not exist.
Action: Check the installed
constraints, and correct the statement to pass an installed constraint name.
ORA-53253:
The metadata for the new DICOM object is invalid.
Cause: The metadata for the new DICOM
object did not conform to the default metadata schema (ordcmmd.xsd).
Action: Check the metadata argument to
ensure it has the correct namespace and conforms to the default metadata schema
(ordcmmd.xsd). See the Oracle Multimedia documentation for information about
the default metadata schema (ordcmmd.xsd).
ORA-53254:
The SOP INSTANCE UID for the new DICOM object is invalid.
Cause: The SOP INSTANCE UID for the
new DICOM object was invalid.
Action: See the Oracle Multimedia
documentation for information about creating a valid SOP INSTANCE UID.
ORA-53255:
cannot import from a null or invalid source type
Cause: A null or invalid source type
was specified in the import procedure.
Action: See the Oracle Multimedia
documentation for information about the supported source types for the DICOM
object.
ORA-53256:
cannot export to a null or invalid destination data type
Cause: A null or invalid destination
data type was specified in the export procedure.
Action: See the Oracle Multimedia
documentation for information about the supported destination data types for
the DICOM object.
ORA-53257:
Attribute does not exist.
Cause: The specified attribute did
not exist.
Action: Ensure that the attribute name
is valid.
ORA-53258:
Metadata attribute is not available.
Cause: The value of the metadata
attribute of the ORDDicom object was null.
Action: Call the setProperties method
first.
ORA-53259:
cannot extract metadata that conforms to the schema definition
Cause: The extracted metadata did not
conform to its schema definition.
Action: Check the metadata schema
definition, the mapping document and the parameters for the extractMetadata
method to ensure that they are correct. See the Oracle Multimedia documentation
for information about creating repository documents and extracting metadata.
ORA-53400:
Missing DICOM magic number.
Cause: The DICOM object did not
contain the DICOM magic number "dicm" required by part 10 of the
DICOM standard.
Action: Fix the DICOM object or the
DICOM object source, if possible. Otherwise, update the DICOM preference
document to ignore this category of error.
ORA-53402:
Missing DICOM header.
Cause: The DICOM object did not
contain the file preamble.
Action: Fix the DICOM object or the
DICOM object source, if possible. Otherwise, update the DICOM preference
document to ignore this category of error.
ORA-53404:
Missing the mandatory DICOM attribute string.
Cause: One or more mandatory DICOM
attributes were missing from the DICOM object.
Action: Fix the DICOM object or the
DICOM object source, if possible. Otherwise, update the DICOM preference
document to ignore this category of error.
ORA-53406:
The DICOM object contains invalid attribute value string.
Cause: The DICOM object did not
conform to the DICOM standard and contained invalid attribute values.
Action: Fix the DICOM object or the DICOM
object source, if possible. Otherwise, update the DICOM preference document to
ignore this category of error.
ORA-53408:
The DICOM object encoding is wrong string.
Cause: The DICOM object did not
conform to the DICOM standard's binary encoding rules.
Action: Determine if the DICOM object
is corrupt. If the DICOM object is not corrupt, verify whether it conforms to
the binary encoding rules in the DICOM standard. If the DICOM object is
corrupt, fix it if possible. Otherwise, update the DICOM preference document to
ignore this category of error.
ORA-53410:
The attribute string does not conform to the VM rule.
Cause: The DICOM object either
contained an attribute that did not conform to the DICOM value multiplicity
rule or was missing an attribute that was required by the DICOM standard.
Action: Determine if the DICOM object
conforms to the DICOM standard. If it does, verify if the data dictionary
matches the DICOM object or is more recent than the DICOM object. If the data
dictionary is obsolete, update it using the ORD_DICOM_ADMIN repository API, if
possible. Otherwise, update the DICOM preference document to ignore this
category of error.
ORA-53412:
The DICOM object contains an invalid VR value string.
Cause: The DICOM object with explicit
value representation encoding had attribute VR values that did not match their
definitions in the data dictionary.
Action: Determine if the DICOM object
conforms to the DICOM standard. If it does, verify if the data dictionary
matches the DICOM object or is more recent than the DICOM object. If the data
dictionary is obsolete, update it using the ORD_DICOM_ADMIN repository API, if
possible. Otherwise, update the DICOM preference document to ignore this
category of error.
ORA-53414:
The DICOM object contains undefined values string.
Cause: The DICOM object had attribute
values that were expected to be part of the data model.
Action: Determine if the DICOM object
conforms to the DICOM standard. If it does, verify if the data model matches
the DICOM object or is more recent than the DICOM object. If the data model is
obsolete, update it using the ORD_DICOM_ADMIN repository API, if possible.
Otherwise, update the DICOM preference document to ignore this category of
error.
ORA-53430:
The DICOM object contains unsupported values string.
Cause: This type of DICOM object is
not supported by the current release.
Action: Check for software updates,
and contact Oracle Support Services for information about feature enhancements.
ORA-53432:
The DICOM object attribute string has invalid definer name.
Cause: A private attribute definer
for a private attribute contained in this DICOM object had invalid characters.
Action: Determine if the DICOM object
is corrupt. If the DICOM object conforms to the DICOM standard, contact Oracle
Support Services.
ORA-53434:
Not a DICOM object.
Cause: The binary object is not a
DICOM object.
Action: Determine if the DICOM object
is corrupt. If the DICOM object conforms to the DICOM standard, contact Oracle
Support Services.
ORA-53500:
Not a DICOM image.
Cause: The binary object was not a
DICOM image.
Action: Determine if the DICOM object
is an image. Only DICOM images can be processed with image processing
functions.
ORA-53502:
Image processing failure.
Cause: An error occurred when
processing a DICOM image.
Action: Determine if the DICOM image
is corrupt, and if it is supported by the current release.
ORA-53800:
The DICOM object does not contain attribute string.
Cause: The DICOM object did not
contain the attribute that was required for conformance validation.
Action: Determine if the locator path
is properly constructed. All attributes used in the locator path must be
defined in the DICOM standard, and must not be retired. All attributes except
the last attribute in the locator path must be of sequence type. If the locator
path is correct, verify if the DICOM data dictionary is up to date. If the data
dictionary is obsolete, update it using the ORD_DICOM_ADMIN repository API.
ORA-53810:
error logging conformance validation messages
Cause: An error occurred while trying
to log conformance validation messages.
Action: Contact Oracle Support
Services.
ORA-53820:
Invalid locator path.
Cause: A locator path for an
attribute was invalid.
Action: Please verify the locator path
is properly constructed. All attribute used in the locator path must be defined
in the DICOM standard and must not be retired. An attribute that is not the
last one of the locator path must be a sequence type. If the locator path is
correct, please verify the DICOM data dictionary is up-to-date. If the data
dictionary is obsolete, please use the ORD_DICOM_ADMIN API to update the data
dictionary.
ORA-53900:
I/O failure string.
Cause: A device I/O failure occurred
when attempting to read from and write to a DICOM object.
Action: Check the permissions and
privileges that have been granted for I/O operations.
ORA-53910:
SQL error string.
Cause: An error occurred when
attempting to run a SQL command.
Action: If you are using a JDBC
connection string, ensure that the connection string is valid. Check the user
account to see if it is locked. Ensure that the listener and the database
server are running. And ensure that the setDataModel() function has been
invoked before any other DICOM functions are called.
ORA-53920:
XML error string.
Cause: An error occurred when
attempting to read from and write to XML metadata.
Action: Ensure that Oracle XDB and all
related schemas are properly installed.
ORA-53930:
XSLT error string.
Cause: An error occurred while
attempting to process XML metadata.
Action: Ensure that Oracle XDB and all
related schemas are properly installed. And, verify that the mapping and
anonymity documents are valid.
ORA-53940:
make anonymous error string.
Cause: An error occurred while
attempting to make DICOM object anonymous.
Action: Ensure that the anonymity
document content is valid.
ORA-53980:
unimplemented feature: string
Cause: The specified feature is not
implemented.
Action: Contact Oracle Support
Services.
ORA-53990:
internal error string.
Cause: An internal error occurred
while attempting to process a DICOM object.
Action: Contact Oracle Support
Services, and supply them with a script that can be duplicated as well as the
DICOM object that caused this error.
ORA-54000:
Virtual column feature not yet implemented
Cause: Feature has not been
implemented.
Action: Feature is being implemented.
ORA-54001: string:
invalid identifier specified for virtual column expression
Cause: Column expression referenced a
column that does not exist in the table.
Action: Rewrite column expression to
reference only scalar columns in the table.
ORA-54002:
only pure functions can be specified in a virtual column expression
Cause: Column expression contained a
function whose evaluation is non-deterministic.
Action: Rewrite column expression to reference
only pure functions.
ORA-54003:
specified data type is not supported for a virtual column
Cause: Only scalar data types are
supported for virtual columns. LONG, BLOB, REF, and BFILE data types are not
supported for virtual columns.
Action: Specify the expression column
with a supported scalar data type.
ORA-54004:
resultant data type of virtual column is not supported
Cause: The data type of the
underlying expression is not supported. Only scalar data types are supported
for virtual columns. LONG, BLOB, REF, and BFILE data types are not supported
for virtual columns.
Action: Specify the expression of
virtual column to return a supported scalar data type.
ORA-54005:
keyword VIRTUAL cannot be specified here
Cause: The keyword VIRTUAL was either
repeated or incorrectly specified.
Action: Remove the keyword from the
specified syntax.
ORA-54006:
keyword VISIBLE cannot be specified here
Cause: The keyword VISIBLE was either
repeated or incorrectly specified.
Action: Remove the keyword from the
specified syntax.
ORA-54007:
keyword HIDDEN cannot be specified here
Cause: The keyword HIDDEN was either
repeated or incorrectly specified.
Action: Remove the keyword from the
specified syntax.
ORA-54008:
expression column is not supported for an index organized table
Cause: Attempt to create/alter an
index organized table with an expression column
Action: These columns are not
supported, change the DDL.
ORA-54009:
expression column is not supported for an external table
Cause: Attempt to create/alter an
external table with an expression column
Action: These columns are not
supported, change the DDL.
ORA-54010:
expression column is not supported for a temporary table
Cause: Attempt to create/alter a
temporary table with an expression column
Action: These columns are not
supported, change the DDL.
ORA-54011:
expression column is not supported for a clustered table
Cause: Attempt to create/alter a
clustered table with an expression column
Action: These columns are not
supported, change the DDL.
ORA-54012:
virtual column is referenced in a column expression
Cause: This virtual column was
referenced in an expression of another virtual column
Action: Ensure the column expression
definition for any virtual column does not refer to any virtual column
ORA-54013:
INSERT operation disallowed on virtual columns
Cause: Attempted to insert values
into a virtual column
Action: Re-issue the statment without
providing values for a virtual column
ORA-54014:
Resulting table from a CTAS operation contains virtual column(s)
Cause: Table being created by a CTAS
operation contains a virtual column definition
Action: Remove the virtual column
definition from the table being created
ORA-54015:
Duplicate column expression was specified
Cause: Expression of the virtual
column being added/created conflicts with an existing/previously specified
functional index expression or virtual column expression
Action: Change the expression of the
virtual column os there are no duplicate expressions
ORA-54016:
Invalid column expression was specified
Cause: Virtual column expression is
not a valid arithmetic expression. it probably refers to another column in the
table
Action: Change the expression of the
virtual column
ORA-54017:
UPDATE operation disallowed on virtual columns
Cause: Attempted to update values of
a virtual column
Action: Re-issue the statment without
setting values for the virtual column
ORA-54018:
A virtual column exists for this expression
Cause: Specified index expression
matches an existing virtual column"
Action: Re-issue the statment by
replacing the index expression with the matching virtual column
ORA-54019:
Virtual column expression cannot be changed because it is a partitioning column
Cause: Attempted to modify the
expression of a virtual column that was also a partitioning column.
Action: This is not supported.
ORA-54020:
Virtual column expression cannot be changed because it is a subpartitioning
column
Cause: Attempted to modify the
expression of a virtual column that was also a subpartitioning column.
Action: This is not supported.
ORA-54021:
Cannot use PL/SQL expressions in partitioning or subpartitioning columns
Cause: Attempted to partition a table
on a virtual column that contained PL/SQL expressions.
Action: This is not supported.
ORA-54022:
Virtual column expression cannot be changed because an index is defined on
column
Cause: Attempted to change the
expression of a virtual column that was indexed.
Action: Alter index unsable. Change
expression and then rebuild index.
ORA-54023:
Virtual column expression cannot be changed because a constraint is defined on
column
Cause: Attempted to change the
expression of a virtual column that had a constraint defined on it.
Action: Drop constraint and then
change expression.
ORA-54024:
expression column is not supported for an organization cube table
Cause: Attempted to create or alter
an organization cube table with an expression column
Action: These columns are not
supported, change the DDL.
ORA-54025:
Virtual column cannot have a default value
Cause: Attempted to alter a virtual
column to have a default value.
Action: This is not valid, change the
DDL.
ORA-54026:
Real column cannot have an expression
Cause: Attempted to alter a real
column to have an expression.
Action: This is not valid, change the
DDL.
ORA-54027:
cannot modify data-type of virtual column
Cause: Attempted to change the
data-type of virtual column without modifying the underlying expression
Action: change the underlying
expression to be compatible with the data-type change
ORA-54028:
cannot change the HIDDEN/VISIBLE property of a virtual column
Cause: Attempted to change the
HIDDEN/VIRTUAL property of a virtual column
Action: re-issue the DDL without the
virtual column property change
ORA-54029:
Virtual column cannot be updated in trigger body
Cause: Attempted to change the value
of virtual column in a trigger body"
Action: This is not valid, change the
trigger definition.
ORA-54030:
datatype mismatch between virtual column and expression
Cause: virtual column expression was
changed after column was created"
Action: change the underlying
expression to return datatype that conforms to the virtual column
ORA-54031:
column to be dropped is used in a virtual column expression
Cause: Attempted to drop a column
that was used in a virtual column expression.
Action: Drop the virtual column first
or change the virtual column expression to eliminate dependency on the column
to be dropped.
ORA-54032:
column to be renamed is used in a virtual column expression
Cause: Attempted to rename a column
that was used in a virtual column expression.
Action: Drop the virtual column first
or change the virtual column expression to eliminate dependency on the column
to be renamed.
ORA-54033:
column to be modified is used in a virtual column expression
Cause: Attempted to modify the data
type of a column that was used in a virtual column expression.
Action: Drop the virtual column first
or change the virtual column expression to eliminate dependency on the column
to be modified.
ORA-54034:
virtual columns not allowed in functional index expressions
Cause: An attempt was made to create
a functional index with an expression defined on one or more virtual columns.
Action: Specify the index expression
using only regular columns.
ORA-54035:
keyword HIDDEN cannot be specified here
Cause: Attempted to specify HIDDEN
key word for a virtual column
Action: This is not supported.
ORA-54036:
cannot define referential constraint with ON DELETE SET NULL clause on virtual
column
Cause: Attempted to specify ON DELETE
SET NULL clause for a referential integrity constraint on a virtual column.
Action: Reissue the statement without
specifying ON DELETE SET NULL clause.
ORA-54037:
table must have at least 1 column that is not virtual
Cause: An attempt was made to create
a table with only virtual columns.
Action: Include at least 1 column that
is not virtual in the table being created.
ORA-54500:
invalid combination of elements
Cause: The geometry did not start
from the correct level in the hierarchy.
Action: Correct the hierarchy in the
geometry.
ORA-54501:
no holes expected
Cause: The geometry contained one or
more unexpected holes.
Action: Remove any holes in the
geometry.
ORA-54502:
solid not closed
Cause: The solid geometry was not
closed i.e., faces of solid are not 2-manifold due to incorrectly defined,
oriented, or traversed line segment because each edge of a solid must be
traversed exactly twice, once in one direction and once in the reverse
direction.
Action: Correct the orientation of the
edges of the neighboring polygons.
ORA-54503:
incorrect solid orientation
Cause: The orientation of the solid
was not correct.
Action: Correct the orientation or
specification of the outer or inner solid geometry according to the geometry
rules for such a solid.
ORA-54504:
multiple outer geometries
Cause: The geometry contained more
than one outer geometry.
Action: Remove all but one of the
outer geometries.
ORA-54505:
ring does not lie on a plane
Cause: The ring was not flat.
Action: Make sure all of the vertices
of the ring are on the same plane.
ORA-54506:
compound curve not supported for 3-D geometries
Cause: The 3-D geometry contained one
or more compound curves, which are not supported for 3-D geometries.
Action: Remove all compound curves
from the geometry.
Cause: The multipoint geometry had
two points that either had identical coordinates or were the same point
considering the geometry tolerance.
Action: Make sure all points are
different, considering the tolerance.
ORA-54508:
overlapping surfaces in a multisolid geometry
Cause: The multisolid geometry
contained one or more fully or partially overlapping surfaces.
Action: Ensure that the multisolid
geometry contains no overlapping areas.
ORA-54509:
solid not attached to composite solid
Cause: To connect solids in a
composite solid geometry, at least one of the faces of a solid must be shared
(fully or partially) with only another solid. However, at least one of the faces
in this composite solid was not shared by exactly two solids only.
Action: Ensure that at least one face
in a composite solid is shared by exactly two solids.
ORA-54510:
no outer geometry expected
Cause: An outer geometry was found
when only inner geometries were expected.
Action: Remove all outer geometries.
ORA-54511:
edges of inner and outer solids intersect
Cause: An inner solid had a common
edge with outer solid.
Action: Ensure that edges of inner and
outer solids do not intersect.
ORA-54512:
a vertex of an inner solid is outside corresponding outer solid
Cause: A solid geometry contained an
inner solid with at least one vertex outside its corresponding outer solid.
Action: Ensure that all vertices of
inner solids are not outside their corresponding outer solid.
ORA-54513:
inner solid surface overlaps outer solid surface
Cause: One or more faces of an inner
solid surface either fully or partially overlapped an outer solid surface.
Action: Ensure that inner and outer
surfaces have no shared (fully or partially overlapping) faces.
ORA-54514:
overlapping areas in multipolygon
Cause: A multipolygon geometry
contained one or more common (shared, fully or partially overlapped) polygons.
Action: Ensure that no polygons in a
multipolygon overlap.
ORA-54515:
outer rings in a composite surface intersect
Cause: Outer rings, either on the
same plane or different planes, in a composite surface intersected.
Action: Ensure that outer rings do not
intersect. They can share edges.
ORA-54516:
adjacent outer rings of composite surface cannot be on same plane
Cause: The conditional flag was set,
and a composite surface had at least two outer rings sharing a common edge on
the same plane.
Action: Change those outer rings into
one larger outer ring.
ORA-54517:
outer ring is on the same plane and overlaps another outer ring
Cause: An outer ring in a composite
surface shared a common area with another outer ring.
Action: Ensure that no outer rings
fully or partially overlap.
ORA-54518:
shared edge of composite surface not oriented correctly
Cause: A shared edge (one shared by
two polygons) in a composite surface was not correctly oriented. Each shared
edge must be oriented in one direction with respect to its first polygon and
then in the reverse direction with respect to its second polygon.
Action: Reverse one of the directions
of the shared edge with respect to its polygons.
ORA-54519:
polygon (surface) not attached to composite surface
Cause: Not all polygons of a surface
had a common (fully or partially shared) edge.
Action: Ensure that each polygon is
attached to the composite surface by one of its edges.
ORA-54520:
inner ring not on the same plane as its outer ring
Cause: An inner ring was not on the
same plane as its outer ring.
Action: Ensure that each inner ring is
on the same plane as its outer ring.
ORA-54521:
inner ring is not inside or is touching outer ring more than once
Cause: An inner ring either was not
inside its outer ring or touched its outer ring more than once.
Action: Ensure that the inner ring is
inside its outer ring and does not touch the outer ring more than once. If an
inner ring touches its outer ring more than once, then the outer ring is no
longer a topologically simple or singly connected polygon (ring).
ORA-54522:
inner rings of same outer ring cannot intersect or share boundary
Cause: Two inner rings of the same
outer ring intersected or shared a boundary.
Action: Ensure that line segments of
an inner ring do not intersect or fully or partially coincide with line
segments of another inner ring sharing the same outer ring.
ORA-54523:
inner rings of same outer ring cannot touch more than once
Cause: Two inner rings of the same
outer ring touched more than once.
Action: Ensure that inner rings of the
same outer ring touch at no more than one point.
ORA-54524:
inner ring cannot be inside another inner ring of same outer ring
Cause: An inner ring was inside
another ring of the same outer ring.
Action: Ensure that no inner ring is
inside another inner ring of the same outer ring.
ORA-54525:
incorrect box volume due to wrong ordinates
Cause: The rectangular box in
shortcut format did not have its first x,y,z coordinates either all greater or
less than its second x,y,z coordinates.
Action: Make sure that the first x,y,z
coordinates are either all greater or all less than the second x,y,z
coordinates.
ORA-54526:
multi or composite geometry must be decomposed before extraction
Cause: The extraction could not be
performed because the multi or composite geometry must first be decomposed into
simple geometries (with or without inner geometries). The multi or composite
geometry had a gtype of GTYPE_MULTISOLID, GTYPE_MULTISURFACE, GTYPE_MULTICURVE,
GTYPE_MULTIPOINT, or GTYPE_COLLECTION, or the geometry was a line string.
Action: Use the MULTICOMP_TOSIMPLE
parameter to element extractor to decompose the multi or composite geometry to
a simple geometry.
ORA-54527:
operation not permitted on a simple geometry
Cause: A MULTICOMP_TOSIMPLE parameter
to element extractor was attempted on a geometry that is already simple.
Action: Do not use the
MULTICOMP_TOSIMPLE parameter to element extractor on simple geometries.
ORA-54528:
inner composite surfaces or surfaces with inner ring(s) expected
Cause: An INNER_OUTER parameter to
element extractor was attempted on a surface that was not simple or composite.
Action: Ensure that the etype of the
geometry for the INNER_OUTER parameter to element extractor is ETYPE_SURFACE or
ETYPE_COMPOSITESURFACE.
ORA-54529:
geometry should have multi-level hierarchy (like triangle)
Cause: The geometry did not have the
multi-level hierarchy required for this operation. For example, if the
parameter to element extractor (hierarchy level) is not LOWER_LEVEL, but the
geometry etype is ETYPE_SOLID and gtype is GTYPE_SOLID, an extract operation is
not allowed, because a simple solid can only be decomposed into lower level
geometries, such as composite surfaces.
Action: Ensure that the geometry has
the appropriate hierarchy. For example, if the geometry etype is ETYPE_SOLID
and gtype is GTYPE_SOLID, the parameter to element extractor (hierarchy level)
should be LOWER_LEVEL.
ORA-54530:
invalid etype for element at element offset
Cause: An invalid etype was
encountered.
Action: Correct the etype of the
geometry.
ORA-54531:
invalid orientation for element at element offset
Cause: The orientation of the current
geometry was not valid.
Action: Reverse the orientation of the
geometry.
ORA-54532:
incomplete composite surface
Cause: The end of composite surface
was reached before all necessary surfaces were defined.
Action: Add more surfaces to match the
geometry definition, or reduce the specified number of surfaces.
ORA-54533:
invalid etype in composite surface of solid
Cause: The etype of the composite
surface of a solid was not valid.
Action: Ensure that the etype is
orient*1000+ETYPE_SOLID, where orient is 1 for outer solid and 2 for inner
solid.
ORA-54534:
incorrect box surface due to wrong specification
Cause: The elemInfo definition was
not correct for the surface of the axis aligned box.
Action: Change the interpretation to 3
in the elemInfo definition.
ORA-54535:
incorrect box surface because it is on arbitrary plane
Cause: The axis aligned box surface
was not on the yz, xz, or xy plane.
Action: Ensure that the first and
fourth coordinates, or the second and fifth coordinates, or the third and sixth
coordinates are the same. This means that the surface is on the yz, xz or xy
plane, respectively.
ORA-54536:
axis aligned box surface not defined properly
Cause: The inner geometry etype did
not start with 2, or the outer geometry etype did not start with 1, or both
occurred.
Action: Use the correct etype for the
inner and outer geometries.
ORA-54537:
incorrect box surface due to wrong orientation
Cause: The rectangular surface in
shortcut format did not have its first x,y,z coordinates all greater than or
equal to or all less than or equal to its second x,y,z coordinates.
Action: Ensure that the first x,y,z
coordinates are either all greater than or equal to or all less than or equal
to the second x,y,z coordinates.
ORA-54538:
unexpected gtype
Cause: The gtype of the geometry was
not GTYPE_SOLID, GTYPE_SURFACE, GTYPE_CURVE or GTYPE_POINT.
Action: Correct the elemInfo array to
fix any invalid gtype and etypes that violate the geometry hierarchy.
ORA-54539:
cannot process the geometry(s) for this operation
Cause: The geometry had errors in it.
Action: Validate the geometry or
geometries to ensure that each is valid.
ORA-54540:
at least one element must be a surface or solid
Cause: One of the geometries had
holes, and the geometries were neither (A) simple, composite, or multisurfaces,
or (B) simple, composite, or multisolids. (Surfaces and solids are the only
geometries that can have holes. Points and curves cannot have holes.)
Action: Ensure that each geometry
having holes is a surface or solid (simple, composite, or multi).
ORA-54545:
holes incorrectly defined
Cause: The holes were defined with
incorrect etype.
Action: Ensure that the etype is
correct in the definition of the inner geometry.
ORA-54546:
volume of solid cannot be 0 or less
Cause: The solid geometry having one
outer and multiple inner geometries had a negative or zero volume.
Action: Correct the orientation or
specification of the outer solid geometry to obey outer geometry rules so that
the outer geometry has a positive volume. Additionally, correct the orientation
or specification of inner solid geometries to obey inner geometry rules so that
each inner geometry has a negative volume.
ORA-54547:
wrong input for COUNT_SHARED_EDGES
Cause: The COUNT_SHARED_EDGES
parameter value was not 1 or 2.
Action: Ensure that the
COUNT_SHARED_EDGES parameter value is either 1 or 2.
ORA-54548:
input geometry gtype must be GTYPE_POLYGON for extrusion
Cause: The input geometry gtype was
not GTYPE_POLYGON.
Action: Ensure that the gtype of the
input polygon is GTYPE_POLYGON.
ORA-54549:
input geometry has incorrect elemInfo
Cause: The input 2-D polygon did not
have only one outer ring.
Action: Ensure that the input 2-D
polygon has only one outer ring.
ORA-54550:
input 2-D polygon not valid
Cause: The 2-D polygon violated the
rules for polygons and rings.
Action: Correct the polygon
definition.
ORA-54551:
grdHeight and/or Height array sizes incorrect
Cause: The sizes of grdHeight and
Height arrays were not equal to half the size of input 2-D polygon's ordinates
array. As a result, each point in the 2-D polygon could not be extruded from
the grdHeight entry to the Height entry.
Action: Ensure that the sizes of the
grdHeight and Height arrays are half that of input 2-D polygon ordinates array.
ORA-54552:
height entries must be >= to ground height entries
Cause: In the definition of a solid,
the height values were less than the ground height.
Action: Ensure that that height values
are greater than or equal to ground height values.
ORA-54553:
incorrect geometry for appending
Cause: The geometry could not be
appended to a homogeneous collection (for example, multi-geometry) or to a
heterogeneous geometry (for example, collection). In other words, the gtype of
the geometry to be appended was neither GYTPE_COLLECTION or GTYPE_MULTI-X
(where X is point, curve, surface, or solid).
Action: Ensure that the geometries
involved in the append operation have appropriate gtypes.
ORA-54554:
arcs are not supported as defined
Cause: An arc was defined in a
geometry type in which arcs are not supported. Arcs are supported for 2-D
(circle) polygons, 2-D compound polygons, 2-D single arc, and 2-D compound
(composite) curves only.
Action: Remove or simplify the arcs.
ORA-54555:
invalid geometry dimension
Cause: The geometry did not have
three dimensions.
Action: Ensure that geometry has three
dimensions.
ORA-54556:
operation is not supported for 3-D geometry
Cause: A 3-D geometry was passed into
an operation that supports only 2-D geometries.
Action: Check the Spatial
documentation for operations that are supported and not supported on 3-D
geometries.
ORA-54557:
incomplete composite solid
Cause: The end of composite solid was
reached before all necessary solids were defined.
Action: Add more solids to match the
geometry definition, or reduce the specified number of solids.
ORA-54601:
CREATE_PC: invalid parameters for creation of Point Cloud
Cause: An invalid or unknown
parameter was specified in the creation of Point Cloud.
Action: Check for valid set of
parameters.
ORA-54602:
CREATE_PC: input points table string does not exist
Cause: The specified table for
loading points into a Point Cloud did not exist.
Action: Create the points table with
appropriate columns, and then create the Point Cloud.
ORA-54603:
CREATE_PC: specified total dimensionality cannot exceed 8
Cause: The specified total
dimensionality for the Point Cloud exceeded the maximum limit of 8.
Action: Create the Point Cloud with
fewer dimensions. You can store the rest in the output points table.
ORA-54604:
CREATE_PC: input points table should not be empty
Cause: The input points table had no
data.
Action: Insert data into the input
points table and then create the Point Cloud.
ORA-54605:
CREATE_PC: scratch-tables/views (string) exist and need to be dropped
Cause: Transient tables/views from a
previous CREATE_PC operation were still in existence.
Action: Delete the invalid Point Cloud
from the base table (for cleanup of scratch tables), and initialize and create
the Point Cloud again. Alternately, use SDO_UTIL.DROP_WORK_TABLES with
oidstring as the parameter.
ORA-54607:
CREATE_PC: error fetching data from input points table
Cause: An internal read error
occurred during Point Cloud creation.
Action: Contact Oracle Support
Services with the error number reported.
ORA-54608:
CREATE_PC: error writing Point Cloud LOB
Cause: An internal LOB write error
occurred during Point Cloud creation. The cause might be lack of table space.
Action: Look for information from other
errors in the stack, or contact Oracle Support Services with the error number
reported.
ORA-54609:
CREATE_PC: input extent cannot be null
Cause: The extent of the Point Cloud
was null.
Action: Specify an extent for the
Point Cloud that is not null.
ORA-54610:
CREATE_PC: input extent cannot be more than 2-D for geodetic data
Cause: The extent of the Point Cloud
was more than 2-D for geodetic data.
Action: Change the extent to 2-D
(longitude, latitude).
ORA-54611:
INIT: either invalid basetable/schema or they do not exist
Cause: The base table or schema, or
both, were invalid strings; or the base table and schema combination did not
exist.
Action: Ensure that the specified base
table exists in the specified schema before performing the initialization operation.
ORA-54613:
INIT: internal error creating DML trigger
Cause: The necessary privileges to
create the trigger were not granted.
Action: Grant the necessary privileges
to create the trigger. If necessary, contact Oracle Support Services for help
with privileges for trigger creation.
ORA-54614:
INIT: block table name has to be unique
Cause: The specified block table name
was not unique. For example, it might have been used for another block table.
Action: Specify a different block
table name.
ORA-54616:
INIT: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services.
ORA-54617:
CLIP_PC: invalid Point Cloud; extent is empty
Cause: The input Point Cloud for the
CLIP_PC operation was invalid.
Action: Specify a point cloud that was
created using the CREATE_PC procedure.
ORA-54618:
CLIP_PC: SRIDs of query and Point Cloud are incompatible
Cause: The Point Cloud and the query
geometry had incompatible SRID values.
Action: Change the query SRID to be
compatible with that of the Point Cloud.
ORA-54619:
CLIP_PC: query and BLKID parameters cannot both be null
Cause: Both the query and BLKID
parameters were null in the call to the CLIP_PC operation.
Action: Either specify a query
geometry that is not null, or specify a BLKID for use as a query.
ORA-54620:
CLIP_PC: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services.
ORA-54621:
TO_GEOMETRY: TOTAL_DIMENSIONALITY not same as in INIT operation
Cause: The specified
TOTAL_DIMENSIONALITY was invalid.
Action: Ensure that the
TOTAL_DIMENSIONALITY matches that specified in the call to the initialization
operation.
ORA-54622:
TO_GEOMETRY: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services.
ORA-54623:
CREATE_PC: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services.
ORA-54640:
PARTITION_TABLE utility: invalid input parameters [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services.
ORA-54641:
PARTITION_TABLE utility: scratch tables exist with oidstr = string
Cause: Scratch tables/views could not
be created because they already existed.
Action: Use SDO_UTIL.DROP_WORK_TABLES
with the specified oidstr parameter to clean up the scratch tables.
ORA-54642:
PARTITION_TABLE utility: invalid SORT_DIMENSION specified
Cause: An invalid string was
specified for the SORT_DIMENSION.
Action: Specify the SORT_DIMENSION as
'BEST_DIM', 'DIMENSION_1', 'DIMENSION_2', or 'DIMENSION_3'.
ORA-54643:
PARTITION_TABLE utility: invalid WORKTABLESPACE parameter
Cause: An invalid string was
specified for the WORKTABLESPACE parameter.
Action: Specify an existing valid
tablespace for WORKTABLESPACE (to hold the scratch tables).
ORA-54644:
PARTITION_TABLE utility: error in reading input, output tables
Cause: The names for the input/output
tables were invalid, or the tables did not exist or did not have the right
structure.
Action: Check the Spatial documentation
for PARTITION_TABLE.
ORA-54651:
CREATE_TIN: invalid parameters specified in creation of TIN
Cause: An invalid or unknown
parameter was specified in the creation of the TIN.
Action: Check the Spatial
documentation for CREATE_TIN.
ORA-54652:
CREATE_TIN: input points table string does not exist
Cause: The specified table for
loading points into a TIN did not exist.
Action: Create the points table with
appropriate columns, and then create the TIN.
ORA-54653:
CREATE_TIN: specified total dimensionality cannot exceed 8
Cause: The specified total
dimensionality for the TIN exceeded the maximum limit of 8.
Action: Create the TIN with fewer
dimensions. You can store the rest in the output points table.
ORA-54654:
CREATE_TIN: input points table should not be empty
Cause: The input points table had no
data.
Action: Insert data into the input
points table, and then create the TIN.
ORA-54655:
CREATE_TIN: scratch tables/views(string) exist and need to be dropped
Cause: Transient tables from previous
CREATE_TIN operation still existed.
Action: Delete the invalid TIN from
the base table (for cleanup of scratch tables), and initialize and create the
TIN again. Alternately, use SDO_UTIL.DROP_WORK_TABLES with oidstring as its
parameter.
ORA-54656:
CREATE_TIN: error fetching data from input points table
Cause: An internal read error
occurred during TIN creation.
Action: Contact Oracle Support
Services with the error number reported.
ORA-54657:
CREATE_TIN: error writing TIN LOB
Cause: An internal LOB write error
occurred during TIN creation. The cause might be lack of table space.
Action: Look for information from
other errors in the stack, or contact Oracle Support Services with the error
number reported.
ORA-54658:
CREATE_TIN: input extent cannot be null
Cause: The extent of the TIN was
null.
Action: Specify an extent for the TIN
that is not null.
ORA-54659:
CREATE_TIN: input extent has to be 2-D for geodetic data
Cause: The extent of the TIN was more
than 2-D for geodetic data.
Action: Change the extent to 2-D
(longitude, latitude).
ORA-54660:
CLIP_TIN: invalid Point Cloud; extent is empty
Cause: The input TIN for the CLIP_TIN
operation was invalid.
Action: Specify a TIN that was created
using the CREATE_TIN operation.
ORA-54661:
CLIP_TIN: SRIDs of query and TIN are incompatible
Cause: The TIN and the query geometry
had incompatible SRID values.
Action: Change the query geometry SRID
to be compatible with that of TIN.
ORA-54662:
CLIP_TIN: query and blkid parameters cannot both be null
Cause: Both the query and blkid parameters
were null in the call to the CLIP_TIN operation.
Action: Either specify a query
geometry that is not null, or specify a blkid for use as a query.
ORA-54663:
CLIP_TIN: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services.
ORA-54664:
TO_GEOMETRY: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services.
ORA-54665:
CREATE_TIN: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support
Services. ////////////////////////////////////////////////// 55200 - 55300
Reserved for MGD RFID Exceptions
//////////////////////////////////////////////////
ORA-55200:
Java exception from tag data translation java stack
Cause: Java exceptions.
Action: Turn on java output by calling
dbms_java.set_output(OUTPUT_SIZE); Set java logging level by calling
MGD_ID_UTL.setJavaLoggingLevel('INFO'); Analyze java logging messages.
ORA-55201:
Tag data translation category not found
Cause: No matching category ID could
be found.
Action: Make sure the input category
name, category version or category ID is correct.
ORA-55202:
Tag data translation scheme not found
Cause: No matching scheme could be
found for the input data format.
Action: Make sure the input data
format is supported and correct.
ORA-55203:
Tag data translation level not found
Cause: No matching level could be
found for the input data format.
Action: Make sure the input data
format is supported and correct.
ORA-55204:
Tag data translation option not found
Cause: No matching option could be
found for the input data format.
Action: Make sure the input data
format is supported and correct.
ORA-55205:
Tag data translation field validation failed
Cause: Invalid field value.
Action: Make sure the field value of
the input data is within the range specified in the tag data translation XML.
ORA-55206:
Tag data translation field not found
Cause: Invalid input field.
Action: Make sure the spellings of the
input fields are correct.
ORA-55207:
Tag data translation rule evaluation failure
Cause: Error occurred when idcode
translator tried to evaluate the rule specified in the tag data translation
XML.
Action: Java proxy must be set in
order to evaluate manager look up rules. Call MGD_ID_UTL.setProxy(PROXY_HOST,
PROXY_PORT) to enable java proxy.
ORA-55208:
Too many matching levels were found for the input data
Cause: Necessary field values were
missing.
Action: Add additional field value
pairs that are necessary to determine a unique matching level.
ORA-55300:
model string does not exist
Cause: The specified model could not
be found.
Action: Make sure that the model has
been created.
ORA-55301:
rulebase string does not exist
Cause: The specified rulebase could
not be found.
Action: Make sure that the rulebase
has been created.
ORA-55302:
insufficient privileges string
Cause: Sufficient privileges were not
granted.
Action: Ask the database administrator
to grant the appropriate privileges.
ORA-55303:
SDO_RDF_TRIPLE_S constructor failed: string
Cause: SDO_RDF_TRIPLE_S constructor
failed.
Action: Check the stack trace for
additional information.
ORA-55304:
specified reuse-bNode model-id string != target model-id string
Cause: The reuse-bNode model-id
specified for the SDO_RDF_TRIPLE_S constructor was neither 0 nor the model-id
of the target model.
Action: Make sure that the reuse-bNode
model is either 0 or the model-id of the target model.
ORA-55305:
reification constructor functions not supported
Cause: Unsupported reification
constructor functions were used.
Action: Insert each triple in the
reification quad individually. See documentation for more information.
ORA-55306:
internal error: invalid string: value_name=string value_type=string
Cause: The value type of this
component of the RDF triple was invalid.
Action: This is an internal error.
Contact Oracle Support Services.
ORA-55307:
invalid value type for lexical value: string
Cause: The value type of this lexical
value was invalid.
Action: Make sure that the lexical
value format is correct. If this error occurs during bulk load from a staging
table, then this may be an internal error. Contact Oracle Support Services.
ORA-55308:
invalid time zone string for lexical value string
Cause: The time zone of this lexical
value was invalid.
Action: Make sure that the lexical
value format is correct. If this error occurs during bulk load from a staging
table then this may be an internal error. Contact Oracle Support Services.
ORA-55309:
hash collision resolution failed for lexical value string
Cause: Attempts to resolve hash
collision exceeded the maximum retry count.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55310:
parse failed for the string lexical value: string
Cause: Attempts to insert the
specified lexical value failed.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55311:
invalid value type string for long lexical value string
Cause: The value type of this long
(length > 4000) lexical value was invalid.
Action: Make sure that the long value
has a valid value type.
ORA-55312:
parse failed for triple: id-form: string string string
Cause: Attempts to insert triple
failed.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55313:
SDO_RDF_TRIPLE_S constructor failed to process triple containing bNode
Cause: The SDO_RDF_TRIPLE_S
constructor without bNode reuse option was invalid for triple containing bNode.
Action: Use SDO_RDF_TRIPLE_S
constructor that allows bNode reuse.
ORA-55314:
invalid temporary table name (string) for use with batch load
Cause: Specified temporary table name
was not valid.
Action: See documentation for rules
for temporary table name validity.
ORA-55315:
batch load attempt failed: string
Cause: The batch load operation
failed.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55316:
model string does not match model string for
table and column
Cause: This column of the table was
not associated with the specified model.
Action: Make sure to use the correct
target model.
ORA-55317:
model string already exists
Cause: A model with the specified
name was already present.
Action: Choose a different model name,
or delete the existing model and create a new model with the specified name.
ORA-55318:
column string in table string already
contains data
Cause: At model creation time, the
table column contained data.
Action: Ensure that the table column
does not contain data before model creation.
ORA-55319:
model string create attempt failed: string
Cause: The attempt to create the
specified model did not succeed.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55320:
model string drop attempt failed: string
Cause: The attempt to drop the
specified model did not succeed.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55321:
network already exists
Cause: Attempt to create the network
failed because the network already existed.
Action: If necessary, drop the network
before trying to recreate the network.
ORA-55322:
model(s) exist
Cause: An attempt was made to drop a
network that contained one or more models.
Action: Drop all the model(s) and then
retry the operation.
ORA-55323:
rulebase(s) exist
Cause: An attempt was made to drop a
network that contained one or more rulebases.
Action: Drop all the rulebase(s) and
then retry the operation.
ORA-55324:
no rulebases specified
Cause: Rulebases for the operation
were not specified.
Action: Specify at least one rulebase.
ORA-55325:
rulebase or rules index string already exists string
Cause: A rulebase or rules index with
the specified name already existed.
Action: Choose a different name, or
delete the existing rulebase or rules index.
ORA-55326:
rules index (string) create attempt failed: string
Cause: The attempt to create the
specified rules index did not succeed.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55327:
rule string yields a triple with a literal subject or
predicate
Cause: The specified rule created an
invalid triple containing a literal in the subject or predicate position.
Action: Check and modify the rule to
avoid creation of invalid triple.
ORA-55328:
literal value string insert attempt failed
Cause: The attempt to create the
specified literal value failed.
Action: This may be an internal error.
Contact Oracle Support Services.
ORA-55329:
same model string specified more than once in the list of
models
Cause: The specified model occurred
more than once in the list of models.
Action: Eliminate duplicate
occurrences of the model in the list of models.
ORA-55330:
rulebase or rules index string is busy
Cause: The specified rulebase or
rules index was busy and could not be used.
Action: Retry your operation later.
ORA-55331:
user owns RDF objects
Cause: The user could not be dropped
because it owns RDF objects.
Action: Drop the RDF objects and then
retry.
ORA-55370:
input parameter not a zero or positive integer
Cause: The input parameter was not
zero or a positive integer.
Action: Change the input parameter to
zero or a positive integer.
ORA-55371:
RDF rules index 'string' exists for different model-rulebase combination
Cause: A rules index with the
specified name has already been built for a different model-rulebase
combination.
Action: Specify a different rules
index name, or drop the existing rules index and then create a new rules index
with that name.
ORA-55372:
entailment (rules index) 'string' already exists
Cause: The entailed graph (rules
index) already exists.
Action: Specify a different rules
index name, or drop the existing rules index and then create a new rules index
with that name.
ORA-55373:
inference internal error: string
Cause: An unexpected internal error
condition occurred.
Action: Check the error message and
the stack trace.
ORA-55374:
query constants not in the database; no rows selected
Cause: URIs or literals used in the
query did not exist in the database.
Action: Check the query, and ensure
that the URIs or literals do exist.
ORA-55375:
cannot drop table 'string' because this table owns RDF objects
Cause: A table containing RDF data
could not be dropped without first dropping its RDF model.
Action: Drop the corresponding RDF
model or models, and then drop the table.
ORA-55376:
cannot alter or drop column 'string' because this column owns RDF objects
Cause: A table column containing RDF
data could not be altered or dropped without first dropping its RDF model.
Action: Drop the corresponding RDF
model or models, and then alter or drop the column.
ORA-55377:
number of triples less than 1 or null error indication marker
Cause: An internal error occurred
during validation. The number of triples was less than 1 or the error
indication marker was null.
Action: Check the input parameters,
and ensure that the number of triples is 1 or greater and that the error
indication marker is not null; or contact Oracle Support Services.
ORA-55378:
invalid error code
Cause: An invalid error code was
passed in during validation.
Action: Specify a valid error code.
ORA-55379:
too many triples
Cause: An internal error occurred
during validation. Too many triples were passed in.
Action: Specify a valid number of
triples for the operation, or contact Oracle Support Services.
ORA-55430:
query pattern is null
Cause: The query pattern specified in
the SEM_MATCH query was null.
Action: Modify the query pattern to be
non-null.
ORA-55455:
rules index status not recognized ( string )
Cause: The specified rules index
status was not recognized.
Action: Ensure that the rules index
status is VALID, INCOMPLETE, or INVALID, and retry the operation.
ORA-55456:
no valid rules index for this model-rulebase combination
Cause: A valid rules index did not
exist for specified combination of models and rulebases.
Action: Create a rules index for the
specified models and rulebases combination, or use a combination of models and
rulebases for which a rules index exists, and retry the operation. Also ensure
that the rules index status matches the status for the rules index specified in
the query.
ORA-55457:
predicate not found in model
Cause: The predicate value passed in
as an argument to the semantic operator did not exist in the model.
Action: In the query using semantic
operators, use a predicate value that exists in the model and retry the
operation.
ORA-55458:
object not found in model
Cause: The object value passed in as
an argument to the semantic operator did not exist in the model.
Action: In the query using semantic
operators, use an object value that exists in the model and retry the
operation.
ORA-55459:
invalid parameter string
Cause: The parameter string used in
the creation of an index of type SEM_INDEXTYPE had invalid or malformed
parameters.
Action: See the documentation for
information on how to write a valid parameter string.
ORA-55460:
incorrect usage of semantic operators
Cause: There was a syntax error in
the call to the SEM_RELATED operator
Action: See the documentation for
information on how to use the SEM_RELATED operator. Check that the value
returned by SEM_RELATED is compared to 1 or 0.
ORA-55461:
no distance information available
Cause: Distance information was not
generated during rules index creation.
Action: Retry query without the
SEM_DISTANCE operator and/or without specifying bounds in the SEM_RELATED
operator. See the documentation for information on when distance information is
generated.
ORA-55462:
internal error
Cause: An internal error occurred
during a semantic operator query or during the creation of an index of type
SEM_INDEXTYPE.
Action: Contact Oracle Support
Services.
ORA-55501:
Backing out live transaction
Cause: Flashback Transaction Backout
was requested on a transaction that has not committed yet.
Action: Commit the transaction before
using this feature.
ORA-55502:
Specified input transaction by name has no SCN hint
Cause: The specified transaction
names for Flashback Transaction Backout was missing an SCN hint.
Action: Provide an SCN hint, and
guarantee that the named transactions start before the given SCN.
ORA-55503:
Mining finished without seeing specified transactions
Cause: The SCN hit passed was not
good. The SCN hit may have come after the start of any of the input
transactions.
Action: Give a lesser and more
conservative SCN hint, with greater probability of having seen the start of a
transaction.
ORA-55504:
Transaction conflicts in NOCASCADE mode
Cause: Transactions other than the
ones specified conflicts with the specified transactions.
Action: Try using other options like
NONCONFLICT_ONLY or CASCADE or NOCASCADE_FORCE.
ORA-55505:
DDL done on an interesting object after mining start SCN
Cause: The Flashback Transaction
Backout process encountered an interesting object which had its last DDL
operation done on it after the mining start time. An interesting object is one
that has been modified by either the specified transactions or any of their
dependents.
Action: Specify transactions that have
committed after the last DDL done on all the objects they touched.
ORA-55506:
Transaction performed unsupported change
Cause: A transaction in the
dependency DAG performed some
Action: The specified transaction
cannot be backed out.
ORA-55507:
Encountered mining error during Flashback Transaction Backout. function:string
Cause: Mining error.
Action: None
ORA-55508:
Invalid input to Flashback Transaction Backout
Cause: Null varrays passed or invalid
input specified
Action: Specify properly formed
varrays and valid options
ORA-55509:
Creation of dependencies could not finish
Cause: One or more input transaction
or any of its dependents are not committed or have been aborted after more than
1 minute of calling the backout function.
Action: Commit all the active
transactions associated with this table and try again.
ORA-55510:
Mining could not start
Cause: Mining could not start for the
following reasons.
1. A
logminer session was processing
2. The database
was not mounted or not opened for read and write
3. Minimum
supplemental logging was not enabled
4.
Archiving was not enabled
Action: Fix the mentioned problems and
try again. Note that if you enable supplemental logging now, you will not be
able to remove a transaction that has committed without supplemental logging.
ORA-55511:
Flashback Transaction experienced error in executing undo SQL
Cause: There was a constraint
violation exception when executing in NOCASCADE_FORCE mode. Users could also get
this error if appropriate supplemental logging is not enabled causing
constraint dependencies to go unnoticed.
Action: Either use CASCADE or
NONCONFLICT_ONLY options or add appropriate level for supplemental logging.
ORA-55512:
Backing out PDML or XA-RAC transaction
Cause: One of the transactions in the
dependency graph was a PDML transaction or a local transaction which is a
branch of a global XA transaction, spanning multiple RAC instances. Currently
flashback transaction does not support this type of transaction.
Action: None
ORA-55513:
Backing out an AQ transaction
Cause: One of the transactions in the
dependency graph touched an AQ table. As AQ externalizes database information,
these transactions are not backed out, as the entire effects of the transaction
cannot be seen from inside the database.
Action: None
ORA-55514:
Backing out a DDL transaction
Cause: One of the transactions in the
dependency graph is a DDL transaction and could not be backed out.
Action: None
ORA-55515:
Mining sees input transaction changes without seeing transaction start
Cause: The start SCN provided was
higher than the transaction start but below the transaction commit. The result
was only partial changes for the given transaction.
Action: Please provide a lower scn
hint to flashback transaction.
ORA-55518:
Mining across reset logs
Cause: Flashback Transaction Backout
cannot work with missing changes. This error is thrown if we walk across a
reset-logs branch, where we might have missed changes.
Action: If the user knows that the
transaction happened in the current reset logs branch, then the SCN-hint is
possibly incorrect. Provide an SCN in the current reset log branch.
ORA-55519:
Supplemental logging not available for mining SCN range
Cause: Flashback Transaction cannot work
if there are regions in the mining range where supplemental logging is not
enabled.
Action: If you have provided a
SCN/time hint which is approximate and far beyond the specified transaction
start time, then readjust the SCN hint and try again. If the system has figured
out the transaction start time or you are sure of the range, then the specified
transaction cannot be backed out.
ORA-55520:
Log record in compatibility lower than 11.0
Cause: The logical change record
shows that the compatibility of the mined redo is lower than version 11.0.
Flashback transaction works only on redo versions 11.0 and above.
Action: Advance the compatibility and
try to back out transactions that have occurred after the compatibility
increase.
ORA-55557:
Trigger 4144 corruption
Cause: Above events used for testing
corruption path
Action: None
ORA-55558: string is
not a corrupted transaction
Cause: the given transaction is not
in the corrupt list v$corrupt_xid_list
Action: check v$corrupt_xid_list
ORA-55563: number is
not a valid undo segment number
Cause: the given usn is not a valid
one
Action: check undo$
ORA-55564: string is
not a valid transaction id
Cause: the given txn is not a valid
one
Action: check txn id
ORA-55565: string is
not a valid undo segment number
Cause: the given usn is not a valid
one
Action: check undo$
ORA-55566:
SQL statement issued when the database was not open for queries
Cause: Tried to access SMON time zone
information when database was not open for queries.
Action: Reissue the SQL statement
after the database is open for queries.
ORA-55600:
The table "string"."string" is already
enabled for Flashback Archive
Cause: The specified table is already
enabled for Flashback Archive.
Action: No action required.
ORA-55601:
The table "string"."string" cannot be enabled
for Flashback Archive
Cause: An attempt is made to enable
Flashback Archive for a table which should never be enabled for Flashback
Archive.
Action: Check the table name.
ORA-55602:
The table "string"."string" is not enabled
for Flashback Archive
Cause: An attempt was made to disable
Flashback Archive on a table on which Flashback Archive is not enabled.
Action: Check the table name.
ORA-55603:
Invalid Flashback Archive command
Cause: An invalid Flashback Archive
command was specified.
Action: Check the SQL statement.
ORA-55604:
Incorrect tablespace is specified
Cause: An incorrect tablespace is
specified for the Flashback Archive.
Action: Check the SQL statement and
verify the possible causes, 1, the tablespace that was already used by the
Flashback Archive. 2, the tablespace was not used by the Flashback Archive. 3,
the tablespace block size is less than 8K.
ORA-55605:
Incorrect Flashback Archive is specified
Cause: An attempt was made to operate
on a Flashback Archive that does not exist, or to create a Flashback Archive
that already exists.
Action: Check the SQL statement.
ORA-55606:
Event to modify archiver sleep time in seconds
Cause: 30 seconds is recommended as
the archiver sleep time for tests.
Action: The default archiver sleep
time is 300 seconds
ORA-55607:
Event to enable debugging of archiver
Cause: The purpose of this event is
for debugging.
Action: Attach to process specified.
ORA-55608:
Default Flashback Archive does not exist
Cause: The default Flashback Archive
did not exist.
Action: Create the default Flashback
Archive first.
ORA-55609:
Attempt to create duplicate default Flashback Archive
Cause: An attempt was made to create
a default Flashback Archive while one already exists.
Action: No action required.
ORA-55610:
Invalid DDL statement on history-tracked table
Cause: An attempt was made to perform
certain DDL statement that is disallowed on tables that are enabled for
Flashback Archive.
Action: No action required.
ORA-55611:
No privilege to manage default Flashback Archive
Cause: An attempt was made to create,
alter, or drop the default Flashback Archive.
Action: No action required.
ORA-55612:
No privilege to manage Flashback Archive
Cause: An attempt was made to create,
alter, or drop a Flashback Archive.
Action: No action required.
ORA-55613:
Invalid Flashback Archive quota size
Cause: An attempt was made to specify
invalid Flashback Archive quota size.
Action: Specify size in MB, GB, TB, or
PB.
ORA-55614:
AUM needed for transactions on tracked tables
Cause: An attempt was made to execute
DML on a tracked table without enabling Auto Undo Management.
Action: Disable tracking on the table
or enable Auto Undo Management.
ORA-55615:
Event to test archiver scheduled internal tasks
Cause: The purpose of this event is
for testing.
Action: No action required.
ORA-55616:
Transaction table needs Flashback Archiver processing
Cause: Too many transaction table
slots were being taken by transactions on tracked tables.
Action: Wait for some amount of time
before doing tracked transactions.
ORA-55617:
Flashback Archive "string" runs out of space and tracking on
"string" is suspended
Cause: Flashback archive tablespace
quota is running out.
Action: Add tablespace or increase
tablespace quota for the flashback archive.
ORA-55618:
Insufficient privilege to grant Flashback Archive privilege
Cause: An attempt was made to grant
Flashback Archive privilege.
Action: No action required.
ORA-55619:
Invalid privilege to grant on Flashback Archive
Cause: An attempt was made to grant
invalid privilege on a Flashback Archive object.
Action: Specify valid privilege.
ORA-55620:
No privilege to use Flashback Archive
Cause: An attempt was made to enable
Flashback Archive on a table without such privileges.
Action: No action required.
ORA-55621:
User quota on tablespace "string" is not enough for Flashback
Archive
Cause: An attempt was made to create
or alter a Flashback Archive quota which is larger than the user's quota.
Action: No action required.
ORA-55622:
DML, ALTER and CREATE UNIQUE INDEX operations are not allowed on table "string"."string"
Cause: An attempt was made to write
to or alter or create unique index on a Flashback Archive internal table.
Action: No action required. Only
Oracle is allowed to perform such operations on Flashback Archive internal
tables.
ORA-55623:
Flashback Archive "string" is blocking and tracking on all
tables is suspended
Cause: Flashback archive tablespace
has run out of space.
Action: Add tablespace or increase
tablespace quota for the flashback archive.
ORA-55624:
The table "string"."string" cannot be enabled
for Flashback Archive at this point
Cause: An attempt was made to enable
Flashback Archive again on a table which was just disabled.
Action: Try again later.
ORA-55625:
Cannot grant Flashback Archive privilege to a role
Cause: An attempt was made to grant
or revoke Flashback Archive privilege to a role.
Action: No action required.
ORA-55626:
Cannot remove the Flashback Archive's primary tablespace
Cause: An attempt was made to remove
the primary tablespace of the Flashback Archive.
Action: No action required.
ORA-55627:
Flashback Archive tablespace must be ASSM tablespace
Cause: An attempt was made to add a
tablespace that was not an ASSM tablespace.
Action: Add tablespace that is created
with segment space management auto.
ORA-55628:
Flashback Archive supports Oracle 11g or higher
Cause: An attempt was made to created
a Flashback Archive with incorrect compatible mode or without auto undo
management.
Action: Use compatible mode equal to
11.0 or higher, and use auto undo management.
ORA-55629:
Event to test Flashback Archiver internal management tasks
Cause: The purpose of this event is
for testing.
Action: No action required.
ORA-55630:
Flashback Data Archive cannot be enabled on this object
Cause: An attempt was made to enable
Flashback Data Archive on an object which is not supported by Flashback Data
Archive.
Action: Do not use Flashback Archive
clause for this object.
ORA-55631:
Table has columns with data types that are not supported by Flashback Data
Archive
Cause: An attempt was made to add a
column of data type that is not supported by Flashback Data Archive. Or, the
table on which Flashback Data Archive is being enabled contains column(s) with
data types not supported by Flashback Data Archive.
Action: Do not use FLASHBACK ARCHIVE
clause for this object. If adding column, do not use LONG or Nested Table
column data type.
ORA-55632:
Tablespace has Flashback Archive tables
Cause: An attempt was made to remove
a tablespace that has Flashback Archive tables.
Action: No action required.
ORA-55710:
Unable to alter system parameter GLOBAL_TXN_PROCESSES at this time
Cause: The system was in the process
of adjusting the number of global transaction background processes.
Action: Retry the operation at a later
time.
ORA-55711:
Unable to bind clusterwide global transactions to compatible undo
Cause: Undo tablespace was not
onlined for automatic undo management.
Action: Create undo tablespace if it
has not been created.
ORA-55712:
XA transactions on RAC are not supported with GLOBAL_TXN_PROCESSES set to 0
Cause: The initialization parameter
GLOBAL_TXN_PROCESSES was set to 0.
Action: Set the initialization
parameter GLOBAL_TXN_PROCESSES to a value greater than 0.
ORA-55713:
GLOBAL_TXN_PROCESSES cannot be set to 0 at runtime
Cause: An attempt was made to set
initialization parameter GLOBAL_TXN_PROCESSES to 0 at runtime.
Action: Set the initialization
parameter GLOBAL_TXN_PROCESSES to 0 before starting RAC instance to disable GTX
background processes. Note that XA transactions are not supported on RAC
database when GTX background processes are disabled.
ORA-55800:
NLS errors while processing Oracle number
Cause: Error occurred when trying to
convert Oracle number to an integer.
Action: Check the input parameters.
ORA-56500:
DRCP: Pool not found
Cause: The pool name passed was
either null or an invalid pool name.
Action: Input a valid pool name.
ORA-56501:
DRCP: Pool startup failed
Cause: The connection pool failed to
start up.
Action: Check logs for details.
ORA-56502:
DRCP: Pool is inactive
Cause: The operation is only
supported on an active pool.
Action: Start the pool.
ORA-56503:
DRCP: Pool is active
Cause: The operation is only
supported on an inactive pool.
Action: Shutdown the pool.
ORA-56504:
DRCP: Invalid pool configuration parameter name
Cause: The configuration paramter
name is null or invalid input.
Action: Input a valid configuration
parameter name.
ORA-56505:
DRCP: Invalid pool configuration parameter value
Cause: The configuration paramter
value is null or invalid input.
Action: Input a valid configuration
parameter value.
ORA-56506:
DRCP: Pool shutdown failed
Cause: Connection pool failed to
shutdown.
Action: Check logs for details.
ORA-56507:
DRCP: Pool alter configuration failed
Cause: Connection pool failed to
configure pool.
Action: Check logs for details.
ORA-56508:
DRCP: Pool startup failed
Cause: Connection Broker failed to
startup the pool.
Action: Check logs for details.
ORA-56509:
DRCP: Pool shutdown failed
Cause: Connection Broker failed to
shutdown the pool.
Action: Check logs for details.
ORA-56510:
DRCP: Pool alter configuration failed
Cause: Connection Broker failed to
configure the pool.
Action: Check logs for details.
ORA-56511:
DRCP: Cross instance synchronization failed
Cause: Publish message to all RAC
instances failed.
Action: Check logs for details.
ORA-56512:
DRCP: Failed to synchronize RAC instances [string]
Cause: Some of the RAC instances were
not synchronized.
Action: Perform the same operations on
all the failed instances.
ORA-56513:
DRCP: Cannot perform requested operation using pooled connection
Cause: This operation was not
supported using connections from a pool.
Action: Use a regular connection to
perform this operation.
ORA-56514:
DRCP: invalid value for maximum number of connections to Connection broker
Cause: The value passed exceeded the
maximum allowed.
Action: No action required. The
maximum number of connections was automatically set to the maximum allowed
value.
ORA-56600:
DRCP: Illegal Call
Cause: An illegal OCI function call
was issued
Action: Check the documentation for
Database Resident connection pool usage
ORA-56601:
DRCP: Illegal connection class
Cause: Wrong value for connection
class was given.
Action: Check the documentation for
Database Resident connection pool usage.
ORA-56602:
DRCP: Illegal purity
Cause: Wrong value for purity was
provided.
Action: Check the documentation for
Database Resident connection pool usage.
ORA-56603:
DRCP: Internal error
Cause: Malformed input values.
Action: Input well-formed values.
ORA-56604:
DRCP: Length[string] for string exceeded the MAX
allowed
Cause: Length exceeded MAX for the
value.
Action: Use a value within the MAX
allowed.
ORA-56605:
DRCP: Session switching and migration not allowed
Cause: Application tried to switch or
migrate session across connections.
Action: This usage is irrelevant in
the Database Resident connection pooling context and is not supported. Release
existing session.
ORA-56606:
DRCP: Client version doesnot support the feature
Cause: The client version is lower
than 11g.
Action: Upgrade to a higher client
version or turn off (SERVER=POOLED) in the connect string.
ORA-56607:
DRCP: Connection is already authenticated
Cause: Attempt to reauthenticate the
connection which is authenticated.
Action: Logoff the connection before
reauthenticating.
ORA-56608:
DRCP: Server Group feature is not supported
Cause: Server Group attribute was set
on the server handle, connected to a Database Resident connection pool.
Action: Do not set Server Group
attribute on server handles while using Database Resident connection pool.
ORA-56609:
Usage not supported with DRCP
Cause: This usage was not supported
on a DRCP connection.
Action: Use a dedicated connection to
perform this task.
ORA-56700:
plan string is a subplan and SUB_PLAN attribute cannot be
modified
Cause: An attempt was made to modify
the SUB_PLAN attribute of the specified plan.
Action: Do not attempt to modify the
SUB_PLAN attribute.
ORA-56701:
INTERNAL_USE attribute of consumer group string cannot be
modified
Cause: An attempt was made to modify
the INTERNAL_USE attribute of the specified consumer group.
Action: Do not attempt to modify the
INTERNAL_USE attribute.
ORA-56702:
consumer group string is for internal use only and cannot be a
switch target
Cause: An attempt was made to specify
an INTERNAL_USE consumer group as a switch target.
Action: Do not attempt to switch to
INTERNAL_USE consumer groups.
ORA-56703:
VKTM process died unexpectedly
Cause: An explicit kill or internal
error caused the death of VKTM background process.
Action: Restart the instance.
ORA-56704:
EXPLICIT consumer group mapping priority must be set to 1
Cause: An attempt was made to set the
EXPLICIT mapping priority to a value other than 1.
Action: Set the mapping priorities to
unique integers within the documented range with the EXPLICT priority set to 1.
ORA-56705:
I/O calibration already in progress
Cause: An attempt was made to run a
second instance of I/O Calibration
Action: Wait until the first I/O
calibration run is complete; then, retry the operation.
ORA-56706:
The specified Resource Manager plan is a subplan and cannot be set as a
top-level plan
Cause: An attempt was made to set a
subplan as a top-level plan.
Action: Do not attempt to set subplans
as top-level plans.
ORA-56707:
INTERNAL_QUIESCE plan cannot be specified as a top-level Resource Manager plan
Cause: An attempt was made to specify
INTERNAL_QUIESCE as a top-level Resource Manager plan.
Action: Do not attempt to set
INTERNAL_QUIESCE as a Resource Manager plan.
ORA-56708:
Could not find any datafiles with asynchronous i/o capability
Cause: There are no datafiles which
are asynchronous I/O capable.
Action: Make sure asynchronous i/o is
permitted to datafiles.
ORA-56709:
timed_statistics set to FALSE
Cause: timed_statistics parameter in
database is set to FALSE. Needs to be enabled for calibration.
Action: set timed_statistics=TRUE in
init.ora or "alter system set timed_statistics=TRUE"
ORA-56710:
DBRM process died unexpectedly
Cause: An explicit kill or internal
error caused the death of the DBRM background process.
Action: Restart the instance.
ORA-56711: string is
an invalid string argument
Cause: The named argument is invalid.
Action: Specify a valid argument for
this procedure.
ORA-56713:
Insufficient Resource Manager privileges
Cause: An attempt was made to switch
the consumer group of a user without the appropriate privilege.
Action: Ask the database administrator
to perform the switch operation or grant switch or system privilege to the
user.
ORA-56714:
Plan name string exceeds the maximum length allowed
Cause: Plan name is greater than 30
characters long.
Action: Do not exceed 30 characters
when naming a resource plan.
ORA-56715: string resource
plan contains a reserved word
Cause: The specified plan name is
prefixed with a reserved prefix such as FORCE or SCHED.
Action: Do not prefix resource plan
name with FORCE or SCHED.
ORA-56716:
Category string does not exist
Cause: A non-existent category was
specified as an argument to a procedure in the package, DBMS_RESOURCE_MANAGER.
Action: Specify an existing category
name or create a new category with this name.
ORA-56717:
SWITCH_TIME is set without specifying SWITCH_GROUP
Cause: The plan directive specifies a
SWITCH_TIME without a SWITCH_GROUP.
Action: Specify a SWITCH_GROUP
parameter in the plan directive.
ORA-56718:
Timeout occurred while setting resource plan
Cause: A timeout occurred while
waiting for one or more RAC instances to set the resource plan.
Action: Since the resource plan may
have actually been set successfully, first check the current resource plan for
each instance by querying gv$rsrc_plan. If the resource plan was not
successfully set on all instances, then retry the operation.
ORA-56719:
Error spawning or communicating with calibration slave
Cause: An error occurred in
calibration slave process - Calibration process aborted.
Action: Review trace files for errors.
ORA-56720:
I/O data limit exceeded - call aborted
Cause: The Resource Manager
SWITCH_IO_MEGABYTES limit was exceeded.
Action: Reduce the complexity of the
update or query, or contact your database administrator for more information.
ORA-56721:
I/O data limit exceeded - session terminated
Cause: The Resource Manager
SWITCH_IO_MEGABYTES limit was exceeded.
Action: Reduce the complexity of the
update or query, or contact your database administrator for more information.
ORA-56722:
I/O request limit exceeded - call aborted
Cause: The Resource Manager
SWITCH_IO_REQS limit was exceeded.
Action: Reduce the complexity of the
update or query, or contact your database administrator for more information.
ORA-56723:
I/O request limit exceeded - session terminated
Cause: The Resource Manager
SWITCH_IO_REQS limit was exceeded.
Action: Reduce the complexity of the update
or query, or contact your database administrator for more information.
ORA-56725:
Could not spawn additional calibration slaves
Cause: An error occurred when
spawning calibration slave process - Calibration process aborted.
Action: Check OS resources required
for spawning processes
ORA-56800:
DSKM process died unexpectedly
Cause: An explicit kill or internal
error caused the death of the DSKM background process.
Action: Restart the instance.
ORA-56865:
Invalid IP address in OSSINIT.ORA
Cause: One or more of the specified
IP addresses in OSSINIT.ORA is not valid.
Action: Check that all IP addresses in
OSSINIT.ORA are valid.
ORA-56866:
No IP parameter
Cause: No IP address is set in
OSSINIT.ORA.
Action: Check that one or more valid
IP addresses are set in OSSINIT.ORA.
ORA-56900:
bind variable is not supported inside pivot|unpivot operation
Cause: Attempted to use bind
variables inside pivot|unpivot operation.
Action: This is not supported.
ORA-56901:
non-constant expression is not allowed for pivot|unpivot values
Cause: Attempted to use non-constant
expression for pivot|unpivot values.
Action: Use constants for
pivot|unpivot values.
ORA-56902:
expect aggregate function inside pivot operation
Cause: Attempted to use non-aggregate
expression inside pivot operation.
Action: Use aggregate function.
ORA-56903:
sys_op_pivot function is not allowed here
Cause: invalid use of sys_op_pivot
function.
Action: Remove sys_op_pivot function.
ORA-56904:
pivot value must have datatype that is convertible to pivot column
Cause: Datatype of pivot value is not
convertible to the datatype of pivot column.
Action: Check and correct pivot value.
ORA-56950:
Invalid value for incident identifier
Cause: Invalid incident identifier
argument passed.
Action: Check and correct the
identifier
ORA-56971:
Invalid set of export options
Cause: The options specified are
inconsistent
Action: Check and a consistent set of
option parameters
ORA-56972:
referenced file not found
Cause: One of the file specified in
the test case package is mising
Action: rebuild the SQL test case or
make sure that all the referenced files are readable and located in the same
directory as the SQL test case manifest.
ORA-56973:
import options do not match export options
Cause: The import options specified do
not match the export options
Action: Check that import is being
invoked with the same values for options like export environment, export data
and export metadata
ORA-56974:
Invalid set of import options
Cause: The import options specified
are inconsistent
Action: Check that import options are
consistent and have valid values
ORA-57000:
TimesTen IMDB error: string, number, string
Cause: An OCI interface error
occurred during a TimesTen operation.
Action: Look up the error code in the
TimesTen error documentation to diagnose.
ORA-60001:
adding (string) blocks to save undo segment in tablespace string with
MAXSIZE (string)
Cause: Save undo for the offline
tablespace at segment MAXSIZE.
Action: Check the storage parameters
for the system tablespace. The tablespace needs to be brought back online so
the undo can be applied.
ORA-60002:
adding (string) blocks to temporary segment in tablespace string with
MAXSIZE (string)
Cause: Extending a temporary segment
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60003:
adding (string) blocks to table string.string partition string with
MAXSIZE (string)
Cause: Extending a table partition
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60004:
adding (string) blocks to table string.string with
MAXSIZE (string)
Cause: Extending a table violated
MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60005:
adding (string) blocks to cluster string.string with
MAXSIZE (string)
Cause: Extending a cluster violated
MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60006:
adding (string) blocks to index string.string partition string with
MAXSIZE (string)
Cause: Extending an index partition
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60007:
adding (string) blocks to index string.string subpartition string with
MAXSIZE (string)
Cause: Extending an index
subpartition violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60008:
adding (string) blocks to index string.string with
MAXSIZE (string)
Cause: Extending an index violated
MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60009:
adding (string) blocks to LOB segment string.string partition string with
MAXSIZE (string)
Cause: Extending a LOB segment
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60010:
adding (string) blocks to LOB segment string.string with
MAXSIZE (string)
Cause: Extending a LOB segment
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60011:
adding (string) blocks to lob segment string.string subpartition string with
MAXSIZE (string)
Cause: Extending a LOB segment
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60012:
adding (string) blocks to table string.string subpartition string with
MAXSIZE (string)
Cause: Extending a table subpartition
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60013:
invalid MAXSIZE storage option value
Cause: Invalid value was specified
for MAXSIZE storage clause.
Action: Correct the value and retry
command.
ORA-60014:
invalid MAXSIZE storage option value
Cause: Minimum of 1M should have been
specified against the MAXSIZE storage clause.
Action: Correct the value and retry
command.
ORA-60015:
invalid RETENTION storage option value
Cause: Value of MIN retention should
have been nonzero.
Action: Correct the value and retry
command.
ORA-60016:
Operation not supported on SECUREFILE segment
Cause: The operation to ALTER
FREELIST/RETENTION was not supported on SECUREFILE segment.
Action: Check the LOB type and reissue
the statement.
ORA-60018:
adding string blocks to rollback segment string with
MAXSIZE (string)
Cause: Extending a rollback segment
violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and
retry command.
ORA-60019:
Creating initial extent of size string in tablespace of extent
size string
Cause: Creation of SECUREFILE segment
failed due to small tablespace extent size.
Action: Create tablespace with larger
extent size and reissue command.
ORA-60025:
Event for temp segment cleanup used for temp lobs
Cause: Temp LOB segments used for
temporary LOBs are deleted only on session exit which may lead to large amounts
of memory being held across multiple sessions.
Action: Setting this event will cause
temporary LOB segments to be freed when there are no active temporary LOBs in
the session. Setting this event will have a significant performance impact as
it can cause temporary lob segments to be allocated and deleted many times
during a session rather than once per session. Use this event only when
temporary LOB segment memory use is an issue.
ORA-62001:
value for parameter cannot contain a comma
Cause: Parameter value contained a
comma.
Action: Remove the comma from the
parameter value.
