At 06:28 PM 1/5/2009, Tom Frederick wrote:
There is no activity delay. Hit Design and RV starts. Data loads
for 5-10 fields then the error pops up and everything stops before
Design actually starts. My question is where do I look to figure
out what caused the error.
Tom,
Here's a proven technique to ensure the Schema and Data Integrity.
Follow the steps below and see if everything is "peachy".
01. Make a backup copy of the database.
02. Copy the entire database (.RX1-.RX4 files) on your local drive
in a separate folder with at least twice as much available free
disk space.
03. Start R:BASE using the latest version/update and switch the
current folder to the appropriate database folder on your
local drive.
04. At the R> prompt:
DISCONNECT
SET MESSAGES ON
SET ERROR MESSAGES ON
SET MULTI OFF
-- CONNECT the database with OWNER password, if any
CONNECT dbname IDENTIFIED BY owner password
-- CONNECT the database with no passwords
CONNECT dbname
05. Check the connected database CHARacter settings, especially
the IDQUOTES.
At the R> prompt:
CLS
SHOW CHAR
-- Notice the setting for IDQUOTES (the last item on list).
If this setting is blank/null, make sure to set the IDQUOTES
settings to ` (that is a single reversed quote, on the same
key as the ~ tilde).
SET IDQUOTES=`
06. Now create the unload file with NULL set to -0-.
At the R> prompt:
CLS
SET NULL -0-
OUTPUT newdb.ALL
UNLOAD ALL
OUTPUT SCREEN
This step will create two files (newdb.ALL and newdb.LOB)
07. DISCONNECT, and then rename this database to some other
name.
At the R> prompt:
DISCONNECT
RENAME dbname.RX? dbnameBK.RX?
08. Now, let's rebuild the fresh database and see if it passes
the integrity check.
At the R> prompt:
CLS
RUN newdb.ALL
-- Watch the activity and all messages on the screen.
-- Don't fall asleep. You might miss an important warning.
-- Completion time may vary based on size of the database
-- (number of tables/records/indexes)
If there were no warnings or error messages, you've got a
fresh/healthy database. Give yourself a pat on the back.
If there are any warning or -ERROR- message(s), take them
seriously. In that case:
-- DISCONNECT the bad database (built using RUN newdb.ALL)
At the R> prompt:
DISCONNECT
-- Delete the bad database
At the R> prompt:
DELETE dbname.rx?
DELETE newdb.ALL
DELETE newdb.LOB
-- Rename the previously saved database (Step 07.)
RENAME dbnameBK.RB? dbname.Rx?
-- CONNECT to the database
CONNECT dbname
09. CORRECT all -ERROR-s accordingly and then repeat Step 06.
10. Do not quit or give up until you see a completely fresh
database without any warnings or errors.
Hope that helps!
Additional housekeeping and database maintenance tips are
also available on From The Edge: http://www.razzak.com/fte/
Very Best R:egards,
Razzak.
