40 RCU-06000 to RCU-07005

RCU-06000: Unable to connect to the database because some of the required database connection details are not provided.

Cause: Could not connect to the database. Some of the required database connection details were not provided or were invalid.

Action: Enter valid values in all required fields.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06001: Port number validation failed.

Cause: An invalid port number {0} was specified. A valid port number ranges from 0 to 65535.

Action: Enter a valid port number.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06002: Prerequisite validation failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06003: No metadata repository schema can be dropped.

Cause: RCU could not find the Schema Version Registry in the database.

Action: Contact the system administrator.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06004: Empty database user password.

Cause: Password for the SYS database user not specified.

Action: Enter the password for the SYS user.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06011: Prefix validation failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06012: Unable to find any prefix.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06013: Prefix validation failed.

Cause: Specified prefix could not be found. Existing prefixes are: {0}

Action: Specify a valid prefix from the existing prefix list.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06014: invalid component

Cause: Specified component did not exist.

Action: Provide a component that exists.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06015: Component validation failed.

Cause: No component was selected or specified.

Action: Select or specify at least one component.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06016: Invalid prefix specified.

Cause: The specified prefix already exists.

Action: Specify another prefix.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06017: Valid component is not specified.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06018: Schema owner validation failed.

Cause: Value for schema owner {0} was not provided.

Action: Provide values for all schema owners.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06019: Invalid format was provided for schema owner {0}.

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 "_".

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06020: Invalid schema owner {0}.

Cause: Schema owner {0} was duplicated. Schema owners must be unique.

Action: Provide unique schema owners.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06021: Existing components cannot be specified.

Cause: The specified component ({0}) was non-prefixable, and it already exists.

Action: Deselect the non-prefixable component as it already exists.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06022: RCU cannot be executed in resume mode.

Cause: No components to resume execution.

Action: Run RCU without resume option.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06030: Tablespace {0} validation for component {1} failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06051: RCUCommandLine Error - command line options validation failed.

Cause: Invalid option specified.

Action: Provide valid command line options. Remove the invalid option:

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06052: RCUCommandLine Error - Error while validating command line arguments.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06053: RCUCommandLine Error - command line option validation failed.

Cause: More than one mutually exclusive option passed.

Action: Provide valid command line options. Provide only one valid option from this list:

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06054: RCUCommandLine Error - Database type validation failed.

Cause: Database type was not provided.

Action: Provide the database type.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06055: RCUCommandLine Error - command line arguments validation failed.

Cause: Database connect string was not provided.

Action: Provide the database connect string.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06056: RCUCommandLine Error - Database host name validation failed.

Cause: Database host name was not provided.

Action: Provide the database host name.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06057: RCUCommandLine Error - Database port number validation failed.

Cause: Database port number was not provided.

Action: Provide the database port number.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06058: RCUCommandLine Error - Database service name validation failed.

Cause: Database service name was not provided.

Action: Provide the database service name.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06059: RCUCommandLine Error - Database user validation failed.

Cause: Database user was not provided.

Action: Provide the database user.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06060: RCUCommandLine Error - Database password validation failed.

Cause: Database password was not provided.

Action: Provide the database password.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06061: RCUCommandLine Error - Database role validation failed.

Cause: Database role was not provided.

Action: Provide the database role.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06062: RCUCommandLine Error - Schema prefix validation failed.

Cause: Schema prefix was not provided.

Action: Provide the schema prefix.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06063: RCUCommandLine Error - Tablespace name validation failed.

Cause: Tablespace name is not provided. Pass DEFAULT_VALUE to use default tablespace name.

Action: Provide the tablespace name.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06064: RCUCommandLine Error - Schema owner name validation failed.

Cause: Schema owner name is not provided. Pass DEFAULT_VALUE to use default schema owner name.

Action: Provide the schema owner.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06065: RCUCommandLine Error - component name validation failed.

Cause: invalid component name.

Action: Provide a valid component name. Check the specified component:

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06066: RCUCommandLine Error - Error occurred while validating Checkpoint object.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06067: RCUCommandLine Error - checkpoint validation failed.

Cause: No pending components found in checkpoint. Cannot proceed in resume mode.

Action: Invoke RCU without resume option.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06068: Checkpoint object cannot be created.

Cause: Failed to write checkpoint object.

Action: Refer to the RCU log for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06080: Global prerequisite check failed for the specified database.

Cause: Global prerequisite check failed. Check requirement for the specified database.

Action: Modify the database configuration to meet the global prerequisite requirements.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06081: Internal Error - unable to run prereq query in the specified database.

Cause: Unable to obtain properties of the specified database.

Action: Make sure that the database is in a proper state.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06082: Tablespace prerequisite check failed for the selected component.

Cause: Tablespace prerequisite check failed. Check tablespace requirement for each selected component.

Action: Modify the properties of the tablespace or change the prerequisite value.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06083:

Cause: Prerequisite check failed for selected component.

Action: Refer to the RCU logs for additional details. Make sure that the prerequisite requirements are met.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06084: {0} failed.

Cause: invalid format for Java prerequisite: {0}

Action: Make sure that the java prerequisite is in a valid format.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06085: Java prerequisite is not met.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06090: Connection step validation failed.

Cause: Skipping main operation: failed to connect to database because database details were missing or invalid.

Action: Provide correct database details and try again.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06091: Component name/schema prefix validation failed.

Cause: Invalid component name or schema prefix specified.

Action: Provide valid component name and prefix and try again.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06092: Components are not selected properly.

Cause: Component Selection validation failed. Refer to log at {0} for details.

Action: Select one or more components to continue.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06093: Skipping main operation because of validation error.

Cause: Failed to validate schema tablespace.

Action: Check the properties of the database and the tablespaces specified.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06100: Prerequisite check failed.

Cause: Exception while executing prerequisite {0}.

Action: Refer to the logs for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06101: The database prerequisite check failed for {0}

Cause: Prerequisite failed for {0}. Current Value is {2}. It should {3} {1}

Action: Modify database configuration to meet the prerequisite requirement.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06102: The database prerequisite check failed for {0}.

Cause: The prerequisite {0} returned an empty result.

Action: Modify the database configuration to meet the prerequisite requirements.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06103: The database option prerequisite check failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06104: The database object prerequisite check failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06105: The database component prerequisite check failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06106: The database version prerequisite failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06107: The database initialization parameter prerequisite check failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06108: The database tablespace free space prerequisite check failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06120: Component dependencies check failed.

Cause: Component dependencies not met for components with following ids: {0}.

Action: Select the dependent components and try again.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06121: Component dependencies check failed.

Cause: Required dependent components were not selected.

Action: Select the dependent components and try again.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06130: Action failed

Cause: Action failed - {0}.

Action: Check the actions for the component or contact the system administrator.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06131: Error while connecting to the database.

Cause: An error occurred while connecting to the database.

Action: Provide correct database details and try again, or contact the system administrator.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06132: The database type of the specified database is not supported - {0}

Cause: The database type of the specified database was not supported.

Action: Use a database type that is supported.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06133: Error while executing host command action.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06134: Error while executing JDBC action.

Cause: An error occurred while trying to execute JDBC action.

Action: Check the jdbc action for the component or contact the system administrator.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06135: Error while executing Java action.

Cause: An error occurred while trying to execute Java action.

Action: Check the java action for the component or contact the system administrator.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06136: Error while executing SQLPlus action.

Cause: An error occurred while trying to execute SQLPlus action.

Action: Check the sqlplus action for the component or contact the system administrator.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06138: The operation has been halted.

Cause: The operation was halted.

Action: Click continue or restart the operation.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06139: Invalid consolidated schema name {0}.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06140: Invalid schemas to be consolidated.

Cause: {0} was not a valid schema in the given database.

Action: Provide valid schema name for consolidation.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06141: Schema validation failed.

Cause: {0} cannot be consolidated.

Action: Refer logs for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06142: Provided schema cannot be consolidated.

Cause: Validation of consolidate schema failed.

Action: Check the logs for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06143: Provided schema name is not a valid consolidated schema.

Cause: Provided schema exists in database, but the schema was not valid for given consolidate operation.

Action: Make sure schema is of type "CONSOLIDATED".

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06144: Same component type schemas are provided for consolidation.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06146: Invalid consolidated schema name.

Cause: {0} was not a valid schema in the provided database.

Action: Make sure the scripts generated during consolidateGrant are executed.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06147: Invalid command line option specified.

Cause: Consolidate operations are supported only in silent mode.

Action: Invoke the command with "-silent" option.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06148: Consolidated schema validation failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06149: Consolidate schema validation failed.

Cause: Failed to find consolidated schema definition for {0}. Cannot execute reconsolidate on this schema.

Action: Refer to RCU logs for any errors.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06150: Consolidate schema validation failed.

Cause: Specified schema {0} already exists in the database.

Action: Drop the existing schema or generate the script using different schema name.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06151: Consolidate schema validation failed.

Cause: Specified schema {0} does not exist in the database. Could not execute "reconsolidate" option.

Action: Use "consolidate" option to create the consolidated schema.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06152: Consolidate schema name validation failed.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06153: Edition value of {0} is empty.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06154: Specified edition/schema name is invalid.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06155: Invalid database type or schemas to be consolidated.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06156: Validation of edition failed.

Cause: Edition was not specified or was empty value.

Action: Specify the value of edition for EBR database type.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06157: Internal error occurred.

Cause: Execution of sql query, {0} failed.

Action: Refer to the RCU logs for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06158: Unable to verify components of the schemas to be consolidated.

Cause: Error in checking whether the component {0} is consolidatable.

Action: Refer to the RCU logs for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06159: Invalid command line arguments.

Cause: Validation of the command line parameters for listSchemas operation failed.

Action: Refer to the RCU logs for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06160: Invalid database type for "listSchemas" operation.

Cause: "listSchemas" operation is supported only on ORACLE and EBR

Action: Provide valid database type.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06161: Consolidated schema cannot be dropped.

Cause: Validation of drop consolidated schema failed. Specified consolidated schema was invalid.

Action: Check the logs for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06162: Invalid consolidated schema name.

Cause: Consolidated schema name was not provided.

Action: Provide valid consolidated schema name using "{0}" parameter.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06163: Invalid schema specified for consolidation.

Cause: Specified schema {0} was not a valid schema in the schema version registry info.

Action: Provide valid schema name.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06164: Invalid schema name specified for drop operation.

Cause: {0} is not of type "CONSOLIDATED". "-dropConsolidatedSchema" operation can be used only to drop consolidated schemas.

Action: Specify valid consolidated schema name.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06165: Invalid consolidated schema name.

Cause: Consolidated schema name was not provided.

Action: Provide valid value for {0}.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06166: Invalid schemas to be consolidated.

Cause: Consolidated schema list was not provided.

Action: Provide valid value for {0}.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06167: Missing command line arguments for consolidate operation.

Cause: Valid value was not specified for consolidated schema name.

Action: Provide the argument {0} for consolidate operation.Refer to RCU help for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06168: Missing command line arguments for consolidate operation.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06169: Unable to write properties to response file.

Cause: An IO error occurred while writing into response file.

Action: Check the log for more details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06170: Unable to generate response file.

Cause: An Internal error happened during response file generation.

Action: Check the log for more details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06171: Initialization of properties from RCU Response template failed.

Cause: Unable to read the RCUResponse.xml template from RCU jar.

Action: Contact the administrator to resolve the issue.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06172: Error in reading properties from RCU Response template.

Cause: A Jaxb error was thrown while parsing the template xml.

Action: Check the log for more details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06173: Unable to generate RCUResponse file.

Cause: An error occurred while generating RCUResponse file.

Action: Check the log for more details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06174: Could not create the response file directory

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}.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06175: Could not create response file.

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}.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06176: {0} is not a valid directory for generating response file.

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}.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06177: Unable to use the specified response file location.

Cause: {0} file already exists under the given directory {1}.

Action: Specify different directory for response file.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06178: Unable to use the specified wallet file location.

Cause: {0} wallet file already exists under the given directory {1}.

Action: Specify different directory for wallet file.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06179: An internal error occurred while initializing.

Cause: Initialization of response file reader failed.

Action: Check the log for more details and contact the administrator to resolve the issue

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06180: Unsupported RCU Operation

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06181: Unsupported RCU Operation

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06182: No value specified for a mandatory property.

Cause: Value for property "{0}" was not provided in the response file.

Action: Provide valid value in the response file.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06183: Some properties in the response file are missing values.

Cause: Some of the mandatory properties in the response file were missing values.

Action: Refer to the log for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06184: An internal error occurred while initializing.

Cause: Error encountered while reading the response file.

Action: Check the logs for more details and contact the administrator to resolve the issue.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06185: Invalid response file.

Cause: Response file was either null or it did not have read permissions.

Action: Provide a valid response file.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06186: Invalid "schemaPrefix" for generating wallet.

Cause: "schemaPrefix" cannot be empty while generating wallet.

Action: Provide a valid "schemaPrefix".

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06187: Invalid "dbUser" for generating wallet

Cause: "dbUser" could not be empty while generating wallet.

Action: Provide a valid "dbUser".

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06188: Invalid "schemaName" for generating wallet

Cause: "schemaName" could not be empty while generating wallet.

Action: Provide a valid "schemaName".

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06189: Unable to create Oracle wallet

Cause: Directory {0} was either not found or was not a directory.

Action: Provide a valid directory path.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06190: Unable to create Oracle Wallet at {0}.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06191: Unable to get wallet data for alias {0} from {1}.

Cause: A file read error occurred while reading data from wallet {1}

Action: Make sure that the wallet file has read permissions.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06192: Specified wallet location is not a valid directory.

Cause: Wallet location specified did not exist.

Action: Provide a valid wallet location.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06193: Wallet alias is not valid.

Cause: Specified value for wallet alias was empty.

Action: Provide a valid wallet alias.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06194: Unable to add entry {0} to wallet at {1}.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06195: Invalid wallet directory location for creating wallet.

Cause: Specified location {0} had wallet file in it.

Action: Provide different directory location for creating wallet.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06196: Unable to create directory {0}.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06197: Invalid arguments specified for the {1} operation.

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.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06198: invalid SSL arguments.

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".

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06199: invalid "serverDN" value.

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".

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06200: Error while validating TDE check on database.

Cause: TDE was not enabled in the database.

Action: Specify "-encryptTablespace false" argument.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06201: invalid password.

Cause: Password was not provided for {0} in the wallet.

Action: Provide a valid password.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06202: RCUCommandLine Error - validation of RCU command line options failed.

Cause: Invalid command line option was specified.

Action: Provide one of the following options:

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06203: Invalid script location is provided.

Cause: Script Location was not provided or was empty string.

Action: Specify a valid location.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06204: Specified script location is invalid.

Cause: The specified directory did not exist.

Action: Specify an existing directory.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06205: Database type validation failed.

Cause: Invalid database type. Valid database types are: {0}

Action: Provide valid database type.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06206: invalid Component {0}.

Cause: Skipping {0} component as config or storage file was missing for the component.

Action: Specify a valid component name.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07000: The referenced variable validation fails.

Cause: The referenced variable "{0}" is not defined.

Action: Provide the required variable value.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07001: invalid database password.

Cause: Database password was not provided.

Action: Specify valid value for database password.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07002: Validation of SSL arguments fails.

Cause: SSL arguments are not provided in proper format.

Action: Refer help for details.

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07003: Command line argument validation fails.

Cause: Invalid command line argument.

Action: Refer help for supported arguments. Remove invalid option

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07004: ServerDN validation fails.

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"

Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07005: Database connectstring validation fails.

Cause: Database connectstring is not provided in expected format.

Action: Refer help for the supported format type.

Level: 1

Type: ERROR

Impact: Repository Configuration