Jump to content


Photo

USING BTREE;. The error message given was: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large.


  • Please log in to reply
1 reply to this topic

#1 spazio

spazio

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 23 December 2018 - 08:17 AM

Hi All,

 

I'm trying to Update X2Engine to 7.0 from 6.9.3 with the webGui

The host is a dedicated debian stretch lamp server with standard configs for Vhosting

 

In the update process. These come up with a green check

Obtain and check data
Review and confirm changes
Download package
Extract package
Verify package contents
 
But when applying changes it return an error. this one return a red X
Apply changes
 
Here is the error:
 
Exception: "A database change failed to apply: ALTER TABLE `x2_accounts` ADD COLUMN `firstName` varchar(255) NULL AFTER `nameId`, ADD COLUMN `lastName` varchar(255) NULL AFTER `firstName`, ADD COLUMN `title` varchar(100) NULL AFTER `type`, ADD COLUMN `phone2` varchar(40) NULL AFTER `phone`, ADD COLUMN `email` varchar(250) NULL AFTER `phone2`, ADD COLUMN `twitter` varchar(50) NULL AFTER `email`, ADD COLUMN `linkedin` varchar(100) NULL AFTER `twitter`, ADD COLUMN `skype` varchar(32) NULL AFTER `linkedin`, ADD COLUMN `googleplus` varchar(100) NULL AFTER `skype`, ADD COLUMN `otherUrl` varchar(100) NULL AFTER `googleplus`, ADD COLUMN `company` varchar(250) NULL AFTER `otherUrl`, ADD COLUMN `modelName` varchar(100) NOT NULL AFTER `company`, ADD COLUMN `address2` varchar(250) NULL AFTER `address`, ADD COLUMN `backgroundInfo` text NULL AFTER `zipcode`, ADD COLUMN `priority` varchar(40) NULL AFTER `backgroundInfo`, ADD COLUMN `facebook` varchar(100) NULL AFTER `createDate`, ADD COLUMN `timezone` varchar(250) NULL AFTER `facebook`, ADD COLUMN `trackingKey` varchar(32) NULL AFTER `dupeCheck`, ADD COLUMN `doNotCall` tinyint(4) NULL DEFAULT '0' AFTER `expectedCloseDate`, ADD COLUMN `doNotEmail` tinyint(4) NULL DEFAULT '0' AFTER `doNotCall`, ADD INDEX `company` (`company`) USING BTREE;. The error message given was: 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
A database change failed to apply: ALTER TABLE `x2_accounts` ADD COLUMN `firstName` varchar(255) NULL AFTER `nameId`, ADD COLUMN `lastName` varchar(255) NULL AFTER `firstName`, ADD COLUMN `title` varchar(100) NULL AFTER `type`, ADD COLUMN `phone2` varchar(40) NULL AFTER `phone`, ADD COLUMN `email` varchar(250) NULL AFTER `phone2`, ADD COLUMN `twitter` varchar(50) NULL AFTER `email`, ADD COLUMN `linkedin` varchar(100) NULL AFTER `twitter`, ADD COLUMN `skype` varchar(32) NULL AFTER `linkedin`, ADD COLUMN `googleplus` varchar(100) NULL AFTER `skype`, ADD COLUMN `otherUrl` varchar(100) NULL AFTER `googleplus`, ADD COLUMN `company` varchar(250) NULL AFTER `otherUrl`, ADD COLUMN `modelName` varchar(100) NOT NULL AFTER `company`, ADD COLUMN `address2` varchar(250) NULL AFTER `address`, ADD COLUMN `backgroundInfo` text NULL AFTER `zipcode`, ADD COLUMN `priority` varchar(40) NULL AFTER `backgroundInfo`, ADD COLUMN `facebook` varchar(100) NULL AFTER `createDate`, ADD COLUMN `timezone` varchar(250) NULL AFTER `facebook`, ADD COLUMN `trackingKey` varchar(32) NULL AFTER `dupeCheck`, ADD COLUMN `doNotCall` tinyint(4) NULL DEFAULT '0' AFTER `expectedCloseDate`, ADD COLUMN `doNotEmail` tinyint(4) NULL DEFAULT '0' AFTER `doNotCall`, ADD INDEX `company` (`company`) USING BTREE;. The error message given was: 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<br />To restore the database to its previous state, use the database dump file update_backup.sql stored in protected/data<br /><br />Update failed.

Update failed." in /var/www/clients/client11/web158/web/protected/components/UpdaterBehavior.php L2226
 
After searching. I came up only with a bug post from 2012 so, I guess it something else.
Any thoughts on this error?
 
Thanks
Spazio
 


#2 X2Josef

X2Josef

    Member

  • Moderators
  • 18 posts

Posted 04 January 2019 - 10:33 AM

At this point of the installation check if the 'x2_accounts' table has already been created with its fields. If it has, its possible you might be able to skip this query and continue on with the installation






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users