You are running a query involving a remote connection. You unexpectedly receive error 936. Depending on the additional error information your application collects and returns you might see a message like this:
936: Error on remote connection, g_prod, conerr=-25582, oserr=0, err
-936 Error on remote connection connection-name.
An attempted connection to a remote host failed. Check the name of the
connection that is specified in your particular connection statement
(CONNECT, DATABASE, and so on) to make sure that you correctly
specified the name or path of the connection. Check for incorrect
spelling. Check for the wrong connection name.
As the finderr output above points out, you should first make sure your connection information is correct.
Assuming the connection information is correct then the cause of error 936 is a connection being lost.
Note: There could be other causes.
Diagnosing the problem
The connection might have been lost due to the session being killed on the remote server using onmode -z. If onmode -z was used, then the remote server's online.log will have a message like this in it:
10:21:58 sid 32 username informix@g_prod pid 4194632 terminated.
If the connection was lost due to a network error it could be difficult to track down the cause. If a network problem is happening consistently and you typically run remote queries, then you will likely see errors in the online.log indicating the same. These would be errors like 22582, 25580, 25579, and possibly other 255** errors.
Resolving the problem
- Correct the connection information and try again.
- Errors 936 and 25582 errors would are expected to occur when the remote session is killed with onmode -z.
- Look at applicable network related logs to see if any problems were reported. Check network related hardware to make sure it is operating properly.
- Read these documents for further help resolving 25582 errors: