Schema Migration Fails With "Violation of PRIMARY KEY constraint 'pk_fintmpl'. Cannot insert duplicate key in object 'dbo.FINTMPL'. The duplicate key value is (1)"
(Doc ID 3075303.1)
Last updated on MARCH 19, 2025
Applies to:
Primavera P6 Professional Project Management - Version 22.12 to 23.12.12.0 [Release 22.12 to 23.12]Information in this document applies to any platform.
Symptoms
When attempting to run a schema migration (PPM to EPPM), error occurs.
ERROR
=======
01.08.2025 14:25:22 [INFO] [USER] Job Starting: Core PPM to PM Schema Migration
01.08.2025 14:25:22 [INFO] [USER] Job Starting: Run SQL Script ssppm_pm_migrate.sql
01.08.2025 14:33:07 [ERROR] Violation of PRIMARY KEY constraint 'pk_fintmpl'. Cannot insert duplicate key in object 'dbo.FINTMPL'. The duplicate key value is (1).
01.08.2025 14:33:07 [ERROR] Database Error: error number=2627
01.08.2025 14:33:07 [ERROR] Error Message: Violation of PRIMARY KEY constraint 'pk_fintmpl'. Cannot insert duplicate key in object 'dbo.FINTMPL'. The duplicate key value is (1).
01.08.2025 14:33:07 [WARN] [USER] Could not complete because the job "Run SQL Script ssppm_pm_migrate.sql" failed.
com.primavera.database.tools.DatabaseToolException: Violation of PRIMARY KEY constraint 'pk_fintmpl'. Cannot insert duplicate key in object 'dbo.FINTMPL'. The duplicate key value is (1).
01.08.2025 14:33:07 [INFO] [USER] Job Failed: Run SQL Script ssppm_pm_migrate.sql
01.08.2025 14:33:07 [INFO] [USER] Job Failed: Core PPM to PM Schema Migration
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |