X-no-Archive:yes
This is what caused the TC file to remain in use on your system.  As I said
before, you must terminate the link from Oracle to the Allbase DBE, before
you bring the network down.

Kind regards,

Denys. . .

Denys Beauchemin
HICOMP America, Inc.
(800) 323-8863  (281) 288-7438         Fax: (281) 355-6879
denys at hicomp.com                             www.hicomp.com



-----Original Message-----
From:   Joseph Rosenblatt [SMTP:[log in to unmask]]
Sent:   Thursday, 28 January, 1999 9:26 AM
To:     [log in to unmask]
Subject:        Re: Oracle on HP Systems

Last night I had to bring down my network. I did this with the standard
NETCONTROL STOP NSCONTROL STOP commands. To my amazement this caused ORACLE
to come down. I guess I can understand why this happened, something like
disruption of the socket but the story continues. The standard recovery
procedures start with stopping ORACLE. The reply was can't stop ORACLE it's
not up. Go to bring up ORACLE it tells me its already attached. Can't go
UP,
can't go DOWN. It's time for a support call. The gist of the response was
ORACLE is hung in limbo, Reboot. I asked," Use START RECOVERY or START
NORECOVERY?" The reply was, "Huh?" I did a START RECOVERY (gotta save those
user streamed jobs in the queue) and was able to restart ORACLE.

My suggestion for an ad slogan: ORACLE! WHEN DOES THE FUN START?

Just my thoughts.