Bug #5837

Import fails after recovery

Added by Kalle Kondelin about 2 years ago. Updated about 2 years ago.

Status:ClosedStart date:2015-05-08
Priority:4Due date:2015-05-08
Assignee:Kalle Kondelin% Done:

100%

Category:DB clientSpent time:-
Target version:1.18.1
Release notes:Fixes for database recovery to prevent producing a broken database as a result of the recovery procedure.
Tags: loss-of-data, db
Story points-
Velocity based estimate-
ReleaseSimantics 1.18.1Release relationshipAuto

Description

Summary

Database server failed to start and displayed error dialog.
User selected recovery option which completed correctly.
However, after this import operation did not work.
Console message revealed a problem with illegal resource index.

Associated revisions

Revision 31271
Added by Kalle Kondelin about 2 years ago

Fixes #5837. Import fails after recovery.
Fixed handling of remove and recover choices in this case.

Revision 31272
Added by Kalle Kondelin about 2 years ago

Merged revision(s) 31271 from db/trunk/org.simantics.db.server/src/org/simantics/db/server/internal.
Refs #5837. Import fails after recovery.

History

#1 Updated by Kalle Kondelin about 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset r31271.

#2 Updated by Tuukka Lehtonen about 2 years ago

  • Target version changed from 1.19.0 to 1.18.2

#3 Updated by Tuukka Lehtonen about 2 years ago

  • Release set to 33

#4 Updated by Tuukka Lehtonen about 2 years ago

  • Target version changed from 1.18.2 to 1.18.1
  • Release changed from 33 to 17

#5 Updated by Tuukka Lehtonen about 2 years ago

  • Release notes set to Fixes for database recovery to prevent producing a broken database as a result of the recovery procedure.

#6 Updated by Tuukka Lehtonen about 2 years ago

  • Status changed from Resolved to Closed

#7 Updated by Tuukka Lehtonen about 2 years ago

  • Subject changed from Import fails after recovery. to Import fails after recovery

Also available in: Atom PDF