Hi,

Where did you find the property "tablePrefixIsSchema" and for what is it used/should it be used?

Cheers,
Thorben

Please check https://jira.codehaus.org/browse/ACT-1940

It is available in the:
http://activiti.org/javadocs/org/activiti/engine/ProcessEngineConfiguration.html

Cheers,
Dimitri

Ok, I updated the bug description accordingly.

Thanks for reporting.

Thanks a lot.

Please keep in mind, that currently the workaround <property name="databaseSchemaUpdate" value="none" /> has to be used in order to assure, that the engine can start. This is a workaround and is not documented.

The situation occurs in cases where oracle is used, and you access the DB from the web application using e.g. APP_USER while the tables are created in the ADMIN_USER. This is usually done to implement security reducing the permissions for the APP_USER to the minimum.

Having
<property name="databaseSchema" value="ADMIN_USER" />
<property name="databaseTablePrefix" value="ADMIN_USER." />
<property name="databaseSchemaUpdate" value="false" />

does not solve the issue, because the version check is performed during the engine startup (spring initialization) and the table with the version cannot be found.

This post can also be helpful http://forums.activiti.org/content/tables-missing-components-engine-history-identity

Hi Bernd,

The fix was to separate cases when determining the actual name of the table to be checked for presence.

Cases:
1)

• databaseSchema: MY_SCHEMA
• databaseTablePrefix: null
• => plain table name is used

2)

• databaseSchema: MY_SCHEMA
• databaseTablePrefix: MY_PREFIX_
• => MY_PREFIX_ + plain table name is used

3)

• databaseSchema: MY_SCHEMA
• databaseTablePrefix: MY_SCHEMA.
• => plain table name is used

4)

• databaseSchema: MY_SCHEMA
• databaseTablePrefix: MY_SCHEMA.MY_PREFIX_
• => MY_PREFIX_ + plain table name is used

The fix assumes that in the databaseTablePrefix property, a schema is separated from the rest of the prefix by a dot.

Cheers,
Thorben