Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Database check, database repair fail

Comments

8 comments

  • SFA
    Mogens,

    For what it is worth ....

    Every check I have tried has failed. I have never attempted to "Repair" as far as I recall. I don't check often. I don't see any problems with the sessions that I have checked even though they seem to have failed.

    The only problem I have had in V7 was a single session (I do not use catalogues other than for experiments and I have many sessions) with a corrupt edit file. Once I spotted the problem (by chance at the time) and deleted the problem edit the session was fine and has continued to be fine. That was using an early V7 release. I have not seen any problems with V7.5 or, in the last day or so, V7.6 (so far).

    The forum is quiet with respect to any V7.6 issues so I assume it is good.

    I do not expect you will have any problems but it is sensible (and potentially useful to C1) to report the problem so that it can be investigated.

    It may be something like the Virus checking applications that frequently identify false positives for some reason. The technical world becomes very complicated - it is not surprising that strange things are reported whether they are correct or an error.

    All my personal opinion of course.


    Grant
    0
  • NNN634578809887629371
    +1

    I've got the same - every check fails. Do the repair - the computer says it's good. Do a check and it fails.
    I'm using a single catalogue with about 10k images.
    0
  • mli20
    Thanks guys, your thoughts are much appreciated.

    The thing for me is, that I do have real problems with one catalog. Ratings and colour tags cannot be stored, and some images are no longer accessible from the catalog. Searching, COP7 won't find them, but, when I then try to re-import them, COP7 will tell me they are already in the catalog.

    And indeed they are: Looking at the catalog tables with SQLite Manager, there they are, in the form of orphaned records in certain tables. "Orphaned".., that's why they can't be seen from within COP7, and that's also why COP7 refuses re-importing them. I of course cannot accept being denied access to my images.

    At the present atate of affairs, for me the catalog features in COP7 are not ready for prime time, as using them seems to be at the risk of loosing many hours of work.

    I'll let you know how things pan out with PhaseOne support.

    Cheers,
    Mogens
    0
  • mli20
    Stilll nothing from technical support...

    I originally raised this issue on dec. 21. 2013 and have as yet not received nothing to indicate that they have even the slightest inkling about what is going on.

    Seeing that users occasionally get personalized support in the user forums, sometimes in a matter of minutes, makes one wonder which is the better and proper channel for obtaining support, or if the problem with the catalog is of such proportions as to warrant the time support is taking.

    Cheers,
    Mogens
    0
  • Gregg Le Blanc
    I have had a lot of Sessions start feeling slow, so when that happens, I do a Check / Repair. Version 7.6 is the first one that will actually fix the errors in the Session. In 7.4 and below, many sessions were just un-repairable. They would just fail.

    I find that when I use Local Adjustments, things almost immediately start to go wrong with a session. Or do lots of cropping then copy / paste adjustments everywhere.

    I haven't used Catalogs much because of the issue you reported - I needed to move the image source from one drive to another (which Expression / Media Pro could do). When I did that, I could never repair my session, and lost all my adjustments on lots of images.

    So I went back to sessions.

    Sorry that doesn't help more. I sent the behavior into support.

    I mostly noticed it around the Cropping (when copied / pasted) and Local Adjustments (especially if I copied and pasted those). I sometimes had to remove those, repair the session, and then start again...
    0
  • mli20
    Thanks all the same, it's of some comfort to know one is not alone with a given problem.

    I was all set to go fully with COP7 as my DAM system. That's not going to happen any time soon now, things looking as they are. I believe the catalog design is flawed. COP7 is still a very good raw converter though.

    Cheers,
    Mogens
    0
  • marcoi
    Any news about this issue? I've the same problem with sessions. I already opened a ticket with P.O. support waiting for reply but would like to know if you (and how) you solved. Thanks a lot
    0
  • mli20
    I have stopped using catalogs. Tech support seemed clueless, and having waited in vain for a full month I took a look at the database design myself (I'm a database professional). I was not encouraged and simply decided to go elsewhere.

    Cheers,
    Mogens
    0

Post is closed for comments.