This section outlines the steps to protect Oracle Resources (non-PDB).
To protect Oracle resources, the data needs to be replicated across nodes using DataKeeper (unless shared storage or SAN devices are used).
The following table outlines the location of each piece.
|Oracle 19c (ORACLE_HOME)||/u01/app/oracle/product/19.3.0/dbhome_1|
|Database (SID: ORCL)||/datakeeper/oradata/ORCL|
As discussed earlier in How to Create Data Replication of a File System, this guide uses /datakeeper to replicate data between nodes. Therefore, the data on /datakeeper/oradata/ORCL is also replicated between nodes.
Please note that this guide uses computing resources with the following devices attached (Oracle resources require more space than other resources even for evaluation purposes).
|Boot Disk (such as /dev/sda/)||30 Gb|
|Data Disk (such as /dev/sdb/, configured and mounted at /datakeeper)||20 Gb|
Configure the Oracle Resource
The following table outlines the general steps to configure an Oracle Resource. The red ‘stacked disk’ shaped icons indicate a node that has Oracle Database instances at the time of each step. The grey ‘stacked disk’ icons indicate Oracle Databases that are not running.
Also, the grey “storage” icon indicates that the storage /datakeeper is not available for the node.
|Install Oracle 19c on both nodes|
|Create Oracle Database on Node-A
• Review How to Confirm if the Data Storage is Available on a Node. The data storage should be available on node-a.
• Create an Oracle Database on node-a
• Stop Oracle Instance on node-a
|Create Oracle Database on Node-B
• Switchover (the data storage) to node-b
• Rename /datakeeper/oradata/ORCL
• Create an Oracle Database on node-b
• Stop Oracle Instance on node-b
|Configure Oracle LISTENER on both nodes
• Switchover (the data storage) back to node-a
|Complete Configuration using LifeKeeper
• Start Database and Listener on node-a
• Configure resources on LifeKeeper
° Configure Oracle LISTENER Resource