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
master replication config has sync entry for source database e:\DB\FB5\MASTER1.FDB
sync_replica=sysdba:[email protected]/3055:e:/DB/FB5/AR2.FDB
Database AR2.FDB - has some inconsistent structure (it is not a clone of master database, so it cannot be used in replication)
Client on master database do some stuff and it produce an error in replication and replication log now have "a description":
DESKTOP-5UMMDAU (primary) Wed Jan 29 12:23:36 2025
Database: E:\DB\FB5\MASTER1.FDB
ERROR: unsuccessful metadata update
ALTER INDEX RDB$PRIMARY27 failed
Index not found
As you can see there are no information about real source of problem.
Here can be something like this:
DESKTOP-5UMMDAU (primary) Wed Jan 29 12:23:36 2025
Database: E:\DB\FB5\MASTER1.FDB
ERROR: unsuccessful metadata update on sync replica 127.0.0.1/3055:e:/DB/FB5/AR2.FDB
ALTER INDEX RDB$PRIMARY27 failed
Index not found
or
DESKTOP-5UMMDAU (primary) Wed Jan 29 12:23:36 2025
Database: E:\DB\FB5\MASTER1.FDB
Sync replica: 127.0.0.1/3055:e:/DB/FB5/AR2.FDB
ERROR: unsuccessful metadata update
ALTER INDEX RDB$PRIMARY27 failed
Index not found
The text was updated successfully, but these errors were encountered:
sync_replica=sysdba:[email protected]/3055:e:/DB/FB5/AR2.FDB
As you can see there are no information about real source of problem.
Here can be something like this:
or
The text was updated successfully, but these errors were encountered: