ADSM-L

Re: Deleting DB and Log Volumes on NT

2015-10-04 17:59:01
Subject: Re: Deleting DB and Log Volumes on NT
From: owner-adsm-l (INTERNET.OWNERAD) at SNADGATE
To: Jerry Lawson at ASUPO
Date: 4/2/98 11:22AM
Yes - I just went through this :-(  Fortunately it was a test system.

The problem is the B-Tree structure used by the DB can leave you with
"leaves" all over the place.  I wound up having to do a Dump and Load, BUT
and Audit is also required, and this caused me grief.  The trick is don't try
to play games and remove anything before you do the dump (I did) and just let
it load and reload.  The audit then is usually clean (My original audit
failed even though the DB was in effect empty).

Lastly, the recommendation from Level 2 is "NEVER do a DUMP/LOAD/AUDIT
without contacting them before you start."  This is not a simple, trivial
task.  Clearly, what the developers need to do is spend some time developing
a compression process for the DB to "rake up" the DB leaves, and avoid this
process.  (Sorry)

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Re: Deleting DB and Log Volumes on NT
Author:  owner-adsm-l (INTERNET.OWNERAD) at SNADGATE
Date:    4/2/98 11:22 AM


I believe this topic was discussed before and that there could be a
problem deleting the files if there's still data on them.  If I'm
remembering correctly, the data in the database can get spread
throughout and sometimes the only recourse is to restore the database or
reload it from a dump.  Does anyone else remember this?

Tina Hilton
Thomson Consumer Electronics

        ----------
        From:  Randall Eggert[SMTP:RANDYE AT MAPCOINC DOT COM]
        Sent:  Thursday, April 02, 1998 7:05 AM
        To:  ADSM-L AT VM.MARIST DOT EDU
        Subject:  Re: Deleting DB and Log Volumes on NT

        Phil asked about deleting his old DB & LOG files after defining
new ones.

        You must REDUCE the size of both your DB & LOG files by the
amount of space
        that is provided by your original DB & LOG files.

        Your new DB & LOG files are 808MB & 64MB respectively.  Say your
old ones
        were 404 and 32, then REDUCE DB 404 & REDUCE LOG 32.

        When you query your db, Q DB, the Maximum Extension field will
show 404MB.
        Then issue your DELETE command.  A process will start, migrating
all DB
        data from the old file to the new.  When complete, the AVAILABLE
SPACE and
         ASSIGNED CAPACITY will reflect the file sizes for just your new
files.

        (Gee.... I hope this still works for V3, as I  am still on V2)

        Good Luck
        Randall Eggert
        Tulsa
<Prev in Thread] Current Thread [Next in Thread>