Database error <>: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Duplicate entry '7F76FF9143B18EB70819608FF560B08A-0154FB3F43BC8095882A628DE63CFCF' for key 'PRIMARY'
CAUSE:
This issue is caused by lingering temporary rows that Strategy inserts and deletes upon connecting to the metadata. This operation is to ensure that the referential integrity trigger used when deleting objects is functioning properly so that inconsistencies are prevented. However, the temporary rows could still be present under one of two scenarios. The first is either an application crash, database server crash, or network interruption partway through the script being run. The other is that the trigger is missing or not functioning properly. Follow the steps below to determine if there are indeed duplicate rows within the metadata.
ACTION:
To determine if duplicate rows existit is necessary to query the metadata. Remember to take a backup of the metadata prior to performing any queries. In order to determine the specific metadata table in which the script is currently failing on check the DSSErrors.log. The duplicate row will always be contained in the very last row of the table and have "Dummy Name" as the OBJECT_NAME. An example is shown below in which the dummy row is returned when specifying the PROJECT_ID that is contained within the error message. If a similar query returns data, then duplicate row(s) exist within the metadata.
