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
A "deadlock at trigger RDB$TRIGGER_9" error can be reported by GBAK when restoring a database under non-SYSDBA credentials. This usually happens while privileges for views are being restored.
This is caused by reading the column RDB$SECURITY_CLASS in a no-record-version transaction A after it has been updated by an active transaction B (GBAK restores tables and views/procedures in two separate transactions).
Submitted by: @dyemanov
A "deadlock at trigger RDB$TRIGGER_9" error can be reported by GBAK when restoring a database under non-SYSDBA credentials. This usually happens while privileges for views are being restored.
This is caused by reading the column RDB$SECURITY_CLASS in a no-record-version transaction A after it has been updated by an active transaction B (GBAK restores tables and views/procedures in two separate transactions).
Commits: 83f78f5
The text was updated successfully, but these errors were encountered: