[jboss-jira] [JBoss JIRA] Updated: (JBAS-4251) JMS persistance configuration for db2 (db2-jdbc2-service.xml)

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4251?page=all ]

Adrian Brock updated JBAS-4251:
-------------------------------

    Assignee: Rajesh Rajasekaran  (was: Adrian Brock)

I'm not going to do anything with this.

This might be a JBossMQ configuration, but the types of blob DB2 7.2 supports
is not an issue I am going to deal with.

See this for the three possibilities available:
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQJDBC2Persistence

And more importantly the DB2 docs for what they support.

This is not the type of issue that should be raised in JIRA!
Help requests belong in the forums not the release notes.


> JMS persistance configuration for db2 (db2-jdbc2-service.xml)
> -------------------------------------------------------------
>
>                 Key: JBAS-4251
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4251
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>            Reporter: Rajesh Rajasekaran
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.0.GA
>
>
> We need a db2-jdbc2-service.xml to be ship with jboss-4.2.x (and also jboss-4.0.x) to support DB2 databases.
> To start with i copied oracle-jdbc2-service.xml to db2-jdbc2-service.xml and made a few SQL changes.
> 1.) With DB2 all primary keys should be explicitly mentioned NOT NULL
> I added NOT NULL to TXID column.
> CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER NOT NULL, PRIMARY KEY (TXID) )
> WIth this persistance configurations work with DB2 8.0
> 2.) With DB2 7.2 the following query throws an error:
> db2 => CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION))
> DB21034E  The command was processed as an SQL statement because it was not a
> valid Command Line Processor command.  During SQL processing it returned:
> SQL0604N  The length, precision, or scale attribute for column, distinct type,
> structured type, attribute of structured type, function, or type mapping
> "MESSAGEBLOB" is not valid.  SQLSTATE=42611

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira