MGTCA-01001 to MGTCA-01233

52 MGTCA-01001 to MGTCA-01233

MGTCA-01001: clusterware stack did not respond: Cause: A wallet operation was requested when the Oracle Clusterware stack was down.; Action: Contact Oracle Support Services.
MGTCA-01002: clusterware stack did not respond to wallet operation: Cause: User attributes could not be read because the Grid Infrastructure Management Repository wallet location was not accessible.; Action: Contact Oracle Support Services.
MGTCA-01003: wallet access denied: Cause: An attempt to access the wallet was denied because the user does not have the required permissions.; Action: Contact Oracle Support Services.
MGTCA-01004: clusterware wallet internal error: Cause: An invalid wallet operation was performed or Oracle Cluster Registry storage for wallet was not present.; Action: Contact Oracle Support Services.
MGTCA-01005: Could not connect to the GIMR. \n{0}: Cause: An attempt to perform a SQL operation against the Oracle Grid Infrastructure Management Repository (GIMR) failed because a connection could not be established to the repository. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
MGTCA-01006: Could not change user credentials for Oracle Grid Infrastructure Management Repository.: Cause: An attempt to change user credentials for the Oracle Grid Infrastructure Management Repository (GIMR) failed. The accompanying messages provide detailed failure information. This was an internal error.; Action: Contact Oracle Support Services.
MGTCA-01007: Grid Infrastructure Management Repository is not running on this node: Cause: During the execution of 'mgmtca', no running instance of the Grid Infrastructure Management Repository was found on the node.; Action: Run 'mgmtca' on the node having Grid Infrastructure Management Repository.
MGTCA-01008: An internal error occurred while querying for the node running Grid Infrastructure Management Repository: Cause: During the execution of 'mgmtca', an internal error occurred while querying for the node running Grid Infrastructure Management Repository.; Action: Contact Oracle Support Services.
MGTCA-01100: This utility is used to configure the Grid Infrastructure Management Repository.\nUsage: mgmtca [verb options]\nFollowing are the supported verbs on the Domain Services Cluster:\n createRepos - creates a repository and credentials for the local cluster or a member cluster.\n removeRepos - removes the repository and credentials for a member cluster.\n queryRepos - lists the member clusters that are currently serviced by the Domain Services Cluster.\n configRepos - configures the repository for the local cluster or a member cluster.\n setpasswd - sets the password for a set of users in the local cluster.\nFollowing are the supported verbs on the member cluster:\n createRepos - creates a schema in the repository for the member cluster.\n configRepos - configures the repository for the member cluster. Type 'mgmtca verb -h' to get help on a specific mgmtca verb.: Cause: None; Action: None
MGTCA-01101: GIMR SQL operation failure: Cause: An attempt to perform a SQL operation against the Oracle Grid Infrastructure Management Repository (GIMR) failed. Additional failure information is provided by the accompanying messages. This was an internal error.; Action: Contact Oracle Support Services.
MGTCA-01102: failure in performing database operation to retrieve the name of the Pluggable Database in the Oracle Grid Infrastructure Management Repository: Cause: An attempt to retrieve the name of the Pluggable Database in Oracle Grid Infrastructure Management Repository failed.; Action: Contact Oracle Support Services
MGTCA-01103: failure in performing database operation to unlock the user of Oracle Grid Infrastructue Management Database: Cause: The user account to be unlocked did not exist.; Action: Contact Oracle Support Services
MGTCA-01104: An internal error occurred during the remote execution of 'mgmtca' on node {0}, which is running the GIMR.: Cause: An attempt to execute 'mgmtca' remotely on the indicated node encountered an internal error. The indicated node was running the Oracle Grid Infrastructure Management Repository (GIMR).; Action: Contact Oracle Support Services.
MGTCA-01105: The GIMR is not running in this cluster.: Cause: An attempt to execute the command 'mgmtca' was rejected because the Oracle Grid Infrastructure Management Repository (GIMR) was not running in this cluster.; Action: Start the GIMR using the command 'srvctl start mgmtdb', then verify that it has started using the command 'srvctl status mgmtdb'. Retry the operation once the GIMR has been started.
MGTCA-01106: An internal error occurred while querying the state of the Grid Infrastructure Management Repository.: Cause: During the execution of 'mgmtca', an internal error occurred while querying the state of the Grid Infrastructure Management Repository.; Action: Contact Oracle Support Services.
MGTCA-01107: The resource for the Grid Infrastructure Management Repository does not exist.: Cause: The execution of 'mgmtca' could not complete because the resource for the Grid Infrastructure Management Repository did not exist.; Action: Contact Oracle Support Services.
MGTCA-01108: failed to determine CRS Home location: Cause: Execution of 'mgmtca' to retrieve the CRS Home location failed. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01109: failed to determine Oracle Base location: Cause: Execution of 'mgmtca' to retrieve the Oracle Base location failed. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01110: An internal error occurred while querying the state of the Grid Infrastructure Management Repository during reconfiguration.: Cause: The execution of 'mgmtca' could not complete because an internal error occurred while querying the state of the Grid Infrastructure Management Repository during reconfiguration.; Action: Contact Oracle Support Services.
MGTCA-01111: An internal error occurred while stopping the existing instance of the Grid Infrastructure Management Repository during reconfiguration.: Cause: The execution of 'mgmtca' could not complete because an internal error occurred while stopping the existing instance of the Grid Infrastructure Management Repository during reconfiguration.; Action: Contact Oracle Support Services.
MGTCA-01112: An internal error occurred while removing the existing instance of the Grid Infrastructure Management Repository during reconfiguration.: Cause: The execution of 'mgmtca' could not complete because an internal error occurred while removing the existing instance of the Grid Infrastructure Management Repository during reconfiguration.; Action: Contact Oracle Support Services.
MGTCA-01113: The reconfigure operation for the Grid Infrastructure Management Repository could not complete because there was already an instance running on the cluster.: Cause: The reconfigure operation for the Grid Infrastructure Management Repository could not complete because there was already an instance running on the cluster.; Action: Contact Oracle Support Services.
MGTCA-01114: An internal error occurred while creating the Grid Infrastructure Management Repository during reconfiguration.: Cause: The execution of 'mgmtca' could not complete because an internal error occurred while creating the Grid Infrastructure Management Repository during reconfiguration.; Action: Contact Oracle Support Services.
MGTCA-01115: An internal error occurred while starting the resource for the Grid Infrastructure Management Repository during reconfiguration.: Cause: The execution of 'mgmtca' could not complete because an internal error occurred while starting the resource for the Grid Infrastructure Management Repository during reconfiguration.; Action: Contact Oracle Support Services.
MGTCA-01116: The syntax of the 'mgmtca' command is incorrect.: Cause: The 'mgmtca' command was rejected because the syntax as entered was incorrect.; Action: Reenter the 'mgmtca' command with the correct syntax. Enter 'mgmtca -h' to display usage.
MGTCA-01117: The user name specififed in the 'mgmtca' command is invalid.: Cause: The 'mgmtca' command was rejected because the user name specified in the command had invalid content.; Action: Provide a valid user name for the 'mgmtca' command.
MGTCA-01118: A credential store operation failed.: Cause: The 'mgmtca' command did not complete because a credential store operation failed.; Action: Contact Oracle Support Services.
MGTCA-01119: Trace file configuration failed.: Cause: The 'mgmtca' command did not complete because trace file configuration failed.; Action: Contact Oracle Support Services.
MGTCA-01120: command not supported on a member cluster: Cause: An attempt to execute the command 'mgmtca' was rejected because it was not supported on a member cluster.; Action: Run the command on the Domain Services Cluster where the Grid Infrastructure Management Repository is hosted. Export the credentials from the Domain Services Cluster and import them on the member cluster.
MGTCA-01121: failed to determine cluster name: Cause: Execution of 'mgmtca' to retrieve cluster name failed. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01122: The credential store operation to retrieve the Grid Infrastructure Management Repository domain failed.: Cause: Execution of 'mgmtca' failed because the credential store operation to retrieve the Grid Infrastructure Management Repository domain failed.; Action: Contact Oracle Support Services.
MGTCA-01123: A credential store operation failed while initializing the connection to the credential store.: Cause: Execution of 'mgmtca' failed because a credential store operation failed while initializing the connection to the credential store.; Action: Contact Oracle Support Services.
MGTCA-01124: A credential store operation failed while terminating the connection to the credential store.: Cause: Execution of 'mgmtca' failed because a credential store operation failed while terminating the connection to the credential store.; Action: Contact Oracle Support Services.
MGTCA-01125: A credential store operation failed while importing the Cluster Manifest File.: Cause: An attempt to execute the command 'mgmtca' failed while importing the Cluster Manifest File because credentials could not be stored.; Action: Contact Oracle Support Services.
MGTCA-01126: A credential store operation failed while exporting the Cluster Manifest File.: Cause: Execution of 'mgmtca' failed because a credential store operation failed while exporting the Cluster Manifest File.; Action: Contact Oracle Support Services.
MGTCA-01127: The credential store operation to retrieve a user domain failed.: Cause: Execution of 'mgmtca' failed because the credential store operation to retrieve the user domain failed.; Action: Contact Oracle Support Services.
MGTCA-01128: The credential store operation to retrieve the credential set for a user failed.: Cause: Execution of 'mgmtca' failed because the credential store operation to retrieve the credential set for a user failed.; Action: Contact Oracle Support Services.
MGTCA-01129: The credential store operation to retrieve the domain representing the member cluster failed.: Cause: Execution of 'mgmtca' failed because the credential store operation to retrieve the domain representing the member cluster failed.; Action: Contact Oracle Support Services.
MGTCA-01130: The credential store operation to retrieve the domain representing the Domain Services Cluster failed.: Cause: Execution of 'mgmtca' failed because the credential store operation to retrieve the domain representing the Domain Services Cluster failed.; Action: Contact Oracle Support Services.
MGTCA-01131: Cluster Manifest File specified in the command did not exist at the specified location.: Cause: Execution of 'mgmtca' failed because the Cluster Manifest File specified in the command did not exist at the specified location.; Action: Re-execute the command with the correct path to the Cluster Manifest File.
MGTCA-01132: failed to retrieve SCAN information for the cluster: Cause: Execution of 'mgmtca' to retrieve the SCAN information failed. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01133: failed to initialize connection to the credential store: Cause: Execution of 'mgmtca' failed because the connection to the credential store could not be initialized.; Action: Contact Oracle Support Services.
MGTCA-01135: failed to determine type of cluster: Cause: Execution of 'mgmtca' to retrieve the type of cluster failed. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01136: failed to create a repository for the member cluster: Cause: An attempt to execute 'mgmtca' to create a repository for a member cluster encountered an internal error.; Action: Contact Oracle Support Services.
MGTCA-01137: failed to remove the repository for the member cluster: Cause: An attempt to execute 'mgmtca' to create a repository for a member cluster encountered an internal error.; Action: Contact Oracle Support Services.
MGTCA-01138: failed to plug in the repository for the member cluster: Cause: An attempt to execute 'mgmtca' to create a repository for a member cluster encountered an internal error.; Action: Contact Oracle Support Services.
MGTCA-01139: failed to unplug the repository for the member cluster: Cause: An attempt to execute 'mgmtca' to create a repository for a member cluster encountered an internal error.; Action: Contact Oracle Support Services.
MGTCA-01140: failed to migrate the Rapid Home Provisioning schema: Cause: Execution of 'mgmtca' to migrate the Rapid Home Provisioning schema failed.; Action: Contact Oracle Support Services.
MGTCA-01141: cannot run command as root: Cause: An attempt to run 'mgmtca' as the OS root user was rejected.; Action: Run the command 'mgmtca' as the Grid Infrastructure user.
MGTCA-01142: When run on the Domain Services Cluster, this command creates a repository and credentials for the local cluster or a member cluster.\nUsage: mgmtca createRepos [-manifest <manifest_file_location> -member <member_cluster_name> -version <member_cluster_version> -guid <member_cluster_guid> -clusterInfoDir <member_cluster_pdb_backup_dir>]\n -manifest <manifest_file_location> - absolute file path of the Cluster Manifest File where the credentials are to be exported.\n -member <member_cluster_name> - name of the member cluster for which the repository is to be created.\n -version <member_cluster_version> - version of the member cluster for which the repository is to be created.\n -guid <member_cluster_guid> - GU ID of the member cluster, if it already pertains to another DSC and corresponding PDB is unplgged from that DSC and will be attached to current DSC on which the command is running. \n -clusterInfoDir <member_cluster_pdb_backup_dir> - This is the directory location of the backup and metadata files of member cluster's unplgged PDB, if and only if the member cluster already pertains to another DSC: Cause: None; Action: None
MGTCA-01143: When run on the Domain Services Cluster, this command removes the repository and credentials for a member cluster.\nUsage: mgmtca removeRepos -member <member_cluster_name>\n -member <member_cluster_name> - name of the member cluster whose repository and credentials are to be removed.\nThis command is not supported on a member cluster.: Cause: None; Action: None
MGTCA-01144: When run on the Domain Services Cluster, this command plugs in a repository for a member cluster.\nUsage: mgmtca plugRepos -manifest <manifest_file_location> -member <member_cluster_name> -pdbBackupFile <backup_file_location> -pdbMetadataFile <metadata_file_location>\n -manifest <manifest_file_location> - absolute file path of the Cluster Manifest File where the credentials are to be exported.\n -member <member_cluster_name> - name of the member cluster whose repository is to be plugged in.\n -pdbBackupFile <backup_file_location> - absolute file path for the backup file for the repository that is to be plugged in.\n -pdbMetadataFile <metadata_file_location> - absolute file path of the metadata file for the repository that is to plugged in.\nThis command is not supported on a member cluster.: Cause: None; Action: None
MGTCA-01145: When run on the Domain Services Cluster, this command unplugs the repository for a member cluster.\nUsage:mgmtca unplugRepos -member <member_cluster_name> -pdbBackupFile <backup_file_location> -pdbMetadataFile <metadata_file_location>\n -member <member_cluster_name> - name of the member cluster whose repository is to be unplugged.\n -pdbBackupFile <backup_file_location> - absolute file path for the backup file for the repository that is to be unplugged.\n -pdbMetadataFile <metadata_file_location> - absolute file path of the metadata file for the repository that is to be unplugged.\nThis command is not supported on a member cluster.: Cause: None; Action: None
MGTCA-01146: When run on the Domain Services Cluster, this command configures the repository for the local cluster or a member cluster.\nUsage: mgmtca configRepos [exportCred -manifest <manifest_file_location> -member <member_cluster_name> | setpasswd -member <member_cluster_name> [-user <user_ID>[,...] | -allusers]]\n exportCred - exports the credentials for all the users to the Cluster Manifest File for the local cluster or a member cluster.\n -manifest <manifest_file_location> - absolute file path of the Cluster Manifest File where the credentials are to be exported.\n -member <member_cluster_name> - name of the member cluster whose credentials is to be exported.\n setpasswd - automatically generates and sets the password for a set of users for the local cluster or a member cluster.\n -member <member_cluster_name> - name of the member cluster whose credentials are to be exported.\n -user userID[,...] - comma-separated list of user IDs (CHMOS, CHA, CALOG, QOS, GRIDHOME) whose password is to automatically generated and set.\n -allusers - automatically generate and set password for all users.\nWhen run on a member cluster, this command configures the repository for the member cluster.\nUsage: mgmtca configRepos importCred -manifest <manifest_file_location>\n importCred - imports credentials for all the users from the Cluster Manifest File for a member cluster.\n -manifest <manifest_file_location> absolute file path of the Cluster Manifest File from where credentials are to be imported.: Cause: None; Action: None
MGTCA-01147: When run on the Domain Services Cluster, this command sets the password for a set of users in the local cluster.\nUsage: mgmtca setpasswd -user <user_IDs>[,...] | -allusers]\n -user <user_ID>[,...] - comma-separated list of user IDs (CHMOS, CHA, CALOG, QOS, GRIDHOME) whose password is to automatically generated and set.\n -allusers - automatically generate and set passwords for all users.\nThis command is not supported on a member cluster.: Cause: None; Action: None
MGTCA-01148: member cluster name specified in the Cluster Manifest File is invalid.: Cause: An attempt to import the Cluster Manifest File for the member cluster failed because the cluster name in the Cluster Manifest File did not match the name of the member cluster on which the mgmtca command was issued.; Action: Run 'mgmtca createRepos -manifest <manifest_file_location> -member <member_cluster_name>' on the Domain Services Cluster with a valid member cluster name.
MGTCA-01149: member cluster '{0}' already exists.: Cause: An attempt to add a member cluster was rejected because the specified member cluster is already a member of this Cluster Domain.; Action: Specify a unique member cluster name that is not already a member of this Domain Services Cluster.
MGTCA-01150: member cluster '{0}' does not exist.: Cause: An attempt to remove the member cluster was rejected because the specified member cluster is not a member of this Domain Services Cluster.; Action: Specify a valid member cluster name that is a member of this Domain Services Cluster.
MGTCA-01151: There are no members for the Domain Services Cluster: Cause: Status Message; Action: None
MGTCA-01152: member cluster '{0}' cannot be removed.: Cause: An attempt to remove the member cluster was rejected because the specified member cluster was the Domain Services Cluster.; Action: Specify a valid member cluster name that is a member of this Cluster Domain.
MGTCA-01153: member cluster '{0}' cannot be removed.: Cause: An attempt to remove the member cluster was rejected because there were active sessions connected to the repository for the specified member cluster."; Action: Shut down and deconfigure the member cluster.
MGTCA-01154: When run on the Domain Services Cluster, this command lists the member clusters that are serviced by the Domain Services Cluster.\nUsage: mgmtca queryRepos [-member <member_cluster_name>]\n -member <member_cluster_name> - name of the member cluster which needs to be queried. If this parameter is not specified the query returns all the members serviced by the Domain Services Cluster.\nThis command is not supported on a member cluster.: Cause: None; Action: None
MGTCA-01155: Unable to retrieve the Domain Services Cluster for member cluster {0}: Cause: An attempt to identify the Domain Services Cluster for the indicated member cluster failed.; Action: Re-export the credentials on the Domain Services Cluster using the command 'mgmtca configRepos exportCred -member <member_cluster_name> -manifest <manifest_file_location>' and import them on the member cluster.
MGTCA-01156: command not supported on a Domain Services Cluster: Cause: Execution of 'mgmtca' failed because the command was not supported on a Domain Services Cluster.; Action: Run the command on a member cluster.
MGTCA-01157: failed to retrieve the member cluster Globally Unique Identifier (GUID) from the Cluster Manifest File: Cause: An attempt to retrieve the member cluster Globally Unique Identifier (GUID) from the Cluster Manifest File failed or an incorrect Cluster Manifest File was supplied.; Action: Recreate the Cluster Manifest File on the Domain Services Cluster, copy the Cluster Manifest File to the member cluster or specify the correct Cluster Manifest File and retry the operation.
MGTCA-01158: failed to generate a Globally Unique Identifier (GUID) for the member cluster: Cause: An attempt to configure the Grid Infrastructure Management Repository (GIMR) for the member cluster using the 'createRepos' command failed because of a failure to generate a Globally Unique Identifier (GUID).; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01159: failed to add the member cluster Globally Unique Identifier (GUID) to the Cluster Manifest File: Cause: An attempt to configure the Grid Infrastructure Management Repository (GIMR) for the member cluster using the 'createRepos' command failed because of a failure to add the Globally Unique Identifier (GUID) to the credentials file.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01160: failed to retrieve the name of the Grid Infrastructure Management Repository Server: Cause: Execution of 'mgmtca' to retrieve the name of the Grid Infrastructure Management Repository Server failed.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01161: failed to validate the provided Cluster Manifest File: Cause: Execution of 'mgmtca' to validate the provided Cluster Manifest File failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01162: failed to add a property to the provided Cluster Manifest File: Cause: Execution of 'mgmtca' to add a property to the provided Cluster Manifest File failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01163: The Globally Unique Identifier (GUID) present in the credential file is {0}.: Cause: None; Action: None
MGTCA-01164: Credential file does not contain a Globally Unique Identifier (GUID).: Cause: None; Action: None
MGTCA-01165: An error occurred during the remote execution of 'mgmtca' on the node running the Grid Infrastructure Management Repository.: Cause: During the execution of 'mgmtca', an error occurred while remotely executing the operation of the node running the Grid Infrastructure Management Repository. Accompanying error messages provide detailed failure information.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported if possible.
MGTCA-01166: An error occurred while querying for the node running Grid Infrastructure Management Repository.: Cause: During the execution of 'mgmtca', an error occurred while querying for the node running Grid Infrastructure Management Repository. Accompanying error messages provide detailed failure information.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported if possible. Make sure that the Grid Infrastructure Management Repository has been configured and running.
MGTCA-01167: The Grid Infrastructure Management Repository is in an invalid state: Cause: The execution of the createRepos operation failed because the repository for the Domain Services Cluster was not present. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01168: failed to create a Repository as an additional {0} MB of space is required in the Disk Group: Cause: The execution of the createRepos operation failed because the Disk Group did not contain the space required to create a repository.; Action: Add disks to the disk group that is used by the Grid Infrastructure
MGTCA-01169: Cluster Manifest File is valid: Cause: Status Message.; Action: None
MGTCA-01170: Cluster Manifest File is invalid: Cause: Execution of 'mgmtca' to validate the provided Cluster Manifest File failed. The structure of the provided Cluster Manifest File is invalid. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages and follow the action recommended there.
MGTCA-01171: Cluster Manifest File is invalid: Cause: Execution of 'mgmtca' to validate the provided Cluster Manifest File failed. The connection endpoints specified in the Cluster Manifest File are invalid. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages and follow the action recommended there.
MGTCA-01172: failed to get CHA instance for the cluster: Cause: Execution of 'mgmtca' failed to get CHA instance. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01173: failed to deploy CHA models for the cluster with error \n{0}: Cause: Execution of 'mgmtca' to deploy CHA models failed. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01174: failed to start CHA resource \n{0}: Cause: An attempt to start the CHA resource failed. This may be a transient error.; Action: Retry 'srvctl start cha' to see whether the CHA resource starts. If it continues to fail, contact Oracle Support Services.
MGTCA-01175: failed to create CHA resource \n{0}: Cause: Execution of 'mgmtca' failed to create CHA resource. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01176: An error occurred while marking the Cluster Manifest File as expired.: Cause: During the execution of 'mgmtca', an error occurred while marking the Cluster Manifest File as expired. Accompanying error messages provide detailed failure information.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01177: An error occurred while checking the expiration status of the Cluster Manifest File.: Cause: During the execution of 'mgmtca', an error occurred while checking the expiration status of the Cluster Manifest File. Accompanying error messages provide detailed failure information.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01178: The cluster name of the Domain Services Cluster is the same as the member cluster specified in the command.: Cause: An attempt to add a member cluster was rejected because the specified member cluster name is the same as that of the Domain Services Cluster.; Action: Specify a unique member cluster name that is not the name of the Domain Services Cluster.
MGTCA-01179: failed to create the cluster repository for the member cluster '{0}' because the Cluster Manifest File '{1}' has already been used: Cause: An attempt to add a member cluster was rejected because the Cluster Manifest File had already been used.; Action: Create a repository for the member cluster using a Cluster Manifest that has not expired.
MGTCA-01180: cannot create a repository for a member cluster on a Standalone cluster: Cause: An attempt to add a member cluster was rejected because the command was issued on a Standalone cluster.; Action: The command 'mgmtca createRepos' is not supported on a Standalone Cluster.
MGTCA-01181: command cannot be executed by current user: Cause: An attempt to run 'mgmtca' was rejected because the current user was not the Grid Infrastructure user.; Action: Run the command 'mgmtca' as the Grid Infrastructure user.
MGTCA-01182: failed to retrieve cluster classification for current cluster: Cause: An attempt to run 'mgmtca' was rejected because of a failure to retrieve the cluster classification.; Action: Examine the accompanying error messages for details and retry after addressing the issues reported.
MGTCA-01183: incorrect arguments passed to the Cluster Manifest File validation API: Cause: An attempt validate the Cluster Manifest File was rejected because an incorrect number of arguments were passed.; Action: Reissue the command passing the location to the Cluster Manifest File and name of the member cluster to be validated.
MGTCA-01184: The credential store operation to retrieve the password from a credset failed.: Cause: Execution of 'mgmtca' failed because the credential store operation to retrieve the password from a credset failed. This is an internal error.; Action: Contact Oracle Support Services.
MGTCA-01185: The execution of the 'mgmtca' command completed successfully.: Cause: None; Action: None
MGTCA-01186: Not used: Cause: None; Action: None
MGTCA-01187: An error occurred while locking the PCMRADMIN account.\n{0}: Cause: An attempt to perform a SQL operation against the Grid Infrastructure Management Repository (GMIR) failed. Additional failure information is provided by the accompanying messages. This may be an internal error.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01188: An error occurred while unlocking the PCMRADMIN account.\n{0}: Cause: An attempt to perform a SQL operation against the Grid Infrastructure Management Repository (GMIR) failed. Additional failure information is provided by the accompanying messages. This may be an internal error.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01189: An error occurred while applying the patch.\n{0}: Cause: An attempt to apply a patch failed. Additional failure information is provided by the accompanying messages. This may be an internal error.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01190: The cluster name specified in the 'mgmtca' command is invalid.: Cause: An attempt to create a Grid Infrastructure Management Repository (GIMR) for a cluster was rejected because the cluster name specified was invalid.; Action: Retry the operation providing a valid cluster name.
MGTCA-01191: The operation to create a repository for the member cluster failed.: Cause: An attempt to create a repository for the member cluster failed because of insufficient disk space in the ASM disk groups configured for the Grid Infrastructure Management Repository (GIMR).; Action: Retry the operation after adding disks to the ASM disk groups configured for the GIMR.
MGTCA-01192: The operation to create a repository for the member cluster failed.: Cause: An attempt to create a repository for the member cluster failed because the query to estimate the size required for creating the repository failed.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01193: The operation to create a repository for the member cluster failed.: Cause: An attempt to create a repository for the member cluster failed because the operation to resize the Grid Infrastructure Management repository failed.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01194: The operation to create a repository for the member cluster failed.: Cause: An attempt to create a repository for the member cluster failed because the operation to restart the Grid Infrastructure Management repository failed.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01195: An error occurred while querying the value of the initialization parameter in the Grid Infrastructure Management Repository.: Cause: An attempt to query the value of the initialization parameter in the Grid Infrastructure Management Repository failed. Additional failure information is provided by the accompanying messages.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01196: An error occurred while setting the value of the initialization parameter in the Grid Infrastructure Management Repository.: Cause: An attempt to set the value of the initialization parameter in the Grid Infrastructure Management Repository failed. Additional failure information is provided by the accompanying messages.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01197: An error occurred while querying the classification of the cluster.: Cause: An attempt to query the classification of the cluster failed. Additional failure information is provided by the accompanying messages.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01198: The cluster version specified to the 'mgmtca' command is invalid.: Cause: An attempt to run the 'mgmtca' command was rejected because the cluster version specified to the command was invalid.; Action: Retry the 'mgmtca' command, providing a valid cluster version.
MGTCA-01199: No record exists of the Domain Services Cluster {0} which should provide services for the member cluster {1}.: Cause: An attempt to run the 'mgmtca' command was rejected because no record existed of the indicated Domain Services Cluster, which should have provided services for the indicated member cluster. This was an internal error.; Action: Contact Oracle Support Services.
MGTCA-01200: The server cluster {0} is not a valid Domain Services cluster.: Cause: An attempt to run the 'mgmtca' command was rejected because the indicated server cluster, which was configured to provide services for the client cluster, was not a valid Domain Services Cluster. This was an internal error.; Action: Contact Oracle Support Services.
MGTCA-01201: The cluster version specified to the 'mgmtca' command '{0}' does not match the one in the Cluster Manifest File '{1}'.: Cause: An attempt to run the 'mgmtca' command was rejected because the specified cluster version did not match the indicated version in the Cluster Manifest File.; Action: Retry the 'mgmtca' command, providing a valid cluster version.
MGTCA-01202: failed to retrieve the member cluster version from the Cluster Manifest File: Cause: An attempt to retrieve the CLIENT_CLUSTER_VERSION property from the Cluster Manifest File failed.; Action: Recreate the Cluster Manifest File on the Domain Services Cluster, copy the Cluster Manifest File to the member cluster, and then retry the operation.
MGTCA-01203: The name supplied to -oldClusterName '{0}' is the same as the current cluster name.: Cause: An attempt to execute 'mgmtca' to update the cluster name property of the Grid Infrastructure Management Repository failed because the indicated name specified as the 'old cluster name' was the same as the current cluster name. Either the cluster rename was not complete or the wrong name was specified.; Action: Verify the cluster name has indeed changed and retry the operation indicating the correct old cluster name.
MGTCA-01204: The name supplied to -oldClusterName '{0}' is not found in the GIMR records.: Cause: An attempt to execute 'mgmtca' to update the cluster name property of the Grid Infrastructure Management Repository (GIMR) failed because the indicated name specified as the 'old cluster name' did not match the current cluster name property in the GIMR.; Action: Verify the old cluster name stored in the GIMR is the cluster name prior to the cluster rename and retry the operation specifying the correct old cluster name.
MGTCA-01205: failed to update the cluster name property for the current cluster in the GIMR: Cause: An attempt to execute 'mgmtca' to update the cluster name property of the Grid Infrastructure Management Repository (GIMR) failed. Additional failure information is provided by the accompanying messages.; Action: Examine the accompanying messages and if the resolution is not clear, contact Oracle Support Services.
MGTCA-01206: failed to access the properties file containing information about the current cluster at '{0}': Cause: An attempt to access a properties file containing the Cluster Name, GUID and Type at the indicated location failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
MGTCA-01207: Process of RMAN backup of the GIMR Database is failed, due to following reason: Cause: An attempt to perform RMAN backup of GIMR database failed.; Action: Contact Oracle support services.
MGTCA-01208: The directory location '{0}' does not exist or is not writable.: Cause: An attempt to execute 'mgmtca' failed because the indicated directory did not exists or was not writable.; Action: Retry the operation, specifying a writable directory.
MGTCA-01209: Failed to drop GIMR from old home.: Cause: An attempt to drop of GIMR database failed.; Action: Contact Oracle support services.
MGTCA-01210: Failed to create GIMR in new home.: Cause: An attempt to creation of GIMR database failed.; Action: Contact Oracle support services.
MGTCA-01211: Required file '{0}' not found at the expected location.: Cause: An attempt to execute 'mgmtca' failed because the indicated required file was not found in the expected location.; Action: Make sure the file is present and is readable in the expected location, and then retry the operation.
MGTCA-01212: GIMR Database is in inconsistent state.: Cause: An attempt to execute upgrade failed because the database was in the inconsistent state.; Action: Contact oracle support services.
MGTCA-01213: Unable to create tablespace due to lack of space. {0}: Cause: An attempt to execute create tablespace failed because the disk space is not sufficient.; Action: Ensure free space is sufficient for creation of the tablespaces, and then retry the operation.
MGTCA-01214: Retrieval of the control file location of the GIMR database in the old home failed.: Cause: An attempt to upgrade GIMR database failed because retrieval of the control file location of the GIMR database in the old home failed .; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
MGTCA-01215: failed to retrieve attribute {0} for the Grid Infrastructure Management Repository resource: Cause: An attempt to execute 'mgmtca' command failed because there was an error while reading an attribute in the resource for the Grid Infrastructure Management Repository.; Action: Contact Oracle Support Services.
MGTCA-01216: unable to write SP file location: Cause: An attempt to write Grid Infrastructure Management Repository (GIMR) Server Parameter (SP) file location failed.; Action: Contact Oracle Support Services.
MGTCA-01217: unable to read SP file location: Cause: An attempt to read Grid Infrastructure Management Repository (GIMR) Server Parameter (SP) file location failed.; Action: Contact Oracle Support Services.
MGTCA-01218: Cluster Version {0} is not compatible with GIMR version {1}.: Cause: The operation could not be performed because the provided version was not supported by the current Grid Infrastructure Mangement Repositiry (GIMR) version.; Action: Ensure that the versions are compatible and retry the operation.
MGTCA-01219: The specified storage type for GIMR creation is not valid.: Cause: An attempt to execute CREATE GIMR command was rejected because the specified storage type was not ASM or shared file system.; Action: Retry with appropriate storage type.
MGTCA-01220: Retrieval of the data file location of the GIMR database failed.: Cause: An attempt to upgrade Grid Infrastructure Management database Repository (GIMR) failed because retrieval of the Oracle Cluster Repository (OCR) location of the Grid Infrastructure Management Repository (GIMR) database failed.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
MGTCA-01221: GIMR storage location {0} does not contain enough free space to configure MGMTDB.: Cause: An attempt to execute UPGRADE Grid Infrastructure Management Repository (GIMR) command was not supported because the storage location did not contain enough free space to configure Grid Infrastructure Management Repository (GIMR).; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
MGTCA-01222: unable to create MGMTLSNR in the GI home: Cause: An attempt to create Grid Infrastructure Management Repository Listener (MGMTLSNR) failed.; Action: Contact Oracle Support Services.
MGTCA-01223: failed to validate existing server cluster PDB: Cause: An attempt to create the server cluster pluggable database failed because the existing pluggable database failed to validate relationship with the server cluster.; Action: Contact Oracle Support Services.
MGTCA-01224: failed to create the repository for the server cluster: Cause: An attempt to execute an Grid Infrastructure Management Repository Configuration Assistant (MGMTCA) command to create a repository for a server cluster encountered an internal error.; Action: Contact Oracle Support Services.
MGTCA-01225: failed to remove the repository for the server cluster: Cause: An attempt to execute an Grid Infrastructure Management Repository Configuration Assistant (MGMTCA) command to remove a repository for a server cluster encountered an internal error.; Action: Contact Oracle Support Services.
MGTCA-01226: deprecated this command in console mode: Cause: An attempt to execute 'mgmtca -em' command to set password for em user failed because it was attempted from console.; Action: Execute 'mgmtca setpasswd -user em'.
MGTCA-01227: Unused PDB in GIMR container.: Cause: An unused PDB exists in GRID Infrastructure Management Repository (GIMR) container database.; Action: Cleanup existing PDB and retry the operation.
MGTCA-01228: GIMR resource does not exist.: Cause: GRID Infrastructure Management Repository (GIMR) resource does not exist.; Action: Contact oracle support services.
MGTCA-01229: failed to enable role separation for user {0} in the CRS Credentials Domain: Cause: The Oracle Cluster Ready Services (CRS) Credential Domain group permissions were not updated.; Action: Contact Oracle Support Services.
MGTCA-01230: dependent resource {0} does not exist.: Cause: GRID Infrastructure Management Repository (GIMR) dependent resource does not exist.; Action: Contact oracle support services.
MGTCA-01231: failed to operate on dependent resource {0} .: Cause: GRID Infrastructure Management Repository (GIMR) dependent resource was failed to operate on.; Action: Contact oracle support services.
MGTCA-01232: failed to laydown software bits in all nodes.: Cause: GRID Infrastructure Management Repository (GIMR) dependent resource was failed to operate on.; Action: Contact oracle support services.
MGTCA-01233: Command not supported in Domain Services Cluster Version {0}: Cause: GRID Infrastructure Management Repository (GIMR) Domain Services Cluster does not support the command in the current version.; Action: Contact oracle support services.