Starting/Stopping of OracleAS Portal Mid-Tier Components Takes Long Time When Metadata Repository is RAC based
(Doc ID 428722.1)
Last updated on FEBRUARY 27, 2017
Applies to:Portal - Version: 10.1.2.0.2
Oracle Fusion Middleware - Version: 10.1.2.0.2 to 10.1.2.3.0 [Release: AS10gR2 to AS10gR2]
Oracle Fusion Middleware High Availability - Version: 10.1.2.0.2 to 10.1.2.3.0 [Release: AS10gR2 to AS10gR2]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: 10.1.2.0.2 to 10.1.2.3.0
Checked for relevance on 03-APR-2009
An OracleAS high available topology has been implemented. This implementation includes a highly available OracleAS Identity Management with a Metadata Repository which resides in a Oracle Server RAC database.
Starting up middle tier components like OC4J_Portal is successful but can take a long time e.g. more than 5 minutes.
The OC4J_Portal component with default settings will attempt to make 5 database connections during startup.
Once started, any additional Database connections required by Portal will sometimes take a long time to connect, causing Portal to report stall time errors.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document