topic ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while relesing a Transport Request in Application Development and Automation Discussions

ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while relesing a Transport Request

Former Member — Wed, 06 Feb 2008 04:45:42 GMT

Hi,

While releasing a Transport request it takes nearly 1100 seconds and then throwing a dump SAPSQL_ARRAY_INSERT_DUPREC.

As per the dump the program (SAPLSTRD) tries to insert a duplicate record into the table E071.......

Please advise.....

Thanks,

jose.

Re: ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while relesing a Transport Request

Former Member — Wed, 06 Feb 2008 04:52:52 GMT

Hi Will

please check note number 847892.

Cheers

shivika

Re: ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while relesing a Transport Request

Former Member — Sat, 09 Feb 2008 10:47:00 GMT

Hi Jose,

Every transport request maintains its piece list in table E071.When object is appended, a new entry with counter = max (existing Counter nummber) + 1 is added to E071.

If to be inserted count nummber is already available in E071, "duplicate key insert" error occurs. This happens when Database runs in "commited read" mode. This is the case when R3 runs on oracle database. New counter inserted by the first user remain invisible for other users before "commit" command is triggered. The solution is given in note '1041098.

But as you have mentioned its taking about 1100 sec to release the transport, then try to reduce the size of the transport request by including lesser number of objects or objects of less size as every transport request creates a physical file in the backend and a large file will take a lond time to process.

Thanks and Regards,

Amit.

Re: ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while relesing a Transport Request

RaymondGiuseppi — Sat, 09 Feb 2008 12:19:02 GMT

Try to sort and compress your task/request before releasing it. if problem persists, perform an overall check or reduce the size of the transport.

Regards