Description of problem:

• The currently available "jbpm-6.1-to-6.2.sql" and "jbpm-6.0-to-6.1.sql" DB upgrade scripts [1][2] do not contain the necessary "ALTER" statement to update an existing database schema with the newly added "owner_id" column from "ContextMappingInfo" table, introduced in jBPM6.1 .
• We already ship these scripts with BPMS 6.1.0 source code but they are missing the necessary SQL statement to allow customers to manually update an existing "ContextMappingInfo" table from BPMS 6.0.3 to be upgraded to be compatible with BPMS 6.1.0 updated schema.

[1] ./jbpm-6.2.0.Final-redhat-4/jbpm-installer/db/upgrade-scripts/jbpm-6.1-to-6.2.sql
[2] ./jbpm-6.2.0.Final-redhat-4/jbpm-installer/db/upgrade-scripts/jbpm-6.0-to-6.1.sql

Version-Release number of selected component (if applicable):

• BPMS 6.1.0

How reproducible:

• Always

Steps to Reproduce:
1. Check the SQL scripts from BPMS 6.1.0 source code as shown above.
2.
3.

Actual results:

• Scripts missing ALTER statements for ContextMappingInfo.owner_id table column.

Expected results:

• The necessary SQL statement should be there for ContextMappingInfo.owner_id table column.

Additional info:

• Nothing