Hi all, Been using koha for the last 5 months. Since yesterday when I try to a mysqldump, I keep on geting the error "mysqldump: Error 2013: Lost connection to MySQL during query when dumping table 'biblioitems' at row: 1052" So now I cant backup my database. I have also installed koha 3.4 on a new system with the intention of moving everything over, but cannot find any documentation that can help me with my situation. Any info will be higly appreciated thanks in advance -- View this message in context: http://koha.1045719.n5.nabble.com/biblioitems-tp4436269p4436269.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
On 29 May 2011 04:38, sysadmin <zahid_mohd786@hotmail.com> wrote:
Hi all,
Been using koha for the last 5 months. Since yesterday when I try to a mysqldump, I keep on geting the error "mysqldump: Error 2013: Lost connection to MySQL during query when dumping table 'biblioitems' at row: 1052"
So now I cant backup my database.
That sounds like a corruption in MySQL. Have you tried googling for the error code/description?
I have also installed koha 3.4 on a new system with the intention of moving everything over, but cannot find any documentation that can help me with my situation.
You'll find the short version here: http://galencharlton.com/blog/2011/04/reading-upgrade-instructions-is-fundam... And the long version is in the INSTALL.* files that are part of the Koha code: http://git.koha-community.org/gitweb/?p=koha.git;a=tree;hb=HEAD Here is the relevant part of INSTALL.debian, for example: UPGRADE ======= If you are upgrading from a previous installation of Koha 3.x, you can use the following: ./koha_perl_deps.pl -u -m # to identify new Perl dependencies Install any missing modules IMPORTANT: Koha 3.4.x uses Template::Toolkit, this must be installed before the webinstaller can run sudo apt-get install libtemplate-perl perl Makefile.PL --prev-install-log /path/to/koha-install-log make make test sudo make upgrade Koha 3.4.x no longer stores items in biblio records so as part of the upgrade you will need to do the following two steps, they can take a long time (several hours) to complete for large databases misc/maintenance/remove_items_from_biblioitems.pl --run misc/migration_tools/rebuild_zebra.pl -b -r Best regards, Magnus Enger libriotech.no
Hi Thanks for the reply, I carried out the command mysqlcheck auto repair command, it would start than fail after biblioframeworks. Also tried to repair it using phpmyadmin but that didnt work as well. I noticed that in phpmyadmin I could open all of the rows from biblio. But when I tried to open biblioitems I could not open the last 4 pages (from row 1046) as it would just bring me back to the login page of phpmyadmin. To fix my problem, I exported the bibliographic and holdings marc record from the tools section of 3.02 koha. Then on the 3.5 koha I configured the libraries and carried out the command bulkmarcimport.pl Now this worked, but I didnt received about 100 books which is probably corrupted in the database. So everythings all good now, except for that I have to re enter the 100 books again. -- View this message in context: http://koha.1045719.n5.nabble.com/biblioitems-tp4436269p4436714.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
sysadmin schreef op zo 29-05-2011 om 02:52 [-0700]:
So everythings all good now, except for that I have to re enter the 100 books again.
I assume you can recover this from backups? You were making backups weren't you? -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
sysadmin schreef op zo 29-05-2011 om 02:52 [-0700]:
So everythings all good now, except for that I have to re enter the 100 books again.
I assume you can recover this from backups? You were making backups weren't you?
I wasn't quite to sure on how to restore the backed up database on the newly built koha :( so I just used the marc record from the old koha system. The reason why I did that was because we are just getting the books in the database for now only. The new system is a virtual machine which makes backup a little bit simpler, but it will be nice to learn on how to do a complete restore of koha from the backed up databases. -- View this message in context: http://koha.1045719.n5.nabble.com/biblioitems-tp4436269p4437974.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
sysadmin schreef op zo 29-05-2011 om 17:00 [-0700]:
I wasn't quite to sure on how to restore the backed up database on the newly built koha :( so I just used the marc record from the old koha system.
A backup is not a backup if you can't restore it.
The new system is a virtual machine which makes backup a little bit simpler, but it will be nice to learn on how to do a complete restore of koha from the backed up databases.
Well, I'm of the opinion that a database snapshot is the most reliable way to back up a database. You know that it's in a consistent state, and it's readily accessible. Also, you could load it into another mysql database and extract the missing records into your koha records without too much difficulty, I should think. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
sysadmin schreef op zo 29-05-2011 om 17:00 [-0700]:
I wasn't quite to sure on how to restore the backed up database on the newly built koha :( so I just used the marc record from the old koha system.
A backup is not a backup if you can't restore it.
True, but I did get all my books, except for the ones that got corrupted one way or another. -- View this message in context: http://koha.1045719.n5.nabble.com/biblioitems-tp4436269p4438136.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
Robin Sheat-2 wrote:
sysadmin schreef op zo 29-05-2011 om 17:00 [-0700]:
I wasn't quite to sure on how to restore the backed up database on the newly built koha :( so I just used the marc record from the old koha system.
A backup is not a backup if you can't restore it.
True, but I did get all my books, except for the ones that got corrupted one way or another.
I still wouldn't mind repairing the old corrupted database. If you could provide some info this Thanks in advance -- View this message in context: http://koha.1045719.n5.nabble.com/biblioitems-tp4436269p4438147.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
sysadmin schreef op zo 29-05-2011 om 19:28 [-0700]:
I still wouldn't mind repairing the old corrupted database. If you could provide some info this
Well, it depends on the nature of the backup, but I'm going to assume it's an SQL dump. Load it into another MySQL database (on the same instance as the koha you're setting up, ideally.) Find the range of biblio numbers that are missing, and using mysql's ability to select and insert across databases, pull all the things across that have a biblionumber within the corrupted range. You'll want to pull from the tables 'biblio', 'biblioitems', 'items'. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
participants (3)
-
Magnus Enger -
Robin Sheat -
sysadmin