cancel
Showing results for 
Search instead for 
Did you mean: 

Stuck -> Error ABAP Import ora to maxdb

Former Member
0 Kudos

Dear Experts,

I'm trying to migrate the Oracle 11G to MaxDB 7.9, I'm stuck on ABAP Import Phase and near to end.

I got 2 failed packages.

Here are the error:


(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

  rc = 26, table "E071K"

(DB) ERROR: DDL statement failed

(DROP INDEX "E071K~ULI" ON "E071K")

DbSlExecute: rc = 103

  (SQL error -4011)

  error message returned by DbSl:

POS(13) Unknown index name:E071K~ULI

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

(DB) INFO: E071K~ULI created#20151109195151


DbSl Trace: EXECUTE on connection 0, rc=-1452 (POS(1) Duplicate secondary key)

(DB) ERROR: DDL statement failed

(CREATE UNIQUE  INDEX "ZMIMT_DRP_STO~Z01" ON "ZMIMT_DRP_STO" ( "MANDT" , "MATNR" , "STO_MONTH" , "STO_YEAR"  ) )

DbSlExecute: rc = 99

  (SQL error -1452)

  error message returned by DbSl:

POS(1) Duplicate secondary key

(DB) INFO: Savepoint on database executed#20151109222321

Kindly aid me how to solve this issue. Really appreciate for your response.

Thank You

Edy

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Edy,

1. Error message -> -4011 Unkown index name
This error tells you that the index which should be dropped does not exist on the database level.
You can check with MaxDb System table indexes if this index really does not exist on database level -> select * from domain.indexes where indexname = 'E071K~ULI'

If this index does not exist on database level this error message can be ignored.

2. Error message -1452 duplicate secondary key
This error message sounds like there is already an index created on the table ZMIMT_DRP_STO to check this use the folowing commands

select * from domain.indexes where tablename = 'ZMIMT_DRP_STO'  check the output if the index
ZMIMT_DRP_STO~Z01 already exist.
If the index already exists everything looks fine. and as well this error message can be ignored.

The reason why such error can happen can be if you stop and restart the import, then it can happen the actions logged in the table INDEXSTATEMENTS are already executed but not deleted from the table. This is an error in the logic of the import but no database error.

Regards, Christiane

Answers (0)