SEO

Informix Versions

4GL - 4.13.UD1
ESQL- 5.03.UC1
SE - 5.02

Operating System: SCO OpenServer 5 versions 5.0.4, 5.0.5, 5.0.6

We are experiencing a number of errors;

-211 Cannot read system catalog catalog-table
-242 Could not open database table table-name
-243 Could not position within a table table-name
-244 Could not do a physical-order read to fetch next row
-245 Could not position within a file via an index
-246 Could not do an indexed read to get the next row
-397 System catalog table-name corrupted
-710 Table table-name has been dropped, altered, or renamed
-750 Invalid distribution format found for table_name

on various sites.

Running bcheck as shown that such errors such as -245 don't always point to
a corrupt .idx file. The -750 is a false report because the table can be seen
& selected from on another login.

The hardware has been checked out by Hardware Engineers and found not
to have any faults.
The problem systems are also from a range of manufacturers.

I realise that we are using an old version of Informix, but has anyone
had any experience with
these sorts of issues.

Fatlad wrote:

>Informix Versions
>
>4GL - 4.13.UD1
>ESQL- 5.03.UC1
>SE - 5.02
>
>Operating System: SCO OpenServer 5 versions 5.0.4, 5.0.5, 5.0.6
>
>We are experiencing a number of errors;
>
>-211 Cannot read system catalog catalog-table
>-242 Could not open database table table-name
>-243 Could not position within a table table-name
>-244 Could not do a physical-order read to fetch next row
>-245 Could not position within a file via an index
>-246 Could not do an indexed read to get the next row
>-397 System catalog table-name corrupted
>-710 Table table-name has been dropped, altered, or renamed
>-750 Invalid distribution format found for table_name
>
>on various sites.
>
>Running bcheck as shown that such errors such as -245 don't always point to
>a corrupt .idx file. The -750 is a false report because the table can be seen
>& selected from on another login.
>
>The hardware has been checked out by Hardware Engineers and found not
>to have any faults.
>The problem systems are also from a range of manufacturers.
>
>I realise that we are using an old version of Informix, but has anyone
>had any experience with
>these sorts of issues.
>
>
Is it feasible for you to rebuild the database (dbexport, drop, create,
dbload)?
This might be the most foolproof way of solving whatever problem it is.

Just a suggestion.

Michael

> Is it feasible for you to rebuild the database (dbexport, drop, create,
> dbload)?
> This might be the most foolproof way of solving whatever problem it is.
>
> Just a suggestion.
>
> Michael

Yes we've tried this with mixed success. Some systems have had their
problems fixed other's not.

"Fatlad" <fatlads03@yahoo.co.uk> wrote in message
news:375a7e0a.0307022354.6b85ecdd@posting.google.c om...
> > Is it feasible for you to rebuild the database (dbexport, drop, create,
> > dbload)?
> > This might be the most foolproof way of solving whatever problem it is.
> >
> > Just a suggestion.
> >
> > Michael
>
> Yes we've tried this with mixed success. Some systems have had their
> problems fixed other's not.
If you use symbolic links to point to the chunks, make sure that you don't
have 2 links pointing to the same
physical disk area. That can cause lots of strange corruption problems.
-Jim

Jim wrote:

>"Fatlad" <fatlads03@yahoo.co.uk> wrote in message
>news:375a7e0a.0307022354.6b85ecdd@posting.google. com...
>
>
>>>Is it feasible for you to rebuild the database (dbexport, drop, create,
>>>dbload)?
>>>This might be the most foolproof way of solving whatever problem it is.
>>>
>>>Just a suggestion.
>>>
>>>Michael
>>>
>>>
>>Yes we've tried this with mixed success. Some systems have had their
>>problems fixed other's not.
>>
>>
>If you use symbolic links to point to the chunks, make sure that you don't
>have 2 links pointing to the same
>physical disk area. That can cause lots of strange corruption problems.
>-Jim
>
>
>
>
He is running SE - there are no chunks, just files.