5 Replies Latest reply on May 5, 2010 6:20 AM by Oliver

    WARNING: problems were detected while recovering the database.

    Oliver

      Title

      WARNING: problems were detected while recovering the database.

      Post

      Using:

      FileMaker Pro Advanced 11.0v1

      Running on:

      Microsoft Windows XP
      Professional
      Version 2002
      Service Pack 2

      Background information:


      We have a database named "Schools Mailing List.fp7", which we keep on one of our servers and access from several computers within our building via our internal network. The database is maybe 5 or 6 years old, having previously been used and updated in versions of FileMaker going at least as far back as version 8. It has 30 tables, the most important one containing 46,545 records. The database file is just under 0.5 GB in size.

      The problem:


      I don't know if this is relevant, but I have this week been doing some cleaning up of the values stored in the main table: mostly removing superfluous spaces and return characters. Since it was fairly basic string manipulation on a number of fields at the same time, I thought it would be easiest to use a text editor. I did various exports of the 46,545 records as CSV files, did some string manipulations on them, and then reimported the modified values. I seem to remember that I got an out-of-memory alert at one point, but I sorted that out and reimported the data without anything seeming to go wrong.

      While I was examining the data, I noticed that a small number of fields for a small number of records in the table had acquired very peculiar values that had nothing to do with the string manipulations that I was doing. (In one record out of the 46,545, an address field somehow changed counties, and in another record at another time, the postcode changed.)

      The database still seems to work perfectly well, but the unexpected values made me wonder if it might have become damaged. So yesterday I made a local copy of the database and ran the "Recover" feature on it. The recovery process ended with the following warning:

      "WARNING: problems were detected while recovering the database.  The recovered file should NOT be used going forward; copy only the most recent work from it into a backup copy of the original file."

      "Recover.log" contained this warning and added that there were "5 item(s) modified". (I have appended some excerpts from "Recover.log" below, in case they are helpful.)

      Unfortunately, our backup of the database is in the same position: it seems to work perfectly well, but if I "recover" it, the same warning is generated.

      The question:

      Does this mean that the database is damaged? If so, what problems can I expect to see, and is there anything that I can do about them?

      Thank you.














        • 1. Re: WARNING: problems were detected while recovering the database.
          Oliver

          APPENDIX: Excerpts from "Recover.log":

          2010-04-28 09:34:31.385 +0100    Schools Mailing List.fp7    0    *** Started consistency check of improperly closed file, total of 123588 block(s) to check
          2010-04-28 09:34:37.074 +0100    Schools Mailing List.fp7    0    *** Completed consistency check, checked 123588 block(s)
          2010-04-29 08:48:00.164 +0100    Schools Mailing List.fp7    0    *** Started consistency check of improperly closed file, total of 123579 block(s) to check
          2010-04-29 08:48:01.883 +0100    Schools Mailing List.fp7    8443    Data page 34573 has the parent of begin hierarchy issue (ignorable)
          2010-04-29 08:48:05.789 +0100    Schools Mailing List.fp7    0    *** Completed consistency check, checked 123579 block(s)
          2010-04-29 08:49:56.773 +0100    Schools Mailing List.fp7    0    *** Started consistency check, total of 123579 block(s) to check
          2010-04-29 08:49:58.491 +0100    Schools Mailing List.fp7    8443    Data page 34573 has the parent of begin hierarchy issue (ignorable)
          2010-04-29 08:50:02.304 +0100    Schools Mailing List.fp7    0    *** Completed consistency check, checked 123579 block(s)
          2010-04-29 08:50:48.850 +0100    Schools Mailing List.fp7    0    *** Started recovery of 'Schools Mailing List.fp7'
          2010-04-29 08:50:48.850 +0100    Schools Mailing List.fp7    0    Scanning blocks and rebuilding file...
          2010-04-29 08:50:52.866 +0100    Schools Mailing List.fp7    0    Scan complete, found 122941 page(s) to process
          2010-04-29 08:51:55.583 +0100    Schools Mailing List.fp7    0    Rebuild processed 122941 page(s), completing end of file
          2010-04-29 08:51:57.474 +0100    Schools Mailing List.fp7    0    Completed copy or rebuild of file blocks
          2010-04-29 08:51:57.536 +0100    Schools Mailing List.fp7    0    Recovering: font catalog


          [...]

          2010-04-29 09:32:19.430 +0100    Schools Mailing List.fp7    0      Recovering data for table 'Annual_Registration'
          2010-04-29 09:32:19.524 +0100    Schools Mailing List.fp7    0      Evaluating library (134)
          2010-04-29 09:32:19.524 +0100    Schools Mailing List.fp7    0      Recovering: field 'ID' (1)
          2010-04-29 09:32:19.524 +0100    Schools Mailing List.fp7    0      Recovering: field 'Year' (2)
          2010-04-29 09:32:19.539 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.539 +0100    Schools Mailing List.fp7    8477      Calculation modified
          2010-04-29 09:32:19.555 +0100    Schools Mailing List.fp7    8476        This item changed


          [The field "Year" is an "Auto-Enter" field with a "Calculated value" specified in the original database as follows:

          ${Schools=39- Essex}::Current_Year

          and in the recovered database as follows:

          ${Schools=39- Essex}::${Current_Year}

          The only change is that the field name has been placed in curly brackets with a dollar sign before it.]

          [... same table...]

          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    0      Recovering: field 'letter_enclosed_templates' (22)
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8477      Calculation modified
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8476        This item changed


          [The field "letter_enclosed_templates" is an "Unstored" "Calculation" field, defined in the original database as follows:

          Substitute(
           Substitute(
            Substitute(
             Substitute(
              Substitute(
                Substitute(
                Substitute(
                Substitute(
                 EMail_Templates::letter_enclosed_templates;
                 "$ID";School_Production_ID
                 );
                "$CHEQUE";Production_2008::Cheques_Payable_To
                );
               "$CHARITY";Production_2008::School_Fund
               );
              "$SCHOOLNAME";${Schools=39- Essex}::School Name
              );
             "$ORGNAME";Organiser_Name
              );
             "$ORGEMAIL";Organiser_Email
            );
            "$ORGTEL";Organiser_Tel
            );
            "$CLASSBAGS";Production_2008::Number_Of_Classes
          )

          and in the recovered database as follows:

          Substitute(
           Substitute(
            Substitute(
             Substitute(
              Substitute(
                Substitute(
                Substitute(
                Substitute(
                 EMail_Templates::letter_enclosed_templates;
                 "$ID";School_Production_ID
                 );
                "$CHEQUE";Production_2008::<Field Missing>
                );
               "$CHARITY";Production_2008::<Field Missing>
               );
              "$SCHOOLNAME";${Schools=39- Essex}::${School Name}
              );
             "$ORGNAME";Organiser_Name
              );
             "$ORGEMAIL";Organiser_Email
            );
            "$ORGTEL";Organiser_Tel
            );
            "$CLASSBAGS";Production_2008::<Field Missing>
          )

          Some fields are missing in the recovered database, because it was created from my local copy of the database, which isn't connected to the other databases. Other than that, the only change is to "School Name". Again, the field name has been placed in curly brackets with a dollar sign before it.]

          [... same table...]

          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    0      Recovering: field 'RM_Dispatch_File' (25)
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8486      Reset field formatting
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8477      Calculation modified
          2010-04-29 09:32:19.570 +0100    Schools Mailing List.fp7    8476        This item changed


          [The field "RM_Dispatch_File" is an "Unstored" "Calculation" field, defined in the original database as follows:

          "ADD¶" &
          "MSCCS" & School_Production_ID & "¶" &
          Trim(${Schools=39- Essex}::School Name) & "¶" &
          "¶" &
          Substitute(Trim(Organiser_Name);"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::Adress_Line_1);"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::Adress_Line_2);"¶";"") & "¶" &
          "¶" &
          Substitute(Trim(${Schools=39- Essex}::Adress_Line_3);"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::School Postcode);"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::Adress_Line_5);"¶";"") & "¶" &
          Case(Number_Of_Templates<=4;"CRL02";Number_Of_Templates>=5 and Number_Of_Templates<=22;"TP201") & "¶" &
          "¶" &
          (207 * Number_Of_Templates) & "¶" &
          "¶" &
          "¶" &
          "¶" &
          Case(Number_Of_Templates<=4;"P";Number_Of_Templates>=5 and Number_Of_Templates<=22;"")

          and in the recovered database as follows:

          "ADD¶" &
          "MSCCS" & School_Production_ID & "¶" &
          Trim(${Schools=39- Essex}::${School Name}) & "¶" &
          "¶" &
          Substitute(Trim(Organiser_Name);"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::${Adress_Line_1});"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::${Adress_Line_2});"¶";"") & "¶" &
          "¶" &
          Substitute(Trim(${Schools=39- Essex}::${Adress_Line_3});"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::${School Postcode});"¶";"") & "¶" &
          Substitute(Trim(${Schools=39- Essex}::${Adress_Line_5});"¶";"") & "¶" &
          Case(Number_Of_Templates<=4;"CRL02";Number_Of_Templates>=5 and Number_Of_Templates<=22;"TP201") & "¶" &
          "¶" &
          (207 * Number_Of_Templates) & "¶" &
          "¶" &
          "¶" &
          "¶" &
          Case(Number_Of_Templates<=4;"P";Number_Of_Templates>=5 and Number_Of_Templates<=22;"")

          Again, various field names have been "escaped", as previously.]

          [...]














































































          • 2. Re: WARNING: problems were detected while recovering the database.
            Oliver

            APPENDIX: Excerpts from "Recover.log" (contd.):

            2010-04-29 09:32:19.820 +0100    Schools Mailing List.fp7    0      Recovering data for table 'Marketing_Event'
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Evaluating library (140)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Marketing_Event_PK' (1)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'School_ID_FK' (2)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Year' (3)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Created_Date' (4)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Marketing_Type' (5)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Date_Sent' (6)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Note' (7)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Created_By_User' (8)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Marketing_Code' (9)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Respose_Received' (10)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Marketing_Medium_FK' (11)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Marketing_Subtype_FK' (12)
            2010-04-29 09:32:20.867 +0100    Schools Mailing List.fp7    0      Recovering: field 'Project_Type_FK' (13)
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    0      Recovering: field 'Marketing_Event_Status_FK' (14)
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    0      Recovering: field 'Sheduled' (15)
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    0      Recovering: field 'Actioned' (16)
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    0      Recovering: field 'Closed' (17)
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    0      Recovering: field 'School_Name' (18)
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    8477      Calculation modified
            2010-04-29 09:32:20.883 +0100    Schools Mailing List.fp7    8476        This item changed


            [The field "School_Name" is an "Unstored" "Calculation" field, defined in the original database as follows:

            Case (
            ${Schools=39- Essex}::School Name  ? "";${Schools=39- Essex}::School Name;
            ${Schools=39- Essex}::Harvested_School Name  ? "" ; ${Schools=39- Essex}::Harvested_School Name ;
            "No organisation name available" )

            and in the recovered database as follows:

            Case (
            ${Schools=39- Essex}::${School Name}  ? "";${Schools=39- Essex}::${School Name};
            ${Schools=39- Essex}::${Harvested_School Name}  ? "" ; ${Schools=39- Essex}::${Harvested_School Name} ;
            "No organisation name available" )

            Again, field names have been "escaped".]

            [...]

            2010-04-29 09:32:21.164 +0100    Schools Mailing List.fp7    0      Recovering data for table 'Diary_Entries'
            2010-04-29 09:32:21.164 +0100    Schools Mailing List.fp7    0      Evaluating library (154)
            2010-04-29 09:32:21.164 +0100    Schools Mailing List.fp7    0      Recovering: field 'Primary_Key' (1)
            2010-04-29 09:32:21.164 +0100    Schools Mailing List.fp7    0      Recovering: field 'Notes' (2)
            2010-04-29 09:32:21.164 +0100    Schools Mailing List.fp7    0      Recovering: field 'Another_Call_Sheduled' (3)
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    0      Recovering: field 'School_FK' (5)
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    0      Recovering: field 'Created' (6)
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    0      Recovering: field 'Sheduled' (7)
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    0      Recovering: field 'Actioned' (8)
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    0      Recovering: field 'School_Name' (9)
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    8486      Reset field formatting
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    8477      Calculation modified
            2010-04-29 09:32:21.180 +0100    Schools Mailing List.fp7    8476        This item changed


            [The field "School_Name" is an "Unstored" "Calculation" field, defined in each database identically to the correpsonding field "School_Name" in the table "Marketing_Event".]

            [...]

            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    8495    WARNING: problems were detected while recovering the database.  The recovered file should NOT be used going forward; copy only the most recent work from it into a backup copy of the original file.
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0    File blocks: scanned and rebuilt 122941 block(s), dropped 0 invalid data block(s)
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0    Schema: scanned fields and tables; some problems were found...
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0      fields created to match record data: 0
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0      field values deleted due to invalid ID or repetition: 0
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0      records deleted due to invalid ID: 0
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0    Structure: scanned; 5 item(s) modified
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0    File size after recovery is 503361536 bytes
            2010-04-29 09:39:25.838 +0100    Schools Mailing List.fp7    0    *** Completed recovery to 'Schools Mailing List Recovered 1.fp7'





































            • 3. Re: WARNING: problems were detected while recovering the database.
              Oliver

              Does anybody have any ideas?

              • 4. Re: WARNING: problems were detected while recovering the database.
                RickWhitelaw

                While I can't say anything that hasn't been said before on this forum, I'd suggest searching the forum for "Recover". There's been quite a lot written on the topic.

                 

                RW

                • 5. Re: WARNING: problems were detected while recovering the database.
                  Oliver

                  I have done a search for "recover", and can agree that there has been a lot written on the very general topic of recovering files. The search page says that there are "200 discussions". I've looked through some, but haven't yet been able to find one that helps me with my specific problem. Reading through 200 discussion threads would take too long for that to be a feasible option.

                   

                  I went to a lot of trouble pulling out all the parts of my log file that looked as if they could be helpful in clarifying what had happened, as well as copying and pasting all the calculations that the log file indicated as having been changed, so that I could help those with more experienced eyes than mine to pinpoint what the issue was. So I was hoping that someone might be able to say something more specific.