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