Installation issues

Situation
Configuring OpenEMR… Connecting to MySQL Server… OK. unable to execute SQL: 'CREATE TABLE history_data ( id bigint(20) NOT NULL auto_increment, coffee longtext, tobacco longtext, alcohol longtext, sleep_patterns longtext, exercise_patterns longtext, seatbelt_use longtext, counseling longtext, hazardous_activities longtext, recreational_drugs longtext, last_breast_exam varchar(255) default NULL, last_mammogram varchar(255) default NULL, last_gynocological_exam varchar(255) default NULL, last_rectal_exam varchar(255) default NULL, last_prostate_exam varchar(255) default NULL, last_physical_exam varchar(255) default NULL, last_sigmoidoscopy_colonoscopy varchar(255) default NULL, last_ecg varchar(255) default NULL, last_cardiac_echo varchar(255) default NULL, last_retinal varchar(255) default NULL, last_fluvax varchar(255) default NULL, last_pneuvax varchar(255) default NULL, last_ldl varchar(255) default NULL, last_hemoglobin varchar(255) default NULL, last_psa varchar(255) default NULL, last_exam_results varchar(255) default NULL, history_mother longtext, dc_mother text, history_father longtext, dc_father text, history_siblings longtext, dc_siblings text, history_offspring longtext, dc_offspring text, history_spouse longtext, dc_spouse text, relatives_cancer longtext, relatives_tuberculosis longtext, relatives_diabetes longtext, relatives_high_blood_pressure longtext, relatives_heart_problems longtext, relatives_stroke longtext, relatives_epilepsy longtext, relatives_mental_illness longtext, relatives_suicide longtext, cataract_surgery datetime default NULL, tonsillectomy datetime default NULL, cholecystestomy datetime default NULL, heart_surgery datetime default NULL, hysterectomy datetime default NULL, hernia_repair datetime default NULL, hip_replacement datetime default NULL, knee_replacement datetime default NULL, appendectomy datetime default NULL, date datetime default NULL, pid bigint(20) NOT NULL default ‘0’, name_1 varchar(255) default NULL, value_1 varchar(255) default NULL, name_2 varchar(255) default NULL, value_2 varchar(255) default NULL, additional_history text, exams text, usertext11 TEXT, usertext12 varchar(255) NOT NULL DEFAULT ‘’, usertext13 varchar(255) NOT NULL DEFAULT ‘’, usertext14 varchar(255) NOT NULL DEFAULT ‘’, usertext15 varchar(255) NOT NULL DEFAULT ‘’, usertext16 varchar(255) NOT NULL DEFAULT ‘’, usertext17 varchar(255) NOT NULL DEFAULT ‘’, usertext18 varchar(255) NOT NULL DEFAULT ‘’, usertext19 varchar(255) NOT NULL DEFAULT ‘’, usertext20 varchar(255) NOT NULL DEFAULT ‘’, usertext21 varchar(255) NOT NULL DEFAULT ‘’, usertext22 varchar(255) NOT NULL DEFAULT ‘’, usertext23 varchar(255) NOT NULL DEFAULT ‘’, usertext24 varchar(255) NOT NULL DEFAULT ‘’, usertext25 varchar(255) NOT NULL DEFAULT ‘’, usertext26 varchar(255) NOT NULL DEFAULT ‘’, usertext27 varchar(255) NOT NULL DEFAULT ‘’, usertext28 varchar(255) NOT NULL DEFAULT ‘’, usertext29 varchar(255) NOT NULL DEFAULT ‘’, usertext30 varchar(255) NOT NULL DEFAULT ‘’, userdate11 date DEFAULT NULL, userdate12 date DEFAULT NULL, userdate13 date DEFAULT NULL, userdate14 date DEFAULT NULL, userdate15 date DEFAULT NULL, userarea11 text, userarea12 text, PRIMARY KEY (id), KEY pid (pid)) ENGINE=InnoDB AUTO_INCREMENT=1 ’ due to: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.

OpenEMR Version
I’m using OpenEMR version

Browser:
I’m using: Firefox

Operating System
I’m using: |cPanel Version|86.0 (build 32)|
| — | — |
|Apache Version|2.4.46|
|PHP Version|5.6.40|
|MySQL Version|10.3.25-MariaDB-log-cll-lve|
|Architecture|x86_64|
|Operating System|linux|

Logs
Did you check the logs? Was there anything pertinent in them? Paste them here (surround with three backticks (```) for readability

As a quick fix for importing you could try editing the MySQL server my.cnf to include
innodb_strict_mode=0
I have seen recently with mysql installed on windows this seems to be a common issue with OpenEMR, this also happened to me.

You can google “Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format”
for further suggestions to try, do make sure you backup my.cnf before applying edits.

2 Likes

Thank you @madmax for your hint:

editing the MySQL server my.cnf to include innodb_strict_mode=0

After updating my.cnf file and restarting the database, it did fix my fatal errors related to the number of tables: “Row size too large” during OpenEMR upgrade from version 6.0 to the latest 6.1.

No table column type alterations were necessary.

Upgrade was completed successfully.

Thanks again Mark!

1 Like