It appears from one of the discussions (http://community.jboss.org/message/571322) that the latest human task code has the fixes to run against Oracle database. I downloaded the code from https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/target/jbpm-5.0-SNAPSHOT-pre-bin/https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/target/jbpm-5.0-SNAPSHOT-pre-bin/https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/target/jbpm-5.0-SNAPSHOT-pre-bin/https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/target/jbpm-5.0-SNAPSHOT-pre-bin/ and I still get the same exceptions as mentioned in the earlier discussions (ORA-01747,ORA-00972,ORA-00903 etc) such as long names for tables/coloums etc, see an example below:
2011-01-16 11:39:40,517 (SchemaExport.java:348) ERROR org.hibernate.tool.hbm2ddl.SchemaExport - Unsuccessful: alter table PeopleAssignments_TaskStakeholders add constraint FKE6997FFA2C122ED2 foreign key (entity_id) references OrganizationalEntity
2011-01-16 11:39:40,517 (SchemaExport.java:349) ERROR org.hibernate.tool.hbm2ddl.SchemaExport - ORA-00972: identifier is too long
….
Unsuccessful: drop table Notification_BusinessAdministrators cascade constraints
2011-01-16 11:39:27,173 (SchemaExport.java:363) DEBUG org.hibernate.tool.hbm2ddl.SchemaExport - ORA-00972: identifier is too long
For example, the code https://github.com/krisv/jbpm/blob/f1918a7170baf2193fafbf8d86555558864a4d03/jbpm-human-task/src/main/java/org/jbpm/task/PeopleAssignments.java still shows the long table names.