Re: OAS 4.0.7 Problem

Johnson Suter wrote:

Hi Johnson,

I wonder if I have a related problem. I have OAS 4.0.7 on Solaris 2.7 with NN 4.51. My tree applet comes up fine. I see no errors in the java console, however, none of the labels are visible to the right of each widget in the left frame (the tree applet one). The labels only become visible when I click on a widget. Is this normal behaviour? My wrb.app file does not appear corrupted in the least.

TIA,
Henry Katz
ISCS, Inc
hkatz_at_iscs-i.com

> The solution for the tree applet problem is:
>
> Problem Description:
> ====================
>
> You are using Oracle Application Server 4.0.7 and trying to bring up the
> OAS
> Manager Page. The right frame comes up okay, but you are receiving an
> error
> when it starts to bring up the left frame.
>
> The error is:
>
> APPLET TREEAPPLET CANNOT START: ERROR
>
> You have recently made changes to Oracle Application Server from the OAS
>
> Manager pages. This includes changes to cartridges, applications,
> logging,
> etc.
>
> Solution Description:
> =====================
>
> When the OAS Manager tries to bring up the left frame (Website
> Information),
> it
> parses the wrb.app file. If for some reason, the file has become
> corrupt, you
> will receive an error when bringing up the treeapplet. If there is any
> error,
> it will not bring up the left frame at all.
>
> Luckily, OAS4.0 has plenty of backups of the wrb.app file.
>
> The file wrb.app.bak is the first backup. (It was created upon
> installation of
> the Oracle Application Server). The file wrb.app.0 is the latest backup
>
> (most recent). You can try replacing the current wrb.app with this file
> or
> you may want to use wrb.app.3 or wrb.app.4.
>
> *** NOTE: Do not delete the current wrb.app, rename it to wrb.app.sav.
>
> If you have made multiple changes you might need to go back further to
> one of
> the older backups. Once the wrb.app file has been replaced, it should
> bring up
> the tree applet successfully.
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> PURPOSE
>
> An OWS-20202 error may result in the Oracle Application
> Server(OAS)Manager
> tree
> applet failing to load, and the owsctl utility returning errors. This
> article
> discusses one possible cause, and a resolution.
>
> SCOPE & APPLICATION
>
> Article intended for anyone who runs into this error, to resolve the
> issue.
>
> RELATED DOCUMENTS
>
> None.
>
> Why does Bad tree item data for OWS-20202 error occur ?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Should you run out of file system space in the %ORACLE_HOME% directory,
> this will prevent Oracle Application Server (OAS) updating its'
> configuration
> files correctly, and may result in corruption of the site.app and
> wrb.app
> files.
> This will result in an error Bad tree item data for OWS-20202. The OAS
> Manager
> tree applet will fail to load (java console will report an OWS-20202
> error),
>
> and the owsctl utility will report the error also.
>
> If this occurs, then examine both files wrb.app and site.app in the
> %ORACLE_HOME%\ows\admin\%ORAWEB_SITE%\wrb directory. If they seem
> corrupt,
> then make a backup of both files.
>
> Then copy a previous backup of both files to wrb.app and site.app
> (whenever modifications are written to these files, a backup is
> automatically
> taken, and given a number as a file extension. For example wrb.app.9 and
>
> site.app.9).
>
> You may now re-load the tree applet, or try the owsctl utility again.
> Provided
> the backup files are not corrupt, then the OWS-20202 issue should be
> resolved.
> If the backup was corrupt, you may need to move to an earlier copy and
> try
> that.
>
> Note:
>
> Reverting to a backup configuration file may result in loss of DAD and
> Cartridge
> information (changes made between backup and now). This may be easily
> re-
> applied,
> using the OAS Manager as normal.
Received on Sat Sep 04 1999 - 04:31:50 CEST