CSP-1262.

      Set the default lengths of clob columns in all hbm.xml files.

            [CONFSERVER-3979] DB2 clob columns default to 255.

            Can someone please let us know exactly where to update the PAGETEMPLATE.CONTENT setting and provide an example of it? Thanks in advance.

            Karamjit Kang added a comment - Can someone please let us know exactly where to update the PAGETEMPLATE.CONTENT setting and provide an example of it? Thanks in advance.

            More information about the actual error message:

            SQL0302N The value of a host variable in the EXECUTE or OPEN statement is
            too large for its corresponding use.

            Explanation: The value of an input host variable was found to be too large
            for its use in the SELECT, VALUES, or prepared statement. One of the
            following occurred:

            The corresponding host variable or parameter marker used in the SQL
            statement is defined as string, but the input host variable contains a
            string that is too long.
            The corresponding host variable or parameter marker used in the SQL
            statement is defined as numeric, but the input host variable contains a
            numeric value that is too large.
            The terminating NUL character is missing from the C language NUL-terminated
            character string host variable.
            Federated system users: in a pass-through session, a data source-specific
            restriction might have been violated.
            This error occurs as a result of specifying either an incorrect host
            variable or an incorrect SQLLEN value in an SQLDA on an EXECUTE or OPEN
            statement.

            The statement cannot be processed.

            User Response: Ensure that the input host variable value is the correct type
            and length. If the input host variables supply values to parameter markers,
            match values with the implied data type and length of the parameter marker.

            Federated system users: for a pass-through session, determine what data
            source is causing the error (see the problem determination guide for
            procedures to follow to identify the failing data source). Examine the SQL
            dialect for that data source to determine which specific restriction has
            been violated, and adjust the failing statement as needed.

            Daniel Ostermeier added a comment - More information about the actual error message: SQL0302N The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use. Explanation: The value of an input host variable was found to be too large for its use in the SELECT, VALUES, or prepared statement. One of the following occurred: The corresponding host variable or parameter marker used in the SQL statement is defined as string, but the input host variable contains a string that is too long. The corresponding host variable or parameter marker used in the SQL statement is defined as numeric, but the input host variable contains a numeric value that is too large. The terminating NUL character is missing from the C language NUL-terminated character string host variable. Federated system users: in a pass-through session, a data source-specific restriction might have been violated. This error occurs as a result of specifying either an incorrect host variable or an incorrect SQLLEN value in an SQLDA on an EXECUTE or OPEN statement. The statement cannot be processed. User Response: Ensure that the input host variable value is the correct type and length. If the input host variables supply values to parameter markers, match values with the implied data type and length of the parameter marker. Federated system users: for a pass-through session, determine what data source is causing the error (see the problem determination guide for procedures to follow to identify the failing data source). Examine the SQL dialect for that data source to determine which specific restriction has been violated, and adjust the failing statement as needed.

            This issue can be manually resolved by increasing the size of the PAGETEMPLATE.CONTENT column from 255 to 10000.

            Daniel Ostermeier added a comment - This issue can be manually resolved by increasing the size of the PAGETEMPLATE.CONTENT column from 255 to 10000.

            [12/7/05 10:48:22:071 GMT-05:00] 00000041 SessionImpl E net.sf.hibernate.impl.SessionImpl execute Could not synchronize database state with session
            [12/7/05 10:48:22:074 GMT-05:00] 00000041 SQLStateSQLEx I org.springframework.jdbc.support.SQLStateSQLExceptionTranslator translate Translating SQLException with SQLState '22001' and errorCode '-302' and message [The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use.]; SQL was [] for task [HibernateTemplate]
            [12/7/05 10:48:22:079 GMT-05:00] 00000041 SystemOut O 2005-12-07 10:48:22,078 ERROR [atlassian.confluence.util.XWorkTransactionInterceptor] Invoking rollback for transaction on action '/pages/templates/doeditpagetemplate.action (EditPageTemplateAction.doEdit())' due to throwable: org.springframework.dao.DataIntegrityViolationException: (HibernateTemplate): data integrity violated by SQL ''; nested exception is com.ibm.db2.jcc.b.SqlException: The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use.
            org.springframework.dao.DataIntegrityViolationException: (HibernateTemplate): data integrity violated by SQL ''; nested exception is com.ibm.db2.jcc.b.SqlException: The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use.
            com.ibm.db2.jcc.b.SqlException: The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use.
            at com.ibm.db2.jcc.b.zc.d(zc.java(Compiled Code))
            at com.ibm.db2.jcc.a.db.l(db.java(Compiled Code))
            at com.ibm.db2.jcc.a.db.a(db.java(Compiled Code))
            at com.ibm.db2.jcc.a.r.a(r.java(Inlined Compiled Code))
            at com.ibm.db2.jcc.a.tb.c(tb.java(Compiled Code))
            at com.ibm.db2.jcc.b.ad.Z(ad.java(Inlined Compiled Code))
            at com.ibm.db2.jcc.b.ad.d(ad.java(Compiled Code))
            at com.ibm.db2.jcc.b.ad.V(ad.java(Compiled Code))

            Daniel Ostermeier added a comment - [12/7/05 10:48:22:071 GMT-05:00] 00000041 SessionImpl E net.sf.hibernate.impl.SessionImpl execute Could not synchronize database state with session [12/7/05 10:48:22:074 GMT-05:00] 00000041 SQLStateSQLEx I org.springframework.jdbc.support.SQLStateSQLExceptionTranslator translate Translating SQLException with SQLState '22001' and errorCode '-302' and message [The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use.] ; SQL was [] for task [HibernateTemplate] [12/7/05 10:48:22:079 GMT-05:00] 00000041 SystemOut O 2005-12-07 10:48:22,078 ERROR [atlassian.confluence.util.XWorkTransactionInterceptor] Invoking rollback for transaction on action '/pages/templates/doeditpagetemplate.action (EditPageTemplateAction.doEdit())' due to throwable: org.springframework.dao.DataIntegrityViolationException: (HibernateTemplate): data integrity violated by SQL ''; nested exception is com.ibm.db2.jcc.b.SqlException: The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use. org.springframework.dao.DataIntegrityViolationException: (HibernateTemplate): data integrity violated by SQL ''; nested exception is com.ibm.db2.jcc.b.SqlException: The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use. com.ibm.db2.jcc.b.SqlException: The value of a host variable in the EXECUTE or OPEN statement is too large for its corresponding use. at com.ibm.db2.jcc.b.zc.d(zc.java(Compiled Code)) at com.ibm.db2.jcc.a.db.l(db.java(Compiled Code)) at com.ibm.db2.jcc.a.db.a(db.java(Compiled Code)) at com.ibm.db2.jcc.a.r.a(r.java(Inlined Compiled Code)) at com.ibm.db2.jcc.a.tb.c(tb.java(Compiled Code)) at com.ibm.db2.jcc.b.ad.Z(ad.java(Inlined Compiled Code)) at com.ibm.db2.jcc.b.ad.d(ad.java(Compiled Code)) at com.ibm.db2.jcc.b.ad.V(ad.java(Compiled Code))

              Unassigned Unassigned
              8873c89cc788 Daniel Ostermeier
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: