MDS-00001 to MDS-92010

18 MDS-00001 to MDS-92010

MDS-00001: exception in Metadata Services layer
Category:: Programmatic
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.

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

MDS-00003: error connecting to the database
Category:: Configuration
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.

MDS-00005: unable to find XML element or text "{0}"
Category:: Programmatic
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.

MDS-00008: Attribute "{0}" is not allowed for element {1} namespace {2} in metadata object {3}.
Category:: Programmatic
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.

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

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

MDS-00012: invalid value "{0}" for attribute {1} (type = "{2}") in metadata object {3}
Category:: Data
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.

MDS-00013: no metadata found for metadata object "{0}"
Category:: Data
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.

MDS-00015: Translation ignored in document "{0}": element with localRef "{1}" not found
Category:: Data
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.

MDS-00016: Ignoring customization for instruction type "{0}" in metadata object "{1}" for customization layer "{2}"/"{3}": not finding element with local reference "{4}"
Category:: Data
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.

MDS-00017: Customization instruction generated for "{0}" uses local reference(s) : "{1}" which is not upgrade safe.
Category:: Data
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.

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.
Category:: Data
Cause:: A customization was fixed because the referenced element was not found.
Action:: Correct the customized element's position if needed.

MDS-00019: Customization document contains an invalid instruction "{0}".
Category:: Data
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.

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

MDS-00029: Invalid namespace: The namespace "{0}" has not been registered with the MetadataManager.
Category:: Configuration
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.

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

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

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

MDS-00035: cannot load the class: {0}.
Category:: Configuration
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.

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

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

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

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

MDS-00041: invalid classpath entry "{0}"
Category:: Configuration
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.

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

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

MDS-00044: Metadata for MetadataObject with name {0} already exists in the configured store.
Category:: Configuration
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.

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

MDS-00054: The file to be loaded {0} does not exist.
Category:: Configuration
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.

MDS-00058: Invalid Metadata Path: Metadata Path cannot be null.
Category:: Configuration
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.

MDS-00068: Element with local name = {0}, namespace = {1} is not expected under Parent Element = {2} in document location = {3}
Category:: Configuration
Cause:: While parsing a document, a request was made to locate a type definition whose usage is either not defined or is not expected for the parent element within the schema definition.
Action:: Check the xml source and any customizations to be applied and ensure that the element with the given namespace is defined and in the correct location as specified by the schema definition.

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

MDS-00085: Parameter {0} is missing.
Category:: Programmatic
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.

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

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}.
Category:: Programmatic
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.

MDS-00091: Unable to customize {0}, empty or null value for tip customization layer {1}
Category:: Configuration
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.

MDS-00092: DuplicateNodeException. The same bean instance {0} already exists in document {1}.
Category:: Programmatic
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.

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

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

MDS-00095: The support to transfer customization documents based on the CustConfig and excluding customization documents of specific customization layers is not yet available.
Category:: Programmatic
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 customization layers.

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

MDS-00153: invalid value for indicator
Category:: Data
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.

MDS-00154: The ContentHandler {0} does not implement org.xml.sax.ext.LexicalHandler.
Category:: Programmatic
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.

MDS-00155: unable to create a JSP file for document {0}
Category:: Files
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.

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

MDS-00157: unable to write to JSP file {0}
Category:: Files
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.

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

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

MDS-00160: no local name has been specified for a resource
Category:: Programmatic
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.

MDS-00161: no local name has been specified
Category:: Programmatic
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.

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

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

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

MDS-00165: metadata Object "{0}" has changed
Category:: Data
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.

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

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

MDS-00168: MDS object {0} is being used after it or its MDSInstance or PManager has been released.
Category:: Session
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.

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}".
Category:: Programmatic
Cause:: The MDS instance cannot be used until metadata deployment has finished.
Action:: Try again later after metadata deployment has completed.

MDS-00170: The MDS instance is not usable because metadata deployment failed with status "{0}".
Category:: Configuration
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.

MDS-00171: Document "{0}" already has unsaved updates on another instance of this metadata object in this session.
Category:: Data
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.

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.
Category:: Data
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.

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

MDS-00174: A tenant scoped MDSInstance {0} is being requested with a null TenantId.
Category:: Session
Cause:: A tenant scoped MDSInstance was requested passing null for TenantId.
Action:: Supply a non null TenantId or request an unscoped MDSInstance.

MDS-00176: The operation on MDSInstance {0} cannot be performed as it is not tenant scoped.
Category:: Session
Cause:: The operation performed on the MDSInstance was invalid with a TenantId because it was not a tenant scoped MDSInstance.
Action:: Perform the operation on an MDSInstance initialized for multitenant operation.

MDS-00177: The operation on resource {0} cannot be performed as it is not configured to be owned by the current tenant scope.
Category:: Session
Cause:: The operation performed was illegal as the resource being created, updated or deleted has global scope and the current scope is tenant or the resource has tenant scope and the current tenant is global.
Action:: Check that the configuration of the namespaces and CustomizationClasses is correct and that the correct customization class list is being used.

MDS-00178: Multitenant MDSInstance {0} cannot be returned as a non-multitenant MDSInstance was requested with the current persistence configuration.
Category:: Session
Cause:: The configuration at the time the MDSInstance was requested did not match with the configuration when it was originally created.
Action:: Request an MDSInstance appropriate to the configuration.

MDS-00179: The requested MDSInstance {0} cannot be returned for TenantId {1} as it was originally created with multitenant enabled = {2}.
Category:: Session
Cause:: The configuration at the time the MDSInstance was requested did not match with the configuration when it was originally created.
Action:: Request an MDSInstance appropriate to the original configuration.

MDS-00180: Only a single tenant cache configuration is allowed.
Category:: Session
Cause:: The number of TenantCacheConfigs was not 1.
Action:: Pass a single tenant cache configuration object. Although the constructor for the TenantCacheConfigs class takes an array this is reserved for future use.

MDS-00181: Only a single tenant document cache configuration is allowed.
Category:: Session
Cause:: The number of TenantDocumentCacheConfigs was not 1.
Action:: Pass a single tenant document cache configuration object. Although the constructor for the TenantDocumentCacheConfigs class takes an array this is reserved for future use.

MDS-00182: Tenant cache configuration information cannot be requested for the global tenant.
Category:: Session
Cause:: Tenant cache configuration information was being requested for the global tenant.
Action:: Do not request the tenant cache configuration for the global tenant - use getCacheConfig directly from MDSConfig

MDS-00183: Tenant document cache configuration information cannot be requested for the global tenant.
Category:: Session
Cause:: Multitenant document cache information was being requested for the global tenant.
Action:: Do not request the tenant document cache configuration for the global tenant - use getDocumentCacheConfig from NamespaceConfig

MDS-00184: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with cascade delete enabled.
Category:: Session
Cause:: Relationships with cascade delete enabled were spanning tenant boundaries.
Action:: Reconfigure the relationship with cascade delete disabled or ensure the parent reference is within the same tenant scope.

MDS-00185: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with enforced integrity.
Category:: Session
Cause:: Relationships with defined referential integrity were spanning tenant boundaries.
Action:: Reconfigure the relationship without referential integrity or ensure the parent reference is within the same tenant scope.

MDS-00186: A {0} element is already present in the parent {1} element in document {2}, but with the QNameLUID identification mechanism only one is allowed.
Category:: Data
Cause:: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.
Action:: Remove duplicate instances of elements with same QName

MDS-00187: The existing {0} element in the parent {1} element in document {2} is automatically removed, and new customized {0} element of "{3}"/"{4}" customization layer is inserted since with the QNameLUID identification mechanism, only one is allowed.
Category:: Data
Cause:: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.
Action:: Removed duplicate instances of elements with same QName

MDS-00188: The relationship from {0} to {1} is invalid because the latter is configured as a tenant resource and cannot be referenced from a global resource.
Category:: Session
Cause:: An attempt was made to reference a tenant resource from a global resource.
Action:: Ensure all references from global resources are also global.

MDS-00189: The existing {0} element with unique id {1} in the parent {2} element in document {3} is automatically removed, and new customized {0} element with unique id {1} of "{4}"/"{5}" customization layer is inserted since {0} element is type-annotated to overwrite duplicates.
Category:: Data
Cause:: An attempt was made to have two or more elements with same QName under same parent having the same unique ID value while overwriteDuplicate mechanism is used.
Action:: Removed duplicate instances of elements with same QName having the same unique ID value

MDS-00190: A call to {0} on the current MDSSession does not specify the correct transaction key
Category:: Session
Cause:: The current MDS Session was created using a transaction key and the subsequent operation was either being attempted passing no key or a different one from that originally used.
Action:: If the MDS Session is created using a transaction key, then use the MDSSession API's that take a transaction key and use the same key.

MDS-00191: An exception occurred in PChangeListener {0}
Category:: Session
Cause:: The MetadataStoreCommunicator was attempting to notify the listener when an exception occurred.
Action:: Check the HandlePChanges method of the listener.

MDS-00192: Validation of {0} caused a NullPointerException: check there is an MDS bean object set on the MDS bean MO
Category:: Data
Cause:: This error most typically occurs when a Bean MO has been created but no bean object has been set on it.
Action:: Check that an MDS bean is set on this MO. Failing that, examine the stack for clues for alternative causes.

MDS-00193: Document with the MDSReference {0} contains an ID attribute with an invalid value: {1}
Category:: Data
Cause:: The value of the ID attribute is invalid according to the schema definition.
Action:: Ensure that the ID conforms to the schema definition .

MDS-00194: Auditing is disabled for component {0}.
Category:: Configuration
Cause:: There was an error registering the audit event definition(s) for the component.
Action:: Ensure that the audit event definitions for the component are valid and that the audit service is functional.

MDS-00195: The custom audit event of type "{0}" that was associated with "{1}" is not audited because the MDS object was unmodified since the last time the changes in the MDSSession were committed.
Category:: Programmatic
Cause:: MDS object associated with the event was unmodified since the last time the changes in the MDSSession were committed. A custom audit event is discarded if the associated MDSObject is not modified.
Action:: No action required.

MDS-00196: The MDSSession referenced by the audit component "{0}" is invalid.
Category:: Programmatic
Cause:: The MDS audit support instance is being used even after the MDSSession that was used to created it is no longer referenced.
Action:: Fetch the audit support instance from the MDSSession and retry the operation.

MDS-00197: An internal error occurred when processing MetadataObject {0} with document {1}.
Category:: Session
Cause:: An error occurred in the LayeredCache processing.
Action:: Check for log messages. If the problem persists, clear the MDS cache and contact Oracle Support Services.

MDS-00198: The requested object is deleted in the current PTransaction
Category:: Data
Cause:: The requested document was deleted in an earlier part of the PTransaction and not replaced.
Action:: Review whether the document needed to be deleted or replace with a new version.

MDS-00199: The requested object is deleted in the current MDSSession
Category:: Data
Cause:: The requested document was deleted in an earlier part of the MDSSession and not replaced.
Action:: Review whether the document needed to be deleted or replace with a new version.

MDS-00200: Reference not found in Document
Category:: Data
Cause:: Unable to locate the reference within the named Metadata Object.
Action:: Check that the reference is correct.

MDS-00201: PDocument not found in MetadataStore : {0}
Category:: Data
Cause:: The requested persistence document was not found in the given MetadataStore.
Action:: Check that the requested name is correct and that the store is mapped to the namespace correctly .

MDS-00202: The Document was not found on the classpath
Category:: Data
Cause:: The requested document was not found on the classpath.
Action:: Check that the document is available on the classpath as a resource .

MDS-00203: An error occurred while attempting to process Element "{0}" from customization document {1} because the change conflicts with information in the base document or changes made by a prior customization
Category:: Data
Cause:: An error occurred during parsing of a customization - see cause.
Action:: Check for any conflicts between the customization and recent changes to the base document or other customizations being applied.

MDS-00204: Remove customization fails on element with local reference "{0}" in document "{1}"
Category:: Programmatic
Cause:: An attempt to remove a customization from an element has failed.
Action:: Reproduce the customization document without the desired customization.

MDS-00205: Unexpected error in ChangeEventParseEngine
Category:: Programmatic
Cause:: An error in the ChangeEventParseEngine.
Action:: Check for log messages. If the problem persists, contact Oracle Support Services.

MDS-00206: Unexpected error while collecting ElementTipCustInfo for a customized element
Category:: Programmatic
Cause:: An error occurred while gathering ElementTipCustInfo for a customized element.
Action:: Check for log messages. If the problem persists, contact Oracle Support Services.

MDS-00207: Cached Object {0} was removed from the MDS cache by thread {1} while being read. Retrying the read.
Category:: Session
Cause:: An object being accessed by MDS was removed from the cache before it could be used to return the requested data.
Action:: The notification can occur if there are concurrent updates to objects cached by MDS. If the notification persists review the MDS cache configuration.

MDS-00208: Root node deleted but not replaced.
Category:: Programmatic
Cause:: The root node of an XML document was deleted, but no replacement node was inserted.
Action:: Insert a replacement root node after deleting the root node.

MDS-00209: Exception adding logging data: " {0}".
Category:: Programmatic
Cause:: An exception was raised in the MDS diagnostic log processing.
Action:: Examine logs for the full exception stack and underlying cause.

MDS-00210: The TenantId supplied {0} does not match the current tenant context: {1}.
Category:: Session
Cause:: A TenantId was supplied to MDS that does not match the TenantId provided by the context.
Action:: Remove the TenantId from the deprecated API or correct the TenantId supplied.

MDS-00211: Action is not allowed on a tenant-specific MetadataStoreCommunicator.
Category:: Programmatic
Cause:: An attempt was made to invoke a method that is not allowed on a non-global tenant
Action:: This change has to be made in a global tenant context.

MDS-00212: Unable to execute a task in the DOMAIN partition in application {0} because the application in the DOMAIN partition is not currently in RUNNING state, or this is a Java SE application that has not initialized MDS in the DOMAIN context.
Category:: Session
Cause:: A task runner was required but unable to be found.
Action:: Ensure that the MDS application lifecycle listener is configured, or that MDS is initialized in the global tenant context before running in any other tenant context.

MDS-00213: It was not possible to lock the cached RootNode with root key {0}.
Category:: Session
Cause:: An error occurred in the LayeredCache processing due to cache contention on a specific object.
Action:: Check for log messages. If the problem persists, clear the MDS cache and contact Oracle Support Services.

MDS-00214: Error encountered while processing root node replacement customization instruction in tip customization layer document.
Category:: Programmatic
Cause:: The customization instructions in tip customization document might be corrupted.
Action:: Check for log messages. If the problem persists, contact Oracle Support Services.

MDS-00215: TenantId is not supported. Please use equivalent ServiceId api.
Category:: Programmatic
Cause:: An attempt was made to invoke MDS deprecated APIs with TenantId.
Action:: Replace TenantId based API with ServiceId based API.

MDS-00216: Notification Manager for MDSInstance {0} was unable to get an application scoped executor for dispatching events in the application context - using a global executor instead.
Category:: Session
Cause:: An attempt was made to get an application scoped executor outside of an application.
Action:: Check if the request should be running within the scope of an application.

MDS-00217: Notification Manager for MDSInstance {0} was unable to get an application scoped contextual proxy for dispatching global events in the tenant context - using a global contextual proxy instead.
Category:: Session
Cause:: An attempt was made to get an application scoped contextual proxy outside of an application.
Action:: Check if the request should be running within the scope of an application.

MDS-00218: Cannot create ServiceId with null Service UUID.
Category:: Configuration
Cause:: An attempt was made to create an MDS ServiceId with a null value.
Action:: Check lifecycle-config.xml and ensure that each 'service' element contains an 'id' attribute defined with a UUID value.

MDS-00219: Invalid resource passed to MDSFaceletsHelper: {0}.
Category:: Programmatic
Cause:: An invalid resource was passed to MDSFaceletsHelper.
Action:: Check exception message. Consider enabling oracle.mds.jrf logging for additional diagnostics.

MDS-00220: Document {0} to be loaded does not exist for label {1}.
Category:: Configuration
Cause:: An attempt was made to load a persistent document using a URL but the underlying document was not found in the DB MetadataStore.
Action:: Check that the document name is correct and that the DB MetadataStore and Label are correctly configured.

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

MDS-00222: Invalid value "{0}" for {1} attribute (type = "{2}").
Category:: Programmatic
Cause:: An attempt was made to read or write an invalid attribute value.
Action:: Double-check the value and attribute type.

MDS-00223: Unable to retrieve pinned Customization Class value from Unified Sandbox For CustomizationClass : {0} with Name {1}.
Category:: Runtime
Cause:: An attempt was made to read a customization value with AutoMergeOverrideValue.PINNED, but no value was retreived from the Unified Sandbox.
Action:: Ensure Unified Sandbox is able to return a pinned value for this Customization Class.

MDS-00224: Customization of {0} Location: {1} is not permitted due to a package level restriction in the cust-restriction-library-config element of the mds-library-config.xml at jar/zip level.
Category:: Runtime
Cause:: A jar level restriction on customization has been specified for objects in this package in the cust-restriction-library-config element of the mds-library-config.xml file.
Action:: Check if customization of this object should be allowed and correct the entries in cust-restriction-library-config at the jar/zip level.

MDS-00225: Updating immutable StreamedObject "{0}" is not allowed.
Category:: Programmatic
Cause:: The StreamedObject being updated was immutable.
Action:: Ensure that the StreamedObject to be updated is mutable.

MDS-00226: Unable to determine the MDSContext while processing cached MDS content : {0}
Category:: Runtime
Cause:: An attempt was made to access an MDSContext but an MDSContext is not presently available to this thread.
Action:: Check for logged diagnostic messages, clear the MDS cache and if the problem persists contact Oracle Support Services.

MDS-00227: Failure in MDS Java Flight Recorder integration processing.
Category:: Configuration
Cause:: A failure occurred in MDS JFR integration processing.
Action:: Examine the exception for clues. Check the JVM FlightRecorder options.

MDS-00228: No MOParseListener instance provided to MOParseListenersBuilder to build MOParseListeners instance.
Category:: Programmatic
Cause:: An attempt was made to build MOParseListeners instance using MOParseListenersBuilder without providing any instances of MOParseListener.
Action:: Provide at least one instance of MOParseListener before building MOParseListeners instance using MOParseListenersBuilder.

MDS-00229: DuplicateRefException occurred while attempting to process prior customization layer.
Category:: Data
Cause:: There exists two or more elements with same id value in base document and/or prior customization layers.
Action:: Fix elements with duplicate id value in prior customization layers before processing tip customization layer.

MDS-00230: Unexpected metadata object parse error.
Category:: Programmatic
Cause:: An unexpected metadata object parse error occurred.
Action:: Check DupIdInsertResolver instance usage.

MDS-00231: ReplaceProcessingOption NOT a valid available ProcessingOption.
Category:: Data
Cause:: An attempt was made to use DupIdElementsFilter.REPLACE_PO to fetch collection of DupIdElementInfo instances while ReplaceProcessingOption is NOT a valid available ProcessingOption.
Action:: Ensure to use DupIdElementsFilter associated to valid available ProcessingOption.

MDS-00232: Selected resolution is NOT amongst one of the available ProcessingOptions.
Category:: Data
Cause:: An attempt was made to use a resolution which is NOT amongst one of the available ProcessingOptions.
Action:: Ensure to use resolution which is amongst one of the available ProcessingOptions.

MDS-00233: Selected resolution is NOT amongst one of the available CustApplyOptions.
Category:: Data
Cause:: An attempt was made to use a resolution which is NOT amongst one of the available CustApplyOptions.
Action:: Ensure to use resolution which is amongst one of the available CustApplyOptions.

MDS-00234: RestrictedSession in CustClassContext should not be null
Category:: Data
Cause:: An attempt was made to create an instance of CustClassContext without specifying a value for RestrictedSession.
Action:: Ensure a non null value is provided to CustClassContext.Builder.withRestrictedSession.

MDS-00235: MOReference {0} and MetadataObject {1} are not consistent.
Category:: Data
Cause:: An attempt was made to create a CustClassContext with both a MetadataObject and an MOReference which did not relate to the same MetadataObject.
Action:: Ensure that MetadataObject and MOReference are consistent.

MDS-00236: Customization of {0} is not allowed because it is not explicitly allowed by any extended metadata entry, file type or package restriction.
Category:: Configuration
Cause:: An attempt was made to customize a StreamedObject 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: An extended metadata file, the FileTypeConfig or MDSLibraryConfig. Also check the customization policy for the MDS session in use and the customization configuration.

MDS-00237: Timed out trying to obtain a lock on the cache.
Category:: Session
Cause:: It was not possible to obtain a lock on a WeakCache after waiting 30 seconds.
Action:: Consider using a diagnostic tool such as jconsole to identify the thread that is not relinquishing this lock.

MDS-00238: Document {0} is not configured as a customizable StreamedObject.
Category:: Configuration
Cause:: The Streamed Object requested has not been configured for customization.
Action:: Ensure customization-type attribute in cust-config is set to FULL_REPLACE and that the content-type is BINARY_STREAM.

MDS-00239: Layer-specific retrieval on immutable StreamedObject "{0}" is not allowed.
Category:: Programmatic
Cause:: The StreamedObject on which a LSOLayerRetrieval method was called is immutable.
Action:: Ensure that the StreamedObject is mutable before calling LSOLayerRetrieval methods.

MDS-00240: A rest request to update a resource requires If-Match.
Category:: Session
Cause:: A rest request to update a resource was issued without specifying an ETag in the If-Match Header.
Action:: Reissue the request with a valid If-Match Content header.

MDS-00241: A rest request to update a resource specified an out of date ETag.
Category:: Session
Cause:: A rest request to update a resource specified an out of date ETag in the If-Match content Header, possibly due to the resource having been updated by another session.
Action:: Re-request the resource to obtain an up to date Etag and reissue the update.

MDS-00242: A rest request to update a resource occurred outside a unified sandbox.
Category:: Session
Cause:: The MDSSession obtained from the ADFContext was not running within a unified sandbox.
Action:: Session options on the ADFContext should use a unified sandbox.

MDS-00243: The document {0} is not within the current unified sandbox.
Category:: Session
Cause:: The document's namespace is not configured to be contained within the active unified sandbox.
Action:: Verify that the document should be updateable and amend the unified sandbox configuration accordingly.

MDS-00244: There is no current ADFContext.
Category:: Session
Cause:: The operation requires that an ADFContext be present on the current thread.
Action:: Verify that the ADFContext is configured correctly.

MDS-00245: A Customization already exists for {0} for the current layer
Category:: Session
Cause:: An attempt was made to create a new customization when one already exists.
Action:: GET the existing customization and modify via PUT.

MDS-00246: A Customization does not exist for {0} for the current layer
Category:: Session
Cause:: An attempt was made to get an existing custimization which does not exist.
Action:: Check the naming of your resource and retry the operation.

MDS-00247: No tip customization layer defined while retrieving details for {0}
Category:: Session
Cause:: Customization Layers have not been defined on the current MDSSession.
Action:: Check the customization config for your environment.

MDS-00248: No support to object-merge VBCS base document.
Category:: Data
Cause:: VBCS base document requires object-merge.
Action:: Remove conflicting VBCS base document available in sandbox and retry sandbox refresh operation.

MDS-00249: No support to object-merge VBCS base document and/or its associated non-tip layer extensions.
Category:: Data
Cause:: VBCS base document or its associated non-tip layer extensions requires object-merge.
Action:: Remove conflicting VBCS base document and/or its associated non-tip layer extensions available in sandbox and retry sandbox refresh operation.

MDS-00500: No metadata store is configured to save the document {0}.
Category:: Configuration
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.

MDS-00501: Document {0} cannot be deleted because no metadata store is configured.
Category:: Configuration
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.

MDS-00503: The metadata path "{0}" does not contain any valid directories.
Category:: Data
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.

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

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

MDS-00506: failure to get child resources of package {0} because package does not exist in metadata store
Category:: Data
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.

MDS-00507: failure to delete document {0} because metadata store "{1}" is read-only
Category:: Data
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.

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

MDS-00509: failure to delete document {0} with file {1}
Category:: Data
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.

MDS-00510: failure to read document {0} because it is not found in the metadata path "{1}"
Category:: Data
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.

MDS-00511: failure to create document {0} at file {1}
Category:: Files
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.

MDS-00512: failure to create document {0} because file {1} already exists
Category:: Files
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.

MDS-00513: failure to create package {0} because directory {1} already exists
Category:: Files
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.

MDS-00514: failure to save document {0} to file {1}
Category:: Files
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.

MDS-00515: failure to create document {0} in the metadata repository
Category:: Data
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.

MDS-00516: failure to create document {0} because it already exists in the metadata repository
Category:: Data
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.

MDS-00517: failure to create package {0} because it already exists in the metadata repository
Category:: Data
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.

MDS-00518: failure to create package {0} in the metadata repository
Category:: Data
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.

MDS-00519: failure to delete document {0} from the metadata repository
Category:: Data
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.

MDS-00520: failure to read document {0} because it is not in the metadata repository
Category:: Data
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.

MDS-00521: error while reading document {0} from metadata repository
Category:: Data
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.

MDS-00522: failure to save document {0} to the metadata repository
Category:: Data
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.

MDS-00526: failure to generate SAX parsing events for document {0}
Category:: Programmatic
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.

MDS-00531: failure to write to "{0}" because output to "{1}:" protocol is not supported
Category:: Programmatic
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.

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.
Category:: Data
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.

MDS-00534: Exception: {3} Sub-object {0} in document {2} has invalid value "{1}" for unique identifier; typed dependencies from this sub-object are not stored in the database repository.
Category:: Programmatic
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.

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

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

MDS-00537: unable to rename {0} to {1}
Category:: Data
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.

MDS-00538: failure to rename document {0} because metadata store "{1}" is read-only
Category:: Data
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.

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}.
Category:: Programmatic
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.

MDS-00541: SAX events cannot be generated for non-XML document {0}.
Category:: Programmatic
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.

MDS-00547: The read operation is not supported for packages from Web content from the servlet context.
Category:: Programmatic
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.

MDS-00550: Updates across multiple stores are not allowed in the same transaction.
Category:: Programmatic
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.

MDS-00551: failure to delete package {0} because it is not empty
Category:: Data
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.

MDS-00552: failure to delete package {0} with directory {1}
Category:: Files
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.

MDS-00554: Package {0} cannot be found in the specified store.
Category:: Programmatic
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.

MDS-00555: The partitionName {0} is invalid.
Category:: Programmatic
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.

MDS-00557: Resource {0} is already locked or is being modified.
Category:: Session
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.

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

MDS-00559: A partition with name {0} already exists.
Category:: Programmatic
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.

MDS-00560: The MDS repository is incompatible with the archive. The repository version is {0} whereas archive version is {1}.
Category:: Upgrade
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.

MDS-00561: The create operation is not supported for metadata stores of type "{0}".
Category:: Configuration
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.

MDS-00562: The delete operation is not supported for metadata stores of type "{0}".
Category:: Configuration
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.

MDS-00563: The save operation is not supported for metadata stores of type "{0}".
Category:: Configuration
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.

MDS-00564: GUID feature is not supported for metadata stores of type "{0}".
Category:: Configuration
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.

MDS-00565: The rename operation is not supported for metadata stores of type "{0}".
Category:: Configuration
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.

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

MDS-00567: The metadata changes for document "{0}" cannot be written in the underlying store because read-only mode is enabled in the configuration.
Category:: 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.

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

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

MDS-00570: The name or content exceeds the MDS repository schema size for {0}.
Category:: Data
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.

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

MDS-00572: failure to get the ConnectionManager because the DBContext is null
Category:: Programmatic
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.

MDS-00573: The metadata store is already associated with a PManager.
Category:: Programmatic
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.

MDS-00574: The document {0} does not exist in the configured metadata store.
Category:: Data
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.

MDS-00575: failure to acquire write lock for {0}
Category:: Data
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.

MDS-00576: failure to process {0} because metadata store "{1}" is read-only
Category:: Configuration
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.

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

MDS-00578: Failed to process document {0} due to a critical error writing to the repository
Category:: Configuration
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.

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

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

MDS-00581: error deleting partition {0} in file repository {1}
Category:: Configuration
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.

MDS-00582: The MetadataStore {0} is writable but does override getMetadataStoreCommunicator() method.
Category:: Programmatic
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.

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

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}.
Category:: Data
Cause:: The MDS repository platform was not compatible with the archive provided.
Action:: Use a platform compatible archive for the operation.

MDS-00585: Failure to create deployment lineage because metadata store "{0}" is read-only
Category:: Configuration
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.

MDS-00586: ArchiveMetadataStore is restricted to be used with MDS Transfer operation only. Reading or writing files in ArchiveMetadataStore is not supported outside of transfer.
Category:: Configuration
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.

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}.
Category:: Data
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.

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

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

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

MDS-00592: Error occurred while initializing FileMetadataStore connection for the temporary directory.
Category:: Data
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.

MDS-00593: Unable to read the file {0} from archive {1}.
Category:: Data
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.

MDS-00594: Unable to write the file {0} to archive {1}.
Category:: Data
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.

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

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

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

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

MDS-00599: Cannot obtain a connection to the Archive Metadata Store for archive file {0}.
Category:: Programmatic
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.

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

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

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

MDS-00771: A component with {0} "{1}" already exists.
Category:: Data
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.

MDS-00907: unable to save document "{0}" because either a document or package of the same name already exists
Category:: Data
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.

MDS-00908: unable to create package "{0}" because a document or package of the same name already exists
Category:: Data
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.

MDS-00910: unable to save the document because of corrupt MDS database sequences or other internal errors.
Category:: Data
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.

MDS-00911: Document with name "{0}" and version {1} [Low CN={2}, High CN={3}] does not exist in the repository.
Category:: Data
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.

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

MDS-00913: MDS repository is incompatible with the middle tier. MDS version "{0}" is older than minimum MDS version "{1}".
Category:: Upgrade
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.

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

MDS-00915: MDS repository is incompatible with the middle tier for dumping or restoring metadata.
Category:: Upgrade
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.

MDS-00916: MetadataStore configured for {0} does not support deployment management.
Category:: Configuration
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.

MDS-00918: Connection details for the MDS repository are incomplete. The values for "{0}" are invalid
Category:: Configuration
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.

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

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

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

MDS-00928: Invalid document reference, package "cust" should appear before package "trans" in the names of customization translation documents.
Category:: Data
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.

MDS-00929: unable to look up name "{0}" in JNDI context
Category:: Configuration
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.

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

MDS-00931: The database version is {0}.{1}, but MDS requires at least {2}.{3}.
Category:: Upgrade
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.

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

MDS-00933: cannot create data source using URL "{0}"
Category:: Configuration
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.

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

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

MDS-00936: Fast Connection Failover is not supported on the underlying database connection ({0}).
Category:: High Availability
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.

MDS-00937: A local transaction operation like commit or rollback cannot be used in a global transaction on connection "{0}".
Category:: Configuration
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".

MDS-00938: Unable to get an ADF library class loader
Category:: Data
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.

MDS-01059: document with the name {0} missing in the source metadata store
Category:: Data
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.

MDS-01061: Listener {0} cannot be instantiated.
Category:: Configuration
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.

MDS-01104: finding no documents for processing that match the pattern provided
Category:: Data
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.

MDS-01105: invalid label {0}
Category:: Data
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.

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

MDS-01107: Post transfer label cannot be created in target store.
Category:: Data
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.

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

MDS-01109: The target archive configured in ArchiveMetadataStore already exists. Cannot export the documents into an existing archive file.
Category:: Data
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.

MDS-01110: Sandbox export operation allowed only from a database metadata store to an archive metadata store.
Category:: Configuration
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.

MDS-01111: Sandbox import operation allowed only from Archive Metadata Store to a Database Metadata store.
Category:: Configuration
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.

MDS-01112: Transfer unit list in a Sandbox export/import operation should have at least one transfer unit.
Category:: Data
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.

MDS-01113: Sandbox metadata file required for import to a new sandbox operation.
Category:: Data
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.

MDS-01114: Sandbox with same name as the one imported in a sandbox import operation exists on the target metadata store.
Category:: Programmatic
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.

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

MDS-01116: Existing target sandbox in import operation does not contain metadata.
Category:: Programmatic
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.

MDS-01117: Sandbox archive imported into an existing sandbox.
Category:: Programmatic
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.

MDS-01118: Sandbox export operation not supported because the source MDS database repository is of older version that does not support this feature.
Category:: Configuration
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.

MDS-01119: Sandbox import operation not supported because the target MDS database repository is of older version that does not support this feature.
Category:: Configuration
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.

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.
Category:: Configuration
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.

MDS-01121: Document "mds-transfer-config.xml" cannot be read by MDSTransfer.
Category:: Data
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.

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.
Category:: Data
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 special document name.

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.
Category:: Data
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.

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

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

MDS-01153: invalid LocationPath expression "{0}"
Category:: Programmatic
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".

MDS-01154: invalid LocationPath expression "{0}"
Category:: Programmatic
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.

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

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

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

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

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

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

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

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

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

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

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

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

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

MDS-01171: The ID prefix generated by concatenating the layer name "{0}" and layer value "{1}" is not a valid MDS ID.
Category:: Programmatic
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.

MDS-01200: This operation is not supported.
Category:: Programmatic
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.

MDS-01201: An invalid parameter cannot be used when constructing a query condition.
Category:: Programmatic
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.

MDS-01205: A SQL error is occurring when performing the query: "{0}" with binds {1}.
Category:: Programmatic
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.

MDS-01206: The array size for the query must be greater than zero.
Category:: Programmatic
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.

MDS-01207: The namespace mapping for the prefix "{0}" specified in the location path, is missing.
Category:: Configuration
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.

MDS-01208: MDS query condition produces more than {0} characters of SQL where clause.
Category:: Programmatic
Cause:: An MDS query condition was so large that it would produce a very large SQL statement.
Action:: Note the stack backtrace and context of the operation, and contact Oracle Support Services.

MDS-01209: The exclusion CustLayerFilter for layer {0} cannot contain another exclusion CustLayerFilter.
Category:: Programmatic
Cause:: An exclusion CustLayerFilter is nested in another exclusion CustLayterFilter.
Action:: Do not include an exclusion CustLayerFilter inside another exclusion CustLayerFitler.

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

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

MDS-01252: The parameter file {0} must have either {1} or {2} definition.
Category:: Data
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.

MDS-01253: The parameter file {0} must not have both {1} and {2} definitions.
Category:: Data
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.

MDS-01254: The parameter file {0} contains same store definition for sourceStore and targetStore.
Category:: Data
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.

MDS-01255: The property {0} has not been supplied.
Category:: Data
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.

MDS-01258: The value {0} for property {1} is invalid.
Category:: Data
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.

MDS-01259: The metadata store "{0}" cannot be instantiated.
Category:: Data
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.

MDS-01260: failure to process command-line arguments
Category:: Data
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.

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

MDS-01263: operation failure on the resource {0} because source metadata store is read-only
Category:: Configuration
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.

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

MDS-01265: Invalid parameter file {0}. Reason: <{1}:{2}> {3}
Category:: Files
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.

MDS-01266: The associated customization document is missing for a given customization class {0} for the given document name {1}.
Category:: Data
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.

MDS-01267: The associated translation document is not found for a given locale {0} for the given document name {1}.
Category:: Data
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.

MDS-01268: The associated extended metadata document for the given document name {0} is missing.
Category:: Data
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.

MDS-01270: Opening and closing parentheses do not match.
Category:: Configuration
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.

MDS-01271: Cannot get the dependency registry
Category:: Configuration
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.

MDS-01272: unable to read mds-webapp-config.xml file
Category:: Files
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.

MDS-01273: The operation on the resource {0} failed because source metadata store mapped to the namespace {1} is read only.
Category:: Configuration
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.

MDS-01301: Element "{1}", namespace "{0}" is not a valid child under parent "{3}", namespace "{2}".
Category:: Programmatic
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.

MDS-01302: failure to load schema file "{0}"
Category:: Data
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.

MDS-01303: failure to register grammar from schema file "{0}"
Category:: Data
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.

MDS-01305: failure to locate schema file "{0}".
Category:: Configuration
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.

MDS-01306: Grammar from a Web application can be added only once.
Category:: Configuration
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.

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

MDS-01308: Event "{0}" is not supported.
Category:: Programmatic
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.

MDS-01309: ContentModelPipeline is empty.
Category:: Programmatic
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.

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

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

MDS-01312: Change-list transaction state is invalid.
Category:: Programmatic
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.

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

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

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

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

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

MDS-01321: Node type should be one of ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.
Category:: Data
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.

MDS-01322: Value "{0}" does not satisfy "{1}" type.
Category:: Data
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.

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

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

MDS-01325: unable to load type definition "{0}"
Category:: Configuration
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.

MDS-01326: Loading of type definition from element "{0}" is not supported.
Category:: Configuration
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.

MDS-01327: unable to load data from "{0}" into {1}
Category:: Configuration
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.

MDS-01328: unable to load element "{0}" into {1}
Category:: Configuration
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.

MDS-01329: unable to load element "{0}"
Category:: Configuration
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.

MDS-01330: unable to load MDS configuration document
Category:: Files
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.

MDS-01331: unable to load MDS configuration document "{0}"
Category:: Files
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.

MDS-01332: Class {0} is not a subclass or implementation of {1}.
Category:: Configuration
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.

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

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

MDS-01335: namespace "{0}" mapped to metadata-store-usage "{1}" but its definition was not found in MDS configuration.
Category:: 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.

MDS-01336: No XML element is provided to create {0}.
Category:: Configuration
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.

MDS-01337: No URL is provided to create {0}.
Category:: Configuration
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.

MDS-01340: More than one metadata store can be resolved for the namespace "{0}".
Category:: Configuration
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.

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

MDS-01342: No metadata store is mapped to the namespace "{0}".
Category:: Configuration
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.

MDS-01343: There is a duplicate file extension mapping for "{0}".
Category:: Configuration
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.

MDS-01344: cannot create {0} due to null parameter
Category:: Configuration
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.

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

MDS-01347: Base restriction is supported only for classpath store or servlet context store: namespace "{0}" mapped to "{1}".
Category:: Configuration
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.

MDS-01348: unable to save configuration document to "{0}"
Category:: Files
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.

MDS-01349: unable to read existing configuration document "{0}" to be updated
Category:: Files
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.

MDS-01350: Adding namespace "{0}" mapped to "{1}" conflicts with existing namespace "{2}" mapped to "{3}".
Category:: Configuration
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.

MDS-01351: Adding namespace "{0}" with "{1}" restriction conflicts with existing namespace "{2}" with "{3}" restriction.
Category:: Configuration
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.

MDS-01352: Customization configuration with granular mapping "{0}" is unsupported; only the slash, "/", is allowed.
Category:: Configuration
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.

MDS-01353: unable to retrieve customization layer values from "{0}"
Category:: Files
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.

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

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

MDS-01357: MDS configuration is not compatible with JAXB 1.0.
Category:: Configuration
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).

MDS-01358: Invalid MDS configuration. Configuring multiple metadata stores as the default repository for customizations.
Category:: Configuration
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.

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.
Category:: Configuration
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.

MDS-01360: Invalid MDS configuration. The attribute file-type-extension on the file-type element is missing for file type configuration.
Category:: 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.

MDS-01361: cannot add XSD grammar
Category:: Configuration
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.

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

MDS-01363: Failed to lookup datasource with JNDI name "{0}" configured for the DBMetadataStore, defaulting to use ClassPathMetadataStore.
Category:: Configuration
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.

MDS-01364: Namespace mapping for "{0}" is overlapping with namespace mapping for "{1}"; the first mapping is redundant.
Category:: Configuration
Cause:: Redundant namespace mappings defined in the persistence configuration.
Action:: Correct persistence configuration to ensure that there is no overlapping redundant mapping.

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

MDS-01366: Cannot find a metadata store with deploy-target attribute set to true
Category:: Configuration
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.

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

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

MDS-01369: Variable declaration in "{0}" in configuration document is incorrect.
Category:: Configuration
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}.

MDS-01370: MetadataStore configuration for metadata-store-usage "{0}" is invalid.
Category:: Configuration
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.

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

MDS-01373: unable to retrieve password.
Category:: Configuration
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.

MDS-01374: unable to save password.
Category:: Configuration
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.

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

MDS-01376: Unable to get database connection from data source "{1}" configured with JNDI name "{0}".
Category:: Configuration
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.

MDS-01377: Unable to get database connection from data source configured with JNDI name "{0}".
Category:: Configuration
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.

MDS-01378: metadata-store-usage attribute should not be set on namespace "{0}" defined in mds-config.xml.
Category:: Configuration
Cause:: metadata-store-usage attribute was set on the specified namespace in mds-component-config, but this namespace is always assumed to map to deploy-target metadata store.
Action:: Ensure that the metadata-store-usage attribute is removed on specified namespace in mds-config.xml.

MDS-01379: Tenant scope "{0}" is not valid for namespace "{1}" with namespace restriction "{2}".
Category:: Configuration
Cause:: Tenant scope configured for the namespace is not supported with the configured namespace restriction.
Action:: Resolve the conflict between tenant scope and namespace-restriction in the application configuration.

MDS-01380: Tenant scoped base metadata in package "{0}" can not have global customization layer "{1}".
Category:: Configuration
Cause:: Tenant scope GLOBAL on the specified customization layer conflicts with tenant scope TENANT on the base namespace.
Action:: Resolve the conflicts between the tenant scope on the base namespace and that on the customization layer.

MDS-01381: Customization layer "{0}" has been configured more than once with the same tenant scope.
Category:: Configuration
Cause:: Duplicate configuration for the same customization layer was found.
Action:: Remove the duplicate customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.

MDS-01382: Customization layer "{0}" has been configured more than once with conflicting tenant scopes.
Category:: Configuration
Cause:: Conflicting tenant scope configurations was found for the same customization layer.
Action:: Remove the incorrect customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.

MDS-01383: Sandbox name should be provided for registering a sandbox change listener.
Category:: Configuration
Cause:: No sandbox name was provided for registering the sandbox change listener.
Action:: Provide a valid sandbox name when registering the sandbox change listener.

MDS-01384: Sandbox change listener is not found when registering the lifecycle listener for sandbox {0}.
Category:: Configuration
Cause:: The SendboxChangeListener being registered was null.
Action:: Provide a valid sandbox change listener when registering the lifecycle listener for the sandbox.

MDS-01385: Tenant scope "{0}" as base tenant scope is not valid for namespace "{1}".
Category:: Configuration
Cause:: The specified tenant scope type could not be configured as base tenant scope for the namespace.
Action:: Use the correct base tenant scope parameter to create the namespace.

MDS-01386: Multitenant application can not be configured with metadata store "{0}" that does not support multitenancy.
Category:: Configuration
Cause:: A metadata store that does not support multitenancy was configured for a multitenant enabled application.
Action:: Configure a metadata store such as DBMetadataStore that supports multitenancy.

MDS-01387: Tenant with id "{0}" is not allowed to change the autopurge settings; only the global admin can change this configuration.
Category:: Configuration
Cause:: A tenant cannot change the autopurge configuration..
Action:: Only a global admin can change the autopurge configuration.

MDS-01388: Unable to set cache size to {0} KiloBytes.
Category:: Programmatic
Cause:: The cache size requested was invalid either because it was negative or it was too large for the Java Object Cache.
Action:: Check that the specified size is >0 and within the limit for the cache implementation.

MDS-01389: content-type cannot be specified for content-config mapping [File extension={0}, Path to match={1}] since isStreamed is set to true.
Category:: Configuration
Cause:: Conflicting settings between content-type and isStreamed were found in content-config.
Action:: Change content-options to use content-type without causing conflict.

MDS-01390: An audit event name for component "{0}" is not specified.
Category:: Configuration
Cause:: An audit event was defined, but a name for the event was not specified.
Action:: Give the audit event a valid name.

MDS-01391: "{0}" is not a valid audit event name.
Category:: Configuration
Cause:: An invalid audit event name was found. An audit event name should start with a letter and contain only letters and digits.
Action:: Specify a valid name for the audit event.

MDS-01392: Conflicting definitions were found for the audit event with name "{0}" and audit-component "{1}".
Category:: Configuration
Cause:: Conflicting audit event definitions were found in audit-component element.
Action:: Remove or modify one of the conflicting audit events.

MDS-01393: Multiple audit events named "{0}" are defined for component "{1}".
Category:: Configuration
Cause:: Duplicate audit events were found in audit-component element.
Action:: Remove or modify one of the duplicate audit events.

MDS-01394: The repository-name property element is not specified for a metadata-store element that does not have the class-name property.
Category:: Configuration
Cause:: The repository-name property element was not specified for a metadata-store element. It is required when the class-name property is not specified on the metadata-store element to support look up of the repository details.
Action:: Specify the repository name in a child property element of the metadata-store element or specify the class-name property for the metadata-store element in the configuration file.

MDS-01395: Unable to look up the details of the specified repository {0} for the metadata-store configuration.
Category:: Configuration
Cause:: The specified repository was not registered in the domain or the repository was not configured properly.
Action:: Ensure that the specified repository for the metadata-store is configured and registered properly in the domain.

MDS-01396: metadata-store-usage attribute is not set on namespace "{0}" defined in mds-config.xml.
Category:: Configuration
Cause:: metadata-store-usage attribute was missing on the specified namespace in mds-component-config.
Action:: Ensure that the metadata-store-usage attribute is set on the specified namespace in mds-config.xml.

MDS-01397: Multiple audit events with display name "{0}" are defined for component "{1}".
Category:: Configuration
Cause:: More than one audit event was found with the same display name in audit-component element.
Action:: Ensure that the display names are unique for all audit events of a component.

MDS-01398: Namespace "{0}" is mapped to both metadata store "{1}" and metadata store "{2}".
Category:: Configuration
Cause:: There were multiple metadata stores mapped to a given namespace in the persistence configuration.
Action:: Correct the namespace mapping in persistence configuration to ensure that the namespace is mapped to only one metadata store.

MDS-01399: A DBMetadataStore store is being registered with a PManager with multitenant enabled set to {1} but an equal store is already registered with a PManager with multitenant enabled set to {0}.
Category:: Configuration
Cause:: The DBMetadataStore store being registered cannot be used for both multitenant and non multitenant operations at the same time.
Action:: Ensure that the same physical store is not used for both multitenant and non multitenant operations.

MDS-01400: Read-only extended metadata resource "{0}" is not writable.
Category:: Programmatic
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.

MDS-01401: Updating a node in one document "{1}" using a node from a different document "{0}" is not allowed.
Category:: Programmatic
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.

MDS-01402: Updating immutable MetadataObject "{0}" is not allowed.
Category:: Programmatic
Cause:: The MetadataObject being updated was immutable.
Action:: Ensure that the MetadataObject to be updated is mutable.

MDS-01403: Updating a mutable MElement in MetadataObject "{0}" using an immutable MElement: "{1}" is not allowed.
Category:: Programmatic
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.

MDS-01404: Customization to replace root node of {0} is not allowed.
Category:: Programmatic
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.

MDS-01450: missing GUID
Category:: Programmatic
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.

MDS-01451: GUIDs do not match.
Category:: Programmatic
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.

MDS-01452: GUID is null.
Category:: Programmatic
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.

MDS-01455: multiple GUIDs on metadata object {0}
Category:: Programmatic
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.

MDS-01456: invalid GUID on metadata object {0}
Category:: Programmatic
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.

MDS-01457: GUID feature not available
Category:: Programmatic
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.

MDS-01458: GUID must not be present.
Category:: Programmatic
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.

MDS-01460: GUIDs on DOM Document do not match.
Category:: Programmatic
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.

MDS-01461: unable to create document {0} in the metadata repository; a document with the same name or GUID already exists
Category:: Data
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.

MDS-01462: GUID feature is not supported in the classpath store.
Category:: Programmatic
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.

MDS-01464: unable to save GUIDRegister {0}
Category:: Files
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.

MDS-01465: unable to remove node {0} from the GUIDRegister
Category:: Data
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.

MDS-01466: unable to create GUIDRegister directory {0}
Category:: Files
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.

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

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

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

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

MDS-01472: GUID is missing in file {0}
Category:: Data
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.

MDS-01500: The MDSObject {0} is an XML document and cannot be loaded using StreamedObject API.
Category:: Programmatic
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.

MDS-01501: The MDSObject {0} is not an XML document and cannot be loaded from MetadataObject API.
Category:: Programmatic
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.

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

MDS-01503: The content of StreamedObject {0} cannot be read.
Category:: Data
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.

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.
Category:: Programmatic
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.

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

MDS-01601: The relationship role name {0} is a duplicate.
Category:: Programmatic
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.

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

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

MDS-01605: The relationship from {0} to {1} is invalid because the latter does not exist.
Category:: Programmatic
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.

MDS-01606: The relationship from {0} to {1} is invalid because the latter is of incorrect type.
Category:: Programmatic
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.

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

MDS-01608: The relationship from {0} to {1} is invalid because the latter maps to a different store.
Category:: Configuration
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.

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

MDS-01610: Some of the changes in the MDS session are not valid.
Category:: Data
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.

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

MDS-01612: The object {0} cannot be deleted because it is referenced by {1}.
Category:: Programmatic
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.

MDS-01613: The object {0} cannot be deleted because of relationship integrity constraints.
Category:: Programmatic
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.

MDS-01614: Rename is not allowed because integrity checking is not turned on in the object {1} in MetadataObject {0}.
Category:: Configuration
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.

MDS-01615: failure to rename {0} because there is no reference attribute in MetadataObject {1}, element {2}
Category:: Data
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.

MDS-01620: The untyped dependency with the following registration details cannot be inserted: {0}, {1}, {2}, {3}.
Category:: Data
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.

MDS-01621: The untyped dependency information for {0} could not be removed.
Category:: Data
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.

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

MDS-01630: invalid operation in a customized context on an element that could participate in a relationship: {0}
Category:: Programmatic
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.

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}.
Category:: Programmatic
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.

MDS-01633: In a customized context, an element that could participate in a relationship cannot be deleted: {0}.
Category:: Programmatic
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.

MDS-01634: In {0}, a {1} element that participates in a relationship lacks a configurable ID.
Category:: Programmatic
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.

MDS-01635: Skipping the relationship validation for {0} in the metadata object {1} because the element contains an invalid MDS reference.
Category:: Programmatic
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.

MDS-01700: MElementBeanImpl._setSimpleChild cannot be called on a non-simpleType element: name={0}, namespace{1}
Category:: Configuration
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.

MDS-01701: Cannot set the value on an element that is not based on a simpleType: name={0}, namespace={1}
Category:: Configuration
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.

MDS-01702: The method getBean() is not valid for metadata object {0} - it is allowed on only bean metadata objects.
Category:: Configuration
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.

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
Category:: Configuration
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.

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
Category:: Data
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.

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

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

MDS-01708: No schema definition found in namespace "{0}" for element of type "{1}". {2} will not be retrievable as an MDS Bean MO.
Category:: Configuration
Cause:: The schema for the generated MDS bean is not found.
Action:: Add the schema for this namespace and element type to the type definitions for the MDSInstance.

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

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

MDS-01802: A sandbox by name {0} already exists in the {1} store.
Category:: Configuration
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.

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

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.
Category:: Programmatic
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.

MDS-01805: Sandbox {0} missing in {1}.
Category:: Data
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.

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

MDS-01807: failure to delete sandbox {0}
Category:: Programmatic
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.

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

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

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

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

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

MDS-01813: sandbox metadata for {0} cannot be saved because it is being updated by another user.
Category:: Programmatic
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.

MDS-01814: sandbox metadata for {0} cannot be changed because it is read only.
Category:: Programmatic
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

MDS-01815: store configured for sandbox {0} does not support sandbox metadata.
Category:: Programmatic
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.

MDS-01816: {0} is not a valid name for a sandbox.
Category:: Programmatic
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.

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

MDS-01818: sandbox {0} is either being refreshed or applied and is in intermediary state. No further updates except sandbox finalize/undo operation are allowed.
Category:: Programmatic
Cause:: The sandbox is in intermediary state and no further updates can be done to the sandbox.
Action:: The only allowed operations in the intermediary state are: finalize and undo.

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

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

MDS-01821: Lifecycle change notifications for the sandbox {0} cannot be sent out because the change type is not defined.
Category:: Other
Cause:: The sandbox lifecycle change does not have a valid change type.
Action:: Contact Oracle Support Services.

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

MDS-01901: specifying multiple labels for a namespace not allowed
Category:: Configuration
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.

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

MDS-01903: Specified label {0} does not exist for {1} namespace.
Category:: Configuration
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.

MDS-01906: A label with same name {0} already exists.
Category:: Programmatic
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.

MDS-01907: The label {1} is already configured for the store "{0}", so the same store cannot be configured with another label "{2}".
Category:: Configuration
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.

MDS-01908: failure to delete versions of the document {0}
Category:: Programmatic
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.

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

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}.
Category:: Programmatic
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.

MDS-01911: failure of the metadata purge operation for the requested repository partition
Category:: Programmatic
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.

MDS-01912: MetadataStore configured for {0} does not support versioning.
Category:: Configuration
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.

MDS-01913: A deployment lineage with same application name "{0}" and deployment module name "{1}" already exists.
Category:: Programmatic
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.

MDS-01914: The application name and deployment module name cannot be null to create DeploymentInfo.
Category:: Programmatic
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.

MDS-02001: Absolute path as metadata-path for the file metadata-store configuration is not supported for SaaS deployment.
Category:: Configuration
Cause:: Configuring an absolute directory in SaaS Multitenant application will violate metadata isolation across tenants.
Action:: Ensure that relative path specified as metadata-path for the file metadata-store.

MDS-02002: RelativeToLocation for the file metadata-store configuration is not supported for SaaS deployment.
Category:: Configuration
Cause:: Configuring an absolute directory in SaaS Multitenant application will violate metadata isolation across tenants.
Action:: Ensure that relative path is specified as metadata-path for the Metadata Store and RelativeToLocation is null

MDS-02003: Package name {0} in cust-restriction-config in {1} is invalid.
Category:: Configuration
Cause:: An invalid package name was encountered whilst loading the component configuration.
Action:: Ensure that a valid package name is specified

MDS-02004: Cannot configure [Path to match={0}] as Layered Stream Objects since path's content-type is not BINARY_STREAM.
Category:: Configuration
Cause:: customization-type attribute in cust-config can be set to FULL_REPLACE only when content-config configures the path as BINARY_STREAM.
Action:: Change content-type to use BINARY_STREAM or remove customization-type configuration.

MDS-02005: Cannot configure [Path to match={0}] as Layered Stream Objects since path is configured for stream storage in content-config using isStreamed option.
Category:: Configuration
Cause:: cust-type is not supported with isStreamed as isStreamed attribute is deprecated.
Action:: Remove isStreamed and configure content-type to use BINARY_STREAM or remove cust-type configuration.

MDS-02006: streamBuilder class not specified for path {0}.
Category:: Configuration
Cause:: The streamBuilder class cannot be null if customization-type is configured as 'extension'.
Action:: Ensure that the streamBuilder class is supplied when configuring customization-type as 'extension'.

MDS-02007: streamBuilder can only be specified with customization-type 'extension' for path {0}.
Category:: Configuration
Cause:: streamBuilder is only valid for 'extension' customization-type.
Action:: Ensure that the streamBuilder class is only supplied when configuring customization-type as 'extension'.

MDS-02024: Setting or modifying the unique (or locally unique) identifier "{0}" of an existing element with localRef "{1}" through customizations is not supported.
Category:: Programmatic
Cause:: An attempt was made to customize unique (or locally unique) identifier.
Action:: Remove any customization that is attempting to modify the unique (or locally unique) identifier of an XML element.

MDS-02025: The requested change is incompatible with changes already pending on the MDS session.
Category:: Programmatic
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.

MDS-02100: Illegal permission target: "{0}" - must begin with {1}.
Category:: Programmatic
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.

MDS-02101: Illegal permission action: "{0}" - unknown action.
Category:: Programmatic
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.

MDS-02102: Illegal permission action: "{0}" - customize action takes 0 or 2 parameters.
Category:: Programmatic
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.

MDS-02201: type validation failure for the metadata object "{0}"
Category:: Programmatic
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.

MDS-02202: Content of the metadata object "{0}" is not valid.
Category:: Programmatic
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.

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

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

MDS-02301: The rename unit is invalid because either "{0}" or "{1}" is reused in the rename plan.
Category:: Programmatic
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.

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

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

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

MDS-02401: The operation {0} on the {1} node is not allowed.
Category:: Configuration
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.

MDS-02402: The type definition for {1} does not allow customization of {0}.
Category:: Configuration
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.

MDS-02404: The subelement {1} in the MDX document does not allow customization of {0}.
Category:: Configuration
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.

MDS-02405: The attribute {2} in element {1} in the MDX document does not allow customization of {0}.
Category:: Configuration
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.

MDS-02406: Customization of {0} is not allowed because it is not explicitly allowed by any type definition nor any extended metadata entry.
Category:: Configuration
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.

MDS-02407: Customization of {0} is not allowed because the local reference was not found in the document.
Category:: Programmatic
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.

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

MDS-02500: Cannot find a valid MDSSession object for accessing the MDS document using ORAMDS URL
Category:: Programmatic
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.

MDS-02501: cannot load the ORAMDS URL "{0}" because MDS session could not be created or resolved
Category:: Programmatic
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.

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

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

MDS-02602: configuration migration failure because it contains more than one metadata-stores element
Category:: Programmatic
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.

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

MDS-02700: The resource "{0}" cannot be updated by tenant "{1}".
Category:: Programmatic
Cause:: The given resource could not be updated by the current tenant because it was not available in current tenant's scope.
Action:: Verify that the resource is being updated in the same scope of the tenant who updates the resource.

MDS-02702: Tenant scoped PManager instance cannot be created for tenant {0} because given PManager instance does not have multitenancy enabled.
Category:: Configuration
Cause:: The PManager instance used here did not have multitenancy enabled but an attempt was made to create tenant scoped PManager instance.
Action:: Verify that the PManager instance being passed has multitenancy support enabled.

MDS-02703: Tenant scoped PManager cannot be created for tenant "null".
Category:: Configuration
Cause:: The PManager instance used here had multitenancy support enabled but an attempt was made to create tenant scoped PManager instance with "null" tenant.
Action:: Create scoped PManager instance for valid tenant id.

MDS-02704: Cannot create tenant scoped PManager instance using another tenant scoped PManager instance.
Category:: Programmatic
Cause:: An attempt was made to create tenant scoped PManager using another scoped PManager instance.
Action:: Create a tenant scoped PManager using an unscoped PManager instance.

MDS-02705: Cannot create PContext using an unscoped PManager instance.
Category:: Programmatic
Cause:: Creating PContext using an unscoped PManager instance was not allowed.
Action:: Use PManager instance that is scoped for a tenant to create PContext.

MDS-02706: Cannot create PTransaction using an unscoped PManager instance.
Category:: Programmatic
Cause:: Creating PTransaction using an unscoped PManager instance was not allowed.
Action:: Use PManager instance that is scoped for a tenant to create PTransaction.

MDS-02707: PContext with tenant id {0} cannot be used in scoped PManager with tenant id {1}.
Category:: Programmatic
Cause:: Tenant id attached to PContext and the tenant id of tenant scoped PManager to which it was passed did not match.
Action:: Create PContext from the tenant scoped PManager to which it is passed.

MDS-02708: PManager instance is being used after it has been released.
Category:: Programmatic
Cause:: PManager instance was being used after it had been released.
Action:: Create a new PManager.

MDS-02709: Configuration change operation "{0}" on scoped PManager is not allowed for the tenant {1}. Only global tenant is allowed to change the configuration settings in PManager.
Category:: Programmatic
Cause:: A non global tenant attempted to change configurations in scoped PManager.
Action:: Use global tenant scoped PManager to change the configuration settings.

MDS-02710: Operation "{0}" is not allowed in unscoped PManager.
Category:: Programmatic
Cause:: A tenant aware operation was invoked in an unscoped PManager instance.
Action:: Use a global or tenant scoped PManager to do the operation.

MDS-02711: No tenant operations are allowed on MetadataStoreConnection not associated with any tenant id.
Category:: Programmatic
Cause:: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.
Action:: Create a new MetadataStoreConnection with a valid tenant id.

MDS-02712: The operation {0} is not allowed in this MetadataStoreConnection to database store because the MetadataStoreConnection is not attached to any tenant id.
Category:: Programmatic
Cause:: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.
Action:: Create a new MetadataStoreConnection with a valid tenant id.

MDS-02713: PContext associated with tenant {0} cannot be used with MetadataStoreConnection associated with different tenant {1}. Operation {2} failure.
Category:: Programmatic
Cause:: The tenant id attached to PContext and MetadataStoreConnection did not match.
Action:: Use PContext with same tenant id as the one attached to metadata store connection.

MDS-02714: Creating metadata store connection for tenant {0} is not allowed in non multitenant application.
Category:: Programmatic
Cause:: An attempt was made to create metadata store connection for non global tenant in non multitenant application.
Action:: Use global tenant id to create metadata store connection.

MDS-02715: No tenant scoped PManager instances can be created on already released PManager instance.
Category:: Programmatic
Cause:: An attempt was made to create a tenant scoped PManager instance on already released PManager instance.
Action:: Create new PManager instance using a PConfig then try creating scoped PManager instance.

MDS-02720: Cannot rename the document {0} to {1} as the new tenant scope does not match the original tenant scope.
Category:: Programmatic
Cause:: The new name for the document was configured to a different tenant scope to the old document name.
Action:: Provide a new valid document name that maps to the same tenant scope as the original document.

MDS-02721: PResource {0} for tenant {1} cannot be used with MetadataStoreConnection that is associated with different tenant {2}. Operation {3} failure.
Category:: Programmatic
Cause:: The tenant ids of the PResource and the MetadataStoreConnection did not match.
Action:: Use PResource with same tenant id of the one attached to metadata store connection.

MDS-02722: Mar Lineage can be created by global tenant only. Creating MAR lineage is not supported for tenant {0}.
Category:: Programmatic
Cause:: A non-global tenant attempted to create MAR lineage which is not supported. MAR lineage creation is allowed only for global tenant currently.
Action:: Create MAR lineage from global tenant context.

MDS-02723: Operation "{0}" is not supported in Sandbox currently.
Category:: Programmatic
Cause:: Unsupported operation was invoked in Sandbox instance.
Action:: This operation is not supported in Sandbox currently.

MDS-02724: The ResourceName that is attached to tenant scope {0} is not allowed in SandboxPTransaction that is attached to the different tenant scope {1}. Operation {2} failure.
Category:: Programmatic
Cause:: Tenant scope for ResourceName and SandboxPTransaction did not match.
Action:: Use ResourceName with same tenant scope of the one attached to SandboxPTransaction.

MDS-02725: The Label {0} that is attached to tenant {1} is not allowed in MetadataStoreConnection that is attached to different tenant {2}. Operation {3} failure.
Category:: Programmatic
Cause:: Tenant id for Label and MetadataStoreConnection did not match.
Action:: Use label with same tenant id of the one attached to MetadataStoreConnection.

MDS-02726: The tenant {0} that is attached to PDocument {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.
Category:: Programmatic
Cause:: Tenant id for PDocument and SandboxPTransaction did not match.
Action:: Use PDocument with same tenant id of the one attached to SandboxTransaction.

MDS-02727: The tenant {0} that is attached to Label {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.
Category:: Programmatic
Cause:: Tenant id for Label and SandboxPTransaction did not match.
Action:: Use label with same tenant id of the one attached to SandboxPTransaction.

MDS-02728: The tenant {0} that is attached to {1} {2} is not allowed in Sandbox that is attached to different tenant {3}. Operation {4} failure.
Category:: Programmatic
Cause:: Tenant id attached and Sandbox did not match.
Action:: Use tenant id same as the one attached to Sandbox.

MDS-02729: The tenant scope {0} that is attached to {1} is not allowed in Sandbox that is attached to the different tenant scope {2}. Operation {3} failure.
Category:: Programmatic
Cause:: Tenant scope attached and Sandbox did not match.
Action:: Use tenant scope same as the one attached to Sandbox.

MDS-02730: Error in deprovisioning the tenant {0}. Unable to delete the resources in {1}.
Category:: Configuration
Cause:: Tenant resources might be on read-only store.
Action:: Verify that tenant resources exist on a writable store.

MDS-02731: Tenant specific operations cannot be done in multitenant disabled environment for tenant {0}.
Category:: Programmatic
Cause:: An attempt was made to do tenant specific operations in Multitenant disabled environment.
Action:: Enable the multitenant feature.

MDS-02732: TenantId cannot be created for the value "{0}".
Category:: Programmatic
Cause:: TenantId could not be created with negative values or a value with more than 18 digits.
Action:: Use positive values with max of 18 digits in decimal format to create a valid TenantId object.

MDS-02733: Rename across multiple tenant stripes is not supported on this store.
Category:: Programmatic
Cause:: The store does not support writing to multiple tenant stripes or multitenancy is not enabled.
Action:: Enable the multitenant feature.

MDS-02734: Unable to get TenantInfo for TenantId "{0}" from tenant management system.
Category:: Configuration
Cause:: Tenant is not yet provisioned or was deprovisioned from the POD.
Action:: Check tenant provisioning system to ensure tenant is provisioned.

MDS-02735: Label "{0}" cannot be deleted since it is attached to sandbox(es): "{1}".
Category:: Programmatic
Cause:: An attempt was made to delete a label that is attached to active sandbox(es).
Action:: Make sure that there are no sandboxes attached to label to be deleted. Refer to FMW Enterprise Manager MDS repository home page to check labels that are attached to a sandbox.

MDS-02736: Failed to update purge configuration value for tenant {0}.
Category:: Programmatic
Cause:: An error occurred while updating purge configuration.
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.

MDS-02737: Prevented potential duplicate tip version for document "{0}". Original request was to update document with PATH_DOC_ID={1}, PATH_VERSION={2} and PATH_LOW_CN={3}, updated latest tip version having PATH_DOC_ID={4}, PATH_VERSION={5} PATH_LOW_CN={6} to avoid duplicate tip version.
Category:: Programmatic
Cause:: MDS detected code flow which could have lead to duplicate tip issue.
Action:: Previous tip document is replaced forcefully with new content, validate content of the document.

MDS-02738: Database based metadata repository initialization failure because of invalid MDS database schema at "[{0}]".
Category:: Configuration
Cause:: Configured Database details refer to invalid or non-MDS schema.
Action:: Configure a valid MDS database schema created using Repository Creation Utility

MDS-02739: MDS Partition with ID {0} does not exist in the database repository
Category:: Programmatic
Cause:: This could be caused by deleting the partition while still being used by application.
Action:: Ensure partition is deleted only when not in use. To resolve the current issue, restart the application or server.

MDS-02740: MDS repository version for tenant "{0}" is not same as Global MDS repository version. Repository version for tenant is "{1}" whereas GLOBAL repository version is "{2}".
Category:: Configuration
Cause:: MDS Repository version for Tenant is not same as Global MDS repository version
Action:: Upgrade the MDS repository to the required version so that Global and Tenant repository versions are same.

MDS-02741: The metadata changes cannot be written to underlying store because read-only mode is enabled in the configuration.
Category:: 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.

MDS-02742: Instance of {0} is being used after it has been released.
Category:: Programmatic
Cause:: Instance of a MDS object was used after it was released.
Action:: Create a new instance.

MDS-02743: Error deleting partition {0} in repository {1}.
Category:: Configuration
Cause:: The directory or partition doesn't exist.
Action:: Verify that the metadata path or partition for the repository exists.

MDS-02744: Failed to delete directory {0}.
Category:: Programmatic
Cause:: The specified directory was invalid, read only or was in use and could not be deleted.
Action:: Check exception message in logs for the exception stack and underlying cause.

MDS-02745: Unable to get database connection from data source "{0}" for store id "{1}".
Category:: Configuration
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:: Check if the data source is configured correctly and the database is accessible. See message of the cause exception for more information on the actual reason for failure.

MDS-02746: Invalid store id.
Category:: Programmatic
Cause:: Store id is null or empty.
Action:: Provide a valid store id.

MDS-02747: Invalid data source.
Category:: Programmatic
Cause:: Data source cannot be null.
Action:: Provide a valid data source.

MDS-02800: The label "{0}" cannot be provided as null for label based transfer.
Category:: Configuration
Cause:: The label was provided as null for label based transfer.
Action:: Provide valid label name for label based transfer.

MDS-02801: Document {0} with scope {1} cannot be transferred by tenant {2}.
Category:: Programmatic
Cause:: The given document could not be transferred from source store by current tenant because the document was not in the scope of current tenant.
Action:: Ensure that document being transferred mapped to current tenant scope.

MDS-02802: Transfer is not supported for multitenant MDSInstance with file store.
Category:: Configuration
Cause:: Either source or target MDSInstance has multitenancy enabled and configured with file store.
Action:: Use a non multitanant MDSInstance with file store.

MDS-02803: List of patterns to select the MOs are either empty or null.
Category:: Programmatic
Cause:: List of MOPatterns are empty or null.
Action:: Ensure that valid list of MOPatterns are provided.

MDS-02804: Layer name "{0}" configured in CustLayerFilter to remove customizations, contains patterns.
Category:: Programmatic
Cause:: Layer name contains patterns.
Action:: Ensure that layer name doesn't contain any patterns.

MDS-02805: Import Metadata With Exact Copy is allowed only from archive.
Category:: Configuration
Cause:: Source MetadataStore was not not archive.
Action:: Use an archive as source store.

MDS-02806: Source archive is invalid because it is missing the export criteria metadata file.
Category:: Configuration
Cause:: MetadataFile containing the export criteria was missing in the source archive
Action:: Import from an archive which has metadata file.

MDS-02807: Import Metadata With Exact Copy is allowed only to Database repository
Category:: Configuration
Cause:: Target MetadataStore was not Database repository
Action:: Use Database repository as target for import.

MDS-02808: Category with which Export Criteria is written in the archive file is different from the one which is used to get ExportCriteriaReader
Category:: Configuration
Cause:: Wrong category was used to get Export Criteria Reader.
Action:: Use right category..

MDS-02809: Import Metadata With Exact copy operation is not supported when export criteria used to generate source archive contains fromLabel or toLabel conditions.
Category:: Configuration
Cause:: Export parameters fromLabel or toLabel were specified to generate archive that was acting as source for Import Metadata With Exact Copy Operation.
Action:: Use an archive MetadataStore that was exported without fromLabel or toLabel specified.

MDS-02810: Transfer operation with TransferType "{0}" has been aborted and rolled back because too many documents failed.
Category:: Other
Cause:: Operation failed for high number of documents.
Action:: Check the server logs to identify root cause, rerun the operation after correcting the issue in the system environment.

MDS-02811: Wrong TransferType {0} is passed in for Sandbox {1}
Category:: Configuration
Cause:: TransferType and TransferParams which is created for Sandbox transfer doesn't match.
Action:: Supply the right TransferType.

MDS-02812: Parameter {0} has null values in it.
Category:: Programmatic
Cause:: Parameter contains null values.
Action:: Ensure that the indicated parameter does not contain null values when the method is called.

MDS-02813: Parameter TransferOptions must be set when transferBaseDocument is set to false.
Category:: Programmatic
Cause:: Filtering out base documents is supported only when TransferOptions is set.
Action:: Ensure that TransferOptions is set when transferBaseDocument is set to false.

MDS-02814: Parallel Transfer of chunk {0} performed by thread {1} failed.
Category:: Other
Cause:: Error occured while transferring the chunk.
Action:: Check the server logs to identify root cause, rerun the operation after correcting the issue in the system environment.

MDS-02815: Parallel Transfer of one or more chunks timedout. Please retry transfer.
Category:: Other
Cause:: Timeout occured while transferring the chunk.
Action:: Check the server logs to identify root cause, rerun the operation after correcting the issue in the system environment.

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

MDS-05787: Partition name is not specified in adf-config.xml file.
Category:: Configuration
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.

MDS-05788: Unable to find the JNDI datasource in the file adf-config.xml.
Category:: Configuration
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.

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

MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration.
Category:: 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

MDS-05791: An error occurred during the deployment of the metadata archive (MAR) {0}.
Category:: Configuration
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.

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

MDS-05793: Metadata path {2} for partition {1} of MDS file repository {0} specified in adf-config.xml is either invalid or unreachable.
Category:: Configuration
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.

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

MDS-05795: Invalid value "{0}" specified in the content-config of the application's configuration
Category:: Configuration
Cause:: Only restriction type CUSTOMIZATIONS is supported in content-config.
Action:: Ensure that the MDS persistence configuration is correctly defined.

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

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

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

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

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

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

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

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

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

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

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.
Category:: Data
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.

MDS-10018: The transfer restriction {0} is not supported in target store. All the documents will be transferred to target store.
Category:: Data
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.

MDS-10019: The deployment information for application name "{0}" and module name "{1}" ignored since transfer operation is of type "{2}".
Category:: Data
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.

MDS-10020: Querying checksum data from target repository to avoid transferring unchanged documents.
Category:: Data
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.

MDS-10022: Query to get the checksum of the documents from target repository completed successfully.
Category:: Data
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.

MDS-10023: No valid exclusion rules are specified in mds-transfer-config.xml to preserve documents in target store.
Category:: Data
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.

MDS-10024: Preparing the list of documents to be excluded during transfer as per the configuration given in mds-transfer-config.xml.
Category:: Data
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.

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}:
Category:: Other
Cause:: Some metadata paths are configured in mds-transfer-config.xml to preserve existing documents in target repository.
Action:: No action required.

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}:
Category:: Other
Cause:: Some metadata object names are configured in mds-transfer-config.xml to preserve existing documents in target repository.
Action:: No action required.

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

MDS-10030: Sandbox {0} created as part of Import operation is not destroyed after import failed.
Category:: Other
Cause:: A Critical Write error on database side has occurred. Look for specific exception in the log file.
Action:: Destroy unused sandbox from metadata repository. Contact application administrator for assistance.

MDS-10031: Value provided in {0} in CustLayerUsage or CustLayerFilter is not properly encoded.Passed in value will considered as it is without interpreting intended encoded value
Category:: Data
Cause:: Passed in value is not proper hexadecimal encoded value
Action:: No action required.

MDS-10032: Transfer operation with transfer type {0} ignoring document {1} because MDSInstance {2} reported it as not existing.
Category:: Programmatic
Cause:: MDSTransfer is configured to ignore such document.
Action:: No action required.

MDS-10033: Transfer operation with transfer type {0} has been rolled back because {1} documents failed with exceptions.
Category:: Other
Cause:: Operation failed for large number of documents due to exceptions.
Action:: Check the server logs to identify root cause, rerun the operation after correcting the issue in the system environment.

MDS-10034: Polling for store {0} failed - {1}. Polling will retry when the polling interval has elapsed.
Category:: Other
Cause:: The polling query was unable to run. If this is a temporary condition, polling should recover automatically once the error condition is resolved.
Action:: Polling will be retried. If problem persists enable tracing for oracle.mds.dbstore to get full stack trace and check datasources.

MDS-10035: Parallel transfer requested but not feasible, configure oracle.mds.transfer logger to FINEST to get more details.
Category:: Other
Cause:: Parallel transfer not supported for given transfer invocation.
Action:: Configure oracle.mds.transfer logger to FINEST to get more details.

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

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

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

MDS-11006: Directory {0} does not exist.
Category:: Files
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.

MDS-11007: Skipping directory {0} because {1} does not match the condition.
Category:: Programmatic
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.

MDS-11008: Skipping directory {0} because it is a filestore root.
Category:: Files
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.

MDS-11009: Skipping directory {0} because {1} is not a valid package name.
Category:: Programmatic
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.

MDS-11010: Document cache {0} exceeds its maximum number of entries {1}, so the cache is cleared.
Category:: Configuration
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.

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

MDS-11012: Cache collision has been detected when adding key {0}, label set {1}, sandbox name {2}, scope {3}.
Category:: Programmatic
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.

MDS-11013: Cannot store the object of type {0} in the Java Object Cache because the cache or cache region is full
Category:: Configuration
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.

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

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.
Category:: Configuration
Cause:: Developer Mode is configured as a servlet initialization parameter either explicitly or because the application is being run within JDeveloper.
Action:: No action required.

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

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

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.
Category:: Configuration
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.

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

MDS-11023: MDS Remote Notifications: Coherence is not configured to use unicast and no cluster name is specified so remote notification is not enabled.
Category:: Configuration
Cause:: MDS remote notification only works if the Coherence configuration specifies unicast or a cluster name.
Action:: Unicast can be set by either specifying a unicast-listener in your Coherence cluster-config or by system property tangosol.coherence.wk. A cluster-name can be set either as part of a member-identity in your cluster-config or by system property tangosol.coherence.cluster.

MDS-11026: Ignoring the duplicate MDS component configuration file URL "{0}" found on the classpath.
Category:: Configuration
Cause:: A duplicate URL for an MDS component configuration file was found on the classpath.
Action:: No action required.

MDS-11027: Some metadata is configured to be stored as xml-stream. However it will be ignored because no metadata store configured for this application supports storing metadata in that form.
Category:: Configuration
Cause:: xml-stream content type was configured for some metadata content, but no metadataStore supports the feature.
Action:: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.

MDS-11028: Some metadata is configured to be stored as xml-stream. However it will be ignored because the corresponding metadata store, with class name: {0}, repository name: {1}, partition name: {2}, does not support storing metadata in that form.
Category:: Configuration
Cause:: xml-stream content type was configured for some metadata content, but the metadata store did not support the feature.
Action:: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.

MDS-11029: MetadataStore configuration for metadata-store-usage "{0}" is invalid. However the MetadataStore is ignored because it is not referenced by any namespace mapping.
Category:: Configuration
Cause:: MetadataStore class or some of its properties were not valid.
Action:: Ensure that the MetadataStore class exists and all required properties are valid.

MDS-11030: Failed to get schema version from registry for repository "{0}" because of exception: {1}
Category:: Configuration
Cause:: Either the DataSource definition for the repository is no longer valid or the MDS schema is not created using RCU.
Action:: Ensure the DataSource connection is valid or the schema is created using RCU.

MDS-11032: Registered grammar using remote schema "{0}". In design time (JDev) environment, it is recommended to use local resources.
Category:: Configuration
Cause:: Remote schema was referred with http URI. In design time environment, recommendation is to use local resources.
Action:: Replace it with local copy of schema.

MDS-11033: Duplicate mappings between namespace "{0}" and metadata store "{1}" are found in the persistence configuration.
Category:: Configuration
Cause:: There were more than one namespace to metadata store mappings for a given namespace in the persistence configuration.
Action:: Correct the namespace mapping in persistence configuration to ensure that the namespace is mapped to only one metadata store.

MDS-11034: The name {0} derived from JNDI will be registered as an MDS repository instead of the DataSource with the same name.
Category:: Configuration
Cause:: A JDBC DataSource and a JNDI have conflict in naming a MDS repository in the domain. MDS repository names must be unique within a domain.
Action:: Find out which application is referencing the repository and the JNDI name. Resolve the naming conflict by removing the DataSource with same name only if it is unused.

MDS-11100: MetadataObject.getBaseMO() found a mismatched CacheAccess in the cache. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}, name={8}, GUID={9}].
Category:: Other
Cause:: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.
Action:: Check the MOName and guid are correct and there are no duplicate Guids in the metadata store.

MDS-11101: MetadataObject.getBaseMO() recursing too deep. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}].
Category:: Other
Cause:: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.
Action:: Check the data in the metadata store to determine the cause.

MDS-11102: The MDS session was created by the ADF framework with a transaction key for its "single flush" feature, and the call to {0} is restricted to that framework. This call does not use that transaction key and although working now, will fail with an exception in future. To find the originator of the call, set the log level for logger "oracle.mds.transkey" to FINEST. Note that the ADF framework manages the MDS session created for the request so an explicit call to {0} should be removed.
Category:: Other
Cause:: A call was made to a restricted method on the MDS session and that call should be removed as it is liable to fail in later releases.
Action:: Identify the caller and ensure that the call to this method is removed.

MDS-11103: Failed to register dump classes.
Category:: Other
Cause:: Failed to register dump classes with DFW.
Action:: Contact Oracle Support Services.

MDS-11104: Content config mapping with path {0} contains reserved keyword "mdssys/cust/", use restrictionType="CUSTOMIZATIONS" instead.
Category:: Configuration
Cause:: The path of the content config mapping contains reserved keyword "mdssys/cust/".
Action:: Change the content config mapping to use restrictionType="CUSTOMIZATIONS"

MDS-11107: Unable to read "{0}" property value : "{1}". Cause : {2}
Category:: Configuration
Cause:: The property value contains invalid characters.
Action:: Correct the property value and retry.

MDS-11108: Invalid value supplied in "{0}" property value : "{1}".
Category:: Configuration
Cause:: The property value contains values that reduce the cache size to less than the minimum allowed.
Action:: Ensure the property values do not reduce the cache size to less than the minimum allowed.

MDS-11109: Successfully read property "{0}"="{1}" and generated "{2}".
Category:: Configuration
Cause:: Cache weightings successfully read.
Action:: No action required if the generated values are correct.

MDS-11110: customization-type will be ignored for mapping [Path to match={1}] because content-type is not configured in content-config.
Category:: Configuration
Cause:: content-type configuration is missing for mapping [Path to match={1}].
Action:: content-type must be configured as BINARY_STREAM (along with customization-type as FULL_REPLACE) for storing customizations as Layered Stream Object.

MDS-11111: Both ContentConfig and FileTypeConfig are configuring Content Type for file extension {0}, ContentType {1} from ContentConfig will override ContentType {2} from FileTypeConfig for path {3}.
Category:: Configuration
Cause:: ContentType configured in both Content Config and FileTypeConfig.
Action:: Correct the configuration to avoid the conflict.

MDS-90013: The metadata partition with name "{0}" does not exist in the metadata repository "{1}".
Category:: Topology
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.

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

MDS-90015: The metadata repository with name "{0}" does not exist.
Category:: Topology
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.

MDS-90016: There are no applications deployed to partition "{0}".
Category:: Topology
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.

MDS-90017: The application to be used for this operation is not specified.
Category:: Topology
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.

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

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

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

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

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

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

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

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

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

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

MDS-90028: Metadata repository with name "{0}" already exists.
Category:: Topology
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.

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

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

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

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

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

MDS-90034: The source directory or archive "{0}" for importing metadata is invalid.
Category:: Topology
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.

MDS-90035: The target directory or archive "{0}" for exporting metadata is invalid.
Category:: Topology
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.

MDS-90036: The application does not have a valid MAR file path.
Category:: Topology
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.

MDS-90037: The archive "{0}" does not contain valid contents.
Category:: Topology
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.

MDS-90038: The database authentication alias "{0}" already exists. To reuse the same authentication alias, try the operation again without specifying user and password.
Category:: Topology
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 authentication alias, or reuse the existing authentication alias by not specifying user and password.

MDS-90039: The database authentication alias "{0}" cannot be found. To create the authentication alias, try the operation again with user and password specified.
Category:: Topology
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.

MDS-90040: failed to connect to database
Category:: Topology
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.

MDS-90041: Customization layer values are not supported for "excludeCustFor" parameter.
Category:: Topology
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.

MDS-90042: "{0}" is not a valid tenant name.
Category:: Configuration
Cause:: The specified tenant was not provisioned in the specified partition and repository.
Action:: Specify a valid tenant name.

MDS-90043: This operation cannot be performed by the tenant named "{0}". It can only be invoked by the "{1}" tenant.
Category:: Configuration
Cause:: The specified tenant was not provisioned in the partition and repository provided.
Action:: Execute this operation as GLOBAL tenant.

MDS-90044: This operation cannot be performed because the WebLogic edit session has been locked by a different user.
Category:: Configuration
Cause:: The WebLogic edit session has been locked by a different user.
Action:: Retry the operation after the edit session lock is released.

MDS-90045: MDS dump operation "{0}" failed.
Category:: Data
Cause:: Exception occurred during the execution of the command.
Action:: Provide the required parameters for the command.

MDS-90046: MDS Application runtime MBean for application "{0}" running in server "{1}" is not available. "{2}" operation failure.
Category:: Configuration
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 application name is correct.

MDS-90047: The target archive name "{0}" is invalid. It must point to a local file name with a valid archive extension.
Category:: Data
Cause:: The archive location used for mds dump operation was invalid.
Action:: Ensure target archive name is a valid local file name with valid archive extension.

MDS-90048: The dump argument "{0}" is invalid. It cannot be an empty string.
Category:: Data
Cause:: A request to execute dump was made with an invalid argument.
Action:: Ensure valid values are given for the dump arguments.

MDS-90049: Exclusion of documents during exportMetadata is not supported for seeded documents.
Category:: Data
Cause:: It was invalid to specify excludeDocs while not setting excludeSeededDos to true.
Action:: Either set excludeSeededDocs to true, or unspecify excludeDocs.

MDS-90050: ExportParameters can not be null for {0} operation.
Category:: Data
Cause:: ExportParameters with null value was not allowed.
Action:: Specify a valid ExportParameters argument.

MDS-90051: ImportParameters can not be null for {0} operation.
Category:: Data
Cause:: ImportParameters with null value was not allowed.
Action:: Specify a valid ImportParameters argument.

MDS-90052: Cannot deregister metadata repository "{0}" because it is based on a JNDI name of a consolidated data source.
Category:: Data
Cause:: The deregistration of a metadata repository that is based on a JNDI name of a consolidated data source is not allowed.
Action:: Perform deregistration operation on a metadata repository that is based on a non-consolidated data source only.

MDS-90053: Import Metadata With Exact copy operation is not supported when export operation used to generate source archive uses programmatic TransferListener.
Category:: Data
Cause:: Export parameter transferListener was specified to generate archive that was acting as source for Import Metadata With Exact Copy Operation.
Action:: Use an archive MetadataStore that was exported without programmatic TransferListener specified.

MDS-90054: The resource group "{0}" cannot not be found in "{1}" partition.
Category:: Data
Cause:: The specified resource group was not found in the current domain partition.
Action:: Verify that the specified resource group is defined in the current domain partition.

MDS-90055: The resource group must be specified to register a metadata repository at "{0}" partition.
Category:: Data
Cause:: The resource group was not specified to register a metadata repository at partition scope.
Action:: Specify a resource group for registering a metadata repository at the domain partition containing that resource group.

MDS-90056: {0} can not be null for {1} operation.
Category:: Data
Cause:: Null value was not allowed.
Action:: Specify a valid argument.

MDS-90057: The document name used in exportDocVersions operation is invalid.
Category:: Data
Cause:: Document pattern or empty document name was used.
Action:: Use the exact full document path.

MDS-90058: {0} operation is not permitted in Weblogic domain configured with consolidate schema or datasource.
Category:: Configuration
Cause:: It was unneccesary to register or deregister a metadata DB repository in consolidate Weblogic domain.
Action:: Use pre-configured metadata DB repository.

MDS-90059: A Metadata Archive (MAR) with the name {0} was found either packaged with the EAR or in directories listed in {1}.
Category:: Configuration
Cause:: Metadata Archive (MAR) names must be unique. Two or more metadata archives were found with the same name.
Action:: Use pre-configured metadata DB repository.

MDS-90060: A required JRF patch to support MSI-D was not applied in this env.
Category:: Other
Cause:: A JRF patch to enhance support for WebLogic Server MSI-D feature is missing in this env.
Action:: Apply the JRF Patch corresponding to the WLS MSI-D feature.

MDS-90061: The path denoted by "{0}" does not represent a Metadata Archive (MAR).
Category:: Other
Cause:: The path to a Metadata Archive (MAR) must represent a file with a "mar" extension.
Action:: Ensure that the Metadata Archive (MAR) path refers to a file with a "mar" extension in the application's EAR file.

MDS-90143: "{0}" is not a valid component name.
Category:: Configuration
Cause:: The specified component name is invalid.
Action:: Specify a valid audit component name that uses only letters.

MDS-90144: Error registering audit event definitions for component "{0}".
Category:: Configuration
Cause:: The audit event definitions could not be registered.
Action:: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

MDS-90145: Error occurred when raising audit event "{0}" for component "{1}".
Category:: Configuration
Cause:: The audit event was not registered or an unknown error occurred in the auditing system.
Action:: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

MDS-90146: Error occurred when checking if "{0}" is auditable.
Category:: Configuration
Cause:: An unknown error occurred when checking if auditing is enabled for the component "{0}".
Action:: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

MDS-90147: Error occurred when checking if the component "{0}" is auditable.
Category:: Configuration
Cause:: An unknown error occurred when checking if auditing is enabled for the event "{1}" defined for the component "{0}".
Action:: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.

MDS-90148: The custom audit event of type "{0}" was not audited because the event was not auditable according to the current audit policy.
Category:: Programmatic
Cause:: The custom audit event was either undefined in the audit configuration or it was not auditable according to the audit policy in effect.
Action:: Check the audit policy in effect.

MDS-90149: The custom audit event of type "{0}" was not audited because the MDSSession was not associated with a sandbox.
Category:: Programmatic
Cause:: The custom audit event was not audited because the current MDSSession was not associated with a Sandbox.
Action:: Use this API only when the custom audit event is intended to be raised in a sandbox context.

MDS-90243: Content auto merge failed for MO part "{0}" with change type "{1}" because its type is not registered for auto merge.
Category:: Programmatic
Cause:: The specified MOType is not registered for auto merge functionality.
Action:: Register the MOType for auto merge functionality.

MDS-90244: Content auto merge failed for MO part "{0}" with change type "{1}" because its base document is not accessible for read from any configured metadata stores.
Category:: Programmatic
Cause:: Base document is not accessible for read.
Action:: Make sure base document is available for read through any of configured metadata stores.

MDS-90245: Content auto merge failed for MO part "{0}" with change type "{1}" because both base and customization MOParts have conflicts and base MOPart is not a stub.
Category:: Programmatic
Cause:: Base MOPart is not a stub document.
Action:: This is unsupported case. Contact Oracle Support Services.

MDS-90246: Content auto merge failed for MO part "{0}" with change type "{1}" because mainline contains conflicting change type "{2}" for the same MOPart.
Category:: Programmatic
Cause:: There were conflicting changes for MetadataObject between sandbox and mainline and cannot be resolved by content auto merge.
Action:: Contact Application Administrator to resolve these conflicts manually or perform the changes again in a new sandbox.

MDS-90247: Content auto merge failed for MOPart "{0}" with change type "{1}", because conflicts identified for metadata object include changes for non tip or non configured customization layer "{2}".
Category:: Programmatic
Cause:: Conflicts detected for given metadata object include changes for non tip or non configured customization layer.
Action:: This is unsupported case. Contact Oracle Support Services.

MDS-90248: Content auto merge failed for MetadataObject "{0}".
Category:: Programmatic
Cause:: Content auto merge failed for specified MO.
Action:: Please check each MOPart exception for detailed reasons.

MDS-90249: Content auto merge failed for MetadataObject "{0}", because the MO constitutes more than one customization MOPart for the customization layer "{2}".
Category:: Programmatic
Cause:: Customization layer yields multiple layer values.
Action:: This is unsupported case. Contact Oracle Support Services.

MDS-90251: Conflict resolution hook annotation is missing for MOType {0}.
Category:: Configuration
Cause:: Conflict resolution policy was set to "callback" for the document type but associated Conflict resolution hook annotation configuration is missing.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90252: Conflict resolution policy is either found missing or it's value is not set to "callback" for MOType {0}
Category:: Configuration
Cause:: Conflict resolution hook annotation was found in document type but conflict resolution policy configuration was either not supplied or the value was not set to "callback".
Action:: Record the accompanying error and contact the developers of the application.

MDS-90253: AutoMergePluginContext is null for AutoMergePlugin class {0}
Category:: Programmatic
Cause:: AutoMergePluginContext was found as null in AutoMergePlugin instance.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90254: Unable to get AutoMergePlugin for MOType "{0}", Parameter AutoMergePluginContext must have a value.
Category:: Programmatic
Cause:: Parameter AutoMergePluginContext was null.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90255: Conflict resolution hook class "{0}" cannot be instantiated for MOType "{1}"
Category:: Configuration
Cause:: An exception occurred while instantiating conflict resolution hook class.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90256: Unable to get AutoMergePlugin instance from AutoMergePluginFactory for MOType "{0}".
Category:: Programmatic
Cause:: AutoMergePluginFactory returned null for AutoMergePlugin.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90257: Unable to get AutoMergePluginFactory instance from ConflictResolutionHook for MOType "{0}".
Category:: Programmatic
Cause:: ConflictResolutionHook returned null for AutoMergePluginFactory.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90258: Conflict resolution hook class "{0}" cannot be instantiated to get merge handler for MOType "{1}"
Category:: Configuration
Cause:: An exception occurred while instantiating conflict resolution hook class to get merge handler.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90259: Unable to get MergeHandler instance from MergeHandlerFactory for MOType "{0}".
Category:: Programmatic
Cause:: MergeHandlerFactory returned null for MergeHandler.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90260: Unable to get MergeHandlerFactory instance from ConflictResolutionHook for MOType "{0}".
Category:: Programmatic
Cause:: MergeHandlerFactory returned null for MergeHandlerFactory.
Action:: Record the accompanying error and contact the developers of the application.

MDS-90343: Sandbox "{0}" Apply operation failed for MO part "{1}" since conflict were identified with mainline changes for MO Part "{2}" that violates the relationship and dependency constraints.
Category:: Programmatic
Cause:: Sandbox changes violate some dependency constraints with mainline changes.
Action:: Contact Application Administrator to resolve these conflicts manually or perform the changes again in a new sandbox.

MDS-90344: Sandbox "{0}" apply operation with content auto merge failed.
Category:: Programmatic
Cause:: Sandbox apply operation with auto merge failed.
Action:: Please check each MO exception for detailed reasons.

MDS-90345: Failure to get conflicts for sandbox
Category:: Programmatic
Cause:: Target label is older than the sandbox mainline label.
Action:: Specify a target label which is later than current label.

MDS-90346: Invalid SandboxUsage. The sandbox name "{0}" in sandboxUsage does not match with Sandbox instance being operated upon.
Category:: Programmatic
Cause:: Wrong sandbox name used while retrieving MDSSession for conflict resolution.
Action:: Use right SandboxUsage that was used earlier for making the sandbox changes.

MDS-90347: Retry refresh operation on Sandbox "{0}" failed as it detected some unexpected mainline changes on MDSSession which is intended for conflict resolution, for following documents : {1}
Category:: Programmatic
Cause:: Unexpected mainline changes detected on MDSSession that was retrieved for conflict resolution during sandbox refresh operation.
Action:: Cancel mainline document changes from the MDSSession and retry the refresh operation.

MDS-90348: This operation cannot continue as Refresh is in progress for Sandbox {0}.
Category:: Programmatic
Cause:: Some other refresh operation might be in progress.
Action:: Cancel or End the in-progress refresh before trying this operation.

MDS-90349: This operation cannot continue as Refresh operation is either not initiated OR already ended for Sandbox {0}.
Category:: Programmatic
Cause:: Sandbox beginRefresh() hasn't been called.
Action:: Invoke the beginRefresh() first before this operation.

MDS-90350: This operation cannot continue as in progress refresh transaction is not yet completed for Sandbox {0}.
Category:: Programmatic
Cause:: Sandbox refresh operation hasn't ended using endRefresh() call.
Action:: Invoke the endRefresh() before trying this operation.

MDS-90351: Tip customization layer name and value are not defined for refresh operations for Sandbox {0}.
Category:: Programmatic
Cause:: Tip customization layer name and value are not defined.
Action:: Define tip customization layer name and value to perform sandbox refresh.

MDS-90352: Refresh operation cannot be ended since there are pending conflicts to resolve for Sandbox {0}.
Category:: Programmatic
Cause:: There are pending conflicts to resolve.
Action:: Resolve the pending conflicts and try the operation again.

MDS-90353: Sandbox name is null or empty.
Category:: Programmatic
Cause:: Sandbox name was null or empty.
Action:: Use a valid sandbox name that is not empty or null.

MDS-90500: Count of unresolved merge conflict(s) - {0}
Category:: Data
Cause:: One or more unresolved merge conflict(s) exists.
Action:: For more details, use getUnresolvedMergeConflicts() method on MOPartChangeContentAutoMergeException instance.

MDS-90501: Unexpected content auto-merge error
Category:: Programmatic
Cause:: An unexpected content auto-merge error occurred.
Action:: Please resolve the conflict before attempting auto-merge operation again.

MDS-90502: Invalid input documents for content auto-merge operation.
Category:: Data
Cause:: Invalid documents are provided to perform content auto-merge operation.
Action:: Provide valid documents.

MDS-90503: Limited support available for XSD content auto-merge operation.
Category:: Programmatic
Cause:: Unable to auto-merge changes being made by the request or by another user done to XSD metadata object.
Action:: Please resolve the conflict before attempting auto-merge operation again.

MDS-90504: No support to auto-merge updates done to elements with brittle local reference.
Category:: Data
Cause:: Updates done on elements with brittle local reference.
Action:: Resolve the conflict before attempting auto-merge operation again.

MDS-90505: Auto-merge synchronous XML tree walk failure occurred while handling following merge conflict - * {0}
Category:: Data
Cause:: An error occurred in the MDSDocumentAutoMergePlugin.
Action:: Check for log messages. If the problem persists, contact Oracle Support Services.

MDS-90506: No support to auto-merge move operation
Category:: Data
Cause:: Encountered move operation while performing content auto-merge operation.
Action:: Resolve the conflict before attempting auto-merge operation again.

MDS-90507: Type annotation "automerge" for child-list order preference on element with local reference "{0}" in metadata object "{1}" does not have valid value. Valid values are "childListOrderNotImportant" and "childListOrderImportant"
Category:: Data
Cause:: Child-list of the underlying element was modified as part of content auto-merge operation.
Action:: Provide valid value for "automerge" type-annotation. Valid values are "childListOrderNotImportant" and "childListOrderImportant".

MDS-90508: Type annotation automergeChildListOrderDefault set on element definition of root element in metadata object "{0}" does not have valid value. Valid values are "childListOrderNotImportant" and "childListOrderImportant".
Category:: Data
Cause:: Invalid value provided for automergeChildListOrderDefault type-annotation.
Action:: Provide valid value for automergeChildListOrderDefault type-annotation. Valid values are "childListOrderNotImportant" and "childListOrderImportant".

MDS-90540: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is inserted with different values "{3}" in the current transaction and "{4}" in another transaction.
Category:: Data
Cause:: Encountered element attribute automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90541: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is updated with different values "{3}" in the current transaction and "{4}" in another transaction.
Category:: Data
Cause:: Encountered element attribute automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90542: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is deleted in the current transaction but updated with value "{3}" in another transaction.
Category:: Data
Cause:: Encountered element attribute automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90543: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is updated with value "{3}" in the current transaction but deleted in another transaction.
Category:: Data
Cause:: Encountered element attribute automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90550: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is inserted with different values "{2}" in the current transaction and "{3}" in another transaction.
Category:: Data
Cause:: Encountered text content element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90551: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is updated with different values "{2}" in the current transaction and "{3}" in another transaction.
Category:: Data
Cause:: Encountered text content element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90552: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is deleted in the current transaction but updated with value "{2}" in another transaction.
Category:: Data
Cause:: Encountered text content element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90553: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is updated with value "{2}" in the current transaction but deleted in another transaction.
Category:: Data
Cause:: Encountered text content element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90560: Unable to automerge insertion of element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered element insertion automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90561: Unable to automerge insertion of merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered merge-unit insertion automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90562: Unable to automerge updates done to element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered element update automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90563: Unable to automerge updates done to merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered merge-unit update automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90564: Unable to automerge changes done to element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since it is deleted in the current transaction but its fragment contents are updated in another transaction.
Category:: Data
Cause:: Encountered element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90565: Unable to automerge changes done to merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since it is deleted in the current transaction but its fragment contents are updated in another transaction.
Category:: Data
Cause:: Encountered merge-unit automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90566: Unable to automerge changes done to element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents are updated in the current transaction but this element is deleted in another transaction.
Category:: Data
Cause:: Encountered element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90567: Unable to automerge changes done to merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents are updated in the current transaction but this merge-unit is deleted in another transaction.
Category:: Data
Cause:: Encountered merge-unit automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90568: Unable to automerge changes done to element "{0}" with local reference "{1}" since it is deleted in the current transaction but moved under a different parent in another transaction.
Category:: Data
Cause:: Encountered element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90569: Unable to automerge insertion of element with local reference "{0}" in the current transaction since it is inserted under a different parent in another transaction.
Category:: Data
Cause:: Encountered element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90570: Unable to automerge insertion of root element "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered element insertion automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90571: Unable to automerge insertion of root merge-unit "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered merge-unit insertion automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90572: Unable to automerge updates done to root element "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered element update automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90573: Unable to automerge updates done to root merge-unit "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.
Category:: Data
Cause:: Encountered merge-unit update automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90574: Unable to automerge changes done to element "{0}" with local reference "{1}" since it is moved under a different parent in the current transaction but deleted in another transaction.
Category:: Data
Cause:: Encountered element automerge conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

MDS-90590: Unable to automerge updates done to element "{0}" with local reference "{1}" since its child order differs between the current transaction and another transaction.
Category:: Data
Cause:: Encountered child order conflict while performing content automerge.
Action:: Resolve the conflict before attempting automerge operation again.

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

MDS-91002: MDS Application runtime MBean for "{0}" is not available. "{1}" operation failure.
Category:: Configuration
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.

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

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

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

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

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

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

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

MDS-91010: The "adf-config" element is not available in the given archive file. "{0}" operation failure.
Category:: Configuration
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.

MDS-91011: No "mds-config" element exists in the adf-config.xml of the given archive. "{0}" operation failure.
Category:: Configuration
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.

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

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

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

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.
Category:: Data
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.

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.
Category:: Data
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.

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.
Category:: Data
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.

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.
Category:: Configuration
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.

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

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.
Category:: Configuration
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.

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

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

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

MDS-91024: Parameters "{0}" and "{1}" cannot be specified at the same time.
Category:: Data
Cause:: The two parameters are not allowed to be specified at the same time.
Action:: Remove one of the parameters.

MDS-92000: Oracle Metadata Services schema upgrade is invalid.
Category:: Upgrade
Cause:: Specified Metadata Services schema was updated but is invalid.
Action:: Restore the Metadata Services schema from a backup and retry. Check the error messages in log file. Correct the problem before running the Assistant again.

MDS-92001: The upgrade is not supported from Oracle Metadata Services schema version of {0}.
Category:: Upgrade
Cause:: An unsupported base schema version was being upgraded.
Action:: Refer to the Oracle Metadata Services Upgrade Guide for supported versions to upgrade.

MDS-92002: Error in upgrading Oracle Metadata Services schema.
Category:: Upgrade
Cause:: An unexpected error occurred during Oracle Metadata Services schema upgrade.
Action:: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

MDS-92003: Error occurred while verifying the character set in target Metadata Services schema
Category:: Upgrade
Cause:: A SQL error occurred while verifying the character set in target Metadata Services schema.
Action:: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

MDS-92004: Error occurred while closing the resources during Metadata Services schema upgrade
Category:: Upgrade
Cause:: A SQL error occurred while closing the resources during Metadata Services schema upgrade.
Action:: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

MDS-92005: Error occurred while closing Metadata Services schema upgrade log files.
Category:: Upgrade
Cause:: An unexpected error occurred while closing Metadata Services schema upgrade log files.
Action:: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

MDS-92006: Oracle Metadata Service schema status is invalid.
Category:: Upgrade
Cause:: Specified Oracle Metadata Services database schema was invalid.
Action:: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

MDS-92007: Error occurred while verifying the user privileges in target Metadata Services schema
Category:: Upgrade
Cause:: A SQL error occurred while verifying the user privileges in target Metadata Services schema.
Action:: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

MDS-92008: The logon DBA user does not have sufficient privileges to upgrade the target Metadata Services schema user
Category:: Upgrade
Cause:: The logon DBA user needs to have grant execute privilege on specific DBMS packages to other users for upgrading the schema user privileges in target Metadata Services schema.
Action:: Logon as SYSDBA or other DBA users with sufficient privileges to grant execute on DBMS packages to other users and run the Assistant again.

MDS-92009: Oracle Metadata Services schema is not enabled for EBR.
Category:: Upgrade
Cause:: Specified Oracle Metadata Services database schema was not enabled for EBR.
Action:: Specify an Oracle Metadata Service schema that is enabled for EBR or Specify an upgrade for Oracle database type.

MDS-92010: Unable to continue due to an unexpected error
Category:: Upgrade
Cause:: An unexpected error occurred.
Action:: See the secondary error message for additional details.