TSV_UNIQUE_NUMBER_OVERFLOW dump

[minchevm]

Hello,

I have the following problem: I have an application that makes intensive reads and writes from various different places into one Shared memory object. The application is not changed for more than 1 month but after 2 weeks of exploitation it is seems a degradation appeared and I have started receiving TSV_UNIQUE_NUMBER_OVERFLOW short-dump every now and then. Any idea what might be causing such a problem? Can somebody help me identify the root cause of the problem as this is fully customer program?

Best regards!

[minchevm]

Hello,

I have the following problem: I have an application that makes intensive reads and writes from various different places into one Shared memory object. The application is not changed for more than 1 month but after 2 weeks of exploitation it is seems a degradation appeared and I have started receiving TSV_UNIQUE_NUMBER_OVERFLOW short-dump every now and then. Any idea what might be causing such a problem? Can somebody help me identify the root cause of the problem as this is fully customer program?

Best regards!

[former_member636927]

please check with the developer, looks like its overflow of number range during processing the same object simultaneously for some internal number assignment.

If you process the object one by one, it will solve your problem.

Regards

Prashant

[FredericGirod]

looks like to be the number of internal tables used at the same moment

[FredericGirod]

1540034 - Short dump TSV_UNIQUE_NUMBER_OVERFLOW

[minchevm]

The description of the short-dump is really "The table body does not have a unique ID any more". I have captured a place in my custom code in which I might be accessing the Object simultaneously from 2 places.

I have corrected that but I won't be sure if my correction works for sometimes.

Thanks all for now!

[Sandra_Rossi]

Could you attach one short dump please?

[Sandra_Rossi]

1540034 - Short dump TSV_UNIQUE_NUMBER_OVERFLOW

[minchevm]

I will test also if we change the system parameter given in OSS 1540034. I hope I will not forget to update this thread in a couple of weeks.

[Sandra_Rossi]

Please use the COMMENT button for comments, questions, adding details, etc., ANSWER is only to propose a solution, dixit SAP text at the right of the answer area.

[S_Sriram]

Hi Mimchil.

First enable the ST12 trace for this dumps, check trace over all read & commit operations in the transactions with help of developers, and then take the necessary action either increasing the buffer values as mention the note or fine tune the transaction based on the trace.

Regards

SS