RS03543: DC AND RES SCHEMA DO NOT COMPLY WITH MYSQL SERVER ROW SIZE LIMIT

IBM Operational Decision Manager V8.9.2.3 Fix Pack
IBM Operational Decision Manager for z/OS 8.9.2.3 Fix Pack
Operational Decision Manager for z/OS 8.10.2.2 Fix Pack
IBM Operational Decision Manager V8.10.2.2 Fix Pack
IBM Operational Decision Manager V8.10.4 Download Document
IBM Operational Decision Manager V8.10.4 Mod Pack
IBM Operational Decision Manager for z/OS 8.10.4 Mod Pack
Operational Decision Manager V8.9.2.2: Interim Fix 15 for Decision Center

APAR status

• Closed as program error.

Error description

• Customer can't change the character set of the database and
  hence can't store multi-byte characters in their rules at the
  moment. MySQL server has a row size limit of 65535 bytes
  independently of the database engine used
  
  https://dev.mysql.com
  /doc/refman/8.0/en/column-count-limit.html
  
  We have tables that
  have large varchar columns i.e. table activitycomment with
  VARCHAR(10000).
  
  With Latin1 encoding, each character occupies
  1 Byte, but with UTF8 each character occupies 3 Bytes
  
  https://d
  ev.mysql.com/doc/refman/8.0/en/charset-charsets.html
  
  All of
  those VARCHAR columns with the UTF8 encoding exceed the maximum
  row size (i.e. 22095 characters x 3 Bytes = 662895 bytes) that
  can be stored in the table and it is not possible to change the
  encoding to utf8mb4 as this will give an error message.
  

Local fix

• Change the schema by running
  alter table ActivityComment
  modify versioncomment long varchar ;
  alter table
  ActivityComment modify text long varchar ;
  alter table
  ActivityCommentLink modify url long varchar ;
  This will
  preserve the data available in those columns since it does not
  reduce the column size.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users working with MySQL JDBC driver 5.1.16, 5.1.26 and      *
  * older.                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * With MySQL JDBC driver 5.1.16, 5.1.26 and older, the tables  *
  * creation script is generated with LONG VARCHAR columns for   *
  * large string columns.                                        *
  * With MySQL JDBC driver 5.1.38 or 5.1.48 for instance, those  *
  * columns are generated using VARCHAR type. This is an issue   *
  * for ActivityComment table since the record size is quite     *
  * large : 22095 characters. Then when using a database with    *
  * utf8 encoding, this record is 22095 * 3 = 66285 bytes large  *
  * which exceed MySQL limit of 65536 bytes row size limit.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The schema generation has been updated to make sure those large
  columns are stored using LONG VARCHAR type in all cases.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R8A0 PSY

     UP