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-52901: “New·cluster·commitid·cannot·be·same·with·old·cluster·commitid.”
SQLSTATE: None
Description: The binary upgrade backup path cannot exist with the major version upgrade backup path.
Solution: Determine the reason of the last upgrade failure and sort backup files.
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-52903: “The new cluster version number[%s] should be bigger than the old cluster[%s].”
SQLSTATE: None
Description: Version rollback is not supported, which means the version number after the upgrade must be greater than that of the previous version.
Solution: Confirm the version information.
GAUSS-52904: “Please choose right upgrade strategy.”
SQLSTATE: None
Description: The right upgrade policy should be selected.
Solution: Revoke a policy and select an interface. Use the upgrade interface properly, or invoke an automatic upgrade interface.
GAUSS-52905: “Upgrade nodes number cannot be more than %d.”
SQLSTATE: None
Description: Failed to obtain the current version.
Solution: View the logs and find out detailed error information.
GAUSS-52906: “Grey upgrade nodes number cannot be more than cluster nodes.”
SQLSTATE: None
Description: The upgrade initialization failed.
Solution: View the upgrade logs and identify the fault cause. Initialize the upgrade again.
GAUSS-52907: “Failed to cancel the cluster read-only mode”
SQLSTATE: None
Description: Failed to cancel the cluster read-only mode.
Solution: Manually invoke the GUC tool using commands gs_guc reload -Z coordinator -N all -I all -c “default_transaction_read_only=false” and gs_guc reload -Z datanode -N all -I all -c “default_transaction_read_only=false”. Try to cancel the read-only mode again.
GAUSS-52908: “Failed to set cluster read-only mode.”
SQLSTATE: None
Description: Failed to set the read-only mode.
Solution: View the GUC logs. After troubleshooting the error, run the command again.
GAUSS-52909: “Specified upgrade nodes with same step can do upgrade task.”
SQLSTATE: None
Description: The mode is invalid.
Solution: Find corresponding log information.
GAUSS-52910: “These nodes %s have been successfully upgraded to new version, no need to upgrade again.”
SQLSTATE: None
Description: Failed to check the user definition.
Solution: Check whether errors exist in the user-defined check script. Identify the upgrade cause based on the expectation.
GAUSS-52911: “Last unsuccessfully upgrade nodes %s are not same with current upgrade nodes.”
SQLSTATE: None
Description: The full upgrade failed.
Solution: Perform the upgrade again.
GAUSS-52912: “Some nodes were upgraded but were unsuccessfully, cannot use --continue.”
SQLSTATE: None
Description: Failed to enable the cluster in normal mode.
Solution: Manually identify the cause. Invoke the gs_om -t start command to enable the cluster.
GAUSS-52913: “All nodes have been upgraded. No need to use --continue.”
SQLSTATE: None
Description: Rollback failed.
Solution: Perform the operation again.
GAUSS-52914: “The record commitid is not same with current commitid.”
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: “$GAUSSHOME is not a symbolic link.”
SQLSTATE: None
Description: The upgrade procedure is invalid.
Solution: In the GPHOST path, confirm whether the backup file that records the upgrade procedure is modified.
GAUSS-52916: “Current upgrade status is not pre commit.”
SQLSTATE: None
Description: The cluster node does not meet the submission conditions.
Solution: Submit the upgrade project after all nodes are successfully upgraded.
GAUSS-52917: “Failed to drop old pmk schema.”
SQLSTATE: None
Description: The upgrade in binary mode fails and rolls back to the primitive cluster.
Solution: View the upgrade logs and identify the fault cause. Perform the upgrade again.
GAUSS-52918: “Failed to record node upgrade step in table %s.%s.”
SQLSTATE: None
Description: Failed to find the GTM.
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 or perform warm backup to restore the cluster.
GAUSS-52919: “Upgrade has already been committed but not finished commit.”
SQLSTATE: None
Description: The upgrade failed.
Solution: View the upgrade logs and identify the fault cause. Perform the upgrade again as required.
GAUSS-52920: “Can not use grey upgrade option --continue before upgrade grey nodes.”
SQLSTATE: None
Description: Failed to restore the GUC parameters after the full upgrade.
Solution: View the upgrade logs and the GUC logs. Identify the cause and perform the upgrade again.
GAUSS-52921: “Failed to query disk usage with gs_check tool.”
SQLSTATE: None
Description: The upgrade type is invalid.
Solution: Use the automatic upgrade interfaces.
GAUSS-52922: “Disk usage exceeds %s, please clean up before upgrading.”
SQLSTATE: None
Description: Failed to record the upgrade procedure.
Solution: Confirm that you have the permission on the temporary file directory or that the directory exists.
GAUSS-52923: “Inplace upgrade commit failed.\n%s”
SQLSTATE: None
Description: Failed to record the upgrade status.
Solution: Confirm that you have the permission on the temporary file directory or that the directory exists.
GAUSS-52924: “The %s parameter are only supported in independent deployment mode.”
SQLSTATE: None
Description: The information in the upgrade status file is incorrect.
Solution: Modify the upgrade backup file and try to restore the record file based on the upgrade procedure.
GAUSS-52925: “Input upgrade type [%s] is not same with record upgrade type [%s].”
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-52929: “Failed to check application version. Output: \n%s.”
SQLSTATE: None
Description: Failed to check the cluster version.
Solution: Check the upgrade logs and confirm the version information on each node.
GAUSS-52932: “There is no CN in the remaining old nodes.”
SQLSTATE: None
Description: No CNs are available in the old cluster.
Solution: Check the upgrade logs and confirm the instance information on each node.
GAUSS-52933: “There is not a majority of %s on the remaining old nodes.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.
GAUSS-52934: “Binary upgrade failed.”
SQLSTATE: None
Description: Failed to upgrade.
Solution: Check the upgrade logs or contact R&D engineers to locate the fault.
GAUSS-52935: “Current upgrade version is not same with unfinished upgrade version record.”
SQLSTATE: None
Description: The previous upgrade operation is not complete (not committed or rolled back), and the upgrade is intended to be performed to another version.
Solution: Submit or roll back the previous upgrade, and then perform the upgrade of another version.
GAUSS-52936: “Upgrade is not finished, cannot do another task.”
SQLSTATE: None
Description:Internal system error.
Solution:Contact technical support.