Bug #6027

Database recovery failure

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

Status:ClosedStart date:2015-09-10
Priority:1Due date:2015-09-10
Assignee:Kalle Kondelin% Done:

100%

Category:DB clientEstimated time:4.00 hours
Target version:1.18.4Spent time:-
Release notes:Fixed an error with database recovery. Database recovery failed if database server had not exited successfully at least once. This special case is now handled correctly.
Tags: db, server, recovery
Story points-
Velocity based estimate-
ReleaseSimantics 1.18.4Release relationshipAuto

Description

Marko reported database recovery failure with Sulca 5.0. He delivered the failed work space. I was able to manually recover the database. This is an attempt to fix the aforementioned failure during automatic recovery.

Associated revisions

Revision 31685
Added by Kalle Kondelin over 2 years ago

Refs #6027. Database recovery failure.

Revision 31696
Added by Tuukka Lehtonen over 2 years ago

Merged trunk@r31685 to branches/simantics-1.18 on 2015-09-21 for 1.18.4 release.

refs #6027

Revision 31697
Added by Tuukka Lehtonen over 2 years ago

Merging scripts.

refs #6025
refs #6027

History

#1 Updated by Tuukka Lehtonen over 2 years ago

Kalle, should these be merged to 1.18?

#2 Updated by Kalle Kondelin over 2 years ago

Yes, this fix should work for 1.18 also.

#3 Updated by Tuukka Lehtonen over 2 years ago

  • Target version changed from 1.19.0 to 1.18.4
  • Release changed from 25 to 36

Merged to 1.18 for 1.18.4.

#4 Updated by Tuukka Lehtonen over 2 years ago

  • Tags set to db, server, recovery
  • Status changed from Feedback to Closed

#5 Updated by Kalle Kondelin over 2 years ago

  • Release notes set to Fixed an error with database recovery. Database recovery failed if database server had not successfully exited at least once. This special case is now handled correctly.

#6 Updated by Kalle Kondelin over 2 years ago

  • Release notes changed from Fixed an error with database recovery. Database recovery failed if database server had not successfully exited at least once. This special case is now handled correctly. to Fixed an error with database recovery. Database recovery failed if database server had not exited successfully at least once. This special case is now handled correctly.

Also available in: Atom PDF