![]() |
|
|
|||||||
| Home | Forums | Register | Rules & FAQ | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX and Linux Applications Questions involving software not covered by other forum go here. This includes Databases and Middleware. |
Other UNIX.COM Threads You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| UNIX memory problems | eddiej | HP-UX | 3 | 12-12-2007 12:41 PM |
| Progress Bar in Perl for UNIX | hifake | Shell Programming and Scripting | 0 | 08-07-2007 11:46 AM |
| IBM Unix progress gains kudos - VNUNet.com | iBot | UNIX and Linux RSS News | 0 | 07-18-2007 09:20 AM |
| 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 | Search this Thread | Display Modes |
|
|||
|
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 |
|||
| Google UNIX.COM |
| Forum Sponsor | ||
|
|