B - Production Support » BSN CDB Support

Error occurred because of the duplicate primary key when inserting data in database.
It is due to passing an already existing id into database.

Expected solution: To query set the start increment with the latest primary key(oid) after get the data from JTM.

Please run these script in database. In SIT, the script is already running.

SELECT MAX (OID)+1 FROM DBO.IB_CONTENT_CATEGORY_ML;
Note: X = value from select max+1 OID.
ALTER TABLE DBO.IB_CONTENT_CATEGORY_ML ALTER COLUMN OID RESTART WITH X;

SELECT MAX (OID) FROM DBO.IB_CONTENT_CATEGORY;
SELECT * FROM DBO.IB_CONTENT_CATEGORY ORDER BY CREATION_DATE DESC;

If the data display already according with the latest OID no need to run the below script

SELECT MAX (OID)+1 FROM DBO.IB_CONTENT_CATEGORY;
Note: X = value from select max+1 OID.
ALTER TABLE DBO.IB_CONTENT_CATEGORY ALTER COLUMN OID RESTART WITH X;

It is to avoid the duplicate error when inserting new data with existing data with the same auto increment primary key(OID).

Test Scenario: 1. Perform create category in Content > Payee.
2. Run i) SELECT * FROM DBO.IB_CONTENT_CATEGORY ORDER BY OID DESC;
ii) SELECT * FROM DBO.IB_CONTENT_CATEGORY ORDER BY CREATION_DATE DESC;
iii)SELECT * FROM DBO.IB_CONTENT_CATEGORY_ML ORDER BY OID DESC; in SIT database.
3. See if the data save according to the latest set starting number.

send of SIT testing on 09/4/21

Tested and Passed on SIT (15/4/2021)

Kindly deploy the fixes to UAT environment.

Thank you

Hi Athira,
already run the script in uat database. Kindly proceed with UAT.

please prepare for pre prod deployment.

Production deployed on 07/05/2021

Migration ID0033