GAUSS-51200 -- GAUSS-51299
GAUSS-51200: “The parameter [%s] in the XML file does not exist.”
SQLSTATE: None
Description: Failed to find the %s parameter in the XML.
Solution: Check the configuration parameters in the XML.
GAUSS-51201: “Node names must be configured.”
SQLSTATE: None
Description: The node name needs to be configured.
Solution: Configure the node name for the node.
GAUSS-51202: “Failed to add the %s instance.”
SQLSTATE: None
Description: Failed to add the instance.
Solution: Ensure that the instance exists and the configuration is correct.
GAUSS-51203: “Failed to obtain the %s information from static configuration files.”
SQLSTATE: None
Description: Failed to obtain the database information from the static configuration file.
Solution: Ensure that the static configuration file exists, that you have the access permission, and that the system is normal.
GAUSS-51204: " Invalid %s instance type: %d."
SQLSTATE: None
Description: The instance type is invalid.
Solution: Check and modify the instance type to be a valid one.
GAUSS-51205: “Failed to refresh the %s instance ID.”
SQLSTATE: None
Description: Failed to update the instance ID.
Solution: Check whether the static configuration file of the current database exists or whether it has been broken, and check whether the user has the access permission. Update the ID of the new database based on this file.
GAUSS-51206: “The MPPRC file path must be an absolute path: %s.”
SQLSTATE: None
Description: The MPPRC path must be an absolute path.
Solution: Change the MPPRC path to an absolute path.
GAUSS-51207: “Failed to obtain backIp from node [%s].”
SQLSTATE: None
Description: Failed to obtain the **backIp **on the node.
Solution: Check and correctly configure the **backIp **on the node.
GAUSS-51208: “Invalid %s number [%d].”
SQLSTATE: None
Description: The quantity is invalid.
Solution: Ensure that the quantity is valid.
GAUSS-51209: “Failed to obtain %s configuration on the host [%s].”
SQLSTATE: None
Description: Failed to obtain the configuration on this node.
Solution: Ensure that the configuration is correct on the node.
GAUSS-51210: “The obtained number does not match the instance number.”
SQLSTATE: None
Description: The number of instances obtained does not match the actual instance number.
Solution: Check and modify the obtained number to match the actual instance number.
GAUSS-51211: “Failed to save a static configuration file.”
SQLSTATE: None
Description: Failed to save the static configuration file.
Solution: Ensure that the static configuration file exists, that you have the access permission, and that the system is normal.
GAUSS-51212: “There is no information about %s.”
SQLSTATE: None
Description: There is no information about %s.
Solution: Configure corresponding information for %s.
GAUSS-51213: “The port number of XML [%s] conflicted.”
SQLSTATE: None
Description: The port number is occupied.
Solution: Check whether the occupied port process is available. If the process is unavailable, kill it, or change a new port number.
GAUSS-51214: “The number of capacity expansion DN nodes cannot be less than three.”
SQLSTATE: None
Description: The number of nodes before scale-out cannot be less than three.
Solution: Ensure that the number of nodes before scale-out is greater than or equal to three.
GAUSS-51215 : “The capacity expansion node [%s] cannot contain CM/ETCD.”
SQLSTATE: None
Description: The CM and ETCD cannot be contained on the scale-out node.
Solution: Delete the CM and ETCD on the scale-out node.
GAUSS-51216: “The capacity expansion node [%s] must contain DN.”
SQLSTATE: None
Description: The node to be added for scale-out does not have any DNs.
Solution: Add DNs on the scale-out node.
GAUSS-51217: “The cluster's static configuration does not match the new configuration file.”
SQLSTATE: None
Description: The database configuration is inconsistent.
Solution: Modify the new XML configuration file, leaving it consistent with the database static configuration.
GAUSS-51218: “Failed to obtain initialized configuration parameter: %s.”
SQLSTATE: None
Description: Failed to obtain the initialization configuration parameters.
Solution: Try to obtain the parameters again.
GAUSS-51220: “The IP address %s is incorrect.”
SQLSTATE: None
Description: The IP address is incorrect.
Solution: Check whether the IP address configured in the XML file is correct.
GAUSS-51221: “Failed to configure hosts mapping information.”
SQLSTATE: None
Description: Failed to configure the host mapping.
Solution: Check whether the /etc/hosts file exists and whether the host name and IP address configured in the file are consistent.
GAUSS-51222: “Failed to check hostname mapping.”
SQLSTATE: None
Description: Failed to check the host mapping.
Solution: Check whether the mutual trust between nodes is normal.
GAUSS-51223: “Failed to obtain network inet addr on the node(%s).”
SQLSTATE: None
Description: Failed to obtain the inet address from the node.
Solution: Run the ifconfig command in the root directory to manually check whether the inet address exists. If it does, try to obtain the address again.
GAUSS-51224: “The ip(%s) has been used on other nodes.”
SQLSTATE: None
Description: The IP address has been used on another node.
Solution: Check whether the IP address on each node in the XML file conflicts with each other.
GAUSS-51225: “Failed to set virtual IP.”
SQLSTATE: None
Description: Failed to configure the virtual IP address.
Solution: Check whether the virtual IP address is used.
GAUSS-51226: “Virtual IP(s) and Back IP(s) do not have the same network segment.”
SQLSTATE: None
Description: The virtual IP address and **backIp **are not in the same network segment.
Solution: Set the virtual IP address and **backIp **in the XML file to be in the same network segment.
GAUSS-51227: “The number of %s on all nodes are different.”
SQLSTATE: None
Description: The number of backIp on all nodes is different from that of the SSH IP addresses.
Solution: Set the number of **backIp **in the XML file to be the same as that of the SSH IP address.
GAUSS-51228: “The number %s does not match %s number.”
SQLSTATE: None
Description: The two numbers are different.
Solution: Set the two numbers to be the same.
GAUSS-51229: “The DN listenIp(%s) is not in the virtualIp or backIp on the node(%s).”
SQLSTATE: None
Description: The listening IP address on the DN is not the virtual IP address or backIp.
Solution: Change the listening IP address to the virtual IP address or **backIp **in the XML file.
GAUSS-51230: “The number of %s must %s.”
SQLSTATE: None
Description: The number of CM servers or ETCDs is incorrect.
Solution: Configure correct numbers for CM servers and ETCDs in the XML file.
GAUSS-51231: “Old nodes is less than 2.”
SQLSTATE: None
Description: The number of old nodes is less than two.
Solution: Set the number of the configured nodes in the XML file to be greater than or equal to 3.
GAUSS-51232: “XML configuration and static configuration are the same.”
SQLSTATE: None
Description: The XML configuration and static configuration files are the same.
Solution: Before the scale-out and scale-in operations, ensure that the XML is different from that of the installed databases.
GAUSS-51233: “The Port(%s) is invalid on the node(%s).”
SQLSTATE: None
Description: The port is invalid.
Solution: Check whether the port number configured in the XML file is correct.
GAUSS-51234 : “The configuration file [%s] contains parsing errors.”
SQLSTATE: None
Description: The XML file is analyzed incorrectly.
Solution: Check whether the configuration file is broken. If the file has been broken, copy a file from another node. If the file has not been broken, reinstall the database.
GAUSS-51235: “Invalid directory [%s].”
SQLSTATE: None
Description: The directory is invalid.
Solution: Check whether the directory is correct.
GAUSS-51236: “Failed to parsing xml.”
SQLSTATE: None
Description: Failed to parse the XML file.
Solution: Check whether the XML file is opened successfully.
GAUSS-51239: “Failed to parse json. gs_collect configuration file (%s) is invalid , check key in json file”
SQLSTATE: None
Description: An error occurs when the system parses the JSON file.
Solution: Check whether the JSON file format is correct.
GAUSS-51240: “gs_collect configuration file is invalid, TypeName or content must in config file.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51241: “The parameter %s(%s) formate is wrong, or value is less than 0.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51242: “gs_collect configuration file is invalid: %s, the key: (%s) is invalid.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51243: “content(%s) does not match the typename(%s) in gs_collect configuration file(%s).”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51244: “(%s) doesn't yet support.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51245: “There are duplicate key(%s).”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51246: “%s info only support one time collect.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51247: “These virtual IP(%s) are not accessible after configuring.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51248: “gs_collector does not support '%s' view collection. please check key in json file.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-51249:“The parent directory of appPath '%s' is a subset of the toolPath '%s', appPath cannot be in any subset of toolPath,please change 'gaussdbToolPath' to another path that does not contain '%s' in the XML file.”
SQLSTATE: None
Description: The parent directory of appPath is a subset of toolPath, so appPath cannot be a subset of toolPath. gaussdbToolPath in the XML file cannot contain appPath.
Solution: Do not use appPath as the bottom-layer parent path under the gaussdbToolPath path configured in the XML file.
GAUSS-51250:“Error: the '%s' is illegal.\nthe path name or file name should be letters number or -_:.”
SQLSTATE: None
Description: Error: the '%s' is illegal.\nthe path name or file name should be letters number or -:. Solution: The path name or file name should be letters number or -:.
GAUSS-51251:“The %s cannot be a root user group or a link.”
SQLSTATE: None
Description: The directory or file cannot belong to the user group of the root owner or the soft link that points to the root owner.
Solution: After confirming that there is no risk, change the owner and permission of related files or directories.
GAUSS-51252:“Failed to start the DSS server. Please check the dss logs.”
SQLSTATE: None
Description: The DSS server fails to be started.
Solution: For details, check the logs in dss_home.
GAUSS-51253:“Failed to clear the shared memory of the user. Error %s.”
SQLSTATE: None
Description: Failed to run the 'ipcm -a' command in the user state.
Solution: For details, check the logs in dss_home.
GAUSS-51254:“Failed to kill dssserver. Error %s.”
SQLSTATE: None
Description: Failed to run the 'pkill -9 -f dssserver' command.
Solution:For details, check the logs in dss_home.
GAUSS-51255:“Failed to reencrypt the password with dsscmd”
SQLSTATE: None
Description: Failed to reencrypt the password with dsscmd
Solution: For details, check the logs in dss_home.
GAUSS-51256:“Failed to get the encrypted text with dsscmd”
SQLSTATE: None
Description: Failed to get the encrypted text with dsscmd
Solution: For details, check the logs in dss_home.
GAUSS-51257:“There are some errors about dsscmd.”
SQLSTATE: None
Description: There are some errors about dsscmd.
Solution: For details, check the logs in dss_home.