PHPNuke Database Restoration Problem

bugsy · Worker Joined: May 08, 2007 Posts: 129

Hi while trying to restore a database of a PHPNuke 7x Site with help of HeidiSQL (As database size is over 50mb) it came accross this error

Code:

/* SQL Error: BLOB/TEXT column 'item' used in key specification without a key length */

I am also posting the queries that were inserted before the error

Code:

CREATE TABLE nuke_myh_blog ( bid int(11) NOT NULL auto_increment, cid int(11) DEFAULT '0' NOT NULL, created int(11) DEFAULT '0' NOT NULL, modified int(11) DEFAULT '0' NOT NULL, published int(11) DEFAULT '0' NOT NULL, visible int(11) DEFAULT '0' NOT NULL, allow_comment int(11) DEFAULT '1' NOT NULL, PRIMARY KEY (bid) )
CREATE TABLE nuke_myh_blog_cache ( cid int(11) NOT NULL auto_increment, sid int(11) DEFAULT '0' NOT NULL, item text NOT NULL, stamp int(11) DEFAULT '0' NOT NULL, hits int(11) DEFAULT '0' NOT NULL, PRIMARY KEY (cid), KEY nuke_myh_blog_cache_idx1 (stamp), KEY nuke_myh_blog_cache_idx2 (sid), KEY item (item) )

then came

Code:

/* SQL Error: BLOB/TEXT column 'item' used in key specification without a key length */

What it was to querry after that is

Code:

KEY item (item)
);

#
# Dumping data for table 'nuke_myh_blog_cache'

Any idea what do i have to change in the .sql file to resolve this issue?

Thanks in advance

hitwalker · Sells PC To Pay For Divorce Joined: Posts: 5661

and what if you import the database without that table?

bugsy · Worker Joined: May 08, 2007 Posts: 129

That i have not tried - logically it should work as 68 tables got installed properly and got stuck on that one - i got a single backedup .sql file so what i can try doing is i) drop that table from the sql file and try to re-execute the sql query with Heidi.

In that case any idea what can the be missed out if nuke_myh_blog table is dropped? I mean how important is it to Nukes Functioning? Its a PhpBB table i believe.

Logically if the .sql file is broken up into multiple files as per the tables then also it should work right? So i might just ii) try to load from the portion after the error table.

For added info - i got MySQL 4.1.20 in the server and sql file was saved from normal backup option from the admin backend.

Thanks

hitwalker · Sells PC To Pay For Divorce Joined: Posts: 5661

well sometimes that happens when importing a table it goes wrong...
that narmally can be solved doing that one seperate..
just strip the stuff and load the other table parts before and after that one..
maybe im mistaken but that table is a forum mod,probably blog but its not that wellknown.

bugsy · Worker Joined: May 08, 2007 Posts: 129

Ya breaking the SQL up and skipping the error tables worked and I also realised that the set of tables came from a module called 'MyHeadlines' which was deactivated in the site anyway. So have dropped the nuke_myh_tables and all got uploaded. Yet to test run the new site though.

Thanks

hitwalker · Sells PC To Pay For Divorce Joined: Posts: 5661

ah i see,but what a weird table name..
im no fan of MyHeadlines...
good luck..