Re: [Koha] Transferring data from an old version to a new one
Hi All, We were using an old version of KOHA in our small library. We recently had a new version installed on a newer server. Our tech support person transferred the data from the old version to the new. However, when we tested the system by doing a search on a topic the new version did not come up with any results. Here is the problem as given to me by out tech person: On the old server, we were running Koha version 1.x (I don't remember what number the 'x' was. If that information is important, I'll need to visit the IC again to find out.) We're now running version 2.2.9. I made a SQL dump of the old database ("mysqldump") and loaded that data nearly verbatim into the new database. The names of the database tables in the old koha database all seem to exist in the new database as well, so I didn't need to change any table names. Likewise, *most* of the column names and types (with maybe one exception) in the old tables are the same in the new tables, so porting the old data to the new database was fairly straightforward. However, some of the tables in the new database have columns that did not exist in the old database. In porting the old data, these new columns would of course have taken their default values. I'm guessing that this may be the crux of the problem; that something other than the default values needs to go into one or more of these new columns. Can anyone offer suggestions on how to fix this problem? Thanks, Judith C. Saulle Interim Associate Director Lorna Sundberg International Center University of Virginia 21 University Circle P.O. Box 400183 Charlottesville, VA 22903 (434) 924-7983 www.virginia.edu/iso/ic
Hi Judith, We have recently done the same upgrade, coming from 1.2.2 to 2.2.9. It is a much more involved process than simply moving the data from your old database to a new one. We had to get copies of koha versions 2.0, 2.2, 2.2.6 and 2.2.9. Then upgrade the database structure in steps using a script called updatedatabase available in each version under /scripts/updater/. We ran this script for each version using the command: perl -I /path/to/koha[version]/modules updatedatabase which upgrades the database structure. In edition to upgrading the database structure with the scripts we had to move all of our biblio records into the new marc record structure that is created during the upgrade. The script to do this is in /scipts/misc/koha2marc.pl we ran this script using the command: perl -I /path/to/koha[version]/modules koha2marc.pl -c We ran into all kinds of errors and issues along the way, it has taken a while, as most upgrades of this kind do. What helped was making backups along the way of both the working code for a version and the database for a version, for example, when we got from 1.2.2 to 2.0 we backed up the working code and database before trying to get to 2.2 and so on. So the trick is, upgrade database structure one version at a time, and see if you can get the code for that version working, then at any point in time (probably at version 2.2.9) you need to create all the marc record data using the koha2marc.pl script. Goodluck, it's a long process but the payoff if a much more usable and feature rich system. Steve. -----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Judith C. Saulle Sent: Tuesday, May 06, 2008 3:49 PM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Transferring data from an old version to a new one Hi All, We were using an old version of KOHA in our small library. We recently had a new version installed on a newer server. Our tech support person transferred the data from the old version to the new. However, when we tested the system by doing a search on a topic the new version did not come up with any results. Here is the problem as given to me by out tech person: On the old server, we were running Koha version 1.x (I don't remember what number the 'x' was. If that information is important, I'll need to visit the IC again to find out.) We're now running version 2.2.9. I made a SQL dump of the old database ("mysqldump") and loaded that data nearly verbatim into the new database. The names of the database tables in the old koha database all seem to exist in the new database as well, so I didn't need to change any table names. Likewise, *most* of the column names and types (with maybe one exception) in the old tables are the same in the new tables, so porting the old data to the new database was fairly straightforward. However, some of the tables in the new database have columns that did not exist in the old database. In porting the old data, these new columns would of course have taken their default values. I'm guessing that this may be the crux of the problem; that something other than the default values needs to go into one or more of these new columns. Can anyone offer suggestions on how to fix this problem? Thanks, Judith C. Saulle Interim Associate Director Lorna Sundberg International Center University of Virginia 21 University Circle P.O. Box 400183 Charlottesville, VA 22903 (434) 924-7983 www.virginia.edu/iso/ic _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hi Steve, Many thanks for your response. I will pass this information on to our tech support guy. Cheers, Judy --On Wednesday, May 07, 2008 11:48 AM -0400 Steve Bradwell <sbradwell@perimeterinstitute.ca> wrote:
Hi Judith,
We have recently done the same upgrade, coming from 1.2.2 to 2.2.9. It is a much more involved process than simply moving the data from your old database to a new one.
We had to get copies of koha versions 2.0, 2.2, 2.2.6 and 2.2.9.
Then upgrade the database structure in steps using a script called updatedatabase available in each version under /scripts/updater/.
We ran this script for each version using the command:
perl -I /path/to/koha[version]/modules updatedatabase
which upgrades the database structure.
In edition to upgrading the database structure with the scripts we had to move all of our biblio records into the new marc record structure that is created during the upgrade.
The script to do this is in /scipts/misc/koha2marc.pl we ran this script using the command:
perl -I /path/to/koha[version]/modules koha2marc.pl -c
We ran into all kinds of errors and issues along the way, it has taken a while, as most upgrades of this kind do. What helped was making backups along the way of both the working code for a version and the database for a version, for example, when we got from 1.2.2 to 2.0 we backed up the working code and database before trying to get to 2.2 and so on.
So the trick is, upgrade database structure one version at a time, and see if you can get the code for that version working, then at any point in time (probably at version 2.2.9) you need to create all the marc record data using the koha2marc.pl script.
Goodluck, it's a long process but the payoff if a much more usable and feature rich system.
Steve.
-----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Judith C. Saulle Sent: Tuesday, May 06, 2008 3:49 PM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Transferring data from an old version to a new one
Hi All,
We were using an old version of KOHA in our small library. We recently had a new version installed on a newer server. Our tech support person
transferred
the data from the old version to the new. However, when we tested the system by doing a search the new version did not come up with any results.
Here is the problem as given to me by out tech person:
On the old server, we were running Koha version 1.x We're now running version 2.2.9. I made a SQL dump of the old database ("mysqldump") and loaded that data nearly verbatim into the new database.
The names of the database tables in the old koha database all seem to exist in the new database as well, so I didn't need to change any table names. Likewise, *most* of the column names and types (with maybe one exception) in the old tables are the same in the new tables, so porting the old data to the new database was fairly straightforward. However, some of the tables in the new database have columns that did not exist in the old database. In porting the old data, these new columns would of course have taken their default values. I'm guessing that this may be the crux of the problem; that something other than the default values needs to go into one or more of these new columns.
Can anyone offer suggestions on how to fix this problem?
Thanks,
Judith C. Saulle Interim Associate Director Lorna Sundberg International Center University of Virginia 21 University Circle P.O. Box 400183 Charlottesville, VA 22903 (434) 924-7983 www.virginia.edu/iso/ic
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Judith C. Saulle Interim Associate Director Lorna Sundberg International Center University of Virginia 21 University Circle P.O. Box 400183 Charlottesville, VA 22903 (434) 924-7983 www.virginia.edu/iso/ic
participants (2)
-
Judith C. Saulle -
Steve Bradwell