> > Has anyone sucessfully upgraded their midgard database
> > from an early 1.4 beta (1.4b5, in my case) to 1.4 release?
> > If so, I'd like to hear how you did it.
>
> Yes, I did.
Thank you for the procedure. I ran into a problem near the
end:
> The beta series had a different layout for the repligard table, and the
> sitegroup table didn't have the realm column. This how I worked around
> the fact that the upgrade script misses these differences:
>
> - mysqldump -u root -p --no-create-info midgard > export.sql
> - edit export.sql, removing al data-entries for the repligard table.
> - verify that the sitegroup table has the correct structure
I didn't specify sitegroups in the 1.4b5 configuration; presumably
that's why there are no entries for the sitegroup table in export.sgl.
> (compare with create statement in empty.sql)
> - if needed add realm values to export.sql
> - mysqladmin -u root -p newmidgard
I think you meant:
mysqladmin -u root -p create newmidgard
which I did.
> - mysql -u root -p newmidgard < export.sql
First I did:
mysql -u root -p newmidgard < empty.sql (to create tables)
then:
mysql -u root -p newmidgard < export.sql
> - edit install-repligard.conf to use database newmidgard in stead of
> midgard.
> - mysql -u root -p newmidgard < GUIDSforOLDSITE.sql
> - repligard -c install-repligard.conf -m , to generate missing guids
> - repligard -c install-repligard.conf -i AsgardSite.xml
Here I got:
Message: Reading config file install-repligard.conf
Message: Importing AsgardSite.xml
REPLIGARD/READ-ERROR **: Failed to allocate delayed resource
f6b665f1984503790ed91f39b11b5392 as a link author for blobs.
aborting...
Aborted
Where did I go wrong?
Paul N.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
