All Forums Tools
chinna 7 posts Joined 10/09
19 Nov 2009
any one plz give me brief explain about this error

iam trying to load data in set and multiset tables with mload ( i tried both ways)i am getting the following error..**** 00:35:00 UTY0805 RDBMS failure, 2801: Duplicate unique prime key error in databasename_tablename_Log.

19 Nov 2009

Hi,What you should look at is that you have probably set the Table with a UPI. No matter whether it is SET or MULTISET, if a UPI is set on the table, it will not accept duplicate values for the keys defined in the Primary Index if it is assigned as UNIQUE. Follow one of the 2 approaches:1. Remove UPI and make it PI and load the data. It should load fine2. Find th duplicate data row and eliminate it and then load. That way the remaining data will load.Use appropriate method as this may affect the data you are loading.

chinna 7 posts Joined 10/09
20 Nov 2009

Hi,thank you for the reply..but i tried PI with set table and PI with multiset table also, i am getting the same error,and second solution I have 2 millions of records in my source file(txt), plz let me know if there is an easy way to find the duplicate records.

20 Nov 2009

Hi,I am not sure if this issue is with the data or the logging. Can you please drop all UV, ET, LG and WT tables, release mload on the table and start the job again and try. Let me know what happens. If it still fails, please look at the Log file and paste the exact error message you see with Failure code and we can trace this back to its source.

chinna 7 posts Joined 10/09
20 Nov 2009

Hi,thank you for immediate replyi dropped UV,ET,WT,LOG and table also and i recreate the table againgnow iam trying to load only one record also getting the same error msg

Jimm 298 posts Joined 09/07
20 Nov 2009

If you have duplicates in the input file, they will go to the error table - not give a duplicate table violation.Table databasename_tablename_Log. Is this the LG table for mload, or is this a table you use to record mload progress?Send the mload output if you still have a problem.

pawan0608 101 posts Joined 12/07
24 Nov 2009

This is very strange, wouldlike to see the mload script. Please paste here.

maddy@1 6 posts Joined 05/08
24 Nov 2009

Can you post the actual error message you are getting...

chinna 7 posts Joined 10/09
25 Nov 2009

this the error msg **** 00:35:00 UTY0805 RDBMS failure, 2801: Duplicate unique prime key error in database.table_Log. ======================================================================== = = = Logoff/Disconnect = = = ========================================================================**** 00:35:02 UTY6212 A successful disconnect was made from the RDBMS.**** 00:35:02 UTY2410 Total processor time used = '0.3125 Seconds' . Start : 00:34:35 - THU NOV 19, 2009 . End : 00:35:02 - THU NOV 19, 2009 . Highest return code encountered = '12'.

pawan0608 101 posts Joined 12/07
26 Nov 2009

Please also paste mload script and show table output of target table

feinholz 1234 posts Joined 05/08
03 Dec 2009

The error you are seeing is from MultiLoad trying to access or update the restart log table.This has nothing to do with the target, work, or error tables.Are you fully qualifying all of your table names in the script?Are you using double-quotes to specify table names in the script?Please post the entire script to this forum (actually, it would be better if you moved these posts to the Developer Exchange because that is the forum we want to use going forward).I have seen this error before when part of the script use fully qualified table names and other places do not, and some places using double-quotes and some places not.I need to see the full script in order to diagnose.

--SteveF

mehaboob 10 posts Joined 12/09
03 Dec 2009

i believe that your table definition has secondary index. If that is the case then drop the table re create with out the secondary index and use mload to load the data and then add the secondary index to it.If there are duplicate values then use the following the the mload script.DML LABEL MYLABELMARK DUPLICATE INSERT ROWSthen all the rows will be loaded to UV table

feinholz 1234 posts Joined 05/08
03 Dec 2009

The table named in the error message was:Duplicate unique prime key error in database.table_Log.The "_Log" is usually the naming convention people use to specify the restart log table.I do not think this has to do with target table.The entire job output would be able to show us this.It would be helpful to know where in the job this error took place.

--SteveF

You must sign in to leave a comment.