topic Re: connection settings for oracle user not owning schema in Alfresco Archive

connection settings for oracle user not owning schema

cvillegas — Thu, 15 Sep 2011 06:31:50 GMT

Hi, we want to deploy activiti in a Oracle database in which the application user that connects to the database is not the owner of the schema. Let's say ACT is the user owner of the Activiti tables and ACTAPP is the user that the engine uses to connect to the database (ACTAPP has all the required p

Re: connection settings for oracle user not owning schema

frederikherema1 — Fri, 16 Sep 2011 07:18:49 GMT

A new method has been added to the ManagementService:


/** programmatic schema update on a given connection returning feedback about what happened */
  String databaseSchemaUpgrade(Connection connection, String catalog, String schema);

You can set the database-upgrade property to "none", jobexecutor active by default to false and call this method with a connection that uses the ACT user to create the schema. After that, you can just start the job-executor.

CHeers,
Frederik

Re: connection settings for oracle user not owning schema

fconrady — Tue, 15 Sep 2015 15:57:00 GMT

I have exactly the same question and I don't understand the answer. Is there some way to configure Activiti to use options 2 or 3 pointed out by the OP?

I have tried databaseSchema and databaseTablePrefix without success. Either these are for a different purpose or I am applying them incorrectly.

Thanks
Florian

Re: connection settings for oracle user not owning schema

trademak — Thu, 17 Sep 2015 19:11:41 GMT

Hi Florian,

Can you explain in a bit more detail what exactly you are trying to do with Oracle?

Best regards,

Re: connection settings for oracle user not owning schema

fconrady — Mon, 21 Sep 2015 13:46:58 GMT

Hi Tijs,

I figured it out after inspecting the source code. The forum messages helped, but I did not fully understand it from them.

It works either like this
<blockcode>
                                <property name="databaseSchemaUpdate" value="false" />
                                <property name="databaseTablePrefix" value="<owner>." />
                                <property name="databaseSchema" value="<owner>" />
                                <property name="tablePrefixIsSchema" value="true" />
</blockcode>

or like that
<blockcode>
                                <property name="databaseSchemaUpdate" value="none" />
                                <property name="databaseTablePrefix" value="<owner>." />
</blockcode>
In the second case, when databaseSchemaUpdate is set to something else than “true” or “false”, it does not seem to check the presence and version of tables at all and the value of databaseSchema appears to be irrelevant.

The parameter tablePrefixIsSchema is available since 5.15 and it solves the Oracle-specific issue raised here:

http://forums.activiti.org/content/tables-missing-components-engine-history-identity

With tablePrefixIsSchema set to true one can have the prefix equal to the schema without having to turn off the version checking.

Thanks
Florian