Topic on Project:Support desk

Problem with upgrade from 1.18 to 1.23

4
Talyaron (talkcontribs)

Hi,

I have updated from 1.18 to 1.23, and got th following massage:

A database query error has occurred. This may indicate a bug in the software.

  • Query:
    SELECT page_title FROM `nsl_page` WHERE page_is_redirect = '0' AND page_namespace = '8' AND (page_title NOT LIKE '%/%' ) AND (page_len > 10000)
  • Function: MessageCache::loadFromDB(en)-big
  • Error: 1146 Table 'talyaron_mdw1.nsl_page' doesn't exist (localhost)

I tried to run update.php from putty but it gave me the following error:

"cannot get command line argument, register_argc_argv is set to falsetalyaron@talyaron.com

How can it be solved ?

Ciencia Al Poder (talkcontribs)

The database error is strange, since nothing should be changed in a way to break it. Looking at the query, your setup seems to have defined $wgDBprefix to "nsl_", and the database is "talyaron_mdw1". Is that correct? So all tables of the database should have that prefix.

register_argc_argv is required on command line, so you need to enable it in php.ini. Alternatively, you can run the update script from the web, as explained in Manual:Upgrading.

Talyaron (talkcontribs)

Thanks Ciencia,

Sorry that it took me a while :-)

I have done what you said, and now I get this error:

A database query error has occurred. Query: SELECT page_title FROM `nsl_page` WHERE page_is_redirect = '0' AND page_namespace = '8' AND (page_title NOT LIKE '%/%' ) AND (page_len > 10000) Function: MessageCache::loadFromDB(en)-big Error: 1146 Table 'talyaron_mdw1.nsl_page' doesn't exist (localhost)

What can be done?

88.130.77.35 (talkcontribs)

You obviously have changed the table prefix. MediaWiki currently tries to use the database talyaron_mdw1 and tables, which are prefixed with nsl_. However, these tables are not there - at least the page table is not there.

When you do an upgrade, you can keep (or copy) your LocalSettings.php file. It is not necessary to change things like $wgDBprefix in it.

After that make sure that you have done the database update.

Reply to "Problem with upgrade from 1.18 to 1.23"