HPE NonStop SQL/MX Error – 20734 Error error number was returned by CONVERTTIMESTAMP while trying to obtain local civil time.

In this blog post, let’s learn about the error message “20734 Error error number was returned by CONVERTTIMESTAMP while trying to obtain local civil time.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20734 Error error number was returned by CONVERTTIMESTAMP while trying to obtain local civil time.

Reason for the Error

When processing COMMIT BEFORE or COMMIT AFTER clauses, the MODIFY command encountered an error number from the CONVERTTIMESTAMP Guardian procedure when converting the current time to local civil time.

Solution

See the Guardian Procedure Calls Reference Manual topic CONVERTTIMESTAMP Procedure for the meaning of error number and possible recovery actions

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022