Based on the SQLCODE, it looks like the table USER in schema DBSCHEMA does not exist. Is that table located in a different schema than the default? If so, you have a few options - specify the schema on the @Table annotation, use the openjpa.jdbc.Schema property, or depending on the driver and platform, specify a different default schema on the connection URL[2]. Or, if possible, define the table in DBSSCHEMA.
[1] http://openjpa.apache.org/builds/latest/docs/manual/ref_guide_schema_def.html [2] http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.apdv.java.doc/doc/cjvcfgpr.htm -Jeremy On Tue, Jun 7, 2011 at 6:45 PM, Pinaki Poddar <[email protected]> wrote: > Right now I do not have a computing environment to give you a definite > answer. But if you do not mind, please try passing a Long (not long). > > Why did you think that the application connects to multiple DBs could be > relevant in this context? > Given rather straightforward nature of the use case, I am thinking whether > something else is causing the reported failure. > > ----- > Pinaki > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/may-be-OpenJPA-limitation-tp6450246p6451867.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
