search cancel

Endpoint Protection Manager truncates the SQL database transaction logs during the upgrade

book

Article ID: 163467

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

You observe that a Symantec Endpoint Protection Manager (SEPM) task truncates the SQL database transaction logs during the migration to a newer version. If auto-growth on the transaction logs is disabled, it can cause issues during or after the upgrade until the transaction logs are manually set to an appropriate size/limit. 

An example of such an issue is that one or more Symantec Endpoint Protection (SEP) installation packages fail to import.

"The transaction log for database 'SEPM_DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases"

Cause

"DBCC SHRINKFILE" on the transaction logs is always called during a SEPM upgrade and when adding a new SEPM replication partner with a Microsoft SQL database. This behavior is working as designed.

Environment

Symantec Endpoint Protection Manager with a SQL database.

Resolution

While auto-growth is not required during normal SEPM operations, it is currently required for upgrades and for adding a new SEPM replication partner. Once those tasks are complete the auto-growth option can be disabled, but the database will need to be monitored closely for errors and for the (growing) size of the transaction log. The database administrator or SEPM administrator should remember to incorporate a process to turn auto-growth back on before any upgrade and before adding any replication partner (even if the partner previously existed).

Symantec is working on implementing an option to turn off automatic truncation of transaction log during SEPM upgrade. This is planned to be implemented in SEP 14.2 RU2.

This issue is fixed in Symantec Endpoint Protection 14.2 RU2. For information on how to obtain the latest build of Symantec Endpoint Protection, see Download the latest version of Symantec software here.
In 14.2 RU2 and above, it is possible modify the /tomcat/etc/conf.properties file and add the line scm.upgrade.truncate.txnlog.enabled=false in order to avoid the transaction log to be truncated during the upgrade.