[Koha] Upgrade 3.01 to 3.6 on Diff Server
joshmikow at gmail.com
Tue Apr 3 10:34:26 NZST 2012
I created a new instance called "brdglibrary" (to be a more understandable
name for us) and I restored the database backup from "biblioteka" to that
database. I then ran the koha-upgrade-schema script and it ran fine. The
koha-upgrade-to-3.4 command kept returning a bunch of "Use of uninitialized
value in pattern match (m//) at /usr/share/koha/lib/C4/Biblio.pm line 2953"
messages. It's still running and I'm not sure if that is a problem or not.
Before I had created "brdglibrary" I had tried creating a few other
instances and now would like to remove them but the koha-remove doesn't
work. It appears that when it tries to drop the mysql user, it fails
because it doesn't pass the name of the instance properly to the DROP
statement. Do you know how I can fix that to make the removal of an
On Mon, Apr 2, 2012 at 3:16 PM, Chris Cormack <chris at bigballofwax.co.nz>wrote:
> On 3 April 2012 11:12, Josh Mikow <joshmikow at gmail.com> wrote:
> > Thanks Chris!
> > I don't believe any customizations to the .pl files would have been done.
> > Is there a way to determine that?
> > I have a database dump from 3.1.0 restored on the 3.6.4 box. That's all
> > I've done so far. I also have a copy of all the files in all the
> > but I haven't done anything with them yet.
> > The instance on the 3.1.0 is called "biblioteka". I restored the
> > of the same name on the 3.6.4 server.
> > I tried running a koha-upgrade-schema biblioteka but it returned an error
> > like it can't find the "koha-conf.xml" file. Should I restore the
> > /etc/koha/ folder to /etc/koha/sites/biblioteka? Is that what you
> > to as an import? I think on the old server it was installed as a single
> > instance but on the new server I'd like to have a test instance
> available if
> > we want to try things out first.
> You will have to have done a koha-create biblioteka on the new one
> then you can do
> koha-mysql biblioteka < name_of_your_dump.sql
> Then run the other commands
> > Thanks again for the help!
> > Josh
> > On Mon, Apr 2, 2012 at 2:35 PM, Chris Cormack <chris at bigballofwax.co.nz>
> > wrote:
> >> On 3 April 2012 08:52, Josh Mikow <joshmikow at gmail.com> wrote:
> >> > Hello,
> >> >
> >> >
> >> > My biggest questions are:
> >> > 1. What is the best way to make sure I backup all of the necessary
> >> > on
> >> > the 3.01 system so that I can successfully get them over to the 3.06
> >> > system
> >> > to restore?
> >> Unless you have done some local customisation by editing the perl
> >> scripts or templates. All you need is the database itself. So a
> >> database dump of that.
> >> > 2. What is the best way to properly restore the 3.01 files under the
> >> > 3.06
> >> > install without causing future problems?
> >> You don't want to do that :) You will cause problems. What you want to
> >> do is import your 3.1.x database into your 3.6.4 instance, then run
> >> koha-upgrade-schema <instancename>
> >> then
> >> koha-uprade-to-3.4 <instancename>
> >> What this second one does is remove the item data from the marcxml
> >> blob in biblioitems. This was changed in 3.4.0 hence the name, since
> >> you are going from 3.1.x to 3.6.4 you need this to be done. It will
> >> then start a zebra reindex. After that you will be up on 3.6.4 .. the
> >> next thing to do would be to work through all the settings and check
> >> they are ok (circulation rules, systempreferences etc). Get the
> >> librarians to test.
> >> If its all ok, do this again and call it live :)
> >> > 3. What steps do I need to do to upgrade the 3.01 to the 3.06 system?
> >> See above :)
> >> > 4. Currently the system is working on localhost but we will need to
> >> > it
> >> > working on our internet site. What configuration changes are needed
> >> > work both internally and externally?
> >> >
> >> You will need to play with the apache config file in sites-enabled to
> >> get the virtual host listening on the names/numbers you want it too.
> >> Hope this helps
> >> Chris
More information about the Koha