[
https://jira.jboss.org/browse/JBPM-2971?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar commented on JBPM-2971:
----------------------------------------
Actually I had to modify the JbpmSchema tool to deal with Sybase. I have ASE 15.0.3
installed in my workstation. When given a script without any "go" command batch
terminator, the Sybase isql tool parses the statements but never actually executes them.
See
http://www.sybase.com/detail?id=938&contentOnly=true#batch
I figure that script execution via JDBC interprets statements differently. What method
invocation produces the exception you posted?
jBPM Sybase scripts not compatible with Sybase 15.
--------------------------------------------------
Key: JBPM-2971
URL:
https://jira.jboss.org/browse/JBPM-2971
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.9
Environment: SOA 5.1.0 ER3
Based on:
http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/jbpm-3.2-soa
Revision 6764
Reporter: Julian Coleman
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Attachments: jbpm.jpdl.sybase.sql
The Sybase SQL ("jbpm.jpdl.sybase.sql") is not compatible with Sybase ASE 15.
The lines containing "go" are not required and cause errors:
Caused by: com.sybase.jdbc4.jdbc.SybSQLException: Stored procedure 'go' not
found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help
may produce lots of output).
The fix is to remove all lines containing "go" from
"jbpm.jpdl.sybase.sql".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira