WARNING: -l exceeded. Automatically increasing from 1010 to 1020

Yahoo Archive
1
https://epicweb.epicor.com/doc/Docs/PerformanceTuningGuideSQL_803405.pdf

I used to see this in my server.log file but haven't in a long time
(maybe since I applied the performance tuning recommendations?). I
believe the -l setting refers to Progress spin locks:

Spin locks define the number of times a process tries to acquire a
launch before it pauses. If the process
cannot acquire the resource latch, it resets and attempts to acquire it
again. This iterative process is
called spinning.

I see these regularly still:

[10/11/29@12:53:39.380-0500] P-008496 T-011956 1 AS -- (Procedure:
'matchList lib/sqlConverter.p' Line:7234) WARNING: -nb exceeded.
Automatically increasing from 122 to 154. (5407)
[10/11/29@12:53:39.396-0500] P-008496 T-011956 1 AS -- (Procedure:
'EvalFactor lib/sqlConverter.p' Line:6335) WARNING: -nb exceeded.
Automatically increasing from 154 to 186. (5407)
[10/11/29@12:53:45.193-0500] P-008736 T-008732 1 AS -- (Procedure:
'IsSqlKeyword manager/Data.p' Line:1836) WARNING: -nb exceeded.
Automatically increasing from 90 to 122. (5407)

Not sure what -nb refers to.

-bws

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Hatcher, John
Sent: Tuesday, November 30, 2010 11:08 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: WARNING: -l exceeded. Automatically increasing
from 1010 to 1020

My understanding is that the only downside is a possible performance hit
while the parameter is adjusted. It does correlate to a specific
setting in either the database or the app server. I don't remember what
it represents. The performance tuning manual has it in it. I've seen
mine increase all the way up to 5000+ without a problem in the past (and
before we took steps to prevent by tuning)



If you don't change the setting in your tuning, it will default back to
the lower number you have set the next time you do a restart. It will
then have to increment by 10 until it gets back to where it needs to be.



Hope this helps.



John



[Non-text portions of this message have been removed]



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
2
My understanding is that the only downside is a possible performance hit
while the parameter is adjusted. It does correlate to a specific
setting in either the database or the app server. I don't remember what
it represents. The performance tuning manual has it in it. I've seen
mine increase all the way up to 5000+ without a problem in the past (and
before we took steps to prevent by tuning)



If you don't change the setting in your tuning, it will default back to
the lower number you have set the next time you do a restart. It will
then have to increment by 10 until it gets back to where it needs to be.



Hope this helps.



John



[Non-text portions of this message have been removed]