Good day colleagues,
We found in our database "dead" model - we cannot do nothing with that - neither open nor delete. And of course we cannot restore from backup by merge.
Checking DB by Admintool we found that there is something wrong with DB:
Did anybody get the same issue? Is any way to "optimize" DB?
Thanks!
Via ARIS Server Administrator, lock the DB, then run checkdb, then optimizedb, then unlock it
...and after checkdb also add checkreferences and then run optimizedb incl_archive. before you unlock the database again.
The document ReleaseNotes.pdf of ARIS 10.0 SR2c (located in the root folder of the ARIS DVD) explains the reason for repairing a database bug which might occur in ARIS 10.0, SR1, SR2, or SR2b.
Cheers
Rune
New problem but this time optimization did not help ((
Any ideas how to fix it?
And horror movie how this bug looks in ARIS
https://www.screencast.com/t/MKHGHjymk1le
And you cannot to do nothing with this model neither move nor delete
Did you request Gobal Support ARIS of Software AG to check and fix your database?
Cheers
Rune
Rune, I'm just asking here because the Global support is too slowly (we have access it of course), the last opened ticket performed for one month and as a result we were suggested to send DB to them... what unacceptable of course. So no, we were even not going to do this. I hope it should be standard method that will help us.
Regards,
Alex
It's hard to solve a technical issue in this forum, particularly, when our support already offered inspecting your database with our internal tools. Do you see any security risk in providing your database to our support?
Cheers
Rune
Rune, I agree that it is impossible to solve some problems, but you see first problem was solved in distance, second unfortunately not.
I don’t see any critical problem to give the base, but the Client sees. We cannot stop the project even for day just to fix DB (but it definitely will not be a day), what then should we do? If even the DB will be fixed, we should merge the data from the current (damaged) base to fixed base, that could damage it again. So it should be some local way to fix it.
I’m just worrying of two things:
1. Frequency of these problems emerging – the last one is the second case in two weeks.
2. Will these “dead” models inside the DB spread / affect or even generate new issues.
Anyway thanks for help.
If sending the database isn't an option for your customer, our support staff offer a remote session for inspecting the issue live in the system. Maybe this way they could be able to find the root cause why the database issues occurred in the first place.