Post reply

Transaction log full error - but no error in SQL log

  • December 15, 2004 at 11:19 am

    #91713

    I have a developer reporting this error: "Error -2147217900: The log file for database 'myDB' is full. Back up the transaction log for the database to free up some log space.".  But when I check the SQLServer Error log, there are no errors.  I'm using SQL Server 2000 Enterprise with SP3a.  Any clues?  I've increased the log file but very concerned that the error did not show up in the SQL log.

    Thanks!!

  • December 15, 2004 at 11:30 am

    #534003

    did you check the log space?

    dbcc sqlperf(logspace)

     

  • December 15, 2004 at 11:44 am

    #534008

    Yes. By the time the developer reported the problem, the log file had already been backed up (backup job runs every 30 minutes) and was in good shape. 

    Additional entries (ex: from the backup job) have been written to the SQL error log.  I thought that all Sev 19 errors would be written to the SQL error log.  We use MOM to scan the log and report any errors.  I'm very concerned that a sev 19 error was not written to the error log and uncomfortable that I may not be seeing other errors as well.

  • December 15, 2004 at 12:00 pm

    #534010

    dis you check available space on the disk. Maybe thats why errorlog stop writing

  • December 15, 2004 at 12:19 pm

    #534016

    Yes, 29gb free.  As mentioned, additional entries were made to the error log after the 9002 occurred.

Viewing 5 posts - 1 through 5 (of 5 total)

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