Stuck Oldest unsent transaction in db mirroring












1















I am seeing some very strange behavior in db mirroring



For one of the databases, during the weekend when rebuild index job ran on the principal, it generated around 60 GB log.



Now its been 2 days and mirroring is not in sync. ON mirror it always showing synchronizing and seems to be DC in between.



When i monitor further i see oldest unsent transaction is always stuck at 2:10:07:20 and increasing with time while unrestored log starts with 60 GB goes to 0 and then starts showing again with 60 GB still pending.



Update@



I see couple of times every 5 min there is a Disconnected state logged in Mirroring_state column



Can someone please guide what can be an issue here and what to check?






sql-server sql-server-2016 mirroring







share|improve this question





























    1















    I am seeing some very strange behavior in db mirroring



    For one of the databases, during the weekend when rebuild index job ran on the principal, it generated around 60 GB log.



    Now its been 2 days and mirroring is not in sync. ON mirror it always showing synchronizing and seems to be DC in between.



    When i monitor further i see oldest unsent transaction is always stuck at 2:10:07:20 and increasing with time while unrestored log starts with 60 GB goes to 0 and then starts showing again with 60 GB still pending.



    Update@



    I see couple of times every 5 min there is a Disconnected state logged in Mirroring_state column



    Can someone please guide what can be an issue here and what to check?






    sql-server sql-server-2016 mirroring







    share|improve this question



























      1












      1








      1








      I am seeing some very strange behavior in db mirroring



      For one of the databases, during the weekend when rebuild index job ran on the principal, it generated around 60 GB log.



      Now its been 2 days and mirroring is not in sync. ON mirror it always showing synchronizing and seems to be DC in between.



      When i monitor further i see oldest unsent transaction is always stuck at 2:10:07:20 and increasing with time while unrestored log starts with 60 GB goes to 0 and then starts showing again with 60 GB still pending.



      Update@



      I see couple of times every 5 min there is a Disconnected state logged in Mirroring_state column



      Can someone please guide what can be an issue here and what to check?






      sql-server sql-server-2016 mirroring







      share|improve this question
















      I am seeing some very strange behavior in db mirroring



      For one of the databases, during the weekend when rebuild index job ran on the principal, it generated around 60 GB log.



      Now its been 2 days and mirroring is not in sync. ON mirror it always showing synchronizing and seems to be DC in between.



      When i monitor further i see oldest unsent transaction is always stuck at 2:10:07:20 and increasing with time while unrestored log starts with 60 GB goes to 0 and then starts showing again with 60 GB still pending.



      Update@



      I see couple of times every 5 min there is a Disconnected state logged in Mirroring_state column



      Can someone please guide what can be an issue here and what to check?






      sql-server sql-server-2016 mirroring




      sql-server sql-server-2016 mirroring






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 3 mins ago







      BeginnerDBA

















      asked 6 hours ago









      BeginnerDBABeginnerDBA

      5811417




      5811417






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233679%2fstuck-oldest-unsent-transaction-in-db-mirroring%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233679%2fstuck-oldest-unsent-transaction-in-db-mirroring%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          Ronny Ackermann

          Image
          Ronny Ackermann Nation Deutschland  Deutschland Geburtstag 16. Mai 1977 Geburtsort Bad Salzungen, DDR Größe 184 cm Gewicht ca. 69 kg Beruf Hauptfeldwebel bei der Bundeswehr Karriere Verein Rhöner WSV Dermbach Status zurückgetreten Karriereende 16. März 2011 Medaillenspiegel Olympische Medaillen 0 × 3 × 0 × WM-Medaillen 4 × 4 × 1 ×  Olympische Winterspiele 0 Silber 0 Salt Lake City 2002 Sprint 0 Silber 0 Salt Lake City 2002 Team 0 Silber 0 Turin 2006 Team  Nordische Skiweltmeisterschaften 0 Bronze 0 Lahti 2001 Einzel 0 Gold 0 Val di Fiemme 2003 Einzel 0 Silber 0 Val di Fiemme 2003 Sprint 0 Silber 0 Val di Fiemme 2003 Team 0 Gold 0 Oberstdorf 2005 Einzel 0 Gold 0 Oberstdorf 2005 Sprint 0 Silber 0 Oberstdorf 2005 Team 0 Gold 0 Sapporo 2007 Einzel 0 Silber 0 Sapporo 200...
          Read more

          Köttigit

          Image
          Köttigit Büscheliges Mineral-Aggregat aus weißen, nadeligen Köttigitkristallen; Fundort: Grube Silbereckle, Reichenbach, Lahr/Schwarzwald, Baden-Württemberg (Sichtfeld 8 mm) Allgemeines und Klassifikation Andere Namen Zinkarseniat Chemische Formel Zn 3 [AsO 4 ] 2 ·8H 2 O [1] Mineralklasse (und ggf. Abteilung) Phosphate, Arsenate und Vanadate System-Nr. nach Strunz und nach Dana 8.CE.40 (8. Auflage: VII/C.13) 40.03.06.05 Kristallographische Daten Kristallsystem monoklin Kristallklasse; Symbol monoklin-prismatisch; 2/ m Raumgruppe C 2/ m (Nr. 12) Vorlage:Raumgruppe/12 Gitterparameter a  = 10,24 Å; b  = 13,41 Å; c  = 4,76 Å β  = 105,2° [1] Formeleinheiten Z  = 2 [1] Häufige Kristallflächen {010}, {201}, Physikalische Eigenschaften Mohshärte 2 bis 3 [2] Dichte (g/cm 3 ) gemessen: 3,33; berechnet: 3.24 [2] Spaltbarkeit vollkommen nach {010} [2] Bruch; Tenazität faserig [3] ...
          Read more

          MySQL 8.0.15 starts normally but any connection hangs

          Image
          .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 0 I dropped a large table (80G) Friday morning and got a crash: InnoDB: ###### Diagnostic info printed to the standard error stream 2019-04-19T18:48:55.445507Z 0 [ERROR] [MY-012872] [InnoDB] Semaphore wait has lasted > 37617336 seconds. We intentionally crash the server because it appears to be hung.[FATAL] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung. 2019-04-19T18:48:55.445541Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:625 thread 140252955932416 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you g...
          Read more