Mauro,
I tried to create a second mirror copy of the DB with the intent of 
reformatting the defective DB copy to get rid of the errors.  However, as soon
as I executed DSMFMT, the first physical hard drive in the system went south, 
never to be seen again!  So, as you guessed, the HD was indeed
damaged.  Now, after many hours of work, the system is back nearly 100%.  
Fortunately, after this server locked up in June, I restored the boot
partition to a subdirectory on the second physical drive as insurance.  Once I 
got the new drive fdisked, and formatted, all I had to do was an
xcopy, and the OS was fully restored.  That was the easy part!  The hard part 
was caused by the VOLHIST backup file being on the
now-defunct hard drive... :)

Thanks for the help!

Roger Perkins

On Wed, 18 Aug 1999 09:02:35 +0200, Mauro M. TINELLI wrote:

>Roger,
>        I'm only guessing ... if you have a mirror copy of the DB, then 
> probably
>the first copy stays on a disk which had (or had not) a
>bad-block-replacement and the page is not anymore valid, in other words
>the disk's damaged.
>
>Does this suit you?
>
>Ciao Mauro, STM
>
>> I'm experiencing the following ADSM error about once every day for the
>last week
>> , typically around the time a full DB backup is scheduled:
>>
>> 08/17/1999 10:05:23  ANR0207E Page address mismatch detected on
>database volume
>> D:\ADSMV2\DB1.DSM, logical page 17584 (physical page
>> 93616); actual: 0.
>> 08/17/1999 10:05:23  ANR0247I Database page 17584 successfully read
>from an alte
>> rnate copy on volume E:\DBVOL\DB4.DSM.
>>
>> I'm using ADSM for OS/2 v2.1 ptf 14, and this installation has been
>stable for q
>> uite some time.  The drives are formatted HPFS386.  Any ideas
>> what could cause this and how I can fix it?
>>
>> Thanks!
>>
>> Roger Perkins
>> Upstate Medicare Division
>>
>>
>> PGP Public Key Fingerprint = 84 DB E2 39 8B DE EA C7  20 91 7D AB F2 67
>33 F0
>

PGP Public Key Fingerprint = 84 DB E2 39 8B DE EA C7  20 91 7D AB F2 67 33 F0