Solution : https://service.sap.com/sap/support/notes/11369 (SAP Service marketplace login required)
Summary :
The SAP Note addresses the error ORA-1452, which prevents creating a unique index due to duplicate keys found when importing datasets from a source system. The duplicity might arise from rollback issues in ORACLE 7.0.13 with cluster tables containing long raw fields. The solution involves identifying the duplicate records using SQL queries and then optionally creating a NONUNIQUE index to expedite the search. If records are absolutely identical, they can be safely deleted using ROWID. After deleting duplicates, the unique index can be created. For discrepancies, consult the developer for correction.
Key words :
recordswith multiple key values, significantly shorter runtime, long raw fields, 2 key columns c1, create unique index, unique index existed, duplicate keys foundwhen, -key fields, unique index, duplicate keys
Related Notes :
541538 | FAQ: Reorganization |