Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

92 Error during upd...
 
Notifications
Clear all

92 Error during updrade to 10.0.2

12 Posts
3 Users
0 Reactions
3,938 Views
(@ganeshkandu)
Posts: 7
Active Member
Topic starter
 
[#8374]

Hi,

i was trying to install projeqtor 10.0.2 while installing i found issue,

Exception-[42000] SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

After debug i found database table CHARSET and COLLATE are changes to utf8mb4

there are some tables who have varchar columns with 4000 length those columns are causing this issue.

when i am trying with utf8 it working and causing error when its utf8mb4

CREATE TABLE `prepq_issue` (
`id` int(12) unsigned NOT NULL AUTO_INCREMENT,
`idProject` int(12) unsigned DEFAULT NULL,
`name` varchar(100) DEFAULT NULL,
`description` varchar(4000) DEFAULT NULL,
`idIssueType` int(12) unsigned DEFAULT NULL,
`cause` varchar(4000) DEFAULT NULL,
`impact` varchar(4000) DEFAULT NULL,
`idPriority` int(12) unsigned DEFAULT NULL,
`creationDate` date DEFAULT NULL,
`idUser` int(12) unsigned DEFAULT NULL,
`idStatus` int(12) unsigned DEFAULT NULL,
`idResource` int(12) unsigned DEFAULT NULL,
`initialEndDate` date DEFAULT NULL,
`actualEndDate` date DEFAULT NULL,
`closureDate` date DEFAULT NULL,
`result` varchar(4000) DEFAULT NULL,
`comment` varchar(4000) DEFAULT NULL,
`idle` int(1) unsigned DEFAULT '0',
PRIMARY KEY (`id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 COLLATE utf8_general_ci ;

I think you should use small number for those varchars.present in opportunity, risk, issue  tables.

 


 
Posted : 22 Jul 2022 15H05
(@babynus)
Posts: 14952
Member Admin
 

Error message is wrongRow size too large.

The maximum row size for the used table type, not counting BLOBs, is 65535

But 4000 x 4 = 16000 < 65535
MySql parameter must be adapted :

innodb_default_row_format=dynamic

(this is a prerequisite to projeqtor installation)


 
Posted : 22 Jul 2022 16H16
(@gauvain)
Posts: 10
Active Member
 

Hello,

For information, the MariaDB config you ask for is the default value since 10.2.2 ( https://mariadb.com/kb/en/innodb-system-variables/#innodb_default_row_format).

But I still have tried to set this parameter to MariaDB and I get the same errrors.

Regards,


 
Posted : 25 Jul 2022 0H08
(@ganeshkandu)
Posts: 7
Active Member
Topic starter
 

Hi,

I tried to do what you suggested but i wasn't able to do
i got this error

#1193 - Unknown system variable 'innodb_default_row_format'

This is because "innodb_default_row_format" variable was Introduced in version 5.7.9 of MySQL, ( https://dev.mysql.com/doc/mysqld-version-reference/en/optvar-changes-5-7.html ) its not there in MySQL 5.6

And according to Compatibility Matrix projeqtor works on MySQL 5.6 ( https://www.projeqtor.org/en/product-en/technical-en/64-setup-en/412-product-prerequisites-en )

its also not working on Barracuda format of mysql 5.6.


 
Posted : 25 Jul 2022 13H23
(@ganeshkandu)
Posts: 7
Active Member
Topic starter
 

Setting innodb_default_row_format to dynamic also not working on MySQL 5.7.37

65535 is a total size of all fields of table excluding BLOB and TEXT ( https://dev.mysql.com/doc/mysql-reslimits-excerpt/5.6/en/column-count-limit.html )

But 4000 x 4 = 16000 65535


 
Posted : 25 Jul 2022 13H46
(@babynus)
Posts: 14952
Member Admin
 

Hi, 

This issue may occur on older version of MySql (I did not test).
To avoid the issue : install V9.5.5, then migrate to V10.0.2


 
Posted : 25 Jul 2022 15H57
(@ganeshkandu)
Posts: 7
Active Member
Topic starter
 

I tested it on 8.0.28
i am getting same issue on latest MySQL too.


 
Posted : 25 Jul 2022 16H17
(@ganeshkandu)
Posts: 7
Active Member
Topic starter
 

I tested this on 8.0.28
i am getting same issue on latest MySQL too.


 
Posted : 25 Jul 2022 16H19
(@babynus)
Posts: 14952
Member Admin
 

Issue will be fixed on V10.0.3.
Workaround : 
 - install V9.5.5
- migrate to V10.0.2


 
Posted : 26 Jul 2022 11H30
(@ganeshkandu)
Posts: 7
Active Member
Topic starter
 

Can you provide a fix in current release ? or what changes we can make it to work ?
so that we can change accordingly and install 10.0.2.


 
Posted : 03 Aug 2022 11H19
(@babynus)
Posts: 14952
Member Admin
 

Have a look at news...


 
Posted : 03 Aug 2022 11H33
(@ganeshkandu)
Posts: 7
Active Member
Topic starter
 

Thanks !


 
Posted : 03 Aug 2022 11H36
Share:

Scroll to Top