The DBDC#@ and DBDS#@ files are produced when there is an abort
from (I believe) SQLCORE (Allbase).  There is a debug dump and an
ASCII dump that can be examined by the RC.  STORE itself should not
be producing these files.  Was there an application running at the time
of the STORE that was being interrupted, thereby producing the abort?
You normally see these files when there has been some form of corruption
of the DBE.
  As long as your backing up the DBE and all related files some other way,
then excluding them from your nightly STORE is ok.  Otherwise you may
be asking for trouble down the line.

Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (509) 943-5109
fax:   (509) 946-1170

--

----------
From:  Lee Hallin[SMTP:[log in to unmask]]
Sent:  Thursday, December 26, 1996 1:20 AM
To:  [log in to unmask]
Subject:  Re: [HP3000-L] STORE / aborting on 3000/922 under 5.5 w/powerpatch

<snip>

In my case, when STORE had trouble [s]he built two files, of the form:
  DBDC####
  DBDS####
The #### starts at 0000 and increments each time (night) that STORE croaked.
The DBDC#### file is a "PRIV" file.  I didn't snoop at it much.
The DBDS#### file is a ASCII file containing an abort trace from STORE.

<snip>