Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2002 03:49 AM
09-18-2002 03:49 AM
I am fairly familiar with the message below. I know about memory windowing at 64bit OS. However, I am getting this error from a peoplefost process scheduler. I know ORacle is only loaded as 32-bit on this Nclass 64-bit OS. We have to address this issue. Now, is the process scheduler art of oracle ot peoplesoft?
/usr/lib/dld.sl: Call to mmap() failed - TEXT
/app/ps/hrtst8/bin/libpssys.sl
/usr/lib/dld.sl: Not enough space
I can't remember the kernel parm to check also, maxdsiz, maybe?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2002 03:58 AM
09-18-2002 03:58 AM
Re: MMAP
The "Not enough space" is indicative of a limited
resource issue. Typically with lack of
swap space .
Check swap_space swapinfo -ta
maxdsiz
dbc_max_pct
Steve steel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2002 04:00 AM
09-18-2002 04:00 AM
Re: MMAP
since the error showing that 'Not enough space'
check the file systems sizes(bdf) if any is full.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2002 04:02 AM
09-18-2002 04:02 AM
Solution[ENOMEM] MAP_FIXED was specified, and the range [addr,
addr+len] exceeds that allowed for the address
space of a process; or if MAP_FIXED was not
specified and there is insufficient room in the
address space to effect the mapping.
So there are problems to find room in your 32bit address space for this mapping. There are no kernel tunables for this... you need to free up space. E.g. by using memory windows, as you already mentioned.
Regards...
Dietmar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2002 04:08 AM
09-18-2002 04:08 AM
Re: MMAP
maxdsiz
maxdsiz_64
parameters and
also the amount of memory available on the system
If your application is a 64 bit try increasing maxdsiz.
ALso check for the processes using the memory using
# UNIX95= ps -e -o ruser,vsz,pid,args|sort -rnk2
stop the unnecessary processes.
check your swap size
Thanks