My Oracle Support Banner

Violations of AK_SNP_TECHNO and/or AK_SNP_DT1 Unique Constraint Are Signaled During ODI Upgrade or Import Operations (Doc ID 1911663.1)

Last updated on APRIL 07, 2020

Applies to:

Oracle Data Integrator - Version 11.1.1.3.0 to 11.1.1.9.99 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

NOTE: In this article, values used in errors (like internal id 1999), and sql commands represent a fictitious sample or default values for clarity.  These and any value placeholders including <> which surround the placeholders should all be replaced by the actual values used in your environment. Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.

Violations of AK_SNP_TECHNO and/or AK_SNP_DT1 unique constraints are signaled during either upgrade from Oracle Data Integrator (ODI) 10g to 11g, or import operations.

For example:

ODI-10035: SNP_TECHNO : 'Netezza' (with global id: <GLOBAL_ID> and internal id: <I_DT>) violates alternate key constraint AK_SNP_TECHNO <TECH_INT_NAME> for values NETEZZA

ODI-10212: The parent object SNP_TECHNO: 'Oracle' already has a child SNP_DT 'NCHAR.
Technical details: SNP_DT 'NCHAR' violates the constraint of replacement key AK_SNP_DT1 (I_TECHNO, DT_SOURCE) for the values (1999, NCHAR)

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.