Runtime Errors DBSQL_DUPLICATE_KEY_ERROR

[former_member547765]

Hi,

I have problem after running client copy from production client 100 to development client 310.

user said they have error when input data using tcode MIGO.

here is the dump from ST22

how to fix the error?

what should i do in my next client copy process so that there are no more errors like this?

Regards

[jmodaal]

Hello,

my first suspicion is that the activities in the source client were not stopped for the runtime of the client copy. As a result you might be faced with inconcistencies in the number ranges (number free according to the number range interval in table NRIV, but still occupied in a document, because the table with the document was copied later than the NRIV table). Therefore, all tasks should be stopped during a client copy.

If my assumption is right, then try to fix it by increasing the number range interval in SNRO / SNUM to a value above the highest existing document. The short dumps should give you information about the table.

[timo_bauer2]

Hello Irfan,

you should check the document table for MIGO (MKPF?) and there sort for the highest document number. Then, as proposed by Jan, increase the Document Number in the number range interval table to the highest doc number + 1. By this the error should not occur anymore. The error is raised as you have already a document in the table that should be used and this leads the system to throw a short dump.

Regards

Timo

[former_member547765]

Hi jmodaal

"all task should be stopped during a client copy" you mean the background job ?

Regards

[jmodaal]

Hello irfan.only

> "all task should be stopped during a client copy" you mean the background job ?

I mean all tasks in the system: jobs, dialog tasks, RFC, ... everything. Use programs BTCTRNS1 to suspend all jobs (release again after the client copy with BTCTRNS2), lock (nearly) all users and then perform the client copy.

Did you check whether the problem is in the number ranges? This issue is also mentioned in SAP note 552711 (FAQ client copy), topic number 19.

[Sasi2005]

Hi,

I don't see the whole of the dump. However based on whatever i am seeing, the issue is during the saving of the material document and has some conflict with a controlling object "COBK"... Please investigate along these lines with the support of a ABAP technical consultant. This should solve the issue.

Regards

Sasi

[former_member547765]

Hi eeee36c5ca424a59973fd7fa9ff786e2

Yes the issue is during saving the document

thanks for the reply

Regards

[former_member698447]

Hi Irfan,

Kindly check once below SAP Note, There might be chances of inconsistency could be have been happened.

https://launchpad.support.sap.com/#/notes/2840883

Best Regards,

Repakula Manoj

[former_member547765]

Hi jmodaal

I need help with this step for checking table NIRV and SNRO/SNUM

any field I should filled for this?

Regards

[jmodaal]

Hello,

for finding the highest given document number you can either use SE16. Faster possibility - if you have access to DBACOCKPIT or ST04 and can use the SQL command editor - is to get the number by an SQL statement. Example (assumed that it's about table COEP in client 100):

select max(BELNR) from "COEP" where MANDT = '100'

The field containing the document number is one of the primary key fields of the table, typically a CHAR feld of length 10 to 20.

Unfortunately I do not know how/where to find a reliable relation between the number range object and the table. Transaction OBA7 might give some help, but maybe you have to ask someone from the application side for the right number range object.

Then use transaction SNRO or SNUM (Edit Intervals) to adjust the "NR status" (highest given number).