Oracle Restart is an option to the award-winning Oracle Database Enterprise Edition. Oracle Restart is a feature introduced in Oracle 11gR2 that automatically restarts Oracle components, such as the database instance, listener, and Oracle ASM, after a failure or system reboot. It ensures that these components are started in the correct order and that they are managed by Oracle's High Availability Services (HAS). This enhances the availability of Oracle databases in a standalone server environment. Refer this documentation
For more information on Oracle Restart, refer to the Oracle Database Documentation.
Kubernetes provides essential infrastructure building blocks, including compute, storage, and networking resources, and exposes them as code for infrastructure automation. This approach enables rapid provisioning of multi-node topologies. Additionally, Kubernetes offers the StatefulSet workload API object—ideal for managing stateful applications such as Oracle Restart, Single Instance Oracle Databases, and other Oracle features or configurations that require persistent storage and stable network identities.
The Oracle Restart Controller in the Oracle Database Operator deploys Oracle databases as a StatefulSet within Kubernetes clusters, using the Oracle Restart Slim Image. The Oracle Restart Controller manages the typical lifecycle operations of an Oracle database in a Kubernetes environment, including deployment, monitoring, scaling, upgrades, and deletion, as illustrated below:
- Create Oracle Database
- Install and Configure Oracle Grid Infrastructure
- Install and Configure Oracle Database
- Create Persistent Storage, along with Statefulset
- Create Services
- Oracle Restart Instances Cleanup
To create an Oracle database, complete the steps in the following sections:
- Prerequisites for running Oracle Restart Controller
- Provisioning Oracle Restart database in a Oracle Kubernetes Engine Environment
- Connecting to Oracle Restart Database
- Known Issues
- Cleanup
- Debugging and Troubleshooting
Note Before proceeding to the next section, you must complete the instructions given in each section based on your enviornment.
IMPORTANT : You must make the changes specified in this section before you proceed to the next section.
To become familiar with Oracle Restart in containerized environments, review the this documentation before proceeding further
Prerequisites for running Oracle Restart Controller
Deploy Oracle Restart Database YAML files using Kubernetes Cluster on your Oracle Kubernetes Engine Environment (OKE). There are multiple use case possible for deploying the Oracle Restart Database.
1. Provisioning an Oracle Restart Database
2. Provisioning an Oracle Restart Database with Security Contexts
3. Provisioning an Oracle Restart Database with NodePort Service
4. Provisioning an Oracle Restart Database with Load Balancer
5. Change Memory and CPU allocation for an earlier provisioned Oracle Restart Database
6. Change the size of Software Storage Location for an existing Oracle Restart Database
7. Provisioning an Oracle Restart Database with Custom Storage Class
8. Provisioning an Oracle Restart Database with RU Patch on FileSystem
9. Provisioning an Oracle Restart Database with RU Patch on Existing PVC
10. Provisioning an Oracle Restart Database with RU Patch and One Offs with Custom Storage Class
11. Provisioning an Oracle Restart Database with multiple diskgroups
12. Provisioning an Oracle Restart Database with multiple diskgroups with different redundancy
13. Provisioning an Oracle Restart Database with multiple diskgroups with different redundancy and option to specify separate storage class
14. Adding ASM Disks - Add ASM Disks to an existing Oracle Restart Database
15. Deleting ASM Disks - Delete ASM Disks from an existing Oracle Restart Database
16. Provisioning an Oracle Restart Database with Huge Page allocation
NOTE: Resizing of the ASM Disks is not allowed. You can add new ASM Disks to an exising Oracle Restart Database.
After the Oracle Restart database has been provisioned using the Oracle Restart Controller in Oracle Database Operator, you can follow the steps in this document to connect to the Oracle Restart Database: Database Connectivity
Refer to the Known Issues document for assistance related to issues deploying Oracle Restart Database using Oracle Restart Controller: Known Issues
Steps to clean up Oracle Restart Database deployed using Oracle Restart Controller in this document in Oracle Database Kubernetes Operator are documented in this page: Cleanup
To debug the Oracle Restart Database provisioned using the Oracle Restart Controller in Oracle Database Kubernetes Operator, follow this document: Debugging and troubleshooting