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!!
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 :)
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...
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...
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.