on 11-23-2004 2:19 PM
Hi all,
When executing multiple parallel jobs (same program) it happens often that the internal key assignment of table BALDAT (application log) is called by two jobs at the same time. The result is that one job short dumps with error SAPSQL_ARRAY_INSERT_DUPREC BALDAT. That is, a record with the same key has already been saved with the other job.
One way to resolve the problem would be to assign a different number range of the internal key (trans SLGN) to each job. But how to make the job understand this?
The application is IS-U BAPI_MTRREADDOC_UPLOAD but as I've understood it, this could happen to any parallel processing.
Has anyone experienced this?
Thankful for any ideas
I had a (selfcreated) aplication log while transferring the data from sd- into copa (user-exit valuation) and experienced the same problem. (I wanted to have only one log for each day and the first poster ran into that problem (while creating the log). If I remember right, I found an oss note indicating that BAL Log has some weak points when it comes to parallel posting. I think, I could have solved it by using another handle for each call but decided to switch it off.
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.