[kdsgrp1] error RAC on TABLE segment with chained rows

From: <Christopher.Taylor2_at_parallon.net>
Date: Wed, 16 Jan 2013 15:37:13 -0600
Message-ID: <F05D8DF1FB25F44085DB74CB916678E8856A7A9129_at_NADCWPMSGCMS10.hca.corpad.net>

Env: 3-node RAC RH Linux 64-bit Ok guys and gals,

I'm a bit stumped here.

Here's what I have and I'm hoping someone can offer some thoughts on chained rows perhaps.

  • 2013-01-16 00:51:51.891
  • ACTION NAME:(wq_rules.run_rules) 2013-01-16 00:51:51.891
  • MODULE NAME:(JDBC Thin Client) 2013-01-16 00:51:51.891
  • SERVICE NAME:(CCMNASP1) 2013-01-16 00:51:51.891
  • SESSION ID:(5304.26095) 2013-01-16 00:51:51.891 row 09b7df57.ffffffff continuation at file# 38 block# 3661655 slot 0 not found

File 38, block# 3661655 matches to MON_ACCOUNT_ACTIVITY table.

I have verified that there are no missing rowids in either the table or index (rowids match up in both table-> index and index-> table).

I get 0 corruption errors/warnings. Export of the table works correctly as well.

Now, I do have 1834 chained rows in this table but it appears that all the chains are valid (all row pieces found) - again verified [I think] by the export.

According to Note 1332252.1:
"If analyze and exporting the table (in the presence of chained rows) both report no errors then this should be considered a consistent read issue."

Rerunning the failing process completes succesfully.

When the process failed, the 3 nodes are heavily utilized - CPU utilization near 100% on all 3 nodes, lots of IO, lots of concurrent processing such that one query executing may looking up data from a table that is being inserted/updated by another session processing a different module.

I was curious if anyone had any suggestions/thoughts about digging deeper into this?


Chris Taylor
Oracle DBA
Parallon IT&S

Received on Wed Jan 16 2013 - 22:37:13 CET

Original text of this message