Frequently, when I am logging into ESB Console - http://localhost:7777/esb - I get the following error:
Designtime cache has not been initialized Please look in logs for following signs of failure. Fix them and restart. (a) Database access errors (b) ESB Bootstrap errors (c) OC4J class load errors (d) Product installation errors (e) Export ESB params and verify if host and port parameters are correct. Please contact Oracle Support if unable to fix the issue.
I figured out that this error could be due to multiple reasons. The two most frequent mistakes which I make are:
1. My database / database listener are NOT started and I start the SOA suite, due to which the above error is thrown. For this, just shut down the SOA Suite, start the database, then the database listener and then start the SOA Suite and that should help.
2. Incorrect deployment of the RAR files. I tried to deploy few standalone Resource adapters in the wrong directory and tried to invoke the WSDLs which use the RAR files. Although successfully compiled at design time, but at runtime, after the deploying the ESBs, when my ESB server is starting, this error is thrown.
In such cases, comment the RAR configuration in the oc4j-connectors.xml in the $ORACLE_HOME/j2ee/
Check the two log files (you can check other log files in the OC4J directory apart from these) to get the information, but these cover most of the error information:
a) $ORACLE_HOME/OracleAS/j2ee/oc4j_soa/log/coreman.log:
Example: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12516, TNS:listener could not find available handler with matching protocol stack
The Connection descriptor used by the client was:
//localhost:1521/XE
b) $ORACLE_HOME/j2ee/oc4j_soa/log/oc4j_soa_default_group_1/oc4j/log.xml:
Example:
at oracle.tip.esb.configuration.ServiceBusConstants.loadESBConfigs(Unknown Source)..............
Keep in mind that this error is due to incorrect setup / configuration issue and not an issue with the Product itself.
