Oracle 9iAS Release 2 + Oracle Reports Installation/Configuration

[OracleMiddleTierGuy]

Hi! I have the following things I have done in getting the Oracle 9iAS Release2 on RedHat Linux Advanced Server 2.1 installed and configured to use Oracle Reports:

1. I installed 9.0.2 Infrastructure tier on the server (in ORACLE_HOME1).
2. I installed 9.0.2 BI tier on same server (ORACLE_HOME2).
3. All configuration wizards after both installs completed successfully.
4. All components in both tiers appeared as running through EM web interface, except for Oracle Reports, which had a question mark next to it, as status.
5. Working with Oracle Support to resolve this. Various changes to configuration files yield unstable results. I can start the Reports server and run demo as well as custom reports. However, after about 30 minutes, Reports server stops responding and Enterprise Manager (OEM) web site for Business Intelligence (BI) tier is no longer accessible - the page hangs. There is no apparent workaround except for shutting down 9iAS components manually from command line every time this happens. This, of course, means that I can't use this 9iAS install for any other purposes, until Reports issue is resolved.
6. It is my perception that the problem is specific to Oracle Reports, but it may not be the case.

Installation is done on Linux RedHat Advanced Server 2.1
Dell dual-Xeon machine with 2GBs of RAM
Latest distribution of 9iAS Release 2 (9.0.2) Enterprise Edition downloaded from technet.oracle.com

Please help me in resolving this problem if you had experianced this before. Any suggestions will be thankfully appreciated.

 

[KC6]

Hi,

I have a installation of 9iAS instance recently but haven't had the chance of any intensive testing yet.

I was having similar problem with my Tomcat 4.x which is the sucessor of Jserv (the servlet engine in 9iAS) and discovered that the problem was due to some unhanlded exception by some servlet exception, for example, file open error (as I know Oracle reports was confired to be executed as a servlet).

I would suggest u tho dig into the log of the Jserv and see if there's any exception esclated to the Jserv and ultimately causing this.

My 2 cents of comments,
Kevin