Drupal 5 to 6 Database Update.php Failures

Drupal 5 to 6 Database Update.php Failures

4 posts / 0 new
Last post
Audiophile's picture
chris
Points: 0
Drupal 5 to 6 Database Update.php Failures

Hi - This is my first post as I just subscribed to Acquia. I need to upgrade my site from 5.20 to 6.14, or whatever the newest version may be, and I am receiving several unnerving messages after moving to 6.14 and running Update.php. I don't know if these failed messages are nothing to worry about or if they are a barrier to upgrading my production site. I've attached the full screen print of all the updates, most of which succeeded just fine.

I'm ready to do all the work it takes to fix my site issues, I just don't know where to start. I've searched all over and haven't found information I can rely on before making changes to my production site.

The following queries were executed

system module
Update #6003
Failed: ALTER TABLE {comments} ADD INDEX status (status)

system module
Update #6043
Failed: ALTER TABLE {accesslog} ADD INDEX uid (uid)
Failed: ALTER TABLE {term_node} ADD PRIMARY KEY (tid, vid)

comment module
Update #6003
Failed: ALTER TABLE {comments} ADD INDEX status (status)

comment_notify module
Update #6000
Failed: DELETE FROM {comment_notify} WHERE cid NOT IN (SELECT cid FROM {comments})

comment_notify module
Update #6004
Failed: ALTER TABLE {comment_notify} ADD `notified` SMALLINT unsigned DEFAULT NULL
Failed: ALTER TABLE {comment_notify} CHANGE `notified` `notified` SMALLINT unsigned NOT NULL
Failed: UPDATE {comment_notify} SET notified = 1

 

 

user warning: Duplicate key name 'status' query: ALTER TABLE comments ADD INDEX status (status) in /Applications/MAMP/htdocs/includes/database.mysql-common.inc on line 434.

user warning: Duplicate key name 'uid' query: ALTER TABLE accesslog ADD INDEX uid (uid) in /Applications/MAMP/htdocs/includes/database.mysql-common.inc on line 434.

user warning: Duplicate entry '31-0' for key 'PRIMARY' query: ALTER TABLE term_node ADD PRIMARY KEY (tid, vid) in /Applications/MAMP/htdocs/includes/database.mysql-common.inc on line 374.

user warning: Duplicate key name 'pid' query: ALTER TABLE comments ADD INDEX pid (pid) in /Applications/MAMP/htdocs/includes/database.mysql-common.inc on line 434.

user warning: Table 'computer_humaliwo.comment_notify' doesn't exist query: DELETE FROM comment_notify WHERE cid NOT IN (SELECT cid FROM comments) in /Applications/MAMP/htdocs/modules/acquia/comment_notify/comment_notify.install on line 102.

user warning: Table 'computer_humaliwo.comment_notify' doesn't exist query: ALTER TABLE comment_notify ADD `notified` SMALLINT unsigned DEFAULT NULL in /Applications/MAMP/htdocs/includes/database.mysql-common.inc on line 298.

user warning: Table 'computer_humaliwo.comment_notify' doesn't exist query: ALTER TABLE comment_notify CHANGE `notified` `notified` SMALLINT unsigned NOT NULL in /Applications/MAMP/htdocs/includes/database.mysql-common.inc on line 520.

user warning: Table 'computer_humaliwo.comment_notify' doesn't exist query: UPDATE comment_notify SET notified = 1 in /Applications/MAMP/htdocs/modules/acquia/comment_notify/comment_notify.install on line 274.

Status: 
Unresolved
Audiophile's picture
chris
Points: 0

Hello - Does anyone work here or browse these forums? I'm really struggling to rationalize my purchase of a subscription considering this is a ghost town over here.

Audiophile's picture
chris
Points: 0

Hello [echo] [echo] [echo]

It's been two weeks now. Someone please offer assistance.

ksilanskas's picture
kenny.silanskas
Points: 2

Hi Chris,

I have taken a look at the information you sent (Thank you for that. Lots of info there) and here's what I think you might consider.

Typically, the add index errors that are received from various modules are because the index already exists (as is the case with the system table) and those can be safely ignored.

As for comment notify, that one looks a little trickier. Can you verify that users who were previously subscribed to comments still are in the new install? Also, worth checking out your own settings to make sure they were ported over. If so, you can probably safely ignore it.

But to be safe, I would go ahead and post an issue in the module's queue and see what the maintainer comes back with. You can find that here: http://drupal.org/project/issues/comment_notify

Hope this helps. Let me know if I can help out further.

---
Regards,
Kenny Silanskas
Drupal Support Engineer
Acquia

---
Kenny Silanskas
Team Manager, Tier 1
Client Advisory Team
@webkenny