GAUSS-02991 -- GAUSS-03000
GAUSS-02991: "requested character too large"
SQLSTATE: 54000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-02992: "requested character too large for encoding: %d"
SQLSTATE: 54000
Description: The input string is too long.
Solution: Ensure that the input string is in Unicode format.
GAUSS-02993: "TIMESTAMP(%d)%s precision must not be negative"
SQLSTATE: 22023
Description: The precision of the timestamp type cannot be smaller than zero.
Solution: Ensure that the precision of the timestamp type is greater than or equal to zero.
GAUSS-02994: "timestamp out of range: '%s'"
SQLSTATE: 22008
Description: The input timestamp value is out of range.
Solution: Ensure that the value of the timestamp type is within the range.
GAUSS-02995: "date/time value '%s' is no longer supported"
SQLSTATE: 0A000
Description: The string value to be converted to the timestamp type is incorrectly parsed.
Solution: Ensure that the format of the input string is correct. The string to be converted to the timestamp type must be in "Date/Time" format. For details, see "Data Types" in the SQL Syntax.
GAUSS-02996: "unexpected dtype %d while parsing timestamp '%s'"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
GAUSS-02997: "timestamp out of range"
SQLSTATE: 22008
Description: The input timestamp value is out of range.
Solution: Ensure that the input value of the timestamp type is valid. For details about the data value range, see "Data Types" in the SQL Syntax.
GAUSS-02998: "timestamp cannot be NaN"
SQLSTATE: 22008
Description: The data of timestamp type cannot be an unlimited value.
Solution: Check the input data.
GAUSS-02999: "smalldatetime out of range: '%s'"
SQLSTATE: 22008
Description: Data is out of range.
Solution: Check the input data.
GAUSS-03000: "unexpected dtype %d while parsing smalldatetime '%s'"
SQLSTATE: XX000
Description: Internal system error.
Solution: Contact technical support.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.