May 10, 2006 at 11:59 am
I have a job running on SQL Server 2000 every night which brings some data from an ORACLE 8i server and store them in the SQL Server database. The process uses OPENQUERY to read the ORACLE server. The ORACLE server is linked using Microsoft OLDB Provider for Oracle.
Sometimes the ORACLE server is restarted without notification and at this point the job on the SQL Server becomes kind of stuck. This means that is not doing anything at all, keeps all the resources locked and, if killed, is not rolling back. As a result it remains in some ambigous state from which I couldn't get out less painfull than using restart (for SQL server instance).
Did anybody had this problem and if so, is there a way to actually kill that SQL Server process that is stuck without restarting the service?
Gabriela
May 11, 2006 at 11:15 am
We haven't had that exact problem before, but we have had cases where the provider ran out of storage (memory) and only restarting the service would fix the hang. Couldn't kill the SPIDS either. It only happens when connecting to Oracle for some reason. I'd look into why the Oracle server is restarted though....
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply