Saturday, May 11, 2013

[SQL 2012] SQL2012SP1, simple recovery, transaction log full, can't add another, won't grow

[SQL 2012] SQL2012SP1, simple recovery, transaction log full, can't add another, won't grow

SQL2012SP1, simple recovery, transaction log full, can't add another, won't grow

Posted: 11 May 2013 03:21 AM PDT

SUMMARY:I have many databases with full transaction logs. They are already in SIMPLE recovery model,and I cannot add a new log or truncate the existing one, because the transaction log is full due to 'CHECKPOINT'DETAILS:(Examining just one of the problematic databases)I have a SQL Server 2012 SP1 database with a full transaction log.This database has one data file (750MB) and one log file (850MB)Compatibility level = SQL Server 2012 (110)Recovery Model is SimpleUnder Recovery Options, Page Verify=CHECKSUM and Target Recovery Time=0I had 5G of free disk (which should have been enough), and I added more, so now I have 25G free.My log file growth is set to: "By 10 percent, Limited to 2097152 MB " (I can't change it - if I try I get an error because the transaction log is full)I can't do a backup - get an error because the transaction log is full due to 'CHECKPOINT'I can't add another log file - get an error because the transaction log is full due to 'CHECKPOINT'Verifying that file#2 is my log file[code] SELECT file_id, name FROM sys.database_files; [/code]I can't do a truncate only shrink successfully:[code] DBCC SHRINKFILE (2, TRUNCATEONLY);[/code] - get an error because my log is out of space - with a cascade error that the transaction log is full due to 'CHECKPOINT'DBCC CHECKDB mostly just gives errors because the transaction log is full due to 'CHECKPOINT'I can't change the recovery model to full - get an error because the transaction log is full due to 'CHECKPOINT'I can't change the recovery model to bulk-logged - get an error because the transaction log is full due to 'CHECKPOINT'From sys.databases,is_read_only=0, state=0, state_desc=ONLINE, is_in_standy=0is_cleanly_shutdown=0, is_supplemental_logging_enabled=0is_read_committed_snapshot_on=0recovery_model=3, recovery_model_desc=SIMPLEis_fulltext_enabled=1is_published=0, is_subscribed=0, is_merge_published=0, is_distributed=0, is_sync_with_backup=0is_broker_enabled=1, log_reuse_wait=1, log_reuse_wait_desc=CHECKPOINTI tried doing a manual CHECKPOINT (using the CHECKPOINT cmd in MgmtStudio) and got errors:[quote](1 row(s) affected)Msg 5901, Level 16, State 1, Line 3One or more recovery units belonging to database 'MYDATABASENAME' 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.Msg 9002, Level 17, State 1, Line 3The transaction log for database 'MYDATABASENAME' is full due to 'CHECKPOINT'. [/quote][code]SELECT count(*) FROM fn_dblog (NULL, NULL);[/code]4,521,289That seems like a lot !?My ERRORLOGs are full of errors about full transaction logs. I have many databases with this same issue - I've just focused on one, for testing.DBCC OPENTRAN gives me no open transactionsHowever, [code]select * from sys.dm_tran_database_transactions where database_id = MYDBID[/code]gives me 6 rows, of which 4 have null begin timesI tried using[code] select request_session_id, * from sys.dm_tran_locks where resource_database_id = MYDBID and resource_subtype = 'BULKOP_BACKUP_LOG'[/code]and killing those sessions, but they always come back immediately

confusion about SSAS security

Posted: 10 May 2013 09:58 AM PDT

hi everyonei am quite confused about read contingent security for cube cell data? I know that it is much stricter than read permission and that it applies to calculated members, but not much morecan anyone please explain it further
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog