Re: OAS408x installation
Date: Thu, 24 Aug 2000 15:31:47 +0800
Message-ID: <39A4CF63.D0A44039_at_hkbu.edu.hk>
Hi,
I am Johnson's collegue who installed OAS on Redhat 6.2. After installation the first thing I did is to start up all the services and listeners and then followed the tutorial to add an application with a PLSQL cartridge. When I invoke the application I got 'An application error has occured. Please try again on the page'. Then I checked the wrb.log file. The cause of the error seems that it cannot bring up the cartridge.
Anyone has some clues? Thanks in advance.
Lilian
Verna Legaspi wrote:
> > I see. BTW, where to get OAS 3.x?
>
> Sorry - I don't know the answer to this one, other than perhaps ordering it
> directly from Oracle?
>
> > > The applications having a red flag (down) for status may be normal. If
no
> > > one has used the application in a while, it will be taken down. It will
> > > become a green flag (up) when it's needed/called.
> >
> > Let me rephase the situation. I know your point. However,
> > the red flag is ALWAYS going up even that I choose to reload.
> > I supposed you and other will answer that the green flag
> > will keep a certain of time until it's timeout. But it does
> > not for me.
>
> When you say reload - are you just reloading the application, or the entire
> OAS? Anyhow, I guess it doesn't matter. If you reload an application this
> is already (currently) down, it will still stay down. Only way to get the
> application to show up as up and green is if you actually use it - In our
> case, run a pl/sql procedure. Only then will the green flag stay up until
> it times out again after a period of inactivity.
>
> > I see. It needs DBA privilege for DB_Browser. But as I've said,
> > the wrb.log said that the node's virtual memory is exhausted.
>
> As for the virtual memory being exhausted - how much RAM is on the machine?
> You mentioned something about changing the domain. We ran into a problem
> with this as it corrupted the svwww.cfg file. Called Oracle on it and there
> was a patch. That was a while ago, and I know they have a servlet patch
> out, too. Maybe this is all you need.
Received on Thu Aug 24 2000 - 09:31:47 CEST
