Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> help: Pro*C app hangs when server crashes
Hi. I'm developing Pro*C precompiler apps on Oracle 7.3, running on a
Sun Enterprise 4000 under SunOS 5.6. To my surprise, if the Oracle
server crashes (e.g. I deliberately do a "shutdown abort"), the embedded
SQL statements in my app don't start failing (e.g. returning ORA-01012):
they hang forever, so my app freezes and can't do any error recovery.
Things get totally blocked up.
If I communicate between two different UNIX hosts via SQL*Net, with the server on one and the app on the other, I *do* get nice error codes (e.g. "end of file on communication stream", "not connected"). But on a single host, communicating via shared memory, things just freeze.
Is there some mode, flag, etc. that I need to set in order to get embedded SQL statments to start returning error codes if the Oracle server crashes? Any help would be helpful. Thanks!
ZZZ Received on Thu May 21 1998 - 12:16:46 CDT
![]() |
![]() |