Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

What causes the error "Table "Sessionlog". The transaction log for database "DBName" is full" - and how can this be recovered or avoided?

What causes the error "Table "Sessionlog". The transaction log for database "DBName" is full" - and how can this be recovered or avoided?

Problem

What causes the error  - "Table "Sessionlog". The transaction log for database "DBName"  is full" - and how can this be recovered or avoided?

Resolution

The log that is full, is the database transaction log, which is generated by MS SQL Server.

The log is generated and the space it uses, are controlled by the MS SQL Server Option "Recovery Model"

Enterprise Analyzer will work with either "Simple", "Full" or "Bulk Logged"  recovery model.

The attached document describes the models available and how they work.

Recovery Model Overview.docx

The problem is that the recovery model "Full" or "Bulk Logged" is being used, and no database backups are being performed.  This means that the log will continue to grow until either, a) the database runs out of physical space or cannot be extened, or b) a database backup is performed.

A database backup will, backup the database, clear down the log and release the space it has used, ready for re-use.

Micro Focus recommend that a backup/recovery plan/process is set up to secure the repository, as this is not supplied with the Enterprise Analyzer product, and would be the responsibility of the Database Administrator.

Incident#2802420


					
				
			
			
			
				

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2014-12-05 08:53
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.