GAUSS-52900 -- GAUSS-52999
GAUSS-52900 : " Failed to upgrade strategy: %s."
SQLSTATE: None
Description: Failed to upgrade the policy.
Solution: Check the version information file version.cfg.
GAUSS-52902 : "Can not support upgrade from %s to %s."
SQLSTATE: None
Description: The version cannot be upgraded.
Solution: Use a supported version or an intermediate version for upgrade.
GAUSS-52904 : "Please choose right upgrade strategy."
SQLSTATE: None
Description: Select the right upgrade policy.
Solution: Revoke a policy and select an interface. Use the upgrade interface properly, or invoke an automatic upgrade interface.
GAUSS-52905 : "Failed to obtain old cluster version."
SQLSTATE: None
Description: The current version fails to be obtained.
Solution: View the log and find out detailed error information.
GAUSS-52908 : "Failed to set cluster read-only mode."
SQLSTATE: None
Description: Failed to set the read-only mode.
Solution: View the guc log. After troubleshooting the error, execute the command again.
GAUSS-52909 : "Invalid mode: %s."
SQLSTATE: None
Description: Invalid mode.
Solution: Find the corresponding log information.
GAUSS-52910 : "Failed to check user definition."
SQLSTATE: None
Description: The user-definition fails to be checked.
Solution: Check whether errors exist in the user-defined check script. Identify the upgrade cause based on the expectation.
GAUSS-52911: Full upgrade failed. Roll back to the original cluster."
SQLSTATE: None
Description: The full upgrade failed.
Solution: Perform the upgrade again.
GAUSS-52912 : "Failed to start the new cluster in normal mode. Please manually handle the problem and start it again."
SQLSTATE: None
Description: The cluster fails to be enabled in normal mode.
Solution: Manually identify the cause. Invoke the gs_om -t start command to enable the cluster.
GAUSS-52913: "Cannot do rollback."
SQLSTATE: None
Description: Rollback failed.
Solution: Run the query again.
GAUSS-52914 : "Failed to clean rollback script."
SQLSTATE: None
Description: Failed to clear the rollback script.
Solution: Check the cluster status. If the upgrade succeeds, manually delete the remaining files.
GAUSS-52915 : "Invalid upgrade step: %s."
SQLSTATE: None
Description: Check the cluster status. If the upgrade succeeds, manually delete the remaining files.
Solution: In the GPHOST path, confirm whether the backup file that records the upgrade procedure is modified.
GAUSS-52916 : "The current environment does not meet upgrade requirements or fails to perform backup operations."
SQLSTATE: None
Description: The environment does not meet the upgrade requirements or the backup fails.
Solution: Check the disk size and confirm there are enough space reserved that must be greater than or equal to 200 MB.
GAUSS-52917 : "Binary upgrade failed. Roll back to the original cluster."
SQLSTATE: None
Description: The upgrade in binary mode fails and rolls back to the primitive cluster.
Solution: View the upgrade log and identify the fault cause. Initialize the upgrade again.
GAUSS-52918 : "Cannot find GTM in current cluster."
SQLSTATE: None
Description: The GTM is not found.
Solution: Invoke the gs_om -t status --detail command to query the cluster status. If the GTM cluster in the cluster is abnormal, reinstall the cluster to restore the cluster.
GAUSS-52919 : "Failed to upgrade."
SQLSTATE: None
Description: The upgrade fails.
Solution: View the upgrade log and identify the fault cause. Perform the upgrade again as required.
GAUSS-52920 : "Failed to restore GUC parameter after full upgrade."
SQLSTATE: None
Description: The GUC parameter fails to be restored after the full upgrade.
Solution: View the upgrade log and the GUC log. Identify the cause and perform the upgrade again.
GAUSS-52921 : "Invalid upgrade type: %s."
SQLSTATE: None
Description: The upgrade type is invalid.
Solution: Use the automatic upgrade interfaces.
GAUSS-52922 : "Failed to record step information on local node."
SQLSTATE: None
Description: The upgrade step fails to be recorded.
Solution: Confirm you have the permission on the temporary file directory and the directory exists.
GAUSS-52923 : "Failed to record upgrade status."
SQLSTATE: None
Description: The upgrade status fails to be recorded.
Solution: Confirm you have the permission on the temporary file directory and the directory exists.
GAUSS-52924 : "The information in upgrade status file is wrong."
SQLSTATE: None
Description: The information in the upgrade status file is incorrect.
Solution: Modify the upgrade backup file and restore the record file based on the upgrade procedure.
GAUSS-52925 : "Input upgrade type: %s record upgrade type: %s\nMaybe you chose the wrong interface."
SQLSTATE: None
Description: An incorrect upgrade interface is used.
Solution: Use the automatic upgrade interface or automatic rollback interface.
GAUSS-52926 : "The step of upgrade should be digit."
SQLSTATE: None
Description: The upgrade procedure must be a digit.
Solution: Check whether the upgrade backup file is modified and try to restore it.
GAUSS-52927 : "Failed to upgrade application."
SQLSTATE: None
Description: The upgrade fails and the new cluster fails to be installed.
Solution: View the local log, identify the cause, and perform the operations again.
GAUSS-52928 : "The version number of old cluster is [%s]. It must be a digit and greater than or equal to 1.0."
SQLSTATE: None
Description: The old cluster version number is incorrect, which should be a digit and greater than or equal to 1.0.
Solution: View the current version file in the cluster and confirm whether it is modified.
GAUSS-52929 : "Failed to check application version. Output: \n%s."
SQLSTATE: None
Description: The cluster version fails to be checked
Solution: Check the upgrade file and confirm the version information on each node.
GAUSS-52930 : "Failed to check upgrade environment."
SQLSTATE: None
Description: The upgrade environment fails to be checked.
Solution: Check the local log, identify the cause. After troubleshooting it, upgrade the environment again.
GAUSS-52931: Failed to check tablespace location path.
SQLSTATE: None
Description: Failed to check the local path of the tablespace.
Solution: Delete \n from the tablespace directory.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot