If your error strictly deals with a corrupt System Table,
you may be able to get away with unloading the structure
and data and then re-creating the database.
OUT STRUC.TXT
UNLOAD STRUCTURE
OUT SCR
OUT DATA.TXT
UNLOAD DATA
OUT SCR
Then, move the database.
OUT STRUC_ERR.LOG --to capture any errors
RUN STRUC.TXT
OUT SCR
OUT DATA_ERR.LOG
RUN DATA.TXT
OUT SCR
John
At 10:52 AM 9/7/2006, you wrote:
John,
This db is for one of my eCommerce web sites. Evidently the customer doesnt look at his web site too often or I would have received a phone call. I looked at the web log files and the problem started 8/24/06 and I have been backing up and unfortunately my oldest backup is 8/25/2006.
I am going to create a cron job to test each db I run every six hours and email me if any problems, so this doesnt happen again.
I have read the manual and followed the instructions. When I check the Database Info & Structure (all), I receive no errors
I get 105 errors when checking all data. There is a commonality in the errors in that the tables that are affected have this similar error.
Checking data for the table SYS_COMMENTS
ERROR at row address 16385.
Changes made to a NOTE column in this table have caused this row to be
relocated lower in the table. The location of the new row is 0
and it should be within the range of 16385 to 4639937.
ERROR
The last address read for this table was 16385.
The structure file expects the end of table to be at 4639937.
ERROR
The number of rows counted for this table was 0.
The structure file expects to count 407 rows.
0 Row(s)
3 Error(s)
Is it possible that one of the db fields is offsetting all the data? Any other suggestions?
Steve
From: John Minyo II [ mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 07, 2006 8:54 AM
To: [email protected]
Subject: [RBASE-L] - Re: DB Problems
Steve,
The "All" option should not be whited out. Normally,
it is View names that are whited out in the table list.
Data errors with NOTE data type columns in the tables
are always more complicated to fix. At this point you
have to outweigh how much time that would be spent on
repairing the database versus restoring a backup and
reentering the data that is different.
If restoring from a backup is not an option, you could
contact a Authorized Developer in your area or send the
database to RBTI and we can see what we can do.
Did you receive the printed R:Scope Manual? It contains
an area on how to deal with errors and provides examples.
There is also a new version of R:Scope, 7.5 for Windows.
http://www.rbase.com/products/rscope/
John
At 06:07 PM 9/6/2006, you wrote:
Thanks for the reply. I try to check the Data and it wont let me check All. It is whited out.
I checked Data on a few individual tables and it seems all of them have a problem. Changes made to a NOTE column in this table have caused have caused this row to be located lower in the table.
Steve
From: John Minyo II [ mailto:[EMAIL PROTECTED] ]
Sent: Wednesday, September 06, 2006 5:00 PM
To: [email protected]
Subject: [RBASE-L] - Re: DB Problems
Steve,
First, make a backup!
Then, in R:Scope locate what table has the error
by checking the "Data".
Once you find the table, choose "Fix" > "Data"
"Manual" to locate and repair the broken pointer.
Did you receive the R:Scope manual with your
version? It will help a great deal! Follow the
Hot Keys to jump to the pointers.
John
At 05:27 PM 9/6/2006, you wrote:
I have a DB that when I try to run AUTOCHK, I get the following error:
ERROR The new location of a moved row is invalid. (1247)
Can someone give me an idea what to start with R:Scope?
Thanks
Steve Fogelson
