• State Suggested Answer
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 95 subscribers
  • Views 86 views
  • Users 0 members are here
Options
Related

Cannot Connect to database because a system update is running.

sherif elaassar
8 hours ago

Hello Guys,

I have a customer environment and it was working fine, then suddenly when I try to open any of the admin tools, it keeps telling me "Cannot connect to database because a system update is running".

It has been into this state now for 2 days and still the update is not finished and I cannot find any service or app running in the background to update.

Also, I don't have access on the DB Server to execute anything on the SQL Server Management Studio as this is a production DB and the customer has concerns about giving access to it.

if anyone has any clue, I would be so grateful.

I'm using OneIdentity Manager 9.2.1

Parents
  • 0 8 hours ago

    Hi,

    I have seen this 'occasionally' in non-prod environments.  Have someone check the value of 'UpdatePhase' on DialogDatabase.  If it's anything other than 0 then that could be the cause of the issue.  Have you applied any recent updates/patches to the DB?  If yes, the system will try to apply these updates to servers running the tools.  If there are tools still open on those servers, the updates will be blocked.

    In a non-prod environment, after checking everything and convincing myself that no update is/should be running I would update 'UpdatePhase' to 0.

    In prod I've never had to do that so best to check around if an update is 'stuck'.  You could get someone to check XDateUpdated/XDateInserted on QBMFileRevision to see if any updates have been applied to the DB.

    HTH, Barry.

Reply
  • 0 8 hours ago

    Hi,

    I have seen this 'occasionally' in non-prod environments.  Have someone check the value of 'UpdatePhase' on DialogDatabase.  If it's anything other than 0 then that could be the cause of the issue.  Have you applied any recent updates/patches to the DB?  If yes, the system will try to apply these updates to servers running the tools.  If there are tools still open on those servers, the updates will be blocked.

    In a non-prod environment, after checking everything and convincing myself that no update is/should be running I would update 'UpdatePhase' to 0.

    In prod I've never had to do that so best to check around if an update is 'stuck'.  You could get someone to check XDateUpdated/XDateInserted on QBMFileRevision to see if any updates have been applied to the DB.

    HTH, Barry.

Children