Instance 'name' has been terminated in application log

[mode906]

Thread posted below and I have the exact same problem, but there were no replies and the thread is closed now. How can I contact the thread creator to find out the resolution to the problem?

http://www.tek-tips.com/viewthread.cfm?qid=1391890&page=10

In the application log we have been getting this event frequently, we already got 10 of them today, yesterday we got about 50, these go back as far as the log goes back to 12/24/2007.

Event ID: 16
Source: Oracle.p001
Description: Instance p001 has been terminated

I’d really like to find out what is causing them.

 

[SantaMufasa]

Mode, The best resolution to your problem is to post your question in the same Windows forum as the original post that had the same problem that you have been experiencing. In your re-post, type in just the thread identifier, which I have done here: thread759-1391890. Note that I typed only "thread759" then "-1391890", which automatically lists the full name of the other thread, plus a link to that other thread (without all of the other "http" gobblety-gook).

In your new thread, I recommend that you explicitly invite Bookouri to post either the resolution to his original post, or acknowledge that he never resolved the problem (and is just ignoring the problem on an on-going basis).

The other alternative is to contact Micro$oft technical support and pay for them to tell you how to fix the issue.

In any case, once you identify a resolution, I'd be pleased to know what the resolution is.

Let us know here how things progress.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[mode906]

I did a few metalink searches and found that this is a false error and bug. Instead of patching this server we are going to migrate to 10g so its a mute point for us. I think the windows application log is throwing the error when dead connection detection disconnects database connections that have been stale for awhile. Thanks for the heads up with your direction, but its probably not a windows problem, only an oracle bug that we haven't patched