question

HabtamuBeneberu-0184 avatar image
0 Votes"
HabtamuBeneberu-0184 asked HabtamuBeneberu-0184 edited

Replication - Unable to redirect an AG publisher to the AG Listener

I have setup SQL 2019 (RTM-CU12)) AG distributor and it seems to work fine. Failover of the distributor does not affect replication.
I have setup SQL 2014 (SP3-CU4) AG publisher and replication seems to work fine.

I run the stored procedure sp_redirect_publisher to associate the original publisher and the published database with the availability group listener name of the publisher availability group. I run validation using sys.sp_validate_replica_hosts_as_publishers and I get the publisher's listener DNS name as expected.

However, After failover, the Log Reader Agent is still trying to read from the former Primary database which is not accessible.

Any idea?

Thanks Geto

sql-server-generalsql-server-transact-sql
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AmeliaGu-msft avatar image
0 Votes"
AmeliaGu-msft answered HabtamuBeneberu-0184 commented

Hi HabtamuBeneberu-0184,

Welcome to Microsoft Q&A.
Is distributor part of Always On?
If so, please refer to Configuring SQL Server replication for distribution databases in SQL Server Always On Availability Groups and Set up replication distribution database in Always On availability group, which might be helpful.

Best Regards,
Amelia


If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, both distributor and publisher are in AG.

I have setup several similar systems recently. It is my first time experiencing this issue.

SQL 2014 SP3-CU4 pub and SQL 2019 RTM-CU12 DIST: Is there a known issue with this combination?

0 Votes 0 ·