![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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, Dmitry, (PerlUser) UDB DBA Independent consultant and Certified IBM professional. |
#3
| |||
| |||
|
|
perluser (AT) optonline (DOT) net (Dmitry) wrote in message news:<71ad9bef.0409141316.2b44f8e (AT) posting (DOT) google.com>... 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, Dmitry, (PerlUser) UDB DBA Independent consultant and Certified IBM professional. This message is not from database dump, but from dbcc. And it's pointing to data corruption. Follow the suggestion from the output to fix the problems. |
![]() |
| Thread Tools | |
| Display Modes | |
| |