Hi all, I have trouble setting up OTRS 2.0.4 on SuSE Linux Enterprise Server 9 with an DB2 database backend (DB2 8.1.2). When running the script 'otrs-schema.db2.sql' I receive the following response: <quote> CREATE INDEX article_message_37 ON article (a_message_id) SQL0614N The index or index extension "ARTICLE_MESSAGE_37" cannot be created or altered because the combined length of the specified columns is too long. SQLSTATE=54008 <unquote> Obviously DB2 refuses to create the requested index on attribute 'a_message_id', which is of type VARCHAR (3800). The statement does not seem to be correct, since DB2 documentation says: <quote> Explanation: The index could not be created or altered because the sum of the key column internal lengths would exceed 1024... Also, an index cannot be created using a LONG VARCHAR, LONG VARGRAPHIC, or LOB column. If the index is defined on a typed table, there is additional index overhead that reduces the maximum length by 4 bytes. The index may be altered by an ALTER TABLE or ALTER NICKNAME statement that alters the data type of one or more columns. An index extension could not be created because the sum of the columns returned by the GENERATE KEY function would exceed 1024. <unquote> Can this be possibly solved by DB2 configuration means (the manual mentions a 'generate key' function which may be altered)? What might be the consequences (performance) if I do not have an index on this column? BTW, does anybody know why this id column is of type varchar? MOst (but not all) id columns in the DDL are numeric (I did not check the source with regard to the data the column is filled with). I did not see any entry at all in the bugzilla concerning DB2 (that may mean everything's perfect or nobody is using DB2...). Any ideas appreciated. Cheers Tobias -- Tobias Lütticke