Wednesday, September 2, 2009

ESB Project Registration Fails in Jdeveloper

After upgrade to a 10.1.3.4 MLR, registration of projects to ESB fails from JDeveloper or ANT.You get the following error at registration time:
Entity Deployment Failederror code: 1001 : 5 summary: Failed to create Service "ESBService". Fix: Ensure that the (a) Repository is available. (b) The Connection information for the Repository is Valid. Verify the detailed cause of error if available. Contact Oracle Support if error not fixable.

The ESB Designtime logfile at $ORACLE_HOME/j2ee//log/*_*_1/oc4j/log.xml will have the following similar errors:

<message>
<header>
<tstz_originating>2009-02-16T13:09:48.858-05:00</tstz_originating> <component_id>tip</component_id>
<msg_type type="ERROR"></msg_type>
<msg_level>1</msg_level>
<host_id>t1-l1</host_id>
<host_nwaddr></host_nwaddr> <module_id>esb.configuration.deployment</module_id>
<thread_id>17</thread_id>
<user_id>test</user_id>
</header>
<correlation_data>
<exec_context_id><unique_id><host>:97790:1234807788280:19</unique_id><seq>0</seq></exec_context_id>
</correlation_data>
<payload>
<msg_text>Deployment failed due to :Failed to create Service "ESBService".Ensure that the (a) Repository is available. (b) The Connection information for the Repository is Valid. Verify the detailed cause of error if available. Contact Oracle Support if error not fixable.</msg_text>
</payload>
</message>


The issue is caused by not successfully running the 10.1.3.4 MLR database upgrade script for the ESB (oraesb) schema after applying one of the 10.1.3.4 MLR patch sets.

The key error from the log.xml file is:
For Oracle database: Caused by: java.sql.SQLException: ORA-00904: "FQ_PATH": invalid identifier

Solution

1. After a 10.1.3.4 MLR is applied to a system make sure that the instructions in the readme for the patch set is followed, specifically running the database upgrade scripts for the specified SOA schema. For this particular case the ESB oraesb script must be run. Verify that the sql scripts complete successfully.

2. After the database scripts have been run successfully try the ESB registration again.

No comments: