Affects: Release Notes Date of First Response: 2009-08-13 00:09:02 project_key: SOA Incompatible changes are required for the jBPM database schema for both DB2 and for Sybase. For DB2: https://jira.jboss.org/jira/browse/JBPM-2116 https://jira.jboss.org/jira/browse/JBPM-2369 For Sybase: http://www.jboss.org/community/wiki/jBPM32xonSybaseASE15#Lock_scheme
Link: Added: This issue is related to JBPM-2116
Link: Added: This issue is related to JBPM-2369
Note that the incompatibility is with the jBPM database schema that we shipped with GA and with CP01.
This must be noted in the `upgrading' section of the release notes for CP02: The jBPM database schema used by SOA 4.3.0 CP02 is not the same as that used by GA and CP01 when the DB2 or Sybase databases are used. It is not possible to automatically upgrade the schema, so it is recommended that the tables affected are dropped. They will then be automatically recreated when the server is next started. The 32 tables affected are: JBPM_ACTION JBPM_BYTEARRAY JBPM_BYTEBLOCK JBPM_COMMENT JBPM_DECISIONCONDITIONS JBPM_DELEGATION JBPM_EVENT JBPM_EXCEPTIONHANDLER JBPM_ID_GROUP JBPM_ID_MEMBERSHIP JBPM_ID_PERMISSIONS JBPM_ID_USER JBPM_JOB JBPM_LOG JBPM_MODULEDEFINITION JBPM_MODULEINSTANCE JBPM_NODE JBPM_POOLEDACTOR JBPM_PROCESSDEFINITION JBPM_PROCESSINSTANCE JBPM_RUNTIMEACTION JBPM_SWIMLANE JBPM_SWIMLANEINSTANCE JBPM_TASK JBPM_TASKACTORPOOL JBPM_TASKCONTROLLER JBPM_TASKINSTANCE JBPM_TOKEN JBPM_TOKENVARIABLEMAP JBPM_TRANSITION JBPM_VARIABLEACCESS JBPM_VARIABLEINSTANCE
added to upgrade section of 4.3.CP02 release notes: jBPM Database incompatibilities for Sybase and DB2 The jBPM database schema used by JBoss Enterprise SOA Platform 4.3 CP02 introduces several table changes. These changes cannot be applied as an automatic upgrade to a Sybase or DB2 jBPM database used by the 4.3 GA or CP01 releases. If you are using Sybase or DB2 as your jBPM database then you need to drop several tables from your database. You must do this before restarting your server when you upgrade to the CP02 release. These tables will be automatically recreated with the new schema when the server starts for the first time after the upgrade. The 32 tables that are affected by this are listed below. JBPM_ACTION JBPM_BYTEARRAY JBPM_BYTEBLOCK JBPM_COMMENT JBPM_DECISIONCONDITIONS JBPM_DELEGATION JBPM_EVENT JBPM_EXCEPTIONHANDLER JBPM_ID_GROUP JBPM_ID_MEMBERSHIP JBPM_ID_PERMISSIONS JBPM_ID_USER JBPM_JOB JBPM_LOG JBPM_MODULEDEFINITION JBPM_MODULEINSTANCE JBPM_NODE JBPM_POOLEDACTOR JBPM_PROCESSDEFINITION JBPM_PROCESSINSTANCE JBPM_RUNTIMEACTION JBPM_SWIMLANE JBPM_SWIMLANEINSTANCE JBPM_TASK JBPM_TASKACTORPOOL JBPM_TASKCONTROLLER JBPM_TASKINSTANCE JBPM_TOKEN JBPM_TOKENVARIABLEMAP JBPM_TRANSITION JBPM_VARIABLEACCESS JBPM_VARIABLEINSTANCE Additional information regarding DB2 changes: https://jira.jboss.org/jira/browse/JBPM-2116 and https://jira.jboss.org/jira/browse/JBPM-2369. Additional information regarding the Sybase changes: http://www.jboss.org/community/wiki/ jBPM32xonSybaseASE15#Lock_scheme.
Link: Added: This issue is related to SOA-1357
Assigning to me for verification during final doc review for rel notes
* removed Sybase reference * added references to tech preview status updated at: http://downtown.englab.bne.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/SOA_Release_Notes/index.html
Verified in the doc here: http://downtown.englab.bne.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02