DLP Network Discover Scan is unable to remediate (copy/quarantine) files

Products

• Data Loss Prevention Core Package
• Data Loss Prevention Network Discover
• Data Loss Prevention
• Data Loss Prevention Discover Suite

Issue/Introduction

During a Network Discover scan, the server fails to remediate (copy or quarantine) files that match policies with associated response rules. The scan remains in Remediation Pending and never completes.

In SymantecDLPDetectorX.log you may see entries like:

11.09.2025 03:24:24 org.hibernate.engine.jdbc.batch.internal.BatchingBatch performExecution

ERROR: HHH000315: Exception executing batch [java.sql.BatchUpdateException: Non-atomic batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.], SQL: /* insert com.symantec.dlp.remediation.resiliency.model.RemediationRequest */ insert into RemediationRequest (allowedRemediationActionBits, contentRootId, contentRootLocation, isGridLeader, isGridScan, itemLocation, itemLocationPasswordText, itemLocationUserName, mountTimeoutMillis, remediationItemIdentifierId, remediatorType, requestState, scanAssignmentId, walkId, remediationRequestId) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)

11.09.2025 03:24:24 org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions

WARN: SQL Error: 20000, SQLState: XJ208

11.09.2025 03:24:24 org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions

ERROR: Non-atomic batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch. Use getNextException() to retrieve the exceptions for specific batched elements.

11.09.2025 03:24:24 org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions

WARN: SQL Error: 20000, SQLState: 23502

11.09.2025 03:24:24 org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions

ERROR: Error for batch element #0: Column 'ITEMLOCATIONPASSWORDKEYALIAS'  cannot accept a NULL value.

11.09.2025 03:24:24 com.vontu.discover.crawler.framework.scanupdate.RepositoryScanUpdateReceiver receiveUpdate

SEVERE: Failed to process scan update : RemediationStepUpdate [remediationItemIdentifier=Walk: 12101 Item path: <path>, remediationRequestResultData=RemediationRequestResultData [remediationAction=QUARANTINE, status=null, statusParams={}, policyId=2161, date=Thu Sep 11 03:24:24 CEST 2025, subTaskState=PRE_CHECK_COMPLETED]]

java.lang.IllegalStateException: Unable to find DB record for corresponding remediation item: //##.##.#.#/<path>/<file> for walk: 12101

at com.symantec.discover.protect.remediator.RemediationDBManagerImpl.updateRemediationRecord(RemediationDBManagerImpl.java:154)

at com.vontu.discover.crawler.framework.scanupdate.RemediationUpdateHandler.handleRemediationUpdate(RemediationUpdateHandler.java:119)

at com.vontu.discover.crawler.framework.scanupdate.RepositoryScanUpdateReceiver.receiveUpdate(RepositoryScanUpdateReceiver.java:291)

at com.vontu.discover.crawler.framework.grid.queue.DefaultLeaderQueueManager.queueMessageReceived(DefaultLeaderQueueManager.java:118)

at com.vontu.discover.crawler.framework.grid.queue.DefaultLeaderQueueManager.queueMessageReceived(DefaultLeaderQueueManager.java:45)

at com.symantec.dlp.messagequeue.activemq.AMQAsyncReceiver.onMessage(AMQAsyncReceiver.java:110)

at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1404)

at org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)

at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)

at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)

at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:750)

 

 

Environment

DLP 16.1

 

Cause

In some environments upgrading from versions prior to 16.1 leaves the RemediationRequest table with an additional column, ITEMLOCATIONPASSWORDKEYALIAS. When the upgraded components attempt to insert remediation records without a value for this column, the database returns "NULL not allowed", causing remediation to remain pending.

Resolution

Upgrade to 16.1 MP1 or later.

Fixed Issues in 16.1 MP1