Summary: | No physical item for this record on records after mysqldump and zebra rebuild | ||
---|---|---|---|
Product: | Koha | Reporter: | Eugene Espinoza <eugenegf> |
Component: | Cataloging | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED INVALID | QA Contact: | |
Severity: | trivial | ||
Priority: | P2 | CC: | liz, m.de.rooy |
Version: | 3.8 | ||
Hardware: | All | ||
OS: | Linux | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 8393 | ||
Bug Blocks: |
Description
Eugene Espinoza
2012-07-09 15:12:25 UTC
Hi, I think this bug and 8393 are probably related and maybe not bugs, but some problem in your configuration. Which version of Koha are you using? Did you update from an earlier version or is this a new installation and the first imports you are doing? Can you provide a sample 952 for one of your items? I am using Kyle Hall's virtual machine of Koha 3.8.1. For this reported 8394 bug (?), I actually mysqldump my previous mysql data from 3.6. I did not incur problems with regards to missing items or no physical items for records in my koha 3.6 machine (kyle hall's virtual machine) which were imported from 3.2. Here is by the way the 952 field: =952 \\$w2011-10-24$p033073hp$r2011-10-24$40$00$6F__KPM_00041_W55_W54_2000$915302$bLLS$10$o(F) KPM 41 W55 W54 2000$d2002-12-10$70$cGEN$2lcc$g695.00$yBK$aLLS$iMR_02 1177; MD_$kR_; PO_; PD 00668 This problem already solve. What I did was to drop the koha database and then import my previous database (koha 3.6). What I did previously was to just overwrite (?) existing original koha database with mysqldump of my backup database. And when I run zebra rebuilds items were showing up. Is there a way that overwriting of original koha mysql database by previous mysqldump won't affect items not showing up? |