[jboss-jira] [JBoss JIRA] Closed: (JBAS-4240) SQL error in uuid-key-generator.sar jboss-service.xml against DB2 7.2

SQL error in uuid-key-generator.sar jboss-service.xml against DB2 7.2 --------------------------------------------------------------------- Key: JBAS-4240 URL: http://jira.jboss.com/jira/browse/JBAS-4240 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Rajesh Rajasekaran Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 The spaces at the end of each line of the SQL doesn not work with DB2 7.2 <!-- Create table DDL --> <attribute name="CreateTableDdl"> create table HILOSEQUENCES ( SEQUENCENAME varchar(50) not null, HIGHVALUES integer not null, constraint hilo_pk primary key (SEQUENCENAME) ) </attribute> The following error occurs on server startup: 2007-03-23 14:34:47,234 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Executing DDL: create table HILOSEQUENCES ( SEQUENCENAME varchar(50) not null, HIGHVALUES integer not null, constraint hilo_pk primary key (SEQUENCENAME) ) 2007-03-23 14:34:47,437 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting failed jboss:service=KeyGeneratorFactory,type=HiLo com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -7, SQLSTATE: 42601, SQLERRMC: ;able HILOSEQUENCES ( at com.ibm.db2.jcc.c.fg.e(fg.java:1596) at com.ibm.db2.jcc.c.fg.b(fg.java:1160) at com.ibm.db2.jcc.b.gb.h(gb.java:217) at com.ibm.db2.jcc.b.gb.b(gb.java:46) at com.ibm.db2.jcc.b.w.b(w.java:40) at com.ibm.db2.jcc.b.vb.f(vb.java:118) at com.ibm.db2.jcc.c.fg.m(fg.java:1155) Going through the db2 reference says: db2 => ? sql0007 SQL0007N The character "<character>" following "<text>" is not valid. Explanation: The specified "<character>" is not a valid character in SQL statements. The "<text>" field indicates the 20 characters of the SQL statement that preceded the character that is not valid. Hence I am wrapping up the SQL in a single line. However this problem does not exist with DB2 8.0