March 14, 2018 at 5:59 am
Using SQL 2014 Enterprise, for my AlwaysOn Availability Group -- I have everything setup and running fine on a 2-node cluster w/ 1 AG pointing to 1 Listener. (AG1 includes 2 databases called DB1 and DB2)
Now, I want to add a 2nd AG as our Vendor wants to isolate the DB's into 2 distinct AoAG's (DB1, DB2 in AG1 -- and -- DB3, DB4 in AG2)
I'm receiving an error when I setup the 2nd AG.. On that 4th tab, Add Listener. ERROR: "The WSFC resource control API returned error code 5057"
Is it possible to add a 2nd AG using the same listener as the 1st AG?
March 14, 2018 at 6:30 am
Express12 - Wednesday, March 14, 2018 5:59 AMUsing SQL 2014 Enterprise, for my AlwaysOn Availability Group -- I have everything setup and running fine on a 2-node cluster w/ 1 AG pointing to 1 Listener. (AG1 includes 2 databases called DB1 and DB2)Now, I want to add a 2nd AG as our Vendor wants to isolate the DB's into 2 distinct AoAG's (DB1, DB2 in AG1 -- and -- DB3, DB4 in AG2)
I'm receiving an error when I setup the 2nd AG.. On that 4th tab, Add Listener. ERROR: "The WSFC resource control API returned error code 5057"
Is it possible to add a 2nd AG using the same listener as the 1st AG?
You cannot use same listener.
March 15, 2018 at 8:30 am
thanks for your reply. I requested 2 new IP's (as we use multi-subnet failover from 1 data center to another w/ D-DNS) and your info set me straight. My 2nd Listener now has a unique Listener name w/ 2 new, additional IP's defined to it.. All is working fine.. Thanks again!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply