You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Database recovery isn't always complete after backup restore. In some cases it needs some additional steps. To prevent users from accessing database during these steps, it would be good to have a gbak/services option to leave the database in single user maintenance mode after restore.
The text was updated successfully, but these errors were encountered:
In some cases (for example, when index participating in FK fails to activate) this is already done. I.e. I agree that leaving DB in maintenance mode is good idea, the question is - after what errors this does not happen?
IIRC, only SYSDBA and database owner can connect to a database in this mode. Exactly because of this this mode is set for the database during restore process.
Submitted by: @aafemt
Database recovery isn't always complete after backup restore. In some cases it needs some additional steps. To prevent users from accessing database during these steps, it would be good to have a gbak/services option to leave the database in single user maintenance mode after restore.
The text was updated successfully, but these errors were encountered: