EA13.0.1310 - EA Software Crash wipes project database (MySQL ODBC 5.3 Unicode)

[s.lenna.r.griffiths]

Hi All,

I have recently been using EA13.0.1310 on a legacy project (has been running for 5+ years) and encountered an issue where restoring a baseline (after a bad merge) resulted in the EA crashing and wiping the associated project from the database.

After talking to colleagues about the problem, it is not an entirely unknown issue where nominal operations (even just adding a new element) in older and longer running projects can cause EA to crash and wipe the associated project. However, steps to "consistently" repeat the issue have not been identifiable and sharing the associated project data for third party diagnostics in our case may not be a viable option.

MySQL Connector options:
 * Allow big result sets
 * Enable automatic reconnect

Has anyone else encountered this type of issue? If so, has anyone been able to identify what the trigger point might be?

[Geert Bellekens]

One of the things you might want to do on a regular basis is to run a Project Integrity Check.

Integrity errors have been known to lead to pretty disastrous consequences.

And of course upgrade to a more recent version (I recommend v15.2 for now)

Geert

[s.lenna.r.griffiths]

One of the things you might want to do on a regular basis is to run a Project Integrity Check.

Integrity errors have been known to lead to pretty disastrous consequences.

Thanks, I will pass on the recommendation to the team... perhaps after each backup/restore.

And of course upgrade to a more recent version (I recommend v15.2 for now)

Unfortunately, I believe that there will be little appetite to do this (wider implications beyond just the projects I am involved with), though I do agree upgrading EA would be a good thing to do.