First off, I’ll be setting up page, where I intend to have a complete list of parameters used in all roles and a description of what they actually do. Up until now I’ve kept it in a file in the github repo, but I think it will be easier to maintain this way. The page is empty at the moment but I’ll try add to it as soon as possible
Now, this is the 3rd post on how to get started with ansible-oracle. You can find the other 2 posts here and here.
This time we will perform a RAC installation, and we will also introduce a few other options we haven’t explored before (mostly because they got added recently).
We will be introducing a concept known as GI role separation which means that the user grid will own the Grid Installation including ASM, and the user oracle will own the database installation.
The default is false, meaning the user oracle will own/run everything (well, except for the parts that run as root then).
We will be creating a container database including 2 pluggable databases
The installation will be performed over nfs this time, using a central repository where all the media is located, instead of copying the files to the installation hosts.
So in summary, this is what we will try to accomplish:
- Use group_vars & host_vars to alter the default values.
- Do the installation over nfs
- Setup RAC using role separation
- Create a container database with 2 pluggable databases
So, I’ve been adding support for GI role separation to the roles so that is why it has taken so long to get this post out.
In the last post we created a single instance database with database storage on a filesystem. This time we’re going to take it a step further and create a single instance database, but now we’re going to use ASM for storage. This means we also have to install the Grid Infrastructure in a stand alone configuration, so we’re adding a few other roles to the playbook.
We’re also going to deploy this configuration on 2 machines in parallel (oradb01, oradb02).
We’re also going to deviate from the default ‘role configuration’, i.e not relying entirely on variable values in defaults/main.yml. You could of course change the default so they more suit your needs and just rely on the defaults, but that limits your options (unless you only have one system to deal with).
The easiest way to override the defaults is to ‘move’ the parameters to a higher priority location, i.e group_vars or host_vars. In this example we’re going to put our ‘host-group’ specifics in group_vars.
So what do I mean by specifics?
- Storage config (storage devices for filesystems. This time, we’re going to put /u01 on its own device instead of the ‘root’-device)
- Storage config (storage devices for ASM)
- We’re going to call the database something else.
- We may want to install a different versions of GI (or DB). So, this time we’re going to install 126.96.36.199 GI and a 188.8.131.52 database
This is where everything will be installed:
- GI – /u01/app/oracle/184.108.40.206/grid
- DB – /u01/app/oracle/220.127.116.11/myhomeasm
I thought I’d write a quick post on how to get started with ansible-oracle.
The reason I decided to use roles when putting this together was to make it easily reusable, and to be able to pick and choose which roles you want to use. If you want to do everything from the ground up you can, and also if you already have a properly configured server and just want to install Oracle and create a single instance database on a filesystem you can absolutely do just that, by using just the oraswdb-install and oradb-create roles.
So, we’re going to do both. And we’re just going to go with the defaults and create a single instance database with datafiles on a filesystem.
Note: The installation will be without a configured listener. I have not gotten around to fixing the listener issue with installations without GI.
1. Configuring the host + installing the database server & creating a database
First off, we’re going to take a newly installed machine and configure it from ground up.
- Oracle version 18.104.22.168
- ORACLE_HOME will be /u01/app/oracle/22.214.171.124/orcl
- One database will be created, ‘orcl’
- Datafiles/fra will reside in /u01/oradata & /u01/fra respectively. The u01 directory is created by Ansible and oradata + fra will be created by dbca
- The Oracle software (linuxamd64_12102_database_1of2.zip, linuxamd64_12102_database_2of2.zip) has been downloaded and the files are placed in /tmp on the control-machine.
And now, on to the good stuff.