How to repair mongodb collection when index is corrupt?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















Mongo version: 2.6 I think one or more of my MongoDB index is corrupt which is not letting me delete the corrupt collection or make a backup with mongodump



Below is the error i get when i try to execute drop



>db.notifications.drop()
"$err" : "no NamespaceDetails for index: { name: "_id_", ns: "Bnk.notifications", key: { _id: 1 }, v: 0 }",
"code" : 17329


What can be done to get this collection removed or repaired if possible ?










share|improve this question














bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















    0















    Mongo version: 2.6 I think one or more of my MongoDB index is corrupt which is not letting me delete the corrupt collection or make a backup with mongodump



    Below is the error i get when i try to execute drop



    >db.notifications.drop()
    "$err" : "no NamespaceDetails for index: { name: "_id_", ns: "Bnk.notifications", key: { _id: 1 }, v: 0 }",
    "code" : 17329


    What can be done to get this collection removed or repaired if possible ?










    share|improve this question














    bumped to the homepage by Community 5 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      Mongo version: 2.6 I think one or more of my MongoDB index is corrupt which is not letting me delete the corrupt collection or make a backup with mongodump



      Below is the error i get when i try to execute drop



      >db.notifications.drop()
      "$err" : "no NamespaceDetails for index: { name: "_id_", ns: "Bnk.notifications", key: { _id: 1 }, v: 0 }",
      "code" : 17329


      What can be done to get this collection removed or repaired if possible ?










      share|improve this question














      Mongo version: 2.6 I think one or more of my MongoDB index is corrupt which is not letting me delete the corrupt collection or make a backup with mongodump



      Below is the error i get when i try to execute drop



      >db.notifications.drop()
      "$err" : "no NamespaceDetails for index: { name: "_id_", ns: "Bnk.notifications", key: { _id: 1 }, v: 0 }",
      "code" : 17329


      What can be done to get this collection removed or repaired if possible ?







      mongodb linux ubuntu mongo-repair






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 8 '18 at 14:02









      satch_boogiesatch_boogie

      1256




      1256





      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Try to repair it by using repairDatabase.



          More information:
          https://docs.mongodb.com/manual/reference/command/repairDatabase/






          share|improve this answer
























          • it failed with same error

            – satch_boogie
            Mar 12 '18 at 6:17












          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%2f199718%2fhow-to-repair-mongodb-collection-when-index-is-corrupt%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Try to repair it by using repairDatabase.



          More information:
          https://docs.mongodb.com/manual/reference/command/repairDatabase/






          share|improve this answer
























          • it failed with same error

            – satch_boogie
            Mar 12 '18 at 6:17
















          0














          Try to repair it by using repairDatabase.



          More information:
          https://docs.mongodb.com/manual/reference/command/repairDatabase/






          share|improve this answer
























          • it failed with same error

            – satch_boogie
            Mar 12 '18 at 6:17














          0












          0








          0







          Try to repair it by using repairDatabase.



          More information:
          https://docs.mongodb.com/manual/reference/command/repairDatabase/






          share|improve this answer













          Try to repair it by using repairDatabase.



          More information:
          https://docs.mongodb.com/manual/reference/command/repairDatabase/







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 8 '18 at 14:57









          fetch_execute_breakfetch_execute_break

          275




          275













          • it failed with same error

            – satch_boogie
            Mar 12 '18 at 6:17



















          • it failed with same error

            – satch_boogie
            Mar 12 '18 at 6:17

















          it failed with same error

          – satch_boogie
          Mar 12 '18 at 6:17





          it failed with same error

          – satch_boogie
          Mar 12 '18 at 6:17


















          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%2f199718%2fhow-to-repair-mongodb-collection-when-index-is-corrupt%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

          Liste der Baudenkmale in Friedland (Mecklenburg)

          Single-Malt-Whisky

          Czorneboh