You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue when the Hugepages are changed after the initial setup of a machine. Newer Linux Kernels allow the increase of Hugepages only when enough free memory is availible. Memory from Filecache is not free memory during this check.
We need to flush the Filecache before the Hugepages could be allocated from free Memory...
This issue is interesting for running systems when a new Database is created or for changes in existing databases. The problem could occur during new installations when most of the Memory is allocated by the Filecache which is really rare.
I don't have an easy solution for this issue at the momen, because clearing the Filecache during each execution of the host tasks is not a good idea in running systems...
Searching for easy solutions...
I saw this issue under RHEL7.
The text was updated successfully, but these errors were encountered:
This is one of the biggest changes during the development of ansible-oracle since last refactoring.
The project moves to a collection, which leads to the following breaking changes:
- rename all roles with '-' in name to '_'
This is a mandatory change, when moving to a collection.
galaxy will not import a collection with a '-' in rolename...
- Ansible 2.9+ needed
Due to the dependency to Collections, the minimum version of Ansible has been cahnged to 2.9.
- moved playbooks to playbooks folder
This is the 1st step to reorganize the old - mostly not working -
playbooks. The redesign of playbooks and example inventory is planned
for a later time.
- renamed variable for EE-Options in Binaries
All variables with `oracle_EE_options` have been changed to `oracle_ee_options`. An assertation has been added to check the inventory for old - unsupported - variables.
Other minor changes:
- update ansible-lint for git pre-commit to v6.3.0
- removed all check exceptions from .ansible-lint
There is an issue when the Hugepages are changed after the initial setup of a machine. Newer Linux Kernels allow the increase of Hugepages only when enough free memory is availible. Memory from Filecache is not free memory during this check.
We need to flush the Filecache before the Hugepages could be allocated from free Memory...
This issue is interesting for running systems when a new Database is created or for changes in existing databases. The problem could occur during new installations when most of the Memory is allocated by the Filecache which is really rare.
I don't have an easy solution for this issue at the momen, because clearing the Filecache during each execution of the host tasks is not a good idea in running systems...
Searching for easy solutions...
I saw this issue under RHEL7.
The text was updated successfully, but these errors were encountered: