none
Attempt to fetch logical page in database 2 failed.

    Question

  • Hi,

    I have facing following error...
    How to resolved this issue..?

    Msg 605, Level 21, State 3, Procedure sp_LiveFolio, Line 14

    Attempt to fetch logical page (1:519806) in database 2 failed. It belongs to allocation unit 450928123772928 not to 562949955649536.

     

    Thursday, July 23, 2009 12:23 PM

Answers

  • Run a DBCC CHECKDB on the problem database.  The resulting messages will indicate the minimal repair level needed.  If ALLOW_DATA_LOSS level is required, you might consider restoring from you last known good backup instead.  See the Books Online for details.

    --
    Hope this helps.
     
    Dan Guzman
    SQL Server MVP
    http://weblogs.sqlteam.com/dang /

    Hi,

    I have facing following error...
    How to resolved this issue..?

    Msg 605, Level 21, State 3, Procedure sp_LiveFolio, Line 14

    Attempt to fetch logical page (1:519806) in database 2 failed. It belongs to allocation unit 450928123772928 not to 562949955649536.

     

    Thursday, July 23, 2009 12:30 PM

All replies

  • What is your procedure attempting to do?

    Are you working with temp tables? If so, maybe this article will help: http://support.microsoft.com/default.aspx/kb/960770
    JP
    Please click the Mark as Answer button if a post solves your problem!
    http://www.johnvpetersen.com
    Thursday, July 23, 2009 12:29 PM
  • Run a DBCC CHECKDB on the problem database.  The resulting messages will indicate the minimal repair level needed.  If ALLOW_DATA_LOSS level is required, you might consider restoring from you last known good backup instead.  See the Books Online for details.

    --
    Hope this helps.
     
    Dan Guzman
    SQL Server MVP
    http://weblogs.sqlteam.com/dang /

    Hi,

    I have facing following error...
    How to resolved this issue..?

    Msg 605, Level 21, State 3, Procedure sp_LiveFolio, Line 14

    Attempt to fetch logical page (1:519806) in database 2 failed. It belongs to allocation unit 450928123772928 not to 562949955649536.

     

    Thursday, July 23, 2009 12:30 PM
  • I've not seen it documented anywhere, but on several occasions I have received that error only to find no errors reported after running DBCC CheckDB.  In all cases it was on a SQL 2005 server running with AWE memory enabled.  Stopping and restarting SQL Server eliminates the error.  I believe the AWE memory management page allocation is the  issue.

     

     

    Monday, June 07, 2010 10:01 PM
  • We have a single customer out of thousands with identical databases that experienced this issue. They were on SQL 10.50.2500.  It happened sometimes when they ran a procedure that used a temp table for some heavy lifting. The temp table had an identity column and I neglected to make the column a Primary Key (as I normally would.) After doing so, the problem was resolved for the customer.

    Thursday, April 12, 2012 6:30 PM