Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Murray Wood (IList) wrote:
> What is the status of each chunk. I would guess that you have a chunk down.
All the chunks report PO (Primary Online) from onstat -d.
> If it is only that and the data is still there you could try to change its
> status with onspaces -s ....
I am doubtful that onspaces would be able access the chunks for the dbspaces in
this table.
Thanks for the thought
Bob
>
> MW
>
>
>>-----Original Message-----
>>From: owner-informix-list@iiug.org
>>[mailto:owner-informix-list@iiug.org] On Behalf Of Robert C B
>>Sent: Thursday, 12 May 2005 9:44 a.m.
>>To: informix-list@iiug.org
>>Subject: IDS 2000 9.21.UC4/Solaris/Sparc Problem accessing
>>table - urgent
>>
>>We had a hardware controller glitch yesterday and the IDS
>>engine panic-ed and crashed. This history was reconstructed
>>from online.log.
>>
>>Informix came up after rebooting the OS, recovered from the
>>logs and gave no error indications. (Lost the af... dump )
>>
>>Of a total of about 50 tables in 2 major databases there is
>>one table that appears to be unaccessible.
>>
>>1. A simple 'select count(*) from tabname;' sits around and
>>gets no IO (onstat -u).
>>
>>2. In dbaccess table/info/tabname/status does not complete.
>> At the bottom of dbaccess page it shows 'Running.....' but
>>does nothing
>>
>>3. dbaccess table/info/index will list the indices ok.
>>
>>4. dbaccess table/info/fragments just hangs and will not complete.
>>
>>5. oncheck on the table just just hangs around and does not
>>get any IOs.
>>
>>6. An attempt to drop the primary index just hung and did no IOs.
>>
>>7. Have restarted IDS several times and there are no error
>>messages of any kind related to this table in the online.log.
>>The table still does not function (as if some lock is being
>>held in sysmaster??)
>>
>>
>>One of the temporarily failed disks contained a fragment of
>>this table.
>> However there were over a dozen failed disks from other
>>tables/fragments and they now work fine including the dbspace
>>for physical log..
>>
>>We need to be able to access the info in this table We would
>>really prefer not to restore from the last backup which is
>>about 2 weeks old.
>>
>>
>>Help please
>>
>>Bob Bankay
>>
>>
>
>
>
> sending to informix-list
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.