Albert
Sorry to say from past experience that a power failure during a RELOAD CAN
damage the original database as well. It happened to a client of mine who
ignored my advice to backup first.
>From then on, I learned to set up AUTOMATED routines for clients for reload
that do this:
AUTOCHK database
IF OK
Back up to local drive
If it works
GO on
Else
Error message and STOP
endif
ELSE
error message and STOP
ENDIF
RELOAD
IF error var shows problems
STOP and restore from backup
ELSE
Go on
ENDIF
Check reloaded database
IF OK
Go on
ELSE
Error message and restore from backup
ENDIF
Delete original database
Rename reloaded to original name
End
David Blocker
----- Original Message -----
From: "Albert Berry" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 11, 2002 6:46 PM
Subject: RE: Unload all/Reload/ Pack
Gunnar, PACK is dangerous. Anything that interrupts the process will destroy
the database. PACK removes empty space from the database and rebuilds the
indexes.
RELOAD writes out to a new database, so if it is interrupted you still have
the original. When RELOAD writes the new database, it goes table by table.
This is a similar effect in your database to a defragmentation of your hard
drive.
UNLOAD creates a text file that will rebuild your database as if you typed
everything in again. Remember to rename the original database before you RUN
the ascii file, or you will double any data that does not have a primary key
on it. This database is even more compact than the RELOADed version.
If UNLOAD/RUN does not return all the data, you have one or more rows of
data that has interesting characters in it. When the process hits these
characters, the process aborts, leaving you with an incomplete database.
The solution to the aborted RUN is to compare the row counts before and
after. I do this even for the system tables, because that I way I see broken
keys, missing indexes, etc.
I highly recommend that you get a database cleaned up to the point that it
will pass through the UNLOAD/RUN sequence, as the bad data rows will cause
abnormal termination and further corruption of your database.
"Gunnar Ekblad" <[EMAIL PROTECTED]> wrote:
>Has someone a guidence?
>1. If I do a pack I understand I take a chance on no power breakdown.
>2. If I do a reload I should not have the risk of power breakdown but
>have the same result as 1 obove.
>3. If I do unload all then delete the database base an load it back,
>that should be the same as 2 obove.!?
>4. If 2 and 3 and that does not give the same result what am I doing
>wrong?
>5. I am mostly on DOS 1.862 (or Windows corresponding version)
>Background:
>1. I am doing conversion work from Glorious 2.11 to Dos version of today
>waiting for the future win 7.0 to go Windows when happy days will
>arrive.
>Other minory ? that I can not answer!
>1. Has someone an Idea where I can look for answers?
>2. Has anyone an Idea what to look out four?
>Not to worry!
>1. Some 20 % of my application is running on 1.862 but I would be happy
>to understand above subject before I Move remaining 80% from 2.11
>
>??? From the Swedish Dinosaur of 2.11 world ???
>Gunnar
>
>
>
>================================================
>TO SEE MESSAGE POSTING GUIDELINES:
>Send a plain text email to [EMAIL PROTECTED]
>In the message body, put just two words: INTRO rbase-l
>================================================
>TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
>In the message body, put just two words: UNSUBSCRIBE rbase-l
>================================================
>TO SEARCH ARCHIVES:
>http://www.mail-archive.com/rbase-l%40sonetmail.com/
>
--
Albert Berry
Full Time Consultant to
PSD Solutions
350 West Hubbard, Suite 210
Chicago, IL 60610
312-828-9253 Ext. 32
__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now!
http://channels.netscape.com/ns/browsers/download.jsp
Get your own FREE, personal Netscape Mail account today at
http://webmail.netscape.com/
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
