Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 2 (11.1.2.3.0)

Part Number E22506-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

11 MDS-00001 to MDS-91023

MDS-00001: exception in Metadata Services layer
Cause: An exception occurred in the Metadata Services layer.
Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00002: unexpected internal error
Cause: An unexpected internal error occurred.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00003: error connecting to the database
Cause: A database connection to the metadata repository could not be established.
Action: Contact the database administrator or system administrator to get the problem resolved.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00005: unable to find XML element or text "{0}"
Cause: The XML element with the given local name or the text node containing the given data could not be located by traversing through the document while applying customizations to a metadata object. The internal in-memory MDocument structure may be corrupted.
Action: Retry the operation. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00008: Attribute "{0}" is not allowed for element {1} namespace {2} in metadata object {3}.
Cause: An attempt was made to add an attribute to an element that does not conform to the element"s schema definition.
Action: If the Bean API is being used, then determine if the beans need to be regenerated. Otherwise, inspect the element definition for valid attributes.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00010: DuplicateRefException. In document {0} there are multiple elements with the same ID {1}.
Cause: Either an element was being added with an ID that already existed within the document, or a preexisting document had multiple elements with the same ID.
Action: Change the ID of the elements so that there is no ID duplication.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00011: unable to create configuration object or MDSInstance due to invalid configuration information: {0}
Cause: The MDS configuration was invalid.
Action: Refer to the MDS specification and correct the configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00012: invalid value "{0}" for attribute {1} (type = "{2}") in metadata object {3}
Cause: The value provided for the named attribute was invalid. For example, this error could occur if a named JNDI connection name is incorrect.
Action: Provide a valid attribute value.

Level: 1

Type: ERROR

Impact: Data

MDS-00013: no metadata found for metadata object "{0}"
Cause: MDS was unable to locate the given metadata object.
Action: Confirm the name and location of the metadata object, its existence in the configured metadata stores, and that it is in an accessible namespace.

Level: 1

Type: ERROR

Impact: Data

MDS-00015: Translation ignored in document "{0}": element with localRef "{1}" not found
Cause: A translation could not be applied because the underlying element to be translated was not found.
Action: If the element is expected, check the base document and any customizations to locate it.

Level: 1

Type: ERROR

Impact: Data

MDS-00016: Ignoring customization for instruction type "{0}" in metadata object "{1}" for customization layer "{2}"/"{3}": not finding element with local reference "{4}"
Cause: A customization was not applied because the underlying element to be customized was not found.
Action: If the element is expected, examine the base document and any customizations to locate the element.

Level: 1

Type: ERROR

Impact: Data

MDS-00017: Customization instruction using local reference(s) : "{0}" is not upgrade safe.
Cause: The customization instruction contained a local reference that was not deemed safe for an upgrade operation.
Action: Ensure that the local reference used in the customization instruction would be safe during an upgrade operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00018: Fixed customization for instruction type "{0}" in metadata object "{1}" for customization layer "{2}"/"{3}": not able to find the referenced element with local reference "{4}", inserted the customized element at the best possible location.
Cause: A customization was fixed because the referenced element was not found.
Action: Correct the customized element's position if needed.

Level: 1

Type: ERROR

Impact: Data

MDS-00019: Customization document contains an invalid instruction "{0}".
Cause: A customization document that was being applied contained an unrecognized instruction.
Action: Retry the operation. If necessary, either remove the customization document, or edit it to correct or remove the offending instruction.

Level: 1

Type: ERROR

Impact: Data

MDS-00020: Layer value "{0}" contains an invalid character.
Cause: Using a layer value that has an invalid character.
Action: Layer value should conform to MDS naming standards.

Level: 1

Type: ERROR

Impact: Data

MDS-00029: Invalid namespace: The namespace "{0}" has not been registered with the MetadataManager.
Cause: An attempt was made to access a document in an unknown location or namespace.
Action: Ensure that the namespace reported is registered in the MDS configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00032: cannot parse the input file: {0}
Cause: An exception occurred while parsing the file.
Action: Record the accompanying error and contact the developers of the application.

Level: 1

Type: ERROR

Impact: Data

MDS-00033: cannot load the input file: {0}
Cause: An exception occurred while loading the file.
Action: Record the accompanying error and contact the developers of the application.

Level: 1

Type: ERROR

Impact: Files

MDS-00034: cannot write to the output file: {0}
Cause: An attempt to write to the output file failed.
Action: Record the accompanying error and contact the developers of the application.

Level: 1

Type: ERROR

Impact: Files

MDS-00035: cannot load the class: {0}.
Cause: The class file could not be loaded.
Action: Ensure the class is available on the classpath so that it can be loaded by the application.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00036: cannot instantiate the class: {0}
Cause: An exception occurred while instantiating a class.
Action: Record the accompanying error and contact the developers of the application.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00037: cannot access the class: {0}
Cause: An attempt was made to access an inaccessible class file.
Action: Record any accompanying errors and contact the developers of the application.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00039: error while attempting to parse the document {0} using SAX.
Cause: A SAX parsing exception occurred while trying to parse a document.
Action: Record the accompanying error and contact the developers of the application.

Level: 1

Type: ERROR

Impact: Data

MDS-00040: There are no namespaces registered.
Cause: The operation attempted requires at least one registered namespace.
Action: Correct the MDS configuration to include the required namespace schemas.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00041: invalid classpath entry "{0}"
Cause: An entry on the application's classpath did not exist or was invalid.
Action: Correct the application's classpath to remove the invalid entry.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00042: Classpath "{0}" does not contain any valid directories or jar files.
Cause: The application's classpath contained no valid entries.
Action: Correct the application's classpath.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00043: A name pattern mapping for path {0} already exists.
Cause: The MDS configuration had duplicate namespace mappings.
Action: The MDS configuration must be corrected to remove the duplicate namespace mappings.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00044: Metadata for MetadataObject with name {0} already exists in the configured store.
Cause: An attempt was made to create a new Metadata Object. However an object with the same MDSReference already existed.
Action: The name or location of one of the objects must be changed.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00047: Use the flushChanges method on the MDSSession to commit the changes.
Cause: Commit was disabled in the PTransaction that was being used.
Action: Use the flushChanges method on the MDSSession to commit the changes.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00054: The file to be loaded {0} does not exist.
Cause: An attempt was made to load a persistent document using a URL but the underlying document was not found in the store.
Action: Check that the document name is correct and that the store is correctly configured.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00058: Invalid Metadata Path: Metadata Path cannot be null.
Cause: The path used to create a FileMetadataStore was empty. It must point to a directory.
Action: Correct the metadata store definition in the application configuration to specify a metadata path.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00068: Unable to find a type definition for: namespace = {0}, local name = {1}, file location = {2}
Cause: A request was made to locate a definition that did not exist in the named schema.
Action: Ensure the document contains only elements which are defined in the schema for the indicated namespace.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00084: Parameter {0} is invalid.
Cause: The supplied parameter was not of the expected type.
Action: Ensure the parameter is of the expected type.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00085: Parameter {0} is missing.
Cause: The named parameter was not supplied.
Action: Ensure that the named parameter is supplied. If transferring documents ensure a parameter file name is supplied.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00089: Parameter {0} must have a value.
Cause: A required parameter was null.
Action: Ensure that the indicated parameter is not null when the method is called.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00090: Error in JNDI lookup operation on MDSInstance name {0}, JNDI name {1}: object found {2} is an instance of class {3} classloader {4}, expected an instance of class {5} classloader {6}.
Cause: An object of an unexpected type was found, and it was bound to the JNDI context as the MDSInstance.
Action: Make sure no user-written code is binding anything to the same JNDI name. If the error occurs again try restarting the application. If the error still occurs, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00091: Unable to customize {0}, empty or null value for tip customization layer {1}
Cause: The customization layer configured as the tip, has a null or empty value.
Action: Ensure that a valid value is supplied for the tip customization layer.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00092: DuplicateNodeException. The same bean instance {0} already exists in document {1}.
Cause: An element was being added that already exists as the same bean instance within the document.
Action: Either create a new bean instance or remove the duplicate before attempting to insert in the document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00093: List of values provided for customization layer {0} was empty or null.
Cause: The list of customization layer values was either empty or null.
Action: Ensure that a valid list of layer values for the customiizaton layer is provided.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00094: List of CustLayerUsage objects provided was empty or null.
Cause: The list of CustLayerUsage objects was either empty or null.
Action: Ensure that a valid list of CustLayerUsage objects is provided.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00095: The support to transfer customization documents based on the CustConfig and excluding customization documents of specific customization layers is not yet available.
Cause: CustOption is created to transfer customization documents based on the CustConfig and to exclude customization documents of specific customization layers which is not yet supported in MDS Transfer.
Action: Ensure CustOption is not created to use CustConfig and to exclude customization documents of specific sutomization layers.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00111: The value of the property {0} for the component {1} must be set to the default value.
Cause: The indicated component property did not have a default value.
Action: Ensure the component property is given a default value.

Level: 1

Type: ERROR

Impact: Data

MDS-00153: invalid value for indicator
Cause: The production of merged XML failed.
Action: Verify the validity of XML documents and any schemas. If necessary forward these on to Oracle Support Services with the exception message and stack trace.

Level: 1

Type: INCIDENT_ERROR

Impact: Data

MDS-00154: The ContentHandler {0} does not implement org.xml.sax.ext.LexicalHandler.
Cause: MergedXML was passed a ContentHandler that does not implement org.xml.sax.ext.LexicalHandler.
Action: Use a ContentHandler that implements org.xml.sax.ext.LexicalHandler.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00155: unable to create a JSP file for document {0}
Cause: Oracle MDS was unable to create a JSP source document.
Action: Examine the MDS base document, as well as any customizations and translations. If necessary, forward these to Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Files

MDS-00156: unable to create a JSP output directory {0}
Cause: MDS-JSP integration failed because a problem was encountered while creating a directory.
Action: Verify that you have permission to create this directory.

Level: 1

Type: ERROR

Impact: Files

MDS-00157: unable to write to JSP file {0}
Cause: MDS-JSP integration failed because a problem was encountered while trying to write to a file.
Action: Verify that you have permission to create this file.

Level: 1

Type: ERROR

Impact: Files

MDS-00158: invalid directory: {0}
Cause: MDS-JSP integration failed. An attempt was made to write to an invalid directory.
Action: Verify the value of the invalid directory.

Level: 1

Type: ERROR

Impact: Files

MDS-00159: Invalid value "{0}" for {1} attribute (type = "{2}") in document {4}.
Cause: An attempt was made to write an invalid value to an attribute.
Action: Double-check the value and attribute type.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00160: no local name has been specified for a resource
Cause: An attempt was made to create a resource without giving it a name.
Action: Verify that the resource that was created is given a local name.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00161: no local name has been specified
Cause: An attempt was made to create a resource without giving it a local name.
Action: Verify that the resource that was created is given a local name.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00162: invalid attribute value
Cause: An attempt was made to give to an invalid value to an attribute.
Action: Verify that the attribute has a valid value.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00163: property value missing from element
Cause: An element was missing a property value.
Action: Ensure that each parameter used to create the element has a property value.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00164: There is a concurrent "{1}" operation on the document "{0}".
Cause: The document on which modification was being attempted had been updated by another user after it was retrieved.
Action: Retrieve the document again.

Level: 1

Type: ERROR

Impact: Data

MDS-00165: metadata Object "{0}" has changed
Cause: The creation, updating, or renaming of a metadata object failed due to conflicting changes made by another user.
Action: Retrieve the document containing the metadata object again.

Level: 1

Type: ERROR

Impact: Data

MDS-00166: unable to locate the unique identifier, {0}:{1}, that has been configured for the element {2}
Cause: The element that required a unique identifier was created without one.
Action: Add a unique identifier attribute to the element.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00167: Invalid local name for mapping "{0}" - an empty string is not allowed.
Cause: A local name was given a null or empty value.
Action: Supply a valid local name.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00168: MDS object {0} is being used after it or its MDSInstance or PManager has been released.
Cause: An MDS object was used after it or its MDSInstance or PManager had been released
Action: Create a new MDSInstance and re-create the MDS object.

Level: 1

Type: ERROR

Impact: Session

MDS-00169: The MDS instance is not ready for use because metadata deployment is in progress (status is "{0}"). Deployment messages so far are: "{1}".
Cause: The MDS instance cannot be used until metadata deployment has finished.
Action: Try again later after metadata deployment has completed.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00170: The MDS instance is not usable because metadata deployment failed with status "{0}".
Cause: Metadata deployment failed with the given status.
Action: Please fix the error and redeploy the application's metadata using the importMAR operation on MDS Application Runtime MBean. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00171: Document "{0}" already has unsaved updates on another instance of this metadata object in this session.
Cause: An attempt was made to update metadata using more than one instance of the same metadata object at the same time in the same session.
Action: Save the changes on the metadata object that already has updates before attempting to update it via another metadata object, or make further modifications on the metadata object on which updates have already been made.

Level: 1

Type: ERROR

Impact: Data

MDS-00172: The value "{0}" of local unique attribute {1} on the {2} element that is being inserted or updated in document {3}, is already used by a sibling element.
Cause: An attempt was made to have two local unique attributes with the same value on elements that share the same parent.
Action: Use a different value for the local unique attribute on the element that is being inserted or updated.

Level: 1

Type: ERROR

Impact: Data

MDS-00173: Attribute {0} of element {1} in document {2} has a null value.
Cause: The value of the named attribute was null.
Action: Provide a non-null value for the attribute or remove the attribute.

Level: 1

Type: ERROR

Impact: Data

MDS-00500: No metadata store is configured to save the document {0}.
Cause: An attempt was made to save a document, when no writable store was configured.
Action: Provide a writable metadata store to save the document.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00501: Document {0} cannot be deleted because no metadata store is configured.
Cause: An attempt to delete a document failed because there was no writable store configured.
Action: To delete the document, provide a writable metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00503: The metadata path "{0}" does not contain any valid directories.
Cause: Either the metadata path was empty or directories on the metadata path did not exist.
Action: Ensure that the metadata path is not empty and that the directories on the metadata path exist.

Level: 1

Type: ERROR

Impact: Data

MDS-00504: failure to create document {0} because metadata store "{1}" is read-only
Cause: An attempt to create a document on a read-only metadata store failed.
Action: To create the document, provide a writable metadata store.

Level: 1

Type: ERROR

Impact: Data

MDS-00505: failure to save document {0} because metadata store "{1}" is read-only
Cause: An attempt to save a document to a read-only metadata store failed.
Action: To save the document, provide a writable metadata store.

Level: 1

Type: ERROR

Impact: Data

MDS-00506: failure to get child resources of package {0} because package does not exist in metadata store
Cause: Child resources for the package were not found because specified package did not exist in the metadata store.
Action: Verify that the package exists in the metadata store, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00507: failure to delete document {0} because metadata store "{1}" is read-only
Cause: An attempt to delete a document from a read-only metadata store failed.
Action: To delete the document, provide a writable metadata store and retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00508: There is no content to be read for {0}.
Cause: An attempt was made to read empty metadata.
Action: Verify that the metadata has valid content, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00509: failure to delete document {0} with file {1}
Cause: An error occurred while the document was being deleted.
Action: Verify that the document exists and then retry the operation, or provide a document that exists in the store.

Level: 1

Type: ERROR

Impact: Data

MDS-00510: failure to read document {0} because it is not found in the metadata path "{1}"
Cause: The document to be read was not found.
Action: Verify that the metadata path is correct and that the document exists in the metadata path.

Level: 1

Type: ERROR

Impact: Data

MDS-00511: failure to create document {0} at file {1}
Cause: An error occurred while creating the document in the file store.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Files

MDS-00512: failure to create document {0} because file {1} already exists
Cause: An attempt was made to create a file that already existed in the metadata store.
Action: Provide a different name for the file to be created, or delete the existing file first, and then retry the operation.

Level: 1

Type: ERROR

Impact: Files

MDS-00513: failure to create package {0} because directory {1} already exists
Cause: An attempt to create a package failed because a directory by the same name already existed.
Action: Provide a different name for the package to be created and retry the operation.

Level: 1

Type: ERROR

Impact: Files

MDS-00514: failure to save document {0} to file {1}
Cause: An error occurred while saving the document to a file.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Files

MDS-00515: failure to create document {0} in the metadata repository
Cause: An error occurred while the document was being created in the metadata repository.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00516: failure to create document {0} because it already exists in the metadata repository
Cause: An error occurred while the document was being created in the metadata repository because the document already existed.
Action: Provide a different name or delete the existing document first, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00517: failure to create package {0} because it already exists in the metadata repository
Cause: An error occurred while the package was being created in the metadata repository because the package already existed.
Action: Provide a different package name or delete the existing package first, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00518: failure to create package {0} in the metadata repository
Cause: An error occurred while the package was being created in the metadata repository.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00519: failure to delete document {0} from the metadata repository
Cause: An error occurred while the document was being deleted from the metadata repository.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00520: failure to read document {0} because it is not in the metadata repository
Cause: The document was not read because it did not exist in the metadata repository.
Action: Verify that the document name is correct and that it exists in the metadata repository, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00521: error while reading document {0} from metadata repository
Cause: An error occurred while the document was being read from the metadata repository.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00522: failure to save document {0} to the metadata repository
Cause: An error occurred while the document was being saved to the metadata repository.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00526: failure to generate SAX parsing events for document {0}
Cause: An error occurred while parsing the XML document.
Action: Verify that the XML document is well-formed. Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00531: failure to write to "{0}" because output to "{1}:" protocol is not supported
Cause: An attempt to write modified metadata to a URL failed because the protocol is not supported.
Action: Retry writing modified metadata to a supported protocol.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00533: Exception: {3} Attribute "{0}" with an invalid MDS reference "{1}" in document "{2}" is not stored as a typed dependency in the database repository.
Cause: An error occurred while adding a typed dependency from the specified attribute.
Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00534: Exception: {3} Subobject {0} in document {2} has invalid value "{1}" for unique identifier; typed dependencies from this subobject are not stored in the database repository.
Cause: An error occurred because the component had an invalid ID.
Action: Provide the correct ID value for the application metadata. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00535: cannot change TypeManager associated with a PManager after it is initialized
Cause: An attempt was made to associate TypeManager with PManager after it was initialized.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00536: cannot change FileTypeManager associated with a PManager after it is initialized
Cause: An attempt was made to associate FileTypeManager with PManager after it was initialized.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00537: unable to rename {0} to {1}
Cause: An error occurred during a rename operation.
Action: Retry the rename operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00538: failure to rename document {0} because metadata store "{1}" is read-only
Cause: An error occurred during rename operation because the metadata store was configured as read-only.
Action: To rename a document, provide a store that can be written to, that is not read-only.

Level: 1

Type: ERROR

Impact: Data

MDS-00539: A document can be renamed only within its source store. The new name {1} in this rename operation does not map to the same store as the old name {0}.
Cause: An error occurred during a rename operation. An invalid new name for the rename operation caused the renamed document to be stored in another metadata store.
Action: Provide a new, valid document name that maps to the same metadata store that contains the original document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00541: SAX events cannot be generated for non-XML document {0}.
Cause: An attempt was made to generate SAX events for non-XML documents.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00547: The read operation is not supported for packages from Web content from the servlet context.
Cause: A read operation was attempted for packages from Web content, which is not supported.
Action: The read operation is not supported, therefore no action is required.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00550: Updates across multiple stores are not allowed in the same transaction.
Cause: An attempt was made to perform updates across multiple stores in the same transaction.
Action: Verify that the document is being saved to the same store on which it exists.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00551: failure to delete package {0} because it is not empty
Cause: An attempt was made to delete a package that was not empty.
Action: Delete the contents of the package to be deleted first, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00552: failure to delete package {0} with directory {1}
Cause: An error occurred while deleting the directory for the package.
Action: Ensure no files from the directory are opened in other applications and retry the operation. Also, refer to the error messages in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Files

MDS-00554: Package {0} cannot be found in the specified store.
Cause: The requested operation was not completed because the package name that was supplied was invalid.
Action: Provide a valid package name and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00555: The partitionName {0} is invalid.
Cause: The requested operation was not completed because the partition name that was supplied was invalid.
Action: Provide a valid partition name and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00557: Resource {0} is already locked or is being modified.
Cause: An attempt was made to modify a document that was already being modified by another user.
Action: Retry modifying the document after the lock is released by the other users. Also, refer to the error messages in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Session

MDS-00558: The partitionName {0} is not available.
Cause: No partition with that name existed.
Action: Provide a partition name that exists.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00559: A partition with name {0} already exists.
Cause: The name provided for creating a new partition was already in use by another partition.
Action: Provide a different name for the new partition.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00560: The MDS repository is incompatible with the archive. The repository version is {0} whereas archive version is {1}.
Cause: The MDS repository was not compatible with the archive provided.
Action: Upgrade the target MDS repository or use a compatible archive for the operation.

Level: 1

Type: ERROR

Impact: Upgrade

MDS-00561: The create operation is not supported for metadata stores of type "{0}".
Cause: An attempt was made to create a new document or package in a read-only metadata store.
Action: Reconfigure the application to use a writable metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00562: The delete operation is not supported for metadata stores of type "{0}".
Cause: An attempt was made to delete a document from a read-only metadata store.
Action: Reconfigure the application to use a writable metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00563: The save operation is not supported for metadata stores of type "{0}".
Cause: An attempt was made to save a document to a read-only metadata store.
Action: Reconfigure the application to use a writable metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00564: GUID feature is not supported for metadata stores of type "{0}".
Cause: An attempt was made to get a document by GUID from a metadata store that does not support GUIDs.
Action: Reconfigure the application to use a metadata store that supports GUIDs, such as DBMetadataStore.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00565: The rename operation is not supported for metadata stores of type "{0}".
Cause: An attempt was made to rename a document or package in a read-only store.
Action: Reconfigure the application to use a writable metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00566: The DOM content is NULL for {0}.
Cause: DOM document content provided was null.
Action: Provide valid DOM content and retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00567: The metadata changes for document "{0}" cannot be written in the underlying store because read-only mode is enabled in the configuration.
Cause: An attempt to change metadata was made while changes were disabled for maintenance operations.
Action: Reconfigure the application to not specify read-only mode in the configuration and use a writable metadata store to persist metadata changes.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00568: MetadataStore initialization failure because "{0}" is invalid
Cause: The URL store mapping was invalid.
Action: Provide a valid URL store mapping.

Level: 1

Type: ERROR

Impact: Files

MDS-00569: unable to read document {0} from "{1}"
Cause: There was an error reading the document from the URL metadata store.
Action: Retry the operation. If the problem persists, verify that the URL metadata store exists.

Level: 1

Type: ERROR

Impact: Data

MDS-00570: The name or content exceeds the MDS repository schema size for {0}.
Cause: The metadata name or the content exceeded the schema size.
Action: Reduce the length of the metadata name or content, and then retry the operation. Refer to the documentation for the allowed sizes for names and content.

Level: 1

Type: ERROR

Impact: Data

MDS-00571: The bean content is NULL for {0}.
Cause: The bean content was null.
Action: Provide valid bean content, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00572: failure to get the ConnectionManager because the DBContext is null
Cause: The DBContext value is null. Also, using any MetadataStore, PManager, or MDSInstance that has already been released might lead to this error.
Action: Do not use any metadata store, PManager, or MDSInstance that is already released.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00573: The metadata store is already associated with a PManager.
Cause: The PConfig provided for creating the PManager or MDSInstance was already used by another PManager or MDSInstance.
Action: Provide a new PConfig when creating the PManager or MDSInstance.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00574: The document {0} does not exist in the configured metadata store.
Cause: The document being locked did not exist in the configured metadata store.
Action: Ensure that the document to be locked exists, and that the name of the document is correct.

Level: 1

Type: ERROR

Impact: Data

MDS-00575: failure to acquire write lock for {0}
Cause: An attempt to acquire a write lock for a document failed.
Action: Refer to the cause exception message in application logs for details on the actual cause of the failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00576: failure to process {0} because metadata store "{1}" is read-only
Cause: An attempt was made to modify metadata in a read-only metadata store.
Action: Provide a writable metadata store to allow modification of the document.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00577: Could not acquire read/write lock for {0} within the default waiting time interval
Cause: Read/Write lock could not be obtained for a file within the waiting time interval.
Action: Try the operation again after some time.

Level: 1

Type: ERROR

Impact: Files

MDS-00578: Failed to process document {0} due to a critical error writing to the repository
Cause: A critical error occurred while the metadata document was being written to the repository.
Action: Contact the application administrator with cause exception message details to resolve the repository error.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00579: The document {0} does not have version {1} in the repository.
Cause: Specified version does not exist for the document.
Action: Provide an existing version for the document.

Level: 1

Type: ERROR

Impact: Data

MDS-00580: operation failed for {0} because no metadata-store was defined in the configuration for metadata-store-usage {0}.
Cause: incomplete configuration, no metadata-store was defined for the metadata-store-usage
Action: Define the metadataStore for the empty metadata-store-usage.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00581: error deleting partition {0} in file repository {1}
Cause: The directory represented by the file repository or partition is read only.
Action: Verify that the metadata path to the repository and partition exist and are writable.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00582: The MetadataStore {0} is writable but does override getMetadataStoreCommunicator() method.
Cause: Configuration used a MetadataStore that was writable but not supporting MetadataStoreCommunicator interface.
Action: Override getMetadataStoreCommunicator() in the MetadataStore class to return an appropriate MetadataStoreCommunicator instance.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00583: Could not release read/write lock for {0} because the lock was not found.
Cause: Read/Write lock could not be released because it was already removed from the lock cache.
Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Files

MDS-00584: The MDS repository's database platform is different that of the archive. The repository's database platform is {1} whereas the archive's platform is {0}.
Cause: The MDS repository platform was not compatible with the archive provided.
Action: Use a platform compatible archive for the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00585: Failure to create deployment lineage because metadata store "{0}" is read-only
Cause: An attempt was made to create deployment lineage in a read-only metadata store. Deployment lineage in repository represents Application name and MAR module name.
Action: Configure a metadata store that supports deployment management, typically a DBMetadataStore.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00586: ArchiveMetadataStore is restrcited to be used with MDS Transfer operation only. Reading or writing files in ArchiveMetadataStore is not supported ouside of transfer.
Cause: An attempt was made to read or write files in ArchiveMetadataStore outside of transfer.
Action: ArchiveMetadataStore is not supported outside of transfer. Either use this ArchiveMetadataStore for MDS transfer operation or use some other MetadataStore to store your files.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00588: Cannot replace the original archive file {0} with the final archive file {1} because the final archive file could not be renamed to {0}.
Cause: The final archive file could not be renamed to the original archive file name.
Action: Look at the cause exception for more details and take corresponding actions.

Level: 1

Type: ERROR

Impact: Data

MDS-00589: Error occurred while creating the final archive file {0}.
Cause: Some exception occurred while creating the final archive.
Action: Look at the cause exception for more details and take corresponding actions.

Level: 1

Type: ERROR

Impact: Data

MDS-00590: Error occurred while opening or closing the input/output stream for archive file {0}.
Cause: Some exception occurred while opening or closing the inpu/output stream for archive file.
Action: Look at the cause exception for more details and take corresponding actions.

Level: 1

Type: ERROR

Impact: Data

MDS-00591: "{0}" operation is not supported in ArchiveMetadataStore.
Cause: An unsupported operation has been attempted in ArchiveMetadataStore.
Action: Look at the ArchiveMetadataStore javadoc for supported operations.

Level: 1

Type: ERROR

Impact: Data

MDS-00592: Error occurred while initializing FileMetadataStore connection for the temporary directory.
Cause: An error occurred while initializing the FileMetadataStore connection for the temporary directory.
Action: Look at the cause exception for more details and take corresponding actions.

Level: 1

Type: ERROR

Impact: Data

MDS-00593: Unable to read the file {0} from archive {1}.
Cause: Some I/O Exception occurred while reading the given file from archive.
Action: Look at the cause exception for more details and take corresponding actions.

Level: 1

Type: ERROR

Impact: Data

MDS-00594: Unable to write the file {0} to archive {1}.
Cause: Some I/O Exception occurred while writing the given file to archive.
Action: Look at the cause exception for more details and take corresponding actions.

Level: 1

Type: ERROR

Impact: Data

MDS-00595: The parent directory {0} given in archive file path does not exist. Cannot create ArchiveMetadataStore for the archive file {1}.
Cause: The parent directory mentioned in archive file path does not exist.
Action: Provide valid parent directory in archive file path to create ArchiveMetadataStore.

Level: 1

Type: ERROR

Impact: Data

MDS-00596: Failure to read document {0} because it is not found in "{1}"
Cause: The document to be read was not found.
Action: Verify that the document exists in the ArchiveMetadataStore before reading the document.

Level: 1

Type: ERROR

Impact: Data

MDS-00597: Failure to open the archive file {0}. Cannot create ArchiveMetadataStore for the archive file {0}.
Cause: Could not open the given archive file.
Action: Try creating ArchiveMetadata store with a valid archive file.

Level: 1

Type: ERROR

Impact: Data

MDS-00598: Cannot create an intermediary archive during export to the archive file {0}.
Cause: Either the intermediary archive file could not be created in the default temporary-file directory or an I/O error occured.
Action: Look at the cause exception for more details and take action accordingly.

Level: 1

Type: ERROR

Impact: Data

MDS-00599: Cannot obtain a connection to the Archive Metadata Store for archive file {0}.
Cause: There was a problem obtaining a connection to the Archive Metadata Store.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00601: The XLIFF document has invalid target language {0}.
Cause: The target language specified was either null or empty.
Action: Specify a valid target language and retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00703: The name {0} is not a valid name under package {1} because {2} resource not considered child of the package.
Cause: A specified child resource was not a child of the package.
Action: Specify a valid child resource name, and then retry the operation.

Level: 1

Type: ERROR

Impact: Data

MDS-00704: invalid value {0} for property {1} on component {2}
Cause: An invalid property value was provided.
Action: Provide a valid property value and retry.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00771: A component with {0} "{1}" already exists.
Cause: The specified component already existed.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00907: unable to save document "{0}" because either a document or package of the same name already exists
Cause: A document or package with the same name already existed in the repository, perhaps because it was just created by another user.
Action: Retry the operation. If necessary, choose another name for the object being saved.

Level: 1

Type: ERROR

Impact: Data

MDS-00908: unable to create package "{0}" because a document or package of the same name already exists
Cause: A document or package with the same name already existed in the repository, perhaps because it was just created by another user.
Action: Retry the operation. If necessary choose another name for the object being saved.

Level: 1

Type: ERROR

Impact: Data

MDS-00910: unable to save the document because of corrupt MDS database sequences or other internal errors.
Cause: The database sequence used for generating the unique document ID was corrupt or some other internal errors caused violation of unique constraints.
Action: Retry the operation after deploying metadata to another MDS database repository partition. If that still fails, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

MDS-00911: Document with name "{0}" and version {1} does not exist in the repository.
Cause: The document was not found in the MDS repository.
Action: Specify a correct name for the document and retry the operation. Check if the document is deleted by another user.

Level: 1

Type: ERROR

Impact: Data

MDS-00912: MDS repository is incompatible with the middle tier. Repository version "{0}" is older than minimum repository version "{1}" required.
Cause: The MDS repository was older than minimum version required by the middle tier.
Action: Upgrade the MDS repository to the required version.

Level: 1

Type: ERROR

Impact: Upgrade

MDS-00913: MDS repository is incompatible with the middle tier. MDS version "{0}" is older than minimum MDS version "{1}".
Cause: The MDS version was older than the minimum required version for using the MDS repository.
Action: Upgrade the MDS library to the required version.

Level: 1

Type: ERROR

Impact: Upgrade

MDS-00914: unable to save document "{0}" because either an already deleted document or package with conflicting name or type already exists
Cause: A document or package with the same name or a parent pacakge of incorrect type already existed in the repository as a deleted version.
Action: Delete the coflicting resource from repository or check if the new resource is invalid. If necessary, choose another name for the object being saved.

Level: 1

Type: ERROR

Impact: Data

MDS-00915: MDS repository is incompatible with the middle tier for dumping or restoring metadata.
Cause: The MDS repository was older than minimum version required by the middle tier to dump or restore metadata.
Action: Retry the operation after upgrading the MDS repository to newer version or use compatible middle tier to perform the operation.

Level: 1

Type: ERROR

Impact: Upgrade

MDS-00916: MetadataStore configured for {0} does not support deployment management.
Cause: The metadata store configured for the resource did not support deployment management.
Action: Deployment management is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00918: Connection details for the MDS repository are incomplete. The values for "{0}" are invalid
Cause: The MDS repository connection details were invalid or missing.
Action: Specify correct values for the MDS repository details in the configuration and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00919: Internal error: The database context for this repository appears to be corrupt.
Cause: The database context was invalid.
Action: Verify that the repository details are correct in the configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00922: The ConnectionManager "{0}" cannot be instantiated.
Cause: There was an error instantiating the ConnnectionManager class
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-00923: Unable to create sandbox "{0}"
Cause: An error occurred during creation of sandbox.
Action: Look in the error message log for the exact reason for the failure.

Level: 1

Type: ERROR

Impact: Data

MDS-00928: Invalid document reference, package "cust" should appear before package "trans" in the names of customization translation documents.
Cause: An internal MDS document (one in package mdssys) was found with an invalid name, or an attempt was made to create a name object with such an invalid name.
Action: Avoid using package or document names containing path element "mdssys" which is reserved for internal MDS use. If necessary, remove such invalid documents from the metadata store.

Level: 1

Type: ERROR

Impact: Data

MDS-00929: unable to look up name "{0}" in JNDI context
Cause: The implementation class to use for initial context was not found.
Action: Verify that environment properties are configured using system properties or application resources files.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00930: The JNDI location details for the registered datasource are incomplete.
Cause: JNDI location details were found to be incomplete.
Action: Provide complete JNDI location information in the configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00931: The database version is {0}.{1}, but MDS requires at least {2}.{3}.
Cause: The database version is older than the minimum database version required for hosting MDS repository.
Action: Upgrade the database to the minimum required version. Contact the database administrator for assistance.

Level: 1

Type: ERROR

Impact: Upgrade

MDS-00932: unknown database vendor {0}
Cause: The database vendor could not be identified.
Action: Verify that the MDS repository is hosted on supported database vendors.

Level: 1

Type: ERROR

Impact: Installation

MDS-00933: cannot create data source using URL "{0}"
Cause: An error occurred while creating the data source using the specified URL.
Action: Verify that the URL specified is correct and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-00934: XDB is not supported on database platform {0}.
Cause: An attempt was made to store XML metadata in a non-XDB database.
Action: Verify that the correct MDS repository is being used.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-00935: Unable to complete operation even after maximum connection retries ({0}).
Cause: An error occurred while performing operation.
Action: Ensure that the database is running. Retry the operation later.

Level: 1

Type: ERROR

Impact: High Availability

MDS-00936: Fast Connection Failover is not supported on the underlying database connection ({0}).
Cause: The underlying database connection did not support fast connection failover, and retry-connection was set to true in either the config file, or programmatically.
Action: Either stop and then restart the database connection and configure it to allow fast connection failover, or do not attempt to set retry-connection to true.

Level: 1

Type: ERROR

Impact: High Availability

MDS-00937: A local transaction operation like commit or rollback cannot be used in a global transaction on connection "{0}".
Cause: The database connection was configured for global transactions, but MDS was not configured to support global transactions.
Action: Reconfigure the database connection to use local transactions. Change "tx-level" attribute on the MDS datasource to "local".

Level: 1

Type: ERROR

Impact: Configuration

MDS-00938: Unable to get an ADF library class loader
Cause: MDS expects to retrieve a resource from an ADF library, but is unable to obtain an ADF library classloader.
Action: Consider whether the resource should be repackaged in an ADF library rather than an ordinary jar.

Level: 1

Type: ERROR

Impact: Data

MDS-01059: document with the name {0} missing in the source metadata store
Cause: The document to be transferred did not exist in the source metadata store.
Action: Verify that the document name is correct, and that it exists in the source metadata store.

Level: 1

Type: ERROR

Impact: Data

MDS-01061: Listener {0} cannot be instantiated.
Cause: The listener class did not exist.
Action: Verify that the name of the listener class is correct. Ensure that the class is available on the class path.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01104: finding no documents for processing that match the pattern provided
Cause: No documents were found on the source metadata store that matched the pattern provided, or that matched the document name.
Action: Provide another pattern or document name, or provide another metadata store in which to look for the documents.

Level: 1

Type: ERROR

Impact: Data

MDS-01105: invalid label {0}
Cause: The label specified for the source metadata store did not exist.
Action: Verify that the label name is correct, or provide a label that exists in the source metadata store.

Level: 1

Type: ERROR

Impact: Data

MDS-01106: The TransferTypeRestriction {0} can not be associated with given TransferType {1}.
Cause: The given TransferTypeRestriction can not be associated with the specified TransferType.
Action: Ensure that given TransferTypeRestriction is valid for the specified TransferType.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01107: Post transfer label cannot be created in target store.
Cause: Post transfer label cannot be created in the target store. Examine the cause exception messages to find the root cause of it.
Action: Examine any accompanying messages to decide if further action is required.

Level: 1

Type: ERROR

Impact: Data

MDS-01108: TransferType cannot be null for ExtendedTransferType.
Cause: TransferType provided to create ExtendedTransferType was null.
Action: Provide valid TransferType to create ExtendedTransferType.

Level: 1

Type: ERROR

Impact: Data

MDS-01109: The target archive configured in ArchiveMetadataStore already exists. Cannot export the documents into an existing archive file.
Cause: The target archive already exists. Exporting the documents into an existing archive is not allowed.
Action: Export the documents into a non existing archive file.

Level: 1

Type: ERROR

Impact: Data

MDS-01110: Sandbox export operation allowed only from a database metadata store to an archive metadata store.
Cause: Either source metadata store is not a database or the target metadata store is not an archive in sandbox export operation.
Action: Configure source metadata store to be a database and target metadata store to be an archive in sandbox export operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01111: Sandbox import operation allowed only from Archive Metadata Store to a Database Metadata store.
Cause: Either source metadata store is not an archive metadata store or the target metadata store is not a database in sandbox import operation.
Action: Configure source metadata store to be an archive metadata store and target metadata store to be a database in sandbox import operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01112: Transfer unit list in a Sandbox export/import operation should have atleast one transfer unit.
Cause: Transfer unit list in Sandbox export/import operation empty.
Action: Ensure that there is at least one transfer unit to be transferred in sandbox export/import operation.

Level: 1

Type: ERROR

Impact: Data

MDS-01113: Sandbox metadata file required for import to a new sandbox operation.
Cause: Sandbox metadata file missing in source Archive metadata store in import to a new sandbox operation.
Action: Import to a new sandbox only from an archive store whose contents were exported from a sandbox and contain sandbox metadata document.

Level: 1

Type: ERROR

Impact: Data

MDS-01114: Sandbox with same name as the one imported in a sandbox import operation exists on the target metadata store.
Cause: Sandbox with same name already exists on the target metadata store and the flag to force creation of sandbox is not set to true.
Action: Pass true for forceSBCreation to TransferParams.createForSandboxImport() or destroy sandbox already existing with same name on the target metadata store in sandbox import operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01115: Source sandbox in a sandbox export operation does not contain metadata.
Cause: Source sandbox in export operation was not created with metadata.
Action: Export from a Sandbox that was created with metadata.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01116: Existing target sandbox in import operation does not contain metadata.
Cause: Target sandbox in an import into an existing sandbox operation was not created with metadata.
Action: Import into an existing sandbox that was created with metadata.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01117: Sandbox archive imported into an existing sandbox.
Cause: The archive imported into an existing sandbox contains sandbox metadata.
Action: Import only regular archives(that do not contain sandbox metadata) into an existing sandbox.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01118: Sandbox export operation not supported because the source MDS database repository is of older version that does not support this feature.
Cause: Sandbox metadata is needed to transfer documents from sandbox. Source store being used does not support storing metadata for sandbox.
Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01119: Sandbox import operation not supported because the target MDS database repository is of older version that does not supporit this feature.
Cause: Sandbox metadata is needed to transfer documents from sandbox. But target store being used does not support storing metadata for sandbox.
Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01120: Sandbox transfer unit list creation not supported because the source MDS database repository is of older version that does not support this feature.
Cause: Sandbox metadata is needed to transfer documents from sandbox. Source store being used does not support storing metadata for sandbox.
Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01121: Document "mds-transfer-config.xml" cannot be read by MDSTransfer.
Cause: The /meta-inf/mds-transfer-config.xml document cannot be read from source store. Refer to cause exception for more information on the actual reason for failure.
Action: Look for messages that describe the cause exception, and then take the appropriate action.

Level: 1

Type: ERROR

Impact: Data

MDS-01122: Metadata Object Name "{0}" specified in the mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata object name.
Cause: Metadata object name specified in /meta-inf/mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata object name.
Action: Make sure the document name specified in mds-transfer-config.xml is a valid metadata object name but not a speical document name.

Level: 1

Type: ERROR

Impact: Data

MDS-01123: The metadata path "{0}" specified in the mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata path.
Cause: The metadata path specified in /meta-inf/mds-transfer-config.xml to preserve the user updated documents in target repository is not a valid metadata path.
Action: Make sure the metadata path specified in mds-transfer-config.xml is a valid metadata path.

Level: 1

Type: ERROR

Impact: Data

MDS-01150: Reference is null or empty.
Cause: A reference value was null or empty.
Action: Use a valid reference value that is not empty or null.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01151: Id/LocationPath reference is null or missing.
Cause: An Id/LocationPath reference value was null or empty.
Action: Use a valid Id/LocationPath reference value that is not empty or null.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01153: invalid LocationPath expression "{0}"
Cause: The LocationPath expression was invalid.
Action: Use a valid LocationPath format. The LocationPath expression should follow the format "/text()" or "/text()[x]", where 'x' is the index of "text block".

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01154: invalid LocationPath expression "{0}"
Cause: The node index in the LocationPath expression was invalid.
Action: Change the node index in the LocationPath expression to a number greater than or equal to 1.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01158: Expecting a base document. Reference "{0}" is a special document.
Cause: A base document was expected, but the reference was a special document.
Action: Use a valid base document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01159: Expecting absolute document reference. Reference "{0}" has local element reference portion.
Cause: The supplied reference was not the expected type.
Action: Ensure the reference is of the expected type.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01160: Expecting absolute document reference. Reference "{0}" is a relative reference to the document.
Cause: The supplied reference was not the expected type.
Action: Ensure the reference is of the expected type.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01161: Reference "{0}" has an invalid character "{1}".
Cause: The supplied reference did not follow the MDS naming standard.
Action: Use valid characters for the reference.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01162: Reference "{0}" has an invalid XML attribute character.
Cause: The supplied reference did not follow the MDS naming standard.
Action: Use valid characters for the reference.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01163: invalid reference "{0}"
Cause: The supplied reference did not follow the MDS naming standard.
Action: Ensure that the reference follows the MDS naming standard.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01164: invalid reference "{0}" for a translation document
Cause: The supplied reference did not have the expected document extension (.xlf).
Action: Use the correct extension, .xlf, for the translation document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01165: invalid reference "{0}" for a customization document
Cause: The supplied reference did not have the expected document extension (.xml).
Action: Use the correct extension, .xml, for the customization document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01166: invalid reference "{0}" for a metadata extension document
Cause: The supplied reference did not have the expected document extension (.rdf).
Action: Use the correct extension, .rdf, for the metadata extension document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01167: There is no namespace declaration for the prefix "{1}" used in LocationPath expression "{0}".
Cause: The LocationPath expression was incomplete.
Action: Use a valid LocationPath format.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01168: Partition name "{0}" starts or ends with character "{1}". Partition name cannot contain leading or trailing spaces, ".", "-"
Cause: The supplied partition name contained leading or trailing spaces, ".", "-".
Action: Ensure that the partition name follows the MDS naming standard for partitions.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01169: Partition name "{0}" has an invalid character "{1}".
Cause: The supplied partition name did not follow the MDS naming standard.
Action: Use valid characters for the partition name.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01170: Partition name is null or empty.
Cause: Partition name value was null or empty.
Action: Use a valid partition name that is not empty or null.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01171: The ID prefix generated by concatenating the layer name "{0}" and layer value "{1}" is not a valid MDS ID.
Cause: The ID prefix generated by concatenating the layer name with layer value did not follow the MDS ID naming standard.
Action: Ensure that the ID prefix generated by concatenating the layer name with layer value follows the MDS ID naming standard.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01200: This operation is not supported.
Cause: An MDS query operation was attempted, but this particular operation is not supported.
Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01201: An invalid parameter cannot be used when constructing a query condition.
Cause: An invalid parameter was passed to the class ConditionFactory.
Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01205: A SQL error is occurring when performing the query: "{0}" with binds {1}.
Cause: An MDS query on a database store led to a SQL error.
Action: Note the stack backtrace and context of the operation, including the reported SQL query and error, and contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01206: The array size for the query must be greater than zero.
Cause: An MDS query specified a fetch unit size that was not positive.
Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01207: The namespace mapping for the prefix "{0}" specified in the location path, is missing.
Cause: During XPath evaluation, the namespace prefix was used, but the prefix was not mapped to a namespace.
Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-01250: The file path "{0}" does not exist.
Cause: An invalid path was provided.
Action: Retry the operation with a valid file path.

Level: 1

Type: ERROR

Impact: Files

MDS-01251: The parameter file {0} has no namespace on the document element.
Cause: A namespace was missing from the parameter file provided.
Action: Provide a parameter file with valid namespace information.

Level: 1

Type: ERROR

Impact: Data

MDS-01252: The parameter file {0} must have either {1} or {2} definition.
Cause: No source stores or target stores information were provided in the parameter file.
Action: Check the parameter file to have source and target store information and retry.

Level: 1

Type: ERROR

Impact: Data

MDS-01253: The parameter file {0} must not have both {1} and {2} definitions.
Cause: An attempt was made to transfer from source directory to target directory. Both source and target as directories is not supported.
Action: Provide correct source and target definition. Either source or target should be a metadata store.

Level: 1

Type: ERROR

Impact: Data

MDS-01254: The parameter file {0} contains same store definition for sourceStore and targetStore.
Cause: An attempt was made to transfer from and to the same store. The definition for sourceStore cannot be the same as the definition for targetStore.
Action: Provide correct source and target information. Change either source or target store definition.

Level: 1

Type: ERROR

Impact: Data

MDS-01255: The property {0} has not been supplied.
Cause: The required property was missing from the parameter file.
Action: Check the parameter file and supply the required property. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.

Level: 1

Type: ERROR

Impact: Data

MDS-01258: The value {0} for property {1} is invalid.
Cause: An invalid property value was provided in the parameter file.
Action: Provide a valid property value. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.

Level: 1

Type: ERROR

Impact: Data

MDS-01259: The metadata store "{0}" cannot be instantiated.
Cause: An error occurred during the instantiation of the class for the metadata store.
Action: Verify that correct values are provided in the parameter file. Refer to the error messages in application logs that describe the cause exception for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Data

MDS-01260: failure to process command-line arguments
Cause: Invalid command-line parameters were provided.
Action: Provide valid command-line parameters, and retry the operation. Refer to the MDS documentation for syntax of the tool parameters, or run the tool without parameters in order to get the Help message.

Level: 1

Type: ERROR

Impact: Data

MDS-01262: failure of transfer operation on a read-only target metadata store
Cause: The target metadata store used for transfer was read-only, for example a classpath store.
Action: Provide a writable target metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01263: operation failure on the resource {0} because source metadata store is read-only
Cause: An attempt was made to delete, create, update or get a mutable metadata object from a read-only source metadata store.
Action: Provide a writable source metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01264: The given element must contain either "customization" or "translation" configuration.
Cause: A customization or a translation configuration was missing for an element.
Action: Examine the transfer parameter file for valid MDS configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01265: Invalid parameter file {0}. Reason: <{1}:{2}> {3}
Cause: Parameter file provided was not valid.
Action: Provide a valid parameter file. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation. Refer to sample parameter for correct syntax.

Level: 1

Type: ERROR

Impact: Files

MDS-01266: The associated customization document is missing for a given customization class {0} for the given document name {1}.
Cause: The associated customization document for the given customization class did not exist.
Action: If the associated customization document was to be transferred, verify that it exists. Otherwise, no action is required.

Level: 1

Type: ERROR

Impact: Data

MDS-01267: The associated translation document is not found for a given locale {0} for the given document name {1}.
Cause: Associated translation document did not exist for the given locale.
Action: If the associated translation document was expected to be transferred, verify if it exists, otherwise, no action required.

Level: 1

Type: ERROR

Impact: Data

MDS-01268: The associated extended metadata document for the given document name {0} is missing.
Cause: No associated extended metadata document for the given document name existed.
Action: If the document was to be transferred, verify that the document exists. Otherwise, no action is required.

Level: 1

Type: ERROR

Impact: Data

MDS-01270: Opening and closing parentheses do not match.
Cause: Either an opening or closing parentheses was missing.
Action: Check and correct the namespace mappings provided. Each opening parentheses should have an equivalent closing parentheses and vice versa.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01271: Cannot get the dependency registry
Cause: An error occurred while getting the dependency registry.
Action: Retry the operation. If the problem persists, look for messages that describe the cause exception for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01272: unable to read mds-webapp-config.xml file
Cause: The mds-webapp-config.xml file was invalid.
Action: Confirm that the mds-webapp-config.xml file for the application is well formed, and valid.

Level: 1

Type: ERROR

Impact: Files

MDS-01273: The operation on the resource {0} failed because source metadata store mapped to the namespace {1} is read only.
Cause: An attempt was made to delete, create, update or get a mutable metadata object from a readonly source metadata store.
Action: Provide a writable source metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01301: Element "{1}", namespace "{0}" is not a valid child under parent "{3}", namespace "{2}".
Cause: An attempt was made to add, insert or replace a child element of the wrong type.
Action: Check the schema definition and ensure that the child element is the correct type.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01302: failure to load schema file "{0}"
Cause: An exception occurred in the XMLEF layer during processing of the schema definitions.
Action: Look for messages that describe the cause exception, and then take the appropriate action.

Level: 1

Type: ERROR

Impact: Data

MDS-01303: failure to register grammar from schema file "{0}"
Cause: An exception occurred in the XMLEF layer during addition of schema definitions.
Action: Look for messages that describe the cause exception, and then take the appropriate action.

Level: 1

Type: ERROR

Impact: Data

MDS-01305: failure to locate schema file "{0}".
Cause: The schema definition file was not found.
Action: Verify that the schema file name is correct, and that it is in the correct location.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01306: Grammar from a Web application can be added only once.
Cause: There were multiple method calls to add grammar from a web application.
Action: Verify that a grammar definition has already been added for the given MDSInstance and ServletContext. If it has then remove the calls to add it multiple times.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01307: no schema files for processing
Cause: No schema files were found against which beans can be generated.
Action: Pass an existing schema file to the bean generator.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01308: Event "{0}" is not supported.
Cause: An attempt was made to use event types that are not supported for the selected content model.
Action: Use only the event types that are allowed for the selected content model.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01309: ContentModelPipeline is empty.
Cause: The contentModelPipeline contained an empty or null builder list.
Action: A list of one or more valid builders must be available in the ContentModelPipeline.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01310: Invalid ContentModelPipeline. Missing {0}.
Cause: The expected builder was not available in builder list of the ContentModelPipeline.
Action: Valid builders must be supplied to the ContentModelPipeline.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01311: The DOM tree does not support the DOM event model.
Cause: This DOM Document did not implement EventTarget interface.
Action: Verify whether the Oracle XML Developer's Kit is used.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01312: Change-list transaction state is invalid.
Cause: The current change-list transaction state is invalid for the customization operation performed.
Action: Ensure Change-list to be in valid transaction state to perform the necessary customization operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01313: The argument for document cannot be null.
Cause: The argument for DocumentName was null.
Action: Provide a valid DocumentName.

Level: 1

Type: ERROR

Impact: Data

MDS-01314: TypeAnnotationProvider cannot be null.
Cause: The argument for TypeAnnotationProvider was null.
Action: Provide a valid TypeAnnotationProvider.

Level: 1

Type: ERROR

Impact: Data

MDS-01316: Support for XPath is not implemented yet.
Cause: Support for XPath has not been implemented yet.
Action: Provide a valid Configurable ID.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01319: JAXP support is not available. Falling back to using Oracle XML Developer's Kit for parsing the document {0}.
Cause: JAXP support was not available.
Action: None.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01320: Modifying the prefix declaration for {0} from "{1}" to "{2}" in document {3} through customizations is not supported.
Cause: An attempt was made to change an existing prefix declaration.
Action: Avoid attempts to change existing prefix declarations.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01321: Node type should be one of ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.
Cause: The node was not of the type ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.
Action: Ensure the node type is one of the following types: ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.

Level: 1

Type: ERROR

Impact: Data

MDS-01322: Value "{0}" does not satisfy "{1}" type.
Cause: The data type conversion failed.
Action: Verify that the expected XSD built-in simple data type and the passed-in string value are convertible.

Level: 1

Type: ERROR

Impact: Data

MDS-01323: Value "{0}" has an incorrect number of characters for a base64Binary.
Cause: The value did not represent a valid Base64Binary.
Action: Verify that the input value is valid.

Level: 1

Type: ERROR

Impact: Data

MDS-01324: Unknown XML schema built-in type "{0}"
Cause: An attempt was made to use an unknown XML schema built-in type.
Action: Use only valid XML schema built-in types.

Level: 1

Type: ERROR

Impact: Data

MDS-01325: unable to load type definition "{0}"
Cause: Could not load this type definition because the specified location did not exist.
Action: Ensure that the specified location for the type definition exists.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01326: Loading of type definition from element "{0}" is not supported.
Cause: An attempt was made to load a type definition from the specified element that is not supported in the MDS configuration.
Action: Examine the schema definition to ensure that the entry specified in type definition is correct.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01327: unable to load data from "{0}" into {1}
Cause: An error occurred while loading the content of this configuration element.
Action: Examine the schema definition to ensure that the content of this configuration element is correct.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01328: unable to load element "{0}" into {1}
Cause: An error occurred while loading this configuration element.
Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01329: unable to load element "{0}"
Cause: An error occurred while loading this configuration element.
Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01330: unable to load MDS configuration document
Cause: An I/O or parsing error occurred while loading the MDS configuration document.
Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.

Level: 1

Type: ERROR

Impact: Files

MDS-01331: unable to load MDS configuration document "{0}"
Cause: An error occurred in loading the content of MDS configuration document.
Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.

Level: 1

Type: ERROR

Impact: Files

MDS-01332: Class {0} is not a subclass or implementation of {1}.
Cause: The class specified in the configuration information did not extend the required class, or implement the required interface.
Action: Ensure that the class specified in the configuration information extends the correct class, or implements the correct interface.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01333: missing element "{0}"
Cause: This element was missing from the MDS configuration information.
Action: Ensure that the element is specified in the configuration information.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01334: missing element "{0}" in document "{1}"
Cause: This element was missing from the MDS configuration information.
Action: Ensure that this element is specified in the configuration document.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01335: namespace "{0}" mapped to metadata-store-usage "{1}" but its definition was not found in MDS configuration.
Cause: Metadata-store-usage element that was referenced by a namespace not found in MDS configuration.
Action: Ensure that this element is specified in MDS configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01336: No XML element is provided to create {0}.
Cause: A null XML element was passed to the constructor of this configuration object.
Action: Ensure that a valid XML element is provided to create a new instance of this configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01337: No URL is provided to create {0}.
Cause: A null URL was passed to the constructor of this configuration object.
Action: Ensure that a valid URL is provided to create a new instance of this configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01340: More than one metadata store can be resolved for the namespace "{0}".
Cause: There were multiple namespace to metadata store mappings in the persistence configuration that satisfied the request for the metadata store of a given namespace.
Action: Correct the namespace mapping in persistence configuration to ensure that the namespace is mapped to only one metadata store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01341: Namespace mapping for "{0}" is overridden by namespace mapping for "{1}"; the first mapping is not used.
Cause: A conflicting mapping to this namespace has already been defined in the persistence configuration.
Action: Correct the namespace mapping in the persistence configuration to ensure that there is no conflicting mapping to this namespace.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01342: No metadata store is mapped to the namespace "{0}".
Cause: No namespace mapping could be found in the persistence configuration for the specified namespace.
Action: Ensure that a correct namespace is passed into the method concerned, or alter the application configuration to define the specified namespace.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01343: There is a duplicate file extension mapping for "{0}".
Cause: A mapping to this file extension has already been defined in the file type configuration.
Action: Remove the duplicate file extension mapping from the file type configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01344: cannot create {0} due to null parameter
Cause: A null parameter was passed to the constructor of this configuration object.
Action: Ensure that a valid parameter is provided to create a new instance of this configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01346: The given namespace path "{0}" is not a valid path.
Cause: An invalid path was provided to create a namespace.
Action: Ensure that a valid path is provided to create a namespace.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01347: Base restriction is supported only for classpath store or servlet context store: namespace "{0}" mapped to "{1}".
Cause: The base restriction was specified for a metadata store other than the classpath metadata store and servlet context store.
Action: Correct the namespace mapping in the configuration to ensure that the base restriction is specified only for the classpath store or servlet context store.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01348: unable to save configuration document to "{0}"
Cause: An I/O error occurred while writing the configuration to a file.
Action: Check the file system and ensure that the file location is writable.

Level: 1

Type: ERROR

Impact: Files

MDS-01349: unable to read existing configuration document "{0}" to be updated
Cause: An I/O or parsing error occurred while reading the configuration file.
Action: Ensure that the configuration file does exist and has valid contents.

Level: 1

Type: ERROR

Impact: Files

MDS-01350: Adding namespace "{0}" mapped to "{1}" conflicts with existing namespace "{2}" mapped to "{3}".
Cause: An attempt was made to add a new namespace that conflicted with an existing namespace because it mapped to a different repository.
Action: Ensure that the new namespace does not map to a different repository if the new namespace is a super-namespace or sub-namespace of existing namespaces.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01351: Adding namespace "{0}" with "{1}" restriction conflicts with existing namespace "{2}" with "{3}" restriction.
Cause: An attempt was made to add a new namespace that conflicted with an existing namespace in the namespace restriction.
Action: Ensure that the new namespace does not conflict with existing namespaces in the namespace restriction if the new namespace is a super-namespace or sub-namespace of existing namespaces.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01352: Customization configuration with granular mapping "{0}" is unsupported; only the slash, "/", is allowed.
Cause: An attempt was made to add an invalid namespace mapping of the customization configuration. Only one namespace to customization class list mapping is currently allowed, and that namespace has to be a slash (/).
Action: Ensure that only the slash (/) is specified in the namespace mapping of the customization configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01353: unable to retrieve customization layer values from "{0}"
Cause: An I/O or parsing error occurred while reading the specified file to retrieve customization layer values.
Action: Ensure that the file does exist and has valid contents.

Level: 1

Type: ERROR

Impact: Files

MDS-01355: Both TypeConfig parameters contain Grammar Providers. Only one Grammar Provider is allowed.
Cause: A Grammar Provider was specified in multiple type configuration sources.
Action: Ensure that only one Grammar Provider is specified in the type Configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01356: Both TypeConfig parameters contain Metadata Providers. Only one Metadata Provider is allowed.
Cause: A Metadata Provider was specified in multiple type configuration sources.
Action: Ensure that only one Metadata Provider is specified in the type Configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01357: MDS configuration is not compatible with JAXB 1.0.
Cause: JAXB 1.0 jar file (xml.jar) was found on the classpath before any JAXB 2.0 jar files.
Action: Ensure that JAXB 2.0 jar files appear on the classpath before JAXB 1.0 jar file (xml.jar).

Level: 1

Type: ERROR

Impact: Configuration

MDS-01358: Invalid MDS configuration. Configuring multiple metadata stores as the default repository for customizations.
Cause: Multiple metadata stores were configured as the default repository for customizations in the MDS configuration.
Action: Ensure that only a single metadata store is configured as the default repository for customizations.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01359: The namespace used (http://xmlns.oracle.com/mds/config_10_1_3_001) in the configuration document is deprecated. Update the configuration document to use "http://xmlns.oracle.com/mds/config" as the namespace.
Cause: The namespace used (http://xmlns.oracle.com/mds/config_10_1_3_001) in the configuration document is deprecated.
Action: Update the configuration document to use "http://xmlns.oracle.com/mds/config" as the namespace.

Level: 1

Type: WARNING

Impact: Configuration

MDS-01360: Invalid MDS configuration. The attribute file-type-extension on the file-type element is missing for file type configuration.
Cause: The attribute file-type-extension was not specified on the file-type element for file type configuration.
Action: Ensure that a valid file-type-extension attribute is specified for every file-type element.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01361: cannot add XSD grammar
Cause: An attempt was made to add XSD grammar made by passing in a SchemaGrammarProvider.
Action: Ensure that the grammar provider is obtained using oracle.jdeveloper.webapp.runtime.WebAppDesignContext.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01362: Failed to auto-purge MDS respository: "{0}".
Cause: MetadataStore was scheduled for auto-purge after the MDSInstance was released
Action: Try later and contact support if persists.

Level: 1

Type: WARNING

Impact: Other

MDS-01363: Failed to lookup datasource with JNDI name "{0}" configured for the DBMetadataStore, defaulting to use ClassPathMetadataStore.
Cause: Application was configured with DBMetadataStore using JNDI datasource and JNDI lookup failed when running outside application server.
Action: No action required if defaulting to ClasspathMetadataStore is acceptable. Otherwise, use appropriate configuration such as FileMetadataStore.

Level: 1

Type: WARNING

Impact: Configuration

MDS-01365: Multiple metadata stores found with deploy-target attribute set to true, only one allowed per configuration.
Cause: Multiple metadata stores were configured as the deployment target.
Action: Ensure that only a single metadata store is configured for deployment.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01366: Cannot find a metadata store with deploy-target attribute set to true
Cause: A single metadata store must be configured as a deploy target. None was found.
Action: Ensure that a single metadata store is configured for deployment.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01367: Failed to create {0}. Invalid MDS configuration specified in: "{1}"
Cause: Declarative MDS configuration is invalid.
Action: Specify correct mds configuration information and try creating the configuration again.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01368: Variable "{0}" used in configuration document is not defined either as system property or as envrionment variable.
Cause: This variable was not defined.
Action: Ensure that this variable is defined before loading the configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01369: Variable declaration in "{0}" in configuration document is incorrect.
Cause: Variable did not either start with "${" or it did not end with "}".
Action: Ensure that the configuration variable is correctly declared in the form ${var}.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01370: MetadataStore configuration for metadata-store-usage "{0}" is invalid.
Cause: MetadataStore class or some of its properties were not valid.
Action: Ensure that the MetadataStore class exists and all required properties are valid. See message of the cause exception for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01371: ADF security is not configured in "{0}", password can not be securely processed.
Cause: ADF security configuration was not found in the config file.
Action: Set the password using JDeveloper to ensure required configuration is generated.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01373: unable to retrieve password.
Cause: unable to retrieve the password due to exception in security layer.
Action: See message of the cause exception for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01374: unable to save password.
Cause: unable to save the password due to exception in security layer.
Action: See message of the cause exception for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01375: No password defined for DBMetadataStore in configuration file or in the wallet file.
Cause: DBMetadataStore uses JDBC based configuration but no password specified.
Action: Set the password for the DBMetadataStore using JDeveloper.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01376: Unable to get database connection from data source "{1}" configured with JNDI name "{0}".
Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.
Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01377: Unable to get database connection from data source configured with JNDI name "{0}".
Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.
Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01400: Read-only extended metadata resource "{0}" is not writable.
Cause: An attempt was made to update a read-only extended metadata resource.
Action: Ensure that the metadata object is mutable before getting the extended metadata.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01401: Updating a node in one document "{1}" using a node from a different document "{0}" is not allowed.
Cause: The node being added or inserted was from a different metadata object. They must be from the same base document.
Action: Ensure that the node being inserted is from the correct metadata object.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01402: attempting to update an immutable MElement: "{0}"
Cause: The MElement being updated was immutable.
Action: Check that the MElement in question really is mutable.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01403: Updating a mutable MElement using an immutable MElement: "{0}" is not allowed.
Cause: An attempt was made to update a mutable MElement using an immutable MElement.
Action: Verify that the child MElement being used for the update is mutable.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01404: Customization to replace root node of {0} is not allowed.
Cause: An attempt was made to replace the root node as part of a customization.
Action: Replace the root node in the base document, or modify the existing root node instead.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01450: missing GUID
Cause: The application removed an object's GUID while editing its XML metadata content.
Action: Fix the application so it does not tamper with MDS GUIDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01451: GUIDs do not match.
Cause: The application altered an object's GUID while editing its XML metadata content.
Action: Fix the application so it does not tamper with MDS GUIDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01452: GUID is null.
Cause: An attempt was made to retrieve a metadata object or document by GUID, but the given GUID was null.
Action: Fix the application so it passes a valid GUID to the method in question.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01455: multiple GUIDs on metadata object {0}
Cause: The application set multiple GUID values while editing an object's XML metadata content.
Action: Fix the application so it does not tamper with MDS GUIDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01456: invalid GUID on metadata object {0}
Cause: The application set an object's GUID to an invalid value while editing its XML metadata content.
Action: Fix the application so it does not tamper with MDS GUIDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01457: GUID feature not available
Cause: The application attempted to retrieve an object by GUID from a metadata store that does not yet support this.
Action: Fix the application so it does not attempt this, or configure the application to use a different type of metadata store.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01458: GUID must not be present.
Cause: The application set an object's GUID value while editing its XML metadata content.
Action: Fix the application so it does not tamper with MDS GUIDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01460: GUIDs on DOM Document do not match.
Cause: The application set an object's GUID to a different value while editing its XML metadata content.
Action: Fix the application so it does not tamper with MDS GUIDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01461: unable to create document {0} in the metadata repository; a document with the same name or GUID already exists
Cause: An attempt was made to import or create a document with a name or GUID that is already used by an existing document.
Action: Delete the document in the MDS repository prior to import or creation.

Level: 1

Type: ERROR

Impact: Data

MDS-01462: GUID feature is not supported in the classpath store.
Cause: The application attempted to retrieve an object by GUID from the classpath metadata store that does not support this.
Action: Fix the application so it does not attempt retrieval by GUID, or configure the application to use a different type of metadata store.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01464: unable to save GUIDRegister {0}
Cause: The GUID register (GUID index files) could not be written.
Action: Verify that the application has write permission for the given file, and that the disk is not full.

Level: 1

Type: ERROR

Impact: Files

MDS-01465: unable to remove node {0} from the GUIDRegister
Cause: The given node was not removed from the GUID register, possibly because it was not found.
Action: Delete the GUID register files, restart the application and try the operation again. If that fails, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Data

MDS-01466: unable to create GUIDRegister directory {0}
Cause: The owning directories for the GUID register (GUID index files) were not created.
Action: Verify that you have permission to create the parent directories for the given file name.

Level: 1

Type: ERROR

Impact: Files

MDS-01468: A different GUID is already registered for document {0}.
Cause: The GUID register has become corrupted.
Action: Delete the GUID register files and restart the application (the files will then be re-created).

Level: 1

Type: ERROR

Impact: Data

MDS-01469: unable to remove old GUIDRegister store path {0}
Cause: Old GUID register files were not deleted.
Action: Verify that you have permission to delete these files.

Level: 1

Type: ERROR

Impact: Files

MDS-01470: more than one GUID is registered for document {0}
Cause: The GUID register has become corrupted.
Action: Delete the GUID register files and restart the application (the files will then be re-created).

Level: 1

Type: ERROR

Impact: Data

MDS-01471: more than one document is registered for GUID {0}
Cause: The GUID register has become corrupted.
Action: Delete the GUID register files and restart the application (the files will then be re-created).

Level: 1

Type: ERROR

Impact: Data

MDS-01472: GUID is missing in file {0}
Cause: No GUID was found in the given file but the metadata object type definition indicated there should be one.
Action: Re-create the metadata object or correct its type definition not to require a GUID.

Level: 1

Type: ERROR

Impact: Data

MDS-01500: The MDSObject {0} is an XML document and cannot be loaded using StreamedObject API.
Cause: An attempt was made to load an XML document via StreamedObject API.
Action: Retry the operation using MetadataObject API or use a non-XML document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01501: The MDSObject {0} is not an XML document and cannot be loaded from MetadataObject API.
Cause: An attempt was made to load a streamed object (non-XML document) using MetadataObject API.
Action: Retry the operation using StreamedObject API or use a document containing valid XML.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01502: The MDSObject "{0}" is an XML document and cannot be saved using StreamedObject API.
Cause: An attempt was made to save an XML document using StreamedObject API.
Action: Retry the operation using MetadataObject API.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01503: The content of StreamedObject {0} cannot be read.
Cause: An attempt to read the StreamedObject content failed.
Action: Look at the error message and exception stack in the application logs to determine the reason for the failure.

Level: 1

Type: ERROR

Impact: Data

MDS-01504: The document {0} is either registered as a streamed file type or is a non-XML file extension and cannot be created using MetadataObject API.
Cause: An attempt was made to create an MDSObject named with a streamed object (non-XML) extension using MetadataObject API.
Action: Retry the operation using StreamedObject API.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01600: The Dependency Analyzer requires a DependencyFilter.
Cause: Either no filter was supplied, or the filter supplied was null.
Action: Supply a non-null filter.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01601: The relationship role name {0} is a duplicate.
Cause: A role name defined in a relationship had already been used.
Action: Ensure that the toParentRole and toChildRole in a relationship have not already been used by another relationship.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01602: cannot locate the element type {0} in namespace {1} defined for the relationship
Cause: The element type did not exist in the given namespace.
Action: Ensure that the element type exists in the given namespace.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01604: The relationship from {0} to {1} is invalid because the latter is not a valid MDS reference.
Cause: An invalid MDS reference was specified as the parent.
Action: Ensure the parent reference is a valid MDS reference.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01605: The relationship from {0} to {1} is invalid because the latter does not exist.
Cause: No parent element was found matching the MDS reference supplied.
Action: Ensure that the parent reference in the relationship points to an existing element.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01606: The relationship from {0} to {1} is invalid because the latter is of incorrect type.
Cause: The child element referenced a parent of the wrong type.
Action: Ensure that the parent type matches the one stipulated in the relationship definition.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01607: The relationship from {0} to {1} is invalid because type information is not available for the latter.
Cause: No type definition could be found for the parent.
Action: Ensure that the parent type information is available.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01608: The relationship from {0} to {1} is invalid because the latter maps to a different store.
Cause: The parent and child objects in the relationship have been mapped to different stores.
Action: Ensure that the parent maps to the same store as the child object.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01609: The document {0} contains relationships that do not conform to the relationship definition.
Cause: Constraints in this document's relationship definitions were violated.
Action: Ensure that the relationships conform to the constraints in the relationship definition.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01610: Some of the changes in the MDS session are not valid.
Cause: A change was made in the MDS session that was not valid.
Action: Check the changes made and ensure each of them is valid.

Level: 1

Type: ERROR

Impact: Data

MDS-01611: not saving changes in MDS session because some changes are not valid
Cause: A change made in the MDS session was not valid.
Action: Check all the changes made and ensure that all changes are valid.

Level: 1

Type: ERROR

Impact: Data

MDS-01612: The object {0} cannot be deleted because it is referenced by {1}.
Cause: An attempt was made to delete an element that was being referenced by a child object.
Action: Remove the child reference to this object so the object can be deleted.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01613: The MetadataObject {0} cannot be deleted because of relationship integrity constraints.
Cause: An attempt was made to delete an object that was still being referenced.
Action: Remove the child references to the metadataObject so that it can be deleted.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01614: Rename is not allowed because integrity checking is not turned on in the object {1} in MetadataObject {0}.
Cause: Integrity checking was switched off so it was not possible to check whether the rename would have broken any relationship integrity constraints.
Action: Ensure that integrity checking is turned on.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01615: failure to rename {0} because there is no reference attribute in MetadataObject {1}, element {2}
Cause: A child object could not reference the renamed object as its current reference was invalid.
Action: Confirm that all the references in the child object are valid.

Level: 1

Type: ERROR

Impact: Data

MDS-01620: The untyped dependency with the following registration details cannot be inserted: {0}, {1}, {2}, {3}.
Cause: The dependency could not be registered in the database repository due to a SQL exception.
Action: Correct the cause of the SQL exception and retry the untyped dependency registration.

Level: 1

Type: ERROR

Impact: Data

MDS-01621: The untyped dependency information for {0} could not be removed.
Cause: An attempt to remove untyped dependency information failed either because the document was invalid or there was a SQL exception.
Action: Verify that the document and its dependencies are valid, or correct the cause of any SQL exceptions.

Level: 1

Type: ERROR

Impact: Data

MDS-01622: There is no analyzer to unregister.
Cause: No analyzers were supplied to be unregistered.
Action: Supply the DependencyAnalyzer to be unregistered.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01630: invalid operation in a customized context on an element that could participate in a relationship: {0}
Cause: Within a customized context there was an attempt to insert an element without first deleting it as part of a composite move.
Action: Within the customized context, do not attempt inserts on elements without first deleting them as part of a composite move.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01631: In a customized context, an element that could participate in a relationship as a child cannot be modified. The reference is {0} on {1}.
Cause: Within a customized context, an attribute being customized could have been a parent reference within a relationship.
Action: Do not attempt to modify or remove an attribute that could be a parent reference within a relationship.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01633: In a customized context, an element that could participate in a relationship cannot be deleted: {0}.
Cause: Within a customized context an attempt was made to delete an element that could participate in a relationship.
Action: Do not attempt to delete an entity while in a customized context.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01634: In {0}, a {1} element that participates in a relationship lacks a configurable ID.
Cause: An operation was attempted on a participant in a relationship that lacked a configurable ID.
Action: Add a configurable ID to the element on which it is missing. If necessary, refer to the element's schema definition to identify the configurable ID attribute.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01635: Skipping the relationship validation for {0} in the metadata object {1} because the element contains an invalid MDS reference.
Cause: Validation of the object's relationships was not performed because the element contained an invalid MDS reference.
Action: Correct the MDS references in the MetadataObject specified.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01700: MElementBeanImpl._setSimpleChild cannot be called on a non-simpleType element: name={0}, namespace{1}
Cause: An attempt was made to set a bean element to a simple type, but the definition in the schema was not a simple type. The generated beans may not have matched the registered schema.
Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01701: Cannot set the value on an element that is not based on a simpleType: name={0}, namespace={1}
Cause: An attempt was made to set an element to a simple type, but the definition in the schema was not a simple type.
Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01702: The method getBean() is not valid for metadata object {0} - it is allowed on only bean metadata objects.
Cause: An attempt was made to access the metadata object using the bean API but the metadata object was not a bean metadata object. The schema for the root element may not have been registered with MDS, or the beans were not available on the classpath.
Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01703: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - no object factory can be found or jaxb.properties cannot be found
Cause: An element was found in the metadata object that did not have a corresponding bean class. The schema for the element may not have been registered with MDS, or the beans were not available on the classpath.
Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01705: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - object factory class {3} does not have the expected unmarshal() method
Cause: The bean object factory found for the element did not appear to have been generated by the MDS bean generation tool.
Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.

Level: 1

Type: ERROR

Impact: Data

MDS-01706: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - object factory class {3} failure in unmarshal() method
Cause: An unexpected exception occurred while creating a bean object for the element.
Action: Contact the developers of the application, providing the cause exception.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01707: Error generating relationship method {0} for relationship defined on attribute {1}: incorrect parentType definition
Cause: There was an error in the relationiship definition.
Action: Check the parentType definition on the relationship

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01800: Sandbox is not supported for {0} configured on {1}.
Cause: An underlying metadata store did not support the sandbox feature.
Action: Provide a metadata store that supports sandbox feature.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01801: Document name {0} should not refer to the raw sandbox resource name.
Cause: A resource name pointed directly to a resource in the sandbox component.
Action: Provide a logical document name to resolve the issue.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01802: A sandbox by name {0} already exists in the {1} store.
Cause: A sandbox with the same name already existed in the store.
Action: Use a different name or destroy the existing sandbox before reusing the same name.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01803: Sandbox Persistence manager cannot be constructed using an instance of SandboxPManager.
Cause: An attempt was made to construct an instance of sandbox persistence manager using an instance of SandboxPManager.
Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01804: Sandbox {0} configured with {1} namespace, {2} store and {3} label from mainline is not compatible with {4} label created on {5} namespace.
Cause: A label was used that is different from the mainline label associated with the sandbox.
Action: Use a label that is compatible with the sandbox and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01805: Sandbox {0} missing in {1}.
Cause: The specified sandbox was not found in the underlying metadata store.
Action: Provide the name of an existing sandbox, or create a new sandbox if necessary.

Level: 1

Type: ERROR

Impact: Data

MDS-01806: failure to remove {0} from {1}, because it is not a valid document in the sandbox
Cause: The specified document to be removed was not found in the sandbox.
Action: Verify that the document exists in the sandbox.

Level: 1

Type: ERROR

Impact: Data

MDS-01807: failure to delete sandbox {0}
Cause: An error occurred while deleting the sandbox.
Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01808: SandboxUsage with the sandbox name set to {0} does not return any namespaces.
Cause: No namespaces were found on the SandboxUsage.
Action: Configure the SandboxUsage with namespaces that are associated with the sandbox.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01809: failure to list sandboxes matching {0}
Cause: An error occurred while listing or querying the sandboxes.
Action: Look for error messages to determine the actual cause of the failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01810: failure to refresh sandboxes to target label {0}
Cause: Target label is older than the current source label.
Action: Specify a target label which is later than current label.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01811: failure to list sandboxes matching customization for {0}, layer: {1}, value: {2}
Cause: An error occurred while listing or querying the sandboxes.
Action: Look for error messages to determine the actual cause of the failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01812: sandbox name {0} exceeds the maximum limit of {1} characters
Cause: Sandbox name is more than the supported size.
Action: Use a shorter sandbox name.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01813: sandbox metadata for {0} can not be saved because it is being updated by another user.
Cause: More than one user is updating the sandbox metadata at the same time.
Action: Get the sandbox metadata again and retry saving after making the changes.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01814: sandbox metadata for {0} cannot be changed because it is read only.
Cause: Sandbox metadata is read only and cannot be updated
Action: To update get an instance of sandbox and then get the sandbox metadata from the instance

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01815: store configured for sandbox {0} does not support sandbox metadata.
Cause: Sandbox metadata is not supported on the repository.
Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later to use this feature.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01816: {0} is not a valid name for a sandbox.
Cause: The specified sandbox name is either an MDS reserved package part name or contains invalid characters.
Action: Ensure that the specified sandbox name is neither an MDS reserved package part name nor does it contain invalid characters as per the MDS Resource name specification.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01817: sandbox {0} is either active or applied to mainline. The undo operation cannot continue.
Cause: The sandbox is either applied or is in the active state.
Action: Check that the sandbox is in the intermediary state

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01818: sandbox {0} is in applied_with_undo state. No further updates except finalized are allowed.
Cause: The sandbox is in applied_with_undo state and no further updates can be done to the sandbox.
Action: The only allowed operations in the intermediary state are: finalize and undo.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01819: Lock on sandbox {0} cannot be taken. A concurrent management operation may be in progress.
Cause: A management operation on the sandbox is in progress and has locked the sandbox.
Action: Retry the operation after a while.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01820: Metadata for sandbox {0} is not available. The sandbox management operation cannot proceed without sandbox metadata.
Cause: Sandbox was created without metadata.
Action: Use the management APIs that are available for sandboxes without metadata.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01900: None of the configured metadata stores support versioning.
Cause: The underlying metadata store did not support versioning.
Action: Configure a metadata store that supports versioning, and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01901: specifying multiple labels for a namespace not allowed
Cause: Multiple labels were provided for a namespace that pointed to a metadata store.
Action: Provide a single label to map to a namespace and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01902: Label or namespace is invalid.
Cause: Either the namespace or the label was invalid.
Action: Verify that the namespace and the label are correct, and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01903: Specified label {0} does not exist for {1} namespace.
Cause: The specified label did not exist in the metadata store mapped to the namespace.
Action: Verify that the label name is correct and that the label exists, and then retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01906: A label with same name {0} already exists.
Cause: An attempt was made to create a label that already existed.
Action: Create a label with a different name, and then retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01907: The label {1} is already configured for the store "{0}", so the same store cannot be configured with another label "{2}".
Cause: An attempt was made to map a label for a store when a label-to-store mapping already existed for that store.
Action: De-associate the existing label mapped to the store first, and then retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01908: failure to delete versions of the document {0}
Cause: An error had occurred while versions were being deleted.
Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01909: No namespaces are specified for creating label {0}.
Cause: No namespace information was found for creating a label.
Action: Provide a namespace for creating a label, and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01910: The namespace {0} is already registered with the label {1}, so the super/sub namespace {2} cannot be assigned with the label {3}.
Cause: An attempt was made to associate multiple labels with a namespace, or an attempt was made to associate multiple namespaces with a single label.
Action: Associate a single label with a single namespace, and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01911: failure of the metadata purge operation for the requested repository partition
Cause: An error occurred during a purge operation.
Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01912: MetadataStore configured for {0} does not support versioning.
Cause: The metadata store configured for the resource did not support versioning.
Action: Configure a metadata store that supports versioning or verify that the resource name is correct.

Level: 1

Type: ERROR

Impact: Configuration

MDS-01913: A deployment lineage with same application name "{0}" and deployment module name "{1}" already exists.
Cause: An attempt was made to create a lineage that already existed.
Action: Create a lineage with a different application or MAR name, and then retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-01914: The application name and deployment module name cannot be null to create DeploymentInfo.
Cause: An attempt was made to create DeploymentInfo with null values.
Action: Make sure that the values for application name and deployment module name are non-null.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02024: Setting or modifying the unique identifier of an existing node through customizations is not supported.
Cause: An attempt was made to customize a configurable ID.
Action: Remove any customization that is attempting to modify the unique identifier of an XML element.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02025: The requested change is incompatible with changes already pending on the MDS session.
Cause: An attempt was made to perform a change operation on the MDS session which would update the same MetadataObject part as another change operation that has been done. For example, if you change a customization of a metadata object then attempt to delete all of its customizations, the latter operation will fail because it conflicts with the former. You must save the former change first before doing the second.
Action: Save the changes that have already been made on the session (by calling flushChanges), then retry the failed operation.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02100: Illegal permission target: "{0}" - must begin with {1}.
Cause: An attempt was made to create an MDS permission class with an incorrect syntax.
Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02101: Illegal permission action: "{0}" - unknown action.
Cause: An attempt was made to create an MDS permission class with an incorrect syntax.
Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02102: Illegal permission action: "{0}" - customize action takes 0 or 2 parameters.
Cause: An attempt was made to create an MDS permission class with an incorrect syntax.
Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02201: type validation failure for the metadata object "{0}"
Cause: The content of the metadata object was not valid against the registered XSDs.
Action: Ensure that the metadata object content is valid with respect to the registered XSDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02202: Content of the metadata object "{0}" is not valid.
Cause: The content was not valid either with respect to the registered XSDs or with the registered relationships.
Action: Check the content of the metadata object and correct the content as necessary to make it valid.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02203: type validation error for the metadata object "{0}" at the node "{1}"
Cause: A validation error occurred at the specified node.
Action: Check the content at the specified node for compliance with registered XSDs and relationships.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02204: type validation warning for the metadata object "{0}" at the node "{1}"
Cause: A validation warning occurred at the specified node.
Action: Check the content at the specified node for compliance with registered XSDs.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02301: The rename unit is invalid because either "{0}" or "{1}" is reused in the rename plan.
Cause: The resource name provided in the rename plan was used more than once.
Action: Provide distinct names for source and target names while renaming.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02302: subobjects "{1}" not found in metadata object "{0}"
Cause: The specified subobjects were not found in the metadata object.
Action: Look in the error message log for details.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02303: The given rename plan syntax is invalid
Cause: The rename plan syntax specified was invalid.
Action: Look in the error message log for details.

Level: 1

Type: ERROR

Impact: Configuration

MDS-02304: RenameOperation failed for StreamedObject "{0}" because subobjects were specified for this streamed object.
Cause: Streamed objects do not support subobjects.
Action: Remove the RenameObject that contains reference to the streamed object and subobject references from the RenamPlan.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02401: The operation {0} on the {1} node is not allowed.
Cause: An attempt was made to customize a node that was not customizable.
Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-02402: The type definition for {1} does not allow customization of {0}.
Cause: An attempt was made to customize a node that was not customizable.
Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file, tag library definition file, or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-02404: The subelement {1} in the MDX document does not allow customization of {0}.
Cause: An attempt was made to customize a node that was not customizable.
Action: Check the customization restriction information which can be located in the schema definition, standalone xml file or an extended metadata file. Also check the customization policy for the MDSSession in use and the customization configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-02405: The attribute {2} in element {1} in the MDX document does not allow customization of {0}.
Cause: An attempt was made to customize a node that was not customizable.
Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-02406: Customization of {0} is not allowed because it is not explicily allowed by any type definition nor any extended metadata entry.
Cause: An attempt was made to customize a node that was not customizable.
Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.

Level: 1

Type: ERROR

Impact: Configuration

MDS-02407: Customization of {0} is not allowed because the local reference was not found in the document.
Cause: An enquiry about the customizability of a node supplied a local reference that wasn't found in the document.
Action: Ensure that the local reference applies to the document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02408: The operation {0} on the {1} node is not allowed because the metadata object reference was not found in the change event.
Cause: A document change is not allowed because the metadata object reference was null.
Action: Ensure that the change document exists.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02500: Cannot find a valid MDSSession object for accessing the MDS document using ORAMDS URL
Cause: A valid MDSSession object was not set before accessing the document using the "oramds:///" protocol.
Action: Use the MDSURLHelper.setMDSSession() method to set a valid MDSSession object before accessing MDS documents using the oramds protocol.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02501: cannot load the ORAMDS URL "{0}" because MDS session could not be created or resolved
Cause: An error occurred while creating or resolving an MDS session object.
Action: Look for messages describing the cause exception in the error message log for more information on the actual reason for failure.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02600: configuration migration failure because the configuration document contains more than one mds-config element
Cause: The given configuration document contained more than one mds-config element.
Action: Correct the configuration document to contain a single mds-config element.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02601: configuration migration failure because it contains more than one persistence-config element
Cause: The configuration document contained more than one persistence-config element.
Action: Correct the configuration document to contain a valid persistence-config element.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02602: configuration migration failure because it contains more than one metadata-stores element
Cause: The configuration document contained more than one metadata-stores element
Action: Correct the configuration document to be a valid 10.1.3 configuration document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-02603: configuration migration failure because it contains an invalid metadata-store element
Cause: The configuration document contained an invalid metadata-store element.
Action: Correct the configuration document to be a valid 10.1.3 configuration document.

Level: 1

Type: ERROR

Impact: Programmatic

MDS-05786: Unable to deploy the metadata archive: {0}.
Cause: Metadata archive (MAR) is corrupt.
Action: Validate that the metadata archive (MAR) is valid and readable.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05787: Partition name is not specified in adf-config.xml file.
Cause: A property with name partition-name was not found as a child of the metadata-store element.
Action: Specify the target partition as a child property of the metadata-store element in adf-config.xml.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05788: Unable to find the JNDI datasource in the file adf-config.xml.
Cause: A property with name jndi-datasource was not found as a child of the metadata-store element.
Action: Specify the JNDI datasource a child property of the metadata-store element in adf-config.xml.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05789: Unable to deploy the metadata archive.
Cause: Metadata archive (MAR) was not found.
Action: Ensure that the metadata archive (MAR) is packaged with the application.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration.
Cause: The metadata store definition is either missing or incorrectly configured in the file adf-config.xml.
Action: Ensure that the metadata store definition is present and contains the correct repository configuration

Level: 1

Type: ERROR

Impact: Configuration

MDS-05791: An error occurred during the deployment of the metadata archive (MAR) {0}.
Cause: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action.
Action: Ensure that the metadata store configuration is correct.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05792: Unable to load MDS configuration from "{0}"
Cause: The MDS configuration is either not defined or incorrect.
Action: Ensure that the MDS configuration is correctly defined.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05793: Metadata path {2} for partition {1} of MDS file repository {0} specified in adf-config.xml is either invalid or unreachable.
Cause: The metadata path named in the error message for the MDS file repository partition cited in the error message was either invalid or unreachable.
Action: Ensure that the MDS file repository named in the error message is registered and that the metadata partition cited in the error message is configured with a valid metadata path in adf-config.xml.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05794: Unable to load MDS persistence configuration from "{0}"
Cause: The MDS persistence configuration is either not defined or incorrect.
Action: Ensure that the MDS persistence configuration is correctly defined.

Level: 1

Type: ERROR

Impact: Configuration

MDS-05795: Invalid value "{0}" specified in the content-config of the application's configuration
Cause: Only restriction type CUSTOMIZATIONS is supported in content-config. It is only allowed with path "/" and no file extension.
Action: Ensure that the MDS persistence configuration is correctly defined.

Level: 1

Type: ERROR

Impact: Configuration

MDS-10001: Error:
Cause: An error occured. Details are usually given in the accompanying messages.
Action: Look for messages describing the cause and take the appropriate action.

Level: 1

Type: ERROR

Impact: Data

MDS-10003: The specified {0} argument is null or empty.
Cause: A required program argument was null or empty.
Action: Record any accompanying exception messages and contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-10009: The transfer of the document {0} is not successful.
Cause: Document transfer failed
Action: Examine any accompanying messages to decide if further action is required.

Level: 1

Type: WARNING

Impact: Data

MDS-10010: Deleting the document {0} is not successful.
Cause: Document deletion failed
Action: Examine any accompanying messages to decide if further action is required.

Level: 1

Type: WARNING

Impact: Data

MDS-10011: The operation on {0} has been rolled back. Total number of documents failed during the operation is {1}.
Cause: The transfer was rolled back
Action: Examine any accompanying messages to decide if further action is required.

Level: 1

Type: WARNING

Impact: Data

MDS-10012: The operation has failed.
Cause: The operation has failed.
Action: Examine any accompanying messages to decide if further action is required.

Level: 1

Type: WARNING

Impact: Data

MDS-10013: {0} operation started.
Cause: Transfer started.
Action: Transfer started, no action required.

Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10014: {0} is completed. Total number of documents successfully processed : {1}, total number of documents failed : {2}.
Cause: Transfer complete.
Action: Check any accompanying messages to decide if any action is required.

Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10015: Failure occurred while committing the {0} operation. The operation has been rolled back.
Cause: Failure occurred while committing the operation.
Action: Examine any accompanying messages to decide if further action is required.

Level: 1

Type: ERROR

Impact: Data

MDS-10016: The operation on {0} has been rolled back. The post transfer label {1} could not be created.
Cause: Failure occurred when creating the post transfer label.
Action: Examine any accompanying messages to decide if further action is required.

Level: 1

Type: ERROR

Impact: Data

MDS-10017: The target store does not support deployment management. Given application name "{0}" and deployment module name "{1}" could not be persisted as deployment information in store.
Cause: The target store does not support deployment management.
Action: No action required. The documents will be transferred without the deployment information attached. If you want to store deployment information as well, configure a metadata store that supports deployment management, typically a DB store.

Level: 1

Type: WARNING

Impact: Data

MDS-10018: The transfer restriction {0} is not supported in target store. All the documents will be transferred to target store.
Cause: Given transfer restriction is not supported in target store.
Action: No action required. The given restriction will not be applied to the transfer, all the documents will be transferred to target store.

Level: 1

Type: WARNING

Impact: Data

MDS-10019: The deployment information for application name "{0}" and module name "{1}" ignored since transfer operation is of type "{2}".
Cause: The deployment information will not be processed in transfer operation type other than "Deployment".
Action: No action required. Given deployment information will not be processed in the current transfer operation.

Level: 1

Type: WARNING

Impact: Data

MDS-10020: Querying checksum data from target repository to avoid transferring unchanged documents.
Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10022: Query to get the checksum of the documents from target repository completed successfully.
Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10023: No valid exclusion rules are specified in mds-transfer-config.xml to preserve documents in target store.
Cause: No valid namespaces or metadata object names specified in /meta-inf/mds-transfer-config.xml to preserve the documents in target store.
Action: No action required.

Level: 1

Type: WARNING

Impact: Data

MDS-10024: Preparing the list of documents to be excluded during transfer as per the configuration given in mds-transfer-config.xml.
Cause: To preserve the documents in target store as specified in the given /meta-inf/mds-transfer-config.xml, MDSTransfer prepares the list of documents to be excluded by looking at source and target stores.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10025: Following metadata paths are configured in mds-transfer-config.xml to preserve existing documents under this metadata path in target repository. Configured metadata paths are as follows {0}:
Cause: Some metadata paths are configured in mds-transfer-config.xml to preserve existing documents in target repository.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10026: Following Metadata object names are configured in mds-transfer-config.xml to preserve existing metadata objects with same name in target repository. Configured metadata object names are {0}:
Cause: Some metadata object names are configured in mds-transfer-config.xml to preserve existing documents in target repository.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10027: To preserve documents in target store, the following documents from source store are marked as excluded by transfer {0}.
Cause: To preserve documents in target store, some documents from source store are marked as excluded by transfer.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11001: The type information for "{0}" is not obtainable though the document exists in the MetadataStore.
Cause: Could not get type information for a document, a possibly non-wellformed XML document.
Action: Examine the document

Level: 1

Type: WARNING

Impact: Data

MDS-11002: The type information for "{0}" is not obtainable because of exception "{1}"
Cause: Failed to get type information because an exception was raised.
Action: Examine the exception and the document.

Level: 1

Type: WARNING

Impact: Data

MDS-11003: Failed to force timestamp advance on file {0}: original timestamp = {1}, new timestamp = {2}.
Cause: Failed to advance the timestamp on a file which is being saved.
Action: Examine the file and its permissions.

Level: 1

Type: WARNING

Impact: Data

MDS-11006: Directory {0} does not exist.
Cause: The value of a name condition package did not have a corresponding file system directory.
Action: Check if the directory was expected and determine why it is not present.

Level: 1

Type: NOTIFICATION

Impact: Files

MDS-11007: Skipping directory {0} because {1} does not match the condition.
Cause: The query considered the given directory, but it could only contain documents that would not match the query.
Action: If you expected results from the directory, check that the query is correctly specified.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

MDS-11008: Skipping directory {0} because it is a filestore root.
Cause: The query considered the directory, but it was another root path of the metadata store. This can arise when file store configuration includes multiple root paths and one of these is contained in another.
Action: If you expected results from the directory, check that the file store is configured correctly.

Level: 1

Type: NOTIFICATION

Impact: Files

MDS-11009: Skipping directory {0} because {1} is not a valid package name.
Cause: The query skipped the directory because the corresponding package name is invalid.
Action: If you expected results from the directory, check the directory name for validity.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

MDS-11010: Document cache {0} exceeds its maximum number of entries {1}, so the cache is cleared.
Cause: The document cache exceeded its defined maximum size so it was cleared. If memory allows, the cache should be large enough for all documents for optimum performance but this is not required.
Action: Edit the adf-config.xml file and increase the size of the document cache.

Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11011: Attempting to get failover connection to retry the operation because the database connection failed.
Cause: The connection to the database failed.
Action: No action is required. The database is configured with FCF so failover will be attempted.

Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11012: Cache collision has been detected when adding key {0}, label set {1}, sandbox name {2}, scope {3}.
Cause: The described document was being added to the cache, but it was already present. This can be caused by an incorrect miss in the preceding lookup, or very rarely by the document having been just inserted by another thread.
Action: If this occurs frequently, contact Oracle Support Services.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

MDS-11013: Cannot store the object of type {0} in the Java Object Cache because the cache or cache region is full
Cause: A CacheFullException or RegionFullException was reported when attempting to store an object in the Java Object Cache.
Action: Consider increasing the size of the configured MDS Cache by modifying the cache-config entry in adf-config.xml.

Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11014: Purge-Repos Diagnostics [auto-purge, partition-name, partition-id, #versions purged]: [{0}, {1}, {2}, {3}].
Cause: An auto-purge occurred on a metadata-store.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11016: MDS JSP Integration has been configured in Developer Mode to allow changes to files to be detected. Do not use this mode for production or performance testing.
Cause: Developer Mode is configured as a servlet initialisation parameter either explicitly or because the application is being run within JDeveloper.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11017: Started creating the final archive file at {0}.
Cause: ArchiveMetadataStore has started to create final archive file with all the changes done on the archive file so far.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11018: The final archive file has been created successfully. The archive file is available at {0}.
Cause: ArchiveMetadataStore has created final archive file with all the changes done on the archive file so far.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11019: The default CharSet {0} is not a unicode character set. File names with non-ASCII characters may not operate as expected. Check locale settings.
Cause: The Java default CharSet is used to convert file names to and from Java Strings. When this CharSet is a non-unicode character encoding, filenames that contain non-ASCII characters may not be correctly mapped to Java characters.
Action: Check the locale environment variable settings for the process that is running the JVM that MDS is running in to ensure that a UTF encoding is being used. For example, the LC_ALL and LANG settings may be relevant.

Level: 1

Type: WARNING

Impact: Configuration

MDS-11020: Cannot delete the intermediary archive file {0}.
Cause: The intermediary archive file could not be deleted.
Action: Try deleting the file outside of MDS.

Level: 1

Type: WARNING

Impact: Other

MDS-90013: The metadata partition with name "{0}" does not exist in the metadata repository "{1}".
Cause: The metadata partition with the specified name was not found in the metadata repository.
Action: Create a metadata partition with the specified name in the metadata repository before trying this operation.

Level: 1

Type: ERROR

Impact: Topology

MDS-90014: cannot update the metadata because the application is read-only
Cause: No metadata update was made because the ReadOnlyMode attribute was enabled.
Action: Disable the ReadOnlyMode attribute of the target application configuration.

Level: 1

Type: ERROR

Impact: Topology

MDS-90015: The metadata repository with name "{0}" does not exist.
Cause: The metadata repository with the specified name was not found.
Action: Verify that the repository name is spelled correctly. If the repository does not exist, create one with the specified name and try again.

Level: 1

Type: ERROR

Impact: Topology

MDS-90016: There are no applications deployed to partition "{0}".
Cause: An attempt was made to perform this operation on a partition that is not associated with a deployed application.
Action: Specify a partition that is associated with a deployed application.

Level: 1

Type: ERROR

Impact: Topology

MDS-90017: The application to be used for this operation is not specified.
Cause: Could not determine which application configuration to use for this operation since there is more than one application deployed to partition "{0}".
Action: Specify an application that is deployed to partition "{0}" to be used for this operation.

Level: 1

Type: ERROR

Impact: Topology

MDS-90018: Application "{1}" is not deployed to partition "{0}".
Cause: The specified application was not deployed to the specified partition.
Action: Specify an application that is deployed to the partition.

Level: 1

Type: ERROR

Impact: Topology

MDS-90019: cannot set the user property on the driver: {0}
Cause: A problem occurred while setting the user property on the driver.
Action: Ensure that the database server is running properly.

Level: 1

Type: ERROR

Impact: Topology

MDS-90020: Metadata store cannot be assigned to server "{0}".
Cause: A problem occurred while assigning resource to the server.
Action: Ensure that the server is running properly.

Level: 1

Type: ERROR

Impact: Topology

MDS-90021: Metadata path {0} is invalid.
Cause: The path used to create a FileMetadataStore was invalid. It must point to a directory.
Action: Correct the metadata path.

Level: 1

Type: ERROR

Impact: Topology

MDS-90022: The host name of the database repository cannot be empty.
Cause: The host name of the database repository was empty or null.
Action: Use a valid host name.

Level: 1

Type: ERROR

Impact: Topology

MDS-90023: The database name of the database repository cannot be empty.
Cause: The database name of the database repository was empty or null.
Action: Use a valid database name.

Level: 1

Type: ERROR

Impact: Topology

MDS-90024: The user name of the database repository cannot be empty.
Cause: The user name of the database repository was empty or null.
Action: Use a valid user name.

Level: 1

Type: ERROR

Impact: Topology

MDS-90025: The password of the database repository cannot be empty.
Cause: The password of the database repository was empty or null.
Action: Use a valid password.

Level: 1

Type: ERROR

Impact: Topology

MDS-90026: The server name cannot be empty.
Cause: The server name was empty or null.
Action: Use a valid server name.

Level: 1

Type: ERROR

Impact: Topology

MDS-90027: cannot find server "{1}" to register the metadata repository "{0}"
Cause: The server name was invalid.
Action: Use a valid server name.

Level: 1

Type: ERROR

Impact: Topology

MDS-90028: Metadata repository with name "{0}" already exists.
Cause: Metadata repository with the specified name already exists.
Action: Verify that the repository name is spelled correctly. If the repository already exists, create one with a different name and try again.

Level: 1

Type: ERROR

Impact: Topology

MDS-90029: The metadata db repository with name "{0}" does not exist.
Cause: The metadata db repository with the specified name was not found.
Action: Verify that the db repository name is spelled correctly.

Level: 1

Type: ERROR

Impact: Topology

MDS-90030: The metadata file repository with name "{0}" does not exist.
Cause: The metadata file repository with the specified name was not found.
Action: Verify that the file repository name is spelled correctly.

Level: 1

Type: ERROR

Impact: Topology

MDS-90031: The JDBC resource of metadata db repository "{0}" cannot be found.
Cause: The JDBC resource was not found.
Action: Verify that the metadata db repository is set up correctly.

Level: 1

Type: ERROR

Impact: Topology

MDS-90032: The metadata store of metadata file repository "{0}" cannot be found.
Cause: The metadata store was not found.
Action: Verify that the metadata file repository is set up correctly.

Level: 1

Type: ERROR

Impact: Topology

MDS-90033: unknown DB vendor code: "{0}"
Cause: The DB vendor code is invalid.
Action: Use a valid DB vendor code, such as 0 (ORACLE), 1 (MSSQL), or 2 (IBMDB2).

Level: 1

Type: ERROR

Impact: Topology

MDS-90034: The source directory or archive "{0}" for importing metadata is invalid.
Cause: The directory or archive location used to import metadata was invalid. It must point to a valid, existing directory or archive.
Action: Correct the source directory or archive location.

Level: 1

Type: ERROR

Impact: Topology

MDS-90035: The target directory or archive "{0}" for exporting metadata is invalid.
Cause: The directory or archive location used to export metadata was invalid. It must point to a valid location.
Action: Correct the target directory or archive file location.

Level: 1

Type: ERROR

Impact: Topology

MDS-90036: The application does not have a valid MAR file path.
Cause: The MAR path used to import MAR was invalid. It must point to a valid, existing MAR file.
Action: Make sure the MAR file exists and is located in the correct directory of the application.

Level: 1

Type: ERROR

Impact: Topology

MDS-90037: The archive "{0}" does not contain valid contents.
Cause: The archive used to import metadata was invalid. It must be to a valid, existing zip or jar file.
Action: Make sure the archive is valid.

Level: 1

Type: ERROR

Impact: Topology

MDS-90038: The database authentication alias "{0}" already exists. To reuse the same authentication alias, try the operation again without specifying user and password.
Cause: An attempt was made to configure a database authentication alias that already existed in Websphere server.
Action: Delete the existing authentication alias and try again, or specify a new authebtication alias, or reuse the existing authentication alias by not specifying user and password.

Level: 1

Type: ERROR

Impact: Topology

MDS-90039: The database authentication alias "{0}" cannot be found. To create the authentication alias, try the operation again with user and password specified.
Cause: An attempt was made to use a database authentication alias that was not configured in Websphere server.
Action: Make sure the specified database authentication alias is properly configured in Websphere server, or automatically create the authentication alias by specifying user and password.

Level: 1

Type: ERROR

Impact: Topology

MDS-90040: failed to connect to database
Cause: An error occurred when trying to connect to database.
Action: Make sure the database connection details are correct. Look at the cause exception for more details.

Level: 1

Type: ERROR

Impact: Topology

MDS-90041: Customization layer values are not supported for "excludeCustFor" parameter.
Cause: One or more customization layer values was specified for "excludeCustFor" parameter.
Action: Make sure there are no customization layer values specified for "excludeCustFor" parameter.

Level: 1

Type: ERROR

Impact: Topology

MDS-91001: MDS domain runtime MBean is not available. "{0}" operation failure.
Cause: MDS domain runtime MBean was not available in the server.
Action: Ensure the MDS domain runtime MBean is available in the server.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91002: MDS Application runtime MBean for "{0}" is not available. "{1}" operation failure.
Cause: MDS Application runtime MBean was not available in the server.
Action: Ensure the MDS Application runtime MBean for the application is available in the server.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91003: Multiple MDSAppRuntimeMBean exist for "{0}". To execute the command, parameter "applicationVersion" is required. "{1}" operation failure.
Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.
Action: Provide the 'applicationVersion' parameter.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91004: MDS domain runtime MBean commands can be executed only from the Admin server. "{0}" operation failure.
Cause: WLST was not connected to the Admin server.
Action: Connect to an Admin server before executing the command.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91005: No connection to a "{0}" server exists. The operation "{1}" can be executed only in the online mode.
Cause: Command was executed in the offline mode.
Action: Ensure WLST/WSADMIN is connected to the server.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91006: Expecting a "{0}" for parameter "{1}" but encountering "{2}". "{3}" operation failure.
Cause: Parameter type passed to the command was not correct.
Action: Ensure the correct type of parameters are passed to the command.

Level: 1

Type: ERROR

Impact: Data

MDS-91007: dbVendor should be one of ORACLE, MSSQL, or IBMDB2. "{0}" operation failure.
Cause: dbVendor value was not correct.
Action: Ensure the dbVendor value is one of ORACLE, MSSQL, or IBMDB2.

Level: 1

Type: ERROR

Impact: Data

MDS-91008: The "{0}" parameter is required. Provide a valid value and retry the operation.
Cause: Required parameter for the command was not given.
Action: Provide the required parameters for the command.

Level: 1

Type: ERROR

Impact: Data

MDS-91009: Operation "{0}" failure.
Cause: Exception occurred during the execution of the command.
Action: Provide the required parameters for the command.

Level: 1

Type: ERROR

Impact: Data

MDS-91010: The "adf-config" element is not available in the given archive file. "{0}" operation failure.
Cause: The "adf-config" element is not available in the given archive file.
Action: Ensure the "adf-config" element is available in the adf-config.xml of the given archive file.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91011: No "mds-config" element exists in the adf-config.xml of the given archive. "{0}" operation failure.
Cause: No mds-config element existed in the adf-config.xml file of the archive file.
Action: Ensure the "mds-config" element is available in the adf-config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91012: Metadata repository connection type value should be either "File" or "DB". "{0}" operation failure.
Cause: Metadata repository connection type value is not correct.
Action: Ensure the metadata repository connection type value is either 'File' or 'DB'.

Level: 1

Type: ERROR

Impact: Data

MDS-91013: For the metadata repository''s DB connection type, JNDI location is a required parameter. "{0}" operation failure.
Cause: JNDI location not provided for DB connection type.
Action: Provide the JNDI location string while updating the repository connection to DB.

Level: 1

Type: ERROR

Impact: Data

MDS-91014: For the metadata repository''s File connection type, path location is a required parameter. "{0}" operation failure.
Cause: The path value was not provided for File connection type.
Action: Provide the path location string while updating the repository connection to File.

Level: 1

Type: ERROR

Impact: Data

MDS-91015: All parameters are required to update shared metadata repository configuration in adf-config.xml. At present, source archive has no connection details for the namespace "{0}". "{1}" operation failure.
Cause: Complete connection information was not provided to set the shared repository for the given namespace.
Action: Provide complete connection information in case the adf-config.xml file does not have any metadata repository connection information for the given namespace already.

Level: 1

Type: ERROR

Impact: Data

MDS-91016: All parameters are required to define new application metadata repository configuration in adf-config.xml. The source archive configuration does not contain any application metadata repository at present. "{0}" operation failure.
Cause: Complete connection information was not provided to set the application target repository.
Action: Provide complete connection information in case the adf-config.xml does not have any metadata repository connection information for the application target repository already.

Level: 1

Type: ERROR

Impact: Data

MDS-91017: The given namespace "{0}" to set the shared repository is not valid. Ensure that the namespace is available in the adf-config.xml file and it is not a sub-namespace of any other namespace. "{1}" operation failure.
Cause: The namespace provided to set the shared repository details is not valid.
Action: Ensure that the namespace is available in the adf-config.xml file and it is not a subnamespace of any other namespace in that file.

Level: 1

Type: ERROR

Impact: Data

MDS-91018: No namespaces are mapped to any shared repository in the source archive adf-config.xml configuration file. Shared repository details cannot be set. "{0}" operation failure.
Cause: No namespaces were mapped to any shared repository in the source archive adf-config.xml configuration file.
Action: To set the shared repository connections, ensure at least one namespace is mapped to shared repository in the source archive adf-config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91019: Multiple MDSAppRuntimeMBean exist for application "{0}". Ensure that the "application" "node" and "server" parameters are correct. "{1}" operation failure.
Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.
Action: Ensure that the "application" "node" and "server" parameters are correct.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91020: MDS Application runtime MBean for "{0}" is not available in server "{2}". Ensure server name and application name are correct. "{1}" operation failure.
Cause: MDS Application runtime MBean was not available in the server.
Action: Ensure the MDS Application runtime MBean for the application is available in the server. Ensure the server name and the application name are correct.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91021: Multiple MDSAppRuntimeMBean exist for "{0}" in server "{2}". To execute the command, parameter "applicationVersion" is required. "{1}" operation failure.
Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.
Action: Provide the 'applicationVersion' parameter.

Level: 1

Type: ERROR

Impact: Configuration

MDS-91022: Parameter "{0}" cannot be an empty string. "{1}" operation failure.
Cause: The parameter is not allowed to be an empty string.
Action: Ensure the parameter has a correct value.

Level: 1

Type: ERROR

Impact: Data

MDS-91023: Parameter "{0}" contains at least one empty element. "{1}" operation failure.
Cause: The parameter is not allowed to contain one or more empty elements.
Action: Ensure every element specified in the parameter is correct.

Level: 1

Type: ERROR

Impact: Data