svn commit: r682478 - /openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml

[al...@apache.org]

Author: allee8285
Date: Mon Aug  4 12:45:12 2008
New Revision: 682478

URL: http://svn.apache.org/viewvc?rev=682478&view=rev
Log:
OPENJPA-663 - Commit manual changes submitted by Jeremy Bauer.

Modified:
    openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml

Modified: openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml
URL: http://svn.apache.org/viewvc/openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml?rev=682478&r1=682477&r2=682478&view=diff
==============================================================================
--- openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml (original)
+++ openjpa/trunk/openjpa-project/src/doc/manual/supported_databases.xml Mon Aug  4 12:45:12 2008
@@ -429,6 +429,20 @@
 extending <classname>DB2Dictionary</classname>.
                     </para>
                 </listitem>
+                <listitem>
+                    <para>
+Explicit creation of indexes specified by the OpenJPA @Index annotation will 
+fail on DB2 for iSeries if the default schema used by the JDBC driver does not 
+exist.  If a default schema is not specified on the connection, the iSeries 
+will default to the user profile name.  If a schema of that name does not 
+exist, DB2 on iSeries will not create the schema, resulting in a failure when 
+creating the index.  The failure message will look similar to: "[SQL0204] 
+USERNAME in QSYS type *LIB not found."  To work around this issue, specify a 
+default schema on the JDBC URL or data source property and make sure that 
+schema exists or create a schema which matches the user profile of the 
+connection.
+                    </para>
+                </listitem>
             </itemizedlist>
         </section>
     </section>