Duplicate keys error

Hello All,
I am trying to create a B2B export to migrate to 11g. I am getting the following error - how to fix it?
Tried the following - but no effect: java oracle.tip.adapter.b2b.data.B2BSchemaUpdate
Thanks.
RosettaNet ...
oracle.xml.parser.v2.XMLParseException: Identity constraint validation error: 'duplicate keys'
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:312)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291)
at oracle.tip.repos.export.Export11g.validate(Export11g.java:2998)
at oracle.tip.repos.export.Export11g.write(Export11g.java:2891)
at oracle.tip.repos.export.Export11g.createDoc(Export11g.java:670)
at oracle.tip.repos.export.Export11g.export(Export11g.java:211)
at oracle.tip.repos.export.Export.main(Export.java:1024)

Hi,
If you want to export 10g metadata to 11g, please refer -
http://blogs.oracle.com/oracleb2bgurus/2009/10/export_the_metadata_from_10g_t.html
Make sure to validate the metadata in 10g before exporting. In your case there is some key duplication problem but from the provided log it is not very clear that where exactly could be the problem. I will sugesst you to validate the entire repository of 10g and delete everything which is not required. After that take the export as mentioned on the above link.
Make sure to be on the latest patch (MLR -13). Let us know if still problem persists.
Regards,
Anuj

Similar Messages

Classic duplicate key error when processing dimensions

I have a dimension attribute that has a list of values below
atlanta
atlanta
Atlanta
Atlanta
Atlanta
ATLANTA
it has caused the duplicate key errors. I've checked the colloation property of AS server and it's set to Latin1_general with case-sensitive UNCHECKED.... I wonder why I still get this type of errors?
thanks
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

You would need to use a case-sensitive collation for these not to be considered duplicates and even then, on closer inspection, I still see duplicates in your data. There are only three distinct case-sensitive values out of the six examples you've
provided: atlanta, Atlanta, and ATLANTA.
Jason

Duplicate key errors table T7KR5CT occured during SHADOW_IMPORT_INC

Hi,
We are getting the following error during EHP4 upgrade :-
Checks after phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC were negative!
Last error code set: Unresolved requests in buffer SRD
Check logfiles 'SHDALLIMP.ELG' and '/EHPI/EHPI/abap/log/SAPehpi.ECO'
A trouble ticket and an archive with all relevant log files have been
generated.
Trouble ticket: "/EHPI/EHPI/abap/log/SAPehpi_troubleticket.log"
Log archive: "/EHPI/EHPI/abap/log/SAPehpi_troubleticket_logs.sar"
01) * Repeat phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to continue at the point it stopped
02) - Initialize phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to restart it from the beginning
03) - Exit this program
Choose action: Repeat phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to continue at the point it stopped
Log file shows the following information :-
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPK-70105INPIBASIS.SRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 import portion 000000 - 000022 not imported because the child processes died for unknown reason
2EETW000 import portion 000023 - 000026 not imported because the child processes died for unknown reason
2EETW000 import portion 000027 - 000185 not imported because the child processes died for unknown reason
2EETW000 import portion 000186 - 000191 not imported because the child processes died for unknown reason
2EETW000 import portion 000192 - 000218 not imported because the child processes died for unknown reason
2EETW000 import portion 000219 - 999999 not imported because the child processes died for unknown reason
1 ETP111 exit code           : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKE60416.SRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 child process 745784 terminated -> setting rc=12 for this import portion
2EETW000 sap_dext called with msgnr "4":
2EETW000 -
db call info -
2EETW000 function:   db_docu
2EETW000 fcode:      CI_WRITE_LINE
2EETW000 len (char): 68
2EETW000 key:        NAHRPAYDEST601                                                EE0012
2EETW000 ok fetches: 0
2EETW000 retcode:    4
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKE60425.SRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
1 ETP111 exit code           : "8"
/EHPI/EHPI/abap/exenew/R3trans finished (0000).
/EHPI/EHPI/abap/exenew/R3trans finished (0000).
/EHPI/EHPI/abap/exenew/R3trans finished (0004).
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
/EHPI/EHPI/abap/exenew/R3trans finished (0000).
/EHPI/EHPI/abap/exenew/R3trans finished (0004).
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
/EHPI/EHPI/abap/exenew/R3trans finished (0008).
ERROR: stopping on error 8 during SHADOW IMPORT
Warning: Parameter INTERRUPT is no longer used.
Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 9).
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 9).
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
stopping on error 8 during SHADOW IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 8
SWARNS: Highest tp internal severe warning was: 0151
tp finished with return code: 151
meaning:
Some warning regarding buffer entries
Process with ID 807096 terminated with status 151
We tried to replace the R3trans with a latest version of R3trans and repeat the SHADOW_IMPORT_INC phase but still the same error is reported.
Can you please help us on this ?
Thanks in adavnce.
Regards,
SS

Hello,
I got the same problem in RPH EHP5 Upgrade Phase SHADOW_IMPORT_INC with table TWUF_CHECK~. After reading some notes (1074030, ...) I decided to restart the phase without any modifications and it worked and I'm happy!
Jörg
./R3trans -v
This is ./R3trans version 6.22 (release 720 - 02.05.11 - 15:56:00).
ALOG702:
SAPK-603DTINEAGLTRAD SID.ALL K 0012 20110901110222 EAGLTRADUSER sidadm       hostname 2011090109242911d001
SAPK-603DTINEAGLTRAD SID.ALL K 0004 20110901114000 EAGLTRADUSER sidadm       hostname 20110901113956128006
SHDALLIMP.ELG:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPK-603DTINEAGLTRAD.DE8
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 1 duplicate key error during insert into table TWUF_EVENT~ occured
2EETW000 sap_dext called with msgnr "16":
2EETW000 -
db call info -
2EETW000 function:   db_setget
2EETW000 fcode:      RT_GET (0)
2EETW000 tabname:    TWUF_CHECK~
2EETW000 len (char): 65
2EETW000 key:        CL_WB2_ANLYTLTRDGVWINVCIDQR   INPUT                         00002
2EETW000 ok fetches: 0
2EETW000 last entry:
2EETW000 retcode:    16
1 ETP111 exit code           : "12"

1 duplicate key error during insert into table

Dear Guru's
While upgrading the SAP_HR patch, I am facing this issue
Current level is SAPKE60455
Trying to apply patch - SAPKE60456
This is seen in the import log
Start import R3TRVDATV_512W_O ...
client 000:   1
client 001:   1
client 070:   1
client 080:   1
client 100:   1
client 320:   1
1 duplicate key error during insert into table T512T occured
End import R3TRVDATV_512W_O (with warnings)
Please help, thank in advance
R3trans is at version 6.19
Regards,
Omkar

Hello,
Issue was resolved after upgrading the R3trans
Regards,
Omkar

Duplicate message and Duplicate key error in Moni and RWB

Hi,
I am getting very frequent issues of Duplicate messages in production system moni and RWB.
Moni error: (IDOC to JMS) Errors are coming in call adapter step:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not insert message 005056aa-730e-1ed4-a6c9-a01ee2b86cb3(INBOUND) into duplicate check table. Reason: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error OpenSQLExceptionCategories: [RECOVERABLE]
RWB error: (File toIdoc) Errors are coming in sender channel.
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id a6d559cf-b00c-11e4-b786-00000daf354a(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: Violation of PRIMARY KEY constraint 'PK__BC_MSG_D__99C1915D3DE9247A'. Cannot insert duplicate key in object 'SAPPGXDB.BC_MSG_DUP_CHECK'. The duplicate key value is (a6d559cf-b00c-11e4-b786-00000daf354a, OUTBOUND). OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION
Moni errors are manually reprocessed and RWB are automatic.
Can you please let me know if there is any solution available for these issues?
Thanks
Navneet.

I'm getting the same issue at my current client:-
Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id e1d4a31b-f0cc-11e4-c7fb-0000029706f7(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00188646) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
I've tried restarting the SOAP channel but this has not resolved the problem.
Just read on another thread that this may be a misleading error message (see last post on the link). It may be an idea to increase the trace level temporarily and look for any other issues that may be the cause.
So far I've not seen any post that describes the error on the SOAP channel - only seeing it for JDBC & File. However it seems to be a common problem across a number of sender channels.

Strange duplicate key error on doing remove/create

Hi,
I am trying to delete a bunch of entities and then re-use the primary keys to
insert a bunch of new ones, all within the same transaction. I am using WL6.1
(EJB2.0), sp1 on NT.
I use the home.ejbRemove (pk) method to remove the beans, and then the appropriate
create method to create the new instances. 98% of the time this seems to work;
I see the delete statements issued to the database and the assocaited create statements.
Every now and then I get the following error:
javax.ejb.DuplicateKeyException: Bean with primary key: 'AssociateActivity Primary
Keycom.Timesheets.domainBean.AssociateActivityPK@962f6d6f
AssocaiteId : 130.00
AssociateActivityId : 204841.00' already exists.
Yet I still see the delete statement for the PK in question issued to the db,
and everything looks the same as it does when the TX succeeds - but in this case
its as if somehow the entity isnt getting deleted from the WL cache in a timely
fashion. I see that the 'delay_updates_until_end_of_tx' could be set to false,
but isnt this a database-related parameter? I have set this up and am re-testing,
but it is hard to produce this error, so I am not comfortable testing a while
and saying its gone. Does anyone know why I might be seeing this error, and shed
some insight as to whether this parameter will fix it for me?
Thanks in advance !
Caroline.

Hi Rob,
thanks for your reply. The beans are CMP. I agree, updating makes more sense -
this is (now) legacy code written by another engineer, and they didnt want to
deal with updates. It doesnt sound as thought this problem should be happening,
though, and that is concerning. I will keep an eye on if - if I see this intermittent
problem again, maybe I wll bite the bullet and change the algorithms to do just
that. Of course, we are in test mode and getting software out is our primary goal
right now. If you have any other suggestions, I would appreciate them.
Thanks,
Caroline.
Rob Woollen <[email protected]> wrote:
WLS doesn't currently delay deletes so it should have removed the entry
from the cache
before you called create.
Are these BMP or CMP beans?
Our of curiousity, why not just update the beans instead of deleting
and re-creating?
-- Rob
Caroline Day wrote:
Hi,
I am trying to delete a bunch of entities and then re-use the primarykeys to
insert a bunch of new ones, all within the same transaction. I am usingWL6.1
(EJB2.0), sp1 on NT.
I use the home.ejbRemove (pk) method to remove the beans, and thenthe appropriate
create method to create the new instances. 98% of the time this seemsto work;
I see the delete statements issued to the database and the assocaitedcreate statements.
Every now and then I get the following error:
javax.ejb.DuplicateKeyException: Bean with primary key: 'AssociateActivityPrimary
Keycom.Timesheets.domainBean.AssociateActivityPK@962f6d6f
AssocaiteId : 130.00
AssociateActivityId : 204841.00' already exists.
Yet I still see the delete statement for the PK in question issuedto the db,
and everything looks the same as it does when the TX succeeds - butin this case
its as if somehow the entity isnt getting deleted from the WL cachein a timely
fashion. I see that the 'delay_updates_until_end_of_tx' could be setto false,
but isnt this a database-related parameter? I have set this up andam re-testing,
but it is hard to produce this error, so I am not comfortable testinga while
and saying its gone. Does anyone know why I might be seeing this error,and shed
some insight as to whether this parameter will fix it for me?
Thanks in advance !
Caroline.

Inbound IDOC processing, error duplicate key

We want to retrieve certain order-idocs in our system, before they are processed, to change AND insert segment data.
Flow we use in our current program
- DOC_STATUS_WRITE_TO_DATABASE
to change the status of the idoc (ok) (status 69)
- EDI_DOCUMENT_OPEN_FOR_EDIT (ok)
- EDI_CHANGE_DATA_SEGMENTS (ok)
- EDI_DOCUMENT_CLOSE_EDIT => not ok
This program gives SAPSQL error
Via debugging, we see that a new idoc number is
called (save as backup idoc ?), but we want the
current IDOC to be processed.
The system wants to insert in EDID4 => dump :
"Use an ABAP/4 Open SQL array insert only if you
are sure that none of the records passed already
exists in the database."
( I prefer to use these standard functions, in stead of just deleting and inserting into "EDID4" )
regards,
answers will be rewarded.
code extract
INCLUDE ZBE01458_TOP.
INITIALIZATION.
V_EDIT_STATUS = '69'.
V_PROCESSED_STATUS = '32'.
start-of-selection.
clear t_edidc. refresh t_edidc.
SELECT * FROM EDIDC into table t_edidc
WHERE DOCNUM in S_docnum
and mestyp in S_mestyp
and idoctp in S_idoctp
and credat in S_credat
and rcvpor in S_rcvpor
and rcvprt in S_rcvprt
and rcvprn in S_rcvprn
and sndpor in S_sndpor
and sndprt in S_sndprt
and sndprn in S_sndprn
and status in S_status.
loop at t_edidc.
move t_edidc-docnum to v_docnum.
refresh v_status.
V_STATUS-docnum = V_DOCNUM.
V_STATUS-status = V_EDIT_STATUS.
clear EDIDS.
select single * from EDIDS where docnum = v_docnum.
if sy-subrc = 0.
MOVE EDIDS-STACOD to V_STATUS-STACOD.
endif .
APPEND V_STATUS.
PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
changing part for DEDIDD "idoc data
PERFORM OPEN_IDOC_FOR_CHANGE.
PERFORM CHANGE_IDOC.
PERFORM CLOSE_IDOC_FOR_CHANGE.
refresh v_status.
V_STATUS-docnum = V_DOCNUM.
V_STATUS-status = V_PROCESSED_STATUS.
APPEND V_STATUS.
PERFORM CHANGE_IDOC_STATUS tables V_STATUS
USING V_DOCNUM.
endloop.
*& Form OPEN_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM OPEN_IDOC_FOR_CHANGE.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
ALREADY_OPEN = 'N'
IMPORTING
IDOC_CONTROL =
TABLES
IDOC_DATA = DEDIDD
EXCEPTIONS
DOCUMENT_FOREIGN_LOCK = 1
DOCUMENT_NOT_EXIST = 2
DOCUMENT_NOT_OPEN = 3
STATUS_IS_UNABLE_FOR_CHANGING = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " OPEN_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC.
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
TABLES
IDOC_CHANGED_DATA_RANGE = DEDIDD
EXCEPTIONS
IDOC_NOT_OPEN = 1
DATA_RECORD_NOT_EXIST = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CHANGE_IDOC
*& Form CLOSE_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM CLOSE_IDOC_FOR_CHANGE.
CLEAR t_EDI_DS40.
t_edi_ds40-docnum = v_docnum.
t_edi_ds40-status = '51'.
t_edi_ds40-repid = sy-repid.
t_edi_ds40-tabnam = 'EDI_DS'.
t_edi_ds40-mandt = sy-mandt.
t_edi_ds40-stamqu = 'SAP'.
t_edi_ds40-stamid = 'B1'.
t_edi_ds40-stamno = '999'.
t_edi_ds40-stapa1 = 'Changes made to idoc ...'.
t_edi_ds40-stapa2 = t_new_kunnr.
t_edi_ds40-logdat = sy-datum.
t_edi_ds40-logtim = sy-uzeit.
APPEND t_edi_ds40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
DO_COMMIT = 'X'
DO_UPDATE = 'X'
WRITE_ALL_STATUS = 'X'
TABLES
STATUS_RECORDS = t_EDI_DS40
EXCEPTIONS
IDOC_NOT_OPEN = 1
DB_ERROR = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CLOSE_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC_STATUS
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
USING P_DOCNUM.
CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
EXPORTING
IDOC_NUMBER = p_docnum
IDOC_OPENED_FLAG = ' '
NO_DEQUEUE_FLAG = 'X'
IMPORTING
IDOC_CONTROL =
TABLES
IDOC_STATUS = P_IDOC_STATUS
EXCEPTIONS
IDOC_FOREIGN_LOCK = 1
IDOC_NOT_FOUND = 2
IDOC_STATUS_RECORDS_EMPTY = 3
IDOC_STATUS_INVALID = 4
DB_ERROR = 5
OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
else.
commit work.
ENDIF.
ENDFORM. " CHANGE_IDOC_STATUS

Urmila,
I tried this sequence : code extract follows...
I got the duplicate key errors again.
what about delete first and then insert again in EDID4 table ?
source code extract:
INCLUDE ZBE01458_TOP.
INITIALIZATION.
V_EDIT_STATUS = '69'.
V_PROCESSED_STATUS = '32'.
V_SAPCODE = 'SAPE0184'.
start-of-selection.
clear t_edidc. refresh t_edidc.
SELECT * FROM EDIDC into table t_edidc
         WHERE DOCNUM in S_docnum
           and mestyp in S_mestyp
           and idoctp in S_idoctp
           and credat in S_credat
           and rcvpor in S_rcvpor
           and rcvprt in S_rcvprt
           and rcvprn in S_rcvprn
           and sndpor in S_sndpor
           and sndprt in S_sndprt
           and sndprn in S_sndprn
           and status in S_status.
loop at t_edidc.
    move t_edidc-docnum to v_docnum.
    move-corresponding T_EDIDC to WA_EDIDC.
    V_STA-docnum      = v_docnum.
    V_STA-status      = '51'.
    V_STA-repid       = sy-repid.
    V_STA-tabnam      = 'EDI_DS'.
    V_STA-mandt       = sy-mandt.
    V_STA-stamqu      = 'SAP'.
    V_STA-stamid      = 'B1'.
    V_STA-stamno      = '999'.
    V_STA-stapa1      = 'Changes made to idoc ...'.
t_edi_ds40-stapa2      = t_new_kunnr.
    V_STA-logdat      = sy-datum.
    V_STA-logtim      = sy-uzeit.
    V_STA-STACOD       = V_SAPCODE.
    PERFORM OPEN_FOR_PROCESS.
    PERFORM SET_IDOC_STATUS USING V_DOCNUM V_STA.
    PERFORM CLOSE_IDOC_FOR_PROCESS.
    PERFORM OPEN_IDOC_FOR_CHANGE.
    PERFORM PROCESS_IDOC_STRUCTURE.
    PERFORM CHANGE_IDOC.
    PERFORM CLOSE_IDOC_FOR_CHANGE.
   refresh v_status.
   V_STATUS-docnum = V_DOCNUM.
   V_STATUS-status = V_EDIT_STATUS.
   V_STATUS-STACOD = V_SAPCODE.
   clear EDIDS.
   select single * from EDIDS where docnum = v_docnum.
   if sy-subrc = 0.
    MOVE EDIDS-STACOD to V_STATUS-STACOD.
   endif .
   APPEND V_STATUS.
   PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
endloop.
*&      Form OPEN_IDOC_FOR_CHANGE
      text
--> p1        text
<-- p2        text
FORM OPEN_IDOC_FOR_CHANGE.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
   EXPORTING
     DOCUMENT_NUMBER                     = V_DOCNUM
ALREADY_OPEN                        = 'N'
IMPORTING
   IDOC_CONTROL                        = WA_EDIDC
   TABLES
     IDOC_DATA                           = DEDIDD
EXCEPTIONS
    DOCUMENT_FOREIGN_LOCK               = 1
    DOCUMENT_NOT_EXIST                  = 2
    DOCUMENT_NOT_OPEN                   = 3
    STATUS_IS_UNABLE_FOR_CHANGING       = 4
    OTHERS                              = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " OPEN_IDOC_FOR_CHANGE
*&      Form CHANGE_IDOC
      text
--> p1        text
<-- p2        text
FORM CHANGE_IDOC.
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
       TABLES
            IDOC_CHANGED_DATA_RANGE = DEDIDD
       EXCEPTIONS
            IDOC_NOT_OPEN           = 1
            DATA_RECORD_NOT_EXIST   = 2
            OTHERS                  = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " CHANGE_IDOC
*&      Form CLOSE_IDOC_FOR_CHANGE
      text
--> p1        text
<-- p2        text
FORM CLOSE_IDOC_FOR_CHANGE.
CLEAR t_EDI_DS40.
t_edi_ds40-docnum      = v_docnum.
t_edi_ds40-status      = '69'.
t_edi_ds40-repid       = sy-repid.
t_edi_ds40-tabnam      = 'EDI_DS'.
t_edi_ds40-mandt       = sy-mandt.
t_edi_ds40-stamqu      = 'SAP'.
t_edi_ds40-stamid      = 'B1'.
t_edi_ds40-stamno      = '999'.
t_edi_ds40-stapa1      = 'Changes made to idoc ...'.
t_edi_ds40-stapa2      = t_new_kunnr.
t_edi_ds40-logdat      = sy-datum.
t_edi_ds40-logtim      = sy-uzeit.
APPEND t_edi_ds40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
       EXPORTING
            DOCUMENT_NUMBER = V_DOCNUM
            DO_COMMIT        = 'X'
            DO_UPDATE        = 'X'
            WRITE_ALL_STATUS = 'X'
       TABLES
            STATUS_RECORDS   = t_EDI_DS40
       EXCEPTIONS
            IDOC_NOT_OPEN    = 1
            DB_ERROR         = 2
            OTHERS           = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " CLOSE_IDOC_FOR_CHANGE
*&      Form CHANGE_IDOC_STATUS
      text
--> p1        text
<-- p2        text
FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
USING P_DOCNUM.
CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
EXPORTING
IDOC_NUMBER                     = p_docnum
        IDOC_OPENED_FLAG                = ' '
        NO_DEQUEUE_FLAG                 = 'X'
      IMPORTING
        IDOC_CONTROL                    =
TABLES
IDOC_STATUS                     = P_IDOC_STATUS
      EXCEPTIONS
        IDOC_FOREIGN_LOCK               = 1
        IDOC_NOT_FOUND                  = 2
        IDOC_STATUS_RECORDS_EMPTY       = 3
        IDOC_STATUS_INVALID             = 4
        DB_ERROR                        = 5
        OTHERS                          = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
else.
    commit work.
ENDIF.
ENDFORM.                    " CHANGE_IDOC_STATUS
*&      Form OPEN_FOR_PROCESS
      text
--> p1        text
<-- p2        text
FORM OPEN_FOR_PROCESS.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_PROCESS'
    EXPORTING
DB_READ_OPTION                 = DB_READ
      DOCUMENT_NUMBER                = V_DOCNUM
ENQUEUE_OPTION                 = SYNCHRONOUS
IMPORTING
   IDOC_CONTROL                   = WA_EDIDC
EXCEPTIONS
DOCUMENT_FOREIGN_LOCK          = 1
DOCUMENT_NOT_EXIST             = 2
DOCUMENT_NUMBER_INVALID        = 3
DOCUMENT_IS_ALREADY_OPEN       = 4
OTHERS                         = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " OPEN_FOR_PROCESS
*&      Form SET_IDOC_STATUS
      text
--> p1        text
<-- p2        text
FORM SET_IDOC_STATUS USING P_DOCNUM P_STA.
CALL FUNCTION 'EDI_DOCUMENT_STATUS_SET'
    EXPORTING
      DOCUMENT_NUMBER               = P_DOCNUM
      IDOC_STATUS                   = P_STA
IMPORTING
   IDOC_CONTROL                  = WA_EDIDC
EXCEPTIONS
DOCUMENT_NUMBER_INVALID       = 1
OTHER_FIELDS_INVALID          = 2
STATUS_INVALID                = 3
OTHERS                        = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " SET_IDOC_STATUS
*&      Form CLOSE_IDOC_FOR_PROCESS
      text
--> p1        text
<-- p2        text
FORM CLOSE_IDOC_FOR_PROCESS.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_PROCESS'
    EXPORTING
      DOCUMENT_NUMBER           = V_DOCNUM
BACKGROUND                = NO_BACKGROUND
NO_DEQUEUE                = ' '
IMPORTING
   IDOC_CONTROL              = WA_EDIDC
EXCEPTIONS
DOCUMENT_NOT_OPEN         = 1
FAILURE_IN_DB_WRITE       = 2
PARAMETER_ERROR           = 3
STATUS_SET_MISSING        = 4
OTHERS                    = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " CLOSE_IDOC_FOR_PROCESS

Db adaptor for insert- SQLException: [SQL0803] Duplicate key value specified

While invoking db adaptor for insert on table 1 selecting values form another table, i am gtting error ; before3 insert i am updating table 2nd using db adaptor
QUERY insert into CRPDTA.F5504579 (SELECT * FROM CRPDTA.F5504571 WHERE PAHDC=#v_updatedRecord_HDC)
Error :
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert_Ledger_F5504579' failed due to: Pure SQL Exception. Pure SQL Execute of insert into CRPDTA.F5504579 (SELECT * FROM CRPDTA.F5504571 WHERE PAHDC=?) failed. Caused by java.sql.SQLException: [SQL0803] Duplicate key value specified.. The Pure SQL option is for border use cases only and provides simple yet minimal functionality. Possibly try the "Perform an operation on a table" option instead. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "--803" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>[SQL0803] Duplicate key value specified.</detail></part><part name="code"><code>-803</code></part></bindingFault></bpelFault>
Please suggest....

Easter1976 wrote:
Hi please can you help me. I think I am having problems with tranactions. I am deleting from a table and then inserting in the same table with the same key that I have just deleted. Simple then - don't do that. It suggests a flaw in the design. Either use a new key or do an update.
Note that you would get a duplicate key error if the table is set up such that it doesn't
actually delete but doesn't something such as creating a log entry with a delete flag set.

PT 8.51 Upgrade - How to find duplicate keys for Portal Registry Structure?

I am upgrading peopletools for two applications (CRM 9.00 and FDM 9.00) from the 8.48.10 to 8.51.11 versions.
For CRM, Task 4-15-9 Completing the Peopletools Conversion ran app engine PTUPGCONVERT ran smoothly.
For FDM, I have the following error messages:
The Navigation Pagelet does not exist. Portal = EMPLOYEE. Object = PT_SC_PGT_MAIN_MENU. Collection = PT_PTPP_PORTAL_ROOT (219,2083)
Message Set Number: 219
Message Number: 2083
Message Reason: The Navigation Pagelet does not exist. Portal = EMPLOYEE. Object = PT_SC_PGT_MAIN_MENU. Collection = PT_PTPP_PORTAL_ROOT (219,2083)
Duplicate key. Portal: EMPLOYEE, Obj Name: PT_SC_PGT_MAIN_MENU, Nodename: LOCAL_NODE, URL: s/WEBLIB_PTPP_SC.HOMEPAGE.FieldFormula.IScript_SCP (133,4)
PT_SC_PGT_MAIN_MENU already exists. (96,3)
Copy of the Main Menu Pagelet From PS_SITETEMPLATE to Portal: EMPLOYEE failed. (219,2111)
Message Set Number: 219
Message Number: 2111
Message Reason: Copy of the Main Menu Pagelet From PS_SITETEMPLATE to Portal: EMPLOYEE failed. (219,2111)
I checked table PSPRSMDEFN which does not have an entry for PT_SC_PGT_MAIN_MENU, under the Employee Portal. I tried to migrate the missing Portal Registry object using App Designer but again receive the "duplicate key" error.
So it seems that I have to find the duplicate key and resolve it before I can migrate the missing object.
Anyone know a quick way to figure out what the duplicate keys are?
Thanks

I tried several things to find the duplicates with no success.
A couple of workarounds were attempted that resulted in the same "duplicate key" error, including:
a) Re-copying file project PPLTLS84CUR
b) Copy object 'PT_SC_PGT_MAIN_MENU" from Demo
After opening an SR, the successful workaround was to use Data Mover to export from Demo the "EMPLOYEE" portal entries for "PT_SC_PGT_MAIN_MENU" from tables PSPRSMDEFN, PSPRSMSYSATTR and PSPRSMSYSATTRVL. The import to the target upgrade environment was successful. A re-run of PTUPGCONVERT finished successfully.
The upgrade is progressing but where the duplicate keys are is still a mystery.
Cheers

Error in Executing a Interface -- Index Duplicate Keys

Hi All,
I ran my Interface 2 times , it was working fine..... but after that when I ran I got these Error...where I am doing the mistake.............
KM I used :
LKM SQL to ORACLE
IKM ORACLE INCREEMENTAL UPDATE
CKM ORACLE
The Step I am getting this Error is : Create Unique Index on Flow Table
1452 : 72000 : java.sql.SQLException: ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
java.sql.SQLException: ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
     at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1086)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3057)
     at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.g.y(g.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)
Thanks
AK
Message was edited by:
Ananda

Hi Anand-
This is completely data issue, when executing the unique index step it will create unique index with the column name you mentioned.
When you ran the first two loads there was no duplicate keys found in the data that's why you didn't get the error but the third run you got the problem.
Check your data records and made changes in the KM as Bouch told if you don't want to create unique index.
Thanks & Regards,
Saravanan Rajavel

Country-State-City hierarchy is driving me crazy ( duplicate attribute key errors)

hi guys:
I've a dimDesitination dimension and inside this dim , I have 4 attributes, dimDest_ID, country, state and city,
my goal is pretty simple, create a hierarchy country-state-city .
I've made sure there are no NULLs in each column, also state and city attribute, I've created composite key
for example, for state attribute , the key column is (country , state)
for city attribute, the key column is (country, state , city)
when the source dim table contains small number of data, every is fine and process full did succeed.
However, when the raw dim table gets bigger( more data comes in), the process full starts to give me error msg
says duplicate attribute key errors.... this is painful as I did check the raw table but no duplicate key found ever
any comments?
thanks
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Hi Cat_ca,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Charlie Liao
TechNet Community Support

French character is causing duplicate attribute key errors, why and how to overcome?

hi there:
I have a retailerproductname called 'Meilleurs vœux' , this character 'œ' is causing headache as it's causing the classic duplicate attribute key errors. When I replaced it with 'e', error goes away...
The thing is that I do not want to correct datawarehouse everyday for this type of work... plus there might be other non-english characters that may pop up depends on what consumers bought.
Is there anyway other than manual intervention?
thanks
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

yes, try use nvarchar instead of varchar.
Using varchar Spree-Neiße <> Spree-Neisse. Using nvarchar Spree-Neiße = Spree-Neisse.
And one more specifying quiestion about your data source. Imagine you have two retailproductname, such as
Spree-Neiße and Spree-Neisse. In your case is it the same product and you should leave only one record?

Sybase Error 2601 Attempt to insert duplicate key row in object with unique

RE: Sybase Error 2601 Attempt to insert duplicate key row in object with unique index.
Hi Folks,
I'm getting the following error whilst executing a stored procedure in Sybase.
ERROR: Sybase Error 2601 Attempt to insert duplicate key row in object with unique index.
I understand that duplicate values have been inserted into a column that has a unique constraint.
I just can't figure out how to rectify the problem.
Your help will be greatly appreciated!
Many thanks in advance.

If the value I'm trying to insert (using update)
already exists in the unique-value field then the DB
refuses to update the field.
If the value is different it will update.Are you trying to insert or update in SQL (identified by the keyword INSERT or UPDATE respectively)?
Even in case of an UPDATE query, if you are going to update the values of some columns to violate the unique constraints, the update will not succeed and you will get the error message.
or is it?
it tries to create a new row, but can't because there
is another row with the same unique-values.
If this is the case, I am only trying to update and
not create a new item.To put it in simpler words, if you have a set of values defining the uniqueness of a record, you cannot insert another record with the same set of unique values. Similarly, you cannot update an existing record by modifying the set to conflict with another set of unique values which already exist in the database.
Suppose there are two columns A and B defining the uniqueness of the record and you have only two records at the moment like -
A B
========
1 1
2 1
If you try to insert a record with A = 1 and B = 1, it will fail because a record already exists. You cannot violate uniqueness because the database has already been told that there will be only one record for any given combination of A and B.
Similarly, if you try to update the second record from A = 2 to A = 1, the end result would be A =1 and B = 1. There is already a record with that set of values and this will result in a violation of the uniqueness. So, this update will also be disallowed. On the other hand, if you try to update B to some value, say 3, there is no problem in doing so.
For convenience, you can imagine an UPDATE operation to be equivalent to DELETE + INSERT operation, though it doesn't necessarily work the same way internally.
I hope I was clear enough.

ERROR ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

Hi,
SAPSSRC.log
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195059
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -ctf I C:/temp/51030721/EXP2/DATA/SAPSSRC.STR C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/DDLORA.TPL C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.TSK ORA -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job completed
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195059
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195133
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.cmd -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: ABTREE created #20071018195134
(IMP) INFO: import of ABTREE completed (39 rows) #20071018195134
(DB) INFO: ABTREE~0 created #20071018195134
(DB) INFO: AKB_CHKCONF created #20071018195134
(IMP) INFO: import of AKB_CHKCONF completed (0 rows) #20071018195134
(DB) INFO: AKB_CHKCONF~0 created #20071018195134
(DB) INFO: AKB_INDX created #20071018195134
(IMP) INFO: import of AKB_INDX completed (0 rows) #20071018195134
(DB) INFO: AKB_INDX~0 created #20071018195134
(DB) INFO: AKB_USAGE_INFO created #20071018195134
(IMP) INFO: import of AKB_USAGE_INFO completed (0 rows) #20071018195134
(DB) INFO: AKB_USAGE_INFO~0 created #20071018195134
(DB) INFO: AKB_USAGE_INFO2 created #20071018195134
(IMP) INFO: import of AKB_USAGE_INFO2 completed (0 rows) #20071018195134
(DB) INFO: AKB_USAGE_INFO2~0 created #20071018195134
(DB) INFO: APTREE created #20071018195134
(IMP) INFO: import of APTREE completed (388 rows) #20071018195134
(DB) INFO: APTREE~0 created #20071018195134
(DB) INFO: APTREE~001 created #20071018195134
(DB) INFO: APTREET created #20071018195134
(IMP) INFO: import of APTREET completed (272 rows) #20071018195134
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-1452 occurred when executing SQL statement (parse error offset=35)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "APTREET~0" ON "APTREET" ( "SPRAS", "ID", "NAME" ) TABLESPACE PSAPBW1 STORAGE (INITIAL 44981 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1452)
error message returned by DbSl:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
(DB) INFO: disconnected from DB
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195134
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195314
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.cmd -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) ERROR: DDL statement failed
(DROP INDEX "APTREET~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-1452 occurred when executing SQL statement (parse error offset=35)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "APTREET~0" ON "APTREET" ( "SPRAS", "ID", "NAME" ) TABLESPACE PSAPBW1 STORAGE (INITIAL 44981 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1452)
error message returned by DbSl:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
(DB) INFO: disconnected from DB
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195315
I'm getting this error "duplicate keys found". I'm finished installing the central instance and during the database instance, i got this error. I'm installing BW 3.5 on x64 windows server 2003 platform. I'm using NU kernel 6.40.
Thanks for your suggestions on how to resolve this error.
Reward points guaranteed.

Issue solved by deleting central and database instance and started a new build. it finished without an error.
Thank you.

Impdp - duplicate keys found error

I'm facing a strange issue. I'm running expdp / impdp using datapump. The export of the schema is successful. The import of the schema is raising the below errors for few PKs. I have verified on the source database. There are no duplicate records found and the PK is in enabled state. What is causing for this issue?. I had the similar issue earlier and run the Point-In Time export using FLASHBACK_SCN parameter and the import run smooth. But, the issue this time is the applications are shutdown and there are no connections from the application side and no DML transactions running on the schema. So, I have run the export without FLASHBACK_SCN parameter as we are moving this production database to another. But, the import is raising the below errors. Could someone let me know why it's causing?.
ORA-39083: Object type INDEX failed to create with error:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
ORA-39083: Object type CONSTRAINT failed to create with error:
ORA-02437: cannot validate (schema.tab_PK) - primary key violated

Hi,
Can you run the impdp commnd with this:
sqlfile=index.sql include=INDEX
then look in index.sql to find the index that is failing and try crating it manually. The other thing is to do a query on the target table to see if there are
duplicate keys on the target. I can't explain why, but I can't imagine why the create index would fail if there were not.
If you have a network link between the 2 databases maybe you can do a
select * from target minus select * from source@network_link
to see if there is anything different.
Dean
Edited by: Dean Gagne on Feb 17, 2010 7:37 AM

Duplicate keys error

Similar Messages

Maybe you are looking for