12C ORA-错误汇总17 NZE-43000 to ORA-56974

NZE-43000: pkcs11 library not found
Cause: The PKCS11 library could not be found.
Action: Make sure that the pkcs11 library is at the location specified in the wallet.
NZE-43001: pkcs11 token not found
Cause: The PKCS11 token could not be found.
Action: Make sure that a token with correct label is present in slot.
NZE-43002: pkcs11 passphrase is wrong
Cause: The PKCS11 passphrase is wrong.
Action: Make sure that the token passphrase specified is correct.
NZE-43005: pkcs11: No tokens present
Cause: a token is not present in the slot
Action: Place a pkcs11 token in the slot
NZE-43011: pkcs11: Token login failed
Cause: To login to the pkcs11 token a correct passphrase is needed
Action: Check the token passphrase.
NZE-43014: pkcs11: finding private key on token error
Cause: error occurred while finding private key on token
Action: Make sure the private key corresponding to the certificate in wallet is on
the token. Check trace message
NZE-43015: pkcs11: key pair gen error
Cause: error occurred while generating key pair using HSM
Action: Check trace message
NZE-43017: pkcs11: No certificate found on the smart card/HSM
Cause: No certificate was found on the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to populate the smart
card/HSM with certificate.
NZE-43018: pkcs11: No user certificate found on the smart card/HSM
Cause: No user certificate was found on the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to populate the smart
card/HSM with certificate and private key.
24-2 Oracle Database Error Messages
NZE-43019: pkcs11: No certificate found on smart card/HSM label with given cert
label
Cause: There were no certificate labels on the smart card/HSM that matched the
certificate label specified in the wallet.
Action: Follow smart card/HSM vendor documentation to set certificate label in
smart card/HSM.
NZE-43020: pkcs11: Multiple certificates found on smart card/HSM with given cert
label
Cause: Certificates with identical labels were found in the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to assign unique
certificate labels to certificates.
NZE-43021: pkcs11: Certificate with given cert label is not a user cert
Cause: The certificate with the specified certificate label did not have a matching
private key in the smart card/HSM.
Action: Follow smart card/HSM vendor instructions to create credentials
(certificate/private key) in smart card/HSM.
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-43814: DROP INDEX is invalid for hash cluster index
Cause: An attempt was made to drop an index defined on a hash cluster. Hash
cluster indexes cannot be dropped.
Action: Do not attempt to drop an index defined on a hash cluster.
ORA-43850: Advanced Compression Option parameter is required to be enabled
Cause: An Advanced Compression Option (ACO) feature was specified without
enabling the ACO parameter.
Action: Set or Update the ACO parameter (enable_option_advanced_
compression) to TRUE.
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. 43854, 0000,
"Deprecated"
ORA-43856: Unsupported LOB type for SECUREFILE LOB operation
Cause: A LOB that is not a SECUREFILE was used in a SQL statement or in a call
where a SECUREFILE LOB was expected.
25-2 Oracle Database Error Messages
Action: Convert the LOB to a SECUREFILE LOB or do not use this keyword or
call.
ORA-43857: Parameter Error
Cause: Attempt to modify a LOB with an invalid parameter.
Action: Fix paramters and retry the operation.
ORA-43859: CONTENTTYPE string too long
Cause: Length of CONTENTTYPE string exceeded the defined maximum.
Action: Modify length of CONTENTTYPE string and retry operation.
ORA-43862: CONTENTTYPE buffer length incorrect
Cause: Length of CONTENTTYPE buffer less than defined constant.
Action: Modify length of CONTENTTYPE buffer and retry operation.
ORA-43878: LOB feature unsupported below compatible setting 11.2.0
Cause: An 11.2 LOB feature was specified when the database was operating at a
compatible setting lower than "11.2.0".
Action: Upgrade the database compatible setting to "11.2.0" or higher to enable
the desired new features.
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.
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.
ORA-43750 to ORA-45907 25-3
ORA-44102: unknown or unsupported algorithm
Cause: An unknown or unsupported authentication or compression algorithm
was encountered.
Action: Check the authentication or compression algorithm. Use one that is
supported by Oracle.
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.
ORA-44204: library cache object string.string found in an in-flux state
Cause: The pseudo-cursor depends on a table which was found to be obsolete due
to metadata invalidation of the library cache object.
Action: Contact Oracle Support Services for additional information.
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
25-4 Oracle Database Error Messages
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-44319: Cannot delete AQ service
Cause: Specified AQ service belonged to a queue.
Action: Delete the queue.
ORA-44320: cannot modify global service
Cause: Could not modify the global service because of insufficient privileges or
you were trying to modify the global service attribute.
Action: Use global service management to modify a global service.
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 'string' to string option
Cause: The given count was a nonpositive number.
ORA-43750 to ORA-45907 25-5
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.
25-6 Oracle Database Error Messages
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-44418: Invalid ACL: string
Cause: The specified ACL did not meet the validation requirements of the
constraining ACL.
Action: Ensure ACL meets the validation requirements of the constraining ACL.
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-44425: XML DB needs to be installed for creating an XMLType table or
column
Cause: An attempt was made to create an XMLType table or column with out
XML DB installed.
Action: Install XML DB.
ORA-43750 to ORA-45907 25-7
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-44607: Archive logging must be enabled.
Cause: Archive logging was not enabled.
Action: Enable archive logging on the database.
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.
25-8 Oracle Database Error Messages
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-44717: First 7 positions (0-6) in the XDB repository is reserved for fusion
security
Cause: An attempt was made to add or add a resource to the XDB repository at a
position reserved for fusion security.
Action: Give a position other than 0 to 6.
ORA-44718: Port conflict in XDB Configuration file
Cause: A port number specified in the XDB Configuration file conflicts with a
port number used in the XDB Configuration file of the same non-consolidated
database or the same Pluggable Database or a different Pluggable Database of the
same consolidated database or the root container of the same consolidated
database.
Action: Specify a different port number.
ORA-43750 to ORA-45907 25-9
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-44734: Predicate Index on nodes with similar children not allowed
Cause: There was at least one node in the document with multiple similar
children which was used in Predicate Indexing.
Action: Try removing Predicate Index on nodes with multiple similar children.
ORA-44735: Too many predicates
Cause: Number of predicates were more than limit.
Action: Try reducing number of predicates.
ORA-44736: Group name already existed
Cause: The group name specified already exists.
Action: Try a different group name.
ORA-44737: Parameter string did not exist.
Cause: The parameter name specified did not exist.
Action: Check the parameter name.
ORA-44738: Group string did not exist.
Cause: The group name specified did not exist.
Action: Check the group name.
ORA-44739: Cannot drop the last group.
Cause: An attempt was made to drop the last group in the index.
Action: Use the DROP INDEX statement instead.
ORA-44740: Parameter string is already registered.
Cause: The parameter name specified was already registered.
Action: Either drop the existing parameter or use a different parameter name.
ORA-44741: Cannot drop a group whose tables are shared by other group(s).
25-10 Oracle Database Error Messages
Cause: An attempt was made to drop a group whose tables are shared by other
group(s).
Action: First drop group(s) with shared table(s) from this group.
ORA-44742: Cannot alter columns of a table that is shared by other group(s).
Cause: An attempt was made to add columns to, modify columns of, or drop
columns from a table shared by other group(s).
Action: First drop group(s) with shared table(s) from this group and then proceed
with this operation.
ORA-44743: Cannot alter columns of a dependent shared table.
Cause: An attempt was made to add columns to, modify columns of, or drop
columns from a dependent shared table. One can only add columns to, modify
columns of, or drop columns from the original shared table.
Action: Use the group name of the original shared table while executing this
operation.
ORA-44744: Cannot have more than one drop, add or modify operations in an
ALTER INDEX statement.
Cause: An attempt was made to have more than one add, modify, or drop column
or group operations in the ALTER INDEX statement.
Action: Use multiple ALTER INDEX statements instead.
ORA-44745: Cannot add or drop columns to or from multiple tables.
Cause: An attempt was made to add or drop columns to or from multiple tables
in a single ALTER INDEX statement.
Action: Use multiple ALTER INDEX statements instead.
ORA-44746: Missing XMLTABLE in GROUP clause.
Cause: An attempt was made to create or add a group without XMLTABLE.
Action: Add required XMLTABLE clause to the GROUP clause.
ORA-44747: An XMLIndex with a structured component cannot be specified with
ASYNC.
Cause: An attempt was made to specify ASYNC parameter for an XMLIndex with
a structured component.
Action: Use valid parameters for XMLIndex with a structured component.
ORA-44748: Invalid name for GROUP.
Cause: An attempt was made to create a GROUP with invalid name.
Action: Use a valid name for the GROUP.
ORA-44749: Missing PATH for the COLUMN.
Cause: An attempt was made to create a COLUMN without PATH.
Action: Specify PATH for the COLUMN definition.
ORA-44750: Cannot create secondary index on unstructured component of
XMLIndex.
Cause: An attempt was made to create a secondary index on the unstructured
component of an XMLIndex when the XMLIndex does not have an unstructured
component.
Action: Alter XMLIndex to add an unstructured component.
ORA-43750 to ORA-45907 25-11
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-44771: Invalid name for a container database.
Cause: The service operation failed.
Action: Check the name of the container database.
ORA-44772: Cluster Ready Services (CRS) operation failed
Cause: The CRS operation failed.
Action: Check the trace file and the CRS daemon log file for details.
ORA-44773: Cannot perform requested service operation.
Cause: The consolidated database was not open. The operation was not
performed.
Action: Open the consolidated database.
ORA-44774: Pluggable database attribute cannot be changed.
Cause: The attempted operation was invalid for a consolidated database.
Action: PDB attribute of a service cannot be changed.
ORA-44775: Pluggable database service cannot be created.
Cause: The attempted pluggable database operation failed.
25-12 Oracle Database Error Messages
Action: Check the trace file for details.
ORA-44776: Pluggable database service cannot be deleted.
Cause: The attempted pluggable database operation failed.
Action: Check the trace file for details.
ORA-44777: Pluggable database service cannot be started.
Cause: The attempted pluggable database operation failed.
Action: Check the trace file for details.
ORA-44778: Invalid value for service attribute retention_time.
Cause: The attempted operation failed.
Action: The value for the service attribute 'retention_time' must be greater than
the value of the service attribute 'replay_initiation_timeout'.
ORA-44779: Invalid value for service attribute replay_initiation_timeout.
Cause: The attempted operation failed.
Action: The value for the service attribute 'replay_initiation_timeout' must be
greater than the value of the service attribute 'failover_delay'.
ORA-44780: Invalid value for service attribute commit_outcome.
Cause: The attempted operation failed.
Action: The value for the service attribute 'commit_outcome' cannot be disabled if
the service attribute 'failover_type' has the value 'transaction'.
ORA-44781: Invalid value for service attribute aq_ha_notifications.
Cause: The attempted operation failed.
Action: The value for the service attribute 'aq_ha_notifications' cannot be disabled
if the service attribute 'failover_type' has the value 'transaction'.
ORA-44782: Cluster Ready Services (CRS) service operation failed - reason: string.
Cause: The attempted CRS service operation failed.
Action: Check the trace file for details.
ORA-44783: The maximum number of runtime load balancing services exceeded.
Cause: The number of runtime load balancing services reached the maximum
allowed.
Action: None
ORA-44784: Service cannot be deleted.
Cause: The attempted service operation failed.
Action: Internal services and the database service cannot be deleted.
ORA-44785: Service attribute commit_outcome cannot be specified for the database
or Pluggable Database service.
Cause: The attempted service operation failed.
Action: None
ORA-44786: Service cannot be started.
Cause: The service was not imported successfully while plugging in the
pluggable database.
Action: None
ORA-43750 to ORA-45907 25-13
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_NAME,
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.
25-14 Oracle Database Error Messages
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 4000 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.
ORA-44822: QoS Resource Manager plan does not exist in database "string"
Cause: QoS Resource Manager plan did not exist in this database.
Action: Rerun CATPROC.SQL to create the plan.
ORA-44823: The QoS Resource Manager plan is not in use
ORA-43750 to ORA-45907 25-15
Cause: The QoS Resource Manager plan was not in use.
Action: Correct the setting of the current Resource Manager plan and try again.
ORA-44824: Resource Manager is disabled
Cause: Resource Manager was turned off.
Action: Reenable the Resource Manager and retry the operation.
ORA-44825: Classifier plan does not match across instances
Cause: Classifier plan was not the same across instances.
Action: Resubmit the classifier plan and try again.
ORA-44826: Number of Performance Classes is more than what was specified.
Cause: The number of Performance Classes submitted were more than what was
specified.
Action: Submit only the specified number of Performance Classes.
ORA-44827: Number of Performance Classes is too large
Cause: A large number ( >= 50) of Performance Classes were requested.
Action: Submit a smaller ( < 50) number of Performance Classes.
ORA-44850: attempt to set a bad status string [string]
Cause: There was an internal Global Service Manager (GSM) error.
Action: Contact Oracle Support Services.
ORA-44851: "string" is not a valid name for a database
Cause: The specified database name was not valid.
Action: Provide a valid database name.
ORA-44852: maximum number of regions exceeded
Cause: The maximum number of regions was exceeded.
Action: Check the catalog to see if you can remove unused regions.
ORA-44853: maximum number of valid nodes for VNCR exceeded
Cause: The maximum number of nodes for valid node checking for registration
(VNCR) was exceeded.
Action: Check the catalog to see if you can remove unused nodes.
ORA-44854: catalog has already been created
Cause: This database already contained the cloud catalog.
Action: Make sure that the specified database name is correct and, if yes, delete
and re-create the catalog.
ORA-44855: cloud name is not valid
Cause: The specified cloud name contained invalid characters or was too long.
Action: Provide a valid (or shorter) cloud name.
ORA-44856: catalog service name is not valid
Cause: There was an internal Global Service Manager (GSM) error.
Action: Contact Oracle Support Services.
ORA-44857: cloud "string" does not exist
25-16 Oracle Database Error Messages
Cause: The specified cloud name did not match the one found in the catalog.
Action: Provide a valid cloud name.
ORA-44858: cannot remove catalog
Cause: The catalog contained one or more database or Global Service Manager
(GSM) objects.
Action: Remove the database and GSM objects from the catalog.
ORA-44859: GSM "string" is already defined in the catalog
Cause: The specified Global Service Manager (GSM) was already in existence in
the catalog.
Action: Check the specified object name.
ORA-44860: Region "string" was not found in the catalog.
Cause: The specified region was not found in the catalog.
Action: Check the specified object name.
ORA-44861: invalid use of REMOVE VNCR command
Cause: A valid node and group name were specified in the same command.
Action: Provide either a valid node or group name.
ORA-44862: region name and buddy region name cannot be the same
Cause: A region was specified as buddy for itself.
Action: Provide a valid buddy region name.
ORA-44863: region "string" is the last region and cannot be removed
Cause: The last region could not be removed from the cloud catalog.
Action: No action is required.
ORA-44864: cannot remove region because it is still being used by a GSM
Cause: The region contained databases or Global Service Manager (GSM).
Action: Remove the database and GSM objects from the region first.
ORA-44865: cannot remove GDS pool because it is still being used by a database or
service
Cause: The Global Data Services (GDS) pool contained databases or services.
Action: Remove the databases and services from the GDS pool.
ORA-44866: pool "string" can only contain databases that belong to a Data Guard
broker configuration
Cause: An attempt was made to add a database that does not belong to a Data
Guard broker configuration to a Data Guard broker pool.
Action: None
ORA-44867: GDS pool already contains database "string"
Cause: The database or service was already in the Global Data Services (GDS)
pool.
Action: None
ORA-44868: pool "string" is a pool that contains a Data Guard broker configuration;
Databases that do not belong to a broker configuration cannot be added to this
pool.
ORA-43750 to ORA-45907 25-17
Cause: An attempt was made to add a database to a pool that contains a Data
Guard broker configuration.
Action: None
ORA-44869: cannot build net service name with "string\ because it is too long
Cause: The automatically created network service name was too long.
Action: Use a shorter network domain name.
ORA-44870: The "role" property is only supported for pools that contain a Data
Guard broker configuration.
Cause: ROLE was specified for a pool that did not contain a Data Guard broker
configuration.
Action: None
ORA-44871: This operation cannot be performed on PREFERRED_ALL service
"string".
Cause: The service was created with the PREFERRED_ALL option.
Action: Do not perform this operation on a PREFERRED_ALL service.
ORA-44872: The same name "string" cannot be used for both source and target
databases.
Cause: The source and target parameters of MOVE SERVICE were the same.
Action: Check the parameters and try again.
ORA-44873: database "string" already offers the service
Cause: An attempt was made to add a service to a database that already offered
the service.
Action: No action is required.
ORA-44874: service "string" not offerered by database "string"
Cause: An attempt was made to start or stop a service on a database that does not
offer the service.
Action: None
ORA-44875: database-related service parameters exceed the maximum allowed
parameter length (1024 bytes)
Cause: The specified database-related service parameters were not valid.
Action: Check the parameters and try again.
ORA-44876: service string is running
Cause: The specified service was running.
Action: This message is informational only.
ORA-44877: service "string" is not enabled on database "string"
Cause: The service could not be started on the database because it was disabled.
Action: Enable the service.
ORA-44878: The database current lag is too high for the service "string".
Cause: The service could not be started on the standby database because the
database current lag exceeds the service lag.
Action: The standby current lag needs to be reduced.
25-18 Oracle Database Error Messages
ORA-44879: A region name has not been provided.
Cause: An attempt was made to add a new Global Service Manager (GSM)
without providing a region. When there is more than one existing region, a region
name must be provided.
Action: Check the syntax and rerun the command.
ORA-44880: catalog has not yet been created
Cause: An attempt was made to modify the catalog, but it does not yet exist.
Action: Create the catalog before trying to modify it.
ORA-44881: GDS pool is not empty
Cause: An attempt was made to add broker configuration to a Global Data
Services (GDS) pool that already contained a database. This is not allowed.
Action: Either remove all databases from the Global Data Services (GDS) pool or
create a new GDS pool.
ORA-44882: The name "string" is not valid for a GDS pool.
Cause: The name of the specified Global Data Services (GDS) pool was not valid.
Action: Check the name and try again.
ORA-44883: The name "string" is not valid for a region.
Cause: The name of the specified region was not valid.
Action: Check the name and try again.
ORA-44884: The name "string" is not valid for a service.
Cause: The name of the specified service was not valid.
Action: Check the name and try again.
ORA-44885: invalid VNCR name string
Cause: The name specified for the valid node checking for registration (VNCR)
was not valid.
Action: Check the name and try again.
ORA-44886: The name "string" is not valid for a VNCR group.
Cause: The name specified for the valid node checking for registration (VNCR)
group was not valid.
Action: Check the name and try again.
ORA-44887: The name "string" is not valid for a GSM.
Cause: The name of the specified Global Service Manager (GSM) was not valid.
Action: None
ORA-44888: The name "string" is not valid for a GSM user.
Cause: The name of the specified Global Service Manager (GSM) was not valid.
Action: Check the name and try again.
ORA-44889: Region "string" is already defined in the catalog.
Cause: The specified region was already in existence in the catalog.
Action: Check the specified region name.
ORA-44890: GDS pool "string" is already defined in the catalog.
ORA-43750 to ORA-45907 25-19
Cause: The specified Global Data Services (GDS) pool was already in existence in
the catalog.
Action: Check the specified pool name.
ORA-44891: GSM "string" was not found in the catalog
Cause: The specified region was not found in the catalog.
Action: Check the specified region name.
ORA-44892: GDS pool "string" was not found in the catalog.
Cause: The specified Global Data Services (GDS) pool was not found in the
catalog.
Action: Check the specified pool name.
ORA-44893: Database "string" was not found in pool "string".
Cause: The specified database was not found in the pool.
Action: Check the specified database name.
ORA-44894: Service "string" was not found in the catalog.
Cause: The specified service was not found in the catalog.
Action: Check the specified service name.
ORA-44895: cannot remove region because it is still being used by a database
Cause: The region contained databases.
Action: Remove the database objects from the region.
ORA-44896: GDS pool already contains service "string"
Cause: The service was already in the Global Data Services (GDS) pool.
Action: None
ORA-44897: The "lag" property is only supported for pools that contain a Data
Guard broker configuration.
Cause: LAG was specified for a pool that did not contain a Data Guard broker
configuration.
Action: None
ORA-44898: The "failover_primary" property is only supported for pools that
contain a Data Guard broker configuration.
Cause: FAILOVER_PRIMARY was specified for a pool that did not contain a Data
Guard broker configuration.
Action: None
ORA-44899: VNCR name "string" is already defined in the catalog.
Cause: The specified valid node checking for registration (VNCR) name was
already in existence in the catalog.
Action: Check the specified VNCR name.
ORA-44900: Identifier "string" is too long.
Cause: The specified identifier exceeded the maximum allowed length.
Action: Use a shorter identifier name
ORA-44901: Unable to resolve symbolic link "string"
Cause: The system is unable to resolve the specified symbolic link.
25-20 Oracle Database Error Messages
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-43750 to ORA-45907 25-21
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.
ORA-45000: SecureFile feature unsupported below compatible 11.2.0.0.0
Cause: An 11gR2 LOB feature was specified when the database was operating at a
compatible setting lower than 11.2.0.0.0.
Action: Upgrade the database compatible setting to 11.2.0.0.0 or higher to enable
the desired new features.
ORA-45001: SecureFile archive implicit not allowed
Cause: A SecureFile was archived and implicit retrieval was not allowed.
Action: Retrieve the SecureFile with a Get operation.
ORA-45002: Content ID not found in the DBFS HS
Cause: The content ID was invalid or was already deleted.
Action: No action required.
ORA-45003: DBFS HS: Invalid checksum, potential data corruption
Cause: Potential data corruption.
Action: No action required.
ORA-45004: DBFS HS SBT Error
Cause: Error related to SBT Tape library.
Action: Refer to error log for more details.
ORA-45005: DBFS HS invalid store
Cause: Error related to DBFS HS Store.
Action: Check that the store name and store parameters are valid values.
ORA-45100: Database incarnation went from string to string. Recovery Appliance
repair is required.
Cause: A 'startup resetlogs' command was executed on the Recovery Appliance.
This caused old metadata to be used to refer to the storage locations. Before the
Recovery Appliance can be started, a repair operation must be run to synchronize
its metadata with its storage.
Action: Execute DBMS_RA.STARTUP_RECOVERY_APPLIANCE. If any
incidents are logged during the subsequent repair, they will need to be corrected.
Once they have been corrected, repeat the execution of DBMS_RA.STARTUP_
RECOVERY_APPLIANCE.
ORA-45102: unable to allocate string bytes of storage
Cause: The Recovery Appliance was unable to allocate additional disk space in
the storage location of the database for the current allocation. This condition may
be due to one of the following reasons: * Guaranteed copy has been specified for a
database and there are too many backups waiting to be copied to tape.
* The metadata of the Recovery Appliance is being repaired.
* Nothing can be purged within the storage location of the database.
Action: Add additional storage to the storage location of the database.
ORA-45109: metadata for database string; file string is corrupt
25-22 Oracle Database Error Messages
Cause: Internal self checks found corruption in the metadata used to manage the
Recovery Appliance block pool.
Action: Contact Oracle Support Services and provide trace and alert files.
ORA-45111: Task string is being terminated after string restarts.
Cause: A Recovery Appliance task generated too many errors. Following an error,
a task is normally restarted. If it fails to restart after 10 tries, the Recovery
Appliance marks the task as broken and no longer tries to restart it.
Action: Correct the error that terminated the task and request the task to be rerun.
ORA-45113: Recovery Appliance internal error string
Cause: An internal error was encountered.
Action: Contact Oracle Support Services and provide trace and alert files.
ORA-45114: file "string" not referenced by metadata for storage location string
Cause: A consistency check performed by the check files task of the Recovery
Appliance identified that the file was not being referenced by the metadata of the
Recovery Appliance. Without these references, the Recovery Appliance cannot
manage the file.
Action: If the file was inadvertently put in the storage location, it should be
moved elsewhere. If the file has been separated from its metadata, contact Oracle
Support Services and provide trace and alert files.
ORA-45115: database with DB_KEY string is too big to move.
Cause: An attempt was made to move the specified database to a new storage
location, but the database could not be shrunk to within its storage reservation and
still preserve its retention window.
Action: Increase the storage reservation for the database or shrink its retention
window.
ORA-45116: anomaly detected while reading metadata for backup piece with BP_
KEY string
Cause: A transient anomaly was found in the backup data.
Action: If the anomaly persists, find a copy of the backup piece, if available, and
reinsert it into the storage location. If no copy is available, generate a new level 0
backup for all data files in the backup piece.
ORA-45118: servlet timeout error
Cause: A restore task was waiting on a servlet process to pass data to a client. The
time allotted for responding was exceeded and the restore task was aborted.
Action: This can be a common occurrence if the client cancels the restore request.
Reissue the request.
ORA-45119: received a nonexistent operation for privilege change
Cause: An illegal option was specified.
Action: BACKUP, RECONCILE, READ, WRITE, and NULL are only supported
values.
ORA-45120: operation failed due to insufficient space
Cause: The storage location was too small to support the new database.
Action: increase the size of your storage location or reduce DISK_RESERVED_
SPACE in the protection policy
ORA-43750 to ORA-45907 25-23
ORA-45121: received an incorrect value for a privilege change
Cause: An internal error was detected while granting or revoking privileges.
Action: Contact Oracle Support Services and provide trace and alert files.
ORA-45122: invalid size or number specified
Cause: An invalid size or number was specified.
Action: Use a non-NULL or number greater than 0.
ORA-45123: The name string (string) already exists.
Cause: The object name was not unique.
Action: Specify a unique name for this object.
ORA-45124: Object string (string) is referenced and cannot be deleted.
Cause: The object was in use by a storage location or database.
Action: Delete all objects that reference this item.
ORA-45125: Object string (string) did not exist.
Cause: The object name did not exist.
Action: Specify an existing object.
ORA-45126: failed to delete database string
Cause: The database could not be deleted. An unexpected error has occurred.
Action: Examine the associated messages to determine the cause of the exception.
ORA-45127: Required parameter string must be specified.
Cause: The parameter was not supplied to API routine.
Action: Rerun the command specifying the missing parameter.
ORA-45128: backup piece string in database string is not referenced by the catalog
Cause: A consistency check performed by the check files task of the Recovery
Appliance identified that the specified backup piece was unreferenced by the
RMAN catalog. Without this reference, the Recovery Appliance cannot reclaim
space used by this piece.
Action: Contact Oracle Support Services.
ORA-45129: expected string bytes used by database string in storage location string,
but found string bytes used
Cause: A consistency check performed by the check files task of the Recovery
Appliance identified that the storage usage of the database in a storage location
did not match the sum of the size of storage pieces assigned to the Recovery
Appliance.
Action: Contact Oracle Support Services.
ORA-45130: Storage parameter overlaps with storage in string.
Cause: A parameter for a storage location was specified that overlapped storage
previously assigned to another storage location.
Action: Reissue the command specifying a different location for the storage.
ORA-45131: illegal or unknown restore compression option specified
Cause: The specified compression option was not supported on either the
Recovery Appliance database or the database providing the backup.
25-24 Oracle Database Error Messages
Action: Query V$RMAN_COMPRESSION_ALGORITHM view to ensure the
algorithm name matches one of the algorithm names in that table and that the
option has IS_VALID = 'YES' and that the INITIAL_RELEASE column is less than
both the Recovery Appliance and the database providing the backup. Reissue the
command specifying a valid compression algorithm name.
ORA-45132: corrupt block detected in backup piece
Cause: A corrupt block was detected in a backup piece when populating the
Recovery Appliance block pool.
Action: Perform block media recovery on the corrupt blocks of the database and
do a cumulative level 1 backup.
ORA-45133: expected string byte allocation by database string, but found string
bytes allocated
Cause: A consistency check performed by the check files task of the Recovery
Appliance found that the storage allocations of the database did not match the
sum of the size of allocations for that database in all storage locations.
Action: Contact Oracle Support Services.
ORA-45135: request terminated by the Recovery Appliance
Cause: A request was holding resources needed by the Recovery Appliance and
was terminated to free those resources. This can be the result of a lack of disk
space or some other resource.
Action: Check available disk space, as well as for errors on the Recovery
Appliance database.
ORA-45136: invalid value for parameter string
Cause: The value supplied for the specified parameter was invalid.
Action: Check the Recovery Appliance documentation and rerun the command
with a correct value.
ORA-45137: unknown platform
Cause: The Recovery Appliance has not received any backups from System
Backup to Tape (SBT) or through polling. This is necessary for the Recovery
Appliance to learn about the protected platform of the database and for the
current operation to succeed.
Action: Backup a small archived log or other backup using SBT or by sending it to
the polling location. Then retry this operation.
ORA-45138: Backup not found.
Cause: The specified backup could not be found in the catalog.
Action: Please check and specify the correct backup piece key or backup set key.
ORA-45139: A useful backup could not be found to correct this corruption.
Cause: A virtual backup piece key was provided, but there was no known backup
on tape or disk to correct this backup.
Action: If the broken backup is the oldest virtual backup for the data file,
sometimes an even older backup will have the data needed to correct the catalog.
Find and specify that older backup directly.
ORA-45140: cannot insert backup into catalog
Cause: The specified backup was either not an incremental or not in the proper
SCN range to correct problems in the catalog.
ORA-43750 to ORA-45907 25-25
Action: Make sure you have provided the correct key value and find a proper
incremental backup piece.
ORA-45141: File "string" was missing from storage location string.
Cause: During recovery of the Recovery Appliance, the specified file was
referenced by the metadata of the Recovery Appliance, but was not found in its
storage location.
Action: The file should be recovered from a replicated Recovery Appliance if it
exists. If the file has been separated from its metadata, then contact Oracle Support
Services and provide trace and alert files.
ORA-45142: The Recovery Appliance prerequisite is already set up.
Cause: The DBMS_RA_INSTALL procedure was executed to set up prerequisite
objects for creation of a catalog schema for the Recovery Appliance. This error is
reported because there can be only one user schema that manages the Recovery
Appliance for the database.
Action: To re-create the Recovery Appliance schema in another user schema,
uninstall the earlier Recovery Appliance schema setup.
ORA-45143: The Recovery Appliance prerequisite setup administors user name is
mismatched.
Cause: The DBMS_RA_INSTALL procedure was executed to uninstall the
Recovery Appliance prerequisite object for the wrong user name.
Action: Correct the user name parameter for DBMS_RA_INSTALL and reexecute
the procedure.
ORA-45144: Undefined initial replication type for protection policy.
Cause: The initial_replication_type was undefined for the protection policy.
Action: Update the protection policy initial_replication_type with one of LAST
FULL, ALL, or NONE.
ORA-45145: Recovery Appliance user string does not exist.
Cause: The Recovery Appliance user did not exist.
Action: Specify an existing Recovery Appliance user.
ORA-45146: Storage location string needs string additional bytes of storage.
Cause: The metadata of the Recovery Appliance was being repaired following a
database open with the 'resetlogs' command and the storage allocated in the
specified storage location was insufficient. This may be caused by either an
'update_storage_location' call being lost due to the 'resetlogs' command or the
storage location becoming very low on free storage when the resetlogs command
was executed.
Action: Update the storage location with the specified values and try the repair
again by executing DBMS_RA.STARTUP_RECOVERY_APPLIANCE.
ORA-45147: Database string and database string are both moving.
Cause: The metadata of the Recovery Appliance was being repaired following a
database open with 'resetlogs' and two databases were found to be moving
between storage locations. The Recovery Appliance will only function correctly
when one database is being moved. This may be caused by an 'update_protection_
policy' or 'update_db' call being lost due to the 'resetlogs' command.
Action: Determine the storage locations used by each database and repeat any
database movements that may have been lost.
25-26 Oracle Database Error Messages
ORA-45148: must fix string errors before restarting the Recovery Appliance
Cause: During a repair of the metadata of the Recovery Appliance, errors were
found that precluded the restart of the Recovery Appliance.
Action: Fix the identified errors and execute DBMS_RA.STARTUP_RECOVERY_
APPLIANCE to retry the repair.
ORA-45149: unknown task type: string
Cause: The Recovery Appliance tried to execute a task with an unknown task
type.
Action: Contact Oracle Support Services.
ORA-45150: File string references unknown DBID string.
Cause: During a repair of the metadata of the Recovery Appliance, the specified
file was found that referenced the specified database which was unknown to the
Recovery Appliance. This may be caused by an 'add_db' call being lost due to a
'resetlogs' command.
Action: Repeat the lost 'add_db' call.
ORA-45151: bad locking protocol for lock string
Cause: An internal error caused locking to be used incorrectly.
Action: Contact Oracle Support Services.
ORA-45152: bad backup piece format for string
Cause: During a repair of the metadata of the Recovery Appliance, the specified
file was found whose type could not be determined.
Action: Remove the corrupted file and reexecute DBMS_RA.STARTUP_
RECOVERY_APPLIANCE.
ORA-45153: unknown data file string for DBID string
Cause: During repair of the metadata of the Recovery Appliance, data for the
specified database was found whose data file could not be found.
Action: Using RMAN on the specified database, use the 'resync' command to
refresh the metadata on the Recovery Appliance and retry the restart of the
Recovery Appliance.
ORA-45154: bad Recovery Appliance format found in file string
Cause: During a repair of the metadata of the Recovery Appliance, a file was
found in a storage location that was neither a chunk file nor a backup piece.
Action: Remove the offending file from the storage location of the Recovery
Appliance and retry the restart of the Recovery Appliance.
ORA-45155: The Recovery Appliance has not been installed.
Cause: The Recovery Appliance was never installed on this database. The
requested procedure is only supported on the Recovery Appliance.
Action: Do not attempt the procedure except on the Recovery Appliance.
ORA-45156: SBT job string not found
Cause: The specified SBT job was not found.
Action: Check if the SBT job has been deleted by user. If so, then drop the
scheduler job.
ORA-45157: Parameter value string (string) is invalid.
ORA-43750 to ORA-45907 25-27
Cause: The specified value for the parameter was invalid.
Action: Specify a valid value.
ORA-45158: SBT library string is not ready.
Cause: The specified SBT library was found to not be ready.
Action: Check if the library has been paused by user. If so, then resume the SBT
library.
ORA-45159: RECOVERY_WINDOW_GOAL is lost for database string.
Cause: A low space condition forced the deletion of backups needed to support
the recovery window goal for the named database.
Action: This is a warning and no action is needed. However, you may use DBMS_
RA.UPDATE_PROTECTION_POLICY to increase the DISK_RESERVED_SPACE
value of the database to ensure additional backups are saved. Select SPACE_
USAGE from RA_DATABASE to see how much space is currently in use. You
should also check for KEEP backups consuming space on disk and decide if they
should be moved to tape or other disk storage. See DBMS_RA.MOVE_BACKUP_
PIECE for more details.
ORA-45160: Incremental forever strategy is lost for database string.
Cause: A low space condition has forced the deletion of backup data needed to
generate the last remaining virtual LEVEL 0 of one or more data files. The next
client backup will be a full LEVEL 0 backup, even if LEVEL 1 was specified.
Action: This is a warning and no action is needed. However, you may use DBMS_
RA.UPDATE_DB to increase the RESERVED_SPACE value of the database to
ensure additional backups are saved. Select SPACE_USAGE from RA_DATABASE
to see how much space is currently in use. You should also check for KEEP
backups consuming space on disk and decide if they should be moved to tape or
other disk storage. See DBMS_RA.MOVE_BACKUP_PIECE for more details.
ORA-45161: The backup piece size cannot exceed database DISK_RESERVED_
SPACE.
Cause: An individual backup piece exceeded the database protection policy
DISK_RESERVE_SPACE value. A safe DISK_RESERVED_SPACE value would
exceed the size of the database.
Action: Use DBMS_RA.UPDATE_DB to increase the DISK_RESERVED_SPACE
value of the database.
ORA-45162: System global area memory is configured incorrectly.
Cause: Check initialization parameters LARGE_POOL_SIZE and SHARED_
POOL_SIZE. The Recovery Appliance will use all of LARGE_POOL_SIZE or 20%
of SHARED_POOL_SIZE to restore virtual or tape backups. The actual space
needed is NETWORK_CHUNKSIZE * 2 * (number of concurrent restore channels)
where NETWORK_CHUNKSIZE is set using DBMS_RA.CONFIG. Use DBMS_
RA.CONFIG to lower NETWORK_CHUNKSIZE or preferably, increase either
LARGE_POOL_SIZE or SHARED_POOL_SIZE.
Action: Check initialization parameters LARGE_POOL_SIZE and SHARED_
POOL_SIZE and set it correctly.
ORA-45163: operation is only supported for user string
Cause: An attempt was made to start the Recovery Appliance by a user other than
the Recovery Appliance administrator.
25-28 Oracle Database Error Messages
Action: Only start the Recovery Appliance as the user specified at installation
time.
ORA-45164: The Recovery Appliance is not running.
Cause: An attempt was made to use the Recovery Appliance, but the Recovery
Appliance has been deactivated by the administrator.
Action: Have the Recovery Appliance administrator execute DBMS_
RA.STARTUP_RECOVERY_APPLIANCE and retry the operation.
ORA-45165: Recovery Appliance backup piece with BP_KEY string is corrupt
Cause: Corruption was found in the backup data.
Action: Ensure that you have a functioning backup of the affected data file. Then
delete the corrupt backup piece to clear the condition.
ORA-45166: unable to access file string
Cause: An attempt was made to access the specified file which resulted in an
error. An explanation of the error appears in the following messages.
Action: Verify the correctness of the file. If it is corrupt, either delete it or replace
it.
ORA-45167: unable to validate backup piece with BP_KEY string
Cause: An attempt was made to validate the specified backup piece which
resulted in an error. An explanation of the error appears in the following
messages.
Action: Verify the correctness of the backup piece. If it is corrupt, either delete it
or replace it.
ORA-45168: unexpected scheduler exit while executing task ID string of type string
Cause: A task failed with an unexpected error code in the Recovery Appliance.
Action: Contact Oracle Support Services.
ORA-45169: unexpected timer process exit
Cause: The timer process failed with an unexpected error code in the Recovery
Appliance.
Action: Contact Oracle Support Services.
ORA-45170: Storage location string is too full.
Cause: Purging the specified storage location would result in the loss of the
recovery window goal for one of its databases.
Action: Add more storage to the storage location or remove some databases from
the storage location or reduce the recovery window goal for some of the databases
in the storage location.
ORA-45171: The chunk optimization task has not run recently for one or more
databases.
Cause: The background chunk optimization task had not been performed recently
for at least one database. This may happen if the Recovery Appliance is too
overloaded with foreground activities to have time to do background tasks.
Action: Remove some load from the Recovery Appliance by reducing the
frequency of backups by protected databases or by offloading some of the
databases from the Recovery Appliance.
ORA-45172: The validation task has not run recently for one or more databases.
ORA-43750 to ORA-45907 25-29
Cause: The background validation task had not been performed recently for at
least one database. This may happen if the Recovery Appliance is too overloaded
with foreground activities to have time to do background tasks.
Action: Remove some load from the Recovery Appliance by reducing the
frequency of backups by protected databases or by offloading some of the
databases from the Recovery Appliance.
ORA-45173: The checkfiles task has not run recently for one or more storage
locations.
Cause: The background checkfiles task had not been performed recently for one
or more storage locations. This may happen if the Recovery Appliance is too
overloaded with foreground activities to have time to do background tasks.
Action: Remove some load from the Recovery Appliance by reducing the
frequency of backups by protected databases or by offloading some of the
databases from the Recovery Appliance.
ORA-45174: unable to use replication server string
Cause: While using the Recovery Appliance, either a backup failed to be
transmitted to the target replicated Recovery Appliance or a restore request failed
to complete on the replicated Recovery Appliance.
Action: Check the following error messages to diagnose the actual error.
ORA-45175: unable to use SBT library string
Cause: While using the Recovery Appliance, a request failed to complete while
using the specified System Backup to Tape library.
Action: Check the following error messages to diagnose the actual error.
ORA-45176: Replication server string is not in the paused state.
Cause: An attempt was made to update information for a replication server that
was not in a paused state.
Action: Pause the replication server on this Recovery Appliance.
ORA-45177: unable to find file string previously found while polling
Cause: A backup piece file previously found in a polling location was later not
accessible to the Recovery Appliance.
Action: If the file was unavailable due to network errors, the file will be found
again once the network is available. If the backup piece was deleted, create a new
backup.
ORA-45178: The allocation unit size cannot be changed.
Cause: An attempt was made to move one or more databases into a storage
location with a different allocation unit size. This value comes from the ASM disk
group allocation unit size specified when creating the disk groups referenced by
the storage location.
Action: Use a storage location with the same minimum allocation size as the
source. If necessary create new disk groups with a matching size before creating a
new storage location.
ORA-45179: The reconcile task has not run recently for database string.
Cause: The background reconcile task had not been performed recently for the
specified database. This may happen if the Recovery Appliance is too overloaded
with foreground activities to have time to do background tasks.
25-30 Oracle Database Error Messages
Action: Remove some load from the Recovery Appliance by reducing the
frequency of backups by protected databases or by offloading some of the
databases from the Recovery Appliance.
ORA-45180: The crosscheck task has not run recently for database one or more
databases.
Cause: The background reconcile task had not been performed recently for at
least one database. This may happen if the Recovery Appliance is too overloaded
with foreground activities to have time to do background tasks.
Action: Remove some load from the Recovery Appliance by reducing the
frequency of backups by protected databases or by offloading some of the
databases from the Recovery Appliance.
ORA-45181: polling found duplicate file name string
Cause: The given file name has already been included in a storage location. There
are three possible reasons for this warning.
* Two databases are contributing to the same polling location but their format does
not include the DBID.
* A backup command did not specify a unique format name.
* Recovery has restored an archived log into that location. This is possible when
the polling location is the primary archive log destination.
Action: If the cause is name formatting, then fix the formatting and rename the
specified files. Polling will then find them again and include them. If this was
recovery, and the files are true duplicates, delete the files. Note that the DELETE_
INPUT option will not help with these duplicate files because they were not
copied.
ORA-45182: database access cannot be granted or revoked using catalog owner or
sys
Cause: The catalog owner or sys was specified as the user in the DBMS_
RA.GRANT_DB_ACCESS and DBMS_RA.REVOKE_DB_ACCESS procedures.
This is not allowed.
Action: A different user should be created and granted the necessary access.
ORA-45183: request is blocked by session string on instance string
Cause: An API request was made to the Recovery Appliance while another API
was in progress. Only one API may be performed at a time.
Action: Wait for the other API to complete or kill the identified session before
repeating the failed API request.
ORA-45184: ORA-string occurred during wallet operation; WRL string
Cause: An operation on the wallet failed due to the indicated error.
Action: Refer to the indicated Oracle message for more information.
ORA-45185: alias string not found in string wallet
Cause: The specified WALLET alias did not appear in the wallet.
Action: Check the WALLET alias or create an alias in the wallet for the specified
attribute and retry the command.
ORA-45187: storage location string is unusable; container repair key is string
Cause: During a repair of the Recovery Appliance, fatal errors were detected
while rebuilding the specified storage location.
ORA-43750 to ORA-45907 25-31
Action: Inspect the alert log for the instance upon which the repair command was
issued for the errors detected. If you detect that the errors are caused by missing
disk groups, add those disk groups and execute the STARTUP_RECOVERY_
APPLIANCE API. If you decide that the missing data cannot be restored, execute
the REPAIR_STORAGE_LOCATION API with the REPLACE option prior to
executing the STARTUP_RECOVERY_APPLIANCE API.
ORA-45188: storage location string requires repair; container repair key is string
Cause: During a repair of the Recovery Appliance, consistency errors were
detected while rebuilding the specified storage location.
Action: Inspect the alert log for the instance upon which the repair command was
issued for the errors detected. If you detect that the errors are caused by missing
disks or disk groups, add those disks or disk groups and execute the STARTUP_
RECOVERY_APPLIANCE API. If you decide that the missing data cannot be
restored, execute the REPAIR_STORAGE_LOCATION API with the REPLACE
option prior to executing the STARTUP_RECOVERY_APPLIANCE API.
ORA-45189: repair failed because storage location was renamed from string to
string
Cause: During a repair of the Recovery Appliance, a storage location was found
whose name was different from the name originally used to define the storage
location.
Action: Delete the bad storage location and re-create it with the proper name.
ORA-45190: anomaly detected while reading metadata for database with DB_KEY
string
Cause: A transient anomaly was found in the backup data.
Action: If the anomaly persists, generate a new level 0 backup for all data files in
the database.
ORA-45191: no suitable SBT library was found for the Recovery Appliance backups
Cause: Recovery Appliance could not find a suitable System Backup to Tape (SBT)
library for performing the Recovery Appliance metadata backups.
Action: Create an SBT library that can be used for the Recovery Appliance
backup.
ORA-45192: reservation already exists for the Recovery Appliance backup
Cause: An attempt was made to create a new reservation to perform a Recovery
Appliance metadata backup when an unexpired reservation exists.
Action: Remove the existing reservation and then create a new reservation.
ORA-45193: multiple SBT libraries are present
Cause: More than one System Backup to Tape (SBT) library was found that can be
used to back up the Recovery Appliance metadata.
Action: Specify a name while reserving the SBT library.
ORA-45194: Recovery Appliance metadata backup to SBT library failed
Cause: An error occurred while backing up the Recovery Appliance metadata to
the System Backup to Tape (SBT) library. The error could be caused by the SBT
library configuration or an internal Recovery Appliance error.
Action: Check the SBT library configuration or RA_INCIDENT_LOG view.
ORA-45195: reservation wait time exceeded
25-32 Oracle Database Error Messages
Cause: A timeout occurred while waiting for the system backup to tape (SBT)
library reservation.
Action: Increase the wait time for the reservation by modifying the '_drive_wait_
minutes' configuration parameter and retry the operation.
ORA-45196: failed to unreserve existing reservation
Cause: The existing System Backup to Tape (SBT) library reservation could not be
unreserved.
Action: Check the 'ERROR_LOG' table and trace files for information about the
cause of this error.
ORA-45197: SBT library string could not be found for reservation
Cause: The Recovery Appliance could not find a System Backup to Tape (SBT)
library for the given name.
Action: Check the SBT library name and retry the operation.
ORA-45198: machine is not a physical Recovery Appliance
Cause: Recovery Appliance services were attempted to start on a machine that
was not a physical Recovery Appliance.
Action: The Recovery Appliance services cannot be started on this system.
ORA-45199: Error string encountered when executing string.
Cause: An error was encountered when executing PL/SQL code. This message
should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
ORA-45200: HTTP status code: string
Cause: The indicated HTTP status code was received while processing a servlet
request,
Action: None
ORA-45201: additional Information: string
Cause: The indicated additional error was received while processing a servlet
request.
Action: None
ORA-45202: operation failed, retry possible
Cause: A backup, restore operation failed while processing a servlet request. The
operation may be retried.
Action: This message is used by the SBT client to decide whether to retry the
operation.
ORA-45203: failed to string backup piece file "string"
Cause: An OS operation on the specified backup piece returned an error.
Action: Check additional messages.
ORA-45210: resource busy, retry possible
Cause: A backup or restore operation failed while processing a servlet request.
The operation may be retried.
Action: This message is used by the SBT client to decide whether to retry the
operation.
ORA-43750 to ORA-45907 25-33
ORA-45211: error encountered while sending data; error code string
Cause: An error was encountered while sending data to the client.
Action: Check additional messages.
ORA-45212: error encountered while receiving data; error code string
Cause: An error was encountered while receiving data from client.
Action: Check additional messages.
ORA-45213: user or role 'string' does not exist
Cause: There was no user or role with the name specified.
Action: Provide a valid user name or role.
ORA-45214: cannot convert 'string' to number
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred.
For example, a NULL value was assigned to a variable that was declared as NOT
NULL or an integer larger than 99 was assigned to a variable declared as
NUMBER(2).
Action: Change the data, how it is manipulated, or how it is declared so that
values do not violate defined constraints.
ORA-45215: cannot delete a replication server that is in use
Cause: An attempt was made to delete a replication server that was actively
restoring a backup.
Action: Cancel the restore or wait for the restore to complete before deleting the
replication server.
ORA-45216: backup metadata of string (string) for database string was not found
Cause: The reported backup metadata was not found.
Action: This is an informational message. Ensure that you retain the backups until
SBT tasks are executed.
ORA-45217: SBT task string is not found
Cause: The specified SBT task was not found.
Action: Provide a valid SBT task identifier and retry the command.
ORA-45264: error encountered during Recovery Appliance test recovery string
Cause: As part of Recovery Appliance protection, test recovery was performed by
the Recovery Appliance metadata protection script. The test recovery uses the
image copies, without additional disk space requirement to restore datafiles, to
test the database.
Action: Additional information regarding this failure is recorded in the RA_
INCIDENT_LOG and is also displayed in the Oracle Enterprise Manager console.
ORA-45265: error encountered during Recovery Appliance backup health check
string
Cause: As part of Recovery Appliance protection, backup health check was
performed by the Recovery Appliance metadata protection script. The backup
health check uses the database 'validate' and 'preview' command to test the
backups.
Action: Additional information regarding this failure is recorded in the RA_
INCIDENT_LOG and is also displayed in the Oracle Enterprise Manager console.
25-34 Oracle Database Error Messages
ORA-45266: error encountered during Recovery Appliance database health check
string
Cause: As part of Recovery Appliance protection, database health check was
performed by the Recovery Appliance metadata protection script. The database
health check uses the 'backup validate' command to perform database health
check.
Action: Additional information regarding this failure is recorded in the RA_
INCIDENT_LOG and is also displayed in the Oracle Enterprise Manager console.
ORA-45275: container: 'string'
Cause: This message reports the name of the Recovery Appliance container
involved in other messages.
Action: See associated error messages for a description of the problem.
ORA-45276: could not create container
Cause: A container creation failed. There will be other messages printed in the
error stack that show more details about the problem.
Action: Investigate the entire error stack. If the problem is correctable, do so and
retry creating this container.
ORA-45277: New AU size string differs from existing AU size string in group string.
Cause: An attempt was made to create a new container that has a different AU
size than the other containers that already exist in this container group.
Action: Specify a container with the same AU size as the other containers in the
container group.
ORA-45278: Container group string is not empty.
Cause: An attempt was made to drop the specified container group but it is not
empty.
Action: Either remove the remaining objects from the group or use the FORCE
option. Note that the FORCE option will irretrievably delete all files in the
container group.
ORA-45279: Container group string does not exist.
Cause: The specified container group does not exist.
Action: Specify a container group that exists.
ORA-45280: Container group string already exists.
Cause: The specified container group already exists.
Action: Specify a container group that does not exist.
ORA-45281: Size of string bytes exceeds maximum container size of string bytes.
Cause: You tried to create a container greater than the maximum size.
Action: Specify a smaller size.
ORA-45282: error identifying container
Cause: An error occurred while identifying a container.
Action: There will be other messages on the error stack that show details of the
problem.
ORA-45283: error writing to container
Cause: An I/O error occurred while writing to a container.
ORA-43750 to ORA-45907 25-35
Action: There will be other messages on the error stack that show details of the
problem.
ORA-45284: error reading from container
Cause: An I/O error occurred while reading from a container.
Action: There will be other messages on the error stack that show details of the
problem.
ORA-45285: Cannot create more than string container groups.
Cause: An attempt to add a new container group would cause the number of
container groups to exceed the system maximum.
Action: Increase the container group limit.
ORA-45286: Cannot create more than string containers.
Cause: An attempt to add a new container would cause the number of containers
to exceed the system maximum.
Action: Increase the container limit.
ORA-45287: File name string is not valid for creation.
Cause: An attempt was made to create a contained file name in an invalid format.
Action: Correct the name and retry the operation.
ORA-45289: Cannot reserve string bytes in container group string.
Cause: The specified container group was out of space.
Action: Add another container to the container group.
ORA-45290: Cannot shrink file string because file is busy.
Cause: The specified file cannot be reduced in size because some other process
was holding the file open.
Action: Wait until the other process releases the file before attempting to reduce
its size.
ORA-45291: Container string is not globally identified.
Cause: An attempt to create or identify a file failed because a required container is
not globally identified in this instance. The logs from the GEN0 process will
usually indicate the reason why the file could not be identified.
Action: Examine the logs from the GEN0 process and correct the problem that is
making some containers inaccessible.
ORA-45292: error during container group rebuild
Cause: An unrecoverable error occurred during container group rebuild.
Action: Review other messages on the error stack for additional details.
ORA-45400: operation not permitted on current database
Cause: An operation was not permitted to start because the database role is not
supported.
Action: Attempt the operation on the primary database. If the primary database
has recently switched to a logical standby database, and an error has occurred,
reexecute the DBMS_ROLLING.SWITCHOVER procedure on the former primary
database until successful completion of the operation.
ORA-45401: upgrade plan is already active
25-36 Oracle Database Error Messages
Cause: An upgrade plan was already active.
Action: The existing plan must first be destroyed by calling DBMS_
ROLLING.DESTROY_PLAN.
ORA-45402: LOG_ARCHIVE_CONFIG must contain the DG_CONFIG attribute
Cause: The DG_CONFIG attribute was missing from the LOG_ARCHIVE_
CONFIG parameter.
Action: Configure this parameter with the DG_CONFIG attribute before
performing DBMS_ROLLING operations.
ORA-45403: database string must be specified in DG_CONFIG
Cause: The specified database was not found in the DG_CONFIG attribute of the
LOG_ARCHIVE_CONFIG parameter.
Action: Add the specified database to the DG_CONFIG attribute of the LOG_
ARCHIVE_CONFIG parameter.
ORA-45404: target version is incompatible
Cause: The configured target software version was incompatible with a DBMS_
ROLLING administered upgrade.
Action: Use alternative upgrade methods.
ORA-45405: A rolling upgrade operation is already in progress.
Cause: A DBMS_ROLLING operation was already in progress. Only one
operation is permitted at a time.
Action: Wait for the operation to complete, or query the PID column of DBA_
ROLLING_STATUS view to identify the active process.
ORA-45406: operation completed with warnings
Cause: An operation succeeded but warnings were generated.
Action: Consult the DBA_ROLLING_EVENTS view for the list of warnings.
ORA-45407: operation encountered a query error
Cause: An internal database query failed.
Action: Consult the DBA_ROLLING_EVENTS and DBA_ROLLING_PLAN views
to identify the error code and instruction that caused the failure.
ORA-45408: parameter name is unknown
Cause: The specified parameter could not be modified because the parameter
name was not recognized.
Action: Verify that the parameter is among the available parameters listed in
DBA_ROLLING_PARAMETERS view.
ORA-45409: parameter value is invalid or out of bounds
Cause: The specified parameter could not be modified because its value was
invalid or out of bounds.
Action: Consult the DBA_ROLLING_PARAMETERS view to obtain the valid
range of values for the associated parameter.
ORA-45410: parameter may not be modified
Cause: The specified parameter could not be modified.
ORA-43750 to ORA-45907 25-37
Action: Internal parameters may not be modified through the DBMS_
ROLLING.SET_PARAMETER procedure. If the parameter is a user parameter, the
parameter is no longer meaningful at the current phase of the upgrade.
ORA-45411: operation requires additional arguments
Cause: An operation has failed because one or more arguments were not
supplied.
Action: Retry the operation with all required arguments.
ORA-45412: parameter scope argument is unknown
Cause: An operation has failed because the database unique name provided in the
scope argument was not known.
Action: Verify that the database unique name exists in the DG_CONFIG attribute
of the LOG_ARCHIVE_CONFIG parameter.
ORA-45413: parameter has no default value
Cause: The specified parameter could not be reverted back to its default value
because the default value did not exist.
Action: The parameter must be set to an explicit value.
ORA-45414: could not connect to a remote database
Cause: Connections to one or more databases failed.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the involved databases and the specific error codes.
ORA-45415: instruction execution failure
Cause: A rolling upgrade operation has halted due to the failure of one or more
required upgrade instructions.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the active instructions and their associated error codes.
ORA-45416: operation cannot start until plan rebuild
Cause: An operation was not permitted to start due to recent parameter
modifications which required a rebuild of the upgrade plan.
Action: Call the DBMS_ROLLING.BUILD procedure to rebuild the upgrade plan.
ORA-45417: operation not permitted since current phase was not string
Cause: An operation was not permitted to start because the upgrade was in a
different phase.
Action: Call the DBMS_ROLLING procedure associated with the current phase.
ORA-45418: database is not running the higher version RDBMS
Cause: A rolling upgrade instruction has failed because a database was not
running the correct target RDBMS version.
Action: Consult the DBA_ROLLING_PLAN view to identify the offending
databases and restart them on the higher version binaries.
ORA-45419: DB_UNIQUE_NAME parameter must be specified
Cause: The DB_UNIQUE_NAME parameter was not configured.
Action: Configure the DB_UNIQUE_NAME parameter.
ORA-45420: return TNS service was not found
25-38 Oracle Database Error Messages
Cause: An instruction failed because a Transparent Network Substrate (TNS)
service name for return communication was not found on a remote database.
Action: Consult the DBA_ROLLING_PLAN view to identify the offending
database or databases.
ORA-45421: database type is not supported by rolling upgrade
Cause: One or more databases specified in the DG_CONFIG attribute was
incompatible with a DBMS_ROLLING administered upgrade.
Action: Disable the databases from the upgrade configuration by setting their
associated INVOLVEMENT parameters to a value of NONE, and rebuild the
upgrade plan.
ORA-45422: operation requires existing plan
Cause: An operation was not permitted to start because it required an active plan.
Action: Configure an upgrade plan by calling the DBMS_ROLLING.INIT_PLAN
procedure.
ORA-45423: target database has mismatched DB_UNIQUE_NAME
Cause: A specified DB_UNIQUE_NAME attribute in a LOG_ARCHIVE_DEST_n
parameter did not match the DB_UNIQUE_NAME at the target database.
Action: Ensure the DB_UNIQUE_NAME attribute and associated Transparent
Network Substrate (TNS) service name or associated connect string has been
configured properly.
ORA-45424: initialization parameter file has unexpected value
Cause: An instruction failed due to an initialization parameter file at a remote
database that was found to be invalid.
Action: Consult the DBA_ROLLING_PLAN view to identify the offending
database.
ORA-45425: operation halted due to required user interaction
Cause: A rolling upgrade operation stopped because interaction is required.
Action: Consult the DBA_ROLLING_EVENTS view to identify the actions
required.
ORA-45426: managed recovery process was not running
Cause: An operation failed due to the inactive managed recovery process at a
remote database.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database. Restart the managed recovery process or
resolve any errors that would prevent the managed recovery process from
remaining active.
ORA-45427: logical standby Redo Apply process was not running
Cause: An operation failed due to the inactive logical standby Redo Apply
process at a remote database.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database. Restart the logical standby Redo Apply process
or resolve any errors that would prevent the logical standby Redo Apply process
from remaining active.
ORA-45428: database was not in expected database role
ORA-43750 to ORA-45907 25-39
Cause: An instruction failed due to a database operating in a database role which
was not expected.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database. If the role change is due to a failover, the
FAILOVER parameter must be set and the upgrade plan must be rebuilt before
resuming the rolling upgrade.
ORA-45429: database was set to an invalid Data Guard protection mode
Cause: An instruction failed due to a database operating at a data protection
mode that was not expected.
Action: Consult the DBA_ROLLING_PLAN view to identify the offending
database. Set the data protection mode accordingly based on the requirement as
described in the instruction.
ORA-45430: flashback database was not enabled
Cause: An instruction failed due to a database that was found to not have
Flashback Database enabled.
Action: Consult the DBA_ROLLING_PLAN view to identify the offending
database. Configure the database with adequate storage to support guaranteed
restore points and enable Flashback Database.
ORA-45431: database was mounted or open in an invalid mode
Cause: An instruction failed due to a database that was mounted or open in an
invalid mode.
Action: Consult the DBA_ROLLING_PLAN view to identify the offending
database and the expected mode. Restart the database in the expected mode.
ORA-45432: future primary database is not a physical standby database
Cause: An operation was not permitted because the future primary database is
not a physical standby database.
Action: Specify a physical standby database as the future primary database.
ORA-45433: failover was detected on an unsupported database
Cause: An operation was not permitted because a failover was detected on a
database which does not permit continuation of the rolling upgrade.
Action: Consult the DBA_ROLLING_EVENTS view to identify the unsupported
database and abort the rolling upgrade.
ORA-45434: multiple failovers of the same type detected
Cause: An operation was not permitted because multiple failovers were detected
on standby databases which protect a common target.
Action: Consult the DBA_ROLLING_EVENTS view to identify the offending
databases. Remove the unwanted databases from the configuration and rebuild
the upgrade plan.
ORA-45435: managed recovery process was running
Cause: An operation failed due to an active managed recovery process at a remote
database.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database and stop the managed recovery process.
ORA-45436: logical standby Redo Apply process was running
25-40 Oracle Database Error Messages
Cause: An operation failed due to an active Redo Apply process at a remote
database.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database and stop the Redo Apply process.
ORA-45437: database upgrade progress is inconsistent
Cause: An operation failed due to the discovery of the catalog upgrade progress
on a database that was different from the progress value saved in the plan state.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database and remove the database from the
configuration.
ORA-45438: database is not in mounted mode
Cause: An operation failed due to the discovery of a database which was not in
mounted mode.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database. If the database was opened, restart the database
in mounted mode.
ORA-45439: database is not in open read/write mode
Cause: An operation failed due to the discovery of a database which was not in
open read/write mode.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database. Open the database in read/write mode.
ORA-45440: server parameter file has not been configured
Cause: An operation failed due to the discovery of a database which was not
configured with a server parameter file that could be modified.
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database. Ensure the database has been configured with a
server parameter file, and that the parameter file can be modified.
ORA-45441: no databases eligible for rollback
Cause: A rollback operation could not start because the databases have not
created the guaranteed restore point needed for rollback.
Action: Arollback is not necessary. The rolling operation can be cancelled by
calling DBMS_ROLLING.DESTROY_PLAN.
ORA-45442: rollback is not permitted after a role change
Cause: A rollback operation was not permitted due to a prior role change event
such as a switchover or failover.
Action: Reconfigure the Data Guard configuration manually.
ORA-45443: cannot quiesce replicated PL/SQL procedures
Cause: An operation failed because there were other processes executing long
running replicated PL/SQL procedures.
Action: Increase the value of DICTIONARY_PLS_WAIT_TIMEOUT and retry the
failed operation.
ORA-45486: database update progress is inconsistent
Cause: An operation failed due to the discovery of the update progress on a
database that was different from the progress value saved in the plan state.
ORA-43750 to ORA-45907 25-41
Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
to identify the offending database and remove the database from the
configuration.
ORA-45500: Cannot remove a database from a pool that contains a broker
configuration.
Cause: An attempt was made to remove a database from a pool that contained a
broker configuration.
Action: If the broker configuration has changed, use the SYNC command in
gsmctl to synchronize the pool
ORA-45501: The maximum number of global service managers for this region has
been exceeded.
Cause: A new Global Service Manager (GSM) was added to a region that already
contained the maximum number of GSMs.
Action: The maximum has been reached. Do not attempt to add anymore GSMs.
ORA-45502: Insufficient privileges to perform this operation.
Cause: A Global Service Manager (GSM) command was executed by a
non-privileged user.
Action: Either connect as a privileged user, or ask your GSM administrator to add
you as a pool or GSM administrator.
ORA-45503: This database is already in cloud string.
Cause: An attempt was made to add a database to a cloud when it was already in
another cloud.
Action: A database can only be in one cloud. Remove it from the other cloud first.
ORA-45504: Cannot relocate a preferred_all service.
Cause: The command 'relocate service' is not supported for preferred_all services.
Action: Do no attempt to relocate a preferred_all service.
ORA-45505: The maximum number of services has been reached.
Cause: The hard limit for the number of global services has been reached.
Action: No more global services can be added without first removing a service.
ORA-45506: The maximum number of GDS pools has been reached.
Cause: The hard limit for the number of Global Data Services (GDS) pools has
been reached.
Action: No more Global Data Services (GDS) pools can be added without first
removing a pool.
ORA-45507: Region string does not have a buddy region.
Cause: The specified region did not have a buddy.
Action: This message is informational only. Consider using 'modify region' to add
a buddy for this region.
ORA-45508: Database string does not have an assigned region.
Cause: The specified database did not have an assigned region.
Action: Use 'modify database' to assign a region to this database.
ORA-45509: Database string has an invalid status "string".
25-42 Oracle Database Error Messages
Cause: The specified database had an invalid status.
Action: Check that the account "gsmuser" has been enabled by the remote DBA,
that you used the correct password for "gsmuser" when running "add database",
and that there is an existing valid node check for registration (VNCR) entry for this
database host.
ORA-45510: There is an outstanding GSM request for change number string created
at string. GSM has failed to apply this request string times.
Cause: A change request originating from a gdsctl command was not applied
after several minutes.
Action: Verify that the Global Service Manager (GSM) server is able to connect to
all databases in the framework to apply the change.
ORA-45511: Service string does not have a preferred database.
Cause: The specified service did not have a preferred database. This can happen if
the database was removed from the pool.
Action: Use 'modify service' to provide a preferred database for this service.
ORA-45512: Service string is a local only service which has an available database in
region string, but does not have a preferred database in the same region.
Cause: The specified service did not have a preferred database in a region in
which it had an available database.
Action: Use 'modify service' to provide a preferred database in this region for this
service, or remove the available database in this region.
ORA-45513: Database string has no global services defined for it.
Cause: A database was added to the global data services framework, but no
global services have been defined for it, or they have all been removed.
Action: This is an informational message. Consider defining a service for this
database, or removing the database from the framework.
ORA-45514: Region string does not contain any databases.
Cause: A region was added to the global data services framework, but no
databases were added to this region, or they have all been removed.
Action: This is an informational message. Consider adding a database to this
region or removing the region.
ORA-45515: Region string does not contain any GSMs.
Cause: A region was added to the global data services framework, but no global
services manager servers were defined for this region, or they have all been
removed.
Action: This is a warning message. You are advised to define a GSM in this region
for high availability.
ORA-45516: GDS pool string does not contain any databases.
Cause: The specified Global Data Services (GDS) pool did not contain any
databases.
Action: This is an informational message. Consider adding databases to this pool
or removing the pool from the global data services framework.
ORA-45517: GDS pool string does not contain any global services.
Cause: The specified Global Data Services (GDS) pool did not contain any global
services.
ORA-43750 to ORA-45907 25-43
Action: This is an informational message. Consider adding services to this pool or
removing the pool from the global data services framework.
ORA-45518: Service string will not be started on logical/snapshot standby.
Cause: The specified service will not be started on a logical/snapshot standby.
Action: This is a warning message. Consider re-defining lag parameter to "any", if
the service needs to be started on a logical/snapshot standby.
ORA-45519: Database pool string is empty; this operation cannot be performed on
an empty pool.
Cause: The database pool does not contain any databases. Therefore this
operation will have no effect.
Action: This is a warning message. Do not perform this operation on an empty
database pool.
ORA-45520: A service with locality ANYWHERE cannot set region failover.
Cause: Service attributes ANYWHERE and REGION_FAILOVER are
incompatible.
Action: Do not attempt to set REGION_FAILOVER on a service with locality
ANYWHERE.
ORA-45521: A service with a primary role cannot set FAILOVER_PRIMARY.
Cause: A service with a primary role cannot set FAILOVER_PRIMARY.
Action: Do not attempt to set FAILOVER_PRIMARY on a service that has a
primary role.
ORA-45522: LOCAL_ONLY service string cannot be relocated to a database in
another region.
Cause: The specified service is LOCAL_ONLY and cannot be relocated to a
database in a different region.
Action: Do not relocate a LOCAL_ONLY service to a database in another region.
ORA-45523: Warning: service string is already stopped.
Cause: The service was stopped already.
Action: None; this is only a warning message.
ORA-45524: must explicitly specify Global Data Services pool name because there
could be multiple candidates
Cause: An attempt to have a default Global Data Services pool when multiple
pools already coexist in the domain failed.
Action: Do not omit '-gdspool gdspool_name_list' when multiple pools exist
ORA-45525: A value of TRANSACTION was provided for the service parameter
'-failovertype', but bad or nonexistent value was specified for service parameter
'-retention'.
Cause: The command specified a value of TRANSACTION for the service
parameter '-failovertype', and either did not provide a value for the parameter
'-retention', or provided a value that was less than or equal to the value provided
for the parameter '-replay_init_time'.
Action: If a service is created with a value of TRANSACTION for the parameter
'-failovertype', then a value must be provided for the parameter '-retention', and
that value must be greater than the value provided for the parameter '-replay_init_
time'.
25-44 Oracle Database Error Messages
ORA-45526: A value of TRANSACTION was provided for the service parameter
'-failovertype', but a bad or nonexistent value was specified for service
parameter '-replay_init_time'.
Cause: The command specified a value of TRANSACTION for the service
parameter '-failovertype', and either did not provide a value for the parameter
'-replay_init_time', or provided a value that was less than or equal to the value
provided for the parameter '-failoverdelay'.
Action: If a service is created with a value of TRANSACTION for the parameter
'-failovertype', then a value must be provided for the parameter '-replay_init_time',
and that value must be greater than the value provided for the parameter
'-failoverdelay'.
ORA-45527: Database compatibility level was too low for use with Global Data
Services (GDS).
Cause: The major database compatibility level is below 12. The Global Data
Services (GDS) feature requires that the database compatibility level of all
participating databases be at 12 or above.
Action: In order to use this database for Global Data Services (GDS), an upgrade
must be completed so that its major compatibility level is at 12 or above.
ORA-45528: Service string has not been globally started.
Cause: An attempt was made to start the service in a specific database without
first starting it globally.
Action: Start the service globally by using 'start service' command without
specifying the '-database' parameter.
ORA-45529: Database has not been configured to use an SPFILE.
Cause: The database was not configured to use an SPFILE. This is required before
it can be used within a Global Data Services (GDS) framework.
Action: again.
ORA-45530: A local service with the same name already exists.
Cause: An attempt was made to create a global service with the same name as an
existing local service.
Action: Use a different service name or delete the existing local service.
ORA-45531: This database is already in another Global Data Services (GDS)
framework.
Cause: An attempt was made to create a Global Data Services (GDS) catalog on a
database that was already in another GDS framework.
Action: Remove this database from the other framework before using it as a
Global Data Services (GDS) catalog.
ORA-45532: This database is already a catalog for another Global Data Services
(GDS) framework.
Cause: An attempt was made add a database to a Global Data Services (GDS)
framework, but it was already a catalog database for another framework.
Action: Do not attempt to to add a Global Data Services (GDS) catalog to another
GDS framework.
ORA-45533: Service string is already being modified from another GDSCTL
session.
Cause: The specified service was already in the process of being modified.
ORA-43750 to ORA-45907 25-45
Action: Wait until any other service modifications have completed. If this problem
persists, contact Oracle Support Services.
ORA-45534: There is a running GSM (Global Service Manager) connected to the
catalog.
Cause: This command could not be executed while there were running GSM
(Global Service Manager) servers connected to the catalog.
Action: Shut down all GSM servers before running this command.
ORA-45535: Catalog version cannot be determined.
Cause: The version of the GDS (Global Data Services) catalog could not be
determined.
Action: Contact Oracle Support Services.
ORA-45536: This version of GDSCTL is not compatible with the GDS (Global Data
Services) catalog.
Cause: The version of GDSCTL being used was not compatible with the current
GDS catalog.
Action: Refer to the documentation for compatible versions and upgrade or
downgrade GDSCTL or the GDS catalog.
ORA-45537: This version of GSM (Global Service Manager) is not compatible with
the GDS (Global Data Services) catalog.
Cause: The version of GSM being used was not compatible with the current GDS
catalog.
Action: Refer to the documentation for compatible versions and upgrade or
downgrade GSM or the GDS catalog.
ORA-45538: The database version is not compatible with the GDS (Global Data
Services) catalog.
Cause: The version of the database being added was not compatible with the GDS
catalog.
Action: Refer to the documentation for compatible versions and upgrade or
downgrade the database or the GDS catalog.
ORA-45539: Database string has already been added to another pool.
Cause: An attempt was made to add a database to a pool, but this database has
already been added to another pool.
Action: Do not attempt to add a database to two different pools.
ORA-45540: Call to SRVCTL failed with status string, errors: string.
Cause: An attempt to call the SRVCTL command line failed with the specified
errors.
Action: Refer to the Oracle Real Application Clusters (Oracle RAC)
documentation and resolve the problems reported by SRVCTL.
ORA-45541: Parameters "-serverpool" and "-cardinality" are invalid for
administrator-managed Oracle RAC databases.
Cause: The service command stipulated -serverpool or -cardinality but this
database was an administrator-managed Oracle RAC database, which does not
recognize these parameters.
Action: Do not use -serverpool or -cardinality on administrator-managed Oracle
RAC databases.
25-46 Oracle Database Error Messages
ORA-45542: Parameters "-serverpool", "-cardinality", and "-instances" are invalid for
non-Oracle RAC databases.
Cause: The service command stipulated -serverpool, -cardinality, or -instances but
this database was a non-Oracle RAC database, which does not recognize these
parameters.
Action: Do not use -serverpool, -cardinality, or -instances on non-Oracle RAC
databases.
ORA-45543: Parameter "-instances" is invalid for policy-managed Oracle RAC
databases.
Cause: The service command stipulated -instances, but this database was a
policy-managed Oracle RAC database, which does not recognize this parameter.
Action: Do not use -instances on policy-managed Oracle RAC databases.
ORA-45544: An invalid weight string was provided for manual override of runtime
load balancing.
Cause: The string provided by GDSCTL to override runtime load balancing with
manual region weights was badly formed.
Action: Retry the command. If the problem persists, contact Oracle Support
Services.
ORA-45545: cannot delete all remaining instances
Cause: This command would delete all remaining instances from the : service,
leaving the service in an invalid state.
Action: Do not provide an instance list that would delete all instances.
ORA-45546: cannot create process to run SRVCTL
Cause: There was a problem creating a new process to run SRVCTL from the
command line.
Action: Check the Oracle alert log on the Oracle database server machine and
rectify the problem on the server.
ORA-45547: A call to SRVCTL failed with error string because of bad parameters.
Cause: The command-line execution of SRVCTL failed because of bad parameters.
Action: Check the database server traces and contact Oracle Support Services.
ORA-45548: The catalog database can be downgraded, downgrading a catalog
database after making changes is not advised.
Cause: This is a warning message only. This command required catalog changes
and the 'compatible' database parameter indicated that the database could be
downgraded. Downgrading a catlog database after making catalog changes is not
advised and may cause data loss in the catalog.
Action: Make your database upgrade permanent by updating the 'compatible'
database parameter before using GDSCTL commands that will alter the catalog.
ORA-45549: Catalog changes are not possible without a running GSM at the current
version.
Cause: This command required catalog changes, which are not allowed unless
there is at least one Global Service Manager (GSM) server running at the current
version.
ORA-43750 to ORA-45907 25-47
Action: Start a GSM server that is running the current version of the software. If
there are none, upgrade at least one exitsing GSM or add a new one at the current
version.
ORA-45550: service does not exist
Cause: An attempt was made to start a service that did not exist on the target
database.
Action: None. This error was caught by the Global Service Manager (GSM), and
the service was created automatically.
ORA-45551: Instance string was not in the instance list for this database.
Cause: An attempt was made to delete an instance from this database but the
instance was not in the existing instance list.
Action: None. This is a warning only. No action was taken for the named instance.
ORA-45552: None of the provided instances were in the instance list for this
database.
Cause: The provided instance list did not contain any valid instances, or the
existing instance list for the catalog was empty.
Action: Check the list of instances and run the command again if necesary.
ORA-45553: Service string does not have any instances defined for database\(s\)
string.
Cause: An attempt was made to start a service on an administrator-managed
Oracle RAC database, but there were no instances defined for the service on that
database.
Action: Define instances for the service on all of the listed databases before
attempting to start the service.
ORA-45554: There are no services that can start on database string.
Cause: An attempt was made to start all services for a given database but there
were no services that could start.
Action: None. This is a warning message indicating that no action was taken for
this command.
ORA-45555: The target database is not in the preferred or available list for this
service.
Cause: The new database name provided was not in the list of preferred or
available databases for the service.
Action: Either add the new database to the service or relocate the service to
another database.
ORA-45556: A database name or service name was not provided.
Cause: A disable service request did not provide either a database name or a
service name.
Action: Provide either a service name or a database name on the request.
ORA-45557: The database pool string does not contain a broker configuration.
Cause: An attempt was made to remove a broker configuration from a database
pool that does not contain one.
Action: Rerun the command using a different database pool.
ORA-45558: There are no database pools in this catalog.
25-48 Oracle Database Error Messages
Cause: The catalog did not have any database pools defined.
Action: Create at least one database pool before running any other commands.
ORA-45559: Global service manager (GSM) string did not provide a version.
Cause: The GSM did not provide a version when attempting to connect to the
catalog.
Action: This version of GSM is too old to connect to the catalog. Upgrade the
GSM installation.
ORA-45560: Database string must contain at least one preferred instance.
Cause: The MODIFY command did not add any preferred instances or removed
all existing preferred instances from this database.
Action: Provide at least one preferred instance, or do not attempt to remove all
existing preferred instances.
ORA-45561: region name is required
Cause: A region name was not provided and was required because there were
multiple regions in the catalog.
Action: Provide the region name on the command line.
ORA-45562: The Global Data Services catalog must be created in a root container.
Cause: The CREATE CATALOG command could not be executed on a container
other than the root container.
Action: Use the root container to create the Global Data Services catalog.
ORA-45563: The pool database cannot be a pluggable database.
Cause: The ADD DATABASE command could not add a pluggable database.
Action: Provide the consolidated database name instead.
ORA-45568: A 12.1.0.1 GDSCTL session cannot make changes in a higher versioned
catalog. Upgrade GDSCTL or run this command from a different client.
Cause: A Global Data Services Control (GDSCTL) command executed from a
12.1.0.1 GDSCTL client attempted to obtain a catalog lock in a higher versioned
catalog.
Action: Upgrade GDSCTL or run this command from another client.
ORA-45600: Transparent Sensitive Data Protection (TSDP) internal error
Cause: There was an unexpected error during TSDP operation.
Action: Retry the command. If the problem persists, contact Oracle Support
Services.
ORA-45601: Invalid data has been found and discarded. Valid data has been
imported.
Cause: The names of invalid or nonexistent database objects were found in the
XML input.
Action: Check the trace files for the names of the invalid objects found in the XML
input.
ORA-45602: Schema string does not exist.
Cause: The schema specified did not exist.
Action: Specify a valid schema.
ORA-43750 to ORA-45907 25-49
ORA-45603: Schema string does not contain table string.
Cause: The table specified did not exist in the schema.
Action: Specify a valid table.
ORA-45604: Column string.string does not exist in schema string.
Cause: The column specified did not exist.
Action: Specify a valid column.
ORA-45605: invalid sensitive type string
Cause: A sensitive type that was associated with one or more sensitve columns
did not exist.
Action: Ensure the valid sensitive type is mentioned. If it is a new sensitive type,
include the definition in the XML input.
ORA-45606: There was no sensitive column matching the given criteria.
Cause: There was no sensitive column matching the schema, table and column
input.
Action: Ensure the valid column is mentioned.
ORA-45607: Column string.string in schema string has already been identified as
sensitive.
Cause: The column was already identified as sensitive.
Action: Remove the column from the list of sensitive columns to be imported.
ORA-45608: There are no sensitive columns for source string.
Cause: No sensitive columns were found for the given source.
Action: Specify the valid source.
ORA-45609: Sensitive type string already exists.
Cause: The sensitive type already existed in the database.
Action: Specify a different name for the sensitive type.
ORA-45610: Sensitive type string does not exist.
Cause: The sensitive type did not exist in the database.
Action: Specify the valid sensitive type.
ORA-45611: cannot drop sensitive type string
Cause: The sensitive type that is associated with one or more columns could not
be dropped.
Action: Ensure the sensitive type is not associated with any column before
dropping it.
ORA-45612: A Transparent Sensitive Data Protection (TSDP) policy with name
string already exists.
Cause: A TSDP policy with the same name was found.
Action: Specify a different name for the policy.
ORA-45613: invalid Oracle security feature
Cause: The Oracle security feature specified was not supported by Transparent
Sensitive Data Protection.
Action: Specify a valid security feature.
25-50 Oracle Database Error Messages
ORA-45614: invalid Transparent Sensitive Data Protection (TSDP) policy string
Cause: The TSDP policy specified did not exist.
Action: Specify a valid policy.
ORA-45615: One or more sensitive column types already exist.
Cause: Importing the list of sensitive columns succeeded. However, one or more
sensitive column types already existed in the database and were not imported
again. The corresponding column is associated with the existing type.
Action: Check the trace files for details regarding which sensitive column types
were not imported.
ORA-45616: Column string.string in schema string is not identified as sensitive.
Cause: An attempt was made to alter a column that was not identified as
sensitive.
Action: Specify a valid column.
ORA-45617: Policy string is not associated with sensitive column type string.
Cause: The given policy was not associated with the sensitive column type.
Action: Specify the valid combination of policy and sensitive column type.
ORA-45618: Policy enforcement on one or more columns failed.
Cause: Policy enforcement on one or more columns encountered errors.
Action: Check the alert log for more details.
ORA-45619: Policy string is not enabled on column string.
Cause: The given policy was not enabled on the column.
Action: Specify a valid policy.
ORA-45620: Policy string is already associated with sensitive column type string.
Cause: The given policy was associated with the sensitive column type.
Action: Specify the valid policy and sensitive column type.
ORA-45621: Disabling of a policy on one or more columns failed.
Cause: Errors were encountered while disabling one or more policies.
Action: Check the alert log for more details.
ORA-45622: warnings generated during policy enforcement
Cause: The cause of this error could be one or more of the following:
- The policy that was associated with the sensitive column type of a column was
not enabled on the column because no subpolicy matched the column properties.
- There was no policy associated with the sensitive column type of a sensitive
column.
- A conflicting redaction policy was enabled on the table.
Action: Check the alert log for more details.
ORA-45623: There is no policy associated with the sensitive column type.
Cause: There was no policy associated with the sensitive column type of a
column.
Action: Check the alert log for more details.
ORA-43750 to ORA-45907 25-51
ORA-45624: reenabling protection failed before import
Cause: Importing the list of sensitive columns failed because there was a problem
in disabling protection on the columns. A subsequent attempt to reenable
protection on the columns also failed.
Action: Check the alert log for more details.
ORA-45625: reenabling protection failed after import
Cause: Importing the list of sensitive columns succeeded. A subsequent attempt
to reenable protection on the columns failed.
Action: Check the alert log for more details.
ORA-45626: Dropping of one or more columns from the list failed.
Cause: Disabling protection on the column failed.
Action: Check the trace files for more details.
ORA-45627: There are no sensitive columns of sensitive column type string.
Cause: There was no column for the given sensitive column type.
Action: Specify a valid sensitive column type.
ORA-45628: no policy associated with sensitive column type string
Cause: There was no policy associated with the sensitive column type.
Action: Specify a valid sensitive column type.
ORA-45629: policy string is enabled on one or more columns
Cause: A Transparent Sensitive Data Protection policy that was enabled on a
column could not be altered or dropped.
Action: Disable the policy before altering or dropping the policy.
ORA-45630: Policy string is associated with one or more sensitive types.
Cause: A Transparent Sensitive Data Protection policy that was associated with a
sensitive column type could not be dropped.
Action: Disassociate the policy from the sensitive column type before dropping
the policy.
ORA-45631: Policy string does not have the given condition.
Cause: The given condition was not found for the policy.
Action: Specify the valid condition for the policy.
ORA-45632: default policy string cannot be altered
Cause: The default policy for Transparent Sensitive Data Protection could not be
altered.
Action: Specify the valid policy to be altered.
ORA-45633: default policy string cannot be dropped
Cause: The default policy for Transparent Sensitive Data Protection could not be
dropped.
Action: Specify the valid policy to be dropped.
ORA-45634: The security feature does not contain parameter string.
Cause: An invalid parameter was found for the given security feature.
Action: Verify the parameters input to the policy.
25-52 Oracle Database Error Messages
ORA-45635: invalid parameter found: string
Cause: An invalid parameter was found for the given security feature.
Action: Verify the parameters input to the policy.
ORA-45636: Input parameter for 'string' is not valid.
Cause: Invalid input was given for the parameter.
Action: Enter valid input.
ORA-45637: invalid condition given for policy condition
Cause: The given condition was invalid.
Action: Enter a valid value for the condition.
ORA-45638: Policy string is enabled on one or more columns of sensitive type
string.
Cause: A Transparent Sensitive Data Protection policy that was enabled on one or
more columns of a particular sensitive type could not be disassociated from the
sensitive type.
Action: Ensure the policy is not enabled on a column of the given sensitive type.
ORA-45639: discovery result cannot be imported
Cause: One or more columns from the XML input were already identified as
sensitive by a different source.
Action: Check the trace file for a list of sensitive columns that were already
identified as sensitive.
ORA-45640: Columns from SYS schema cannot be marked as sensitive.
Cause: A column in a SYS-owned table was being marked as sensitive.
Action: Ensure the column being marked as sensitive does not belong to SYS
schema.
ORA-45641: cannot specify SEC_RELEVANT_COLS parameter
Cause: The SEC_RELEVANT_COLS parameter was specified while configuring a
Transparent Sensitive Data Protection (TSDP) policy. SEC_RELEVANT_COLS_
OPT parameter can be specified to indicate that TSDP should input the sensitive
column as input to SEC_RELEVANT_COLS parameter at the time of enabling
protection.
Action: Use the SEC_RELEVANT_COLS_OPT parameter to configure the security
relevant column.
ORA-45900: data file number string already included as string
Cause: RMAN attempted to use the specified data file number, but this data file
number was already in use by a different container database.
Action: Resolve the conflict and retry the command.
ORA-45901: File string is from different container identifier string; current string
Cause: This backup piece contained a data file that did not belong to the current
container. Cataloging such a backup piece is not allowed.
Action: Connect to root or correct Pluggable Database and retry the command.
ORA-45902: cannot rename data file 'string' - file was instantly restored.
Cause: During ALTER DATABASE RENAME or RMAN command SWITCH, the
rename was specified for an instantly restored file.
ORA-43750 to ORA-45907 25-53
Action: Rename the file that was not instantly restored or wait until the
repopulation work is complete and the retry the command.
ORA-45903: catalog instantly restored data file copy string is not supported
Cause: This data file copy was instantly restored. Cataloging such file is not
supported.
Action: Do not request to catalog instantly restored data file copy.
ORA-45904: instant restore of data file copy string is not supported
Cause: An attempt was made to create a data file copy in instant restore mode.
This is not supported.
Action: Do not request to create data file copy in instant restore mode.
ORA-45905: deleting or restoring instantly restored data file string is not supported
Cause: This data file was instantly restored with the full option. A background
process was repopulating the data file. An attempt to take the data file out of the
process failed. Deleting or restoring such files is not supported.
Action: Retry the command later.
ORA-45906: moving instantly restored data file string is not supported
Cause: This data file was instantly restored. Moving such file is not supported.
Action: Do not request to move instantly restored data file.
ORA-45907: instant restore of data file string failed
Cause: During an instant restore, it was not possible to initialize the destination
data file. There might be other messages on the error stack or alert log or trace file
that indicate the specific reason for the failure. One common reason for this
message is that the instant restore feature is disabled in this database.
Action: Check the other messages. If the situation cannot be resolved, then
request a regular (not instant) restore.
ORA-46000: invalid option to apply XS Data Security
Cause: The input value was not a valid option to apply XS Data Security.
Action: Use a valid option to apply XS Data Security.
ORA-46001: argument string is not valid for XS Data Security policies
Cause: An illegal argument value was used with DBMS_RLS to apply XS Data
Security.
Action: Use the XS_DATA_SECURITY API to apply XS Data Security.
ORA-46003: Column "string" is not valid in data security policy for "string"
Cause: An invalid column was specified in the data security policy.
Action: Correct the column name in the policy.
ORA-46004: XS Data Security policy is not applied on string.string
Cause: A table without an XS Data Security policy applied was specified.
Action: Specify a table with one XS Data Security policy applied.
ORA-46005: multiple XS Data Security policies applied on string.string
Cause: A table with more than one XS Data Security policy applied was specified.
Action: Specify a table with one XS Data Security policy applied.
ORA-46006: cannot mix VPD column and XS column constraint policies
Cause: The object was protected by both VPD (Virtual Private Database) column
security and XS column constraint policies.
Action: Disable or drop either the VPD or XS column policies.
ORA-46007: no XS Data Security policy associated with string.string
Cause: A table not associated with an XS Data Security policy was specified.
Action: Specify a table associated with an XS Data Security policy.
ORA-46008: multiple XS Data Security policies associated with string.string
Cause: A table associated with more than one XS Data Security policy was
specified.
Action: Specify a table associated with one XS Data Security policy.
ORA-46019: User-built Static ACL Materialized View does not exist
Cause: A non-existing user-built Static ACL Materialized View was specified
26-2 Oracle Database Error Messages
Action: Create a user-built Static ACL Materialized View with the specified name
or use system-built Static ACL views
ORA-46020: User-built Static ACL Materialized View has invalid schema
Cause: A user-built Static ACL Materialized View was specified but with an
incorrect schema
Action: Create a user-built Static ACL Materialized View with at least the
required columns with correct names and types
ORA-46021: Invalid refresh mode specified for Static ACL Materialized View
Cause: The refresh mode specified for the Materialized View supporting static
ACLs is invalid.
Action: Specify either "ON DEMAND" or "ON COMMIT" for parameter refresh_
mode
ORA-46022: Invalid name specified for user-built Static ACL Materialized View
Cause: The name specified for the Static ACL Materialized View (ACLMV) is
reserved for system-built ACLMVs.
Action: Rename the user-built Static ACL Materialized View
ORA-46023: Application Session affinity is not the same as when the cursor was
parsed.
Cause: The security context was changed and was different from the time the
cursor was parsed.
Action: Make sure the security context is the same as when the cursor was parsed.
ORA-46024: The policy schema differs from the object schema for Static ACL
Materialized View based XDS policy.
Cause: The specified object schema was different from the policy schema.
Action: Make sure the object and the policy have the same schema.
ORA-46025: no static rule specified in applied policy
Cause: The policy applied on the table did not contain any static rules.
Action: Ensure the applied policy has at least one static rule.
ORA-46026: creation of static ACL materialized view (MV) failed
Cause: Creation of the static access control list (ACL) materialized view (MV)
failed.
Action: Check the trace file for detailed error information.
ORA-46050: Oracle Real Application Security internal error.
Cause: There was an Oracle Database Real Application Security internal error.
Action: None
ORA-46051: invalid application user specified
Cause: An invalid application user was specified.
Action: Check the user name and execute the function or procedure again.
ORA-46052: invalid session ID specified
Cause: An invalid XS Security session ID was specified.
Action: Check the session ID and execute the function or procedure again.
ORA-46000 to ORA-46900 26-3
ORA-46053: invalid cookie specified
Cause: An invalid XS 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 XS session application namespace or system-defined
namespace was specified. Certain operations are not allowed on the
system-defined namespace.
Action: Check the namespace and execute the function or procedure again.
ORA-46055: invalid role specified
Cause: An invalid application role was specified.
Action: Check the role and execute the function or procedure again.
ORA-46056: invalid namespace or attribute specified
Cause: An invalid XS 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 XS Security application namespace was already in existence.
Action: Execute the function or procedure with a different namespace.
ORA-46058: attribute string is invalid
Cause: An invalid XS 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: user name not specified
Cause: An application user was not specified.
Action: Execute the function or procedure with a user name.
ORA-46061: session ID not specified
Cause: XS Security session ID was not specified.
Action: Execute the function or procedure with a session ID.
ORA-46062: Namespace not specified
Cause: XS Security application namespace was not specified.
Action: Execute the function or procedure with a namespace.
ORA-46063: not attached to XS Security session
Cause: There was no attachment to an XS Security session.
Action: Attach to an XS Security session and execute the function or procedure.
ORA-46064: attribute name not specified
Cause: XS Security application namespace attribute name was not specified.
Action: Execute the function or procedure with an attribute name.
26-4 Oracle Database Error Messages
ORA-46065: attribute value not specified
Cause: XS 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: XS Security session inactivity timeout was not specified.
Action: Execute the function or procedure with an inactivity timeout value.
ORA-46067: cookie not specified
Cause: XS Security session cookie was not specified.
Action: Execute the function or procedure with a cookie value.
ORA-46068: role not specified
Cause: XS Security role was not specified.
Action: Execute the function or procedure with a Role value.
ORA-46069: operation disallowed in an application session
Cause: Operations were blocked when an application session was attached.
Action: Try the operation later after the application session is detached.
ORA-46070: insufficient privileges
Cause: An attempt was made to execute an XS 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 occured in event handler string
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.
Also, abort attach session since the changes made to the session by the event
handler might not have been recorded because of the error.
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 in use by another session
Cause: The specified XS Security session cookie was used by another XS 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 an application user session
Cause: The current database session is already attached to an application user
session.
ORA-46000 to ORA-46900 26-5
Action: Detach from the current application user session before attaching to the
new application user session.
ORA-46076: The specified name length not within valid range.
Cause: The length of the name was shorter or longer than allowed limits.
Action: Try again with a new name with a length less than the maximum or or
more than the minimum allowed.
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.
ORA-46079: invalid external principal specified
Cause: An XS Security principal already existed with same name.
Action: Specify another external principal and try again.
ORA-46080: User status is currently inactive
Cause: User was marked inactive.
Action: Change status in enterprise directory to active and try again.
ORA-46081: User's password has expired
Cause: User password was expired.
Action: Change the user's password and update status to active.
ORA-46082: User's account was locked
Cause: The user's account is locked.
Action: Update user's status to Active in Enterprise Directory and try again.
ORA-46083: Cannot update the GUID of the principal
Cause: The GUID of the principal existed or the external source was not set.
Action: None
ORA-46084: cannot update or delete system-seeded XS objects.
Cause: An attempt was made to update or delete system-seeded XS objects.
Action: Do not attempt to update or delete system-seeded XS objects.
ORA-46085: Cannot add a proxy user when there was no proxy roles.
Cause: An attempt was made to add a proxy user to a target user when proxy
roles did not exist.
Action: Verify the proxy roles and try again.
ORA-46086: Cannot detach from a direct-login XS session
Cause: An attempt was made to detach from an XS session created by a direct
password login.
Action: To detach and destroy the XS session, logout of the DB session.
ORA-46087: Switching users not allowed for a proxy session
Cause: An attempt was made to switch users within a proxy session.
26-6 Oracle Database Error Messages
Action: Switch back to original user and try again.
ORA-46088: operation disallowed in application session
Cause: The specified operation was not allowed in an application session.
Action: None
ORA-46089: Unsupported verifier type
Cause: This verifier was not currently supported.
Action: Execute again with a different verifier type.
ORA-46090: Requested event handler not registered for the event
Cause: An attempt was made to update or delete nonregistered event handler.
Action: Please verify event handler name.
ORA-46091: Requested event handler already registered for the event
Cause: An attempt was made to re-register an event handler.
Action: Please verify event handler name.
ORA-46092: Requested event handler does not exist
Cause: An attempt was made to register a nonexistent event handler.
Action: Please verify event handler name or create the event handler.
ORA-46093: Cannot destroy a direct-login XS session
Cause: An attempt was made to destroy an XS session created by a direct
password login.
Action: To destroy the XS session, logout of the DB session.
ORA-46094: XS user not effective
Cause: An attempt was made to create an XS session by a user that is not effective.
Action: To create the XS session, contact the administrator to check the effective
dates on the user.
ORA-46095: Invalid error code supplied
Cause: An error code with an illegal value was supplied.
Action: Use an error code from the range of valid values.
ORA-46096: An attribute in a namespace cannot have both default value and first
read event set.
Cause: Both default value and first read were specfied in namespace template.
Action: Specify either default value or first read for the attribute in the
namespace, but not both.
ORA-46097: The string did not exist in the string.
Cause: An attempt was made to delete an XS artifact which was not in existence
within the scope.
Action: Check if the XS artifact was created or referenced within the scope.
ORA-46098: The string already exists in the string.
Cause: An attempt was made to create or refer to an XS artifact which was already
in existence within the scope.
Action: Check if the XS artifact name is unique within the scope.
ORA-46000 to ORA-46900 26-7
ORA-46099: Feature unsupported or not implemented
Cause: This feature was not supported or implemented.
Action: None
ORA-46100: XS session operations are disallowed during the execution of a
definer's rights program unit.
Cause: An attempt was made to do an XS session operation that could modify the
current security context inside a definer's rights program unit.
Action: Change the program unit to invoker's rights.
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 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: Privilege string not found in the associated security classes
Cause: The specified privilege did not exist in the security classes that were
associated with the ACLs.
Action: Use a security class that contains the specified 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.
ORA-46109: Duplicate definition for privilege string in security class string.
Cause: The privilege name in the security class was previously defined in another
security class.
Action: Provide a unique name for the privilege.
26-8 Oracle Database Error Messages
ORA-46111: Security Class string specified in the ACL string does not exist.
Cause: An invalid security class was specified in the ACL.
Action: Specify a valid security class.
ORA-46112: Duplicate security class name string under targetnamespace string
Cause: The security class name under the targetnamespce was also used for
another security class.
Action: Provide a unique name for the security class.
ORA-46114: ACL name string not found.
Cause: An invalid ACL name was used as one of the operator parameters.
Action: Specify a valid ACL name.
ORA-46115: error raised during evaluation of a data realm
Cause: During SQL execution, evaluation of a data realm failed with an error.
Action: Find the cause of the error from the error stack.
ORA-46116: The ACL string is referenced by a namespace template.
Cause: An attempt was made to delete an access control list (ACL) which was
referenced by a namespace template.
Action: Delete the namespace template first if the ACL needs to be deleted.
ORA-46200: Attribute cannot be deleted. The attribute is seeded from the template.
Cause: An attempt was made to delete an attribute that was seeded from the
template from which this namespace was created.
Action: Attempt to delete only custom attributes.
ORA-46201: Attribute string already exists in namespace string.
Cause: An attempt was made to create an attribute that already exists within the
given namespace.
Action: Make sure the attribute name is unique within the namespace.
ORA-46202: handler specified in the namespace template does not exist
Cause: An attempt was made to create a namespace template with an invalid
handler function.
Action: Specify a valid handler function in the template.
ORA-46203: handler is not specified in the namespace template
Cause: An attempt was made to create a template or a custom attribute with
events specified. However, a handler function was not specified in the template.
Action: Specify a valid handler function in the template.
ORA-46204: Multiple UID or GUID specified for the resource.
Cause: An attempt was made to create a resource with multiple UIDs or GUIDs
specified in the document.
Action: Provide, at most, one UID or GUID for the resource in the document.
ORA-46205: User with empty GUID cannot create session.
Cause: An attempt was made by an user with an empty GUID to create a session.
Action: Update the GUID for the user.
ORA-46206: Negative inactivity timeout value not allowed.
ORA-46000 to ORA-46900 26-9
Cause: An attempt was made to set the inactivity timeout time to a negative
value.
Action: Specify a non-negative inactivity timeout value.
ORA-46207: During global callback execution, string is not allowed.
Cause: An attempt was made to execute a disallowed session operation during
global callback execution.
Action: Remove the invalid session operation from callback function.
ORA-46208: Circular callback call caused by string
Cause: Circular callback call caused an infinite chain of callback function
executions.
Action: Check the event handling functions to identify the source of the circular
callback call. Attempt the operation again after the error has been resolved.
ORA-46209: User switch is disallowed for administrative operation.
Cause: An attempt was made to switch user with administrative operation.
Action: Attach the application session to a database session first.
ORA-46210: Source user is not anonymous in user assignment operation.
Cause: An attempt was made to assign user to a named user.
Action: Change source user to the anonymous user first.
ORA-46211: XS entity name length not within valid range.
Cause: An attempt was made to create an XS entity with a name length less than
the minimum or more than the maximum allowed.
Action: Ensure the name length is in the valid range (between 1 and 128).
ORA-46212: XS entity with this name already exists.
Cause: An attempt was made to create an XS entity with a name that already
belongs to another entity.
Action: Use a different name and try again.
ORA-46213: An unexpected constraint violation occurred during creation of an XS
entity.
Cause: An attempt was made to create an XS entity resulting in an unexpected
constraint violation.
Action: Check with the DBA or security administrator for resolution.
ORA-46214: Deletion of the XS entity is not allowed while dependencies exist.
Cause: An attempt was made to delete an XS entity with dependent entities in the
system.
Action: Remove the dependencies and try again.
ORA-46215: XS entity by the name string did not exist.
Cause: A reference was made to an XS entity that did not exist.
Action: Review the entity reference and try again.
ORA-46216: XS entities are not related.
Cause: An attempt was made to remove a relation that did not exist.
Action: Review the entity reference and try again.
26-10 Oracle Database Error Messages
ORA-46217: Operation is not allowed.
Cause: An unexpected operation was performed.
Action: Check with the DBA or security administrator for resolution.
ORA-46218: Unauthorized proxy user
Cause: The current user was not an authorized proxy user of the client user
during a switching user operation.
Action: Add the current user as a proxy user of the client user.
ORA-46219: Role version numbers mismatch in server and mid-tier.
Cause: There was another mid-tier attached to the server session with a different
set of roles.
Action: Reattach the session supplying the current set of roles.
ORA-46220: database is in readable standby mode; changes will not be saved
Cause: An attempt was made to change an application session in readable
standby mode.
Action: None
ORA-46221: cannot modify an application user that is currently connected
Cause: An attempt was made to modify an application user that is currently
logged on.
Action: Make sure the application user is logged off, then repeat the command.
ORA-46222: Real Application principal name string conflicts with another user or
role name.
Cause: There was already a user or role with that name.
Action: Specify a different user or role name.
ORA-46230: XS administrative operation failed.
Cause: An unexpected error occurred during the requested XS administrative
operation.
Action: None
ORA-46231: Granted role is not a regular role.
Cause: A nonregular role was granted to a principal.
Action: Grant a regular role to a principal.
ORA-46232: Circular grant for role
Cause: The role was granted from itself through circular operation.
Action: Fix the role grant operation.
ORA-46233: Circular definition for ACL string
Cause: The ACL was inherited from itself through circular definition.
Action: Fix the ACL definition.
ORA-46235: Policy parameter string did not exist.
Cause: The policy parameter did not exist.
Action: Review the parameter definition and try again.
ORA-46236: Invalid policy parameter type
ORA-46000 to ORA-46900 26-11
Cause: Invalid parameter type was specified.
Action: Use the correct parameter type.
ORA-46237: Mid-tier cache synchronization failed
Cause: An unexpected error occurred during mid-tier cache synchronization.
Action: None
ORA-46238: Database user or role 'string' does not exist
Cause: An invalid database user or role was specified as the principal name.
Action: Make sure the database principal is a valid database user or role.
ORA-46239: Key manager not initialized.
Cause: A request to sign the message could not be processed because the key
manager was not initialized.
Action: Reinitialize the key manager and resubmit the request.
ORA-46240: Application proxy user is already configured with a schema.
Cause: An attempt was made to add a schema to an application proxy user that
already was configured with a schema.
Action: Remove the schema configuration of the application proxy user and try
again.
ORA-46241: Application proxy user is not configured with the schema.
Cause: An attempt was made to remove a schema from an application proxy user
that was not configured.
Action: None
ORA-46242: Granting a role to XSGUEST is not allowed.
Cause: An attempt was made to grant a role to the XSGUEST seeded user.
Action: None
ORA-46243: The dispatcher's session does not exist.
Cause: The dispatcher's session timed out due to inactivity.
Action: Increase the inactivity timeout for the dispatcher's session.
ORA-46244: The request is not signed by the dispatcher.
Cause: A request was made without the dispatcher's signature. The server is
configured to accept requests signed by the dispatcher only.
Action: Ask the administrator to configure the mid-tier allowing the dispatcher
signature. Or, ask the administrator to configure the server to not be in
dispather-only mode.
ORA-46245: Invalid session or namespace request
Cause: The request message was corrupt.
Action: Check with the DBA or security administrator for resolution.
ORA-46246: session operation failed
Cause: An attempt was made to either update an XS Data Security session which
did not exist, or to create an XS Data Security session which already existed, or to
attach a direct-login XS Data Security session.
Action: None
26-12 Oracle Database Error Messages
ORA-46247: detach completed; session changes are not saved
Cause: The XS Data Security session is detached successfully, but session changes
are not saved due to updating an XS Data Security session which did not exist.
Action: None
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.
ORA-46000 to ORA-46900 26-13
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 DBMS_AUDIT_MGMT operation.
Action: Check the PL/SQL error stack and trace files for a possible error. Fix the
cause and retry the operation. If the error is internal or if there is no error, contact
Oracle Support Services.
ORA-46265: Subset of audit trail is already initialized
Cause: Audit Trail was initialized which spans the given audit trail type.
Action: Use DBMS_AUDIT_MGMT.DEINIT_CLEANUP to deinitialize conflicting
audit trail types.
ORA-46266: Missing value for argument 'string' in Oracle RAC enabled database
Cause: The DBMS_AUDIT_MGMT API was executed in an Oracle RAC enabled
database and AUDIT_TRAIL_TYPE was one of AUDIT_TRAIL_OS or AUDIT_
TRAIL_XML. But, Oracle RAC instance number for which DBMS_AUDIT_MGMT
API was run, was not supplied.
Action: Input a valid Oracle RAC instance number for which the configuration
must be done.
ORA-46267: Insufficient space in 'string' tablespace, cannot complete operation
Cause: Could not complete the operation because the DBMS_AUDIT_MGMT API
involved movement of one or more audit tables and there was not enough space in
the destination tablespace.
Action: Turn on tracing using DBMS_AUDIT_MGMT.SET_DEBUG_LEVEL to
find the amount of space required. Then, allocate that space in the destination
tablespace, even if destination tablespace datafile has AUTOEXTEND option
turned on. And then, retry the operation.
ORA-46268: Conflicting operation on audit table(s)
Cause: Audit tables were being operated by more than one DBMS_AUDIT_
MGMT API from different sessions. The simultaneous execution of the following
API with one another and with itself can cause the conflict: INIT_CLEANUP,
DEINIT_CLEANUP, SET_AUDIT_TRAIL_LOCATION and MOVE_DBAUDIT_
TABLES.
Action: Wait until the execution of one of the API's completes and try executing
the API again.
ORA-46269: Conflicting operation on audit files
26-14 Oracle Database Error Messages
Cause: Audit files were being operated by more than one DBMS_AUDIT_MGMT
API from different sessions. The simultaneous execution of the CLEAN_AUDIT_
TRAIL API with itself can cause the conflict.
Action: Wait until the execution of one of the API's complete and try executing the
API again.
ORA-46271: Error during DBMS_AUDIT_MGMT operation; database I/O
suspended
Cause: An I/O attempt occurred during DBMS_AUDIT_MGMT operation and
the database I/O was suspended.
Action: Retry the operation after resuming database I/O suspension. If database
I/O is not suspended, contact Oracle Support Services.
ORA-46272: Subset of audit trail is already deinitialized
Cause: Audit trail was deinitialized which spans the given audit trail type.
Action: Use DBMS_AUDIT_MGMT.INIT_CLEANUP to initialize conflicting audit
trail types.
ORA-46273: DBMS_AUDIT_MGMT operation failed in one of the PDB
Cause: The executed DBMS_AUDIT_MGMT operation failed in one of the PDB.
Action: Check the trace files for the PDB information where the operation failed.
Fix the cause and retry the operation. If the error is internal or if there is no error,
contact Oracle Support Services.
ORA-46274: Error during DBMS_AUDIT_MGMT operation; tablespace 'string' not
available
Cause: The tablespace associated with Unified Audit Trail is either invalid or is
offline.
Action: Check if the tablespace is valid and make sure the tablespace is online and
writable.
ORA-46275: Conflicting operations on 'string' table
Cause: Audit trail table was being operated by more than one API from different
sessions. The simultaneous execution of DBMS_AUDIT_MGMT.INIT_CLEANUP
or DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_LOCATION with SA_
SYSDBA.CREATE_POLICY or SA_SYSDBA.DROP_POLICY can cause the conflict.
Action: Wait for the completion of the conflicting SA_SYSDBA procedure and try
executing the DBMS_AUDIT_MGMT API again.
ORA-46276: DBMS_AUDIT_MGMT operation on unified audit trail failed
Cause: Audit records were not generated in the unified audit trail.
Action: Generate audit records in the unified audit trail and retry the operation.
ORA-46277: Conflicting operation on unified audit trail
Cause: Unified audit trail is being operated by more than one DBMS_AUDIT_
MGMT API from different sessions. The simultaneous execution of the following
API with one another and with itself can cause the conflict: FLUSH_UNIFIED_
AUDIT_TRAIL, LOAD_UNIFIED_AUDIT_FILES, CLEAN_AUDIT_TRAIL, and
SET_AUDIT_TRAIL_LOCATION.
Action: Wait until the execution of one of the API's complete and try executing the
API again.
ORA-46278: Conflicting operation using DBMS_AUDIT_MGMT routines
ORA-46000 to ORA-46900 26-15
Cause: One of the following API's was concurrently executed with itself or with
another API in separate sessions causing a conflict:
- SET_LAST_ARCHIVE_TIMESTAMP
- CLEAR_LAST_ARCHIVE_TIMESTAMP
- CLEAN_AUDIT_TRAIL
- SET_AUDIT_TRAIL_PROPERTY
- CLEAR_AUDIT_TRAIL_PROPERTY.
Action: Wait until the execution of one of the API's completes and try executing
the API again.
ORA-46340: Command cannot have both BY and IN SESSION
clauses together
Cause: BY clause was supplied with IN SESSION
clause in the command.
Action: Use either BY or IN SESSION clause.
ORA-46341: ALL STATEMENTS option cannot be supplied with BY SESSION
clause
Cause: An attempt was made to use ALL STATEMENTS audit option with BY
SESSION clause. ALL STATEMENTS audit option can be configured with BY
ACCESS only.
Action: Specify BY ACCESS instead of BY SESSION.
ORA-46342: NOAUDIT command cannot be executed with IN SESSION clause
Cause: An attempt was made to use IN SESSION clause in
NOAUDIT command.
Action: None
ORA-46343: Cannot drop AUDSYS user
Cause: An attempt was made to drop the AUDSYS user that hosts the audit trail.
Action: None
ORA-46350: Audit policy string already applied with the BY clause.
Cause: An attempt was made to apply audit policy with the EXCEPT clause
which was already applied with the BY clause.
Action: Remove audit policy using the NOAUDIT command.
ORA-46351: Audit policy string already applied with the EXCEPT clause.
Cause: An attempt was made to apply audit policy with the BY clause which was
already applied with the EXCEPT clause.
Action: Remove audit policy using the NOAUDIT command.
ORA-46352: NOAUDIT command with the EXCEPT clause is not allowed.
Cause: An attempt was made to remove audit policy using NOAUDIT command
with the EXCEPT clause.
Action: Remove audit policy selectively using NOAUDIT command with the BY
clause.
ORA-46353: missing or invalid audit policy name.
Cause: A valid audit policy name was expected.
26-16 Oracle Database Error Messages
Action: Specify a valid audit policy name.
ORA-46354: missing or invalid audit context or attribute name.
Cause: A valid context or attribute name was expected.
Action: Specify a valid context attribute name.
ORA-46355: missing or invalid privilege audit option.
Cause: Creating or altering the audit policy was attempted with an invalid system
privilege audit option.
Action: Use a valid system privilege audit option.
ORA-46356: missing or invalid action audit option.
Cause: Creating or altering the audit policy was attempted with an invalid action
audit option.
Action: Use a valid action audit option.
ORA-46357: Audit policy string not found.
Cause: The specified audit policy object did not exist in the database.
Action: Use the correct audit policy name and try again.
ORA-46358: Audit policy string already exists.
Cause: The specified audit policy object already existed in the database.
Action: Use a different name and try again.
ORA-46359: Invalid auditing option for string.
Cause: Creating or altering the audit policy was attempted with an invalid audit
option for the object.
Action: Use a valid audit option for the object.
ORA-46360: Same auditing option cannot be both added and dropped in audit
policy.
Cause: Altering the audit policy was attempted for adding and dropping the
same auditing option in the audit policy.
Action: Choose either to add or drop the audit option.
ORA-46361: Audit policy cannot be dropped as it is currently enabled.
Cause: An attempt was made to drop the audit policy which is currently enabled.
Action: Disable the audit policy before dropping.
ORA-46362: Could not translate variable ORACLE_BASE.
Cause: An attempt to obtain the value for ORACLE_BASE failed.
Action: Make sure the variable is set.
ORA-46363: Audit directory 'string' not found.
Cause: Could not find the specified audit directory.
Action: Make sure the audit directory is created.
ORA-46364: Audit directory 'string' could not be created.
Cause: Could not create the specified audit directory.
Action: Make sure the Oracle process has permissions to create the audit
directory.
ORA-46000 to ORA-46900 26-17
ORA-46365: Audit file 'string' could not be created.
Cause: Could not create the specified audit file.
Action: Make sure the Oracle process has permissions to create the audit files in
the audit directory.
ORA-46366: File 'string' is not a recognized Oracle audit file.
Cause: The file found in Oracle audit directory was not a valid Oracle audit file.
Action: Remove the file from the audit directory and try the action again.
ORA-46367: Database is not opened for write; cannot complete operation.
Cause: An operation requiring the database to be open in read/write mode was
attempted.
Action: Open the database in read/write mode.
ORA-46368: Audit policy does not have a simple rule condition.
Cause: Creating or altering the audit policy was attempted with a complex audit
condition.
Action: Use a simple rule expression for audit policy condition.
ORA-46369: An error occurred while evaluating audit policy condition.
Cause: Check the error stack for detailed error information.
Action: Fix the errors in the error stack and retry the operation.
ORA-46370: cannot connect as AUDSYS user
Cause: An attempt was made to connect to the database as AUDSYS user.
Action: Do not connect to the database as AUDSYS user.
ORA-46372: audit file 'string' not found
Cause: An operation was attempted on the audit file which was not available in
the audit directory.
Action: Make sure the file exists in the $ORACLE_BASE/audit/$ORACLE_SID
directory.
ORA-46373: Audit policy 'string' must have at least one audit option.
Cause: An attempt was made to create, alter or enable the empty audit policy.
Action: Use at least one audit option in the audit policy.
ORA-46374: error during AUDIT or NOAUDIT of audit policy in an Oracle RAC
enabled database
Cause: The operation could not be completed on one or more Oracle RAC
instances.
Action: Check the trace file for more information. Ensure every instance in Oracle
RAC is operational and retry the operation.
ORA-46376: FGA policy owner 'string' is not available
Cause: An attempt to import Fine-Grained Audit (FGA) policy failed because the
specified FGA policy owner has not been imported.
Action: Perform the import of the specified user schema and retry the operation.
ORA-46377: Auditing cannot be configured on the specified system privilege.
Cause: An attempt was made to configure auditing on the system privilege which
is not supported by the audit facility.
26-18 Oracle Database Error Messages
Action: None
ORA-46378: Cannot use bind variable in VERSIONS clause when the object has
FGA policy defined on it.
Cause: The object being accessed had a fine-grained audit (FGA) policy defined
on it and the VERSIONS clause contained a bind variable.
Action: Rewrite the query without the use of a bind variable in the VERSIONS
clause.
ORA-46379: generation of audit session ID failed with error 'number'
Cause: An error was encountered while generating the audit session ID.
Action: Retry the operation and, if the error persists, contact Oracle Support
Services.
ORA-46500: User is not a common user.
Cause: An attempt was made to apply the common audit configuration to a local
user. Common audit configuration can be applied only to common users.
Action: Specify a common user.
ORA-46501: Object is not a common object.
Cause: Object audit option for the common audit policy was specified on a local
object. A common audit policy can have object audit options on common objects
only.
Action: Specify a common object.
ORA-46503: not connected to a pluggable database
Cause: An attempt was made to create a local audit policy or configuration while
not connected to a pluggable database. Local audit policy or configuration can be
created only when connected to a pluggable database.
Action: Connect or switch session to a pluggable database to create local audit
policy or configuration.
ORA-46504: AUDIT command cannot specify ON