on 05-10-2010 11:44 PM
Hi
The production system has been experiencing short dumps in a custom program since 700 Unicode kernel level 252 was applied and IBM PTFs from the Info Apar of 30/3/10 for V5R4M5. The DLTR3PKG was run afterwards.
The WP joblogs show these messages - Row or object NRIV in R3PRDDATA type *FILE in use.
Record 7703 in use by job 274397/PRD00/WP28.
Record 7703 in use by job 274397/PRD00/WP28.
Row or object NRIV in R3PRDDATA type *FILE in use.
ST22 short dumps have this information -
>>>>>>>>>>>>>>>>>>>>>>>>>
Termination occurred in the ABAP program "SAPLSNR3" - in "READ_NRIV".
The main program was "RBDAPP01 ".
In the source code you have the termination point in line 245
of the (Include) program "LSNR3F01".
The program "SAPLSNR3" was started as a background job.
Job Name....... "Z_AUTOBILL"
Job Initiator.. "BATCHADM"
Job Number..... 07401703
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "READ_NRIV" "(FORM)", but it was neither handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLSNR3 "; its source code begins in line
240 of the (Include program "LSNR3F01 ".
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
240 FORM READ_NRIV USING P_OBJECT P_SUBOBJECT P_NR_RANGE_NR P_TOYEAR
241 P_QUANTITY P_RETURNCODE P_NUMBER.
242
243 IF TNRO-YEARIND = NO.
244 * Nummernkreise sind jahresunabhängig
>>>> SELECT SINGLE FOR UPDATE * FROM NRIV WHERE
246 OBJECT = P_OBJECT
247 AND SUBOBJECT = P_SUBOBJECT
248 AND NRRANGENR = P_NR_RANGE_NR
249 AND TOYEAR = '0000'.
250 IF SY-SUBRC NE 0.
251 MESSAGE E751 RAISING INTERVAL_NOT_FOUND WITH P_OBJECT P_SUBOBJECT
252 P_NR_RANGE_NR TNRO-CODE.
253 ENDIF.
254 ELSE.
255 * Nummernkreise sind jahresabhängig
256 G_FOUND = NO.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Any ideas ?
To fix another program issue from before the new kernel only one instance parameter was changed -
dbs/db4/max_hostvars from 2000 to 3000
as these errors were logged in the WP were logged when the program cancelled with a DBIF_RSQL_INVALID_RSQL dump-
B Sat Apr 24 09:34:59 2010
B *** ERROR => dbtran ERROR (set_input_da_spec): statement too big
marker count = 2412 > max. marker count = 2000
This program now completes successfully but the first problem with NRIV is causing more serious problems.
Thanks
Michael
Edited by: Michael Power on May 11, 2010 8:52 AM -
The short dumps related to NRIV are all -
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
-
-
-
-
Short text |
SQL error in the database when accessing a table. |
Termination occurred in the ABAP program "SAPLSNR3" - in "READ_NRIV". |
| The main program was "SAPMV60A ".
Hi Michael,
nice to hear from you ))
This seems to be a duplicate to the newer - but easier readable - one from Chris.
Therefore, the same answer:
unfortunately, this is "normal" and a typical application issue.
NRIV is "THE" number buffering table. If you do have locks there, you have to investigate the currently running and failing applications. One of them will not work properly with the number rage table.
Perhaps, it might be an option, to buffer the table for the "row in problem" - but this needs to be discussed with the application people, because sometimes, this is forbidden.
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.