56 RCS-00001 to RCS-23000

RCS-00001: unexpected error has occurred: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00003: failed to instantiate an instance of class [{0}]: Cause: The class could be found in the classpath; Action: Ensure the class is included in the application classpath
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00002: unexpected error has occurred: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00004: required parameter [{0}] is missing or null: Cause: An attempt was made to invoke a method without passing all the required parameters; Action: Ensure all required parameters are passed to the method
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00006: cannot find resource [{1}] in resource bundle [{0}]: Cause: An attempt was made to load a text resource from a resource bundle but the resource was not found. The resource key was used instead.; Action: Add the missing resource to the resource bundle or correct the resource reference.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00005: cannot find resource bundle [{0}]: Cause: The resource bundle could not be found on the classpath; Action: Ensure the resource bundle is included in the application classpath
Level: 1

Type: ERROR

Impact: Configuration

RCS-00007: value [{1}] for parameter [{0}] is invalid: Cause: An invalid parameter value was passed to the method; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00009: operation [{0}] is not supported in this release: Cause: An attempt was made to invoke a method that is not supported in this release; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00008: expected type [{1}] but received type [{2}] for parameter [{0}]: Cause: An attempt was made to read a parameter value but the parameter type was invalid; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00011: no objects bound to name [{0}]: Cause: An attempt was made to find an object using the specified name. No object was bound to that name.; Action: Verify that the named object has not been renamed or deleted and re-try the operation.
Level: 1

Type: ERROR

Impact: Logging

RCS-00010: name [{0}] is not valid for a resource catalog object: Cause: An attempt was made to access a resource catalog object using a name that does not conform to the required structure or format; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00012: error while initializing class: Cause: An unexpected error occurred during execution of a static initializer while loading a Java class. The class could not be loaded; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00015: error while canceling pending changes for RCSession [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00014: error while flushing pending changes for RCSession [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-00013: invalid MDS reference [{0}]: Cause: An attempt was made to create an MDS Reference from a String that does not conform to the required format; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00016: error while creating a URI using catalog Id [{0}] and catalog path [{1}]: Cause: The catalog id or catalog path contain characters that are invalid in a URI; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00018: error while creating a URI using repository [{0}] and repository path [{1}]: Cause: The repository id or repository path contain characters that are invalid in a URI; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00017: error [{1}] while creating a catalog reference from URI [{0}]: Cause: The specified URI could not be parsed either because it is not a Catalog Reference URI or the URI is corrupt; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00019: error while creating a repository reference from URI [{0}]: Cause: The specified URI could not be parsed either because it is not a repository reference URI or the URI is corrupt; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00021: error [{0}] while setting default value [{2}] on attribute descriptor [{1}]: Cause: Review the cause included in the message for more details; Action: Take appropriate action based on the cause included in the message and any underlying exceptions
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00020: data type [{1}] in attribute descriptor [{0}] is not supported: Cause: An attempt was made to create an attribute descriptor using an invalid data type; Action: Change the attribute descriptor to use a supported data type.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-00023: operation [{0}] is not allowed in the current session: Cause: An attempt was made to perform a catalog related operation in a session configured for connection operations only; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00022: Session properties cannot be modified after the session has been initialized.: Cause: An attempt was made to modify the properties of a resource catalog session after the session had been initialized; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-00026: operation canceled. operation=[{0}]. reason=[{1}]: Cause: An operation was canceled by a user. This usually happens when the operation was taking too long to complete.; Action: No action is necessary
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-00027: search canceled. root context=[{0}]. expression=[{1}]. reason=[{2}]: Cause: A search operation was canceled by a user because it may have taken too long to complete; Action: No action is necessary
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-00028: An attempt was made to modify an immutable Name object: Cause: A program attempted to modify a immutable Name object; Action: Correct the program so it does not attempt to modify immutable names
Level: 1

Type: ERROR

Impact: Programmatic

RCS-01000: The resource catalog service has not been configured for this application.: Cause: Configuration parameters for the resource catalog service could not be found in the application's adf-config.xml file; Action: Refer to the resource catalog service documentation and add the necessary configuration parameters to the application's adf-config.xml file
Level: 1

Type: ERROR

Impact: Configuration

RCS-01001: configuration parameter [{1}] is missing from resource catalog instance [{0}]: Cause: A required configuration parameter was not specified in the adf-config.xml file.; Action: Refer to the resource catalog service documentation and add the missing configuration parameter to the configuration file
Level: 1

Type: ERROR

Impact: Configuration

RCS-01003: error occurred initializing MDS instance [{0}]: Cause: The MDS instance used by the resource catalog service could not be initialized due to an previous error; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01002: Invalid configuration parameter. RCInstance=[{0}] Parameter=[{1}] Invalid value=[{2}] Substituted value=[{3}]: Cause: The resource catalog service was configured with an invalid parameter value; Action: Refer to the resource catalog service documentation and correct the configuration parameters
Level: 1

Type: ERROR

Impact: Configuration

RCS-01004: a resource catalog instance with Id [{0}] already exists.: Cause: An attempt was made to create a new resource catalog instance using an ID that is already in use by another instance.; Action: Verify that the instance Id specified in adf-config.xml is unique. If it is unique, verify that the application code is not attempting to create multiple instances with the same ID instead of re-using an existing instance.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01006: error while obtaining an MDS Session from session provider [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01005: error while obtaining a connection context using connection context provider [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01007: an ADFContext has not been registered for name [{0}].: Cause: The named ADFContext required by the resource catalog service cannot be found; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01009: error while creating a connections metadata object using path [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-01008: error while initializing the connections context: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01010: error while deleting a connections metadata object using path [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-01011: error while opening a connections metadata object using path [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-01013: cannot find any resource catalog extensions on the classpath: Cause: The classpath did not include any jars that declare resource catalog extensions. The resource catalog requires at least one connection type and one resource catalog adapter to function.; Action: Add one or more jar files containing these extensions to your application classpath
Level: 1

Type: WARNING

Impact: Configuration

RCS-01012: error while attempting to locate the resource catalog extensions.: Cause: An exception was raised while attempting to find resource catalog extensions from the classpath; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01015: error while instantiating CatalogItemFactoryPlugin [{0}]: Cause: The specified plugin could not be instantiated or does not implement the required interface. Failure to load one plugin does not prevent the loading of others.; Action: Add the missing class to the classpath, modify the class to implement the correct interface or remove the declaration from META-INF/rc_ext.xml
Level: 1

Type: ERROR

Impact: Configuration

RCS-01014: error while processing a resource catalog extension using URL [{0}]: Cause: An exception was raised while loading a resource catalog extension. Failure to load one extension does not prevent other extensions from loading; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01017: duplicate resource type [{0}]: Cause: A Resource Type with the specified ID has already been loaded. The duplicate was ignored; Action: Remove the declaration for the duplicate resource type from META-INF/rc_ext.xml
Level: 1

Type: WARNING

Impact: Configuration

RCS-01016: error while instantiating a resource type [{0}]: Cause: The specified plugin class could not be instantiated or does not implement the required interface. Failure to load one plugin does not prevent the loading of others.; Action: Add the missing class to the classpath, modify the class to implement the correct interface or remove the declaration from META-INF/rc_ext.xml
Level: 1

Type: ERROR

Impact: Configuration

RCS-01019: Target directory [{0}] for resource catalog configuration files does not exist.: Cause: An attempt was made to dynamically create a resource catalog instance, but the target directory specified by the client does not exist.; Action: Create the target directory or configure the client to use a different directory for the resource catalog configuration files
Level: 1

Type: ERROR

Impact: Configuration

RCS-01021: Target directory [{0}] for resource catalog configuration files is not readable.: Cause: An attempt was made to dynamically create a resource catalog instance, but the target directory specified by the client is not readable; Action: Change the permissions on the target directory so it is readable or configure the client to use a different path for the resource catalog configuration files.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01020: Target path [{0}] for resource catalog configuration files is not valid.: Cause: An attempt was made to dynamically create a resource catalog instance, but the target path specified by the client is not a directory; Action: Configure the client to use a different path for the resource catalog configuration files. The path must be a directory
Level: 1

Type: ERROR

Impact: Configuration

RCS-01022: Target directory [{0}] for resource catalog configuration files is not writable.: Cause: An attempt was made to dynamically create a resource catalog instance, but the target directory specified by the client is not writable; Action: Change the permissions on the target directory so it is writable or configure the client to use a different path for the resource catalog configuration files.
Level: 1

Type: ERROR

Impact: Configuration

RCS-01025: cannot find configuration template [{0}]: Cause: The specified configuration file template could not be found on the application classpath; Action: Ensure the missing template is included in the classpath
Level: 1

Type: ERROR

Impact: Configuration

RCS-01024: error while creating a resource catalog instance: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-01023: An ADFContext has already been registered using name [{0}].: Cause: The named ADFContext required by the resource catalog Service cannot be registered using the specified name because the name is already in use; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

RCS-02000: error while attempting to lookup connection [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02001: cannot find connection [{0}]: Cause: The specified connection could not be found. The connection may have been deleted or renamed; Action: Create a new connection with the specified ID
Level: 1

Type: ERROR

Impact: Configuration

RCS-02005: The resource catalog adapter factory [{1}] for connection type [{0}] does not implement the required interfaces.: Cause: Resource catalog adapters are required to implemented a specific set of interfaces. The specified adapter does not implement one or more of these interfaces.; Action: If the adapter was provided by Oracle, contact Oracle Support Services. Otherwise contact the provider of the adapter
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02004: A resource catalog adapter has already been registered for connection type [{0}]. The duplicate will be ignored: Cause: Two or more META-INF/rc_ext.xml files found on the application classpath include resource catalog adapter declarations for the same connection type.; Action: Remove the duplicate adapter declarations from the application classpath
Level: 1

Type: WARNING

Impact: Logging

RCS-02003: error while registering resource catalog adapter factory [{1}] for connection type [{0}]: Cause: An exception was raised while registering the resource catalog adapter; Action: Verify the connection type registered and that the resource catalog adapter factory class is included in the application classpath
Level: 1

Type: ERROR

Impact: Logging

RCS-02006: cannot find a resource catalog adapter for connection type [{0}]: Cause: A resource catalog adapter has not been registered for the specified connection type.; Action: Add an appropriate resource catalog adapter implementation to the application classpath
Level: 1

Type: ERROR

Impact: Logging

RCS-02010: error while closing subcontext [{0}] for repository id [{1}], repository path [{2}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02009: error while creating InitialContext for repository ID [{0}], repository path [{1}] using InitialContextFactory [{2}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02012: The value [{1}] of resource catalog environment parameter [{0}] is not valid.: Cause: An attempt was made to read a resource catalog environment variable but the variable contained an invalid value.; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02011: cannot find resource catalog environment parameter [{0}]: Cause: An expected parameter could not be found in the resource catalog environment hashtable; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02013: error while obtaining the connection type for connection [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02014: resource catalog adapter factory [{0}] returned null for repository reference [{1}]: Cause: The resource catalog adapter factory returned null when a CatalogContext object was expected.; Action: If the resource catalog adapter was provided by Oracle, contact Oracle Support Services. Otherwise contact the provider of the adapter
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-02017: error while creating InitialContext for repository ID [{0}], repository path [{1}] using InitialContextFactory [{2}]. Error was [{3}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-02016: cannot find connection type for connection [{0}]: Cause: The resource catalog service could not determine the connection type of the specified connection.; Action: Declare the connection type in META-INF/rc_ext.xml (runtime) or META-INF/extension.xml (designtime).
Level: 1

Type: WARNING

Impact: Programmatic

RCS-02015: unexpected object type [{1}] returned by resource catalog adapter factory [{0}] for repository reference [{2}]: Cause: The resource catalog adapter factory returned an invalid object type. Adapter factories are required to return an instance or oracle.adf.rc.core.CatalogContext.; Action: If the InitialContextFactory was provided by Oracle, contact Oracle Support Services. Otherwise contact the provider of the InitialContextFactory
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RCS-03000: cannot find resource catalog [{0}] using MDS path=[{1}]: Cause: An attempt was made to open a resource catalog, but the catalog could not be found; Action: Verify the catalog exists in the MDS repository. If the document exists, check the resource catalog configuration settings in adf-config.xml
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03002: invalid resource catalog ID [{0}] using MDS path [{1}]: Cause: The MDS path generated using the specified resource catalog ID was rejected by MDS; Action: Use an ID whose structure and characters meets the requirements for MDS references.
Level: 1

Type: ERROR

Impact: Logging

RCS-03001: duplicate resource catalog ID [{0}] using MDS path [{1}]: Cause: A resource catalog with the specified ID already exists.; Action: Open the existing catalog or choose a different catalog ID if you want to create a new catalog.
Level: 1

Type: ERROR

Impact: Logging

RCS-03003: error while renaming catalog from [{0}] to [{1}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03005: error while deleting resource catalog [{0}] using MDS Path [{1}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03008: error while removing element [{1}] from resource catalog [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03010: error while adding element [{1}] to parent element [{2}] in resource catalog [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03011: error while processing an elementAdded event for element [{3}], folder [{2}] in resource catalog [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03014: unrecognized element [{1}:{2}] found in resource catalog [{0}]: Cause: The resource catalog definition contains an unrecognized element type. The element was ignored.; Action: Remove the invalid element from the resource catalog definition
Level: 1

Type: WARNING

Impact: Logging

RCS-03013: error while processing an elementRenamed event, renaming element [{2}] to [{3}] in folder [{1}], resource catalog [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03012: error while processing an elementModified event for element [{3}], folder [{2}] in resource catalog [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03015: Element [{1}] of resource catalog [{0}] has been excluded from the catalog due to error [{2}].: Cause: An exception was raised by an underlying component that prevented the specified element from being included in the catalog.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03016: An error has occurred while creating folder [{1}] in resource catalog [{0}]. The folder was ignored.: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03018: An error has occurred while processing expression filter [{2}] of folder [{1}] in resource catalog [{0}]. The filter was ignored.: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03017: An error has occurred while creating dynamic folder [{1}] in resource catalog [{0}]. The dynamic folder was ignored.: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03019: An error has occurred while creating custom filter [{2}] of folder [{1}] in resource catalog [{0}]. The folder was ignored. Filter class=[{3}].: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03021: cannot find resource using repository [{0}] and repository path [{1}]. The repository may not be accessible or the resource may have been deleted or renamed: Cause: The source repository may be temporarily inaccessible or the resource may have been deleted or renamed in the source repository.; Action: Refresh the parent folder see the revised contents
Level: 1

Type: WARNING

Impact: Logging

RCS-03020: An error has occurred while creating custom folder [{1}] in resource catalog [{0}]. The custom folder was ignored. Factory class=[{2}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03023: An error has occurred while querying source repository [{2}], repository path [{3}] for dynamic folder [{1}] in resource catalog [{0}]. The dynamic folder source was ignored: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03022: unexpected object type returned using repository [{3}] and repository path [{4}] in resource catalog [{0}]. Expected [{1}] but received [{2}] from adapter [{5}]: Cause: A resource catalog adapter returned an unexpected item type; Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03024: The custom content element [{1}] in resource catalog [{0}] does not specify a CustomContextProvider class. The element was ignored.: Cause: The specified custom content element does not include a class attribute specifying the CustomContentProvider implementation. This attribute is required.; Action: Add the missing attribute to the specified element or remove it from the catalog.
Level: 1

Type: ERROR

Impact: Logging

RCS-03027: The catalog definition filter [{1}] in resource catalog [{0}] does not implement the oracle.adf.rc.spi.plugin.catalog.CatalogDefinitionFilter interface. The filter was ignored: Cause: The specified filter class does not implement the required interface.; Action: Modify the specified class so it implements the required interface or replace it with one that does.
Level: 1

Type: ERROR

Impact: Logging

RCS-03026: An error has occurred while instantiating catalog definition filter [{1}] in resource catalog [{0}]. The filter was ignored.: Cause: The specified class could not be found in the application classpath.; Action: Verify the specified class is included in the application classpath.
Level: 1

Type: ERROR

Impact: Logging

RCS-03025: error while creating an instance of [{2}], referenced by CustomContent element [{1}] in resource catalog [{0}]: Cause: The specified class could not be found in the application classpath.; Action: Add the specified class to the application classpath.
Level: 1

Type: ERROR

Impact: Logging

RCS-03029: An error has occurred while creating a custom folder using InitialContextFactory [{1}] in resource catalog [{0}]. The custom folder was ignored.: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03028: An error has occurred while invoking catalog definition filter [{2}] in resource catalog [{0}]. The filter was ignored.: Cause: An exception was raised by the catalog definition filter; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03032: error while adding a transient catalog element to a persistent catalog folder.: Cause: Transient catalog elements can only be added to catalogs by CustomContentProviders. They cannot be added to persistent catalog definitions.; Action: Change the client code that is invoking the specified API so it uses PersistentElements instead of TransientElements.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03031: An error has occurred while creating catalog item [{1}] in catalog [{0}]. The catalog item was ignored.: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03030: An error has occurred while refreshing the contents of folder [{1}] in catalog [{0}]. Some child elements may not have been loaded.: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03034: An attempt was made to add a persistent catalog element to a transient catalog folder.: Cause: Transient catalog folders are intended for use by CustomContentProviders. They can only contain other transient elements; Action: Change the client code so it uses TransientElements instead of PersistentElements
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03033: operation [{1}] of interface [{0}] is not supported for transient elements.: Cause: An attempt was made to invoke an unsupported operation on a transient catalog element.; Action: Change the client code that it does not invoke the specified method.
Level: 1

Type: ERROR

Impact: Programmatic

RCS-03038: An error has occurred while creating component [{1}] in resource catalog [{0}]. The component was ignored.: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03037: error while opening catalog [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-03036: cannot resolve reference to resource using repository [{2}], repository path [{3}] at element [{1}] in catalog [{0}]: Cause: The specified resource element could not be resolved because the repository or repository path could not be found.; Action: Verify that the catalog entry is correct, the repository exists in your application and the repository path is valid.
Level: 1

Type: ERROR

Impact: Logging

RCS-03035: cannot resolve reference to repository using repository [{2}], repository path [{3}] at element [{1}] in catalog [{0}]: Cause: The specified repository element could not be resolved because the repository or repository path could not be found.; Action: Verify that the catalog entry is correct, the repository exists in your application and the repository path is valid.
Level: 1

Type: ERROR

Impact: Logging

RCS-04000: error while processing predicate [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04001: query expression [{0}] is invalid: Cause: The query string does not conform to the JNDI query syntax (RFC 2254); Action: Use a query string that conforms to the JNDI query syntax (RFC 2254)
Level: 1

Type: ERROR

Impact: Programmatic

RCS-04004: error while comparing catalog item [{0}] with [{1}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04003: The type [{1}] of attribute [{0}] does not implement the Comparable interface.: Cause: The specified attribute value is of an unsupported data type that does not implement the Comparable interface. All attributes declared as searchable by a resource catalog adapter schema must implement this interface.; Action: Modify the resource catalog schema for the source adapter so this attribute is not searchable or modify the attribute's datatype so it is Comparable.
Level: 1

Type: ERROR

Impact: Logging

RCS-04002: query expression [{0}] contains invalid wildcard syntax: Cause: Wildcards can only be used with the EQUALS operator; Action: Modify the query expression so wildcards are only used with the EQUALS operator
Level: 1

Type: ERROR

Impact: Programmatic

RCS-04010: An error has occurred while searching folder [{1}] in catalog [{0}]. The folder was skipped. Implementation class=[{2}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04012: An error has occurred while searching custom folder [{1}] in catalog [{0}]. The folder was skipped. Implementation class=[{2}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04011: An error has occurred while searching folder [{1}] in repository [{0}]. The folder was skipped. Implementation class=[{2}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-04013: attribute [{0}], value [{1}], has an unsupported data type [{2}]: Cause: An attribute returned a value with an unsupported data type. The value was converted to a String.; Action: Ensure that the values for all resource catalog attributes correspond to one of the supported data types defined by oracle.adf.rc.attribute.AttributeConstants
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05000: error processing transfer set [{0}]: Cause: An exception was raised by an underlying component.; Action: Review the exception details for more information. If the information provided is not sufficient to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-05002: transfer set [{0}] is empty: Cause: The transfer set did not include any connection or catalog entries.; Action: Create a transfer set containing at least one connection or one catalog and then repeat the operation.
Level: 1

Type: ERROR

Impact: Logging

RCS-05004: An error has occurred transferring connection [{1}] in transfer set [{0}]. The failure control is set to [{2}].: Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.; Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05003: An error has occurred while transferring connections in transfer set [{0}]. The failure control is set to [{1}].: Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.; Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05006: An error has occurred while transferring catalogs in transfer set [{0}]. The failure control is set to [{1}].: Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.; Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05005: Connection ID [{1}] in transfer set [{0}] already exists in the target environment. The duplicates control is set to [{2}].: Cause: A connection included in the specified transfer set already exists in the target environment and the duplicates control is set to fail upon detecting a duplicate.; Action: Remove the duplicate connection from the target environment and then restart the transfer process. Alternatively, change the duplicates control to overwrite or ignore duplicates.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05008: Catalog ID [{1}] in transfer set [{0}] already exists in the target environment. The duplicates control is set to [{2}].: Cause: A catalog included in the specified transfer set already exists in the target environment and the duplicates control is set to fail upon detecting a duplicate.; Action: Remove the duplicate catalog from the target environment and then restart the transfer process. Alternatively, change the duplicates control to overwrite or ignore duplicates.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-05007: An error has occurred while transferring catalog [{1}] in transfer set [{0}]. The failure control is set to [{2}].: Cause: An exception was raised by an underlying component and the transfer process was configured to fail when encountering an error.; Action: Review the cause of the failure, correct it, and then restart the transfer process. Alternatively, change the failure controls to ignore errors.
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-06001: An unexpected error has occurred destroying a pooled object. Pool=[{0}]: Cause: Review the root cause of the exception for more details.; Action: If the root cause does not provide sufficient information to resolve the issue, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

RCS-06002: leakage detected while destroying object pool [{0}]. In-use count=[{1}]: Cause: An attempt was made to destroy an object pool when objects were still in use. This is a potential memory leak; Action: Identify the clients of the object pool and ensure all objects are returned to the pool before it is destroyed.
Level: 1

Type: WARNING

Impact: Programmatic

RCS-23000: An unexpected error has occurred.: Cause: Review the root cause of the exception in the log file for more details.; Action: If the root cause does not provide sufficient information to resolve the issue, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Logging