Executing a stored procedure makes the network database server stop.
The procedure declares a FOR loop (cursor) where it iterates a proxy table. Running the procedure I get "communication error" as the network database service sometimes stops. However sometime I do get a successful run.
the proxy table is located in a remote server (oracle), so it seems to be an issue with the communication between sybase/oracle.
Transcript of console.log
I. 12/12 13:59:07. TCPIP link started successfully I. 12/12 13:59:07. Now accepting requests
I am able to do crash the db network service by running a sql towards the proxy table also.
SELECT * FROM PROXY_ORACLE_TABLE;
There's less than 50 rows (though there is a blob column).
Is there a db log which would give me more details to figure out what's causing this? Or does anyone have an idea of what the issue might be?
If the possibility exists that the server is down. I would copy the rows into a temp table and work on that set.
Even then it is possible that the server stops responding during the select.
Hope This Helps
answered 12 Dec '12, 06:06