Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Fatal Error 669 - The row object is inconsistent. Please Rerun the query Expand / Collapse
Author
Message
Posted Wednesday, August 6, 2014 7:30 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, July 20, 2016 11:08 AM
Points: 194, Visits: 864
Hi All,

I'm troubleshooting an issue that's occurred in one of our applications, which produced error 669, severity 22 - The row object is inconsistent. Please rerun the query.

I've tried doing some research into this, and very little has come up.

The application itself is written in cold fusion and is using a loop to update a table (I'm currently rewriting this as a stored procedure), which I'll happily admit I know diddly squat about; so I've no idea whether that might cause an issue.

If I run the code manually in SQL it runs fine.

I've also run DBCC CHECKTABLE against the tables in question, which has shown no issue, and also run DBCC CHECKALLOC as well and no issues there. At this point I won't be able to run CHECKDB until I get a maintenance window.

The only other thing of note I can think of is that the page verification is set to TORN_PAGE_DETECTION; I'm going to request changing this to CHECKSUM, but not sure if that might cause an issue that means the corruption checks aren't as good as they might be?

Cheers

Matthew



Follow me on twitter @EvoDBA

Check out my blog Natural Selection DBA
Post #1600224
Posted Tuesday, June 7, 2016 5:57 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 22, 2016 4:21 AM
Points: 2, Visits: 88
Hello,

I am getting the same error. Did you manage to get to the bottom of this?
Post #1792669
Posted Tuesday, June 7, 2016 6:42 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, July 20, 2016 11:08 AM
Points: 194, Visits: 864
I never did, I'm afraid. If I recall, that piece of code was totally redeveloped into a stored procedure. In my honest opinion, I think it was something in which the way cold fusion was working..... badly.

Follow me on twitter @EvoDBA

Check out my blog Natural Selection DBA
Post #1792677
Posted Tuesday, June 7, 2016 6:50 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 6:30 AM
Points: 852, Visits: 1,605
Charlene, in your case this still could be corruption. Did you try DBCC?

----------------------------------------------------------------------------------------------------------------------------------------------------
Roshan Joe


Jeff Moden -Forum Etiquette: How to post data/code on a forum to get the best help
Post #1792680
Posted Tuesday, June 21, 2016 4:03 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 19, 2016 12:29 AM
Points: 169, Visits: 1,369
Please run this DBCC CHECKDB('CPS') WITH NO_INFOMSGS, ALL_ERRORMSGS and share the error message.

SQL Database Recovery Expert
Post #1796070
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse