topic Command does not have memory locking privileges in Operating System - HP-UX

Command does not have memory locking privileges

jaminas — Fri, 10 Aug 2007 06:46:28 GMT

Hi,

I have HP_UX 10.20 system with large databases on. It is a sybase server that returns the following error messages whenver the server is started:

process pid == 2513, command RUN_ABUJA does not have memory locking privileges required for using large text pages in this system version. Either correct the privileges (see setprivgrp(1m)) or chatr the executable text to a non +L option see chatr(1m)

where RUN_ABUJA is the script that is run at /opt/sybase/install to start the sybase server.

these messages do not stop the server from starting but we are unable to load from DLT8000 backup (containing large database)

Pls what is responsible?

thanks in advance

Re: Command does not have memory locking privileges

Steven E. Protter — Fri, 10 Aug 2007 06:50:38 GMT

Shalom,

Could be fixed by OS patches or database patches, or other issues.

To be of further help, please give more details such as version number of Sybase, what bi-annual patch update is installed, things like that.

What is your backup methodology, eg software.

SEP

Re: Command does not have memory locking privileges

Dennis Handly — Fri, 10 Aug 2007 09:37:14 GMT

Have you read about, see setprivgrp(1m)?
This may not be related to your DLT8000 issue?

Re: Command does not have memory locking privileges

whiteknight — Fri, 10 Aug 2007 11:47:46 GMT

Brief explanation of why these messages occur:
---------------------------------------------

An application is coded to use large text pages but the OS and hardware
that this application is running on, may or may not be able to handle
this request. You can use the echo allow_superpage..... command (see
below) to see if the system can handle large text pages. If so, then the group
that is trying to run the processes that is trying to use large text pages
needs to have permission to do so. That is where the setprivgrp command
is used.

To verify:
---------

Run the following command to verify the system you are running on can
handle large text pages:

echo allow_superpage_text/D | adb -w /stand/vmunix /dev/kmem

It will return the following:

allow_superpage_text:
allow_superpage_text: 1

If the value is 1, then the system can handle large text pages. If it
is set to 0, then it can't and the Sybase code will have to be changed
to not try to grab large text pages. You will need to get that code
change from Sybase.

If the value is 1, then you simply need to give the sybase group the
appropriate privileges. You can do that by creating a file called
/etc/privgroup:

touch /etc/privgroup

From the command line you can run

setprivgrp -f /etc/privgroup

This will make the messages go away without rebooting the system. Upon reboot,
there is a startup script in /sbin/init.d called set_prvgrp that
will be run once the file /etc/privgroup exists.

The file /etc/privgroup needs to be in this format:

groupname [privileges]

EXAMPLE:
--------

sybase CHOWN MLOCK

The CHOWN and MLOCK are the two privileges that you need to
include.