Re: HELP URGENT CORRUPTED DATA

  • From: "Alex Gorbachev" <gorbyx@xxxxxxxxx>
  • To: paulastankus@xxxxxxxxx
  • Date: Fri, 19 May 2006 20:45:40 +0200

If you restore your database to a point in time in the past than
transactional integrity is preserved. However, your application should
be done in such a ways that business transaction is done as database
transaction. This was the change is atomic. If your business
transaction is done so that you have 10 commits for one business
transaction than you might have got restored to the middle of this
business transaction. Such inconsistencies shoule be than handled by
application otherwise it's a design flaw. Often these might be
bastches that are commiting work every so many records. For example,
your purge batch might have purged half of your tables and introduced
inconsistency.

Also you didn't really say what exactly wrong with it and how you see
the problem from application point of view - some query returns wrong
result? Or it's just users see "something" wrong and you can't
identify what's that. If the latter, than I would suggest to narrow
down the area.

Regarding point A - it's possible that index can be corrupted and you
are correct in the way to detect it. Fix is to rebuild the index. Btw,
PiT recovery should not cause index corruption becasue it's updated as
part of the transaction and PiT recovery doesn't leave non-commited
transactions on the half way.

Point B - I am not sure about your question. Do you mean string comparison?

Good luck!

2006/5/19, Paula Stankus <paulastankus@xxxxxxxxx>:

Guys,

We recovered a database, did a dbverify - everything looked good, exports
are working fine.  However, we recovered to an earlier point (few hours
earlier) and on the "earlier"  database we have no errors in a specific
function of the application in the "later" one we have errors.  We have been
beating our hands against the brick wall doing comparisons of the data - the
comparisons - table by table, column by column look okay.  We have been
working on this issue round-the-clock for days.

Questions:

A-Can an index be somehow causing this problem and can we use validate
structure or something to be sure of the validity of the index? - analyze
table validate structure...cascade...

B-Can there be missing characters (characters we cannot visually see)
causing the problem and can a "MINUS" find it if there is? :)

Thanks,

Paula


________________________________ New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.




--
Best regards,
Alex Gorbachev

http://oracloid.blogspot.com
--
//www.freelists.org/webpage/oracle-l


Other related posts: