iVend Primary Key Violation issue after Re-initialize of Store

iVend Primary Key Violation issue after Re-initialize of Store

Product Version: 

6.5 Update 6 Patch 2


Problem Statement - 

Primary Key Violation issue after Re-initialize of Store.


Proposed Solution: - 

We require to increase sysnextnumber for smooth function of store.


Steps if any: 

Below are the steps we require to follow-up to resolve the issue.


Step 1 -Take backup from iVend Enterprise for the specific store


Step 2 -Re-initialize the store from backup copy generated from iVend Enterprise.


Step 3 - Do not configure the replication at Store or if it is already configured never start the replication


Step 4 - Never allow customer to perform the transactions


Step 5 - Inform CXS Support and share information i.e. customer DB crashed and all the records in SysNextNumber need to be incremented by 0.7 million (700000)


Constraints / Scenarios: 

Please note this is applicable if the customer is having iVend version less than 6.6 as with or post 6.6 version primary key generation mechanism is completely changed and these instructions will never be required.