Hi,
I have a strange problem in one of the SQL 2012 SP1 database. Sometimes my transaction log file grow unexpectedly than the preallocated space and i had to shrink it back . I usually preallocate space to around 15GB and the autogrow is set to 1000MB. The VLF count is less than 50. Database recovery model is Simple.
After i shrink the file and preallocate space again,everything seems to be normal.But later when the backup starts, SQL server starts generating the below error. The database will remain online and accept connections. Users do not get any errors or disconnected. The logs continue to grow as it cannot issue a checkpoint. We resolve this error by restarting SQL as database goes through crash recovery and comes up clean. Checkdb does not show any data corruption as well. I am not sure why the log gets corrupted after the shrink operation. Can someone please advice.
"The log scan number (10082614:43271:1) passed to log scan in database 'xyz' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup."
"One or more recovery units belonging to database 'xyz' failed to generate a checkpoint. This is typically caused by lack of system resources such as disk or memory, or in some cases due to database corruption. Examine previous entries in the error log for more detailed information on this failure."
Thanks