Results 1 to 2 of 2
  1. #1
    Join Date
    Nov 2002
    Posts
    8

    Unanswered: Page corrupt in the table tb_irecap]\

    Please your help with these question. Yesterday, i had the following error in my ASE 12.5:

    01:00000:00038:2004/05/06 17:51:53.73 server Error: 12322, Severity: 21, State: 301:00000:00038:2004/05/06 17:51:53.75 server Row -26592 on DOL datapage 592301 in database 'db_visabb' has size 10 and an invalid holesize 0. Page is corrupted.01:00000:00038:2004/05/06 17:51:53.75 kernel ************************************01:00000:00038 :2004/05/06 17:51:53.75 kernel SQL causing error : _visabb..sp_vrf_reg_crg_archivo 01:00000:00038:2004/05/06 17:51:53.75 kernel ************************************01:00000:00038 :2004/05/06 17:51:53.75 server SQL Text: _visabb..sp_vrf_reg_crg_archivo 01:00000:00038:2004/05/06 17:51:53.75 kernel curdb = 6 pstat = 0x10100 lasterror = 12322 01:00000:00038:2004/05/06 17:51:53.75 kernel preverror = 0 transtate = 001:00000:00038:2004/05/06 17:51:53.75 kernel curcmd = 197 program = MoniTran Kernel

    At the moment of the error, two programs were updating data in the table tb_irecap, the following errors were displayed in the user's programs:

    SQL Error: 530
    Attemp to insert NULL value into column 12 in work table (table id - 10616882); column does not allow NULLS. UPDATE fails.

    ================================================== ===

    Error: (Native Error code:21)
    (DataDirect ADO Sybase Provider) WARNING - Fatal Error 614 ocurred at May 6 2004 5:51. Please note the time, and contact a user with System Administrator (SA) authorization.

    ================================================== ===

    Is this corruption in the table caused by a program(stored procedure) or is a error in the database?

    The result of dbcc checktable of the table shows:
    Checking tb_irecap: Logical pagesize is 8192 bytes
    Msg 9991, Level 16, State 1
    Orphan row at offset 157 in page 592301 of object 2000007125 must be marked committed delete and is not
    The total number of data pages in this table is 62630
    The total number of pages which could be garbage collected to free up some space is 5995
    Table has 1639500 data rows.
    Msg 2510, Level 16, State 2
    Key mismatch between index page 592220, at offset 1164 and data page 592301 (row ID 0) in database 'db_visabb'. Drop and re-create index id 2 of table 'tb_irecap'
    Msg 2510, Level 16, State 2
    Key mismatch between index page 573039, at offset 2678 and data page 592301 (row ID 0) in database 'db_visabb'. Drop and re-create index id 3 of table 'tb_irecap'
    Msg 2510, Level 16, State 2
    Key mismatch between index page 288278, at offset 7018 and data page 592301 (row ID 0) in database 'db_visabb'. Drop and re-create index id 4 of table 'tb_irecap'
    Msg 2510, Level 16, State 2
    Key mismatch between index page 592352, at offset 44 and data page 592301 (row ID 0) in database 'db_visabb'. Drop and re-create index id 5 of table 'tb_irecap'
    Msg 2510, Level 16, State 2
    Key mismatch between index page 234427, at offset 4506 and data page 592301 (row ID 0) in database 'db_visabb'. Drop and re-create index id 6 of table 'tb_irecap'

  2. #2
    Join Date
    Feb 2002
    Location
    Willy is on vacation
    Posts
    1,208
    "Is this corruption in the table caused by a program(stored procedure) or is a error in the database?"

    If your application can cause corruption in a clean database, certainly this has to be a bug in the product(Sybase).

    I have seen the sort of errors that you got before on 12.0.0.6, Sybase provided a fix on 12.0.0.8 ESD#1.

    Check with Sybase support to confirm this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •