Troy,

Does it make any difference whether you edit or browse? Assuming no
corruption, of course.

Regards,
Alastair.



----- Original Message -----
From: "Troy Sosamon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 18, 2002 10:15 PM
Subject: RE: I/O Problems on SCONNECTed database


> Maybee a corrupted index.  Rscope & autochk don't check indexes.
>
> You might want to try BROWSE instead of EDIT.  That is a large table to be
> editing.
>
> Troy Sosamon
>
> ===== Original Message from [EMAIL PROTECTED] at 9/18/02 12:45 pm
> >I have two databases; for the sake of anonymity we'll call them A and B.
> >
> >A is the working database.  B holds history and audits.
> >
> >A table 'audits' in B is SATTACHed to A.
> >
> >I have performed an unload/input on B.  B passes all tests in R:Scope and
> >AUTOCHK.
> >
> >If I do EDIT ALL FROM audits while connected to A and SCONNECTed to B,
and
> >then do [ctrl] [end] twice to go to the bottom of the table, I get "I/O
> >error - check for a full disk."  If I do "EDIT ALL FROM audits WHERE
> >auddttm >= 091802" I get the same error.  There are exactly two rows that
> >meet the specification and they are the last two in the table.  The field
> >auddttm is not indexed.  It is a datetime field.
> >
> >The table contains 106250 rows.
> >
> >Peforming the same actions on a table in B with only 28,643 rows works
fine.
> >
> >The same actions while CONNECTed to B work fine.
> >
> >My TEMP directory is defined and scratch is set to write there; the disk
> >containing that directory has 2.7 gb free.
> >
> >I get the same result using the R:Base ODBC driver and Oterro 2.5
1.850xRT03.
> >
> >I get the same result using R:Base version 6.5++ 1.855xRT03 and 6.5++
> >1.858xRT03.
> >
> >Any clues?
> >
> >
> >Emmitt Dove
> >Manager, DairyPak Business Systems
> >Blue Ridge Paper Products, Inc.
> >40 Lindeman Drive
> >Trumbull, CT  06611
> >(203) 673-2231
> >[EMAIL PROTECTED]
> >[EMAIL PROTECTED]
> >
> >================================================
> >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/

Reply via email to