The changes I made for Oracle were:
1. Add ojdbc5 11.1.0.7.0 to classpath
2. Change the hibernate.dialect in persistence.xml to
org.hibernate.dialect.Oracle9Dialect
3. Use oracle.jdbc.xa.client.OracleXADataSource for the PoolingDataSource
class name
The tables will be created depending on how you have persistence.xml
configured (I used hibernate.hbm2ddl.auto value 'create')
However, I did experience a problem with the eventTypes member of
ProcessInstanceInfo:
'create table ProcessInstanceInfo_eventTypes' yields the error 'ORA-00972:
identifier is too long'.
The team is aware of this but I haven't seen a fix yet.
Hope this helps.
ramram wrote:
Hi All,
I have been using the H2 in memory database to test all my Drools Flow
scenarios using Guvnor and Gwt Console provided. And I have some questions
to ask and was wondering if someone can help. The main plan now is to
switch
from using the H2 in memory database to Persist using the Oracle database.
1- What are the files that should be affected in this switch? or where
should I be looking into?
2- Are the tables created dynamically? and under which schema?
3- is there any test case implemented using this technology?
Thnx in advance for your help
Regards,
Ram
--
View this message in context:
http://n3.nabble.com/Persistence-issue-using-Oracle-tp417257p422087.html
Sent from the Drools - User mailing list archive at
Nabble.com.