KBI 310776 Issue Addressed: SQL Bulk Insert Can Fail In Argent Non-Stop Monitor Environment


Argent Advanced Technology 3.1A-1310-A and earlier


Wednesday, 11 Dec 2013


In Argent Non-Stop Monitor environment using a remote SQL Server, Motors generally need to use a shared folder at SQL Server or SQL Server Cluster to put the SQL Bulk Insert data, so that the SQL Server can run the SQL Bulk Insert query using a local path

But because Motors use the same shared folder, they may compete for the same data file when to execute the SQL Bulk Insert query

As results, at least one Motor can fail executing the query due to unique key constraint as another Motor is already in the middle of executing the SQL Bulk Insert

Technical Background

Argent AT 3.1A-1401-A addresses the issue by renaming the SQL Bulk Insert data file with TMP extension so that other motors won’t attempt to process the same file


Upgrade to Argent Advanced Technology 3.1A-1401-A or later