Log not available error 9001

  • shaun.stuart

    SSCertifiable

    Points: 6660

    Came in to work this morning to face a bunch of alerts for severity 21 errors.

    "DESCRIPTION: The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database."

    Hmm.. The drive the log is on was available and logs for other DB were on it. Plenty of space left. Window Application event log showed no errors other than the one listed above. Windows System log showed no errors. I ran dbcc checkdb on the database and the only error reported was that the log was not available.

    I took the database offline, then brought it online again and all seems good now. DBCC Checkdb gives no errors. DBCC loginfo(0) gives info, so I'm assuming the log is available. Now just trying to figure out what happened.

    Took a closer look at the SQL error log and I see this:

    12/20/2010 02:30:01,spid20s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    12/20/2010 02:30:01,spid20s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.

    12/20/2010 02:20:29,spid18s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    12/20/2010 02:20:29,spid18s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.

    12/20/2010 02:00:14,spid217,Unknown,Recovery completed for database NetPerfMon (database ID 18) in 6 second(s) (analysis 1 ms<c/> redo 1212 ms<c/> undo 4437 ms.) This is an informational message only. No user action is required.

    12/20/2010 02:00:13,spid217,Unknown,1 transactions rolled back in database 'NetPerfMon' (18). This is an informational message only. No user action is required.

    12/20/2010 02:00:09,spid217,Unknown,21 transactions rolled forward in database 'NetPerfMon' (18). This is an informational message only. No user action is required.

    12/20/2010 02:00:03,spid19s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    12/20/2010 02:00:03,spid19s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.

    12/20/2010 02:00:03,spid212,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.

    12/20/2010 02:00:03,spid212,Unknown,Configuration option 'user options' changed from 0 to 0. Run the RECONFIGURE statement to install.

    12/20/2010 02:00:03,spid15s,Unknown,Transaction (Process ID 15) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    12/20/2010 02:00:03,spid15s,Unknown,Error: 1205<c/> Severity: 13<c/> State: 51.

    12/20/2010 02:00:03,spid15s,Unknown,Transaction (Process ID 15) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    12/20/2010 02:00:03,spid15s,Unknown,Error: 1205<c/> Severity: 13<c/> State: 51.

    12/20/2010 02:00:02,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/20/2010 02:00:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/20/2010 01:30:01,spid204,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/20/2010 01:30:01,spid204,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/20/2010 01:00:01,spid217,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/20/2010 01:00:01,spid217,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/20/2010 00:30:01,spid206,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/20/2010 00:30:01,spid206,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/20/2010 00:00:23,spid18s,Unknown,This instance of SQL Server has been using a process ID of 1788 since 12/7/2010 9:47:54 PM (local) 12/8/2010 3:47:54 AM (UTC). This is an informational message only; no user action is required.

    12/20/2010 00:00:01,spid295,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/20/2010 00:00:01,spid295,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 23:30:01,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 23:30:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 23:00:01,spid215,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 23:00:01,spid215,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 22:30:02,spid210,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 22:30:01,spid210,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 22:00:01,spid223,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 22:00:01,spid223,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 21:30:01,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 21:30:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 21:00:01,spid203,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 21:00:01,spid203,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 20:30:02,spid203,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 20:30:01,spid203,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 20:00:01,spid222,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 20:00:01,spid222,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 19:30:01,spid217,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 19:30:01,spid217,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 19:00:03,spid212,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 19:00:02,spid212,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 18:30:01,spid212,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 18:30:01,spid212,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 18:00:01,spid218,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 18:00:01,spid218,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 17:30:01,spid196,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 17:30:01,spid196,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 17:00:02,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 17:00:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 16:30:01,spid214,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 16:30:01,spid214,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 16:00:01,spid229,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 16:00:01,spid229,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 15:30:02,spid205,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 15:30:02,spid205,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 15:00:02,spid219,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 15:00:01,spid219,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 14:30:01,spid213,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 14:30:01,spid213,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 14:00:01,spid204,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 14:00:01,spid204,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 13:30:01,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 13:30:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 13:00:02,spid223,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 13:00:01,spid223,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 12:30:01,spid222,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 12:30:01,spid222,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 12:00:02,spid215,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 12:00:01,spid215,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 11:30:01,spid203,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 11:30:01,spid203,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 11:00:01,spid220,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 11:00:01,spid220,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 10:30:01,spid206,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 10:30:01,spid206,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 10:00:02,spid212,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 10:00:02,spid212,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 09:30:02,spid214,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 09:30:01,spid214,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 09:00:03,spid225,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 09:00:01,spid225,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 08:30:01,spid199,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 08:30:01,spid199,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 08:00:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 08:00:01,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 07:30:02,spid204,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 07:30:01,spid204,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 07:00:01,spid216,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 07:00:01,spid216,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 06:30:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 06:30:01,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 06:00:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 06:00:00,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 05:30:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 05:30:01,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 05:00:01,spid217,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 05:00:01,spid217,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 04:30:01,spid207,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 04:30:01,spid207,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 04:00:04,spid215,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 04:00:04,spid215,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 04:00:00,spid207,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 04:00:00,spid207,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 03:30:01,spid198,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 03:30:01,spid198,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 03:00:05,spid234,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 03:00:04,spid234,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 02:52:32,spid78,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 02:52:32,spid78,Unknown,Starting up database 'SpotlightManagementFramework'.

    12/19/2010 02:52:29,spid71,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.

    12/19/2010 02:52:29,spid71,Unknown,Starting up database 'SpotlightManagementFramework'.

    2 AM is when my maintenance jobs run. It looks like, for some reason, checkdb got stuck in a loop on this database and had tons of spids working. The first "log uinavailable" error occurs at 12/20/10 2:00:03 with a state value of 5. The subsequent ones all have a state value of 1. I haven't been able to find out what the state value represents. I also noticed that the DBCC CHECKDB messages are appearing at times when DBCC is not scheduled to be run - at roughly half hour intervals through out the day. My transaction log backups run then, but I have verified that job does not perform dbcc.

    It looks like the clusters of checkdb messages started happening on 12/7/10 at 10 PM, which is just after I restarted the server after applying SQL 2008 SP2.

    Anyone have any ideas?

  • shaun.stuart

    SSCertifiable

    Points: 6660

    Figured out part of this.. Still don't know why the logfile was not available, but the repeated DBCC messages were due to the database having autoclose enabled. Each time the db is accessed, the db is started up and dbcc is run against it.

  • Andrew G

    SSChampion

    Points: 12687

    Was this ever resolved? I've had the exact same issue:

    Midday: Restored a database which had autoclose enabled.

    to

    1:31:43 pm: Starting up database 'xxxxxxxx'. (repeatedly due to auto-close)

    1:31:45 pm: Error: 1205, Severity: 13, State: 51.

    1:31:45 pm: Transaction (Process ID 19) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    1:31:46 pm: Error: 9001, Severity: 21, State: 5.

    1:31:46 pm: The log for database 'xxxxxxxx' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    Interesting that it's basically the same problem.. the log is corrupt, but the data is SELECTable. UPDATE or INSERTs fail with the message:

    Msg 9001, Level 21, State 1, Line 1

    The log for database 'TopCat_Mater_CYMH' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    Database is in simple recovery and no maintenance or backup tasks had been run as this was on a test server.

  • Andrew G

    SSChampion

    Points: 12687

    To resolve, I took the database offline, brought online, DBCC CHECKDB and found no alllocation or consistency errors. Very weird.

  • vultar

    Hall of Fame

    Points: 3150

    Thanks for your post.. I've just fixed a database with exactly the same error using this method 🙂 Have you had anymore thoughts as to why it occurred in the 1st place ?

    I've checked the logs etc but can't see clues to why it happened! Would be good to get to the root cause to prevent it from happening again.

    Cheers

    Vultar

  • Gail Shaw

    SSC Guru

    Points: 1004424

    Usually IO related, someone fiddled with permissions or the drive with the log file on didn't come online/failed/etc.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • chandan_jha18

    SSChampion

    Points: 11264

    I had this issue and found that the database had 'autoclose' option enabled and while trying to open that database it messed up with some system process and got killed. not sure what all happened there. I just disabled this option, took the database offline and back online and it fixed the issue.

    Thanks

    Chandan

  • Atze Ackermann

    Old Hand

    Points: 317

    Thanks, that was exactly what I needed!

  • sajal19866

    SSC Enthusiast

    Points: 121

    We faced exactly the same issue and found Database Auto_Close Option is set to 'True'. We set it False and put database offline and online. The error message stopped popping up soon after this. Still don't know why this option when set ON lead started triggering this error message because log was not corrupted and we were able to query on the database. :exclamation: :ermm:

  • Joy Smith San

    SSC-Insane

    Points: 24875

    .. How it works when taken to offline and then online again, any idea ?

  • MSQLDBA

    SSCrazy

    Points: 2742

    Hi Buddies,

    I am facing the same problem even my database Auto_close option is False. When the application team running package, database going on suspect mode. rest of the time its working fine. I am also not getting any error message in Evnt log and SQL server error log for the same. I put database on emergency mode and run dbcc checkdb i found one table corruption in the database, after putting database on online i didn't get any corruption in the database, result is showing no error.

    Could you please help me to fix this issue?

    Thanks in advance.

    M.I

    ________________________________________
    M.I.
    [font="Times New Roman"]

    Learning is a path with no destination...
    [/font]

  • chandan_jha18

    SSChampion

    Points: 11264

    MSQLDBA (12/12/2013)


    Hi Buddies,

    I am facing the same problem even my database Auto_close option is False. When the application team running package, database going on suspect mode. rest of the time its working fine. I am also not getting any error message in Evnt log and SQL server error log for the same. I put database on emergency mode and run dbcc checkdb i found one table corruption in the database, after putting database on online i didn't get any corruption in the database, result is showing no error.

    Could you please help me to fix this issue?

    Thanks in advance.

    M.I

    Do you have the checkdb output handy? Can you paste it here.

    Thanks

    chandan

  • MSQLDBA

    SSCrazy

    Points: 2742

    Thanks for the reply,

    Run DBCC CHECKDB in Emergency mode:

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

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156536) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156537) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156538) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156539) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156540) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156541) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156542) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    Msg 2533, Level 16, State 1, Line 1

    Table error: page (1:1156543) allocated to object ID 2121058592, index ID 0, partition ID 72057594038845440, alloc unit ID 72057594166050816 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.

    CHECKDB found 0 allocation errors and 8 consistency errors in table 'Table1' (object ID 2121058592).

    CHECKDB found 0 allocation errors and 8 consistency errors in database 'AdventureDB'.

    repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (AdventureDB).

    After DB come Online DBCC Checkdb result:

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

    DBCC results for 'AdventureDB'.

    Service Broker Msg 9675, State 1: Message Types analyzed: 14.

    Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.

    Service Broker Msg 9667, State 1: Services analyzed: 3.

    Service Broker Msg 9668, State 1: Service Queues analyzed: 3.

    Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.

    Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.

    Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.

    Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.

    DBCC results for 'sys.sysrscols'.

    There are 965 rows in 10 pages for object "sys.sysrscols".

    DBCC results for 'sys.sysrowsets'.

    There are 98 rows in 1 pages for object "sys.sysrowsets".

    DBCC results for 'sys.sysallocunits'.

    There are 116 rows in 2 pages for object "sys.sysallocunits".

    DBCC results for 'sys.sysfiles1'.

    There are 2 rows in 1 pages for object "sys.sysfiles1".

    DBCC results for 'sys.syspriorities'.

    There are 0 rows in 0 pages for object "sys.syspriorities".

    DBCC results for 'sys.sysfgfrag'.

    There are 2 rows in 1 pages for object "sys.sysfgfrag".

    DBCC results for 'sys.sysphfg'.

    There are 1 rows in 1 pages for object "sys.sysphfg".

    DBCC results for 'sys.sysprufiles'.

    There are 2 rows in 1 pages for object "sys.sysprufiles".

    DBCC results for 'sys.sysftinds'.

    There are 0 rows in 0 pages for object "sys.sysftinds".

    DBCC results for 'sys.sysowners'.

    There are 20 rows in 1 pages for object "sys.sysowners".

    DBCC results for 'sys.sysprivs'.

    There are 136 rows in 1 pages for object "sys.sysprivs".

    DBCC results for 'sys.sysschobjs'.

    There are 64 rows in 1 pages for object "sys.sysschobjs".

    DBCC results for 'sys.syscolpars'.

    There are 824 rows in 24 pages for object "sys.syscolpars".

    DBCC results for 'sys.sysnsobjs'.

    There are 1 rows in 1 pages for object "sys.sysnsobjs".

    DBCC results for 'sys.syscerts'.

    There are 0 rows in 0 pages for object "sys.syscerts".

    DBCC results for 'sys.sysxprops'.

    There are 0 rows in 0 pages for object "sys.sysxprops".

    DBCC results for 'sys.sysscalartypes'.

    There are 34 rows in 1 pages for object "sys.sysscalartypes".

    DBCC results for 'sys.systypedsubobjs'.

    There are 0 rows in 0 pages for object "sys.systypedsubobjs".

    DBCC results for 'sys.sysidxstats'.

    There are 188 rows in 10 pages for object "sys.sysidxstats".

    DBCC results for 'sys.sysiscols'.

    There are 333 rows in 3 pages for object "sys.sysiscols".

    DBCC results for 'sys.sysbinobjs'.

    There are 23 rows in 1 pages for object "sys.sysbinobjs".

    DBCC results for 'sys.sysaudacts'.

    There are 0 rows in 0 pages for object "sys.sysaudacts".

    DBCC results for 'sys.sysobjvalues'.

    There are 187 rows in 57 pages for object "sys.sysobjvalues".

    DBCC results for 'sys.sysclsobjs'.

    There are 16 rows in 1 pages for object "sys.sysclsobjs".

    DBCC results for 'sys.sysrowsetrefs'.

    There are 0 rows in 0 pages for object "sys.sysrowsetrefs".

    DBCC results for 'sys.sysremsvcbinds'.

    There are 0 rows in 0 pages for object "sys.sysremsvcbinds".

    DBCC results for 'sys.sysxmitqueue'.

    There are 0 rows in 0 pages for object "sys.sysxmitqueue".

    DBCC results for 'sys.sysrts'.

    There are 1 rows in 1 pages for object "sys.sysrts".

    DBCC results for 'sys.sysconvgroup'.

    There are 0 rows in 0 pages for object "sys.sysconvgroup".

    DBCC results for 'sys.sysdesend'.

    There are 0 rows in 0 pages for object "sys.sysdesend".

    DBCC results for 'sys.sysdercv'.

    There are 0 rows in 0 pages for object "sys.sysdercv".

    DBCC results for 'sys.syssingleobjrefs'.

    There are 146 rows in 1 pages for object "sys.syssingleobjrefs".

    DBCC results for 'sys.sysmultiobjrefs'.

    There are 121 rows in 1 pages for object "sys.sysmultiobjrefs".

    DBCC results for 'sys.sysguidrefs'.

    There are 0 rows in 0 pages for object "sys.sysguidrefs".

    DBCC results for 'sys.syscompfragments'.

    There are 0 rows in 0 pages for object "sys.syscompfragments".

    DBCC results for 'sys.sysftstops'.

    There are 0 rows in 0 pages for object "sys.sysftstops".

    DBCC results for 'sys.sysqnames'.

    There are 97 rows in 1 pages for object "sys.sysqnames".

    DBCC results for 'sys.sysxmlcomponent'.

    There are 99 rows in 1 pages for object "sys.sysxmlcomponent".

    DBCC results for 'sys.sysxmlfacet'.

    There are 112 rows in 1 pages for object "sys.sysxmlfacet".

    DBCC results for 'sys.sysxmlplacement'.

    There are 18 rows in 1 pages for object "sys.sysxmlplacement".

    DBCC results for 'sys.sysobjkeycrypts'.

    There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".

    DBCC results for 'sys.sysasymkeys'.

    There are 0 rows in 0 pages for object "sys.sysasymkeys".

    DBCC results for 'sys.syssqlguides'.

    There are 0 rows in 0 pages for object "sys.syssqlguides".

    DBCC results for 'sys.sysbinsubobjs'.

    There are 3 rows in 1 pages for object "sys.sysbinsubobjs".

    DBCC results for 'sys.syssoftobjrefs'.

    There are 0 rows in 0 pages for object "sys.syssoftobjrefs".

    DBCC results for 'REP_DatasetAttributeDefinition'.

    There are 381 rows in 9 pages for object "REP_DatasetAttributeDefinition".

    DBCC results for 'REP_LifeCycle'.

    There are 0 rows in 0 pages for object "REP_LifeCycle".

    DBCC results for 'sys.queue_messages_1977058079'.

    There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".

    DBCC results for 'sys.queue_messages_2009058193'.

    There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".

    DBCC results for 'sys.queue_messages_2041058307'.

    There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".

    DBCC results for 'sys.filestream_tombstone_2073058421'.

    There are 0 rows in 0 pages for object "sys.filestream_tombstone_2073058421".

    DBCC results for 'sys.syscommittab'.

    There are 0 rows in 0 pages for object "sys.syscommittab".

    DBCC results for 'REP_Associations'.

    There are 3044883 rows in 173635 pages for object "Table1".

    DBCC results for 'REP_TransposedDocAttributes'.

    There are 92415 rows in 5125 pages for object "Table2".

    DBCC results for 'REP_TagAttributes'.

    There are 13736431 rows in 906374 pages for object "Table3".

    DBCC results for 'REP_TransposedTagAttributes'.

    There are 704117 rows in 74856 pages for object "Table4".

    DBCC results for 'REP_DocAttributes'.

    There are 749995 rows in 38073 pages for object "Table5".

    CHECKDB found 0 allocation errors and 0 consistency errors in database 'AdventureDB'.

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    ________________________________________
    M.I.
    [font="Times New Roman"]

    Learning is a path with no destination...
    [/font]

  • SevereIdea

    SSC Enthusiast

    Points: 146

    THANKS!!! I had a db that up until today was doing a CHECKDB every few seconds... never reported any errors, but certainly filling up my event log. Yesterday the db hit a deadlock and then all of sudden the log file became unavailable... restored the last good back up and it all happened again.... 3x in 2 days.... setting the auto_close to OFF seems to have resolved the issue. Why was that even set? could it have been because this particular database was upsized from Access <facepalm> before I came on board here? IDK, but I think this is fixed now. Just wanted to say THANKS!!

  • Gail Shaw

    SSC Guru

    Points: 1004424

    SevereIdea (2/13/2014)


    THANKS!!! I had a db that up until today was doing a CHECKDB every few seconds... never reported any errors, but certainly filling up my event log.

    It wasn't running checkDB every few seconds. It was closing and reopening every few seconds and when SQL opens a database it prints the last date checkDB succeeded into the error log.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 15 posts - 1 through 15 (of 25 total)

You must be logged in to reply to this topic. Login to reply