WCS-06901: Failure attempting to create JCR Manager Repository object
Cause: An attempt to create a JCR Manager Repository object failed.
Action: Contact Oracle Support Services.
WCS-06902: Error searching for Repository Configuration Descriptors: {0}
Cause: An exception occurred while searching the class path for Repository Configuration Descriptors.
Action: Verify that the class path is valid. Examine the error text associated with this exception for more information.
WCS-06903: Repository Descriptor {0} is not valid
Cause: The Repository Descriptor failed to parse or lacked required elements.
Action: Verify that the Repository Descriptor is syntactically valid and contains all required elements.
WCS-06904: Calling setValue on fixed value parameter {0} is not allowed
Cause: The setValue method was called on a fixed JamConfigParam. This is not allowed.
Action: Remove the call to setValue.
WCS-06905: Credentials for user {0} not found using credential store key {1}
Cause: An attempt to fetch user credentials failed. The credential store key may be incorrect, or user credentials may be required.
Action: Verify that the credential store key is correct. If necessary, provide credentials for the user.
WCS-06906: To set, fetch, or remove the default credentials, the credential store key must not be null.
Cause: An attempt was made to set, fetch, or remove the default credentials with an invalid credential store key.
Action: Supply a valid credential store key. If the JCR Adapter name is being used as the credential store key, make sure it is not null.
WCS-06907: User authentication is not supported for this JCR adapter. Setting default credentials is not allowed.
Cause: An attempt was made to set default user credentials to a JCR adapter that does not support user authentication.
Action: Avoid calling the JamAdapterInfo.setDefaultCredentials() method when the JCR adapter does not support user authentication.
WCS-06908: JCR Repository creation failure
Cause: A JCR repository instance could not be created from the parameters provided.
Action: Check the configuration parameters, and retry.
WCS-06909: JCR Repository login failure
Cause: An attempt to log in to a JCR repository failed.
Action: Check configuration parameters and user credentials, and retry.
WCS-11001: Error on content write: {0}
Cause: The content write operation failed for the given reason.
Action: Investigate the reason for the failure.
WCS-11002: Internal server error: {0}
Cause: An unexpected internal error has occurred.
Action: Contact Oracle Support Services.
WCS-11003: Invalid HTTP request
Cause: A client has submitted an invalid HTTP request.
Action: The client should re-send the corrected request.
WCS-11004: Request not implemented by server
Cause: The requested operation is not implemented by this server.
Action: The operation is not implemented. The client should not repeat the request.
WCS-11005: Request forbidden
Cause: The server has refused the client's request for an operation.
Action: The client should not repeat the request as the operation is forbidden.
WCS-11006: Path not found {0}
Cause: The requested path has not been found on the server.
Action: The client should correct the path and re-send the request.
WCS-11007: Unknown content view name: {0}
Cause: The content view name is not valid.
Action: The client should correct the content view name and re-send the request.
WCS-11008: Not an ISO8601 date: {0}
Cause: The client supplied a date which is not in ISO8601 format.
Action: The client should correct the date format and re-send the request.
WCS-11009: Not an http date: {0}
Cause: The client supplied a date which is not in http date format.
Action: The client should correct the date format and re-send the request.
WCS-11010: Namespace not supported: {0}
Cause: The repository does not support the given namespace.
Action: No action required.
WCS-11011: Failed to parse date: {0}
Cause: The given date could not be understood.
Action: The client should correct the date format and re-send the request.
WCS-11012: Failed to find connection {0}
Cause: The given connection could not be found.
Action: Ensure that the connection name is correctly configured in the Oracle Connection Architecture.
WCS-11013: Bad Request
Cause: The client submitted a request that could not be understood by the server.
Action: The client should correct the syntax and resubmit the request.
WCS-11014: Not Modified
Cause: The client has performed a conditional GET request; access is allowed but the document has not changed.
Action: No action required.
WCS-11015: Not Acceptable
Cause: The requested resource cannot generate an entity with an acceptable media type for the client.
Action: No action required.
WCS-11016: Precondition Failed
Cause: A request precondition has failed.
Action: No action required.
WCS-11017: JVM does not support UTF-8 character set.
Cause: The UTF-8 character set is not supported by the JVM.
Action: Contact Oracle Support Services.
WCS-11018: No DAV dead property name matches jcr property name {0}.
Cause: An unexpected JCR property name has been found that does not correspond to a DAV dead property name.
Action: Contact Oracle Support Services.
WCS-11019: Error closing servlet output stream
Cause: There was an error closing the servlet output stream.
Action: No action required.
WCS-11020: Error closing content input stream
Cause: There was an error closing the content input stream.
Action: No action required.
WCS-11101: Invalid ResourceName: {0}
Cause: The given name is not a valid resource name.
Action: The client should correct the URL and re-submit the request.
WCS-11102: Invalid ResourceName. Illegal escape sequence in path: {0}.
Cause: The given name is not a valid resource name as it contains an illegal escape sequence.
Action: The client should correct the URL and re-submit the request.
WCS-11103: JVM does not support UTF-8 character set.
Cause: The UTF-8 character set is not supported by the JVM.
Action: Contact Oracle Support Services.
WCS-11151: Cannot find required environment entry
Cause: A required servlet environment entry was missing.
Action: Review log file for the name of the missing environment entry.
WCS-11152: Invalid Content View: {0}
Cause: The specified content view was not valid.
Action: No action required.
WCS-11153: No Content View
Cause: No content view was specified in the request URL.
Action: Include a content view in the request URL.
WCS-11154: Null VcrUsageChecker classname
Cause: No Vcr usage checker class was set on the Vcr usage checker filter.
Action: Ensure that the appropriate Vcr usage checker class name is set as a parameter on the filter.
WCS-11155: Usage checker is not an instance of oracle.vcr.dav.usagechecker.VcrUsageChecker
Cause: The Vcr usage checker class was the wrong type.
Action: Ensure that the usage checker class is of the correct type.
WCS-11156: Failed to instantiate ServletUsageChecker
Cause: The Vcr usage checker class was not instantiated.
Action: Check the log to establish why instantiation failed.
WCS-35001: Cannot create XML node from data control metadata
Cause: The metadata required to create the XML document was not available or an error occurred in constructing the XML document object.
Action: Ensure that the connection name and other data control metadata is provided.
WCS-35002: The connection name is null.
Cause: The connection name is part of the data control metadata. Either the metadata did not load properly from the XML node or the connection name was not specified while creating the data control with the wizard.
Action: Check the data control definition (.dcx) file.
WCS-35003: Cannot get JCR session
Cause: The login credentials were invalid.
Action: Confirm the credentials and ensure that the connection to the repository can be successfully created.
WCS-35004: Cannot fetch a resource (JCR node) from the repository for path {0}
Cause: The resource paths specified in the data control metadata were invalid.
Action: Check the data control definition (.dcx) file.
WCS-35005: Cannot add global operations to the data control structure
Cause: The resource paths specified in the data control metadata were invalid.
Action: Check the data control definition (.dcx) file.
WCS-35006: Cannot load metadata from XML node
Cause: The data control metadata file (.dcx) had invalid contents.
Action: Check the data control definition (.dcx) file.
WCS-35008: Log on failure
Cause: The provided login credentials were incorrect.
Action: Provide a valid user name and password pair.
WCS-35010: Cannot retrieve connection context from ADF
Cause: The ADF Adapter Framework is not working properly.
Action: Make sure the Oracle ADF libraries are present in your installation.
WCS-35011: Null connection context from ADF
Cause: The connections.xml file was missing or the file format was incorrect.
Action: Make sure that the ADF application is configured properly with correct entries in web.xml and connections.xml.
WCS-35012: Failure looking up the repository connection
Cause: The connection name was invalid or no connection with that name was found in the connection context.
Action: Provide a valid connection name. Validate the connections.xml file.
WCS-35013: Incorrect or missing method parameters
Cause: The provided method parameters were invalid.
Action: Ensure that the method parameters are valid.
WCS-35014: No data control operation or system method to invoke
Cause: Content Data Control got an invokeAction call with no specified method name.
Action: Make sure the methodAction bindings in the page definition file are correct.
WCS-35016: Retrieving data control abstract definition from run time data control object returns null.
Cause: ADF framework has not set the data control definition within the run-time data control
Action: Make sure the dcx and cpx files are correct.
WCS-35017: Cannot configure webApp (web.xml)
Cause: Could not add servlet, servlet mapping, or filter mapping to webApp.
Action: Check the web.xml file for the project.
WCS-35300: Parameters are missing for the operation.
Cause: The ADF framework passed a null parameter map to the data control operation.
Action: Check the page definition file to see if the operation parameters are correctly specified.
WCS-35301: Path parameter is incorrect. It should be a valid JCR repository absolute path string starting with /.
Cause: The specified path parameter is not a valid repository path.
Action: Make sure the path string starts with / and is a valid path in the content repository.
WCS-35302: Type parameter is incorrect.
Cause: The specified type string was not a valid node type in the JCR repository.
Action: Confirm that the type is valid for the content repository on which the data control is based. Both the prefix and the local name should be valid. For example, nt:file and nt:folder are valid types.
WCS-35303: Cannot generate XPath query
Cause: The parameters given in the search operation could not be resolved to a valid XPath query string using the content repository session.
Action: Make sure the attribute names and prefixes used in the parameters are valid and registered in the content repository.
WCS-35304: Incorrect attribute {0} in the predicate
Cause: No such property existed in the repository.
Action: Provide another attribute name that does exist in the repository.
WCS-35305: Incorrect prefix for the attribute {0} in the predicate
Cause: The name space used in the attribute was incorrect or not registered in the repository.
Action: Enter another prefix or report the problem to the JCR adapter provider for the repository.
WCS-35306: Cannot resolve attribute {0} using the repository session
Cause: The attribute was invalid or the prefix was not registered in the JCR session.
Action: Make sure it is a valid attribute name in the repository session.
WCS-35307: Operator {0} not supported
Cause: An invalid operator was used.
Action: Use another, valid operator.
WCS-35309: The XPath query {0} is not supported by the JCR adapter.
Cause: The JCR adapter was not compliant with the XPath support required for the content repository data control.
Action: Confirm that the XPath query is supported by this JCR adapter.
WCS-35310: Error in the JCR repository
Cause: An error occurred in the JCR adapter.
Action: Check the JCR adapter's error log.
WCS-35311: Error getting the item's URL
Cause: An error occurred while generating the URL for an item.
Action: Confirm that the GET servlet is configured properly.
WCS-35312: Invalid return attribute name {0}
Cause: The name of a return attribute must be a valid java name and must be different from 'name', 'URL', 'path' and 'primaryType'.
Action: Verify that the attribute name is valid
WCS-35313: Invalid return attribute type
Cause: The type of a return attribute must be one of the following JCR types Boolean, Integer, Double, String or Date.
Action: Verify that the attribute type is valid
WCS-35314: Cannot get value for attribute {0}
Cause: The value for the specified attribute could not be retrieved from the JCR node.
Action: Check that the JCR path for the attribute is correct
WCS-35900: Illegal value state, cannot read a Value previously streamed
Cause: The application is mixing calls to getStream() and other get* accessors on the same Value object.
Action: Verify your application code.
WCS-35901: Illegal value state, cannot stream a Value previously read
Cause: The application is mixing calls to getStream() and other get* accessors on the same Value object.
Action: Verify your application code.
WCS-35902: Error in value conversion (source type = {0}, target type = {1})
Cause: The JCR values cannot be converted to the specified type.
Action: Verify your application code.
WCS-35903: Error in value conversion (invalid ISO8601 string)
Cause: The specified string is not a valid ISO8601 string as specified by JCR and therefore cannot be converted to a date.
Action: Verify the format of the date string.
WCS-35904: Cannot create REFERENCE values
Cause: Values of type REFERENCE are not supported by this JCR repository.
Action: Avoid using properties of type REFERENCE in your application.
WCS-35905: IO error while reading the binary stream
Cause: The data for the binary property could not be accessed.
Action: Verify that the storage medium for the JCR repository is accessible.
WCS-35906: UTF8 encoding not supported on this system
Cause: The JVM you are using does not support UTF-8 encoding.
Action: Use a supported Java 1.4 compliant JVM.
WCS-35907: This iterator does not contain any more elements
Cause: The iterator has exhausted all its elements.
Action: Check the usage of the RangeIterator by your application.
WCS-35908: This iterator does not support the remove operation
Cause: The remove() operation is not supported on this Iterator.
Action: Avoid making calls to RangeIterator#remove() in your application.
WCS-35909: The Item at path {0} is not a Node
Cause: An item was found at the specified path but it was not a Node.
Action: Check that your application is specifying the correct path.
WCS-35910: {0} is not a known namespace prefix
Cause: A name or path contains a namespace prefix unknown to this repository.
Action: Check the namespace mappings in the current Session.
WCS-35911: {0} is not a known namespace URI
Cause: The specified namespace URI is unknown to the current repository.
Action: Check the set of namespaces allowed by the current repository.
WCS-35912: The prefix {0} is already used
Cause: The specified prefix is already mapped to a namespace and cannot be remapped.
Action: Change the prefix mapping for the URI associated with that prefix before mapping it to another URI.
WCS-35913: {0} is a reserved namespace prefix and cannot be remapped
Cause: The 'xml' prefix is reserved by JCR and cannot be remapped.
Action: Check that your application is not trying to remap the 'xml' prefix.
WCS-35914: Namespace prefix remapping is not permitted
Cause: Persistent namespace remapping is not permitted by this JCR repository.
Action: Use the session for any namespace remapping needs.
WCS-35915: Invalid JCR name or path ({0})
Cause: The specified name or path is not a valid JCR name or path.
Action: Check that the name or path uses valid namespace prefixes and satisfies the JCR grammar rules for Names and Paths.
WCS-35915: Index out of bound while accessing Path
Cause: The specified index for a path element is not valid.
Action: Check your use of the Path object.
WCS-35916: Cannot append an absolute Path
Cause: When appending a path to an existing path, the appended path must be relative.
Action: Make sure that the appended path is always relative.
WCS-35917: Not a valid relative path
Cause: The repository was provided an absolute path when it is expecting a relative path.
Action: Make sure you use a relative path when calling this function.
WCS-35918: Unexpected error while accessing node type
Cause: An unexpected error happened while accessing a node type.
Action: Contact Oracle Support Services.
WCS-35919: No such node type (name = {0})
Cause: The specified node type is unknown to the JCR repository.
Action: Make sure your are using the correct node types for this repository.
WCS-35920: Not a supported query language: {0}
Cause: The specified language is a not a supported query language.
Action: Make sure you use only XPath queries.
WCS-35921: Saved queries are not supported
Cause: This repository does not support saved query.
Action: Make sure your application does not call unsupported JCR functionality.
WCS-35922: Unexpected Expr type
Cause: The specified xpath expression is not supported by this JCR repository.
Action: Check your xpath query.
WCS-35923: XPath expression error: invalid enum value
Cause: An internal data structure uses an invalid value.
Action: Contact Oracle Support Services.
WCS-35924: XPath expression error: invalid expression tree
Cause: The specified xpath expression is not supported by this JCR repository.
Action: Check your xpath query.
WCS-35925: Error while generating XML representation of expression tree
Cause: There was an error while creating an XML representation of this expression tree.
Action: Check the exception's cause.
WCS-35926: Invalid xpath expression
Cause: The specified xpath expression is not supported by this JCR repository.
Action: Check your xpath query.
WCS-35927: Invalid qualified name: {0}
Cause: The specified xpath expression contains an invalid qualified name.
Action: Check your xpath query.
WCS-35928: Unexpected error during XML export
Cause: There was an XML processing error while performing an XML export operation.
Action: Check that you are using Oracle XML parser v2.
WCS-35991: {0} is not a valid expression for use as a search string with jcr:contains()
Cause: The specified full text search expression is not valid for use with jcr:contains().
Action: Check the valid full text search expressions in the JCR 1.0 specification.
WCS-35992: {0} is not a valid expression for use as a search string with jcr:like()
Cause: The specified regular expression is not valid argument for jcr:like().
Action: Check the valid regular expressions in the JCR 1.0 specification.
WCS-35993: This XPath expression contains constructs that are not supported by this query engine.
Cause: This XPath query is not supported by this repository.
Action: Check your xpath query.
WCS-36002: Item not found
Cause: The item was not found in the repository.
Action: Correct the item reference, and retry.
WCS-36003: Item not found, ancestor depth is not valid.
Cause: The depth specified for the getAncestor method was not valid. Note that if depth "n" is specified ("n" being the depth of the item itself), then an ItemNotFoundException is thrown.
Action: Respecify the depth of the item's ancestor, and retry.
WCS-36004: The folder or file is not synchronized with the file system.
Cause: Stale file-system information prevented synchronization with the folder or file.
Action: Invoke refresh() or save() to synchronize file-system information with the folder or file.
WCS-36005: Folders do not have primary items.
Cause: The method getPrimaryItem() was improperly invoked on a folder.
Action: Avoid invoking the getPrimaryItem() method on a folder.
WCS-36006: Operation has not yet been implemented
Cause: The method that was invoked has not been implemented.
Action: Do not use this method, or contact Oracle Support Services.
WCS-36007: Path not found
Cause: The method was invoked with an invalid path.
Action: Specify a valid path, and retry.
WCS-36008: Unsupported repository operation
Cause: A method has been invoked that is not supported.
Action: Do not invoke this method, or contact Oracle Support Services.
Cause: A null or invalid file-system adapter repository reference was entered.
Action: Invoke the FSRepository constructor with a valid reference.
WCS-36014: {0} is not a valid file-system mount point.
Cause: An invalid directory was specified for the file-system mount point.
Action: Invoke the FSRepository constructor with a valid root directory.
WCS-36015: {0} is not a known workspace in this repository.
Cause: Login was attempted using an unsupported value (workspace).
Action: Invoke the login() method with a null workspace.
WCS-36016: The file-system adapter does not accept login credentials.
Cause: Login was attempted using an unsupported value (credentials).
Action: Retry invoking the login() method with null credentials.
WCS-36017: Impersonation is not allowed.
Cause: The method impersonate() was invoked on the file-system adapter. Impersonation is not allowed.
Action: Avoid invoking the impersonate() method on the file-system adapter.
WCS-36018: Unexpected error
Cause: The system encountered an unexpected error.
Action: Contact Oracle Support Services.
WCS-36021: IO error
Cause: There was an error reading a file.
Action: Contact the system administrator.
WCS-36022: This property is not a REFERENCE.
Cause: An attempt was made to invoke the getNode() method on a property that does not support the method.
Action: Avoid invoking the getNode() method on the specified property.
WCS-36023: Illegal single value access: property is multi-value
Cause: An attempt to access a single-value property was a made on a multi-value property.
Action: Determine whether a property is single- or multi-value, and retry.
WCS-36024: Illegal multi-value access: property is single-value
Cause: An attempt to access a multi-value property was made on a single-value property.
Action: Determine whether a property is single- or multi-value, and retry.
WCS-36025: XPath error
Cause: An attempt to process an XPath resulted in an error.
Action: Contact Oracle Support Services.
WCS-36026: Invalid XPath query
Cause: An invalid XPath query was entered.
Action: Correct the XPath query, and retry.
WCS-36035: Item exists
Cause: An attempt was made to overwrite an existing Item.
Action: Specify the overwrite option, or remove the Item before attempting this operation.
WCS-36037: Access denied
Cause: An attempt was made to perform an action that is not allowed on the path that was specified.
Action: Contact the system administrator.
WCS-36038: The session has pending changes.
Cause: Pending changes in the session prevented the operation from proceeding.
Action: Invoke the save() or refresh() method, and retry.
WCS-36301: Unexpected error
Cause: The system encountered an unexpected error.
Action: Contact Oracle Support Services.
WCS-36302: Connection or statement could not be closed.
Cause: The system encountered an unexpected error while trying to close a database connection or a statement.
Action: Verify that the Portal instance is up and running.
WCS-36303: Unexpected error
Cause: The system encountered an unexpected error while running the Portal Adapter Search.
Action: Contact Oracle Support Services.
WCS-36304: SQL error while performing a search
Cause: An error occurred while performing a search in the Portal Repository.
Action: Check that search criteria is valid, and verify that the Portal instance is up and running.
WCS-36305: Could not connect to the Portal Repository
Cause: An error occurred while connecting to the Portal Repository when attempting to perform the search.
Action: Verify that the Portal instance is up and running.
WCS-36306: Error while executing a search
Cause: An unexpected error occurred while executing a search.
Action: Check that search criteria is valid, and verify that the Portal instance is up and running.
WCS-36307: Invalid nodetype : {0}
Cause: An invalid nodetype was specified for the search.
Action: Ensure the search query is valid.
WCS-36308: nodetype error
Cause: An unexpected error occurred while determining the node type for the search.
Action: Ensure the search query is valid.
WCS-36309: Error determining the search criteria
Cause: An error occurred while determining the criteria for the search.
Action: Ensure the search query is valid.
WCS-36310: Invalid search specified
Cause: The specified XPath for the search was invalid.
Action: Ensure the search query is valid.
WCS-36311: An error occurred while building the search.
Cause: An error occurred while building the search.
Action: Ensure the search query is valid.
WCS-36320: Property cannot be created for {0} because the data type, {1}, is invalid. Path: {2}; node id: {3}; node site id: {4}.
Cause: The data type for the requested property was invalid.
Action: Specify a valid data type for the property, and retry.
WCS-36321: Primary item name for node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.
Cause: The node type was invalid.
Action: Check if the requested node type exists in the repository.
WCS-36322: Property definitions of node type, {0}, cannot be returned.
Cause: An error occurred while creating the property definitions.
Action: Check that the requested node type exists in the repository.
WCS-36323: Super types of node type, {0}, cannot be returned.
Cause: An error occurred while creating the super types.
Action: Check that the node type is valid, and retry.
WCS-36324: Primary item name for node type, {0}, cannot be returned.
Cause: Node type was not found.
Action: Check that the node type is valid, and retry.
WCS-36325: Node definitions for node type, {0}, cannot be returned.
Cause: Node definition could not be created.
Action: Check that the node type is valid, and retry.
WCS-36326: Super types of node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.
Cause: The node type was not found.
Action: Verify that the requested node type exists in the repository.
WCS-36327: Invalid credentials
Cause: Session could not be created for the user.
Action: Verify that the credentials passed are valid.
WCS-36328: Could not connect to the database
Cause: A connection to the database could not be established.
Action: Verify that the Portal instance is up and running.
WCS-36329: Access denied
Cause: You do not have the sufficient privilege to perform this operation.
Action: Contact the WebCenter administrator to check your privileges.
WCS-36330: The requested node type, {0}, does not exist.
Cause: An error occurred while trying to find the requested node type.
Action: Ensure the node type exists in the repository.
WCS-36331: Property definitions of node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.
Cause: An error occurred while creating the property definitions.
Action: Check that the node type is valid, and verify that the Portal instance is up and running.
WCS-36332: Property, {0}, cannot be set for node type, {1}. NodeTypeID: {2}; NodeTypeSiteID: {3}.
Cause: The property value was invalid.
Action: Provide a valid property value.
WCS-36333: Oracle data source, {0}, could not be looked up.
Cause: The data source was not available.
Action: Verify that the data source is created correctly and is available.
WCS-36334: Oracle data source could not be created.
Cause: Oracle data source could not be created.
Action: Check the database URL, and verify that the username and password is valid for the data source.
WCS-36335: The root nodes of the Portal repository could not be obtained.
Cause: An error occurred while obtaining root nodes.
Action: Verify that the Portal instance is up and running.
WCS-36336: Statement/Connection objects could not be closed.
Cause: An error occurred while closing the statement or connection objects.
Action: Verify that the Portal instance is up and running.
WCS-36337: The child nodes of folder, {2}, cannot be obtained. Parent folder id: {0}; folder site id: {1}.
Cause: SQLException occurred while trying to obtain the child nodes.
Action: Verify that the folder id, folder page group id, and path are valid, and verify that the Portal instance is up and running.
WCS-36338: Property, {0}, is a single-valued property.
Cause: The property was a single-valued property.
Action: Verify that the value for the property is a single value.
WCS-36339: Unable to check if the session is live
Cause: An error occurred when checking whether the session is live.
Action: Verify that the Portal instance is up and running.
WCS-36340: The Portal session could not be logged out.
Cause: An error occurred while logging out of the Portal session.
Action: Verify that the Portal instance is up and running.
WCS-36341: Cannot determine UUID for node, {0}
Cause: An error occurred while determining UUID of context node.
Action: Verify that the path is correct and that the node can be referenced.
WCS-36342: Cannot get the node, {0}
Cause: An error occurred while fetching the requested node.
Action: Verify that the path is valid.
WCS-36343: Cannot get the node for the given UUID, {0}
Cause: An error occurred while fetching the requested node.
Action: Verify that the UUID is valid.
WCS-36344: Cannot determine if item exists at given path, {0}
Cause: An error occurred while determining if the requested item exists.
Action: Verify that the path is valid.
WCS-36345: Cannot get base type for node type id: {0}, and node type site id: {1}
Cause: An error occurred while fetching the base type.
Action: Verify that the requested type exists in the Portal repository.
WCS-36346: Property definitions of node type cannot be returned. NodeTypeID: {0}; NodeTypeSiteID: {1}.
Cause: An error occurred while creating the property definitions.
Action: Verify that the node type exists in the Portal repository.
WCS-36347: Property, {0}, cannot be set for node type. NodeTypeID: {1}; NodeTypeSiteID: {2}.
Cause: The property value was invalid.
Action: Provide a property value that is valid.
WCS-36348: Cannot retrieve all the node types from the Portal repository
Cause: An error occurred while retrieving the Portal node types.
Action: Verify that the Portal instance is up and running.
WCS-36349: Cannot get the properties for node with id: {0}, site id: {1}
Cause: An error occurred while obtaining the properties of the node from the repository.
Action: Verify that the node and node type is valid and the Portal instance is up and running.
WCS-36350: Cannot get the references for the requested node. Node id: {0}; node site id: {1}.
Cause: An error occurred while obtaining the references for the requested node.
Action: Verify that the node is valid and the Portal instance is up and running.
WCS-36351: Cannot get binary property value for property, {0}, that belongs to node, {1}
Cause: An error occurred while fetching the binary property of node.
Action: Verify that the path is correct.
WCS-36352: Cannot get Portal property name for property id: {0}
Cause: An error occurred while obtaining the Portal property name.
Action: Verify that the property requested is valid.
WCS-36353: Cannot determine if the Portal session is valid
Cause: A SQL Error occurred when checking whether the Portal session was valid.
Action: Verify that the Portal instance is up and running.
WCS-36354: The Portal session could not be logged out
Cause: A SQL Error occurred when attempting to log out.
Action: Verify that the Portal instance is up and running.
WCS-36355: Cannot determine the length of the given input stream
Cause: An error occurred while determining the length of the input stream.
Action: Verify that the input stream is valid.
WCS-36356: Property, {0}, is a single-valued property.
Cause: The property used was a single-valued property.
Action: This API cannot be invoked on a single-valued property.
WCS-36357: This node, {0}, cannot be referenced and hence, does not have a UUID property.
Cause: The context node did not have a UUID property.
Action: Make this request on a node that can be referenced.
WCS-36358: Property, {0}, is a multivalued property.
Cause: The property used was a multivalued property.
Action: This API cannot be invoked on a multivalued property.
WCS-36359: This operation is not supported by the Portal repository.
Cause: Error performing this action as the operation is not supported by the underlying Portal repository.
Action: Check that the operation being attempted is a valid operation for the repository.
WCS-36360: The Portal repository has only one workspace, so this request is invalid.
Cause: The underlying Portal repository has only one workspace.
Action: The request is invalid because the repository is a single-workspace repository. Retry with a valid request.
WCS-36361: Cannot convert length of property, {0}, to long
Cause: An error occurred while converting the length to the long data type.
Action: Verify that the property value is valid.
WCS-36362: Cannot parse the date value for property, {0}
Cause: An error occurred while parsing the date value.
Action: Verify the value of the property is valid.
WCS-36363: The requested property was not found. Path of context node: {0}; Relative Path: {1}.
Cause: The property was not found.
Action: Verify that the requested property is valid and that the path is valid.
WCS-36364: The requested item, {0}, was not found.
Cause: An error occurred while fetching the requested item.
Action: Verify that the item exists in the Portal repository.
WCS-36365: The property, {0}, cannot be converted to a reference.
Cause: The property could not be converted to a reference or was a multivalued property.
Action: Verify that the property can be converted to a reference.
WCS-36366: {0} is a folder and consequently does not have a primary item.
Cause: A folder was specified, and a folder is not a primary item.
Action: Retry the request without specifying a folder.
WCS-36367: The requested node was not found. Path of context node: {0}; Relative Path: {1}.
Cause: The requested node was not found.
Action: Verify that the requested node is valid and that the path is valid.
WCS-36368: The given path, {0}, is invalid.
Cause: The path was invalid.
Action: Pass a valid path.
WCS-36416: Error determining if child node, {0}, could be added
Cause: An error occurred while determining if child node could be added.
Action: Verify the node is valid.
WCS-36417: Error determining if child node, {0}, based on type, {1}, could be added
Cause: An error occurred while determining if a child node based on the given type could be added.
Action: Verify that the node and type are valid.
WCS-36418: Error removing the child item, {0}, for node type, {1}
Cause: An error occurred while removing the child item.
Action: Verify item and node type are valid.
WCS-36419: Error removing the property, {0}, for node type, {1}
Cause: An error occurred while removing the property.
Action: Verify that the node type and property are valid.
WCS-36421: Connection could not be closed
Cause: The system encountered an unexpected error while trying to close a database connection.
Action: Verify that the Portal instance is up and running.
WCS-36422: The node types array object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node types object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36423: The "all node types" node type iterator could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node type iterator in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36424: The Portal node types linked list object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the Portal node types linked list object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36425: The cache region, {0}, has already been defined.
Cause: The cache region has already been defined.
Action: No action is required.
WCS-36428: Generic cache exception when trying to retrieve object from cache
Cause: A cache exception was thrown when trying to retrieve the object from the cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36429: Object cannot be stored in cache because the cache is full.
Cause: The object could not be stored in cache because the cache was full.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36430: The root node does not have a parent node.
Cause: The parent node was requested for a root node.
Action: Request the parent node of any node except the rootnode, which, by definition, does not have a parent.
WCS-36431: The node type iterator object could not be removed from cache.
Cause: The node type iterator object could not be removed from the cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36432: The node type name could not be returned from the QName.
Cause: The namespace could not be resolved.
Action: Verify that the specified node type name is valid.
WCS-36433: The property name could not be returned from the QName.
Cause: The namespace could not be resolved.
Action: Contact Oracle Support Services.
WCS-36434: The property definition name could not be returned from the QName.
Cause: The namespace could not be resolved.
Action: Verify that the property type is valid.
WCS-36435: The item at the requested depth, {0}, was not found.
Cause: An error occurred while attempting to retrieve the requested item.
Action: Verify that the expressed depth of the item is valid.
WCS-36436: The root node does not have a parent.
Cause: The parent node could not be requested on the root node.
Action: Verify that the context node is not the root node.
WCS-36437: The Portal session could not be restored.
Cause: SQL Error when attempting to restore the session for the user.
Action: Verify that the user has been authenticated.
WCS-36438: The declared property definition array object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the declared property definition array object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36440: The property definition array object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the property definition array object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36441: The property iterator object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the property iterator object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36442: The property object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the property object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36443: The node iterator object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node iterator object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36444: The node object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36446: The node type object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node type object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36447: The "primary node types" node type iterator could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node type iterator in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36448: The "mixin node types" node type iterator could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node type iterator in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36449: The "super types" node type array could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the node type array in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36450: The child node definitions of the node type could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the child node definitions of the node type in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36451: The property definitions of the node type could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the property definitions of the node type in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36452: The boolean object could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the boolean object in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36453: The requested child node definition of the node type could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the child node definition of the node type in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36454: The requested property definition of the node type could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the property definition of the node type in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36456: The repository property objects could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the repository property objects in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36457: The repository property definition objects could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the repository property definition objects in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36458: One of the cache regions could not be destroyed.
Cause: The system encountered an unexpected exception when trying to destroy one of the cache regions.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36459: The cache could not be initialized.
Cause: The system encountered an unexpected exception when trying to initialize the cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36460: The cache configuration file could not be read.
Cause: The system encountered an IO exception when trying to read the cache configuration file.
Action: Verify that the configuration file exists.
WCS-36461: The repository node type objects could not be stored in cache.
Cause: The system encountered an unexpected exception when trying to store the repository node type objects in cache.
Action: Contact the WebCenter administrator to check the status of the cache.
WCS-36462: Cannot get the super types for node type: {0}
Cause: An error occurred while fetching the super types of the given node type.
Action: Verify that the requested node type exists in the Portal repository and that it is a custom type.
WCS-36463: The region, {0}, could not be found.
Cause: The requested region has not been defined in Java Object Cache (JOC).
Action: Verify that the region name is valid and is expected to exist in this hierarchy.
WCS-36464: Error occurred while running an Oracle Text search
Cause: An error occurred with Oracle Text while running a search.
Action: Check with the Administrator of the Portal you are trying to search that Oracle Text is valid. Additional information as to the cause of the error may be in the portal diagnostics log.
WCS-36465: A root search cannot be performed because the base languages of the page groups are different.
Cause: The base language of the page groups to be search are not the same; therefore, a search cannot be performed.
Action: Perform searches that search only a single page group.
