Long time to close catalog New version 9.2
I've upgraded from 9.1.2 to 9.2.
If I close the catalogue now The activity window "saving" show up and it took almost 10-15 minutes, before the application close. I didn't occur with older versions. Actually I reinstalled the older version 9.1.2. and I don't have this problem. So it's 9.2 related to my opinion. What I did see is, if I startup the application I see in the catalog directory a file show up: "Foto Archief One.cocatalogdb-journal", I didn't see before. Do have others seen this behavior.
Some other thing I'v noticed that my catalog file size was 85 mb, after upgrading it was 60mb what is the cause of this, what information is removed.
If I close the catalogue now The activity window "saving" show up and it took almost 10-15 minutes, before the application close. I didn't occur with older versions. Actually I reinstalled the older version 9.1.2. and I don't have this problem. So it's 9.2 related to my opinion. What I did see is, if I startup the application I see in the catalog directory a file show up: "Foto Archief One.cocatalogdb-journal", I didn't see before. Do have others seen this behavior.
Some other thing I'v noticed that my catalog file size was 85 mb, after upgrading it was 60mb what is the cause of this, what information is removed.
0
-
Hi,
the journal file "tells" you, that there are some activity on the database.
You can try to install 9.2 again and then "repair catalog"0 -
[quote="RobiWan" wrote:
Hi,
the journal file "tells" you, that there are some activity on the database.
You can try to install 9.2 again and then "repair catalog"
I've reinstall 9.2 again and did verify catalog but this reported that the catalogue was oke. Problem still exist.0 -
[quote="BertG" wrote:
I've reinstall 9.2 again and did verify catalog but this reported that the catalogue was oke. Problem still exist.
Hmm, is the *.journal file direct after start created and will not be deleted?
By me, if I do any changes - select a photo or deselect, journal file will be created and later ~ 30-40sec its deleted. and is coming only if C1 hat anything to do.
Exit C1 also takes a long time - but catalog itself is closed much faster (you see it, when the "writelock" no more exist0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare