Professional Documents
Culture Documents
Upgrade DB Training 05-2022 (46) - Read-Only
Upgrade DB Training 05-2022 (46) - Read-Only
and Dynamic
Matthew Watkins
Account Escalations Row Format
Staff Engineer
22 Feb, 2018
• What do we know?
– The 8k rowsize limitation can occur during an record insert, import set, update set or adding a column to a table.
– The error message displays on the console when encountered during data entry in a form.
– For a import, update set and insert of a column, the message can be found in the localhost logs.
- Thenewer Innodb File Format of Barracuda was introduced which supported additional row formats of DYNAMIC and
COMPRESSSED.
(Tables with large BLOB or TEXT columns in particular would benefit from the dynamic row format)
- Prior to Barracuda file formats, there was only COMPACT and REDUNDANT.
- In the Antelope file format, 768 bytes of TEXT values are stored onrow and actually contribute to this limit.
-Tables declared with ROW_FORMAT=DYNAMIC doesn't have this 768-byte problem with TEXT columns. All TEXT data is
stored fully offrow in Barracuda if the field holds more than 256 bytes. Since we use a 3-byte UTF8 character set this means N must
be 86 or higher (256/3 = 85)
*Post DB upgrade it is still possible to hit the dynamic row limit, Simply widening the field’s that are less then Varchar(86) would
resolve the issue.
- The catalog item must be submitted 3 hours prior to the change window time.
- Remember to inform customer that the database upgrade does require a 5-15 minute downtime as the AHA transfer
is performed to repoint the server node.
- What data is needed:
* The Instance name
* The new version of the database (currently, the version being chosen is 10.2.27snc2)
- Parent change
- This occurs 2 hours prior to the change window to allow for the AHA transfer to occur from the Primary
server during the change window time with minimal downtime.
- This occurs at the change window time and after the AHA transfer the Primary Server node becomes the
Secondary Server node and vice versa.
- The new Secondary server node will be upgraded within 48 hours.
- NOTE: In the subsequent change to rebuild the table, ensure that the database you are performing
the rebuild on is the primary server node.
- Perform a /replication.do to validate the DB Server
- The Primary database server node upgrade change (now, secondary server node)
Documents for:
Limits on Table Column Count and Row Size
https://dev.mysql.com/doc/refman/8.0/en/column-count-limit.html
InnoDB Row Formats
https://dev.mysql.com/doc/refman/5.7/en/innodb-row-format.html
Antelope vs Barracuda:
https://bobcares.com/blog/your-database-has-tables-using-antelope-as-the-file-format/