"Connectivity error ...Violation of PRIMARY KEY constraint 'PKNC_XDBxx'" when running a consolidation, caused by second Controller application server
User runs a consolidation. User opens the batch queue, and notices that the consolidation "Finished with Error". User double-clicks on the batch job and there is an error in the "details" section.
The message may vary slightly, but it will be similar to:
Connectivity error:[Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'PKNC_XDB14'. Cannot insert duplicate key in object 'dbo.xd
There are several possible causes for the generic error "Violation of PRIMARY KEY constraint 'PKNC_XDBxx'".
- TIP: For more examples, see separate IBM Technote #1455393.
This Technote specifically relates to the scenario where the cause is that the customer has mistakenly configured two different Controller application servers to simultaneously connect (via a database connection) to the same database.
Customer mistakenly has 2 separate Controller application servers (for example 'production' and 'test') with each having a database connection to the same database.
- This means that the batch jobs are being processed by *both* application servers simultaneously.
Resolving the problem
Only have one database connection (on one Controller application server) per database.