News:

SMF 2.1.4 has been released! Take it for a spin! Read more.

Main Menu

2.0 upgrades fail

Started by Sir Osis of Liver, May 12, 2019, 12:31:29 AM

Previous topic - Next topic

Sir Osis of Liver

Trying to upgrade two old 1.1.11 databases (Jan 2012) to 2.0.15.  Neither dump would import on my server, getting TYPE=MyISAM error.  Changed all TYPE=MyISAM; to ENGINE=MyISAM DEFAULT CHARSET=latin1;, imported both dumps successfully, running in 1.1.11, upgraded normally to 1.1.21, working fine.  Cannot get 2.0.15 upgrade to complete on either one. It starts, gets anywhere from 14% to 49%, then stalls.  No script errors, no server errors.  Small databases, 30mb and 12mb.  Host support is not seeing anything on their end.  Best guess is there's something in the dumps that's choking the upgrade, but haven't been able to find it.  There's no information in the headers re: original server config.  Only odd things I see is when I dump the upgraded 1.1.21 databases off my server, phpmyadmin is running in php 7.2.7, my account is set for 5.6, and the table structures in the original databases are different from 1.1.21 upgraded -

Original 1.1.11 -



CREATE TABLE `smf_boards` (
  ID_BOARD smallint(5) unsigned NOT NULL auto_increment,
  ID_CAT tinyint(4) unsigned NOT NULL default 0,
  childLevel tinyint(4) unsigned NOT NULL default 0,
  ID_PARENT smallint(5) unsigned NOT NULL default 0,
  boardOrder smallint(5) NOT NULL default 0,
  ID_LAST_MSG int(10) unsigned NOT NULL default 0,
  ID_MSG_UPDATED int(10) unsigned NOT NULL default 0,
  lastUpdated int(11) unsigned NOT NULL default 0,
  memberGroups varchar(128) NOT NULL default '-1,0',
  name tinytext NOT NULL,
  description text NOT NULL,
  numTopics mediumint(8) unsigned NOT NULL default 0,
  numPosts mediumint(8) unsigned NOT NULL default 0,
  countPosts tinyint(4) NOT NULL default 0,
  ID_THEME tinyint(4) unsigned NOT NULL default 0,
  permission_mode tinyint(4) unsigned NOT NULL default 0,
  override_theme tinyint(4) unsigned NOT NULL default 0,
  PRIMARY KEY (ID_BOARD),
  UNIQUE categories (ID_CAT, ID_BOARD),
  UNIQUE children (childLevel, ID_PARENT, boardOrder, ID_BOARD),
  KEY ID_PARENT (ID_PARENT),
  KEY ID_MSG_UPDATED (ID_MSG_UPDATED)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;



Upgraded 1.1.21 -



CREATE TABLE `smf_boards` (
  `ID_BOARD` smallint(5) UNSIGNED NOT NULL,
  `ID_CAT` tinyint(4) UNSIGNED NOT NULL DEFAULT '0',
  `childLevel` tinyint(4) UNSIGNED NOT NULL DEFAULT '0',
  `ID_PARENT` smallint(5) UNSIGNED NOT NULL DEFAULT '0',
  `boardOrder` smallint(5) NOT NULL DEFAULT '0',
  `ID_LAST_MSG` int(10) UNSIGNED NOT NULL DEFAULT '0',
  `ID_MSG_UPDATED` int(10) UNSIGNED NOT NULL DEFAULT '0',
  `lastUpdated` int(11) UNSIGNED NOT NULL DEFAULT '0',
  `memberGroups` varchar(128) NOT NULL DEFAULT '-1,0',
  `name` tinytext NOT NULL,
  `description` text NOT NULL,
  `numTopics` mediumint(8) UNSIGNED NOT NULL DEFAULT '0',
  `numPosts` mediumint(8) UNSIGNED NOT NULL DEFAULT '0',
  `countPosts` tinyint(4) NOT NULL DEFAULT '0',
  `ID_THEME` tinyint(4) UNSIGNED NOT NULL DEFAULT '0',
  `permission_mode` tinyint(4) UNSIGNED NOT NULL DEFAULT '0',
  `override_theme` tinyint(4) UNSIGNED NOT NULL DEFAULT '0'
) ENGINE=MyISAM DEFAULT CHARSET=latin1;



The latter is the same in clean 1.1.21 install.  Can probably rebuild the databases manually by copying data dumps into clean db, but that's more work than I'd like to put into this. :P 
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

Advertisement: