Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

on large databases we have lower memlock than needed #12

Open
DmitriyStoyanov opened this issue Jan 18, 2019 · 0 comments
Open

on large databases we have lower memlock than needed #12

DmitriyStoyanov opened this issue Jan 18, 2019 · 0 comments

Comments

@DmitriyStoyanov
Copy link

DmitriyStoyanov commented Jan 18, 2019

SUMMARY

On database with 20GB we found that memlock hard limited to 8GB
as described here https://docs.oracle.com/cd/E11882_01/server.112/e10839/appi_vlm.htm#UNXAR396
we should have memlock configured to shm and SGA size

in that case here vars/oracle12.yml we should change static limits here
- "oracle soft memlock 7340032"
- "oracle hard memlock 8388608"

also in centos7 we have some changes in checks of /etc/security/limits.conf
https://serverfault.com/questions/628610/increasing-nproc-for-processes-launched-by-systemd-on-centos-7/678861#678861
and such changes also should be configured in service template file templates/oracledb.systemd.j2
for example:
[Service]
...
LimitMEMLOCK=infinity
LimitNOFILE=65535
..,

ISSUE TYPE
  • Bug Report
COMPONENT NAME
ANSIBLE VERSION

CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE

Create DB with 20GB
and in alert log you will see message like:

  1. Increase per process memlock (soft) limit to at least 20GB
    to lock 100% of SHARED GLOBAL AREA (SGA) pages into physical memory
EXPECTED RESULTS

memlock size configured as SGA or SHM size

ACTUAL RESULTS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant