|Oracle® Beehive Installation Guide
Release 1 (1.5) for Solaris Operating System (SPARC 64-Bit)
Part Number E14832-05
Unable to Perform FTP Operations
Check the log files of BEEAPP, BEECORE, and BEEMGMT. If you see an exception thrown by oracle.ocs.omb.transport.exception.TimedOutException, ensure the port defined by ServerPort in the BTI component is accessible.
This may occur if you have two Oracle Beehive instances, and you block this port (through your firewall) between these instances.
ORA-12850: Could not allocate slaves on all specified instances, ORA-00018: Maximum number of sessions exceeded
If you receive the error "Failed to access configuration repository (database). Internal error message: java.sql.SQLException: Connection Unavailable" when running a
beectl command and in your database alert log see the errors ORA-12850: Could not allocate slaves on all specified instances and ORA-00018: Maximum number of sessions exceeded, increase the processes initialization parameter in your database. Refer to "Initialization Parameters" in "Oracle Beehive Database Requirements" for information on changing initialization parameters in your database.
Oracle Beehive Install Wizard Fails Because Apache HTTP Server Unable to Start
Oracle Beehive Install Wizard may fail because of an error similar to the following:
<ORACLE_HOME>/Apache/Apache/bin/apachectl startssl: execing httpd Syntax error on line 233 of <ORACLE_HOME>/Apache/Apache/conf/httpd.conf: Cannot load <ORACLE_HOME>/Apache/Apache/libexec/mod_auth_dbm.so into server: <ORACLE_HOME>/Apache/Apache/libexec/mod_auth_dbm.so: undefined symbol: dbm_fetch
The undefined symbol error may result from the symbolic link
/usr/lib/libdb.so.2 pointing to a different file or an incorrect version of the shared library.
Before starting the Install Wizard, create (or recreate) the following symbolic link as the root user:
ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
You may export the entire system model configuration data into an XML file for any given configuration version with the
beectl export_configuration_data command.
You may provide your Oracle support representative the output from this command. This will help your representative investigate any problems with your Oracle Beehive deployment faster. You may also use the output of from this command to compare the configuration between different Oracle Beehive deployments, such as between a test and a production deployment.
Note that secure values do not appear in the output for security reasons.
HTTP Server mod_oc4j Continues Trying to Route to OC4J after Being Disconnected
If you suddenly shutdown an application tier, you may receive the following error messages in your Oracle HTTP Server error log file (typically named
[Thu Sep 4 12:59:07 2008] [error] [client 22.214.171.124] [ecid:1220558336:126.96.36.199:3454:0:2430,0] mod_oc4j: request to OC4J myhost.example.com:12503 failed: Connect failed (errno=113) ... [Thu Sep 4 13:02:40 2008] [error] [client 188.8.131.52] [ecid:1220558560:184.108.40.206:3802:0:2395,0] mod_oc4j: request to OC4J myhost.oracle.com:12503 failed: Connect failed (errno=111)
In this situation, the
mod_oc4j module has not been notified that the application tier it is trying to connect to has been shutdown. Consequently, it will repeatedly attempt to connect to the application tier until it fails a certain number of times , which is specified by the
The default value for
MaxErrors is 100. You may change the value of this parameter to a lower value (such as 1) by following these steps:
Edit the file
\beehive\conf\scripts\httpd.conf.tmp and add the line
Oc4jSet MaxErrors 1 in the
<IfModule mod_oc4j.c> section:
<IfModule mod_oc4j.c> Oc4jSet MaxErrors 1 </IfModule>
Run the following command to regenerate the file
\Apache\Apache\conf\mod_oc4j.conf (which contains the
beectl modify_local_configuration_files --restart_needed false
Run the following command to restart Oracle HTTP Server:
<Oracle home>\opmn\bin\opmnctl restartproc process-type=HTTP_Server
Refer to OracleMetaLink Note 468325.1 "HTTP Server mod_oc4j Continues Trying To Route To OC4J After Node Is Disconnected" for more information.