Re: Oracle problems.

From: Paul Sture <paul.sture_at_bluewin.ch>
Date: Wed, 05 Dec 2001 22:02:58 +0100
Message-ID: <VA.000004d8.cb2232ec_at_bluewin.ch>


In article <Tj6P7.69396$Z2.1019213_at_nnrp1.uunet.ca>, Peter Weaver wrote:
> "Leigh G. Bowden" <LGBowden_at_bowdenfamily.fsnet.co.uk> wrote in message
> news:9uh0g8$7kk$1_at_newsg1.svr.pol.co.uk...
> > We have an AlphaServer 2100 4/200 with two CPU's and 1GB of memory and
> > plenty of disks - all shadowed. As far as I am aware it is using Oracle
> > 7.1.5 on OpenVMS 6.2 AXP.
> >
> > It appears to be unreliable. After about three weeks this system will lock
> > up and the console will report "Insufficient memory for operation" type
> > errors and will allow nobody to logon even at the console. The only way to
> > get out of this to power cycle it.
> >
> > Has anybody experienced this before and got any suggestions for a fix??
>
> I do not know if this will help or not, but it sounds like a problem we had
> with an old version or Oracle (I don't think it was 7.1.5, but it may have
> been). Make sure you take a look at what the procedure is doing and run it
> in test mode (i.e. comment out the actual deassign and double check that
> the table the .COM wants to deassign is actually no longer in use before you
> let the job run completely) since I do not know what versions of VMS/Oracle
> we had had this problem on.
>
That was my diagnosis too. When the logical name tables are "full", you can't even perform a new logon.
___
Paul Sture
Switzerland Received on Wed Dec 05 2001 - 22:02:58 CET

Original text of this message