At 01:44 PM 6/30/2008, Ramsour Mike wrote:
However, if I run AUTOCHK on the database it keeps coming back with an
"Error reading column list (1221)" message and an "Error reading column
information (1256)" message.
What results do you get when using the same procedures in R:BASE 7.5/7.6?
Is there something I can look for in the database structure that might
be causing this?
The big question:
How healthy is your database to start with, even in 7.5?
Follow the steps below and see if everything is "peachy".
01. Make a backup copy of the database.
02. Copy the entire database (.RB1-.RB4/.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.RB? dbnameBK.RB?
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.rb?
DELETE newdb.ALL
DELETE newdb.LOB
-- Rename the previously saved database (Step 07.)
RENAME dbnameBK.RB? dbname.RB?
-- 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.
Believe me, the time spent on this exercise will save you a
lot of hassle and embarrassment, instead of chasing something
obvious that should have been taken care of a long time ago.
Additional housekeeping and database maintenance tips are
also available on From The Edge: http://www.razzak.com/fte/
You may also follow the article on "Upgrading to R:BASE Turbo
V-8 for Windows (Database Conversion Guide)"
Very Best R:egards,
Razzak.
