Using PROCESSOR_GROUP_NAME to bind a database instance to CPUs or NUMA nodes on Solaris
(Doc ID 1928328.1)
Last updated on MARCH 06, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
Purpose
This document provides a step-by-step guide for binding a database instance to a subset of a server's CPUs and memory, using Solaris Resource Pools. Solaris Resource Pools provide a way to create a named set of CPUs and memory. A database that is associated with this Solaris Resource Pool can only use its CPUs and memory.
Using Solaris Resource Pools, a DBA that is consolidating multiple database instances on a single server can
- Physically isolate database instances onto different CPUs
- Bind database instances to specific NUMA nodes to improve performance on NUMA-based systems.
Scope
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| Step 1 - Configuring the Solaris Resource Pool |
| Step 2 - Configuring the Database |
| Best Practices |
| Solaris Resource Pools vs Zones |
| Support and Recommended Bug Fixes |
| References |