[Koha] [Important] Update your MySQL|MariaDB configuration to avoid data loss

Jonathan Druart jonathan.druart at bugs.koha-community.org
Fri Aug 4 01:39:56 NZST 2017


Yes you should create the file to make sure the situation will not appear
again for other rows.
For the corrupted records (the ones returned by the SQL queries), please
follow bug 19016.


On Thu, 3 Aug 2017 at 05:00 vinod mishra <mishravk79 at gmail.com> wrote:

> Dear All,
> I am using Koha 16.11.07 and because of below problems i faced lot of
> transaction related issues, since it was start of the koha so i simply
> deleted all circulation history (Very less which came along with test
> database during setup) and now things work fine. I did not upgraded koha
> too and using RFID which is configured via Koha SIP. Everything is working
> fine now but as per the instruction i run commands and found some output
> while excecuted below three so please suggest. Please suggest should i
> create the file as suggested in the chain of email? or leave it as it is.
> SELECT r.reserve_id     FROM reserves r  JOIN old_reserves o      ON r.reserve_id=o.reserve_id;
> SELECT b.biblionumber   FROM biblio b    JOIN deletedbiblio db    ON b.biblionumber=db.biblionumber;
> SELECT i.itemnumber     FROM items i     JOIN deleteditems di     ON i.itemnumber=di.itemnumber;
> With Regards,
> Vinod Kumar Mishra,
> Assistant Librarian,
> Biju Patnaik Central Library (BPCL),
> NIT Rourkela,
> Sundergadh-769008,
> Odisha,
> India.
> Mob:91+9439420860
> Website: http://mishravk.com/
> ORCID ID: http://orcid.org/0000-0003-4666-7874
> *"Spiritual relationship is far more precious than physical. Physical
> relationship divorced from spiritual is body without soul" -- Mahatma
> Gandhi*
> On Wed, Aug 2, 2017 at 3:15 PM, Jon Knight <J.P.Knight at lboro.ac.uk> wrote:
>> On Tue, 1 Aug 2017, Bortel, Gary wrote:
>>> For a multi-tenant installation with multiple MySQL databases...
>>> "The Solution" (
>>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix)
>>> recommends adding "init-file=/var/lib/mysql/init-file_kohadev.sql" in the
>>> my.cnf MySQL configuration file, then creating the appropriately configured
>>> "init-file_kohadev.sql" file. Where there are multiple Koha databases,
>>> should one add multiple "init-file=..." statements to my.cnf as well as
>>> multiple init-file_kohadev.sql files? Or will MySQL only accept one
>>> init-file directive in which case the .sql file would include multiple
>>> blocks of code...one for each database?
>> I'd say that its up to you really - both will work.  If you use just one
>> "init-file_kohadev.sql" file you'll just have to repeat all the SQL, just
>> changing the database in the "use" line. If you've got lots of Koha
>> instances that file is going to be quite long.
>> Personally for tidiness and ease of maintenance I'd probably opt for one
>> init file per Koha database, as those would be clearer and could then be
>> maintained more easily using normal Linux command line tools and a few Perl
>> scripts.  I assume people hosting lots of tenants are probably using tools
>> like Ansible to set up provisioning of a new Koha instance so these files
>> would be created from a template and just one line added/removed from the
>> my.conf file.
>> Jon
>> _______________________________________________
>> Koha mailing list  http://koha-community.org
>> Koha at lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha

More information about the Koha mailing list