Re: Many Dr Watsons after installing OEM on NT 4.0 service pack 6

What has happened, is that the partial installation of OEM has left a few files behind. What you have to do is remove all the oracle software, registry entries AND the directory \Program Files\Oracle. The last bit cleans up the failed install and a fresh install should now work.

To stop the Dr Watsons, stop all the Oracle services and make sure that they are on manual. Then reboot.

Good Luck
Cheers
Gordon

In article <8f745e$s3i$1_at_nnrp1.deja.com>,   shawnnesser_at_my-deja.com wrote:
> A while back ( a year actually) I got Some Dr.Watson errors when I
> installed Oracle on an NT box. I later found out that the video
> resolution was causing the java apps to fail. Wierd, but as soon as I
> changed resolution it worked fine.
>
> hope this helps,
>
> Shawn Nesser
> OraDBA
> Unisys Federal Systems
> shawnnesser_at_Geo!NOSPAM!!cities.com
>
> In article <3911AEEB.EE766137_at_attens.com>,
> Fernando Mendoza <mendozaf_at_attens.com> wrote:
> > Hello everyone,
> >
> > Has anyone experienced Dr Watson errors after attempting to install
> > Enterprise Manager. I have a small network at home (3 NT 4.0
 machines),
> > I installed Oracle 8.1.5 and OEM on two and all installed fine, I
 then
> > tried to install OEM on the third and it hung. After I noticed no
> > activity on the HDD I killed the installation. Now, every time I try
 to
> > log on to this machine a series of Dr Watson errors pop up rendering
 the
> > machine useless. There is enough Dr Watsons to fill the bottom
 activity
> > toolbar. I've tried to close all the Dr Watson windows but it takes
 so
> > long and it seems to generate more as I close some!!!!
> >
> > The unusual behavior, is that no matter what I try to do on this
> > machine, for example bring up NT explorer, Dr Watsons get generated.
> > I've tried connecting from my other networked machines to try to
 delete
> > the OEM directory ?!?! but the other machines can't even get to it.
 It
> > seems that this 3rd machine is so busy generating Dr. Watsons that
 it
> > doesn't have time to fill requests from other nodes.
> >
> > The only difference between the broken machine and the other two, is
> > that this particular PC was connected to my cable modem, could it be
> > that when Enterprise Manager was trying to scan the network, it went
 out
> > and tried to pick up nodes outside my internal network???? Any
 ideas???
> >
> > Confused
> >
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

--
Gordy
ICQ 3290116
http://www.geocities.com/Area51/Cavern/4253


Sent via Deja.com http://www.deja.com/
Before you buy.