HPE NonStop SQL/MX Error – 3192 Union operands table1 and table2 have different access/lock modes.

In this blog post, let’s learn about the error message “3192 Union operands table1 and table2 have different access/lock modes.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

3192 Union operands table1 and table2 have different access/lock modes.

Reason for the Error

NonStop SQL/MX attempted to compile a UNION query that has an access/lock mode that can be applied to both branches of the access/lock mode or only to the second branch of the UNION.

Solution

Specify that the access/lock mode apply to both branches and resubmit

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