File to database adapter error

Question

I am trying to run the File2Database example shipped as part of database adapter samples.Though i have created the tables and modified oc4j-ra.xml as mentioned in readme file.I am getting merge error followed by table or view does not exist,but tables do exist under schema specified in oc4j-ra.xml.Do i need to configure anything else.Please let me know if anyone has faced similar problem.
This is the log :
=====================
<2005-06-15 16:26:59,056> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Since unable to locate the JCA Resource Adapter deployed at 'eis/MyDBConnection', will then attempt to instantiate ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory directly.
<2005-06-15 16:27:08,738> <INFO> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.ox.TopLinkXMLProjectInitializer initialize> Initializing an existing toplink project for use by the database adapter.
<2005-06-15 16:27:09,755> <ERROR> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.DBInteraction executeOutboundWrite> unable to execute the outbound merge operation on: File2Table.Purchaseorder
<2005-06-15 16:27:09,817> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/D:/OraBPELPM/integration/jdev/jdev/myWork/File2Table/DBOutbound.wsdl [ DBOutbound_ptt::merge(PurchaseorderCollection) ] - Could not invoke operation 'merge' against the 'Database Adapter' due to:
ORABPEL-11616
DBWriteInteractionSpec Execute Failed Exception.
merge failed. Descriptor name: [File2Table.Purchaseorder].
Caused by Local Exception Stack:
Exception [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException
Exception Description: java.sql.SQLException: ORA-00942: table or view does not exist
Internal Exception: java.sql.SQLException: ORA-00942: table or view does not exist
Error Code: 942
at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:227)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:698)
at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:506)
at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:131)
Regards
Raju

Answer 1

Hi Raju,
Looking at the error your DBOutbound.wsdl has [location="eis/MyDBConnection"] although the sample shipped has [location="eis/DB/BPELSamples"]. So, I am guessing you have either modified the sample manually, or you may have rerun the db adapter wizard which could have caused this change. So, you could fix this in one of the following ways:
1. Start with a fresh sample and follow the instructions to the dot
2. Go ahead and define an entry in oc4j-ra.xml for eis/MyDBConnection with the appropriate connection parameters
3. Currently, when the jndi name is not defined in the oc4j-ra.xml, the runtime tries to work with the design time connection information which is captured in the DBOutbound.wsdl. In your case, this doesn't seem to work for either of the following reasons: your runtime connection is different from design time connection, or else the design time connection info is not valid for the runtime assuming it is running on different m/c. I could pinpoint what is wrong if I had access to the DBOutbound.wsdl file.
Couple of other best practices while we are on this issue:
- the location attribute which ties the design time and runtime together follows a convention so that we don't have to make sure that it is unique across all of the various adapters: to help out on this front, we follow the convention of eis/<AdapterAbbrev>/<connectionName>. So, I'd change yours to eis/DB/MyDBConnection. By default the wizard generates locations using this convention although it is hand-editable.
- from another error message below "file:/D:/OraBPELPM/integration/jdev/jdev/myWork/File2Table/DBOutbound.wsdl [" I get the feeling that you are copying the sample elsewhere. Is there a need to do that ? You could just add the jdev project (.jpr) for this sample to any existing jdev workspace and you should be able to deploy from there w/o making any changes. This approach would be preferable and would have helped you from running into the set of issues that you are seeing.
Let me know if the above makes sense.
Cheers,
Shashi