Problem Note 56726: The Load_STG2DM_Profile job generates "ORA-00001: unique constraint (DI_TRANS.SYS_<constraint_nbr>) violated"
The SAS® Pack Optimization Load_STG2DM_Profile job might generate the following message in the Load_STG2DM_Profile.log file:
The following index(es) on table DI_TRANS.PROFILE were processed:
index DI_TRANS.SYS_<constraint_nbr> was made unusable due to:
ORA-00001: unique constraint (DI_TRANS.SYS_<constraint_nbr>) violated
Table DI_TRANS.PROFILE:
XXXX Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
In addition, messages similar to the following are also generated in the log file:
the value of processed_count is YYYY
the value of chunk_size is 1000
the value of processed_count is ZZZZ
NOTE: No Rows processed.
The Load_STG2DM_Profile job compares the PROFILE_ID values in the STG_PROFILE table to the PROFILE_ID values in the DI_TRANS.PROFILE table and checks for duplicates. If there are duplicates for PROFILE_ID, then the last duplicate record is kept and the others are moved to the job’s exception table. The deletion of existing PROFILE_ID keys from the DI_TRANS.PROFILE table is performed in chunks of 1000 keys at a time as indicated in the log file. The "Note: No Rows processed." message indicates no PROFILE_ID keys were deleted from the DI_TRANS.PROFILE table for that particular chunk of 1000 PROFILE_ID values, which results in the "ORA-00001..." message.
This issue occurs when you attempt to replace several existing very long PROFILE_ID values that are nearly consecutive in value.
Contact Technical Support for a workaround for this issue.
Operating System and Release Information
SAS System | SAS Pack Optimization | Linux for x64 | 3.2 | 3.4 | 9.3 TS1M1 | 9.4 TS1M3 |
64-bit Enabled AIX | 3.2 | 3.4 | 9.3 TS1M1 | 9.4 TS1M3 |
Microsoft® Windows® for x64 | 3.2 | 3.4 | 9.3 TS1M1 | 9.4 TS1M3 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Date Modified: | 2017-01-31 13:16:37 |
Date Created: | 2015-10-06 15:34:19 |