Upgrade to 6.10 fails with error "ALTER DATABASE ADD FILE and encryption changes on a database must be serialized"
search cancel

Upgrade to 6.10 fails with error "ALTER DATABASE ADD FILE and encryption changes on a database must be serialized"

book

Article ID: 403625

calendar_today

Updated On:

Products

Data Center Security Server Advanced

Issue/Introduction

Upgrade of Data Center Security (DCS) from 6.9.3 to 6.10 failed with the error below:

DB Installer failed!
Exception thrown:  java.lang.Exception: Failed to run SQL statement. 
    at com.symantec.dcs.server.install.sql.DbInstaller.runSqlStatements(DbInstaller.java:1175)
    at com.symantec.dcs.server.install.sql.DbInstaller.processSqlFile(DbInstaller.java:755)
    at com.symantec.dcs.server.install.sql.DbInstaller.processAllFiles(DbInstaller.java:697)
    at com.symantec.dcs.server.install.sql.DbInstaller.processAllFiles(DbInstaller.java:679)
    at com.symantec.dcs.server.install.sql.DbInstaller.run(DbInstaller.java:531)
    at com.symantec.dcs.server.substitutor.Substitutor.runDbInstaller(Substitutor.java:309)
    at com.symantec.dcs.server.substitutor.Substitutor.run(Substitutor.java:331)
    at com.symantec.dcs.server.substitutor.SubstitutorApp.run(SubstitutorApp.java:154)
    at com.symantec.dcs.server.substitutor.SubstitutorApp.main(SubstitutorApp.java:88)
Caused by: java.sql.SQLException: Failed to run SQL statement. 
    at com.symantec.dcs.server.install.sql.DbInstaller.executeSql(DbInstaller.java:1208)
    at com.symantec.dcs.server.install.sql.DbInstaller.runSqlStatements(DbInstaller.java:1170)
    ... 8 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.

Environment

Windows Server 2019

DCS 6.9.3.328 upgrade to 6.10

Cause

There was a backup job on the SQL starting every 1 hour and it started during DCS upgrade. 

Resolution

The issue was resolved by stopping the SQL backup job and re-running the upgrade.