Does the RESTORE fail or DBOPEN?  If RESTORE, you could try using a
fileset that excludes the ILR file  MYDB@-MYDB00  (zero zero).

Also, I found this in our database...

KBRC00000663
ILR LOG INVALID. INTERNAL ACCOUNT NAME DOES NOT MATCH ROOT
Document Information Table
ILR LOG INVALID. INTERNAL ACCOUNT NAME DOES NOT MATCH ROOT
 DocId:
       KBRC00000663

                     Updated:
                             1/18/00 7:38:59 AM


PROBLEM

I have a database that I have :RESTOREd into a test account. The
database
was created and used on a mpe/v system.  I am restoring this database to
a mpe/xl system.

When I try to access the test database, I get the following message:
     ILR LOG INVALID
     INTERNAL ACCOUNT NAME DOES NOT MATCH ROOT FILE

Why is this happening?

CONFIGURATION

mpe/xl all versions

RESOLUTION

If a database has been ENABLEd FOR ILR, there exists a privileged file,
with the root file name followed by 00. This is the ILR file. When the
database is stored off via the DBSTORE command, the ILR file is auto-
matically stored. If the MPE :STORE command is used, and the syntax for
storing the database is rootfile-name followed by an "@" (TOYDB@), then
the ILR file will also be stored (TOYDB00).

When the files are :RESTOREd into the new account, the ILR file will,
internally, contain the group and account name of the production group
and account from which it came. This is not automatically changed like
it is with the root file. Therefore, when you try to open the database
you will get the referenced error message.

To resolve this problem:

1) Purge the 00 file. This can be done with MPEX, FScheck.prvxl.telesup,
   or DBDRIVER.

   -MPEX is a 3rd party product which allows the user to purge any type
    of file include file which are privileged.

   -FSCHECK.PRVXL.TELESUP is a HP Unsupported tool which will purge
    any file including privileged.  To use this program:
    logon. to mgr.telesup,prvxl
    run. fscheck.prvxl.telesup
    .  purgefile dbname00.group.account
    .  exit

   -DBDRIVER.PUB.SYS is a HP IMAGE utility.  It will purge the 00 file
    for you.  To use this program:
    The. creator of the image database MUST have PM capability.  The
system
     manager can add this capability to the account and user.
    RUN. DBDRIVER.PUB.SYS,DIAG
     Please choose one of the following options:
     0. Exit.
     1. Purge the <dbname>00 file.
     2. Analyze the error status found in the <dbname>00 file.
     3. Change the Root condition word from 'XT' to 'FW'
     4. Change the Root condition word from 'FW' back to 'XT'

     CHOOSE option 1.  This will purge the 00 file.

    Use. DBUTIL to disable ilr from the database
     RUN DBUTIL.PUB.SYS
     disable dbname for ilr   << this will return an error in most
cases>>
     exit

    USE. QUERY TO VERIFY the database is ok to use:
     QUERY
       DEF
         BASE> DBNAME
         PASSWORD> ;  (IF CREATOR SEMICOLON CAN BE USED)
         MODE>  5    <<IF NO ERROR OCCURS HERE..THE PROBLEM IS RESOLVED.
>>
                     >>If an error does occurs Please call the response
center
                       or Image specialist for additional help.<<





Cecile Chi wrote:
>
> I am trying to help someone who needs to restore a data base from
> a backup tape written on a Classic, onto a Precision Architecture system.
> The data base was stored with ILR enabled.  The restore fails with
> "log file invalid.  ILR log file account name does not match root file"
> The account name on the tape is the same as the name of a current
> production account, so the data base cannot be restored into the same
> account it was stored from.  Only one machine exists at this company;
> there is no development machine to use for this.
> Can anyone help?
>
> Cecile Chi