Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2012
    Posts
    133

    Unanswered: dump tran not working due to error logical page

    Hi Guys,
    I'm having problem dumping the transaction log due to logical page error. I've already done fixing table level relating to error on fetch logical page but the problem still persist. I suspect i have already corrupt pages on transaction log prior to fixing the table. btw, querying what object belong on the page gives me an output of NULL. below ff procedures already done but no luck in clearing the error page.


    1. dbcc checktable(syslogs) - gives me an output of

    The default report option of OPTIMIZED is used for this run.
    The default fix option of NOFIX is used for this run.
    ************************************************** *************
    TABLE: syslogs OBJID = 8
    INDID=0 FIRST=16195517 ROOT=19184047 SORT=0
    TOTAL # of extents = 0
    Table Corrupt: Object id wrong; tables: alloc page 16195328 extent id=16195512 l page#=16195517 objid in ext=0 (name = 0) objid in page=8 (name = syslogs) objid in sysindexes=8 (name = syslogs)

    trying using this command single mode on dbName, run DBCC TABLEALLOC('dbo.syslogs', full, fix) - still error

    2.dump tran with no_log, truncate_only - still error
    3. I can proceed with full database dump but unable to dump the transaction log using number 2.


    I'm looking on this option running dbcc rebuild_log found on this link
    http://www.petersap.nl/SybaseWiki/in...rebuild_log%29


    I can afford downtime for just 1 day only but i need the database back online after that 1 day period.

    sybase version : 12.5.3


    The SQL Server is terminating this process.
    Server Message: Number 4216, Severity 21
    Server 'DO', Line 1:
    DUMP TRANSACTION failed in database dbName: unexpected end of log encountered on page 16204071 while scanning for page 19244976.


    Your advice would be much appreciated. Thanks advance

  2. #2
    Join Date
    Feb 2012
    Location
    Pune
    Posts
    11
    you can try with these steps:-
    Bypass recovery mode for the database :-
    use master
    go
    select status from sysdatabases where name = "<database>" --- make note of Db status
    go

    sp_configure "allow updates to system tables",1
    go
    begin tran
    go
    update sysdatabases set status = -32768 where name = "<database>"
    go
    commit tran
    go
    use <database>
    go
    checkpoint
    go
    shutdown
    go
    --- Rebuild the transaction log
    use <database>
    go
    dbcc rebuild_log(<database>,1,1)
    go
    use master
    go
    begin tran
    go
    update sysdatabases set status = <original status> where name = "<database>"
    go
    commit tran
    go
    shutdown
    go
    ------------------------
    check if it worked
    -------------------

    use <database>
    go
    dbcc checktable(syslogs)
    go
    sp_configure "allow updates to system tables",0
    go

  3. #3
    Join Date
    Feb 2012
    Location
    Pune
    Posts
    11
    you can try with these steps:-
    Bypass recovery mode for the database :-
    use master
    go
    select status from sysdatabases where name = "<database>" --- make note of Db status
    go

    sp_configure "allow updates to system tables",1
    go
    begin tran
    go
    update sysdatabases set status = -32768 where name = "<database>"
    go
    commit tran
    go
    use <database>
    go
    checkpoint
    go
    shutdown
    go
    --- Rebuild the transaction log
    use <database>
    go
    dbcc rebuild_log(<database>,1,1)
    go
    use master
    go
    begin tran
    go
    update sysdatabases set status = <original status> where name = "<database>"
    go
    commit tran
    go
    shutdown
    go
    ------------------------
    check if it worked
    -------------------

    use <database>
    go
    dbcc checktable(syslogs)
    go
    sp_configure "allow updates to system tables",0
    go

Posting Permissions

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