![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| HP-UX HP-UX (Hewlett Packard UniX) is Hewlett-Packard's proprietary implementation of the Unix operating system, based on System V. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| UNIX memory problems w/Progress DB | eddiej | UNIX and Linux Applications | 0 | 12-12-2007 09:06 AM |
| Unix Help - allocate more memory to /tmp | cmackin | UNIX for Dummies Questions & Answers | 1 | 06-01-2006 03:25 AM |
| unix memory management | gfhgfnhhn | UNIX for Advanced & Expert Users | 1 | 04-03-2006 02:19 PM |
| Program/ Memory Problems | dbrundrett | UNIX for Advanced & Expert Users | 1 | 07-28-2004 03:19 AM |
| plock() memory locking problems | troccola | UNIX for Advanced & Expert Users | 5 | 01-30-2002 06:28 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
|||
|
I don't know if this is better suited for the application section, but here goes.
We are currently running HP-UX 11 as our database server. The database is Progress version 9.1C. As of late, some of our batch processes that run on the UNIX db server are erroring out because of what appear to be memory issues(at least according to Progress). The db error messages indicate that either there are too may subprocesses and it cannot fork, there is not enough memory to execute the request, or there is not enough memory to allocate a sort buffer. There does not appear to be a consistent pattern to when this happens. Also, we don't appear to be exceeding swap space. Not sure what else it could be. If any of you have encountered similiar problems, how did you resolve it? Any and all feedback is appreciated. -Ed |
| Forum Sponsor | ||
|
|
|
|||
|
You said it wasn't a swap space issue, but as Perderabo suggested take another close look at that, and if you have more than one swap space, there's no real guarantee which one will be selected at any point in time.
The first issue, can't fork, almost sounds like you need to do some kernel tweeking. The database owners should be able to give you some ballpark kernel settings, however thats all dependant of DB size, how much/how often updates, queries take place for your installation; however they should be able to give you some min. settings. If you've not already tweeked these, max_thread_count might be a place to look, however there are many other paramaters worth looking at. Doing in a production envoriment is not ideal. Definately document well, what your original setting were, and exactly what was changed. Best done with someone with some experience with kernel tuning. |