update.php failed to update database

We need to know the errors you got.

You can't.

What you should do now, is recreate the 4.6.3 database from a backup, and try to do the update again. If it fails again, record the errors this time.

Nono. there is a way to do it.

You just have to do what you did initially, and run update.php on the 4.6.3 database.

I confirm that this issue is a serious problem.

I was unable to upgrade directly to 4.7.0 beta1 because of an update issue. (http://drupal.org/node/40687)

As an alternative, I was asked to upgrade my 4.5 database first to 4.6 then to 4.7.0 beta1. The upgrade to 4.6 went smoothly. I did not test the site extensively, but all expected functionality was present.

The update from 4.6 to 4.7 beta1 also seemed to run smoothly, but in actual effect it did not work. There were no recorded errors; the update ran from system_update_133, but even though there are multiple database structure additions reflected in updates.inc, there was no display of any database changes made in update.php.

Examination of the mysql table revealed that there were some changes made, however - the number of records increased by 113, and the size of the database increased by 0.1MB.

The end result is a site which displays no information at all: See screenshots, of the front page and admin page.

The behaviour of the site is not entirely consistent over Firefox and Opera. (see screenshots)

Well, playback the backup you made (you did make one, right?), try again, and report back the errors.

I see similar problems. 4.6.4 to 4.7 cvs or 4.7 beta is the same

update.php?op=selection gives page where System module 130 is selected for update

clicking 'update' gives nothing I just end up on update.php?op=selection again very quickly....

going to the website after that gives "Pagina niet gevonden"

On screen I see no error, the system log gives the following:

I try to upgrade goju-andy on my local system, duplicated the database into testbed...

 PHP Warning:  Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 0, cache = 0, hostname = '127.0.0.1', session = 'messages|a:0:{}', timestamp = 1134300734 WHERE sid = 'e556k4oljafovv9jjbvqckr9l5&am
Dec 11 12:32:50 Blaster /usr/sbin/httpd: PHP Warning:  Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 0, cache = 0, hostname = '127.0.0.1', session = 'messages|a:0:{}', timestamp = 1134300770 WHERE sid = 'e556k4oljafovv9jjbvqckr9l5&am
Dec 11 12:40:38 Blaster /usr/sbin/httpd: PHP Warning:  Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'page not found', '<em>node</em> niet
Dec 11 12:40:38 Blaster /usr/sbin/httpd: PHP Warning:  Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'theme' in 'where clause'\nquery: SELECT * FROM blocks WHERE theme = 'gojuandy' AND status = 1 ORDER BY region, weight, module in /Users/bwynants/Sites/4.7/drupal/includes/database.mysql.inc op lijn 108.', 2, &#0
Dec 11 12:40:38 Blaster /usr/sbin/httpd: PHP Warning:  Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'sid' in 'field list'\nquery: INSERT INTO accesslog (title, path, url, hostname, uid, sid, timer, timestamp) values('Pagina niet gevonden', 'node', '', '192.168.1.4&#03
Dec 11 12:40:38 Blaster /usr/sbin/httpd: PHP Warning:  Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 1, cache = 0, hostname = '192.168.1.4', session = 'messages|a:0:{}watchdog_overview_filter|s:3:\\"all\\";node_overview_filter|a:0:{}
Dec 11 12:40:38 Blaster /usr/sbin/httpd: PHP Warning:  Unknown column 'referer' in 'field list'\nquery: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'access' in 'field list'\nquery: UPDATE users SET access = 1134301238 WHERE uid = 1 in /Users/bwynants/Sites/4.7/drupal/includes/database.mysql.inc op lijn 108.', 2, '', '/4.7/drupal/', '', '192.
Dec 11 12:44:40 Blaster /usr/sbin/httpd: PHP Warning:  main(sites/default/settings.php) [<a href='function.main'>function.main</a>]: failed to open stream: No such file or directory in /Users/bwynants/Sites/goju-ryu/includes/bootstrap.inc on line 636
Dec 11 12:44:40 Blaster /usr/sbin/httpd: PHP Warning:  main() [<a href='function.include'>function.include</a>]: Failed opening 'sites/default/settings.php' for inclusion (include_path='.:/usr/local/php5/lib/php') in /Users/bwynants/Sites/goju-ryu/includes/bootstrap.inc on line 636

I find the referal to Users/bwynants/Sites/goju-ryu/includes/bootstrap very weird since that site has nothing to do with the site being updated....

Same problem updating from a 4.6.3 to 4.7.
The update runs smoothly (a bit too fast perhaps) starting at system_update_133, it finishes almost instantly, which is very odd knowing i have a 300+ MB database, no errors are displayed, it says any errors are logged, but because no page can be displayed those can't be displayed either. after checking it does seem the database has been slightly changed. But I get theme and watchdog errors and none of the pages are displayed.

So i did reverted to the old databse from a backup and did it a second time, this time changing settings to default, and using the bluemarine theme before the update, but still the same problems occur.
Eventually after 3 times of failure. I took a look at update.php, but didn't figure out where the problem could be.

I wrote my own script to do the updates, because I really want to go to 4.7 as soon as possible to prevent me from having to do all the changes I planned for my site again when 4.7 final is released.

I'm sure there's an error in the update.php, and my best guess would be that it's in the progress displaying section.
Still, I haven't been able to figure out what it is exactly.

I had the same problems and errors as multiplex. Can you post you update script please?
It seem that the update script changes something but not all....

Have you tried running the update script with JavaScript switched off? There were at least some problems associated with this in beta1, but I think they've all been cleared up by now. See http://drupal.org/node/40677.

Cheers,
Andy J.

I had similar problems upgrading to 4.6.3 to 4.7-beta.2 (I got a screen saying upgrade is complete, no errors were reported, but the db wasn't updateds and no queries at all seemed to be run). Don't know why, but I got it to work by first upgrading to 4.6.5 and then to 4.7-beta.2

Lets open up new issues for 4.7.0-beta3 if they exist.