Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 2756

Re: Possible data corruption

$
0
0

Hello Bret,

 

I encounter similar situation in my enivornment as well.

Unlike the example mentioned in your post. I have issue with a user table .

 

 

Jan  6 19:02:28 2016: D00: Page Verification Error: Page 132025, object 2041771300, index 0, level 0, was found with fixed-row status improperly set.

Jan  6 19:02:28 2016: D00: SYBMULTBUF WARNING: One or more errors have been reported while performing consistency checks on the pages being dumped. The affected pages w

ill be reread in an attempt to discard spurious errors.

Jan  6 19:02:28 2016: D00: SYBMULTBUF WARNING: After rereading the pages, the consistency check has continued to report one or more errors.

Jan  6 19:02:28 2016: D00: Page Verification Error: Page 132027, object 2041771300, index 0, level 0, was found with fixed-row status improperly set.

Jan  6 19:02:28 2016: D00: SYBMULTBUF WARNING: One or more errors have been reported while performing consistency checks on the pages being dumped. The affected pages w

ill be reread in an attempt to discard spurious errors.

Jan  6 19:02:28 2016: D00: SYBMULTBUF WARNING: After rereading the pages, the consistency check has continued to report one or more errors.

Jan  6 19:03:10 2016: D00: Page Verification Error: Table Corrupt: The row number and offset of each row in the page should have a matching entry in row number table; c

heck this page (page#=8507087 row#=0 offset in row number table=0).

Jan  6 19:03:10 2016: D00: SYBMULTBUF WARNING: One or more errors have been reported while performing consistency checks on the pages being dumped. The affected pages w

ill be reread in an attempt to discard spurious errors.

Jan  6 19:03:10 2016: D00: SYBMULTBUF WARNING: After rereading the pages, the consistency check has continued to report one or more errors.

 

 

 

1> select object_name(2041771300)

2> go

                                                                                                                                                                       

--------------------------------------------

JPL_MOD_ACTN_PERM                                                                                                                                                     

 

The table is of very small size. I ran adbcc checkdb. I went fine with no errors.

I saw a recommendation of creating a clustered index and then dropping it.

 

Any other thoughts? I do not have dbccdb configured here.

 

Regards,

Ajith Prabhakaran


Viewing all articles
Browse latest Browse all 2756

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>