hey all-

I had a failed database upgrade moving from 4.6.6 to 4.6.8 on my way to 7.X.

Can someone tell me the steps I supposed to take. What is meant by manually update the dbase? Do I clear the whole table and reinsert it?

Can I revert the update?

here is my failure:

2005-03-03

2005-03-18

ALTER TABLE {poll} CHANGE voters polled longtext 
FAILED

2005-03-21

ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid) 
FAILED

Comments

shojo’s picture

I dropped the database, re-imported it, and ran the script again. Again, the same two updates failed.

what I don't understands is what exactly to alter and how. like many, I use phpadmin.

(edit)

Here's some more informartion from 128 to use as an example:

----this is the 4.6.8 sql table---

CREATE TABLE term_node (
  nid int(10) unsigned NOT NULL default '0',
  tid int(10) unsigned NOT NULL default '0',
  KEY nid (nid),
  KEY tid (tid),
  PRIMARY KEY (tid,nid)
) TYPE=MyISAM;

---this is the original 4.6.6 table---

CREATE TABLE `term_node` (
  `nid` int(10) unsigned NOT NULL default '0',
  `tid` int(10) unsigned NOT NULL default '0',
  PRIMARY KEY  (`tid`,`nid`),
  KEY `nid` (`nid`),
  KEY `tid` (`tid`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

----this is the update script----

function update_128() {
  $ret = array();

  if ($GLOBALS['db_type'] == 'mysql') {
    $ret[] = update_sql('ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid)');
  }
  elseif ($GLOBALS['db_type'] == 'pgsql') {
    $ret[] = update_sql('ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid)');
  }

  return $ret;
}

-----this is the failure warning---

2005-03-21

ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid) 
FAILED

_____________________
Visit
http://www.localghost.org
Education As Intellectual Self-Defense

calebgilbert’s picture

you don't actually need to upgrade from 4.6 to 4.8 to be able to go to 4.7. I did it from 4.6 to 4.7.

Had some issues with that, but then again having upgrade issues seems normal enough.

You can always try and issue a repair table command from phpmyadmin and see if that helps, other than that, hopefully you've backed up. And it is likely you'll need to troubleshoot some things along the way. When I ran into my upgrade problems I just started searching Drupal.org and google for the error I was receiving and went from there. Very tedious, but many times I was able to find someone who had the same issue and some clues for what to do...

=====
Bloggyland.com
Hosting for pre-tuned/pre-configured Drupal installations
Instantly activated site, Drupal specific support, SSH/FTP/cPanel
Portfolio: HigherVisibilitywebsites.com

shojo’s picture

so are you saying i should just continue with the upgrade and ignore the failed database entries?

_____________________
Visit
http://www.localghost.org
Education As Intellectual Self-Defense

calebgilbert’s picture

...likely just need to troubleshoot your way out of a couple things. Wish I could be more definitive, but upgrading Drupal is not a very definitive thing at this point. It can be done, of course.

=====
Bloggyland.com
Hosting for pre-configured Drupal installations
Instantly activated, Drupal specific support
Portfolio: HigherVisibilityWebsites.com