Major 3.18 upgrade problem -- Please help!
Dear all, We are having a major problem upgrade from from 3.16 to 3.18! Our IT person is able to resolve 2 warning messages related to Zebra_Bib_Index_Mode and Zebra_Auth_Index_Mode (found in About > System Informaiton). However, after a complete reindexing of Zebra, all our catalogue records (some 12,900 of them) have vanished! Searching of known items found nothing either via Staff Client or OPAC. We haven't able to use Koha last 2 days! As I'm not familiar with the operating system, etc., but my understanding is that he followed past upgrade method and it didn't involve a fresh/new install of Koha. Never encountered problem in the past upgrade until now. We don't seem to have any problem with patron records. I hope someone can provide advise and assistance. Also there seems to be some "challenge" to find upgrade instruction. Could we have such instruction made downloadable separate to the actual system files, so we can see what's involved. Kind regards, Iming ----- Iming Chan Translib Information Service Melbourne, Australia http://opac.translib.com Phone: +61 3 9801 5097 Fax: +61 3 9801 4024 E-mail: iming@translib.com -- View this message in context: http://koha.1045719.n5.nabble.com/Major-3-18-upgrade-problem-Please-help-tp5... Sent from the Koha-general mailing list archive at Nabble.com.
Some more details passed on from our IT person at this point in time: Zebra configuration information ================================ Zebra biblio directory = /var/lib/koha/library/biblios Zebra authorities directory = /var/lib/koha/library/authorities Koha directory = /usr/share/koha/intranet/cgi-bin Lockfile = /var/lock/koha/library/rebuild/rebuild..LCK BIBLIONUMBER in : 999$c BIBLIOITEMNUMBER in : 999$d ================================ skipping authorities ==================== exporting biblio ==================== 6001.................................................................................................... Records exported: 6060 ==================== REINDEXING zebra ==================== 11:26:31-07/12 zebraidx(3654) [warn] Couldn't open collection.abs [No such file or directory] ----- Iming Chan Translib Information Service Melbourne, Australia http://opac.translib.com Phone: +61 3 9801 5097 Fax: +61 3 9801 4024 E-mail: iming@translib.com -- View this message in context: http://koha.1045719.n5.nabble.com/Major-3-18-upgrade-problem-Please-help-tp5... Sent from the Koha-general mailing list archive at Nabble.com.
Hi Iming, Iming Chan schrieb am 07.12.2014
Dear all,
We are having a major problem upgrade from from 3.16 to 3.18! Our IT person is able to resolve 2 warning messages related to Zebra_Bib_Index_Mode and Zebra_Auth_Index_Mode (found in About > System Informaiton). However, after a complete reindexing of Zebra, all our catalogue records (some 12,900 of them) have vanished! Searching of known items found nothing either via Staff Client or OPAC. We haven't able to use Koha last 2 days!
My guess is that your IT person copied to your koha-conf.xml file <zebra_bib_index_mode>dom</zebra_bib_index_mode> <zebra_auth_index_mode>dom</zebra_auth_index_mode> to the get rid of the warnings, while the rest of your system is set to GRS-1 indexing (not DOM indexing). You can see that in the same file. For Biblios check the section
<!-- BIBLIOGRAPHIC RECORDS --> <server id="biblioserver" listenref="biblioserver"> <directory>/var/lib/koha/koha/biblios</directory> <config>/etc/koha/sites/koha/zebra-biblios-dom.cfg</config>
^^^^^^ and for authorities see the part beginning with
<!-- AUTHORITY RECORDS --> <server id="authorityserver" listenref="authorityserver" > <directory>/var/lib/koha/koha/authorities</directory> <config>/etc/koha/sites/koha/zebra-authorities-dom.cfg</config> ^^^^^^
They are set to DOM in my example and may look different in your configuration. Try changing the new parameters to grs1 for biblios or both, depending on these settings, like <zebra_bib_index_mode>grs1</zebra_bib_index_mode> <zebra_auth_index_mode>grs1</zebra_auth_index_mode> In the long run, consider switching to DOM indexing as GRS-1 is deprecated and no longer maintained. Hope that helps, Mirko
participants (2)
-
Iming Chan -
Mirko Tietgen