cancel
Showing results for 
Search instead for 
Did you mean: 

SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key

Former Member
0 Kudos
436

Hi All,

System copy export completed but while importing into the Target system getting below error.

Error:

(SQL error 3701)

  error message returned by DbSl:

[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index '/BI0/F0SMD_PED1./BI0/F0SMD_PED1~0', because it doesn't exist in the system catalogs.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: DDL statement failed

(CREATE UNIQUE  INDEX "/BI0/F0SMD_PED1~0" ON "/BI0/F0SMD_PED1" ( "KEY_0SMD_PED1P", "KEY_0SMD_PED1T", "KEY_0SMD_PED1U", "KEY_0SMD_PED11", "KEY_0SMD_PED12", "KEY_0SMD_PED13", "KEY_0SMD_PED14", "KEY_0SMD_PED15", "KEY_0SMD_PED16", "KEY_0SMD_PED17", "KEY_0SMD_PED18", "KEY_0SMD_PED19" ) with sorted_data )

DbSlExecute: rc = 99

  (SQL error 1505)

  error message returned by DbSl:

[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key.  Primary key is '18, 160, 0, 66, 31, 67, 4, 17, 175, 3, 2, 2'

Import Monitor jobs: running 1, waiting 1, completed 42, failed 0, total 44.

Loading of 'SAPDFACT_2' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 42, failed 1, total 44.

Please advice.

Regards,

Karthik

Accepted Solutions (0)

Answers (1)

Answers (1)

victoria_normand
Contributor
0 Kudos

Hello Karthik,

For this error it might be possible that the problem already comes from the source with this particular index. Is this an heterogeneous system copy or homorgeneous ?

Suggestions to check on the source system:

- from RSA1 for the Infocube 0SMD_PED1 -> Manage option -> Performance tab -> Check Indices. If red traffic light is returned then click on "Repair Indices" button.

or

- run ABAP report SAP_INFOCUBE_INDEXES_REPAIR, it will check ALL Infocubes to identify missing or required to repair primary and secondary indexes.

Besides that:

- ensure to have the last PL of R3load
- ensure to have on the source system the last ASE/BW Correction Collection implemented (this is valid for both: BW and Solman environments)

Then re-run the export again to ensure correct SQL commands are generated.

Best regards,
Victoria.

Former Member
0 Kudos

Hi Victoria,

I have followed the same and ran ABAP report SAP_INFOCUBE_INDEXES_REPAIR, it will check ALL Infocubes and is GREEN.

I have also updated latest kernel , tp,retrans and dbsl But still getting below error:

(SYB_IMP) ERROR: DbSlEndModify failed

  rc = 99, table "/BI0/F0SMD_PEH1"

  (SQL error 3621)

  error message returned by DbSl:

[ASE Error SQL4851][SAP][ASE ODBC Driver][Adaptive Server Enterprise]BULK COPY IN failed. One or more rows do not belong to any partition of table '/BI0/F0SMD_PEH1'.

[ASE Error SQL4851][SAP][ASE ODBC Driver][Adaptive Server Enterprise]BULK COPY IN failed. One or more rows do not belong to any partition of table '/BI0/F0SMD_PEH1'.

[ASE Error SQL3621][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Command has been aborted.

(IMP) ERROR: EndFastload: rc = 2

(DB) INFO: /BI0/F0SMD_PEH1~0 not dropped (corresponding CREATE is only a dummy)

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~0" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~01" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~01" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~02" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~02" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~04" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~04" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~05" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~05" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~06" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~06" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~07" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~07" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~08" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~08" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~09" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~09" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~10" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~10" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~11" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~11" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~12" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~12" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~13" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~13" is not created.

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~P" is not created.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: failed to load table "/BI0/F0SMD_PEH1", index "/BI0/F0SMD_PEH1~P" is not created.

(DB) INFO: disconnected from DB

/usr/sap/SND/SYS/exe/run/R3load: job finished with 30 error(s)

/usr/sap/SND/SYS/exe/run/R3load: END OF LOG: 20160601212018

Please advice.

Regards,

Karthik

victoria_normand
Contributor
0 Kudos

Hi Karthik,
This isssue is another one and it usually happens because new data has been inserted on the source F table, which will mean new partitions that are not existing on the target F table as the SMIGR_CREATE_DDL was run before those new partitions were added. Basically the DDL used to create the tables on target is out of date.
You'll  have to re-run the SMIGR_CREATE_DDL report on the source system (restart the export from scratch).

There is an SAP KBA for this (it talks about migration but that involves system copy anyway): 2125141 - BW on ASE: Error SQL4851 returned during import of F table


Regards,

Victoria.