Duplicated record number? Then Delete the 4DIndy
|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
 |
Duplicated record number? Then Delete the 4DIndy
by Allan Udy (Golden Micro)
::
Rate this Message:
We have an overnight procedure that automatically calls the 'VERIFY DATA FILE' command to check that the datafile is OK. A couple of weeks ago after one nightly run the verification report came back with an error (and has continued to do so every night): >Problem on page # 71 in B-tree Index 1 on stamp (stamp) index : >Key references a duplicated record number (24;126) The database was/is running on Windows, 4D Server 11.4 (HF4). A compiled and merged server application, and there is NO field called 'stamp' in the entire database... We tried the usual fixes... 1. Running an MSC 'Repair' routine did not correct the issue. 2. A 'manual' check of the entire datafile failed to find a duplicate record number in any of the tables (used Selection To Array then stepped through all record numbers returned). 3. A 'manual' check of the entire datafile failed to find any duplicate values in any of the half dozen or so fields that have the Unique attribute set. I asked local (Oz) tech support to escalate a call to Tech Support in France to find out in what situations the error message quoted above is generated. Got no response from France. I wasn't trying to report a bug, nor was I trying to get someone to fix my problem -- all I wanted was some additional information about the error message (which I couldn't find elsewhere) so that I might be able to track down the root cause myself. After the amount of time I wasted on this, and the relatively simple fix that I eventually discovered on my own, I'll pretty annoyed that there was no help forthcoming from tech support (France). Especially when we've been paying Solutions Partners fees for over 15 years :-( So the next step was to update my version 6.7 routines to do a complete automated text export of data and then allow the user to do an automated import of all the files. Updated the methods to either spit out individual blob/picture files which would be automatically re-imported into the correct fields during the import process, or allow those tables to be exported in internal record format (Send Record) . Much time spent updating the code and much spent on testing it worked correctly. Ran a test on the full 13gb datafile to check that the export/import fixed the problem. Five of 40 tables were exported in internal record format due to blobs/pictures. Imported the data. Ran verification - failed. SAME PROBLEM still exists in new datafile :-( Went through the five tables that were saved as internal record files, deleted all records in the table and ran verification checks again. ALWAYS failed -- same error as above. Was about to do a full 13Gb export/import again, forcing ALL tables to be exported to text files when I suddenly had another thought. Opened the database and created a new empty datafile, and did NOT import any of the data. The database automatically created two records in two tables, otherwise the datafile was completely new and empty. Ran a verification check. SAME PROBLEM still exists!!!! At this point it became more or less 'obvious' that the issue MUST have something to do with the structure rather than the data, so I deleted the .4DIndy file and let the system recreate it. Problem solved. Immense relief and anguish!! Would have been nice if someone in France could have suggested this earlier in the piece. Would be nice if the error messages were to be made a little more readable/intelligent, and if a detailed list of how and when such verification errors are generated so that we can hopefully track down issues like this more easily. With any luck this message (as posted to the 4D NUG) might save someone else the hassle that I went through to reach this point. Cheers Allan -- Allan Udy :: Software Development + Video Production Golden Micro Solutions Ltd Box 590, Blenheim 7240, New Zealand http://www.golden.co.nz ********************************************************************** Get the speed and power of 4D v11 SQL before upgrade prices increase - http://www.4d.com 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4D.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4D_Tech-Unsubscribe@... ********************************************************************** |
|
|
Re: Duplicated record number? Then Delete the 4DIndy
by psmith-3
::
Rate this Message:
Allan,
Thanks for the information. One of our customers experienced this too. We tried a lot of things like you did and never solved it. We just assumed it was an error in the MSC verification routines, since this did not appear to cause any problems. The problem did eventually go away. Now I know why: I did, at some point, delete the .indy file, though not with the intent of trying to fix that particular problem. I'm still not comfortable with v11 in real world use. Thanks, Paul Smith TSE International > We have an overnight procedure that automatically calls the 'VERIFY > DATA FILE' command to check that the datafile is OK. > > A couple of weeks ago after one nightly run the verification report > came back with an error (and has continued to do so every night): ********************************************************************** Get the speed and power of 4D v11 SQL before upgrade prices increase - http://www.4d.com 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4D.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4D_Tech-Unsubscribe@... ********************************************************************** |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |
