System error -s exceeded

[krellan2]

The error I am getting is as follows:

USR SYSTEM Error -s exceeded. Raising STOP condition and attempting to write stack trace file 'procore'. Consider increasing -s startup parameter (5635)
The error only occurs when running a nightly routine which we have been running for several years without issue.

Pasted our startup .pf below. Total database size is fairly large, around 10GB. Server is a dual xeon, 2GB ram, running Server 2003 and has no other purpose than running progress.

Is it safe to increase the -s value? How much should I increment it?


# PF-TYPE = B "faria Server" no
#
# SESSION,Session-related parameters
-L 200000
-TB 24
-TM 31
-tok 1599
-inp 7000
-rand 2
-s 1000
-spin 1000
-n 200
-Bt 2000
-D 150
-mmax 32768
-nb 255
-q
-l 20000
-Mn 20
-yy 1920
#
# MAIN,faria
#-db \\manuf_server\SyteLine\db\faria
-B 100000
-H manuf_server
-N tcp
-S faria

Thanks for any input.

 

[TomBascom]

What version of Progress is this? You're using SyteLine so I'll guess 9.1C. Hopefully I am wrong because 9.1C is of course ancient, obsolete and unsupported.

Anyhow -s is limited only by available memory. (The documented maximum is 5,242,878 but that probably assumes some things like a 32 bit executable.) -s is measured in 1KB units -- 1,000 is roughly 1MB. So, yes, it should be safe to increase it. 2048 might be a good setting to try.

You probably have something going on where your code is sensitive to the amount of data being manipulated and that data has probably grown over time. (Your -l and -Bt settings seem to support that thought.) If you know what code is causing this you might want to review it and see if there is a way to make it more efficient.

 

[krellan2]

Thanks for the fast response!

Yes, we are on 9.1C. We are outside all support agreements, which was fine while my predecessor was still here since he had been to all the training available and wrote most of our in use routines.
He still comes in to add/modify as needed but is not available this week (of course that is when we start having problems).

My role in this software is more of a caretaker running set routines and a few changes here and there I know how to do.

Changed the startup parameters and will restart the database this evening after everyone has gone. Will post tommorow with the results.

Thanks again!

 

[krellan2]

Error happened again last night after making the change to the -s parameter from -s 1000 to -s 2048.

Attaching both the current startup .pf info as well as the log for when I retarted the database. On the database restart I see nothing listed for it aplying the -s value so I am wondering if it is just running the default -s value for some reason.

Log of the startup:

Tue Jan 05 17:27:13 2010
17:27:13 BROKER 0: Multi-user session begin. (333)
17:27:14 BROKER 0: Begin Physical Redo Phase at 3072 . (5326)
17:27:14 BROKER 0: Physical Redo Phase Completed at blk 13026 off 4937 upd 733. (7161)
17:27:14 BROKER 0: Started for faria using tcp, pid 5984. (5644)
17:27:14 BROKER 0: PROGRESS Version 9.1C on WINNT. (4234)
17:27:14 BROKER 0: Server started by on CON:. (4281)
17:27:14 BROKER 0: Started using pid: 5984. (6574)
17:27:14 BROKER 0: Physical Database Name (-db): d:\syteline\db\faria. (4235)
17:27:14 BROKER 0: Database Type (-dt): PROGRESS. (4236)
17:27:14 BROKER 0: Force Access (-F): Not Enabled. (4237)
17:27:14 BROKER 0: Direct I/O (-directio): Not Enabled. (4238)
17:27:14 BROKER 0: Number of Database Buffers (-B): 100000. (4239)
17:27:14 BROKER 0: Maximum private buffers per user (-Bpmax): 64. (9422)
17:27:14 BROKER 0: Excess Shared Memory Size (-Mxs): 16442. (4240)
17:27:14 BROKER 0: Current Size of Lock Table (-L): 200000. (4241)
17:27:14 BROKER 0: Hash Table Entries (-hash): 25621. (4242)
17:27:14 BROKER 0: Current Spin Lock Tries (-spin): 1000. (4243)
17:27:14 BROKER 0: Number of Semaphore Sets (-semsets) 1. (6526)
17:27:14 BROKER 0: Crash Recovery (-i): Enabled. (4244)
17:27:14 BROKER 0: Database Blocksize (-blocksize): 4096. (6573)
17:27:14 BROKER 0: Delay of Before-Image Flush (-Mf): 3. (4245)
17:27:14 BROKER 0: Before-Image File I/O (-r -R): Reliable. (4247)
17:27:14 BROKER 0: Before-Image Truncate Interval (-G): 60. (4249)
17:27:14 BROKER 0: Before-Image Cluster Size: 524288. (4250)
17:27:14 BROKER 0: Before-Image Block Size: 8192. (4251)
17:27:14 BROKER 0: Number of Before-Image Buffers (-bibufs): 5. (4252)
17:27:14 BROKER 0: BI File Threshold size (-bithold): 0.0 Bytes. (9238)
17:27:14 BROKER 0: BI File Threshold Stall (-bistall): Disabled. (6552)
17:27:14 BROKER 0: After-Image Stall (-aistall): Not Enabled. (4254)
17:27:14 BROKER 0: Number of After-Image Buffers (-aibufs): 5. (4256)
17:27:14 BROKER 0: Storage object cache size (-omsize): 1024 (8527)
17:27:14 BROKER 0: Maximum Number of Clients Per Server (-Ma): 10. (4257)
17:27:14 BROKER 0: Maximum Number of Servers (-Mn): 21. (4258)
17:27:14 BROKER 0: Minimum Clients Per Server (-Mi): 1. (4259)
17:27:14 BROKER 0: Maximum Number of Users (-n): 201. (4260)
17:27:14 BROKER 0: Host Name (-H): manuf_server. (4261)
17:27:14 BROKER 0: Service Name (-S): faria. (4262)
17:27:14 BROKER 0: Network Type (-N): tcp. (4263)
17:27:14 BROKER 0: Character Set (-cpinternal): ISO8859-1. (4264)
17:27:14 BROKER 0: Parameter File: d:\syteline\db\faria_pc.pf. (4282)
17:27:14 BROKER 0: Minimum Port for Auto Servers (-minport): 3000. (5648)
17:27:14 BROKER 0: Maximum Port for Auto Servers (-maxport): 5000. (5649)
17:27:14 BROKER 0: This broker supports both 4GL and SQL server groups. (8865)

Current .pf info:

# PF-TYPE = B "faria Server" no
#
# SESSION,Session-related parameters
-L 200000
-TB 24
-TM 31
-tok 1599
-inp 7000
-rand 2
-s 2048
-spin 1000
-n 200
-Bt 2000
-D 150
-mmax 32768
-nb 255
-q
-l 20000
-Mn 20
-yy 1920
#
# MAIN,faria
#-db \\manuf_server\SyteLine\db\faria
-B 100000
-H manuf_server
-N tcp
-S faria

Any healp would be greatly appreciated.

 

[TomBascom]

-s is a client parameter not a db startup parameter.

Actually your .pf file is a mix of various things and, generally, a mess. It could use a serious review

 

[TomBascom]

Current .pf info:

# PF-TYPE = B "faria Server" no
#
# SESSION,Session-related parameters
-L 200000 # this is a DB parameter, not a session parameter
-TB 24 # this is a session parameter, it has no purpose in a db startup .pf
-TM 31 # this is a session parameter, it has no purpose in a db startup .pf
-tok 1599 # this is a session parameter, it has no purpose in a db startup .pf
-inp 7000 # this is a session parameter, it has no purpose in a db startup .pf
-rand 2 # this is a session parameter, it has no purpose in a db startup .pf
-s 2048 # this is a session parameter, it has no purpose in a db startup .pf
-spin 1000 # this is a DB parameter, not a session parameter
-n 200 # this is a DB parameter, not a session parameter
-Bt 2000 # this is a session parameter, it has no purpose in a db startup .pf
-D 150 # this is a session parameter, it has no purpose in a db startup .pf
-mmax 32768 # this is a session parameter, it has no purpose in a db startup .pf
-nb 255 # this is a session parameter, it has no purpose in a db startup .pf
-q # this is a session parameter, it has no purpose in a db startup .pf
-l 20000 # this is a session parameter, it has no purpose in a db startup .pf
-Mn 20 # this is a DB parameter, not a session parameter
-yy 1920 # this is a session parameter, it has no purpose in a db startup .pf
#
# MAIN,faria
#-db \\manuf_server\SyteLine\db\faria
-B 100000 # this is a DB parameter, not a session parameter
-H manuf_server # this is both a DB & a session parameter
-N tcp # this is both a DB & a session parameter -- but it is silly, there is no other network protocol
-S faria # this is both a DB & a session parameter

 

[krellan2]

Added the -s 2048 to the pf file that is called when starting the session for the nightly routine. Hopefully that will take care of this.

Again I thank you for all the help, this is all moslty greek to me

 

[krellan2]

Adding the -s value to the correct .pf file did the trick. Running smooth for now.
I need to go through all those settings now and see which ones are in the wrong .pf's.

Thank you for all your help!!