[Koha] Upgrading from 2.2 to 3.0, not so smooth...
Ming214
myan at judcom.nsw.gov.au
Thu Dec 11 14:18:45 NZDT 2008
I suggest you not use its migration scripts which are not good enough. Export
the biblio records and do a fresh installation of koha 3.0, then do a bulk
import of your old data. I know it seems easier to upgrade from 2.2 to 3.0,
but we found it even much easier to do it in the other way as we have been
through too many problems with its scripts and given up.
Ming
PasiK wrote:
>
> We tried to upgrade our Koha system from 2.2 to 3.0. Installation went ok,
> but data-conversion failed. Here are the error messages from
> update22to20.pl:
>
> Adding textmessaging field to deletedborrowers table...
> DBD::mysql::st execute failed: Unknown column 'faxnumber' in
> 'deletedborrowers' at ./update22to30.pl line 3071.
> **Error : DBI::st=HASH(0x88f6500)->errstr
> altering borrowers zipcode to zipcode
> altering deletedborrowers zipcode to zipcode
> altering deletedborrowers homezipcode to B_zipcode
> DBD::mysql::db do failed: Duplicate column name 'B_zipcode' at
> ./update22to30.pl line 3104.
> removing some unused fields...
> alter or create notify_id in accountlines
> alter or create notify_level in accountlines
> alter or create accountno in accountlines
> alter or create booksellerid in aqbasket
> alter or create bookfundid in aqbookfund
> alter or create branchcode in aqbookfund
> alter or create id in aqbooksellers
> DBD::mysql::db do failed: Multiple primary key defined at
> ./update22to30.pl line 3271.
> Error while executing: alter table aqbooksellers change `id` `id` int(11)
> NOT NULL PRIMARY KEY auto_increment at ./update22to30.pl line 3271.
> alter or create currency in aqbooksellers
> alter or create listprice in aqbooksellers
> alter or create invoiceprice in aqbooksellers
> alter or create invoicedisc in aqbooksellers
> alter or create bookfundid in aqbudget
> alter or create bookfundid in aqorderbreakdown
> alter or create ordernumber in aqorderdelivery
> alter or create currency in aqorders
> alter or create authtypecode in auth_header
> alter or create datecreated in auth_header
> alter or create origincode in auth_header
> alter or create authtypecode in auth_subfield_structure
> alter or create tagfield in auth_subfield_structure
> alter or create tagsubfield in auth_subfield_structure
> alter or create liblibrarian in auth_subfield_structure
> alter or create libopac in auth_subfield_structure
> alter or create authorised_value in auth_subfield_structure
> alter or create value_builder in auth_subfield_structure
> alter or create seealso in auth_subfield_structure
> alter or create kohafield in auth_subfield_structure
> alter or create frameworkcode in auth_subfield_structure
> alter or create authtypecode in auth_tag_structure
> alter or create tagfield in auth_tag_structure
> alter or create liblibrarian in auth_tag_structure
> alter or create libopac in auth_tag_structure
> alter or create authorised_value in auth_tag_structure
> alter or create auth_tag_to_report in auth_types
> alter or create summary in auth_types
> alter or create category in authorised_values
> alter or create authorised_value in authorised_values
> alter or create lib in authorised_values
> alter or create frameworkcode in biblio
> alter or create frameworkcode in biblio_framework
> alter or create frameworktext in biblio_framework
> alter or create itemtype in biblioitems
> alter or create dewey in biblioitems
> alter or create publicationyear in biblioitems
> alter or create collectiontitle in biblioitems
> alter or create collectionissn in biblioitems
> alter or create collectionvolume in biblioitems
> alter or create editionstatement in biblioitems
> alter or create editionresponsibility in biblioitems
> alter or create shelfname in bookshelf
> alter or create owner in bookshelf
> alter or create category in bookshelf
> alter or create cardnumber in borrowers
> alter or create surname in borrowers
> alter or create branchcode in borrowers
> alter or create categorycode in borrowers
> alter or create address in borrowers
> alter or create city in borrowers
> alter or create sex in borrowers
> alter or create branchcode in branches
> alter or create branchname in branches
> alter or create branchcode in branchrelations
> alter or create categorycode in branchrelations
> alter or create frombranch in branchtransfers
> alter or create tobranch in branchtransfers
> alter or create category_type in categories
> alter or create categorycode in categories
> DBD::mysql::db do failed: Multiple primary key defined at
> ./update22to30.pl line 3271.
> Error while executing: alter table categories change `categorycode`
> `categorycode` varchar(10) NOT NULL PRIMARY KEY default '' at
> ./update22to30.pl line 3271.
> alter or create frameworkcode in deletedbiblio
> alter or create itemtype in deletedbiblioitems
> alter or create dewey in deletedbiblioitems
> alter or create itemtype in deletedbiblioitems
> alter or create branchcode in deletedborrowers
> alter or create categorycode in deletedborrowers
> alter or create B_zipcode in deletedborrowers
> alter or create zipcode in deletedborrowers
> alter or create address in deletedborrowers
> alter or create city in deletedborrowers
> alter or create surname in deletedborrowers
> alter or create streetnumber in deletedborrowers
> alter or create streettype in deletedborrowers
> alter or create sex in deletedborrowers
> alter or create borrowernumber in issues
> alter or create itemnumber in issues
> alter or create return in issues
> alter or create categorycode in issuingrules
> alter or create branchcode in issuingrules
> alter or create itemtype in issuingrules
> alter or create homebranch in items
> alter or create holdingbranch in items
> alter or create itemtype in itemtypes
> DBD::mysql::db do failed: Multiple primary key defined at
> ./update22to30.pl line 3271.
> Error while executing: alter table itemtypes change `itemtype` `itemtype`
> varchar(10) NOT NULL PRIMARY KEY default '' at ./update22to30.pl line
> 3271.
> alter or create description in itemtypes
> alter or create summary in itemtypes
> alter or create marc in marc_breeding
> alter or create defaultvalue in marc_subfield_structure
> alter or create authtypecode in marc_subfield_structure
> alter or create tagfield in marc_subfield_structure
> alter or create tagsubfield in marc_subfield_structure
> alter or create authorised_value in marc_subfield_structure
> alter or create seealso in marc_subfield_structure
> alter or create tagfield in marc_tag_structure
> alter or create liblibrarian in marc_tag_structure
> alter or create libopac in marc_tag_structure
> alter or create authorised_value in marc_tag_structure
> alter or create frameworkcode in marc_tag_structure
> alter or create expirationdate in opac_news
> alter or create printername in printers
> alter or create printqueue in printers
> alter or create printtype in printers
> alter or create reservedate in reserveconstraints
> alter or create constrainttype in reserves
> alter or create branchcode in reserves
> alter or create planneddate in serial
> alter or create notes in serial
> alter or create branch in statistics
> alter or create datetime in statistics
> alter or create startdate in subscription
> alter or create histstartdate in subscriptionhistory
> alter or create enddate in subscriptionhistory
> removing some unused data...
> DELETE FROM userflags where bit = 8
> synch'ing borrowers and deletedborrowers
> synch'ing items and deleteditems
> synch'ing biblio and deletedbiblio
> synch'ing biblioitems and deletedbiblioitems
> Updating publisheddate
> Checking for data required in table userflags...
> Checking for data required in table systempreferences...
> Checking for data required in table authorised_values...
> Adding row to authorised_values: authorised_value => Not enough budget
> lib => This book it too much expensive category => SUGGEST
> insert into authorised_values (authorised_value,lib,category) values
> (?,?,?)Checking for index required...
> Creating index borrowernumber in borrowers
> DBD::mysql::db do failed: Multiple primary key defined at
> ./update22to30.pl line 3408.
> Error alter table borrowers ADD PRIMARY KEY (borrowernumber) :
> DBI::db=HASH(0x885d484)->err
> Checking for foreign keys required...
> Creating foreign key items in accountlines
> Creating foreign key aqbookfund in aqorderbreakdown
> Creating foreign key biblio in aqorders
> Creating foreign key branches in borrowers
> Creating foreign key branchcategories in branchrelations
> Creating foreign key items in branchtransfers
> Creating foreign key items in issues
> Creating foreign key branches in items
> Creating foreign key branches in items
> DBD::mysql::db do failed: Cannot add or update a child row: a foreign key
> constraint fails (`Koha/#sql-a58_52`, CONSTRAINT `#sql-a58_52_ibfk_5`
> FOREIGN KEY (`holdingbranch`) REFERENCES `branches` (`branchcode`) ON
> UPDATE CASCADE) at ./update22to30.pl line 3442.
> ====================
> An error occured during :
> alter table items ADD FOREIGN KEY holdingbranch (holdingbranch)
> REFERENCES branches (branchcode) on update CASCADE on delete RESTRICT
> It probably means there is something wrong in your DB : a row
> (items.holdingbranch) refers to a value in branches.branchcode that does
> not exist. solve the problem and run updater again (or just the previous
> SQL statement).
> You can find those values with select
> items.* from items where holdingbranch not in (select branchcode from
> branches)
> ====================
>
> Creating foreign key biblio in reserves
> Creating foreign key items in reserves
> Creating foreign key branches in reserves
> Creating foreign key bookshelf in shelfcontents
> DBD::mysql::db do failed: Can't DROP 'borrowernumber'; check that
> column/key exists at ./update22to30.pl line 3531.
> upgrade to Koha 3.0 done
>
> At the moment we are able to access Koha via browser, but there are no
> biblios in the database (borrower information, branches and such seem to
> be there, however). There is a number of biblios in the database that
> don't have item information and we are also using some non-marc21 fields.
> Could this be the cause? Ideas for fixing this?
>
>
--
View this message in context: http://www.nabble.com/Upgrading-from-2.2-to-3.0%2C-not-so-smooth...-tp20934550p20947725.html
Sent from the Koha - Discuss mailing list archive at Nabble.com.
More information about the Koha
mailing list