This is a known issue, documented in APAR IC19821 and fixed in PTF 1 of the
ADSMConnect Agents for Lotus Notes on AIX and WIndows NT. Go to the ftp site
index.storsys.ibm.com and check directory /adsm/fixes/v2r1/agents The APAR text
follows.

Andy Raibeck
ADSM Level 2 Support



ERROR DESCRIPTION:

ENVIRONMENT: ADSMConnect Agent for Lotus Notes on Windows NT or
             AIX.

PROBLEM: If the ADSMConnect Agent determines that the internal
         database ID of the Notes .NSF file does not match the
         internal database ID of the backup version, the
         requested operation will fail. (The "internal database
         ID" is the one that Lotus Notes generates for the
         database at the time it is created. It can be viewed by
         examining the database properties.)

         One way this problem could occur is illustrated with
         the following scenario:

         1) Database TEST.NSF is created. Lotus Notes gives it
            an internal database ID of 8025658C:00252655.
         2) ADSMConnect Agent for Lotus Notes backs it up.
         3) Database TEST.NSF is renamed to TESTOLD.NSF. It
            still has the internal ID of 8025658C:00252655.
         4) A new TEST.NSF database is created. Lotus Notes
            gives it an internal ID of 9256853D:00953233.
         5) ADSMConnect Agent for Lotus Notes tries to back up
            TEST.NSF. It fails with message:
                  ANS0955E Database ids do not match
            This is because TEST.NSF's internal ID is
            8025658C:0025FEFF, but when ADSM originally backed
            it up, it had an ID of 8025658C:00252655.

         Another similar scenario would be if the database was
         was backed up by the ADSMConnect Agent for Lotus Notes,
         subsequently restored with a different name, then
         renamed back to its original name (i.e. if TEST.NSF
         was restored as TESTORG.NSF, then renamed back to
         TEST.NSF).

         This problem may also affect restore operations.

         The comparison of the internal database IDs was meant
         to be an integrity check. For example, in the first
         scenario above, if the two TEST.NSF databases were
         really two different databases and the backup was
         permitted, a subsequent restore of TEST.NSF would yield
         a "hybrid" database.

         However there are also very legitimate reasons why a
         database ID might change. For example, a DSMNOTES
         RESTORE with the -TO=newname option followed by a
         rename of the new database name to the original name
         could cause this to occur. The Lotus Notes "object
         collect" operation also causes the database ID to
         change.

 ADSM-L AT VM.MARIST DOT EDU
 02-10-98 09:14 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet

To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
Subject: Lotus Notes Agent Question

Fellow ADSMers

  In my Lotus Notes agent backup I sometimes get the following message:

    ANS0995E  Database ids do not match

  I can't find this error message in the manual and am wondering if
somebody else knows what it means.

  TIA

   Ron Heflin