| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2401.1 | I'd say, pay the money | AIMTEC::ZANIEWSKI_D | Taking bids on Andrew's Alphatraz cell | Wed Nov 27 1996 13:28 | 7 |
| 2401.2 | 5p for hitting it; $$$$ for knowing where... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Wed Nov 27 1996 17:43 | 14 |
| 2401.3 | A lot of hammering | SHRMSG::HOWARD | Ben | Fri Dec 06 1996 15:48 | 12 |
| 2401.4 | What are the future dangers ? | NETRIX::"Karl [email protected]" | Karl Strong | Fri Jan 31 1997 15:05 | 1 |
| [Posted by WWW Notes gateway]
|
| 2401.5 | What are the future dangers ? | NETRIX::"Karl [email protected]" | Karl Strong | Fri Jan 31 1997 15:08 | 10 |
| So the concensus is that its not easy to fix ?
If we run with that shared area closed, what dangers lie ahead by not fixing
this currupt DAF file ?
Regards,
Karl Strong.
[Posted by WWW Notes gateway]
|
| 2401.6 | | AIMTEC::ZANIEWSKI_D | Taking bids on Andrew's Alphatraz cell | Fri Jan 31 1997 19:26 | 6 |
| The problem can only get worse, never better. Even with the mail
area closed, somebody is going to delete a mail message bordering
the corruption. Depending upon the type of corruption, this will
then extent the problem or cause the whole file to be unusable.
Dave Zaniewski
|
| 2401.7 | Agreed | SHRMSG::HOWARD | Ben | Mon Feb 03 1997 22:01 | 8 |
| FCVR began to hang for me, causing ALL-IN-1 to stay down through most
of Monday morning (it started at midnight Friday). I think you really
have to fix it. Consulting is always expensive, and as Dave says it's
going to get worse, not better. The worse the problem, the more it is
going to cost. I would expect that what one needs is RMS expertise
most of all.
Ben
|
| 2401.8 | | MAIL2::KMAHER | Un clavo saca otro clavo | Fri Feb 14 1997 15:36 | 18 |
| I have used recover many times, and don't think it requires any
particular expertise. You will lose data, but only the corrupted
bucket. Whenever I had the problem as a client, we called atlanta
support and they dialed in and fixed it. (no extra charge, though we
did have a support contract)
If you really need to recover the corrupted bucket it's not pretty, but
it is manageable.
First run recover, to get a clean copy of your current file
Then get a copy from backup which is not corrupt. (anal/rms) will tell
you. You can then merge the two files. And run RMS convert/fdl =
whatever the fdl name is, and get a new, noncorrupt file. The new file
will probably containg lots of incorrect document usage counts, but
that can be cleaned up with the next FCVR run.
I don't reccomend the latter unless the lost data is truely critical.
|