ESB Control shows "Designtime cache has not been initialized"

0

After installing Oracle SOA Suite 10g (10.1.3.3) and logging on to the ESB Control, the following error appears:
Designtime cache has not been initialized Please look in logs for following signs of failure.
Fix them and restart.

Possible causes are various, but here are the most important ones:
(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.
Similarly, the OC4J log shows the following:


08/06/01 23:56:57 oracle.tip.esb.infra.exception.ESBRuntimeException: 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.
08/06/01 23:56:57 at oracle.tip.esb.console.CacheManager.getInitializedInstance(CacheManager.java:319)
08/06/01 23:56:57 at oracle.tip.esb.console.XMLConsoleManagerImpl.(XMLConsoleManagerImpl.java:218)
08/06/01 23:56:57 at ………..

And so on
If you are running ESB in a cluster, before attempting the solution below, try shutting down both the ESB Design Time and ESB Runtime. Then start up all your ESB Design Times before starting up ESB Runtime, and try logging in again.

Details
1. If the hostname or IP address of the server has changed (e.g., if this is a DHCP host), this is the root cause of this error.
If that is the case, perform the following steps to resolve the issue, otherwise proceed to Step 2 to reset your metadata.

a. Edit the ServerName and Port directives in $ORACLE_HOME/Apache/Apache/conf/httpd.conf and ensure that it is set to a valid hostname.

b. Log in to the database as the ORAESB user, and issue the following SQL statement:
UPDATE oraesb.esb_parameter
SET dt_oc4j_host = ”,
dt_oc4j_http_port = ”;

2. Steps 2-4 describe how to reset your metadata. If the solution above resolves your issue, do not proceed.

Shutdown the SOA Suite:
export ORACLE_HOME=your values
$ORACLE_HOME/opmn/bin/opmnctl stopall

3. Run the reset.sh script. However, it will reset all your metadata (i.e., delete all existing metadata). The command below backs up the existing metadata to a file called metadata.zip.
cd $ORACLE_HOME/integration/esb/bin
reset.sh -Dexport true -Dmetadatafile /u01/app/oracle/product/10.1.3/soa_1/metadata.zip -DDB_URL=jdbc:oracle:thin:@:1521: -DDB_USER oraesb -DDB_PASSWORD -DDB_DRIVER oracle.jdbc.driver.OracleDriver
The output will be similar to:
oracle@oradev:/u01/app/oracle/product/10.1.3/soa_1/integration/esb/bin> /u01/app/oracle/product/10.1.3/soa_1/integration/esb/bin/reset.sh -Dexport true -Dmetadatafile /u01/app/oracle/product/10.1.3/soa_1/metadata.zip -DDB_URL=jdbc:oracle:thin:@oradev:1521:soadb -DDB_USER oraesb -DDB_PASSWORD oraesb -DDB_DRIVER oracle.jdbc.driver.OracleDriver
…….. and so on…..

it ends with

BUILD SUCCESSFUL
Total time: 21 seconds

4. Startup the SOA Suite:
$ORACLE_HOME/opmn/bin/opmnctl startall

Note Use for the topics the proper values; any inconsistensies ends up in the same error message
I used inhere the lightweight adapter values, but better to use the database persistent one (OracleOJMS)

Share.

About Author

Started in pharmacy, I made the change to IT in 1996. I am an Oracle Fusion Middleware Architect at AMIS, with focus on technical infrastructure, Serverside solutions, installing, administering, configuring the Oracle Fusion Middleware stack. My experience is from integrations at telco´s using Oracle AIA, Oracle Portal, OID, Forms&Reports, Discoverer upto the latest Oracle WebLogic 11g releases with practically all Oracle products running on top of it

Comments are closed.