On Aug 26, 11:36 pm, "Thomas J. Girsch" <tgir...@NOSPAM.gmail.com>
wrote:
> Not a real problem. The oncheck repaired the damage. Could be that a
> crash or non-standard shutdown in the past caused modified bitmap
> pages to not be flushed to disk.
>
> Art S. Kagel
I can't imagine that would be it. It occurred for nearly every record
in a table with millions of rows. But I've heard other reports that
it's nothing to worry about unless it persists.
Thanks,
- TJG
bozon - 28 Aug 2007 16:28 GMT
On Aug 28, 12:20 am, "Thomas J. Girsch" <tgir...@NOSPAM.gmail.com>
wrote:
> > Not a real problem. The oncheck repaired the damage. Could be that a
> > crash or non-standard shutdown in the past caused modified bitmap
[quoted text clipped - 9 lines]
>
> - TJG
You don't have 2 instances sharing the same space do you? Otherwise I
agree with what you have heard.
Art S. Kagel - 28 Aug 2007 17:18 GMT
On Aug 28, 12:20 am, "Thomas J. Girsch" <tgir...@NOSPAM.gmail.com>
wrote:
> > Not a real problem. The oncheck repaired the damage. Could be that a
> > crash or non-standard shutdown in the past caused modified bitmap
[quoted text clipped - 5 lines]
> in a table with millions of rows. But I've heard other reports that
> it's nothing to worry about unless it persists.
But each bitmap page describes over 4000 pages and depending on
pagesize and rowsize a single bitmap page can affect more than
10million rows!
Art S. Kagel