Use this checklist to check minimum operating system requirements for Oracle Database.
Table 1-2 Operating System General Checklist for Oracle Database on Linux
Item
Task
Operating system general requirements
OpenSSH installed manually, if you do not have it installed already as part of a default Linux installation.
A Linux kernel in the list of supported kernels and releases listed in this guide.
Linux x86-64 operating system requirements
The following Linux x86-64 kernels are supported:
Oracle Linux 8.1 with the Unbreakable Enterprise Kernel 6: 5.4.17-2011.0.7.el8uek.x86_64 or later Oracle Linux 8 with the Red Hat Compatible kernel: 4.18.0-80.el8.x86_64 or later
Oracle Linux 7.4 with the Unbreakable Enterprise Kernel 4: 4.1.12-124.19.2.el7uek.x86_64 or later Oracle Linux 7.4 with the Unbreakable Enterprise Kernel 5: 4.14.35-1818.1.6.el7uek.x86_64 or later Oracle Linux 7.7 with the Unbreakable Enterprise Kernel 6: 5.4.17-2011.4.4.el7uek.x86_64 or later Oracle Linux 7.5 with the Red Hat Compatible Kernel: 3.10.0-862.11.6.el7.x86_64 or later
Red Hat Enterprise Linux 8: 4.18.0-80.el8.x86_64 or later
Red Hat Enterprise Linux 7.5: 3.10.0-862.11.6.el7.x86_64 or later
SUSE Linux Enterprise Server 15: 4.12.14-23-default or later
SUSE Linux Enterprise Server 12 SP3: 4.4.162-94.72-default or later
Review the system requirements section for a list of minimum package requirements.
IBM: Linux on System z operating system requirements
The following IBM: Linux on System z kernels are supported:
Red Hat Enterprise Linux 8.3: 4.18.0-240.el8.s390x or later
Red Hat Enterprise Linux 7.4: 3.10.0-693.el7.s390x or later
SUSE Linux Enterprise Server 12: 4.4.73-5-default s390x or later
Review the system requirements section for a list of minimum package requirements.
Oracle Database Preinstallation RPM for Oracle Linux
If you use Oracle Linux, then Oracle recommends that you run the Oracle Database Preinstallation RPM for your Linux release to configure your operating system for Oracle Database and Oracle Grid Infrastructure installations.
Oracle RPM Checker utility for IBM: Linux on System z
Oracle recommends that you use the Oracle RPM Checker utility to verify that you have the required Red Hat Enterprise Linux or SUSE packages installed on your IBM: Linux on System z operating system before you start the Oracle Database or Oracle Grid Infrastructure installation.
Disable Transparent HugePages
Oracle recommends that you disable Transparent HugePages and use standard HugePages for enhanced performance.
Источник
How to see the version of Oracle Linux
Determine Oracle Linux version
Oracle Linux is based on Red Hat Enterprise Linux. At first, it may be confusing to determine what specific operating system is running. This is because both have the /etc/redhat-release file.
If that file exists, use the cat command to display the contents. Next step is to determine if there is a /etc/oracle-release file as well. If so, then you can be sure that Oracle Linux is running.
Sample output might be: Oracle Linux Server release 6.7
Other options
Next time when you are on a system and not sure what it is running, use this:
This shows you any files that might give a hint on the operating system version.
Related files
/etc/enterprise-release (older versions of OEL)
/etc/issue
/etc/issue.net
/etc/lsb-release
Keep learning
So you are interested in Linux security? Join the Linux Security Expert training program, a practical and lab-based training ground. For those who want to become (or stay) a Linux security expert.
Run automated security scans and increase your defenses. Lynis is an open source security tool to perform in-depth audits. It helps with system hardening, vulnerability discovery, and compliance.
Continue reading
Livepatch: Linux kernel updates without rebooting
How to secure a Linux system
The state of Linux security in 2017
Linux security myths
Leave a Reply Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
About Linux Audit
This blog is part of our mission: help individuals and companies, to scan and secure their systems. We simply love Linux security, system hardening, and questions regarding compliance.
Besides the blog, we have our security auditing tool Lynis. Open source, GPL, and free to use.
For those with enterprise needs, or want to audit multiple systems, there is an Enterprise version.
«One security solution to audit, harden, and secure your Linux/UNIX systems.»
Benefits:
Perform audits within a few minutes
Central management
Powerful reporting
Compliance checks (e.g. PCI DSS)
Additional plugins and more tests
Enjoy the articles!
Linux and UNIX security automation
Lynis is a free and open source security scanner. It helps with testing the defenses of your Linux, macOS, and Unix systems. Typical use-cases for this software include system hardening, vulnerability scanning, and checking compliance with security standards (PCI-DSS, ISO27001, etc).
Recent Posts
Contact
This blog is part of our mission to share valuable tips about Linux security. We are reachable via @linuxaudit
Company details
CISOfy De Klok 28, 5251 DN, Vlijmen, The Netherlands +31-20-2260055
Источник
C Administering Oracle Database on Linux
This appendix contains information about administering Oracle Database on Linux. It contains the following topics:
C.1 Extended Buffer Cache Support
This section applies to Linux x86 only.
Oracle Database can allocate and use more than 4 GB of memory for the database buffer cache. This section describes the limitations and requirements of the extended buffer cache feature on Linux x86 systems.
Oracle Database Concepts for more information about the extended buffer cache feature
In-Memory File System
To use the extended buffer cache feature, create an in-memory file system on the /dev/shm mount point equal in size or larger than the amount of memory that you intend to use for the database buffer cache. For example, to create an 8 GB file system on the /dev/shm mount point:
Run the following command as the root user:
To ensure that the in-memory file system is mounted when the system restarts, add an entry in the /etc/fstab file similar to the following:
When Oracle Database starts with the extended buffer cache feature enabled, it creates a file in the /dev/shm directory that corresponds to the Oracle buffer cache.
If an in-memory file system is already mounted on the /dev/shm mount point, then ensure that its size is equal to or larger than the amount of memory that is used for the database buffer cache.
To enable the extended buffer cache feature, set the USE_INDIRECT_DATA_BUFFERS initialization parameter to TRUE in the parameter file. This enables Oracle Database to specify a larger buffer cache.
Dynamic Cache Parameters
If the extended cache feature is enabled, then you must use the DB_BLOCK_BUFFERS parameter to specify the database cache size.
Do not use the following dynamic cache parameters while the extended buffer cache feature is enabled:
The following limitations apply to the extended buffer cache feature:
You cannot create or use tablespaces with nondefault block sizes. You can create tablespaces using only the block size specified by the DB_BLOCK_SIZE parameter.
You cannot change the size of the buffer cache while the instance is running.
Oracle Database SQL Reference for more information about the default block size used by the CREATE TABLESPACE command
The default VLM window size is 512 MB. This memory size is allocated to the address space of the process. To increase or decrease this value, set the VLM_WINDOW_SIZE environment variable to the new size in bytes. For example, to set the VLM_WINDOW_SIZE to 256 MB, run the following command:
The value that you specify for the VLM_WINDOW_SIZE environment variable must be a multiple of 64 KB.
Red Hat Enterprise Linux 3 Only: VL M Window Size
To accommodate the VLM window size, you must increase the default maximum size of the per-proce ss locked memory. To increase it, add the following lines to the /etc/security/limits.conf file, where oracle is the user that administers the database:
If you use ssh to log in to the system, then add the following line to the /etc/ssh/sshd_config file to enable the default values to be used when an ssh session is started:
C.2 Using hugetlbfs on SUSE Linux Enterprise Server 9 or Red Hat Enterprise Linux 4
To enable Oracle Database to use large pages (sometimes called huge pages) on SUSE Linux Enterprise Server 9, or Red Hat Enterprise Linux 4, set the value of the vm.nr_hugepages kernel parameter to specify the number of large pages that you want to reserve. You must specify a sufficient number of large pages to hold the entire SGA for the database instance. To determine the required parameter value, divide the SGA size for the instance by the size of a large page, then round up the result to the nearest integer.
To determine the default large page size, run the following command:
For example, if /proc/meminfo lists the large page size as 2 MB, and the total SGA size for the instance is 1.6 GB, then set the value for the vm.nr_hugepages kernel parameter to 820 (1.6 GB / 2 MB = 819.2).
C.3 Using hugetlbfs on Red Hat Enterprise Linux AS 3
Linux on POWER is not supported on Red Hat Linux AS 3.
To use large pages on Red Hat Enterprise Linux AS 3:
Determine the memory required for the large page pool.
To determine this value, convert the size of the SGA of the instance to megabytes, and round up by 4 MB. For example, if the SGA is 2.7 GB, then the appropriate value is 2768 MB.
Depending on the type of your boot loader, perform one of the following procedures:
Add the hugepages option to the appropriate image section in the /etc/lilo.conf file, specifying the number of pages:
Restart the system.
Add the hugepages option to the kernel command in the /etc/grub.conf file, specifying the number of pages as follows:
Restart the system.
Add or edit the following entry in the /etc/sysctl.conf file, specifying the large page pool size in megabytes:
Run the following command to set the kernel parameter values:
To verify that this amount of memory was moved successfully into the large page pool, run the following command:
The lines at the end of the display show how many memory pages were moved into the large page pool.
Start Oracle Database.
C.4 Increasing SGA Address Space
This section applies to Linux x86 only.
Depending on your distribution of Linux, apply the instructions in one of the following sections to increase the SGA address space:
SUSE Linux Enterprise Server 9
To increase the SGA address space on SUSE Linux Enterprise Server 9:
Log in as the oracle user.
In the $ORACLE_HOME/rdbms/lib directory, run the following commands:
If Oracle Database does not start after completing this procedure, or if there are run-time memory errors, then increase the hexadecimal number specified in the first command. For example, if the 0x15000000 value prevents Oracle Database from starting, then specify the value 0x20000000. Lowering this value increases the SGA address space, but could decrease the PGA address space.
Run the following command to determine the process ID of the oracle user’s shell process:
The number returned is the process ID.
Run the following command to switch user to root :
Run the following commands to change the mapped base setting for the oracle user’s shell process, where pid is the process ID identified in step 3:
Run the exit command to return to the oracle user’s shell process, and start Oracle Listener and Oracle Database.
All Oracle processes must get this modified mapped base value. Starting the listener from the shell that has the modified mapped base enables client connections to connect properly.
Red Hat Enterprise Linux AS 3
To increase the SGA address space on Red Hat Enterprise Linux AS 3 or 4:
Log in as the oracle user.
In the $ORACLE_HOME/rdbms/lib directory, run the following commands:
Start Oracle Database.
C.5 Asynchronous I/O Support
On Linux, Automatic Storage Management uses asynchronous I/O by default. Asynchronous I/O is not supported for database files stored on NFS file systems.
Oracle Database supports kernel asynchronous I/O. This feature is disabled by default.
By default, the DISK_ASYNCH_IO initialization parameter in the parameter file is set to TRUE to enable asynchronous I/O on raw devices. To enable asynchronous I/O on file system files:
Ensure that all Oracle Database files are located on file systems that support asynchronous I/O.
Set the FILESYSTEMIO_OPTIONS initialization parameter in the parameter file to one of the following values:
Linux Distribution
Recommended Value
SUSE Linux Enterprise Server 9
SETALL
Other distributions
ASYNCH
C.6 Direct I/O Support
Direct I/O support is available and supported on Red Hat Enterprise Linux 3 and SUSE Linux Enterprise Server 9.
To use direct I/O on Red Hat Enterprise Linux 3, the driver that you use must support vary I/O.
On Linux on POWER, you can use direct I/O on Red Hat Linux 4.
To enable direct I/O support:
Set the FILESYSTEMIO_OPTIONS initialization parameter to DIRECTIO .
If you are using the asynchronous I/O option, then set the FILESYSTEMIO_OPTIONS initialization parameter to SETALL .
C.7 semtimedop Support
semtimedop is not supported on Linux on POWER.
On Red Hat Enterprise Linux 3 and SUSE Linux Enterprise Server 9, Oracle Database supports the semtimedop() system call (semaphores with a time limitation). To enable support for the feature, run the following command as the oracle user in the $ORACLE_HOME/rdbms/lib directory:
To disable semtimedop() support, run the following command as the oracle user in the $ORACLE_HOME/rdbms/lib directory:
C.8 High-Speed Network Support
This section applies to Linux x86 only.
Oracle Net supports Sockets Direct protocol (SDP) over the InfiniBand network architecture on Red Hat Enterprise Linux AS 3 for Oracle Database 10 g release 1. For this release, SDP support is limited to synchronous I/O only. For information about support for using asynchronous I/O on SDP, refer to the following document:
Do not set the Oracle Net NET_ASYNC_IO and SDP_ASYNC_IO configuration parameters, unless otherwise stated in this document.
C.9 Simultaneous Multithreading (SMT)
If Simultaneous Multithreading (SMT) is enabled, the v$osstat view reports 2 additional rows corresponding to the online logical ( NUM_LCPUS ) and virtual cpus ( NUM_VCPUS ).
