- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Memory error
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
Discussions
Discussions
Forums
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
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
тАО01-19-2006 08:02 AM
тАО01-19-2006 08:02 AM
Anyone seen this error (below) before??
The specs on the Alpha severs as follows:
Alpha 4100 w/2.0GB of RAM - OpenVMS 7.3-2
Error: Not enough memory. Attempting to allocate
64000 entries of 2 bytes for 'c042bf'
Thanks,
J
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 08:10 AM
тАО01-19-2006 08:10 AM
Re: Memory error
Anyway, sounds like a working set is too small.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 08:25 AM
тАО01-19-2006 08:25 AM
Re: Memory error
Error: Not enough memory. Attempting to allocate
64000 entries of 2 bytes for 'c042bf'
This is NOT a VMS error.
All of them are of the format:
%xxx-y-zzz , text
Where xxx = facility ( LIB or SYS or SOR 0r... many others
y = S, I, W, E, or F
for Success (usually supperssed messages!), Informational, Warning, Error or Fatal
zzz = short message mnemonic, like in this case it probably would have been INSVIRMEM
text = description. In this case a likely text would have been Insufficient Virtual Memory.
I suspect this message is from a package (a Unix port maybe ?) that captures several errors and then tries to give a "more descriptive error message" - only, the standard VMS messages are MUCH more informational.
Can you tell us what software gave this message?
Proost.
Have one on me.
jep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 08:26 AM
тАО01-19-2006 08:26 AM
Re: Memory error
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 09:08 AM
тАО01-19-2006 09:08 AM
SolutionIn the simple case...
$ set default sys$system:
$ run authorize
UAF> show USERNAME
UAF> mod USERNAME/wsex=nnnnn
UAF> exit
where USERNAME is the owner of that batch log file and nnnnn is some number greater than the previous value of WSEXTENT (in pages). 64000*2 bytes is only 250 pages sp that's just the last thing that occurred in the process prior to failure. If you don't have the source to determine the needs then just guess. On an alpha server with memory such as yours 32000 pages is certainly not out of line (64k is unlikely to be a problem either).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 10:07 AM
тАО01-19-2006 10:07 AM
Re: Memory error
I have no info what kind of application you with other system's loads, anyway I would like to suggest to consider couple of more sysgen params for this kind error.
Usually when a process starts executing an image, the process works within WSDEFAULT.
When that process has higher page fault rate than PFRATH, then it will go upto WSQUOTA by the size of WSINC.
i.e WSDEFAULT - WSINC - WSQUOTA
If the process keeps increasing page fault rate and the free list size exceeds BORROWLIM, then that process continues to get the pagelets by WSINC until the free list size is inadequate or WSEXTENT is reached
i.e WSDEFAULT - WSINC - WSQUOTA - WSINC - WSEXTENT.
So better you can look into atleast DSDEFAULT, WSQUOTA, and WSEXTENT values and once you confirm this is the reason, you can follow Jim's way to modify the params values.
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 06:20 PM
тАО01-19-2006 06:20 PM
Re: Memory error
A process starts with wsdefault (doing dcl).
When an image is started, you get wsquota.
When you page fault (a lot), the ws can grow to wsext if memory allows it.
So, if the working set is too small, you need to increase wsquota (and may be wsextent).
But memory is normally allocated from your pagefilequota ...
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 06:53 PM
тАО01-19-2006 06:53 PM
Re: Memory error
You get the right to use wsquota. You just have to use the memory and you get it. In contract to wsextent for which you have to work (earn it).
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 07:29 PM
тАО01-19-2006 07:29 PM
Re: Memory error
It could be something like in Oracle where a shared pool can be configured which can run out even though 'the system' has more memory and the process has the right to use that memory.
Please dig deeper for details around the message.
What product/application?
Did it ever work?
What changed?
Is there an applicaiton error log perhaps?
Jim, Archunan, I respectfully dissagre with any suggestion that this might have anything to do with Working Sets. Working sets are strictly a performance influencing setting. They have no functional effect. No program (other than VMS SORT and RDB :-) ever fails due to working set settings, they just run slower than needed.
As Wim indicates, it is more likely to be PAGFILQUO, but it could be lack of pagefile itself or a VIRTUAL MEMORY limit. The process could be out of its 1GB base memory. Or it could have poorly alloacted (fragmented) that base memory. It could be out of stack, or is could be a program imposed restriction in which case no VMS setting can fix it and noone here can help untill we know the program.
Good luck,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 08:03 PM
тАО01-19-2006 08:03 PM
Re: Memory error
Almost correct. TCPTRACE (tested in VMS 6.2) locks pages in the working set. If wsquota is too low it fails. Try with a wsquota of 512. It will fail.
Wim