ORA-43750 to ORA-45928

92 ORA-43750 to ORA-45928

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-43817: indexes on ROWID not allowed: Cause: An attempt was made to create an index that refers to the ROWID pseudo-column, either directly or in an expression.; Action: Do not use ROWID to define an index on a table.
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-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.; 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-43907: This argument must be a literal or bind variable.: Cause: An attempt was made to provide an argument that was not a literal or bind variable.; Action: Provide an argument that is either a literal or bind variable.
ORA-43908: invalid output data type: Cause: An invalid output data type was provided. The valid output data types for VALIDATE_CONVERSION operator and the operators supporting DEFAULT ON CONVERSION ERROR syntax are: NUMBER, BINARY_FLOAT, BINARY_DOUBLE, DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL DAY TO SECOND, INTERVAL YEAR TO MONTH.; Action: Provide a valid output data type.
ORA-43909: invalid input data type: Cause: An invalid input data type was provided for Validate_Conversion operator. For the NUMBER, BINARY_FLOAT and BINARY_DOUBLE output data types, the input data types can be: - NUMBER - BINARY_FLOAT - BINARY_DOUBLE - CHAR - VARCHAR2 - NCHAR - NVARCHAR2 For the DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL DAY TO SECOND, and INTERVAL YEAR TO MONTH output data types, the input data types can be: - CHAR - VARCHAR2 - NCHAR - NVARCHAR2; Action: Provide a valid input data type.
ORA-43910: precision is not supported by Validate_Conversion operator: Cause: Precision was provided for the following data types: NUMBER, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND.; Action: Do not specify precision for following data types: NUMBER, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND.
ORA-43911: cannot specify collation for non-character columns: Cause: COLLATE was specified for a non-character column.; Action: Remove the COLLATE keyword.
ORA-43912: invalid collation specified for a CLOB or NCLOB value: Cause: A character LOB column or expression was declared as having a collation other than USING_NLS_COMP or the determined collation for a collation-sensitive operator or function operating on character LOB values was not USING_NLS_COMP. Character LOB values support only the USING_NLS_COMP collation.; Action: Correct the collation declarations to make sure the USING_NLS_COMP collation is applied to the character LOB values.
ORA-43913: unable to derive collation for the result: conflicting collations: Cause: Arguments to the operator or function (operation) that have the lowest coercibility level and are relevant for derivation of the collation for the result of this operation had conflicting collations.; Action: Check the collation derivation rules in the Oracle Database documentation and apply the COLLATE operator as appropriate to remove the existing conflict.
ORA-43914: unable to determine collation: arguments have undefined collation: Cause: Arguments to the operator, function, or condition (operation) that are relevant for determining the collation to be used by this operation had undefined collations.; Action: Check the collation determination rules in the Oracle Database documentation and apply the COLLATE operator as appropriate to assign a collation explicitly.
ORA-43915: unable to determine collation: arguments have conflicting collations: Cause: Arguments to the operator, function, or condition (operation) that have the lowest coercibility level and are relevant for determining the collation to be used by this operation had different collations.; Action: Check the collation determination rules in the Oracle Database documentation and apply the COLLATE operator as appropriate to remove the existing conflict.
ORA-43916: unable to determine collation for the column: Cause: An attempt was made to create a virtual character column in a table, a character column in a table based on a query (CREATE TABLE AS SELECT), or a character column in the key of a functional index. The expression on which the column definition was based did not have a derived collation to be used for the column, because of a collation conflict in one of its operators. In case of a virtual column, no collation was provided for the column through the data type declaration, either.; Action: Check the collation derivation rules in the Oracle Database documentation and apply the COLLATE operator in the defining expression as appropriate to resolve collation conflicts. If defining a virtual column, alternatively, specify a data type for the column to let the column inherit the collation from the table default, or specify the collation explicitly with the data type.
ORA-43917: invalid collation for a primary key column of the index-organized table: Cause: An attempt was made to specify an invalid collation for the primary key column of an index-organized table.; Action: Use one of the supported collations for the primary key column of the index-organized table: BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, or USING_NLS_SORT_VAR1_CS.
ORA-43918: This argument must be a literal: Cause: An attempt was made to provide an argument that was not a literal.; Action: Provide a literal argument.
ORA-43919: Nested aggregates are not supported for pivot operation.: Cause: Nested aggregates were specified in the pivot operator. This operation is not supported.; Action: Remove the nested aggregates from the pivot operation.
ORA-43920: DEFAULT ON NULL is not supported for object type or REF columns: Cause: DEFAULT ON NULL was specified on a object type or REF column. These types are not supported.; Action: Remove the ON NULL keyword for this column.
ORA-43921: invalid collation for cluster column: Cause: An attempt was made to create an index cluster in which one of the key columns had an unsupported declared collation or an attempt was made to create a hash cluster in which a key column with SORT clause had an unsupported declared collation. Only the collations BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS are supported for character columns in index clusters and for sorted character columns of hash clusters.; Action: Use one of the supported collations for the offending column.
ORA-43922: Collation of the column cannot be modified.: Cause: An attempt was made to modify the declared collation of a column that either: o belonged to a foreign key o belonged to a primary or unique key and that key was referenced by some foreign key o corresponded to a cluster key column o was referenced by a defining expression of a virtual column o was referenced by a defining expression of a functional index o corresponded to an attribute of a user-defined type or an object table o belonged to the container table of a materialized view o was referenced by a join condition of a bitmap join index The declared collation of such columns cannot be modified.; Action: Use one of the following as appropriate: o Drop the offending constraint, virtual column, or index, modify the collation of the column, and re-create the dropped element. o If possible, modify the type attribute instead of the column. o If possible, modify the derived collation of the corresponding materialized view column (for example, with the COLLATE operator) and re-create the materialized view to re-create its container table with the new column collation. o Save the tables of a cluster, re-create the cluster using the new collation, and restore the saved tables into the cluster.
ORA-43923: The column cannot be modified to the specified collation.: Cause: An attempt was made to modify the declared collation of a column that belonged to a primary or unique key, or a standard index key, or a partitioning key, and the new collation was from a different group than the old collation, where the groups are defined as follows: Group 1: BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS Group 2: BINARY_CI, USING_NLS_SORT_CI, and USING_NLS_SORT_VAR1_CI Group 3: BINARY_AI, USING_NLS_SORT_AI, and USING_NLS_SORT_VAR1_AI; Action: When modifying the column collation, specify a new collation that is in the same group as the current column collation. If there is no current collation, because you changed the column data type at the same time and the old data type is not a character data type, then select a collation from Group 1 as the new collation.
ORA-43924: unable to modify collation of an Oracle-maintained database object: Cause: An attempt was made to modify the collation of an Oracle-maintained database object. Modifications of Oracle-maintained database objects are generally not permitted.; Action: Do not modify Oracle-maintained database objects unless explicitly instructed to do so by Oracle Support Services.
ORA-43925: A character column in the index definition has an unsupported collation.: Cause: An attempt was made to create a bitmap join index or a domain index with a key or join condition that contained a character column with a declared collation other than BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, or USING_NLS_SORT_VAR1_CS. Only these listed collations are supported by this type of the index.; Action: Use one of the supported collations for the key column or join condition.
ORA-43926: Cannot use the specified collation with some of the dependent objects.: Cause: An attempt was made to change the collation of a character column to a collation that is not supported in a key of a bitmap join index, a domain index key to which the column belongs. Only the collations BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS are supported in these keys.; Action: Use one of the supported collations for the key column.
ORA-43927: Cannot specify default collation for object tables.: Cause: An attempt was made to explicitly state the default collation setting for an object table. However, default collations do not apply to object tables because all columns of an object table inherit collations from the attributes of the base type of the table.; Action: The operation is not allowed.
ORA-43928: Conversion error handling is not allowed here.: Cause: An attempt was made to use the default value, in case of a conversion failure, by specifying the DEFAULT argument ON CONVERSION ERROR statement to a conversion operator. This feature is not allowed for current operation.; Action: Remove DEFAULT argument ON CONVERSION ERROR from the conversion operator and try again.
ORA-43929: Collation cannot be specified if parameter MAX_STRING_SIZE=STANDARD is set.: Cause: The COLLATE or DEFAULT COLLATION clause was specified in a DDL statement or the DEFAULT_COLLATION parameter was specified in an ALTER SESSION statement, but the value of the initialization parameter MAX_STRING_SIZE was STANDARD. The data-bound collation feature is disabled if the value of this parameter is STANDARD.; Action: Set MAX_STRING_SIZE to EXTENDED by following the procedure documented in the Oracle Database Reference.
ORA-43930: A query issued from a pre-12.2 database references a column with an unsupported collation.: Cause: A table or view column with a declared collation other than USING_NLS_COMP was referenced in a distributed query that originated in an Oracle Database with the release number lower than 12.2. Such references are not allowed.; Action: In the remote database that reported this error, create a view corresponding to the subquery that was executed in that database and make sure that all columns of this view have the collation USING_NLS_COMP. Use the COLLATE operator if necessary. In the original query, replace the subquery with a reference to the view.
ORA-43931: DEFAULT COLLATION may not be combined with other operations: Cause: An ALTER TABLE statement attempted to combine DEFAULT COLLATION with some other operation, which is not allowed.; Action: Ensure that DEFAULT COLLATION is the only operation specified in an ALTER TABLE statement.
ORA-43932: DROP IDENTITY cannot be combined with other operations: Cause: An ALTER TABLE statement attempted to combine DROP IDENTITY with some other operation, which is not allowed.; Action: Ensure that DROP IDENTITY is the only operation specified in an ALTER TABLE statement.
ORA-43933: Collation must be specified.: Cause: Collation was not specified in a context where it was required.; Action: Specify the required collation.
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 SQL name.; Action: Check the DBMS_ASSERT specification to verify that the parameter string is a valid SQL name.
ORA-44004: invalid qualified SQL name: Cause: The input parameter string was not a valid qualified SQL name.; Action: Check the DBMS_ASSERT specification to verify that the parameter string is a valid qualified SQL name.
ORA-44021: DBMS_SESSION.SET_CURRENT_SCHEMA_DEFERRED failed due to change of PDB.: Cause: Set schema failed because an attempt was made to change the pluggable database (PDB) before the set schema took effect.; Action: Do not change the PDB before the set schema takes effect.
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-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-44103: Materialized view has a circular dependency and cannot be validated.: Cause: A materialized view with a circular dependency was encountered by UTL_RECOMP and could not be validated.; Action: Drop and re-create the materialized view to remove the circular dependency.
ORA-44203: timeout waiting for lock on cursor: Cause: A timeout occurred 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-44206: cursor exceeded parse time limit: Cause: The cursor consumed too much elapsed time during parse and was aborted to avoid blocking other sessions.; Action: Tune the SQL statement or increase the parse time limit.
ORA-44301: NULL service name is not permitted: Cause: The service name argument was found to be NULL.; Action: Provide a non-NULL service name.
ORA-44302: NULL network name is not permitted: Cause: The network name argument was found to be NULL.; Action: Provide a non-NULL network name.
ORA-44303: service name exists: Cause: This service name was already in existence.; Action: Provide a new unique service name.
ORA-44304: service string does not exist: Cause: The specified service was not in existence.; Action: Provide a valid service name.
ORA-44305: service string is running: Cause: The specified service was running.; Action: This message is informational only.
ORA-44306: service name exceeds maximum length of string: Cause: The service name was too long.; Action: Use a shorter service name.
ORA-44307: network name too long: Cause: The network name, excluding the domain, was too long.; Action: Use a shorter network name.
ORA-44310: maximum number of services exceeded: Cause: The maximum number of services has been reached.; Action: None
ORA-44311: service string not running: Cause: The specified service was not running.; Action: This message is informational only.
ORA-44312: database closed: Cause: The database was closed.; Action: Open the database and retry the operation.
ORA-44313: instance name invalid: Cause: The instance name argument was not valid.; Action: Provide a valid instance name.
ORA-44314: network name already exists: Cause: The network name was already in existence.; Action: Use an alternate network name.
ORA-44315: all service attributes null: Cause: All attributes specified were null.; Action: At least one attribute must be non-null.
ORA-44316: invalid argument: Cause: Invalid argument supplied.; Action: Supply a valid argument.
ORA-44317: database open read-only: Cause: The database is open read-only.; Action: Close the database and reopen it read/write before trying again.
ORA-44318: exceeded maximum SERVICE_NAMES length: Cause: The total length of all running service network names exceeded the maximum allowable length.; Action: Stop another service to start this one.
ORA-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 count 'string' to string option: Cause: The given count was a nonpositive number.; Action: Provide a positive count number.
ORA-44324: no count 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 symbol argument to string option: Cause: symbol argument to -[un]trace option was missing.; Action: Provide symbol argument to -[un]trace option.
ORA-44327: no filename argument to string option: Cause: filename argument to the option was missing.; Action: Provide filename 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-44329: length of full path name too long: Cause: The full path name provided was too long.; Action: Use a shorter directory path, file name or both.
ORA-44403: Change user id operation failed due to invalid flag parameter.: Cause: Mutually exclusive values were specified for the flag parameter.; Action: Internal error. Contact Oracle Support Services.
ORA-44404: Oracle client version 10.2 requires Oracle server version 10.2 or higher.: Cause: The user name could not be changed for an Oracle client with version 10.2 or higher when connected to an Oracle server version lower than 10.2.; Action: Use an Oracle server with the same version as the client, and retry the operation.
ORA-44411: START_DATE cannot be later than END_DATE for all ACEs: Cause: The END_DATE was earlier than the START_DATE in one of the access control entries (ACEs) in this access control list (ACL).; Action: Set the END_DATE to be later than or the same as the START_DATE in each of the ACEs in this ACL.
ORA-44412: Cyclic ACL inheritance is not allowed.: Cause: A cycle was formed by the access control list (ACL) inheritance.; Action: Check the ACL inheritance and break the cycle by removing some of the ACL inheritance.
ORA-44413: Security class of parent ACL must be an ancestor of security class of child ACL.: Cause: The security class of the parent access control list (ACL) was not an ancestor of the security class of the child ACL.; Action: Change the security class of the parent ACL to be an ancestor of the security class of the child ACL.
ORA-44414: Invalid ACL: Parent ACL 'string' does not exist: Cause: The path to the parent ACL was not a valid resource.; Action: Change the parent ACL of this resource or create the parent ACL at the specified location.
ORA-44415: undefined privileges: Cause: An undefined privilege was found in an access control entry (ACE) in the access control list (ACL).; Action: Ensure that the privilege is defined in the security class as specified in the ACL.
ORA-44416: invalid ACL: unresolved principal 'string': Cause: An unresolved principal was found in an access control entry (ACE) in the access control list (ACL).; Action: Ensure that the principal is a valid user or role in the system.
ORA-44417: invalid access control list ID (ACLID): Cause: The specified ACLID did not point to a valid access control list (ACL) document.; Action: Ensure that 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 not allowed for this column: Cause: An attempt was made to insert nonschema-based XML documents in a binary XML column that did not allow 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 or Object-Relational clause.: Cause: An attempt was made to use an XML schema registered for BINARY usage as part of a CLOB or Object-Relational clause.; Action: Specify a schema registered for CLOB or Object-Relational use. Otherwise, specify BINARY XML storage for the column.
ORA-44424: BINARY XML storage requires an XML schema registered for BINARY usage.: Cause: An attempt was made to specify BINARY XML storage using an XML schema that was not registered for BINARY.; Action: Specify a schema registered for BINARY usage. Otherwise, specify CLOB or Object-Relational storage for the 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-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-44608: Supplemental logging settings cannot be modified in Oracle Database Express Edition.: Cause: An attempt was made to modify supplemental logging settings using Oracle Database Express Edition.; Action: Upgrade to Oracle Database Standard Edition (SE) or Oracle Database Enterprise Edition (EE) to enable supplemental logging and logical replication.
ORA-44609: CONTINOUS_MINE is desupported for use with DBMS_LOGMNR.START_LOGMNR.: Cause: An attempt was made to use DBMS_LOGMNR.START_LOGMNR with CONTINOUS_MINE as an option.; Action: Reissue START_LOGMNR without the CONTINUOUS_MINE option specified.
ORA-44610: DBMS_LOGSTDBY extended data type support is desupported.: Cause: An attempt was made to use one of the DBMS_LOGSTDBY extended data type support procedures.; Action: DBMS_LOGSTDBY extended data type support is desupported and cannot be used.
ORA-44611: Only one LogMiner adhoc session is allowed in Oracle Cloud Autonomous Database.: Cause: A second LogMiner adhoc session is being attempted in Oracle Cloud Autonomous Database.; Action: Try again after the existing LogMiner adhoc session has ended.
ORA-44612: could not attach to LogMiner session because session is disabled: Cause: The LogMiner session was disabled because the metadata information was not available in the metadata tables.; Action: Ensure that the upgrade or downgrade has migrated all of the metadata information to the SYS or SYSTEM schema LogMiner tables and try again.
ORA-44700: Language 'string' is not a valid language for a translation: Cause: Invalid language.; Action: The language must conform to IETF RFC 3066.
ORA-44701: language not found for translation: Cause: The document had multiple translations and one of them did not have the xml:lang attribute.; Action: All translations must have the xml:lang attribute when multiple translations are present.
ORA-44702: Multiple translations found for language 'string': Cause: The document had multiple translations for a language.; Action: The document must contain only one translation per language for every translated element.
ORA-44703: Multiple source language translations found: Cause: The document had multiple source language translations.; Action: The document must contain only one source language translation for every translated element.
ORA-44704: XPath 'string' does not uniquely identify a translated element: Cause: The given XPath pointed to multiple translated elements.; Action: The given XPath must uniquely identify a translated element.
ORA-44705: Must have xdb:maxOccurs='1' for translated elements: Cause: The value of xdb:maxOccurs was not '1' for a translated element.; Action: The value of xdb:maxOccurs must be '1' for a translated element.
ORA-44706: Must have xsd:maxOccurs='unbounded' for translated elements: Cause: The value of xsd:maxOccurs was not 'unbounded' for a translated element.; Action: The value of xsd:maxOccurs must be 'unbounded' for a translated element.
ORA-44707: no source language translation found: Cause: The document had no source language translation for a translated element.; Action: The document must contain exactly one source language translation for each 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: XML Path Language (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-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 in XML Index: Cause: An attempt was made to drop the last group in the XML Index. The last group could not be dropped as the index required at least one group.; Action: Use DROP INDEX statement to drop the index.
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).: 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 groups: Cause: An attempt was made to add, modify, or drop columns of a table that is shared by other groups.; Action: Drop the group or groups with the shared table or tables 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 add, modify, or drop operation in an ALTER INDEX statement.: Cause: An attempt was made to have more than one add, modify, or drop column or group operation 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-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.; 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 operation cannot be completed.: Cause: The service was not imported successfully while plugging in the pluggable database or the service is defined in a different pluggable database.; Action: Connect to the correct pluggable database and re-execute the service operation.
ORA-44787: Service cannot be switched into.: Cause: The service did not exist in the new pluggable database or the service was not started in the pluggable database.; Action: Use a valid service name for the pluggable database or start the service in the pluggable database first.
ORA-44789: Service cannot be switched into.: Cause: One of the verification checks failed.; Action: Check the previous error message.
ORA-44790: exceeded maximum GUID length: Cause: The total length of a globally unique identifier (GUID) exceeded 16 characters.; Action: Specify a GUID with the correct length.
ORA-44791: Drain timeout or stop option cannot be specified for a different database instance.: Cause: Drain timeout and stop option could not be used for remote operations.; Action: Connect to the correct database instance to use drain timeout or stop option.
ORA-44792: cannot initialize Oracle Call Interface (OCI) environment: Cause: There was not enough memory available.; Action: Configure the Oracle database with more memory.
ORA-44793: cannot stop internal services: Cause: The user tried to stop an internal service.; Action: None
ORA-44794: cannot create the specified service: Cause: Oracle Clusterware was configured but not running.; Action: Start Oracle Clusterware and try to create the service.
ORA-44795: service string is not a child service or string is not its parent service: Cause: The specified service was not a child service or it was not a child service of the specified parent service.; Action: Provide a valid child service.
ORA-44796: invalid goal attribute value for parent service string: Cause: An attempt was made to specify a goal attribute of SERVICE_TIME or THROUGHPUT for a parent service.; Action: If a child service is being created, modify the parent service goal attribute and re-create the child service. If a parent service is being modified, only NONE or SMART_CONN are valid goal attribute values.
ORA-44797: illegal operation attempted on child service string: Cause: An operation such as start, stop or modify was attempted on a child service.; Action: Some operations cannot be performed directly on a child service. Perform the operation on the parent service instead.
ORA-44798: maximum number of child services exceeded for parent service string: Cause: The maximum number of child services for a parent service was exceeded.; Action: None
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.; 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: 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-44828: memory allocation failed: Cause: Memory allocation for the attempted operation failed.; Action: Retry the operation. Contact Oracle Support if the problem persists.
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 catalog.; Action: Ensure that the specified database name is correct and, if yes, delete and re-create the catalog.
ORA-44855: configuration name is not valid: Cause: The specified configuration name contained invalid characters or was too long.; Action: Provide a valid (or shorter) configuration 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: catalog does not exist: Cause: A catalog did not exist in the database.; Action: Validate the connect string and retry the operation.
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.: 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.
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: n/a
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.: 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 was unable to resolve the specified symbolic link.; Action: Check the definition of the symbolic link to ensure that it refers to a valid resource.
ORA-44902: failed to resolve symbolic link "string": Cause: The system was 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 path in document link.: Cause: The target path does not resolve to a valid resource.; Action: Check the target path validity.
ORA-44907: cannot delete resource with incoming hard document links: Cause: An attempt was made to delete a resource that had hard incoming document link targeting the resource.; Action: Query the DOCUMENT_LINKS view to see which resources have hard links to this resource, and change the document link in the source resource accordingly.
ORA-44908: Found a loop in XInclude elements while expanding string.: Cause: A loop in XInclude elements was detected in the document.; Action: Remove the loop in XInclude elements.
ORA-44909: HREF attribute is required within an XInclude element.: Cause: The HREF attribute was missing within XInclude element.; Action: Add the HREF attribute.
ORA-44910: XPointer is not supported within an XInclude element.: Cause: An Xpointer attribute was used within an XInclude element, and this is not supported.; 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: The XPath expression string is invalid or unsupported.: Cause: The specified XPath was either invalid or not supported in this context.; Action: Change or correct the XPath expression.
ORA-44913: error while processing XInclude string: Cause: There was an error while processing the specified XInclude.; Action: Ensure that the XInclude attributes are correct.
ORA-44914: schema XPointer exceeds maximum length: Cause: The XPointer was too long with the schema URL and element name.; Action: Use a shorter name.
ORA-44915: cannot rename virtual folders: Cause: Renaming virtual folders was not supported.; Action: Create a new virtual folder instead.
ORA-44916: Cannot recursively delete virtual folders.: Cause: Attempted to recursively delete virtual folders.; Action: Delete components of the virtual folder first.
ORA-44917: References cannot point to resources.: Cause: Attempted to set a REF to point to the resource table.; Action: Correct the reference to not point to the resource table.
ORA-44918: The source of a copy cannot be an ancestor of the destination.: Cause: The destination of a copy was an ancestor of the source.; Action: Correct the source and destination of the copy.
ORA-44919: cannot overwrite existing resource: Cause: An attempt was made to overwrite an existing resource without permission.; Action: Specify a new destination or allow overwrites.
ORA-44920: The source and destination of a copy or move cannot be the same.: Cause: A copy or move was attempted with the same source and destination.; Action: Use the correct source and destination.
ORA-44921: The XPath returns none or more than one node.: Cause: The XPath did not map to a single node.; Action: Specify a path that maps to a single node.
ORA-44922: The XPath expression must evaluate to a scalar type.: Cause: The XPath did not map to a scalar type.; Action: Specify a path that maps to a scalar type.
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-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: 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.; 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 initialization parameter was not set for a member.: Cause: The DB_UNIQUE_NAME initialization parameter was not set for a member.; Action: Set the member's DB_UNIQUE_NAME initialization parameter and retry the operation.
ORA-45420: return TNS service was not found: 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: 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: 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: A rollback 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.; Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views to identify the offending database and remove the database from the configuration.
ORA-45494: database is not in open read-only mode: Cause: An operation failed due to the discovery of a database which was not in open read-only mode.; Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views to identify the database. Open the database in read-only mode.
ORA-45495: capture is unusable due to not migrating on earlier rolling upgrade: Cause: An operation failed due to the discovery of a capture session that did not migrate across an earlier rolling upgrade before a second rolling upgrade was done.; Action: Re-create the capture.
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".: 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.; 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'.
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: Reconfigure the database to use an SPFILE and attempt the 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.; 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.
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 with system error string: 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.; 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.: 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-45564: pool "string" contains a sharded root configuration; only preferred_all services are allowed: Cause: An attempt was made to add non-uniform service to a pool that contains a sharded root.; Action: None
ORA-45565: pool "string" contains a sharded root configuration; databases cannot be added to this pool: Cause: An attempt was made to add a database to a pool that contains a sharded root.; Action: None
ORA-45566: pool "string" contains a sharded root configuration: Cause: An attempt was made to work with a generic pool that was not a sharded root.; Action: None
ORA-45567: pool "string" is not a shard: Cause: An attempt was made to work with a generic pool that was not a shard.; Action: None
ORA-45568: database link to catalog is invalid: Cause: An attempt to use a database link from a pool database to a catalog failed.; Action: Check the network connectivity and master global service manager (GSM) endpoint.
ORA-45570: The string is not empty and cannot be removed.: Cause: The shardspace or shardgroup was not empty and contained at least one shardgroup or shard.; Action: Delete all shards or shardgroups before calling the procedure again.
ORA-45572: Remote shard conversion job string failed with error: string: Cause: The remote scheduler job to convert a shard from seed has failed.; Action: Read the error and resolve the problem described, then restart the job using the "deploy" command in GDSCTL.
ORA-45573: shard open mode is string, it should be READ WRITE: Cause: The shard was opened in the incorrect mode for Oracle Data Guard broker setup.; Action: If the open mode was "MOUNTED", then check that the shard has been correctly converted from a shard seed. If the shard was already a converted primary shard, then open it in the correct mode and rerun "deploy" from GDSCTL.
ORA-45574: shard has role string, it should be PRIMARY: Cause: The shard did not have the correct role for Oracle Data Guard broker setup.; Action: Ensure the shard is placed in a shardgroup that will automatically assign the correct role to it.
ORA-45575: Deployment has terminated due to previous errors.: Cause: Due to previous errors deployment could not continue.; Action: Resolve the issues described in all of the displayed errors and rerun "deploy" from GDSCTL.
ORA-45576: Shard string requires conversion from seed, but the remote scheduler is not configured.: Cause: The remote scheduler agent is required to convert the shard from a seed, but it has not been configured.; Action: Configure the remote scheduler and rerun "\deploy" from GDSCTL.
ORA-45577: cannot convert standby shards to primary shard string because the DBID is unknown: Cause: A primary shard was added to the catalog but the DBID was not discovered, and none of the standby shards could be converted.; Action: Remove the primary shard from the catalog and re-add it so that the database identifier (DBID) can be discovered.
ORA-45578: No credential for scheduler jobs.: Cause: Credential could not be created or retrieved.; Action: Specify -osaccount and -ospassword in "add shard", or use "add credential" command to add credential.
ORA-45579: There are converted physical standby shards for intended primary seed shard string.: Cause: The primary shard was still an unconverted seed, but it had converted standby shards. Standby shards cannot be converted before their primary shard.; Action: Either remove the converted standby shards or remove the primary shard, convert it manually, and re-add it.
ORA-45580: invalid value specified for input parameter string: Cause: The specified parameter was set to an invalid value.; Action: Verify the parameter value and retry operation.
ORA-45581: cannot mix sharded and non-sharded pools in the same catalog: Cause: At attempt was made to create a sharded and a non-sharded database pool in the same catalog.; Action: Create a separate catalog for each database pool type.
ORA-45582: The chunk string was not found or has been moved to another shard.: Cause: The client application specified a chunk name associated with the current user call that was not found on the current shard.; Action: Invalidate the connection pool routing table for this shard.
ORA-45583: chunk string does not contain the specified key: Cause: The chunk, specified by the client application, was split or never contained the specified key.; Action: Invalidate the pool routing table for the given chunk. The client should ask the listener to route to the specified key.
ORA-45584: The shard object to be removed does not exist.: Cause: The shardspace or shardgroup that you intended to remove did not exist in catalog.; Action: Do not attempt to remove the shard object again.
ORA-45585: Chunk move failure: target shard is unavailable: "string": Cause: The chunk move failed. The source shard could not connect to the target.; Action: Check the availability of the target shard and network configuration.
ORA-45586: Chunk move failure: target shard is in invalid state: "string".: Cause: The chunk move failed. The target shard was improperly configured.; Action: Call the GDSCTL VALIDATE command for more details.
ORA-45587: Chunk move failure: target standby is unavailable; connection string: "string": Cause: The chunk move failed. The source shard could not connect to the target standby shard.; Action: Check the availability of the target standby shard and broker configuration.
ORA-45588: Chunk move failure: unable to read tablespace information "string": Cause: Shard metadata inconsistency was detected.; Action: Call the GDSCTL VALIDATE SHARD command for more details.
ORA-45589: Chunk move failure: DB_FILE_CREATE_DEST value is not valid: Cause: Shard configuration inconsistency was detected.; Action: Set the DB_FILE_CREATE_DEST initialization parameter to a valid existing folder.
ORA-45590: Chunk move failure: backup cannot be created for tablespace "string": Cause: Shard configuration inconsistency was detected.; Action: Set the DB_FILE_CREATE_DEST initialization parameter to a valid existing folder.
ORA-45591: Chunk move failure: data file copy error. Destination: "string": Cause: There was a database management system (DBMS) file transfer error.; Action: Check the alert log for details.
ORA-45592: Chunk move failure: RPC error on: "string": Cause: There was a database management system (DBMS) file transfer error.; Action: Check the alert log for details.
ORA-45593: Chunk move failure: file delete error on source shard: Cause: The backup file could not be deleted from the file system.; Action: Check the operating system log for details.
ORA-45594: Chunk move failure: cannot put chunk into read-only state: Cause: There was an internal error which prevented a chunk state change.; Action: Check the alert log for details.
ORA-45595: Chunk move failure: export metadata error: Cause: There was an internal error which prevented the metadata export.; Action: Check the alert log for details.
ORA-45596: cannot remove region because it contains a shardgroup: Cause: The region was not empty because it contained at least one shardgroup.; Action: Remove all shardgroups from the region and retry the operation.
ORA-45598: Shard string is in converted state string, it should be either "PRIMARY" or "PHYSICAL STANDBY".: Cause: The shard was in an invalid or unsupported state for use with sharding.; Action: Rebuild the shard using Oracle Database Configuration Assistant (DBCA) or reapply an RMAN backup to bring the shard to a supported state.
ORA-45599: Shard string is in converted state string, but does not have a valid DBID.: Cause: The discovered database identifier (DBID) for the shard was invalid, but the shard was already converted from a shard seed.; Action: Check the DBID for the shard and report this issue to Oracle Support Services.
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-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.
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 failure on one or more columns: Cause: Policy enforcement on one or more columns encountered errors.; Action: Check the alert log or trace files 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 given sensitive column type.; Action: Specify the valid combination of 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: Disabling protection failed during import of sensitive columns.: Cause: Importing the list of sensitive columns failed because there was a problem in disabling protection on the columns.; Action: Check the alert log or trace files for more details.
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 is no associated sensitive column(s) of sensitive column type string.: Cause: DBMS_TSDP_PROTECT.ENABLE_PROTECTION PL/SQL API is executed prior to associating sensitive columns to the sensitive column type.; Action: Specify a valid sensitive column for the sensitive column type using DBMS_TSDP_PROTECT.ASSOCIATE_POLICY PL/SQL API.
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.
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-45642: transparent sensitive data protection (TSDP) operation not supported: Cause: An attempt was made to perform the TSDP operation from inside the application install or patch begin-end block.; Action: Perform the TSDP operation outside the application install or patch begin-end block.
ORA-45643: specified column cannot be marked as sensitive.: Cause: An attempt was made to mark one of the virtual or hidden columns as sensitive.; Action: Retry the operation by removing the virtual or hidden 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 to the 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.; 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 restore a data file copy in instant restore mode. This is not supported.; Action: Do not restore a 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. A possible cause for this message is that the instant restore feature is disabled in this database.; Action: Check the other messages in the error stack, alert log, or trace file to see if there is a specific reason for this failure. If the situation cannot be resolved, then request a regular (not instant) restore.
ORA-45908: cannot create a control file record for data file number string: Cause: This data file was instantly restored. An attempt was made to create a record in the control file for the data file. Unless the database is mounted, this command cannot be completed.; Action: Mount the database and retry the command.
ORA-45909: restore, recover or block media recovery may be in progress: Cause: A backup or copy was attempted while restore, recover or block media recovery was in progress. This error should be preceded by another error indicating file access enqueue problem for a file specified in a backup, copy or restore operation.; Action: Let restore, recover or block media recovery finish before starting a backup or copy operation.
ORA-45910: cannot look up the rewrapped key for tablespace string: Cause: During transport, an encrypted tablespace could not find its rewrapped key as part of a Recovery Manager (RMAN) cross-platform command.; Action: Connect to the respective pluggable database and check if the master table is created.
ORA-45911: cannot restore as encrypted/decrypted on database with compatibility below 12.2: Cause: Restore with encryption and decryption is only supported on 12.2 compatible databases and above.; Action: Upgrade database or restore without encryption/decryption.
ORA-45912: cannot restore as encrypted or decrypted from backup piece with pre-12.2 compatiblity: Cause: An attempt to restore with encryption or decryption failed because backups must be Oracle Database 12c Release 2 compatible.; Action: Create a backup of the Oracle Database 12c Release 2 database or restore without encryption or decryption.
ORA-45913: cannot backup file string because it belongs to dropped PDB: Cause: The indicated file was not included in the backup because it belongs to a dropped pluggable database (PDB).; Action: Do not request to backup dropped PDB files.
ORA-45914: cannot backup a mounted control file of type backup: Cause: An attempt was made to backup a control file when the mounted control file at that time was a backup control file. This is not allowed.; Action: Mount a current control file and retry the operation.
ORA-45915: physical block size string does not match logical block size string: Cause: The physical block size and logical block size of the backup piece did not match.; Action: Ensure that the physical block size size and logical block size match before copying the backup piece.
ORA-45916: must use backup control file that has dropped PDB with GUID string: Cause: Some restored files belonged to the dropped pluggable database (PDB) with respect to the current control file.; Action: Restore and mount a backup control file that has the dropped PDB.
ORA-45917: nonexistent backup piece or data file "string" in the current container: Cause: An attempt was made to access a backup piece or data file. This attempt failed because the specified file is not known to the current container.; Action: Specify the name of an existing file that can be accessed by the current container. Check the relevant V$ table for a list of possible files.
ORA-45918: data file string is offline: incremental start SCN is too recent: Cause: The incremental start system change number (SCN) which was specified when starting an incremental data file backup was greater than the data file checkpoint SCN, which could cause some blocks to be missed.; Action: Specify a smaller incremental start SCN.
ORA-45919: no key present in wallet: Cause: An attempt was made to restore a backup as encrypted. This attempt failed because the current wallet did not contain an encryption key with which to encrypt the data.; Action: Create an encryption key in the wallet and retry the command.
ORA-45920: multiple keys present in wallet: Cause: An attempt was made to restore a backup as encrypted. This attempt failed because the current wallet contained more than one encryption key.; Action: Specify with which key to encrypt by using the USING KEY clause of RESTORE AS ENCRYPT.
ORA-45922: backup operation interrupted by restoration or recovery of file string: Cause: A restoration, recovery, or block media recovery interrupted a backup or copy in progress. This error indicates that restoration or recovery of file is given preference over the backup operation.; Action: Let restoration, recovery, or block media recovery finish before starting a backup or copy operation.
ORA-45923: Archived log thread string sequence string does not exist.: Cause: An attempt was made to access the indicated archived log. This attempt failed because the specified file is not known to the backup step.; Action: Specify the name of an existing file that can be accessed by the database.
ORA-45924: Multi-section archived log backup requires COMPATIBLE string or higher.: Cause: An attempt was made to perform a multi-section archived log backup with a database compatibility that was not high enough.; Action: Raise the compatibility level and retry the operation.
ORA-45925: cannot obtain string enqueue for archived log thread string sequence string: Cause: The file access enqueue could not be obtained for a file specified in a backup, copy or restore operation.; Action: Wait until the conflicting operation is complete, then retry the copy or backup.
ORA-45926: failed to generate RMAN backup encryption key: string: Cause: RMAN failed to generate a typed key for backup encryption. Error code definitions as follows: 2 : key buffer is too small 5 : invalid owner type 7 : cannot find specified encryption key 9 : master key revoked or disabled; Action: Resolve the error or contact Oracle Support Services.
ORA-45927: PDB number with GUID string now has ID number and GUID string. RMAN cannot backup file string due to PDB change.: Cause: The indicated pluggable database (PDB) has changed since the start of the backup operation. RMAN can no longer back up the files associated with the PDB.; Action: Restart the backup.
ORA-45928: SBT Library callback invalid function value string: Cause: An unrecognized function code was supplied from the SBT library.; Action: The SBT library will determine if this is a fatal error or not. If this is a fatal error, the SBT will report the error with more detail.