Increasing "MEMORY" size in ulimit...

[aique]

Hi, i want to increase "MEMORY" size to "Unlimited" in ulimit output. But i can't find it in Kernel Tuner Utility in Tru64 UNIX V5.1B.
Here is the output of ulimit -H:

# ulimit -H
cputime unlimited
filesize unlimited
datasize 1048576 kbytes
stacksize 32768 kbytes
coredumpsize 9007199254740991 kbytes
memory 2024864 kbytes
descriptors 4096 files
addressspace 4194304 kbytes

Can anybody tell me that from where can i change its (memory) value?

Please help,
Thanks.

[Steven Schweda · Accepted solution]

On my system:

urt# ulimit -H
unlimited

urt# /usr/bin/ulimit -H
unlimited

Which "ulimit" are you using?

> coredumpsize 9007199254740991 kbytes

It that's supposed to be significantly
different from "unlimited", then your file
system must be a lot bigger than mine.

> memory 2024864 kbytes

My "ulimit" programs say:

urt# ulimit -a
core file size (blocks) unlimited
data seg size (kbytes) 2097152
file size (blocks) unlimited
max memory size (kbytes) 371696
open files 4096
pipe size (512 bytes) 8
stack size (kbytes) 8192
cpu time (seconds) unlimited
max user processes 8192
virtual memory (kbytes) 4194304


urt# /usr/bin/ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 2097152
stack(kbytes) 8192
memory(kbytes) 371696
coredump(blocks) unlimited
nofiles(descriptors) 4096
vmemory(kbytes) 4194304


urt# ulimit -m
371696

urt# /usr/bin/ulimit -m
371696

"man ulimit" says:

-m limit
[Tru64 UNIX] The limit operand specifies the number of Kilobytes for
the size of physical memory.


My system has 384MB. I suspect that yours
has 2GB. Not knowing the model of your
hardware, I can't supply any details on how
to increase its memory, but if you open the
box, you may find some empty memory slots.

Rather than waste a lot more time, perhaps
you could tell us what the problem is which
you're trying to solve.

[aique]

Hi,
Actually we need to install Oracle 9i-R2 on this machine and Oracle people ran a script on this machine to find out requirements before installation can proceed. Following is the output of Oracle script:

#strinds /tmp/InstallPrep.err

ALERT- Increase the ulimit(DATA) to 1572864 from the present 1048576
ALERT- Increase the ulimit(MEMORY) to unlimited from the present 2024864
ALERT- new-wire-method has not been defined and needs to be set to 0
Please review this report and resolve all ALERTS or WARNINGs before attempting to install the Oracle Database Software
RESULTS = There were 3 ALERTs to address in running the InstallPrep

Thats why i need to increase 'memory' size to unlimited.

Please advice,
Thanks.

[Vladimir Fabecic]

Hello Abdul
First, IGNORE "increase "MEMORY" size to "Unlimited" in ulimit output" in TRU64. Non root user should not have bigger limit then RAM.
So do not worry about that!
But you shoud increase parameters "max-per-proc-data-size" and "per-proc-data-size" (to be 1572864 or higher).
These parameters are for datasize limit.
What Patch Kit do you have installed? Probably PK4 or PK5. In that case parameter new-wire-method is obsolete and do not worry about that.
Just ignore these alerts and install Oracle.
By the way, you should read this:
http://forums1.itrc.hp.com/service/forums/helptips.do?#28

[Johan Brusche]

RE: ALERT- Increase the ulimit(MEMORY)
Above statement is too ambigeous.
Physical memory is as it says "physical" and can only be increased by adding hardware.

Probably their talking about the proc parameters 'per_proc_address_space' and 'max_per_proc_address_space' which should in any case be 2 to 4 times lager than per_proc_data_size.

The Oracle users is NOT root, though you are root(unlimited) while installing, this user is subject to the same 'proc' limits as any other user.

RE: ALERT- new-wire-method

To set straigth some incorrect statements about new_wire_method in this and other threads in december

For V5.1B LOWER than BL24 ie BEFORE patchkit#3, Oracle recommends to set new_wire_method=0

For V5.1B BL24 AND BL25 ie patchkit#3 AND #4
Oracle's recommendation is to set new_wire_method=1

In current manuals Oracle still recommends to set new_wire_method=1, but in the current V5.1B BL25 this parameter is RETIRED, using it in /etc/sysconfigtab has no influence at all.

All the best for 2006.

__ Johan ./

[aique]

Hi Vladimir,
I will assign points once my problem is solved, don't worry ;)

Well you said i should ignore these Alerts but when i ignore these Alerts, Oracle exits. :(
Means it will not continue unless we change those values. I have changed 'datasize' value in Kernel Tuner. But i didn't find any thing related to change 'MEMORY' there.
So it will highly be appretiated if someone tell me that from where i can change 'MEMORY' to unlimited.
Thanks.

[aique]

Hi Johan,
Thanks for your new year wish:)
Well if 'MEMORY' field can only be increased by adding new hardware then why it shows 16-digit value when i give it following command?

#ulimit -m unlimited

Although this only lasts for current session and when i close that terminal windows it also resets.
BTW i have Tru64 UNIX V5.1B with PK5.
Please see my first Post again for your reference.

Thanks once again.

[Vladimir Fabecic]

Edit the Oracle scripts.

[Steven Schweda]

> Well if 'MEMORY' field can only be
> increased by adding new hardware then why
> it shows 16-digit value when i give it
> following command?
>
> #ulimit -m unlimited

Which "ulimit"? It seems as if every claim
you make about what you did, and what you
saw when you did it, disagrees with what I
see on my system whan I do what you say.

urt# /usr/bin/ulimit -m
371696

urt# /usr/bin/ulimit -m unlimited

urt# /usr/bin/ulimit -m
371696

The only "16-digit value" you've shown is
the one for "core" file size ("-c").

> BTW i have Tru64 UNIX V5.1B with PK5.
> Please see my first Post again for your reference.

Your first post did not mention PK5. If
that's the same as "Version 5.1B-3
Consolidated Patch Kit", then that's what I
have, too.

If your problem is with an Oracle
installation, then perhaps you should ask
the Oracle.

[aique]

Hi,
Well Steven, if you applied the 'ulimit -m' command for 'unlimited' then you can see 16 digit value by applying following command:

#ulimit -H

And yes my first post is not mentioning about my Patch Kit Level but i asked you to review it for the output of "ulimit -H" :)

BTW my Oracle problem is solved :)
and you were right problem was with oracle people.

Thanks for your co-operation.

[Steven Schweda]

> [...[ if you applied the 'ulimit -m'
> command for 'unlimited' then you can see 16
> digit value by applying following command:
>
> #ulimit -H

No, not really.

urt# /usr/bin/ulimit -H
unlimited

urt# ulimit -H
unlimited

urt# ulimit -m unlimited

urt# ulimit -H
unlimited

urt# /usr/bin/ulimit -H
unlimited

urt# /usr/bin/ulimit -m unlimited

urt# ulimit -H
unlimited

urt# /usr/bin/ulimit -H
unlimited

I show how I get what I get. You never seem
to show how you get what you claim to get,
and I never seem to get what you claim to
get when I do what you say you do.

Actual commands and actual results are often
much more useful than vague descriptions of
commands and results. (They tend to reduce
wasted time and effort, too.)

[aique]

Well Steven what i think arguments never ends. But i only want to say that i was not kidding at all and on my machine These commands showed the same results as i showed to you people out there. And i have no intentions to waste any of yours time.

Anyhow my problem is solved so i am now going to close this thread.

Thanks for your compliments towards me :(

[Steven Schweda]

It might be nice if you posted a summary of
the solution you found, in case someone with
a similar problem seaches this forum and
finds this thread.

And if you ever figure out which "ulimit"
acts the way you say yours does...

[aique]

Well actually we only had to change 'datasize' and 'per_proc_address_space'. It worked and there was no need to change 'memory' size. According to HP experts, those 'Oracle Alerts' should be ignored which we did and installed Oracle successfully :)
But i still can't understand that why "#ulimit -m unlimited" command sets memory field to 16-digit figure for that terminal session.
Bye.

[Steven Schweda]

> But i still can't understand that why
> "#ulimit -m unlimited" command sets memory
> field to 16-digit figure for that terminal
> session.

And I can't understand why you won't say
which "ulimit" you are using, which makes it
hard to guess why you see what you see.

My latest guess is that it's the built-in in
/bin/sh, which does appear to act that way.
You should try a better shell. I seem to be
using GNU bash 2.05, and its built-in
"ulimit" has no such problems. The real
program, "/usr/bin/ulimit", as I've shown,
also has no such problems.

http://www.gnu.org/software/bash/bash.html

Apparently bash 3.1 is current. The command
line editing feature alone is worth the
effort.