Compress Data Base error on GloHD

mconh · 11-07-2015, 06:59 PM

When attempting to compress the data base I get this "database or disc full" error. Any ideas on how to fix? Also getting random WIN7 requests to scan device disc on connect (never any errors).

calibre, version 2.43.0
ERROR: Unhandled exception: <b>OperationalError</b>:database or disk is full

calibre 2.43 [64bit] isfrozen: True is64bit: True
Windows-7-6.1.7601-SP1 Windows ('64bit', 'WindowsPE')
('Windows', '7', '6.1.7601')
Python 2.7.9
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
Successfully initialized third party plugins: K4PC, K4Mac, Kindle Mobi and Topaz DeDRM && Inept Epub DeDRM && Goodreads && Find Duplicates && Reading List && Resize Cover && Quality Check && Inept PDF DeDRM && Ignoble Epub DeDRM && Kobo Utilities
Traceback (most recent call last):
File "calibre_plugins.koboutilities.action", line 1441, in vacuum_device_database
File "calibre_plugins.koboutilities.action", line 3189, in _vacuum_device_database
OperationalError: database or disk is full

davidfor · 11-07-2015, 08:56 PM

Unless the disk of the device is actually full, or doesn't have enough space to write a copy of the database, it probably means the database is corrupt. Run database check function in the plugin to check. And check the size of the database and the space left. The database is ".kobo\KoboReader.sqlite".

mconh · 11-09-2015, 04:09 PM

Thank you. The problem was traced to a couple of bad books that showed up when I used create books catalog. I corrected the problems (author and author sort did not match in meta data) with the books. Then reloaded the books. This allowed a compress data base command to proceed.

davidfor · 11-09-2015, 05:53 PM

Sorry, but I doubt that was the problem or fix. The Kobo devices do not handle the sort_author in any way. When they process a book into the internal database, only the first creator attribute in the OPF is used and then only the text part. And I have no idea how creating a catalog in calibre could affect the database on the Kobo device.

Most likely the firmware cleaned something up in the database that fixed whatever triggered the first error. Disconnecting the device and restarting it could have triggered something in the firmware to fix it. Or, something else about how you had attached the device caused the problem. Running the Kobo desktop application at the same time as calibre can cause these sort of things.

11-07-2015, 06:59 PM	#1
mconh Connoisseur Posts: 68 Karma: 112688 Join Date: Oct 2011 Location: Cambridge Ontario Device: Kobo Touch, Glo, AuraHD, AuraH20	Compress Data Base error on GloHD When attempting to compress the data base I get this "database or disc full" error. Any ideas on how to fix? Also getting random WIN7 requests to scan device disc on connect (never any errors). calibre, version 2.43.0 ERROR: Unhandled exception: <b>OperationalError</b>:database or disk is full calibre 2.43 [64bit] isfrozen: True is64bit: True Windows-7-6.1.7601-SP1 Windows ('64bit', 'WindowsPE') ('Windows', '7', '6.1.7601') Python 2.7.9 Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free') Successfully initialized third party plugins: K4PC, K4Mac, Kindle Mobi and Topaz DeDRM && Inept Epub DeDRM && Goodreads && Find Duplicates && Reading List && Resize Cover && Quality Check && Inept PDF DeDRM && Ignoble Epub DeDRM && Kobo Utilities Traceback (most recent call last): File "calibre_plugins.koboutilities.action", line 1441, in vacuum_device_database File "calibre_plugins.koboutilities.action", line 3189, in _vacuum_device_database OperationalError: database or disk is full

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
corrupted data base	keith1241	Calibre	4	05-05-2013 10:40 PM
Can Calibre compress ePub?	marty1990	Calibre	2	06-09-2012 06:52 AM
error when editing meta data	tom233	Calibre	1	10-06-2010 03:28 AM

11-07-2015, 08:56 PM	#2
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Unless the disk of the device is actually full, or doesn't have enough space to write a copy of the database, it probably means the database is corrupt. Run database check function in the plugin to check. And check the size of the database and the space left. The database is ".kobo\KoboReader.sqlite".

11-09-2015, 04:09 PM	#3
mconh Connoisseur Posts: 68 Karma: 112688 Join Date: Oct 2011 Location: Cambridge Ontario Device: Kobo Touch, Glo, AuraHD, AuraH20	Thank you. The problem was traced to a couple of bad books that showed up when I used create books catalog. I corrected the problems (author and author sort did not match in meta data) with the books. Then reloaded the books. This allowed a compress data base command to proceed.

11-09-2015, 05:53 PM	#4
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Sorry, but I doubt that was the problem or fix. The Kobo devices do not handle the sort_author in any way. When they process a book into the internal database, only the first creator attribute in the OPF is used and then only the text part. And I have no idea how creating a catalog in calibre could affect the database on the Kobo device. Most likely the firmware cleaned something up in the database that fixed whatever triggered the first error. Disconnecting the device and restarting it could have triggered something in the firmware to fix it. Or, something else about how you had attached the device caused the problem. Running the Kobo desktop application at the same time as calibre can cause these sort of things.

Advert