Hi, I'm just leaving for dinner so I can't help out now. For now do not touch the damaged database or hard drive of that computer. any new attempts could increase the damage as it may have originated in a damaged hard drive. You can copy the database to another computer and try to fix it there. I'll be back in about 7 hours and check back. any copies of previous backups should be copied as well to a new computer.
Best Regards, Mark To: [email protected] From: [email protected] Date: Mon, 11 Oct 2010 14:32:18 -0500 Subject: Re: [Dataperf] Error 154 Don, Since you couldn't even export the STR to an STE, that sounds like it was the STR file that was corrupted. If so, and you hadn't made any structure changes (other than reports) since your last backup, you might could have gotten away with just restoring the STR file and re-indexing. Ah well. As least you're getting good practice in data importing. :) I use DPBackup often while working on databases of important stuff. Especially before I do something like an import or modifying an important report. That way I can always 'undo' pretty painlessly if I shoot myself in the foot (which happens fairly regularly). I don't let it backup the index file and it works pretty quickly. Tim Rude "Don Friedman" <[email protected]> wrote in message news:aanlktinpnyup1a=m4yzepgph0uz6dqc6xu5u2i_qj...@mail.gmail.com...tim - thanks - yeah, I had looked it up but never before come across a circumstance where it was even impossible to rebuild the .str file. I was writing a modification of a report when it happened and can't imagine what I did if in fact it was anything I did do. And while I have backups of the sort of large database structure itself, I had just recently imported a million records in one panel, 600K in another and 500K in yet another and didn't have a current backup of the project in development. Once nothing else worked I simply started again and am re-importing the voter data. This time I'll be backing up in stages, that you can count on! Generally I back these large databases up once I've finalized them for the election cycle and have them in multiple places. As it is I'll be doing this until the wee hours to catch up to where I was supposed to be which was already behind schedule. Oh well, the wonderful part about elections is that win or lose they have a definite ending date. Thanks. Don 2010/10/11 Tim Rude <[email protected]> Don, I'm sure you've already looked up Error 154 meaning, but just in case you haven't... Error 154 - Attempt to read block 0 as text. The file DataPerfect is trying to read is corrupt or not a valid format. Restore from backup. If there is no backup, try deleting the .IND file, exporting all data, deleting panel files and .TXX file, importing data. If it's the STR file that's corrupted, you'll need to restore from a backup. (You do have a backup right?) Otherwise, try renaming your panel files one at a time to see if it's one of them that has become corrupted. Also try renaming your .TXX file to see if it's the corrupted file. Once you track down which file is corrupt, you can restore a copy of it from your most recent backup and hopefully get into the database. Then export all data, delete panel, index (IND), and text (TXX) files (leaving just the STR file), and then import data back into the database. You'll likely end up with some lost data. If you have a recent backup, you might be best to just restore the backup and then re-enter any data since the backup was made. Also - be sure to run a diagnostic or two on the hard drive that hosts your database. If the drive's getting flakey you're spinning your wheels until you replace it. Tim Rude ----- Original Message ----- From: Don Friedman To: [email protected] Sent: Monday, October 11, 2010 10:30 AM Subject: [Dataperf] Error 154 I am in an election cycle and was just modifying a report on a very large voter database and got kicked out with an error code 154. Re-entering the database doesn't work. Removing the index file and attempting to rebuild that doesn't work. Trying to export the .str file so I could delete the report I was working on doesn't work. Every attempt to use the database is stymied by this error code. Does anyone have any ideas on how I could recover this? Don -- Don Friedman ProfessionalRecords.Com LLC PRS Data Systems 205 S Main Street Pittsburgh, PA 15215 412-784-1600 - 1-800-PRS-FILE 412-784-1615 Fax _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf -- Don Friedman ProfessionalRecords.Com LLC PRS Data Systems 205 S Main Street Pittsburgh, PA 15215 412-784-1600 - 1-800-PRS-FILE 412-784-1615 Fax _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
