Saturday, June 13, 2009

ESB Error - ESB DT Cache is not initialized. ESB bootstrap failed

Sometimes after applying patch to upgrade to esb console might show design time issues/ the processes not loading . As usual if we explore the log.xml file you should be able to get the error associated with the issue.

One of the common errors are

error code: 2006 : 5

summary: ESB DT Cache is not initialized. May be ESB bootstrap failed

Fix: Please review ESB prameters for their correctness.

"ORA-01000: maximum open cursors exceeded" , with

"ESB bootstrap: Error occurred while initializing ESB server from the ping thread"

and " Internal error raised trying to instantiate web-application: <> defined in web site OC4J 10g (10.1.3) Default Web Site. Application: <> does not exist. Error creating Web application: <>

The only way to solve it is to check for the number of cursors. Usually it will be configured to ‘300’, That needs to be increased.

1. Shut down the SOA server
2. Increase the open_cursors to 1500 by changing the "open_cursors" parameter in the init.ora file

3. Bounce the DB.
4. Restart the SOA server

You should be good to go and must be able to register new processes as well as see all the existing processes.

No comments: