Skip to content

Not enough information in replication log on error #8415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SENikitin opened this issue Jan 29, 2025 · 0 comments
Open

Not enough information in replication log on error #8415

SENikitin opened this issue Jan 29, 2025 · 0 comments

Comments

@SENikitin
Copy link

  1. 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
  2. Database AR2.FDB - has some inconsistent structure (it is not a clone of master database, so it cannot be used in replication)
  3. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant