MemoryLock
Enables applications that connect to a shared database to specify whether the real memory should be locked during database loading.
On Linux, MemoryLock=4 will try to obtain a
MemoryLock based on what the operating system allows. On Linux,
locking all of the virtual memory size (physical + swap) can occur. TimesTen
performs best if it does not use swap. Since the operating system allows locking
more memory than is actually available, it is important to carefully configure the
operating system memory management parameters to limit the amount of lockable
memory. You can configure these parameters in the
/etc/security/limits.conf file.
Note:
If you are using systemd, set the LimitMEMLOCK
setting in the #Service Limit Settings section of the service
unit configuration file as specified in Using systemd to Manage a TimesTen Service in Oracle TimesTen In-Memory Database
Installation, Migration, and Upgrade Guide to control the amount of memory a
user can lock.
On AIX the MemoryLock attribute is not implemented.
The PL/SQL shared memory segment is not subject to MemoryLock.
Required Privilege
Only the instance administrator can change the value of this attribute.
On Linux systems, set the groupname in the MemLock setting to be the same as the instance administrator in the /etc/security/limits.conf file. Set the value of MemLock to be at least as large as the TimesTen database shared memory segment.
To restart the TimesTen daemons, in the new login shell, use:
% ttDaemonadmin -restart
Setting
Set MemoryLock as follows.
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |