Confluence Docs 3.0 : Known Issues for DB2
This page last changed on Sep 25, 2008 by rhartono.
On this page:
DB2 Does Not Support Unicode Character By DefaultTo support the Unicode character set, create your database like this: db2 create database <name> using codeset utf-8 territory us pagesize 8 k Before 8.2.2 db2 create database <name> using codeset utf-8 territory us db2 drop tablespace userspace1 db2 create bufferpool bufpool8k <number of pages> pagesize 8 k db2 create tablespace userspace1 pagesize 8 k managed by database using \(file \'<location>\' <number of pages>\) bufferpool bufpool8k The territory may not be important when using UTF-8, but it must be included. DB2 Does Not Support Transaction Logging Of BLOBs Larger Than 1GB
<property name="body" type="com.atlassian.confluence.core.persistence.hibernate.CustomClobType" update="true" insert="true" column="BODY" length="1073741824" /> Configuring Database Character EncodingRefer to Configuring Database Character Encoding. DB2 Dialect class change (if upgrading from Confluence version 2.2 or older)If you are using DB2, and are upgrading Confluence from version 2.2 or older, the 'hibernate.dialect' property in the confluence.cfg.xml file needs to be changed to 'com.atlassian.hibernate.dialect.DB2Dialect' like so:
<property name="hibernate.dialect">com.atlassian.hibernate.dialect.DB2Dialect</property>
Encoding Test ProblemsAt the time of writing this, there is an open bug with the encoding test when using DB2. Details are here: CONF-8588. Transaction Isolation Level of Read UncommittedDue to CONF-9323, DB2 requires a transaction isolation level of "read uncommitted" to avoid occasional deadlocks. The more concurrent usage a Confluence instance experiences, the higher the frequency of deadlocks with a transaction isolation level higher than "read uncommitted". Set the following property in the confluence.cfg.xml file. <property name="hibernate.connection.isolation">1</property> Incompatible Data Types on z/OS 8There are problems when running DB2 on z/OS 8 and 9. This platform is not officially supported but there is an unsupported workaround here. SQLCODE: -443, SQLSTATE: 38553, SQLERRMC: SYSIBM.SQLTABLES;TABLES;SYSIBM:CLI:-805Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -443, SQLSTATE: 38553, SQLERRMC: SYSIBM.SQLTABLES;TABLES;SYSIBM:CLI:-805 at com.ibm.db2.jcc.b.hh.b(hh.java:1369) at com.ibm.db2.jcc.b.hh.c(hh.java:1356) at com.ibm.db2.jcc.c.db.k(db.java:352) at com.ibm.db2.jcc.c.db.e(db.java:96) at com.ibm.db2.jcc.c.t.e(t.java:83) at com.ibm.db2.jcc.c.sb.h(sb.java:167) at com.ibm.db2.jcc.b.hh.q(hh.java:1329) at com.ibm.db2.jcc.b.ih.d(ih.java:2529) at com.ibm.db2.jcc.b.jh.V(jh.java:146) at com.ibm.db2.jcc.b.fb.a(fb.java:7374) at com.ibm.db2.jcc.b.fb.a(fb.java:5997) at com.ibm.db2.jcc.b.fb.getTables(fb.java:5908) at com.mchange.v2.c3p0.impl.NewProxyDatabaseMetaData.getTables(NewProxyDatabaseMetaData.java:2828) at net.sf.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:54) ... 23 more You might encounter this problem after an upgrade to UDB Version 8.1 FixPak 10 (also known as Version 8.2 FixPak 3) when invoking a DB2 Call Level Interface (CLI) catalog function. The solution to this is to perform a rebind of the db2schema.bnd file locally against each database. Refer to the IBM Technote FAQ for more instruction. RELATED TOPICS |
![]() |
Document generated by Confluence on Nov 05, 2009 23:34 |