Kbase 21845: Error 778 Running Client/Server Config. on ORACLE DataServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/02/2002 |
|
SUMMARY:
This Solution gives some possible reasons for error 778 when using a client/server connection with the ORACLE DataServer.
EXPLANATION:
When starting an ORACLE DataServer broker and trying to connect a Progress client to an ORACLE database, you might receive the following error on a Windows client:
Error reading socket, ret=10054, errno=2. (778)
On a UNIX client, the error would look like this:
Error <read/writing> socket, ret=-1, errno=232. (778)
Error (778) can be reproduced by starting both client and server on the same machine; so it is not a problem with physical network.
The error is caused by _orasrv crashing.
SOLUTION:
When starting the ORACLE DataServer broker, either from ProControl or command line, ORACLE_HOME and ORACLE_SID need to be set correctly so that Progress can pick up the ORACLE OCI library.
The server (_orasrv) checks to see if ORACLE_HOME is set. It does not check to see if it is set correctly. That is why orasrv can initially be spawned, but then dies when the client is actually talking to ORACLE.
On UNIX, (in particular Progress 9.1A and above), Progress looks in $ORACLE_HOME/lib for the shared library. The server on UNIX won't run without ORACLE_HOME being set correctly.
You might also want to verify that ORACLE_SID is set to point to the proper ORACLE instance (ORACLE_SID matters if not using sqlnet
et8).