MDMP unicode conversion:"ORA-01452" Error during database import

[Former Member]

Hello,

We have done Upgrade of 4.5B MDMP system to ECC6 EHP4 MDMP and currently Unicode conversion in progress. Database export completed successfullu and now we are importing unicode system. We are facing issue during Import Abap phase

"ORA-12801: error signaled in parallel query server P000

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

for COEP. Please find attached log file.

*Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

DbSl Trace: Error 12801 in exec_immediate() from oci_execute_stmt(), orpc=0

DbSl Trace: ORA-12801 occurred when executing SQL stmt (parse error offset=0)

(DB) ERROR: DDL statement failed

(CREATE UNIQUE INDEX "COEP~0" ON "COEP" ( "MANDT", "KOKRS", "BELNR", "BUZEI" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 1782579200 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS PARALLEL 4 )

DbSlExecute: rc = 99

(SQL error 12801)

error message returned by DbSl:

ORA-12801: error signaled in parallel query server P000

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

(DB) INFO: disconnected from DB

/usr/sap/PV1/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/PV1/SYS/exe/run/R3load: END OF LOG: 20100823121710P

kindly suggest

Regards

Vinay

[sunny_pahuja2]

Hi,

Check SAP Note 11369 - ORA-1452 during import after export from other system

Thanks

Sunny

[Former Member]

Hi Sunny,

Thanks for your response.

I referred to that note Note 11369 - ORA-1452 during import after export from other system.

in that note Reason and prereq: This may result from rollback problems with ORACLE 7.0.13 in connection with cluster tables containing long raw fields.

My cuurent oracle version is oracle 10.2.0.4. It will be applicable for my version ?. Kindly suggest

Regards

Vinay

[nils_buerckel]

Hi Vinay,

the reason for your duplicate key error might be a different one in your case.

However in any case you need to find out which entries cause this error - and here SAP note 11369 might be helpful.

Best regards,

Nils Buerckel

SAP AG