Jira server fails to start with full MS-SQL transaction log error
Symptoms
JIRA is unable to start up due to a SQL Exception.
The following appears in the atlassian-jira.log:
2013-07-26 08:49:03,821 Spring executor 11 ERROR [module.propertyset.ofbiz.OFBizPropertySet] Error removing value from PropertySet
org.ofbiz.core.entity.GenericDataSourceException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM dbo.propertytext WHERE ID=? (The transaction log for database 'JIRA' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases))
at org.ofbiz.core.entity.GenericDAO.deleteByAnd(GenericDAO.java:1247)
at org.ofbiz.core.entity.GenericHelperDAO.removeByAnd(GenericHelperDAO.java:193)
at org.ofbiz.core.entity.GenericDelegator.removeByAnd(GenericDelegator.java:1101)
...
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:DELETE FROM dbo.propertytext WHERE ID=? (The transaction log for database 'JIRA' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases)
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:650)
at org.ofbiz.core.entity.GenericDAO.deleteByAnd(GenericDAO.java:1284)
at org.ofbiz.core.entity.GenericDAO.deleteByAnd(GenericDAO.java:1244)
...
java.sql.SQLException: The transaction log for database 'JIRA' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)Diagnosis
JIRA is connected to an MS SQL Server.
Cause
The transaction log for the database is full, and the database is no longer able to function until this can be resolved. Subsequently, JIRA is unable to be used as it has a dependency upon a working database.
Resolution
Please refer to the Troubleshoot a Full Transaction Log (SQL Server Error 9002) KB for full details on how to go about fixing this problem. Please keep in mind that you will need to stop all Jira nodes to perform the suggested changes in this article.
If further assistance is required, please raise this with Microsoft Technical Support and your DBA as they will be best skilled to assist in the resolution of the problem.