Error 'ORA-00001: Unique constraint (ADMUSER.NDX_SETTING_ID) violated' When Running a Scheduled Service OR When Upgrading a Database Using the P6 EPPM 19.12.9 'dbsetup.bat' Tool (Doc ID 2183530.1)

Last updated on JUNE 21, 2023

Applies to:

Symptoms

When attempting to run a P6 Global Scheduled Service, the following error occurs in the log file:

[TASK]:[ResourceHour]: [26] CORE(SQL): DBEngine.executeStatement for {call settings_write_date(?, ?, ?)} failed: ORA-00001: unique constraint (ADMUSER.NDX_SETTING_ID) violated
ORA-06512: at "ADMUSER.SETTINGS_WRITE_STRING", line 21
ORA-06512: at "ADMUSER.SETTINGS_WRITE_DATE", line 8
ORA-06512: at line 1

The issue can be reproduced at will with the following steps:

1. Manually run a Global Scheduled Service (ex. project publication).
2. View the reported error message in the log file.

This issue can also occur when attempting to upgrade a P6 EPPM database using the version 19.12.9 dbsetup.bat utility.  The DatabaseSetup_<date>.log shows the following error:

[INFO] [USER] Upgrade from schema version 1712.0000.0000.0008 to schema version 1912.0000.0000.0009

[ERROR] ORA-00001: unique restriction violation (ADMUSER.NDX_SETTING_ID)
ORA-06512: at line 6

[ERROR] Database Error: error number=1
[ERROR] Error Message: ORA-00001: unique restriction violation (ADMUSER.NDX_SETTING_ID)
ORA-06512: at line 6

[WARN] [USER] Could not complete because the job "Run SQL Script ORPM_P17128.sql" failed.
com.primavera.database.tools.DatabaseToolException: ORA-00001: unique restriction violation (ADMUSER.NDX_SETTING_ID)
ORA-06512: at line 6

Changes

Cause