2801 Duplicate Unique Prime Key Error
Contents |
baseUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean: Teradata : Product Forums : Database : duplicate unique primary key error Options Subscribe
2801 Duplicate Unique Prime Key Error In Teradata
to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to teradata 2801 error the Top Bookmark Subscribe Printer Friendly Page sharad Fan Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Get Direct failure 2801 duplicate unique prime key error in teradata Link Print Email to a Friend Report Inappropriate Content 01-19-2006 03:46 PM 01-19-2006 03:46 PM duplicate unique primary key error Hi, I had to modify a column's width so i created a temporary table, with modified
Duplicate Unique Prime Key Error In Target Table
column width, and populated that temporary table through (insert into temp select * from original_table).Later I dropped the original_table and renamed the temporary table to the original one. The original_table had id as the unique primary index and was defined as "Id INTEGER NOT NULL GENERATED BY DEFAULT AS IDENTITY". Now I am not able to insert data in this table manually through insert query. It gives me error as "duplicate
Duplicate Unique Key Error Wow
unique primary key error". Any solutions to rectify this situations. Please Help!!Thanks & Regards, 0 Kudos Reply All Forum Topics Previous Topic Next Topic 2 REPLIES Fred Teradata Employee Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Get Direct Link Print Email to a Friend Report Inappropriate Content 01-19-2006 11:00 PM 01-19-2006 11:00 PM Re: duplicate unique primary key error GENERATED BY DEFAULT columns are not guaranteed to be unique anyway, but if you're sure that's what you want: create another table but specify that generated values START WITH a value beyond anything already present in the table; INSERT/SELECT the data, drop old, rename again.Since you have to copy the data to a new table anyway, consider whether GENERATED ALWAYS NOCYCLE would be better for your application. (Of course, then you wouldn't use "SELECT *" because you're not allowed to specify a value to insert into that column). 0 Kudos Reply DEEPU Enthusiast Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Get Direct Link Print Email to a Friend Report Inappropriate Content 01-20-2006 12:29 PM 01-20-2006 12:29 PM Re: duplicate unique primary key error Sharad,UPK error occurs only when the UPI column that you are trying to insert is alraedy present there in your table.Check if you are passin
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack duplicate unique key 211489 Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Teradata identity column and “Duplicate unique prime key error in dbname.tablename” up vote 0 down vote favorite http://community.teradata.com/t5/Database/duplicate-unique-primary-key-error/td-p/383 I created a table using the below definition for a Teradata identity column: ID INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 1 INCREMENT BY 1 MINVALUE 0 MAXVALUE 100000000 NO CYCLE), ---- UNIQUE PRIMARY INDEX ( ID ) For several months, the ID column has been working properly, automatically generating a unique value for the column. Over the past month, however, ELMAH has been intermittently reporting the following exception from http://stackoverflow.com/questions/11727972/teradata-identity-column-and-duplicate-unique-prime-key-error-in-dbname-tablena our .NET 4.0 ASP.NET app: Teradata.Client.Provider.TdException: [Teradata Database] [2801] Duplicate unique prime key error in DATABASENAME.TABLENAME. I was able to replicate it by opening SQL Assistant and inserting a bunch of records into the table with raw SQL. As expected, most of the time it would insert successfully, but other times it would throw the above exception. It appears that this error is occuring because Teradata is trying to generate a value for this column that it has previously generated. Does anyone have any idea how to get to the bottom of what's happening? At the very least, I'd like some way to debug the issue a bit deeper. unique identity teradata share|improve this question asked Jul 30 '12 at 19:06 oscilatingcretin 2,8211468130 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote I would suggest changing the definition of your identity column to GENERATED ALWAYS to prevent the application or ETL process from supplying a value that could have been used. In fact, it is recommended by Teradata that if you are using your IDENTITY column as part of a UPI that it should be defined as GENERATED ALWAYS ... NO CYCLE EDIT: If your business requirements are such that you must be able to provide a val
location is: KBSolution21Pages143113 Sign In Log In | Sign Up | Log out https://kb.informatica.com/solution/21/Pages/143113.aspx Feedback Authoring Home Toggle navigation Network Home Informatica.com Communities Big Data Management Big Data Management Edition Big Data Parser Big Data Management Trial Edition Cloud Integration Cloud Application Integration Cloud Data Integration Cloud Customer 360 DiscoveryIQ Cloud Data Wizard Informatica Cloud for Amazon AWS Complex Event Processing Proactive Healthcare Decision Management Proactive Monitoring Real-Time duplicate unique Alert Manager Rule Point Data Integration B2B Data Exchange B2B Data Transformation Data Integration Hub Data Replication Data Services Data Validation Option Fast Clone Informatica Platform Metadata Manager PowerCenter PowerCenter Express PowerExchange PowerExchange Adapters Data Quality Address Doctor Address Doctor Cloud Data as a Service Data Explorer Data Quality Data Quality Services (Strike Iron) duplicate unique prime Data Security Group (Formerly ILM) Data Archive Data Centric Security Secure@Source Secure Testing Master Data Management Identity Resolution MDM Big Data Relationship Management MDM Multidomain Edition MDM Registry Edition Process Automation ActiveVOS Cloud Extend Product Information Management Informatica Procurement Product Information Management Ultra Messaging Ultra Messaging Options Ultra Messaging Persistence Edition Ultra Messaging Queuing Edition Ultra Messaging Streaming Edition Vibe Data Stream Documentation Knowledge Base Resources PAM (Product Availability Matrices) Support TV Informatica Expert Assistant Velocity (Best Practices) Mapping Templates Debugging Tools User Groups Informatica Network Knowledge Base 21 KB > Solution > 21 > Pages > 143113 KB Home Page Authoring Home Top Link Bar KBCurrently selected FAQHowToSolution 6789 WhitepapersKBOktaSyncAdminKBOktaSync KB Search Authoring Home Search Demo Quick Launch Rate It: Average Rating: ERROR: "Duplicate unique prime key error in Schema.table_name" when performing the Apply process from Oracle source to Teradata target in IDR Problem Description INFA_Problem_DescriptionIn Informatica Data Replication (IDR), when applying changes from Oracle source to Terad