3.6.1 updatedatabase.pl [was: Checkout fails]
We also experienced a few failures while installing a new 3.6.1 and importing an sql dump from the production 3.2: [Thu Dec 15 13:59:43 2011] updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'maxItemsInSearchResults' for key 'PRIMARY' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3955. [Thu Dec 15 13:59:43 2011] updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'privacy' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3997. [Thu Dec 15 13:59:43 2011] updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'privacy' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 3998. A quick verification showed no loss of functionality, but I haven't yet had time to look at what "privacy" means|does. Paul At 08:35 PM 12/16/2011 +0800, Muhammad Abdullah wrote:
I encountered exactly those same errors on my Koha 3.6.1. It seems the errors only appear when you upgrade the db from a previous version (3.2, in my case) of Koha to 3.6.
I also got these errors when Koha is updating the database through the web installer:
-- [Fri Dec 09 04:52:16 2011] updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'privacy' at /home/koha/kohaclone/installer/data/mysql/updatedatabase.pl line 3997. [Fri Dec 09 04:52:16 2011] updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'privacy' at /home/koha/kohaclone/installer/data/mysql/updatedatabase.pl line 3998. [Fri Dec 09 04:52:18 2011] updatedatabase.pl: DBD::mysql::db do failed: Table 'need_merge_authorities' already exists at /home/koha/kohaclone/installer/data/mysql/updatedatabase.pl line 4535. --
Chris C.(Koha's developer) said they are safe to ignore, though.(http://koha.1045719.n5.nabble.com/3-4-4-gt-3-6-1-upgrade-td5068580.html)
And Kyle Hall(Koha Virtual Appliance's creator) has these to say about them: "I think it's probably safe to ignore those errors. The script is attempting to create fields that are already in the tables, so I doubt you will see any problems."
On Thu, Dec 15, 2011 at 3:22 AM, Perch <jp@pk.dy.fi> wrote:
Upon trying to check items out to a patron this message appears:
-- Software error:
Can't call method "subfield" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 3008.
For help, please send mail to the webmaster (webmaster@vps185), giving this error message and the time and date of the error. --
The item gets checked out (i.e. it appears in the list of items checked out to the client when you go return to the checkout page). The same happens with check in. The items get checked in, but Koha stops at the error message.
Similar error message appears when trying to add a new issue to an existing subscription. I think the problem might be related to error I received when updating the database to new Koha version (http://koha.1045719.n5.nabble.com/Database-update-errors-td5068234.html).
Any help here? We really really need to get this working.
-- View this message in context: http://koha.1045719.n5.nabble.com/Checkout-fails-tp5075418p5075418.html Sent from the Koha-general mailing list archive at Nabble.com.
Duplicate entry 'maxItemsInSearchResults' for key 'PRIMARY'
"Duplicate entry" means that the update is trying to make a change that has already been made. That's why it's safe to ignore. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
On Fri, Dec 16, 2011 at 9:46 AM, Owen Leonard <oleonard@myacpl.org> wrote:
Duplicate entry 'maxItemsInSearchResults' for key 'PRIMARY'
"Duplicate entry" means that the update is trying to make a change that has already been made. That's why it's safe to ignore.
These errors are caused by the fact that these columns are created by earlier updates in updatedatabase.pl and then duplicated in later updates without checking for their existence first. IIRC this happened when we had some issue with some databases missing some of the acquisitions "stuff" in the first set of updates. As Owen pointed out, these types of errors may safely be ignored. Hopefully some minor changes in update coding practices will avoid these issues in the future. Kind Regards, Chris
participants (3)
-
Chris Nighswonger -
Owen Leonard -
Paul