It is quite possible that update had already been processed through some
fix in your 3.12.x sub-version.
Having done quite a few upgrades over the years, I don't remember one
where I didn't get one update error or another. But always there was a
logical explanation, and the end result was perfectly ok.
If the errors on patronimage are your only ones, I would (personnally)
trust the end result and keep proceeding with a simple upgrade using
updatedatabase.pl to move to 17.11.
Best regards,
Philippe Blouin,
Responsable du développement informatique
Tél. : (888) 604-2627
philippe.blo...@inlibro.com <mailto:philippe.blo...@inlibro.com>
inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
On 05/24/2018 04:50 PM, Help Desk DSS, UG wrote:
Thanks for your feedback. Please see below the errors from
updatedatabase.pl <http://updatedatabase.pl>
Regards,
Sekhar Mallampati
+++++++++++++++++++++++++++++++++++++++
Updating database structure
Update report :
* Status: 500
* Content-type: text/html
*
* <h1>Software error:</h1>
* <pre>DBD::mysql::db do failed: Can't DROP 'patronimage_fk1'; check
that column/key exists [for Statement "
* ALTER TABLE patronimage DROP FOREIGN KEY patronimage_fk1
* "] at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
<http://updatedatabase.pl> line 7291.
* </pre>
* <p>
* For help, please send mail to the webmaster (<a href="mailto:[no
address given]">[no address given]</a>), giving this error message
* and the time and date of the error.
*
* </p>
Update errors :
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: DBD::mysql::db do failed: Duplicate
column name 'borrowernumber' [for Statement "
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: ALTER TABLE patronimage ADD
borrowernumber INT( 11 ) NULL FIRST
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: "] at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
<http://updatedatabase.pl> line 7272.
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: DBD::mysql::db do failed: Can't DROP
'patronimage_fk1'; check that column/key exists [for Statement "
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: ALTER TABLE patronimage DROP FOREIGN
KEY patronimage_fk1
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: "] at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
<http://updatedatabase.pl> line 7291.
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: DBD::mysql::db do failed: Can't DROP
'patronimage_fk1'; check that column/key exists [for Statement "
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: ALTER TABLE patronimage DROP FOREIGN
KEY patronimage_fk1
* [Thu May 24 16:08:16 2018] updatedatabase.pl
<http://updatedatabase.pl>: "] at
/usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl
<http://updatedatabase.pl> line 7291.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On Thu, May 24, 2018 at 4:44 PM, Philippe Blouin
<philippe.blo...@inlibro.com <mailto:philippe.blo...@inlibro.com>> wrote:
Hi Sekhar,
Upgrading from 3.12 is usually ok. Could you detail the errors
you encounter?
Exporting/importing the biblios also theoratically works fine, but
some versions have had glitches preventing it. Still,
updatedatabase.pl <http://updatedatabase.pl> should work unless
you have customized the DB.
Philippe Blouin,
Responsable du développement informatique
Tél. : (888) 604-2627
philippe.blo...@inlibro.com <mailto:philippe.blo...@inlibro.com>
inLibro | pour esprit libre | www.inLibro.com
<http://www.inLibro.com>
On 05/24/2018 04:38 PM, Help Desk DSS, UG wrote:
Hi,
This is Sekhar from University of Guyana. I had sent an email few years
back.
We are trying to upgrade from Koha 3.12 to Koha 17.11 and encountering
problems in updating database schema. These SQL errors are reported from
updatedatabase.pl <http://updatedatabase.pl>
I am wondering why can't we export the biblios and items data in MARC
format and import them back into new Koha installation using MARC
Management.
The only issue with this approach is circulation data. I am hoping that we
can get around this by using Koha Offline Circulation tool.
Your feedback is much appreciated.
Thanks,
Sekhar Mallampati
University of Guyana
_______________________________________________
Koha mailing listhttp://koha-community.org
Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
https://lists.katipo.co.nz/mailman/listinfo/koha
<https://lists.katipo.co.nz/mailman/listinfo/koha>
--
Dept. of Software Services Staff
University of Guyana
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
