[
https://jira.jboss.org/jira/browse/JBPM-2477?page=com.atlassian.jira.plug...
]
Joram Barrez commented on JBPM-2477:
------------------------------------
The Oracle database that currently is used in QA is 'Oracle Database 10g Enterprise
Edition Release 10.2.0.4.0 - Production'
That is also the reason why we use the same driver version 'Oracle Database 10g
Release 2 (10.2.0.4) driver'.
The QA integration test suite uses the generated SQL scripts, so this combination is
tested to work.
Possible there is a mismatch in the reporters config (ie 10g database, 11g driver).
This is not a blocking issue, since the DDL generation will proceed if the index already
exists, so it will be reviewed for the 4.2 release.
Problems with indexes in jbpm.history.hbm.xml
---------------------------------------------
Key: JBPM-2477
URL:
https://jira.jboss.org/jira/browse/JBPM-2477
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.0
Environment: Ubuntu 9.04
Oracle JDBC Driver version - "11.1.0.6.0-Production+"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Oracle Database 10g Express Edition Release 10.2.0.1.0
Reporter: Michael Wohlfart
problem with indexes already indexed when running jbpm.oracle.create.sql:
create.jbpm.schema:
[sql] Executing resource:
C:\SEAM\jbpm-4.0\db\schema.scripts\jbpm.oracle.create.sql
[sql] Failed to execute: create index IDX_HDETAIL_HACTI on JBPM4_HIST_DETAIL
(HACTI_)
[sql] java.sql.SQLException: ORA-01408: such column list already indexed
[sql] Failed to execute: create index IDX_HDETAIL_HPROCI on JBPM4_HIST_DETAIL
(HPROCI_)
[sql] java.sql.SQLException: ORA-01408: such column list already indexed
[sql] Failed to execute: create index IDX_HDET_HVAR on JBPM4_HIST_DETAIL (HVAR_)
[sql] java.sql.SQLException: ORA-01408: such column list already indexed
[sql] Failed to execute: create index IDX_HDET_HTASK on JBPM4_HIST_DETAIL
(HTASK_)
[sql] java.sql.SQLException: ORA-01408: such column list already indexed
[sql] 76 of 80 SQL statements executed successfully
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira