By nancydru on
Trying to start up D6-beta3 (upgrade from D5.3), I get "Unknown column 'info' in 'field list' query" on every table in the database.
Trying to start up D6-beta3 (upgrade from D5.3), I get "Unknown column 'info' in 'field list' query" on every table in the database.
Comments
and...
Update #6015
* Failed: CREATE TABLE {cache_form} ( cid varchar(255) NOT NULL default '', data longblob, expire int NOT NULL default '0', created int NOT NULL default '0', headers text, serialized int(1) NOT NULL default '0', PRIMARY KEY (cid), INDEX expire (expire) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6019
* Failed: UPDATE {users} SET uid = 4294967296 WHERE uid = 0
* Failed: ALTER TABLE {users} CHANGE uid `uid` INT unsigned NOT NULL auto_increment, ADD PRIMARY KEY (uid)
Update #6020
* Failed: CREATE TABLE {menu_router} ( `path` VARCHAR(255) NOT NULL DEFAULT '', `load_functions` VARCHAR(255) NOT NULL DEFAULT '', `to_arg_functions` VARCHAR(255) NOT NULL DEFAULT '', `access_callback` VARCHAR(255) NOT NULL DEFAULT '', `access_arguments` TEXT DEFAULT NULL, `page_callback` VARCHAR(255) NOT NULL DEFAULT '', `page_arguments` TEXT DEFAULT NULL, `fit` INT NOT NULL DEFAULT 0, `number_parts` SMALLINT NOT NULL DEFAULT 0, `tab_parent` VARCHAR(255) NOT NULL DEFAULT '', `tab_root` VARCHAR(255) NOT NULL DEFAULT '', `title` VARCHAR(255) NOT NULL DEFAULT '', `title_callback` VARCHAR(255) NOT NULL DEFAULT '', `title_arguments` VARCHAR(255) NOT NULL DEFAULT '', `type` INT NOT NULL DEFAULT 0, `block_callback` VARCHAR(255) NOT NULL DEFAULT '', `description` TEXT NOT NULL, `position` VARCHAR(255) NOT NULL DEFAULT '', `weight` INT NOT NULL DEFAULT 0, `file` MEDIUMTEXT DEFAULT NULL, PRIMARY KEY (path), INDEX fit (fit), INDEX tab_parent (tab_parent) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
* Failed: CREATE TABLE {menu_links} ( `menu_name` VARCHAR(32) NOT NULL DEFAULT '', `mlid` INT unsigned NOT NULL auto_increment, `plid` INT unsigned NOT NULL DEFAULT 0, `link_path` VARCHAR(255) NOT NULL DEFAULT '', `router_path` VARCHAR(255) NOT NULL DEFAULT '', `link_title` VARCHAR(255) NOT NULL DEFAULT '', `options` TEXT DEFAULT NULL, `module` VARCHAR(255) NOT NULL DEFAULT 'system', `hidden` SMALLINT NOT NULL DEFAULT 0, `external` SMALLINT NOT NULL DEFAULT 0, `has_children` SMALLINT NOT NULL DEFAULT 0, `expanded` SMALLINT NOT NULL DEFAULT 0, `weight` INT NOT NULL DEFAULT 0, `depth` SMALLINT NOT NULL DEFAULT 0, `customized` SMALLINT NOT NULL DEFAULT 0, `p1` INT unsigned NOT NULL DEFAULT 0, `p2` INT unsigned NOT NULL DEFAULT 0, `p3` INT unsigned NOT NULL DEFAULT 0, `p4` INT unsigned NOT NULL DEFAULT 0, `p5` INT unsigned NOT NULL DEFAULT 0, `p6` INT unsigned NOT NULL DEFAULT 0, `p7` INT unsigned NOT NULL DEFAULT 0, `p8` INT unsigned NOT NULL DEFAULT 0, `p9` INT unsigned NOT NULL DEFAULT 0, `updated` SMALLINT NOT NULL DEFAULT 0, PRIMARY KEY (mlid), INDEX path_menu (link_path(128), menu_name), INDEX menu_plid_expand_child (menu_name, plid, expanded, has_children), INDEX menu_parents (menu_name, p1, p2, p3, p4, p5, p6, p7, p8, p9), INDEX router_path (router_path(128)) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
Update #6030
* Failed: CREATE TABLE {actions} ( `aid` VARCHAR(255) NOT NULL DEFAULT '0', `type` VARCHAR(32) NOT NULL DEFAULT '', `callback` VARCHAR(255) NOT NULL DEFAULT '', `parameters` LONGTEXT NOT NULL, `description` VARCHAR(255) NOT NULL DEFAULT '0', PRIMARY KEY (aid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
* Failed: CREATE TABLE {actions_aid} ( `aid` INT unsigned NOT NULL auto_increment, PRIMARY KEY (aid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
and then ...
* warning: array_map() [function.array-map]: Argument #2 should be an array in C:\www\drupal\modules\system\system.module on line 856.
* warning: array_keys() [function.array-keys]: The first argument should be an array in C:\www\drupal\includes\theme.inc on line 1769.
* warning: Invalid argument supplied for foreach() in C:\www\drupal\includes\theme.inc on line 1769.
NancyDru
I was busy upgrading from
I was busy upgrading from Drupal 5.5 to 6.19 and I got a bunch of errors. One of which was:
user warning: Unknown column 'serialized' in 'field list' query: SELECT data, created, headers, expire, serialized FROM cache_similarterms WHERE cid = '0:1028' in /home/xxx/public_html/xxx.com/includes/cache.inc on line 26.
Just running this in phpmyadmin:
ALTER TABLE cache_similarterms ADD serialized SMALLINT(6) NOT NULL;
The article here helped me out:
http://www.zyxware.com/articles/635/solved-warning-unknown-column-serial...
...
This message says there isn't a column named 'info' in some table. This error is generated, for example, when you do
SELECT info FROM {some-table-here}when there's no 'info' column in that table.There's a new 'info' column in Drupal 6's {system} table. Adding this column is one of the first things Drupal 6's update.php does. Examine the {system} table (using phpMyAdmin for example) to see if this column was indeed added. (Perhaps you didn't overwrite D5's 'update.php' with that of D6?)
Well, I tried again
This would be so much easier if my access problem was fixed.
I tried again with beta4 and got different errors. I wonder if I'll ever get D6 going?
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
Most recent problems
I upgraded a very minimal 5.5 site to 6-beta4. The system works just fine under D5.5. On firing up D6, I get:
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
...
(I assume you remembered to run 'update.php' beforehand ...and that it, too, spew errors.)
1. Examine the new {system} table: does it have an 'info' column? (You can use phpMyAdmin for this.)
2. If you're going to upgrade another D5 site: at the 'Select updates' screen (of update.php) there's a 'Select versions' collapsed fieldset. When you open it, what number do you see under 'system module'? You should see exactly '6000'.
...
I'm not getting the "info column" problem now. But I got that error running update.php. These latest errors are before I even have a chance to run it.
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
...
Please open an 'issue'. We need more eyeballs here. You describe a problem where you can't upgrade several sites, one of them "very minimal", and it sounds critical.
I tried to reproduce this problem, but failed.
(So everything is alright now? No other errors? The missing "info column" error did appear in the last batch you pasted. I'm fond of it because adding this column belongs in a simple part of the update process and I thought tackling it would be the easiest route to solve the mystery.)
("have a chance" is present tense. So you still get errors?)
"Still"
Well, let me put it this way: The only clean start up of D6 I have had was on a new database - not a conversion. So, yes, I still get errors.
http://drupal.org/node/200900
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
ditto
I get the same message - Unknown column 'serialized' in 'field list' query etc.
Working on a test copy of my site.
Actually happened twice.
First on my normal test version of the site.
And then, in case i had stuffed something up, as per instructions, i took a copy of my production database and files, set them up locally,
put it in maintenance mode, changed the theme to garland, turned off non-core modules, and ran update.php.
I got a blank screen after the update.php.
Then when i visit the site, i get the unknown column message.
So the database update is definitely not happening.
I have too much data to start again.
Any ideas?
and a few minutes
and a few minutes later.......
all the other forum posts on this subject implied it was a contributed module error.
i had definitely unticked all non-core modules before upgrading the site, however to make sure, i went into the database and looked at table "system".
There were still some modules there with a status of "1". So i changed them to "0".
Reran the update.php again. It had warnings, but at least it finally came up with the continue message, so it could update the database.
Given that it happened twice, i reckon the modules are not being turned off correctly.
Thanks! Success ...
Thanks! This was super helpful. With your info I was successful in upgrading my Drupal site from 5.12 to 6.6. See my post here:
http://drupal.org/node/333011
Thanks again.
-backdrifting
Clear your caches. I just had
Clear your caches.
I just had an update with all these problems, but clearing all the caches cured it.
:)
And now...
I tried again to go from 6.6 to 6.10 and it worked fine. Maybe something in 6.8.
NancyDru