Timeline for Could not obtain exclusive lock on database 'model' - who is using it?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 28, 2022 at 11:32 | comment | added | Kiquenet | How-to get more info about request_session_id ? | |
| Mar 21, 2022 at 15:11 | comment | added | sepupic | I repeat you one more time: it's not a good idea to backup all the databases at working hours, it's no matter if it is you or AWS RDS to do it. It's up to you to complain with AWS RDS and to re-schedule it. | |
| Mar 21, 2022 at 13:48 | comment | added | nateirvin | I'm aware that backing up the model database is a little odd and should be a quick operation. I'm saying the last time I ran into this kind of situation, that's what was going on - the managed service provider we host with (AWS RDS in this case) was backing up all the DBs and that one locked for a little while. | |
| Mar 18, 2022 at 5:51 | comment | added | sepupic | @nateirvin maybe you do not know the purpose of model db if you think that system processed could be interested in it, and you definitely have problems if you take a backup of system databases at work time and if it takes more then 1 second to backup model db | |
| Mar 18, 2022 at 4:45 | comment | added | nateirvin |
Be careful before you kill the session though - if model is locked due to a backup or some other system process, stop the session could do a lot of harm to your system. Check to see what user owns that session and what that user is doing before deciding whether to kill it or wait out the lock.
|
|
| May 10, 2021 at 7:29 | history | edited | Paul White♦ | CC BY-SA 4.0 |
The referenced "other answer" no longer exists. Incorporated comment.
|
| Sep 5, 2018 at 14:00 | vote | accept | Marcello Miorelli | ||
| Sep 5, 2018 at 13:23 | history | answered | sepupic | CC BY-SA 4.0 |