Hello,

I am getting a following error during the sybase backup:

Checking billing_item
The total number of data pages in this table is 5457.
Table has 74367 data rows.
Msg 2511, Level 16, State 3:
Server 'SYBASE_PROD1', Line 2:
Keys of index id 4 for table 'billing_item' in leaf page 183292 should
be in
ascending order. Drop and re-create the index in database 'tesd01'.
Msg 2511, Level 16, State 3:
Server 'SYBASE_PROD1', Line 2:
Keys of index id 4 for table 'billing_item' in leaf page 183306 should
be in
ascending order. Drop and re-create the index in database 'tesd01'.
Msg 2511, Level 16, State 3:
Server 'SYBASE_PROD1', Line 2:
Keys of index id 4 for table 'billing_item' in leaf page 183458 should
be in
ascending order. Drop and re-create the index in database 'tesd01'.
Msg 2511, Level 16, State 3:
Server 'SYBASE_PROD1', Line 2:
Keys of index id 4 for table 'billing_item' in leaf page 183447 should
be in
ascending order. Drop and re-create the index in database 'tesd01'.
Msg 2511, Level 16, State 3:
Server 'SYBASE_PROD1', Line 2:
Keys of index id 4 for table 'billing_item' in leaf page 183447 should
be in
ascending order. Drop and re-create the index in database 'tesd01'.


I have dropped and recreated an indexe in question several times.
There are NO errors produced during the index creation. I have also
successfully ran a dbcc reindex (billing_item) command and it did not
yield any errors.

However, the database dump still isn't working unless I remove the
index in question from the table. The table is loaded fresh using the
command line bcp without any problem.

What could be the reason for that?

Thanks,

PerlUser.

hi Dmitry!
maybe the following steps would do u a little help:
1.use 'dbcc checktable' to check if your table and index is REALLY all right
2.use 'checkpoint' to flush your changes into those meta-data tables
3.maybe u colud use 'update statistics' to complement the 2nd action

yours sincerely Wukong

perluser (AT) optonline (DOT) net (Dmitry) wrote in message news:<71ad9bef.0409141111.203b7d46 (AT) posting (DOT) google.com>...

Hi Wukong,

I have run DBCC per your recommendation and it has produced following
result on the same index in question:

Checking billing_item
The total number of data pages in this table is 5457.
Table has 74367 data rows.
DBCC execution completed. If DBCC printed error messages, contact a
user with System Administrator (SA) role.
Keys of index id 4 for table 'billing_item' in leaf page 174492 should
be in ascending order. Drop and re-create the index in database
'tesd01'.
Keys of index id 4 for table 'billing_item' in leaf page 174498 should
be in ascending order. Drop and re-create the index in database
'tesd01'.
Keys of index id 4 for table 'billing_item' in leaf page 174650 should
be in ascending order. Drop and re-create the index in database
'tesd01'.
Keys of index id 4 for table 'billing_item' in leaf page 174647 should
be in ascending order. Drop and re-create the index in database
'tesd01'.
Keys of index id 4 for table 'billing_item' in leaf page 174647 should
be in ascending order. Drop and re-create the index in database
'tesd01'.

I have tried to drop and recreate this index several times without any
luck. Index recreation works fine and then same result is being
produced by DBCC.

Is there a way to find out which records pointers actually located on
the leaf page that is being reported in error?

Thanks,

Dmitry.

sj (AT) ahhexin (DOT) com.cn (Wukong) wrote in message news:<98159ed6.0409151946.421cd596 (AT) posting (DOT) google.com>...