Alas, this version of the server does not have an  AUDIT DB command.  Or is 
there another
command I am missing?

Having a defect in the HD sounds plausible, but if you understand HPFS, it can 
handle certain
faults, mark the blocks bad, and continue on.

Any other suggestions are welcome!

Roger

On Wed, 18 Aug 1999 11:07:10 -0500, Wu, Jie wrote:

>Mauro,
>
>well, like I said, it is solely based on my personal experience. It is lucky
>that Roger mirrored the database, otherwise, the server was going to crash
>when the database page mismatch error was encontered. As pointed out from
>Roger's email, the server looked for a morror copy from E:\DBVOL\DB4.DSM
>while a page mismache happened on D:\ADSMV2\DB1.DSM. I do not know how much
>database knowledge you have, but anyway, one really need some database
>knowledge in order to understand a page mismatch error. (logical page -->
>physical page).
>physical page).
>
>Actually you would find that several people have reported the same error
>before if you search this archive. It was suggest that bad hard disk might
>be the problem. However, other possibilities exist. For example, a corrupted
>database. I remember an adsm developer from IBM suggested auditing the
>database. I believe that IBM has no sure answer to this problem and is still
>dealing with it.
>
>I would like to repeat myself, the above is only my understanding. I might
>be wrong.
>
>Jie Wu
>System and Storage Administrator
>ROW Sciences Inc @NCTR FDA
>phone: 870-543-7958
>fax: 870-543-7382
>
>
>> -----Original Message-----
>> From: Mauro M. TINELLI [SMTP:Mauro.TINELLI AT ST DOT COM]
>> Sent: 1999??8  18   9:10
>> To:   ADSM-L AT VM.MARIST DOT EDU
>> Subject:      Re: Page address mismatch ANR0207E
>>
>> Jie,
>>
>>  ... and  did you accept it as a matter of fact or did you get confort
>> from IBM/Tivoli guys & girls?
>>
>> Mauro, STM
>>
>> > Based on my experience, this argument is not correct. I saw this error
>> > before on our adsm server with single copy of DB.
>> >
>> > Jie Wu
>> > System and Storage Administrator
>> > ROW Sciences Inc @NCTR FDA
>> > phone: 870-543-7958
>> > fax: 870-543-7382
>> >
>> >
>> > > -----Original Message-----
>> > > From: Mauro M. TINELLI [SMTP:Mauro.TINELLI AT ST DOT COM]
>> > > Sent: 1999??8  18   2:03
>> > > To:   ADSM-L AT VM.MARIST DOT EDU
>> > > Subject:      Re: Page address mismatch ANR0207E
>> > >
>> > > 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