Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!mcnc!ecsgate!stat.appstate.edu!cookdl
From: cookdl@stat.appstate.edu
Newsgroups: comp.databases
Subject: Re: ACCELL problems
Message-ID: <1991Apr30.112215.762@stat.appstate.edu>
Date: 30 Apr 91 15:22:14 GMT
References: <1991Apr25.185015.1978@hrc.uucp>
Organization: Appalachian State University
Lines: 69

In article <1991Apr25.185015.1978@hrc.uucp>, dan@hrc.uucp (Dan Troxel) writes:
> 
> [posted for a friend -- dan]
> 
> I'm running ACCELL 1.4 under Xenix 2.3.2 on an IBC [sic] 80486, and am having
> problems creating a new application.  Upon entering the environment, I'm 
> greeted with the normal CURRENT APPLICATION screen.  I zoom from that to get
> the LIST OF APPLICATIONS, press F7 to add, type in the name (zzzz) and 
> description, hit F9, and get the following messages: 'The name <zzzz> is
> already registered with ACCELL/DBMS.  Cannot add application.'  It makes no
> difference what name you type in for the application- it will always tell you
> that the name is already registered.  From there, I can completely exit the
> database, come back in, then type in 'zzzz' for an application name, and
> instead of giving me the normal 'Application: zzzz not found' error, it will
> actually bring up a LIST OF FORMS FOR CURRENT APPLICATION form, with nothing
> in it- it's just blank.  
> 
> So it's obvious that these 'attempted' application names are being stored in
> the DBMS, and I've probably got a whole batch of them stuffed in there.  I
> need to know how to get them out, and how to get the DBMS to quit giving me
> this static so I can add a new application and get back to work.
> 
> I've only got eleven applications currently defined, and there is absolutely
> no naming conflict- that is, I don't have another application named 'zzzz'.
> 
> I don't have any problems with the other databases on the system, but
> can't find the discrepancy.  My initial thought was that a permissions problem
> existed which would cause ACCELL to barf half-way through creating the
> application, but this is not the case.  All I can figure is that unify.db is 
> corrupt.
> 
> Any help will be greatly appreciated.  Thanks.
> 
> 
> -- 
> Dan Troxel @ Handwriting Research Corporation                  WK 1-602-957-8870
> Camelback Corporate Center  2821 E. Camelback Road  Suite 600  Phoenix, AZ 85016
> ncar!noao!asuvax!hrc!dan          zardoz!hrc!dan      hrc!dan@asuvax.eas.asu.edu


This is a bug in Accell.  I ran into the same problem and called Unify's
hotline.  In my system this problem reoccurs every 10th application and I have
to do the following to fix it.

   cd $DBPATH
   mkdir tmp
   cd tmp
   DBPATH=$DBPATH/tmp
   export DBPATH
   ln ../unify.db file.db
   ln file.db file.dbr
   SQL
    sql> tables
         (look for a table name of mprec)
    sql> fields mprec
         (look for a field name of index and coreload)
    sql> 
    sql> (now run the following script)
     
    sql> update mprec
         set index = 0
         where coreload = 'ACCELL'/

    exit sql program
    rm tmp directory
    reset DBPATH TO previous value

    You will probably have to run this about every 10th application.  I know i
do.