v9.3 Corrupt Database / my Solution / and Other sqlite thing
I want to fist say I am not recommending anyone to do this. In the day and to some extent still I'm a developer. As such I would do things many of you might not do. That said the database was corrupt, and before restoring I decided to experiment.
I know why it corrupted. I Force Quitted. Now this is due to the fact it was taking toooooooo long to close the catalog (about 80,000 pictures).
I tried all the things recommended in C1 but to no avail. Knowing this is a sqlLight database I downloaded Valentina Studio (VS) App (free) and decided to see if it could open the database, and possibly repair it .. and while there do a little exploring.
First I had to open the C1 catalog file as a package, then not to hard to find the database file. I dragged it into VS. Behold loaded fine. So I chose the right click (Analize, then Compact and then Reindex) 3 tasks all done separately. You right click on the DB Name.
All seems fine.
I open C1 9.3 and all is good (from what I can tell) ... and I might add the compact/reindex seems to have improved things.
I share this as others may encounter this issue and if stuck, and nothing to loose why not.
This brings on new questions that only a C1 Developer could answer, or someone that had time to explore could answer. sqlite can have a file when you can store settings. How much paging to use etc. I explored and can not seem to find them. Im left to assume the C1 software "chooses" what looks good. I would rather a file where I could adjust the values. If it exists then I would love to know about them.
The other things I noticed is the DB structure "appears" very simple. A few tables (20 or so), and some indexes, no views that I can tell. Also seems the "querys" are client side driven not internalized in the DB. Im not here to say its good or bad, but for the length of time it takes some transactions to execute I thought the under the hood would be far more complex.
Anyway, if this helps someone great. If your a C1 Support person is there anyway I can tweek the sqlite engine?
I know why it corrupted. I Force Quitted. Now this is due to the fact it was taking toooooooo long to close the catalog (about 80,000 pictures).
I tried all the things recommended in C1 but to no avail. Knowing this is a sqlLight database I downloaded Valentina Studio (VS) App (free) and decided to see if it could open the database, and possibly repair it .. and while there do a little exploring.
First I had to open the C1 catalog file as a package, then not to hard to find the database file. I dragged it into VS. Behold loaded fine. So I chose the right click (Analize, then Compact and then Reindex) 3 tasks all done separately. You right click on the DB Name.
All seems fine.
I open C1 9.3 and all is good (from what I can tell) ... and I might add the compact/reindex seems to have improved things.
I share this as others may encounter this issue and if stuck, and nothing to loose why not.
This brings on new questions that only a C1 Developer could answer, or someone that had time to explore could answer. sqlite can have a file when you can store settings. How much paging to use etc. I explored and can not seem to find them. Im left to assume the C1 software "chooses" what looks good. I would rather a file where I could adjust the values. If it exists then I would love to know about them.
The other things I noticed is the DB structure "appears" very simple. A few tables (20 or so), and some indexes, no views that I can tell. Also seems the "querys" are client side driven not internalized in the DB. Im not here to say its good or bad, but for the length of time it takes some transactions to execute I thought the under the hood would be far more complex.
Anyway, if this helps someone great. If your a C1 Support person is there anyway I can tweek the sqlite engine?
0
-
Oh thank you very much.
I've all but given up on catalogs in C1. I had two hangs today with one of my catalogs and had to force quit. C1 was unable to repair either time with the database and I had to restore the backup.
It happened again and I turned to the forum and saw your post. The steps fixed my issue. Thanks so much for this, I was despairing.0 -
Thank you.
Yes Phase One need to do some optimisation on there SQLite database. With big DB it is just horrible to work with Capture One.0 -
Glad I could help. I was not going to post as thought maybe look like harping etc ..
Anyway I was just testing out the catalog again. I loaded it up and they have made some improvements but overall as a owner of the Media Pro (lightning fast), I just can't commit to the DAM in C1. At 80K photos I tried to nest a keyword and it was about 15 minutes. This on the latest 27" imac.
By comparison, Media Pro was less than 2 seconds.
Anyway glad I could help.0 -
Made my day and night! Thanks a lot for this useful posting! 0 -
Dear NN635399196184276250UL,
you are my hero of the day. Thank you!
Chris.0 -
Thank you everyone. Im glad to help. 0 -
In which way I can open the database with Valentina.
I Finder on desktop I see only the catalog „C1_9_CaptureOneCatalog Kopie"
I can open catalog with command „Show content"
Then I see lot of files, also „C1_8_CaptureOneCatalog.cocatalogdb"
See screenshot.
I think that is the relevant database.
In Valentine I cannot open this because I can not use in Valentine the command „Show content"
If I use in Valentina open Database and use „C1_9_CaptureOneCatalog Kopie" a message come in Valentina Database could not be opened!
Jochen
http://www2.pic-upload.de/thumb/32114585/Bildschirmfoto2016-11-14um08.51.42.png0 -
[quote="NN635399196184276250UL" wrote:
First I had to open the C1 catalog file as a package, then not to hard to find the database file. I dragged it into VS.
I dragged this also but following message come.
Jochen
http://www2.pic-upload.de/thumb/32114690/Bildschirmfoto2016-11-14um10.10.48.png0 -
I don't know why the solution don't work on my OS X.
I don't know why the solution work by Tommy Weir, Mario152 and starter of the thread.
Please, can someone help me step by step.
Jochen0
Post ist für Kommentare geschlossen.
Kommentare
9 Kommentare