RCU-06000 to RCU-07006

Previous Next JavaScript must be enabled to correctly display this content

27 RCU-06000 to RCU-07006

RCU-06000: Unable to connect to the database.
Category:: Repository Configuration
Cause:: Could not connect to the database. Required database connection field(s) "{0}" is/are empty.
Action:: Enter valid value in all required field(s).

RCU-06001: Port number validation failed.
Category:: Repository Configuration
Cause:: An invalid port number {0} was specified. A valid port number ranges from 1 to 65535.
Action:: Enter a valid port number.

RCU-06002: Prerequisite validation failed.
Category:: Repository Configuration
Cause:: The minimum requirements to load metadata repository were not met for the specified database.
Action:: Modify the database configuration to meet the prerequisite requirements.

RCU-06003: No metadata repository schema can be dropped.
Category:: Repository Configuration
Cause:: RCU could not find the Schema Version Registry in the database.
Action:: Contact the system administrator.

RCU-06004: Empty database user password.
Category:: Repository Configuration
Cause:: Password for the SYS database user not specified.
Action:: Enter the password for the SYS user.

RCU-06005: Unable to execute sql query.
Category:: Repository Configuration
Cause:: Database not in open state.
Action:: Make sure that the database is open.

RCU-06006: Could not identify valid Oracle Home(s).
Category:: Repository Configuration
Cause:: The inventory associated with the Oracle Home {0} does not recognize any Oracle Home(s).
Action:: Contact the system administrator to fix the issue.

RCU-06007: Error in populating database details.
Category:: Repository Configuration
Cause:: Exception "{0}" occurred while querying database.
Action:: Refer to the RCU log for details.

RCU-06011: Prefix validation failed.
Category:: Repository Configuration
Cause:: An invalid prefix was specified. A valid prefix can contain only alpha-numeric characters. It should not start with a number and should not contain any special characters.
Action:: Select a prefix from the existing prefixes or enter a new prefix.

RCU-06012: Unable to find any prefix.
Category:: Repository Configuration
Cause:: There were no existing prefixes in the Schema Version Registry of the specified database.
Action:: Refer to the rcu logs or contact the system administrator.

RCU-06013: Prefix validation failed.
Category:: Repository Configuration
Cause:: Specified prefix could not be found. Existing prefixes are: {0}
Action:: Specify a valid prefix from the existing prefix list.

RCU-06014: invalid component
Category:: Repository Configuration
Cause:: Specified component did not exist.
Action:: Provide a component that exists.

RCU-06015: Component validation failed.
Category:: Repository Configuration
Cause:: No component was selected or specified.
Action:: Select or specify at least one component.

RCU-06016: Invalid prefix specified.
Category:: Repository Configuration
Cause:: The specified prefix already exists.
Action:: Specify another prefix.

RCU-06017: Valid component is not specified.
Category:: Repository Configuration
Cause:: There was no prefix specified and the specified component already exists.
Action:: If the component is non-prefixable, only one instance can exist. To re-create the instance, drop it first and then create it again.

RCU-06018: Schema owner validation failed.
Category:: Repository Configuration
Cause:: Value for schema owner {0} was not provided.
Action:: Provide values for all schema owners.

RCU-06019: Invalid format was provided for schema owner {0}.
Category:: Repository Configuration
Cause:: Prefixable components should have the schema owner in the following format <prefix>_<Any String> where the prefix is {1}.
Action:: Ensure that the schema owners of all prefixable components begin with the prefix, followed by "_".

RCU-06020: Invalid schema owner {0}.
Category:: Repository Configuration
Cause:: Schema owner {0} was duplicated. Schema owners must be unique.
Action:: Provide unique schema owners.

RCU-06021: Existing components cannot be specified.
Category:: Repository Configuration
Cause:: The specified component ({0}) was non-prefixable, and it already exists.
Action:: Deselect the non-prefixable component as it already exists.

RCU-06022: RCU cannot be executed in resume mode.
Category:: Repository Configuration
Cause:: No components to resume execution.
Action:: Run RCU without resume option.

RCU-06030: Tablespace {0} validation for component {1} failed.
Category:: Repository Configuration
Cause:: The specified tablespace {0} for component {1} did not have enough free space to hold the repository. The required free space is {2} MB, but the available space was {3} MB.
Action:: Modify the properties of the tablespace or change the prerequisite value.

RCU-06051: RCUCommandLine Error - command line options validation failed.
Category:: Repository Configuration
Cause:: Invalid option specified.
Action:: Provide valid command line options. Remove the invalid option:

RCU-06052: RCUCommandLine Error - Error while validating command line arguments.
Category:: Repository Configuration
Cause:: Invalid format/order of command line options and values.
Action:: Ensure that the format/order of the options and values in the command line are correct.

RCU-06053: RCUCommandLine Error - command line option validation failed.
Category:: Repository Configuration
Cause:: More than one mutually exclusive option passed.
Action:: Provide valid command line options. Provide only one valid option from this list:

RCU-06054: RCUCommandLine Error - Database type validation failed.
Category:: Repository Configuration
Cause:: Database type was not provided.
Action:: Provide the database type.

RCU-06055: RCUCommandLine Error - command line arguments validation failed.
Category:: Repository Configuration
Cause:: Database connect string was not provided.
Action:: Provide the database connect string.

RCU-06056: RCUCommandLine Error - Database host name validation failed.
Category:: Repository Configuration
Cause:: Database host name was not provided.
Action:: Provide the database host name.

RCU-06057: RCUCommandLine Error - Database port number validation failed.
Category:: Repository Configuration
Cause:: Database port number was not provided.
Action:: Provide the database port number.

RCU-06058: RCUCommandLine Error - Database service name validation failed.
Category:: Repository Configuration
Cause:: Database service name was not provided.
Action:: Provide the database service name.

RCU-06059: RCUCommandLine Error - Database user validation failed.
Category:: Repository Configuration
Cause:: Database user was not provided.
Action:: Provide the database user.

RCU-06060: RCUCommandLine Error - Database password validation failed.
Category:: Repository Configuration
Cause:: Database password was not provided.
Action:: Provide the database password.

RCU-06061: RCUCommandLine Error - Database role validation failed.
Category:: Repository Configuration
Cause:: Database role was not provided.
Action:: Provide the database role.

RCU-06062: RCUCommandLine Error - Schema prefix validation failed.
Category:: Repository Configuration
Cause:: Schema prefix was not provided.
Action:: Provide the schema prefix.

RCU-06063: RCUCommandLine Error - Tablespace name validation failed.
Category:: Repository Configuration
Cause:: Tablespace name is not provided. Pass DEFAULT_VALUE to use default tablespace name.
Action:: Provide the tablespace name.

RCU-06064: RCUCommandLine Error - Schema owner name validation failed.
Category:: Repository Configuration
Cause:: Schema owner name is not provided. Pass DEFAULT_VALUE to use default schema owner name.
Action:: Provide the schema owner.

RCU-06065: RCUCommandLine Error - component name validation failed.
Category:: Repository Configuration
Cause:: Invalid component name(s) were provided : {0}
Action:: Provide valid component name(s). Supported component names can be obtained by running "-listComponents" command.

RCU-06066: RCUCommandLine Error - Error occurred while validating Checkpoint object.
Category:: Repository Configuration
Cause:: Checkpoint object was not found or was not readable. Cannot proceed in resume mode.
Action:: Refer to the RCU log and make sure that checkpoint object exists to continue in resume mode.

RCU-06067: RCUCommandLine Error - checkpoint validation failed.
Category:: Repository Configuration
Cause:: No pending components found in checkpoint. Cannot proceed in resume mode.
Action:: Invoke RCU without resume option.

RCU-06068: Checkpoint object cannot be created.
Category:: Repository Configuration
Cause:: Failed to write checkpoint object.
Action:: Refer to the RCU log for details.

RCU-06080: Global prerequisite check failed for the specified database.
Category:: Repository Configuration
Cause:: Global prerequisite check failed. Check requirement for the specified database.
Action:: Modify the database configuration to meet the global prerequisite requirements.

RCU-06081: Internal Error - unable to run prereq query in the specified database.
Category:: Repository Configuration
Cause:: Unable to obtain properties of the specified database.
Action:: Make sure that the database is in a proper state.

RCU-06082: Tablespace prerequisite check failed for the selected component.
Category:: Repository Configuration
Cause:: Tablespace prerequisite check failed. Check tablespace requirement for each selected component.
Action:: Modify the properties of the tablespace or change the prerequisite value.

RCU-06083
Category:: Repository Configuration
Cause:: Prerequisite check failed for selected component.
Action:: Refer to the RCU logs for additional details. Make sure that the prerequisite requirements are met.

RCU-06084: {0} failed.
Category:: Repository Configuration
Cause:: invalid format for Java prerequisite: {0}
Action:: Make sure that the java prerequisite is in a valid format.

RCU-06085: Java prerequisite is not met.
Category:: Repository Configuration
Cause:: Error occurred while executing Java prerequisite: {0}
Action:: Make sure that the java prerequisite is in a valid format and all required classes and jar files are present.

RCU-06086: Global prerequisite check failed.
Category:: Repository Configuration
Cause:: Schema metadata initialization failed.
Action:: Refer to RCU logs for more details.

RCU-06090: Connection step validation failed.
Category:: Repository Configuration
Cause:: Skipping main operation: failed to connect to database because database details were missing or invalid.
Action:: Provide correct database details and try again.

RCU-06091: Component validation failed.
Category:: Repository Configuration
Cause:: One or more component specific validation failed.
Action:: Check log for more details and fix the validation error.

RCU-06092: Components are not selected properly.
Category:: Repository Configuration
Cause:: Component Selection validation failed. Refer to log at {0} for details.
Action:: Select one or more components to continue.

RCU-06093: Skipping main operation because of validation error.
Category:: Repository Configuration
Cause:: Failed to validate schema tablespace.
Action:: Check the properties of the database and the tablespaces specified.

RCU-06100: Prerequisite check failed.
Category:: Repository Configuration
Cause:: Exception while executing prerequisite {0}.
Action:: Refer to the logs for details.

RCU-06101: The database prerequisite check failed for {0}
Category:: Repository Configuration
Cause:: Prerequisite failed for {0}. Current Value is {2}. It should {3} {1}
Action:: Modify database configuration to meet the prerequisite requirement.

RCU-06102: The database prerequisite check failed for {0}.
Category:: Repository Configuration
Cause:: The prerequisite {0} returned an empty result.
Action:: Modify the database configuration to meet the prerequisite requirements.

RCU-06103: The database option prerequisite check failed.
Category:: Repository Configuration
Cause:: The database option prerequisite check failed for: {0} Required Value = {1}, Current Value = {2}
Action:: Make sure that the database option has the required value.

RCU-06104: The database object prerequisite check failed.
Category:: Repository Configuration
Cause:: The database object prerequisite check fails for: {0} This object does not exist or its status is not valid.
Action:: Make sure that the database object exists and is valid.

RCU-06105: The database component prerequisite check failed.
Category:: Repository Configuration
Cause:: The database component prerequisite check failed for {0}. This component does not exist or its status is not valid.
Action:: Make sure that the database component exists and is valid.

RCU-06106: The database version prerequisite failed.
Category:: Repository Configuration
Cause:: The database version prerequisite failed because the current database version is not supported with RCU. Current Version is {1}. It should be {2} {0}.
Action:: Make sure that the database version being used is supported with RCU.

RCU-06107: The database initialization parameter prerequisite check failed.
Category:: Repository Configuration
Cause:: The database initialization parameter prerequisite check failed for {0}. Current Value is {2}. It should {3} {1}.
Action:: Make sure that the database initialization parameter has the required value.

RCU-06108: The database tablespace free space prerequisite check failed.
Category:: Repository Configuration
Cause:: The database tablespace free space prerequisite check failed for {0}. Current space is {2}. It should be {3} {1}.
Action:: Modify the properties of the tablespace or change the prerequisite value.

RCU-06120: Component dependencies check failed.
Category:: Repository Configuration
Cause:: Component dependencies not met for components with following ids: {0}.
Action:: Select the dependent components and try again.

RCU-06121: Component dependencies check failed.
Category:: Repository Configuration
Cause:: Required dependent components were not selected.
Action:: Select the dependent components and try again.

RCU-06130: Action failed
Category:: Repository Configuration
Cause:: Action failed - {0}.
Action:: Check the actions for the component or contact the system administrator.

RCU-06131: Error while connecting to the database.
Category:: Repository Configuration
Cause:: An error occurred while connecting to the database.
Action:: Provide correct database details and try again, or contact the system administrator.

RCU-06132: The database type of the specified database is not supported - {0}
Category:: Repository Configuration
Cause:: The database type of the specified database was not supported.
Action:: Use a database type that is supported.

RCU-06133: Error while executing host command action.
Category:: Repository Configuration
Cause:: An error occurred while trying to execute host command action.
Action:: Check the host command action for the component or contact the system administrator.

RCU-06134: Error while executing JDBC action.
Category:: Repository Configuration
Cause:: An error occurred while trying to execute JDBC action.
Action:: Check the jdbc action for the component or contact the system administrator.

RCU-06135: Error while executing Java action.
Category:: Repository Configuration
Cause:: An error occurred while trying to execute Java action.
Action:: Check the java action for the component or contact the system administrator.

RCU-06136: Error while executing SQLPlus action.
Category:: Repository Configuration
Cause:: An error occurred while trying to execute SQLPlus action.
Action:: Check the sqlplus action for the component or contact the system administrator.

RCU-06138: The operation has been halted.
Category:: Repository Configuration
Cause:: The operation was halted.
Action:: Click continue or restart the operation.

RCU-06139: Invalid consolidated schema name {0}.
Category:: Repository Configuration
Cause:: Consolidated schema {0} exists in database, but schema version registry table did not have an entry for the schema with expected status. The consolidated schema should be created through RCU.
Action:: Provide valid consolidated schema name.

RCU-06140: Invalid schemas to be consolidated.
Category:: Repository Configuration
Cause:: {0} was not a valid schema in the given database.
Action:: Provide valid schema name for consolidation.

RCU-06141: Schema validation failed.
Category:: Repository Configuration
Cause:: {0} cannot be consolidated.
Action:: Refer logs for details.

RCU-06142: Provided schema cannot be consolidated.
Category:: Repository Configuration
Cause:: Validation of consolidate schema failed.
Action:: Check the logs for details.

RCU-06143: Provided schema name is not a valid consolidated schema.
Category:: Repository Configuration
Cause:: Provided schema exists in database, but the schema was not valid for given consolidate operation.
Action:: Make sure schema is of type "CONSOLIDATED".

RCU-06144: Same component type schemas are provided for consolidation.
Category:: Repository Configuration
Cause:: Both schemas {0} and {1} are of type {2}. Schemas of same type cannot be consolidated.
Action:: Make sure that schemas to be consolidated are not of the same component.

RCU-06146: Invalid consolidated schema name.
Category:: Repository Configuration
Cause:: {0} was not a valid schema in the provided database.
Action:: Make sure the scripts generated during consolidateGrant are executed.

RCU-06147: Invalid command line option specified.
Category:: Repository Configuration
Cause:: Consolidate operations are supported only in silent mode.
Action:: Invoke the command with "-silent" option.

RCU-06148: Consolidated schema validation failed.
Category:: Repository Configuration
Cause:: Consolidation of an existing schema is not allowed. {0} already consolidated to the schemas {1}.
Action:: Execute "dropConsolidatedSchema" to delete the existing schema and recreate it using "consolidate". To recreate the synonyms to the existing schemas use "-reconsolidate" option.

RCU-06149: Consolidate schema validation failed.
Category:: Repository Configuration
Cause:: Failed to find consolidated schema definition for {0}. Cannot execute reconsolidate on this schema.
Action:: Refer to RCU logs for any errors.

RCU-06150: Consolidate schema validation failed.
Category:: Repository Configuration
Cause:: Specified schema {0} already exists in the database.
Action:: Drop the existing schema or generate the script using different schema name.

RCU-06151: Consolidate schema validation failed.
Category:: Repository Configuration
Cause:: Specified schema {0} does not exist in the database. Could not execute "reconsolidate" option.
Action:: Use "consolidate" option to create the consolidated schema.

RCU-06152: Consolidate schema name validation failed.
Category:: Repository Configuration
Cause:: Specified schema name "{0}" length exceeds allowed number of characters. Maximum number of characters allowed in consolidated schema name is 25.
Action:: Specify valid value for consolidated schema name.

RCU-06153: Edition value of {0} is empty.
Category:: Repository Configuration
Cause:: Specified database type is EBR. But the schema to be consolidated "{0}" is not created with this edition, "{1}". Schemas to be consolidated have to be created in the same edition as the value specified for consolidate schema.
Action:: Ensure that the schemas to be consolidated exist in the same edition as that of the consolidated schema.

RCU-06154: Specified edition/schema name is invalid.
Category:: Repository Configuration
Cause:: Schemas to be consolidated have to be created in the same edition as the value specified for consolidate schema. "{0}" schema is created with edition "{1}". But the edition specified for consolidate schema is "{2}"
Action:: Ensure that the schemas to be consolidated exist in the same edition as that of the consolidated schema.

RCU-06155: Invalid database type or schemas to be consolidated.
Category:: Repository Configuration
Cause:: Specified database type is ORACLE. Consolidated schema could not be created using schemas created in EBR database type. "{0}" schema is created with EBR as database type.
Action:: Ensure that the schemas to be consolidated are not created using EBR database type.

RCU-06156: Validation of edition failed.
Category:: Repository Configuration
Cause:: Edition was not specified or was empty value.
Action:: Specify the value of edition for EBR database type.

RCU-06157: Internal error occurred.
Category:: Repository Configuration
Cause:: Execution of sql query, {0} failed.
Action:: Refer to the RCU logs for details.

RCU-06158: Unable to verify components of the schemas to be consolidated.
Category:: Repository Configuration
Cause:: Error in checking whether the component {0} is consolidatable.
Action:: Refer to the RCU logs for details.

RCU-06159: Invalid command line arguments.
Category:: Repository Configuration
Cause:: Validation of the command line parameters for listSchemas operation failed.
Action:: Refer to the RCU logs for details.

RCU-06160: Invalid database type for "listSchemas" operation.
Category:: Repository Configuration
Cause:: "listSchemas" operation is supported only on ORACLE and EBR
Action:: Provide valid database type.

RCU-06161: Consolidated schema cannot be dropped.
Category:: Repository Configuration
Cause:: Validation of drop consolidated schema failed. Specified consolidated schema was invalid.
Action:: Check the logs for details.

RCU-06162: Invalid consolidated schema name.
Category:: Repository Configuration
Cause:: Consolidated schema name was not provided.
Action:: Provide valid consolidated schema name using "{0}" parameter.

RCU-06163: Invalid schema specified for consolidation.
Category:: Repository Configuration
Cause:: Specified schema {0} was not a valid schema in the schema version registry info.
Action:: Provide valid schema name.

RCU-06164: Invalid schema name specified for drop operation.
Category:: Repository Configuration
Cause:: {0} is not of type "CONSOLIDATED". "-dropConsolidatedSchema" operation can be used only to drop consolidated schemas.
Action:: Specify valid consolidated schema name.

RCU-06165: Invalid consolidated schema name.
Category:: Repository Configuration
Cause:: Consolidated schema name was not provided.
Action:: Provide valid value for {0}.

RCU-06166: Invalid schemas to be consolidated.
Category:: Repository Configuration
Cause:: Consolidated schema list was not provided.
Action:: Provide valid value for {0}.

RCU-06167: Missing command line arguments for consolidate operation.
Category:: Repository Configuration
Cause:: Valid value was not specified for consolidated schema name.
Action:: Provide the argument {0} for consolidate operation.Refer to RCU help for details.

RCU-06168: Missing command line arguments for consolidate operation.
Category:: Repository Configuration
Cause:: Valid value was not specified for schemas to be consolidated.
Action:: Provide the argument {0} for consolidate operation.Refer to RCU help for details.

RCU-06169: Unable to write properties to response file.
Category:: Repository Configuration
Cause:: An IO error occurred while writing into response file.
Action:: Check the log for more details.

RCU-06170: Unable to generate response file.
Category:: Repository Configuration
Cause:: An Internal error happened during response file generation.
Action:: Check the log for more details.

RCU-06171: Initialization of properties from RCU Response template failed.
Category:: Repository Configuration
Cause:: Unable to read the RCUResponse.xml template from RCU jar.
Action:: Contact the administrator to resolve the issue.

RCU-06172: Error in reading properties from RCU Response template.
Category:: Repository Configuration
Cause:: A Jaxb error was thrown while parsing the template xml.
Action:: Check the log for more details.

RCU-06173: Unable to generate RCUResponse file.
Category:: Repository Configuration
Cause:: An error occurred while generating RCUResponse file.
Action:: Check the log for more details.

RCU-06174: Could not create the response file directory
Category:: Repository Configuration
Cause:: Unable to create the response file directory {0}. This could be due to permission related issue.
Action:: Check if neccessary permissions are present to create the directory {0}.

RCU-06175: Could not create response file.
Category:: Repository Configuration
Cause:: Unable to create the response file {0}. This could be due to permission related issue.
Action:: Check if neccessary permissions are present to create the response file {0}.

RCU-06176: {0} is not a valid directory for generating response file.
Category:: Repository Configuration
Cause:: {0} could be a non existent directory or it could already contain an existing response file.
Action:: Choose a different location or clean the directory {0}.

RCU-06177: Unable to use the specified response file location.
Category:: Repository Configuration
Cause:: {0} file already exists under the given directory {1}.
Action:: Specify different directory for response file.

RCU-06178: Unable to use the specified wallet file location.
Category:: Repository Configuration
Cause:: {0} wallet file already exists under the given directory {1}.
Action:: Specify different directory for wallet file.

RCU-06179: An internal error occurred while initializing.
Category:: Repository Configuration
Cause:: Initialization of response file reader failed.
Action:: Check the log for more details and contact the administrator to resolve the issue

RCU-06180: Unsupported RCU Operation
Category:: Repository Configuration
Cause:: No value was specified for the property "operation".
Action:: Refer to the RCU guide or command line help for a list of valid RCU operations.

RCU-06181: Unsupported RCU Operation
Category:: Repository Configuration
Cause:: Value provided for the property "operation" was not a valid RCU operation.
Action:: Refer to the RCU guide or command line help for a list of valid RCU operations.

RCU-06182: No value specified for a mandatory property.
Category:: Repository Configuration
Cause:: Value for property "{0}" was not provided in the response file.
Action:: Provide valid value in the response file.

RCU-06183: Some properties in the response file are missing values.
Category:: Repository Configuration
Cause:: Some of the mandatory properties in the response file were missing values.
Action:: Refer to the log for details.

RCU-06184: An internal error occurred while initializing.
Category:: Repository Configuration
Cause:: Error encountered while reading the response file.
Action:: Check the logs for more details and contact the administrator to resolve the issue.

RCU-06185: Invalid response file.
Category:: Repository Configuration
Cause:: Response file was either null or it did not have read permissions.
Action:: Provide a valid response file.

RCU-06186: Invalid "schemaPrefix" for generating wallet.
Category:: Repository Configuration
Cause:: "schemaPrefix" cannot be empty while generating wallet.
Action:: Provide a valid "schemaPrefix".

RCU-06187: Invalid "dbUser" for generating wallet
Category:: Repository Configuration
Cause:: "dbUser" could not be empty while generating wallet.
Action:: Provide a valid "dbUser".

RCU-06188: Invalid "schemaName" for generating wallet
Category:: Repository Configuration
Cause:: "schemaName" could not be empty while generating wallet.
Action:: Provide a valid "schemaName".

RCU-06189: Unable to create Oracle wallet
Category:: Repository Configuration
Cause:: Directory {0} was either not found or was not a directory.
Action:: Provide a valid directory path.

RCU-06190: Unable to create Oracle Wallet at {0}.
Category:: Repository Configuration
Cause:: An internal error occurred while creating Oracle Wallet at {0}.
Action:: Check the log for more details and contact the administrator to resolve the issue.

RCU-06191: Unable to get wallet data for alias {0} from {1}.
Category:: Repository Configuration
Cause:: A file read error occurred while reading data from wallet {1}
Action:: Make sure that the wallet file has read permissions.

RCU-06192: Specified wallet location is not a valid directory.
Category:: Repository Configuration
Cause:: Wallet location specified did not exist.
Action:: Provide a valid wallet location.

RCU-06193: Wallet alias is not valid.
Category:: Repository Configuration
Cause:: Specified value for wallet alias was empty.
Action:: Provide a valid wallet alias.

RCU-06194: Unable to add entry {0} to wallet at {1}.
Category:: Repository Configuration
Cause:: A file read or write error or a security error was thrown while writing into wallet at {1}.
Action:: Check the log for more details and contact the administrator to resolve the issue.

RCU-06195: Invalid wallet directory location for creating wallet.
Category:: Repository Configuration
Cause:: Specified location {0} had wallet file in it.
Action:: Provide different directory location for creating wallet.

RCU-06196: Unable to create directory {0}.
Category:: Repository Configuration
Cause:: A file read or write error occurred while creating directory {0}.
Action:: Check if you have permissions to create the directory {0}. Contact the administrator if problem persists.

RCU-06197: Invalid arguments specified for the {1} operation.
Category:: Repository Configuration
Cause:: Some of the argument(s) specified, "{0}" were not valid for the {1} operation.
Action:: Refer to the RCU guide or command line help for list of valid arguments.

RCU-06198: invalid SSL arguments.
Category:: Repository Configuration
Cause:: SSL authentication requires client and server authentication or encryption details.
Action:: Provide the properties as key-value pair separated by comma using the argument "-sslArgs".

RCU-06199: invalid "serverDN" value.
Category:: Repository Configuration
Cause:: Value for "serverDN" was not provided. "serverDN" is a mandatory parameter for SSL connection.
Action:: Provide a valid value for "serverDN" argument. To disable the serverDN check, provide the property "oracle.net.ssl_server_dn_match=false" in "-sslArgs".

RCU-06200: Error while validating TDE check on database.
Category:: Repository Configuration
Cause:: TDE was not enabled in the database.
Action:: Specify "-encryptTablespace false" argument.

RCU-06202: RCUCommandLine Error - validation of RCU command line options failed.
Category:: Repository Configuration
Cause:: Invalid command line option was specified.
Action:: Provide one of the following options:

RCU-06203: Invalid script location is provided.
Category:: Repository Configuration
Cause:: Script Location was not provided or was empty string.
Action:: Specify a valid location.

RCU-06204: Specified script location is invalid.
Category:: Repository Configuration
Cause:: The specified directory did not exist.
Action:: Specify an existing directory.

RCU-06205: Database type validation failed.
Category:: Repository Configuration
Cause:: Invalid database type. Valid database types are: {0}
Action:: Provide valid database type.

RCU-06206: invalid Component {0}.
Category:: Repository Configuration
Cause:: Skipping {0} component as config or storage file was missing for the component.
Action:: Specify a valid component name.

RCU-06250: Internal Error while parsing component metadata files.
Category:: Repository Configuration
Cause:: Specified schema base definition {0} not found in the Oracle Home. Schema base definition of {1} was wrong.
Action:: Check the logs for more details and contact the administrator to resolve the issue.

RCU-06251: Drop repository validation failed.
Category:: Repository Configuration
Cause:: Component "{0}" could not be dropped independently.
Action:: Specify schema base component "{0}" to drop component "{1}".

RCU-06252: Consolidated component is not found in the Oracle Home.
Category:: Repository Configuration
Cause:: Component "{0}" is consolidated to the schema of the component "{1}". For dropping consolidated schema, all the consolidated components have to be present in the Oracle Home.
Action:: Invoke dropRepository from Oracle Home which contains the component {0}.

RCU-06253: Tablespace configuration of component "{0}" cannot be overridden.
Category:: Repository Configuration
Cause:: Component "{0}" is consolidated to the schema of the component "{1}". "{0}" could not configure custom tablespace.
Action:: Override the tablespace configuration of the component "{0}" which will be used by the component "{1}" also.

RCU-06254: Drop repository validation failed.
Category:: Repository Configuration
Cause:: Component(s) "{0}" could not be dropped independently.
Action:: Select corresponding schema base component(s) "{0}" to drop component(s) "{1}".

RCU-06255: Drop repository validation failed.
Category:: Repository Configuration
Cause:: Component "{0}" for the prefix "{1}" was created as standalone schema. Component could not be dropped in consolidate mode.
Action:: Disable consolidate mode and drop the component.

RCU-06256: Drop repository validation failed.
Category:: Repository Configuration
Cause:: Component "{0}" for the prefix "{1}" was created as consolidate schema. Component could not be dropped in non-consolidate mode.
Action:: Enable consolidate mode and drop the component.

RCU-06257: Create repository validation failed.
Category:: Repository Configuration
Cause:: Consolidated schema component "{0}" for the prefix "{1}" could not be created. The specified prefix was already in use for some of the standalone schemas.
Action:: Specify different prefix.

RCU-06258: Host name or IP address validation failed.
Category:: Repository Configuration
Cause:: An invalid host name or IP address {0} was specified.
Action:: Enter a valid host name or IP address.

RCU-06259: Component validation failed.
Category:: Repository Configuration
Cause:: Incompatible components {0}, {1} were selected/specified.
Action:: Select/specify either component {0} or component {1}.

RCU-06301: invalid password.
Category:: Repository Configuration
Cause:: Password was not provided for {0} in the wallet.
Action:: Provide a valid password.

RCU-06302: Command line arguments validation failed.
Category:: Repository Configuration
Cause:: Value for "{0}" was not provided.
Action:: Provide values for both "-compInfoXMLLocation" and "-storageXMLLocation" or invoke without any of these arguments.

RCU-06303: internal error
Category:: Repository Configuration
Cause:: Value for "{0}" was not provided in rcu properties file.
Action:: Provide valid values for properties "COMPONENT_INFO_LOCATION" and "STORAGE_INFO_LOCATION" in rcu properties file located at {0}

RCU-07000: The referenced variable validation fails.
Category:: Repository Configuration
Cause:: The referenced variable "{0}" is not defined.
Action:: Provide the required variable value.

RCU-07001: invalid database password.
Category:: Repository Configuration
Cause:: Database password was not provided.
Action:: Specify valid value for database password.

RCU-07002: Validation of SSL arguments fails.
Category:: Repository Configuration
Cause:: SSL arguments are not provided in proper format.
Action:: Refer help for details.

RCU-07003: Command line argument validation fails.
Category:: Repository Configuration
Cause:: Invalid command line argument.
Action:: Refer help for supported arguments. Remove invalid option

RCU-07004: ServerDN validation fails.
Category:: Repository Configuration
Cause:: Value for serverDN is not provided. "serverDN" is mandatory parameter for SSL connection.
Action:: To disable the serverDN check, provide the property "oracle.net.ssl_server_dn_match=false" in "-sslArgs"

RCU-07005: Database connectstring validation fails.
Category:: Repository Configuration
Cause:: Database connectstring is not provided in expected format.
Action:: Refer help for the supported format type.

RCU-07006: Validation of log location failed.
Category:: Repository Configuration
Cause:: Could not create the log directory {0}.
Action:: Make sure that the specified log directory and system temporary directory has write permission.