cancel
Showing results for 
Search instead for 
Did you mean: 

direct read causing locks in Table - NRIV

Former Member
0 Kudos

Hi Guys, since the kernel upgrade the system has been having a huge number of dumps & the performance has gone down drastically. did some checking on SM50 & DB01, i can see so many locks on the NRIV table.

Has anyone come across this issue before ?

Thanks in advance

Chris

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..... 15174905

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 ".

>>>>> 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'.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Solved by SAP OSS

KayKa
Active Participant
0 Kudos

Hi Christopher,

do you have some more details of this solution for us ?

best regards

Kay

Former Member
0 Kudos

First thing.. SAP asked us to reduce the frequency of the job that was causing the dumps... from 1 min... to every 7mins....

Check note 1453114

restart this morning with the active parameter dbs/db4/connect_type = L has solved the poor database response time that was contributing to system slowness.

The Machine Pool has been increased

Former Member
0 Kudos

Hi Chris,

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