Red Hat Bugzilla – Bug 1009443
Quartz DDL for Oracle DB execution ends with error message: ORA-00942 table or view does not exist
Last modified: 2014-08-06 16:08:17 EDT
Description of problem: Quartz DDL for Oracle (Supplementary tools) starts with delete and drop statements without checking existence of tables being deleted/dropped => this results in error message stated in the summary. Version-Release number of selected component (if applicable): BRMS/BPMS 6.0.0.ER3
PostgreSQL shows very similar error message, the reason is probably the same - DDL script starts with DROP table commands without any checking. On the other hand, script for DB2 does not drop any table. Would it be possible to unite this behaviour of DDL scripts for all supported DBs ?
removed all drop/delete statements from DDL scripts as they are intended to be used to create new schemas and drop/delete might impose a risk of accidentally removing valid data. jbpm master: https://github.com/droolsjbpm/jbpm/commit/8d42d2872e9984ff5ad7c922bd501341d9f28105 6.0.x https://github.com/droolsjbpm/jbpm/commit/8ec9469691980e4efc4e02e4505f17a44fbb54ad
I cannot see any change here: dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.0-ER5/jboss-bpms-brms-6.0.0-redhat-5-supplementary-tools.zip DDL scripts still contain delete/drop statements, I am afraid the commits Maciej stated in comment 3 didn't get into the supplementary tools.
reassigning to Ryan as it's available in the source so it's just matter of moving that into right location on product side. please also include following bz that fixes invalid column names in some of the tables: https://bugzilla.redhat.com/show_bug.cgi?id=1035901
Yes, product doesn't use the installer in community. Ok, I will fix this in ER6.
Fixed in http://git.app.eng.bos.redhat.com/ip.git/commit/?id=c590ab2e68f0e8e1acba509b7f15a46cdde2611d
Verified on BPMS-6.0.0.ER7