Transaction log full
Logs:
Depends On Me: com.adventnet.persistence.DataAccessException: [TierComponent] The transaction log for database 'supportcenter' 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.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1155)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:607)
Solution:
Please run the following query to shrink the size of the transaction log.
Depends On Me: com.adventnet.persistence.DataAccessException: [TierComponent] The transaction log for database 'supportcenter' 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.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1155)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:607)
Solution:
There are two methods to fix this issue.
Method 1:
Method 1:
Please run the following query to shrink the size of the transaction log.
Executing this query brought the LDF file to around 1MB.
USE supportcenter
GO
DBCC SHRINKFILE (supportcenter_log, 1)
BACKUP LOG supportcenter WITH TRUNCATE_ONLY
DBCC SHRINKFILE (supportcenter_log, 1)
GO
exec sp_helpfile
Please run this query after taking a Backup of the Database.
You can run the Script to re-index the Tables in the DB.This shouldn't cause any problems.
The only thing that we insist on is to take a back up of the database before you attempt any of these steps on the DB.
Please set the transactions logs growth to say 4 GB and set it to unrestricted growth, so that the logs will grow to the mentioned limit and then will overwrite the. This will prevent the logs to grow in size.
Method 2
To fix this issue, we have to detach SupportCenter database, after detaching we can delete the transaction log ( .LDF log)
and attach the SupportCenter database back.
The important part in this process of attaching database will be removing the log path.The attaching database configuration window will show the path of the log (.LDF log), we have to remove the log path only then we will be able to attach the database.
Following steps given below, explains in detail about the process of attaching and detaching database.
# Stop the SupportCenter Plus service.
# Connect to the SQL database, take a SQL backup and detach supportcenter database.
# After detaching the database, goto the location where the .LDF log file is located.
Follow the screenshots given below to delete the .LDF log
Eg:-
C:\\Program Files\\Microsoft SQL Server\\MSSQL10.SQLEXPRESS\\MSSQL\\DATA
Delete the "mike_log.LDF" log file
# Import and add the detached SupportCenter database as per the screenshot given below.
# In order to complete SupportCenter database attaching process, remove the .LDF log file path as per the screen shot given below and click OK.
The important part in this process of attaching database will be removing the log path.The attaching database configuration window will show the path of the log (.LDF log), we have to remove the log path only then we will be able to attach the database.
# Restart the SupportCenter Plus service.
New to ADSelfService Plus?
Related Articles
The transaction log (Servicedesk_log.ldf) for database 'servicedesk' is full
There are two methods to fix this issue. Method 1 To fix this issue, we have to detach ServiceDesk database, after detaching we can delete the transaction log ( .LDF log) and attach the ServiceDesk database back. The important part in this process of ...Alternative for Full Backup - Trimmed backup
Applicable till 8.1 version (Till 8121 builds) Nowadays the database size is huge in various users instance. It is because the indexing related files, archived files, file attachments are folder are huge in size. Due to which either our application ...To Change the application log directory
Environment: Windows Notes: This kb is not recommended. The support file (Community -> Troubleshoot -> Support File) will be generated with log files which are generated using the bat files. The new logs, generated in changed log directory won't be ...Workaround to add Customized Header Image
This is applicable only 110XX builds (till 11021). In 11021 users are unable to change the logo of the header image due to the Issue ID - 2538. Below mentioned is the workaround to add Customized Header Image. -> In the application path ...Workaround: Complete the current mail schedule after a timeout value
Issue: The mail fetching schedule thread might have went unresponsive in certain scenarios. So, mail fetching task checker thread will try to create a new schedule every 30 minutes. The newly created thread also couldn't fetch mails as the entry in ...