Jim & everyone, oops, sorry - it was nearly midnight here when I replied and
I must have been brain-dead! At least I gave a warning about what I said.
I think that you _can_ delete the .RB3 file (that's R.. B.. three) and
R:Base should recreate it so that the indexes can be re-built using PACK.
The same "ensure you have a backup" applies before trying!
Regards,
Alastair.
----- Original Message -----
From: "James (Jim) Bentley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 02, 2002 1:24 AM
Subject: Re: Database issue
Alastair,
The Indexes are stored in the RB3 file not the RB4 file. If you
can identify the specific problem you can do the following:
PACK ----------------------------------
+ dbspec ++ KEYS ----------------�
+ INDEX indexname------�
+ SCHEMA --------------�
+ ALL -----------------�
+ WITH USER CASE +
"PACK dbspec INDEX indexname"
or
"PACK dbspec KEYS" to do all indexes
--
Jim Bentley
American Celiac Society
[EMAIL PROTECTED] - email
(973) 325-8837 voice
(973) 669-8808 Fax
---- "Alastair Burr" <[EMAIL PROTECTED]> wrote:
> Mike,
>
> From your later posts it looks as if you might have solved the
> problems but
> just in case you haven't and for anyone else who might be interested...
>
> Autochk does NOT check indexes.
>
> In the past I believe that if you had a problem with indexes
> you could
> delete (rename!!!) the .rb4 file and R:Base would re-create
> it but I think
> it now holds too much form/reports/labels info so that you can
> no longer do
> this.
>
> If your have corrupt indexes then _usually_ a reload will solve
> the problem
> but, if it doesn't, use BACKUP and pray it works - it usually
> does! The file
> that is created does not contain the indexes - only the commands
> to create
> them so re-create your database with the output file. The usual
> "ensure you
> have a copy/backup of all you files" applies!!! (By the way,
> I've often got
> "error" messages here but been able to ignore them and had no
> data loss.
> Generally they concern record counts which are what is causing
> the original
> problem. Just check the last entry rows to make sure that they
> are all
> there...)
>
> If you still have a problem then you probably need R:Scope or
> your most
> recent valid backup.
>
> Good luck & regards,
> Alastair.
>
>
>
> ----- Original Message -----
> From: "Ramsour Mike" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, August 01, 2002 7:36 PM
> Subject: RE: Database issue
>
>
> > In the process of the reload I just encountered what seems
> to be an
> > indication of the problem. I got the following error message:
> >
> > A COLUMN'S INDEX FILE REFERENCE IS INVALID.
> >
> > I am going to do an unload all and reload to see if that fixes
> it. What's
> > the error message all about? Technical explanation anyone?
> >
> > Thanks -- Mike
> >
> > -----Original Message-----
> > From: Alastair Burr [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, August 01, 2002 2:15 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Database issue
> >
> >
> >
> >
> >
> >
> > I think that your first error check is in the wrong place
> - all it's
> telling
> > you at the moment is that the CLS gave no error.
> >
> > If you move it between the AUTOCHK line and the OUTPUT SCREEN
> line you
> > should get what you want.
> >
> > Regards,
> > Alastair.
> >
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Ramsour Mike" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, August 01, 2002 4:50 PM
> > Subject: Database issue
> >
> >
> > > Part of a routine that I do each day is to reload my database,
> run
> AUTOCHK
> > > on it and if everything comes out OK I then copy the database
> to a
> network
> > > share for my users. During this morning's run I encountered
> a problem
> > where
> > > the RB2 did not get entirely reloaded and none of the indices
> were
> rebuilt
> > > but AUTOCHK apparently gave an OK result so that the copy
> took place.
> > >
> > > Here is the code that I use:
> > >
> > > DISCONNECT
> > > --
> > > CLEAR ALL VAR now
> > > --
> > > SET ERROR VAR vchk_result
> > > --
> > > OUTPUT d:\autoload.$$$
> > > --
> > > AUTOCHK maindata FULL
> > > --
> > > OUTPUT SCREEN
> > > --
> > > CLS
> > > --
> > > IF vchk_result <> 0 THEN
> > > --
> > > CLS
> > > --
> > > OUTPUT d:\loadrslt.txt
> > > --
> > > WRITE 'Errors encountered during data loading -- aborting'
> > > --
> > > OUTPUT SCREEN
> > > --
> > > GOTO endline
> > > --
> > > ENDIF
> > > --
> > > CONNECT maindata
> > > --
> > > RUN mon_calc.prg
> > > --
> > > RELOAD NEXTDATA
> > > --
> > > DISCONNECT
> > > --
> > > OUTPUT d:\autoreld.$$$
> > > --
> > > AUTOCHK nextdata FULL
> > > --
> > > OUTPUT SCREEN
> > > --
> > > IF vchk_result = 0 THEN
> > > --
> > > CLS
> > > --
> > > OUTPUT d:\reldrslt.txt
> > > --
> > > WRITE 'Database reload successful'
> > > --
> > > OUTPUT SCREEN
> > > --
> > > DELETE MAINDATA.*
> > > --
> > > RENAME NEXTDATA.* MAINDATA.*
> > > --
> > > COPY MAINDATA.* m:\rbased~1
> > > --
> > > GOTO endline
> > > --
> > > ELSE
> > > --
> > > CLS
> > > --
> > > OUTPUT d:\reldrslt.txt
> > > --
> > > WRITE 'Errors encountered on database reload'
> > > --
> > > OUTPUT SCREEN
> > > --
> > > GOTO endline
> > > --
> > > ENDIF
> > > --
> > > LABEL endline
> > > --
> > > EXIT
> > >
> > > The database files are somewhat large by some measures:
> > >
> > > MAINDATA.RB1 169,196
> > > MAINDATA.RB2 805,486,492
> > > MAINDATA.RB3 201,887,774
> > > MAINDATA.RB4 1,126,400
> > >
> > > My concern is that the files are getting too large or that
> I have
> > something
> > > wrong with my system or possibly the database. If there
> was an error in
> > the
> > > database then why didn't AUTOCHK catch it? I am running
> the latest
> > version
> > > of R:Base for Windows on a Windows 2000 PC. Could there
> be a problem
> with
> > > an index file being that big?
> > >
> > > As an aside, will v. 7.0 also be limited to around 2 GB
> or will that
> limit
> > > be lifted?
> > >
> > > Thanks
> > >
> > > Mike Ramsour
> > > AK Steel Coshocton Works
> > >
> > > 740-829-4340
> > > ================================================
> > > 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/
> >
> > ================================================
> > 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/
>
================================================
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/
