Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 8 of 8 total |
Corrupt DBISAM 3 Table |
Mon, Feb 11 2008 4:11 PM | Permanent Link |
Stuart Kelly | Hi all,
I've posted a seriously corrupt table from DBISAM 3. I tried to repair it, using the Database System Utility but I got a floating point error. This was from a computer running Microsoft Windows XP, with a FAT32 partition, which we recently converted to NTFS. The customer, has reported that the computer restarts intermittently, so it could be a memory/hard drive problem. Anyway, I thought I'd post it as an example for you all! Enjoy Stu |
Mon, Feb 11 2008 4:43 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Stuart,
<< Anyway, I thought I'd post it as an example for you all! >> Do you need it to be fixed ? Not promising that it can be, but it may be possible. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Feb 11 2008 5:06 PM | Permanent Link |
"Rita" | "Stuart Kelly" <stuart@nospam.com> wrote in message news:1DDAEA25-8253-4026-B72C-276DE74F2460@news.elevatesoft.com... > Hi all, > > I've posted a seriously corrupt table from DBISAM 3. I tried to repair > it, using the > Database System Utility but I got a floating point error. Its only the 1st 15 records that are corrupt their are 13,532 records in total its a uk table with £££££££££££££ would you like it back ? Rita |
Mon, Feb 11 2008 6:10 PM | Permanent Link |
"Rita" | The 1st 15 are not numbered 1-15 I think they attached themselves
to the table. Also 65 records from record id 9,000 to 9,065 seem to be corrupt. Maybe someone got a virus but I love conspiracies Apart from that I cant help. Rita "Stuart Kelly" <stuart@nospam.com> wrote in message news:1DDAEA25-8253-4026-B72C-276DE74F2460@news.elevatesoft.com... > Hi all, > > I've posted a seriously corrupt table from DBISAM 3. I tried to repair > it, using the > Database System Utility but I got a floating point error. > > This was from a computer running Microsoft Windows XP, with a FAT32 > partition, which we > recently converted to NTFS. The customer, has reported that the computer > restarts > intermittently, so it could be a memory/hard drive problem. > > > Anyway, I thought I'd post it as an example for you all! > > Enjoy Stu > |
Tue, Feb 12 2008 8:17 AM | Permanent Link |
Stuart Kelly | >
> Do you need it to be fixed ? Not promising that it can be, but it may be possible. > No I posted as an example. We had most of the data because records are copied to a remote database server, during the day. Rita, thanks for the recovered records, I'll keep them in case the customer complains. Cheers Stu |
Tue, Feb 12 2008 4:25 PM | Permanent Link |
=?iso-8859-1?Q?Luis_Concepci=F3n?= | Just wondering...
How do you 'fix' those corrupted tables that can't be fixed with the tablr repair? Some customers (only two in last 3 years) have send us corrupted tables and we were not able to fix them Customers know that they have the obligation of making backups, but I was wondering is there is any method to fix this kind of corruptions. Maybe a pretty customer kiss me someday if I fix her tables "Rita" <no@no.com> escribió en el mensaje de noticias:E0B24195-7484-45D2-B78C-CA0389101F4F@news.elevatesoft.com... > The 1st 15 are not numbered 1-15 I think they attached themselves > to the table. > Also 65 records from record id 9,000 to 9,065 seem to be corrupt. > Maybe someone got a virus but I love conspiracies > Apart from that I cant help. > Rita > > "Stuart Kelly" <stuart@nospam.com> wrote in message > news:1DDAEA25-8253-4026-B72C-276DE74F2460@news.elevatesoft.com... >> Hi all, >> >> I've posted a seriously corrupt table from DBISAM 3. I tried to repair >> it, using the >> Database System Utility but I got a floating point error. >> >> This was from a computer running Microsoft Windows XP, with a FAT32 >> partition, which we >> recently converted to NTFS. The customer, has reported that the computer >> restarts >> intermittently, so it could be a memory/hard drive problem. >> >> >> Anyway, I thought I'd post it as an example for you all! >> >> Enjoy Stu >> > > |
Tue, Feb 12 2008 5:44 PM | Permanent Link |
"Rita" | "Luis Concepción" <santyweb@hotmail.com> wrote in message news:3C1C0A55-6AD4-4C0D-A1AF-45317385F05A@news.elevatesoft.com... > > Maybe a pretty customer kiss me someday if I fix her tables > > I doubt it very much if a lady would have to ask for anything to be fixed. Ladies as in wives and mother's are the world's leading authorities on everything just ask your mum or wife. For corrupt anything just use a Hex editor Stu had already said it was a floating point error and the 1st 15 records in the file before the autoinc ID 1 read 200,000,000 plus so I figured remove them then the file stopped at about 9,948 and I had already found 13,000 + present so I looked from 9.948 and found 65 or so corrupted meaningless records so I removed them. The whole thing could have been avoided if whoever caused the problem at the time owned up. I dont think they lost much and would not have lost anything if staff would just shoulder the blame. I bet like Uddo Tim got the blame ;-( Rita |
Wed, Feb 13 2008 5:07 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Luis,
<< How do you 'fix' those corrupted tables that can't be fixed with the tablr repair? Some customers (only two in last 3 years) have send us corrupted tables and we were not able to fix them >> Sometimes there really is no way to repair the corruption because Windows has thoroughly overwritten portions of the file with "junk" from other areas of the file system. The best solution to the problem is to take measures to ensure that backups are regularly done and that you use the OS buffer flushing in DBISAM to prevent this sort of issue, especially with single-user installations where the data is stored locally on the user's computer. << Maybe a pretty customer kiss me someday if I fix her tables >> I would say that would depend highly on whether she found you worthy of a kiss *prior* to you fixing her tables. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, April 24, 2024 at 11:07 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |