HP3000-L Archives

February 1996, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Larry Boyd <[log in to unmask]>
Date:
Mon, 26 Feb 1996 06:19:24 PST
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Brad Straiton worte:
> Greetings,
>
> We are currently adding a set into an existing database using DBCPLUS
> version A.02.02 but DBALTER fails with the following messages.
>
> FWIW  - we added many sets using DBCHANGE (pre MPE/iX 5.0)
>
> Cannot rename set <setname> to ALTER22  (DBA 600)
> File system error 100  (DBA 410)
> =>DUPLICATE PERMANENT FILE NAME  (FSERR 100)
> Restructuring has not been completed due to fatal error  (DBA 280)
>
> Has anyone else experienced the same problem, we have logged with the
> local response centre but no solution yet.(it takes a bit longer here)
I don't know exactly, but it sounds like you may have a file sitting
around that DBCPLUS wants to use.  Most database alteration products
use a standard database name for their alter capabilities.  It looks
like DBCPLUS using the name ALTER for the db name and the file ALTER22
already exists.  This could occur if there was some previous failure
or abort during an alteration.
 
My suggestion is to look for ALTER@ with Listf and see if there are
any files by that name.  If so, delete them with MPEX or some other
means.  Then try it.  If there are no ALTER@ file names, try @22.  There
should be more than just you normal databases in that group.
 
Good luck,
 
Larry Boyd
[log in to unmask]

ATOM RSS1 RSS2