Reference

Table of Contents

Classes

• ora_profile::client: This is a highly customizable Puppet profile class to define an Oracle client on your system.
• ora_profile::client::software: Installs the Oracle client software on your system.
• ora_profile::database: This is a highly customizable Puppet profile class to define an Oracle database on your system.
• ora_profile::database::asm_diskgroup: This class contains the code to create the ASM diskgroups.
• ora_profile::database::asm_init_params: This class configures initialization parameters for the ASM instance
• ora_profile::database::asm_listener: This class contains the definition of the Oracle listener process.
• ora_profile::database::asm_patches: This class contains the definition for the ASM patches.
• ora_profile::database::asm_setup: This class contains the code to install Oracle Grid Infrastructure.
• ora_profile::database::asm_software: This class contains the code to install Oracle Grid Infrastructure.
• ora_profile::database::asm_storage: This class sets up the storage for usage by ASM.
• ora_profile::database::asm_storage::afd_label: A short summary of the purpose of this class
• ora_profile::database::asm_storage::asmlib: This class configures ASMLib devices.
• ora_profile::database::asm_storage::nfs: This class will create the specified mountpoint and mount the nfs share there.
• ora_profile::database::asm_storage::udev: This class will apply udev rules to specified disk devices.
• ora_profile::database::cis_controls: This class contains the actual code secureing the database.
• ora_profile::database::common: This class contains common variables used by more then one class.
• ora_profile::database::db_definition: This class contains the actual database definition using the ora_database type.
• ora_profile::database::db_definition_template: This class contains the actual database definition using the ora_install::database class.
• ora_profile::database::db_init_params: This class configures initialization parameters for the databases instance(s)
• ora_profile::database::db_listener: This class contains the definition of the Oracle listener process.
• ora_profile::database::db_monitoring: This class contains the definition of the db monitoring facility to install.
• ora_profile::database::db_patches: This class contains the definition for the Oracle patches.
• ora_profile::database::db_profiles: This class contains the definition for all Oracle profiles you'd like on your system.
• ora_profile::database::db_services: This class contains the definition of all the database services you'd like on your system.
• ora_profile::database::db_software: This class contains the definition of the Oracle software you want to use on this system.
• ora_profile::database::db_startup: This class contains the definition for the auto startup of Oracle after a system reboot.
• ora_profile::database::db_tablespaces: This class contains the definition for all the tablespaces you'd like on your system.
• ora_profile::database::db_users: This class contains the definition for all the database users you'd like on your system.
• ora_profile::database::disable_thp: This class contains the definition of the Transparent HugePages settings required for running Oracle.
• ora_profile::database::em_license: This class will deploy the Enterprise Modules license.
• ora_profile::database::fact_caching: This class will enable Oracle fact caching, when enabled.
• ora_profile::database::firewall: This class contains the definition of the firewall settings you need for Oracle.
• ora_profile::database::firewall::firewalld: Open up ports for Oracle using the firewalld firewall
• ora_profile::database::firewall::iptables: Open up ports for Oracle using the iptables
• ora_profile::database::rac::authenticated_nodes: Setup authentication for the cluster nodes.
• ora_profile::database::rman_config: This class contains the definition for all the tablespaces you'd like on your system.
• ora_profile::database::tmpfiles: This class contains the definition all the required OS limit settings on your system.
• ora_profile::extracted_database: A short summary of the purpose of this defined type.
• ora_profile::oem_agent: This is a highly customizable Puppet profile class to define an Oracle Enterprise Manager installation on your system.
• ora_profile::oem_agent::software: Installs Oracle Enterprse Manager Agent.
• ora_profile::oem_server: This is a highly customizable Puppet profile class to define an Oracle Enterprise Manager installation on your system.
• ora_profile::oem_server::software: Installs Oracle Enterprse Manager.
• ora_profile::secured_database: This is a highly customizable Puppet profile class to define an Secured Oracle database on your system.

Defined types

• ora_profile::database::asm_storage::partition: This class adds partition table and partitions to specified device.
• ora_profile::database::authenticated_nodes::user_equivalence: Setup user equivalence for the specified user on specified nodes.
• ora_profile::database::rac::instance: Add Undo tablespace, Thread and init parameters for RAC instances

Functions

• set_param: See the file "LICENSE" for the full license governing this code. Returns the value for requested parameter. Currently supported parameters:

Classes

ora_profile::client

ora_profile::client

In it's core just adding:

contain ora_profile::client

Is enough to get an client installed on your system.

But sometimes you have specific uses cases that are not handled well by the standard classes. This profile class allows you to add your own code to the execution.

Stages

Defining an Oracle client on you system goes through several stages(These are not puppet stages):

• packages (Install all required packages)
• groups_and_users (Create required groups and users)
• software (Install the Oracle client software )

All these stages have a default implementation. This implementation is suitable to get started with. These classed all have parameters you can customize through hiera values. The defaults are specified in the module's data/default.yaml file.

before classes

But sometimes this is not enough and you would like to add some extra definitions, you can, for example, add a Puppet class to be executed after the packages stage is done and before the groups_and_users is started. You can do this by adding the next line to your yaml data:

ora_profile::client::before_groups_and_users:   my_profile::my_extra_class

after classes

You can do the same when you want to add code after one of the stage classes:

ora_profile::client::after_packages:   my_profile::my_extra_class

Skipping

Sometimes organisation use different modules and mechanisms to implement a feature and you want to skip the class:

ora_profile::client::packages:   skip

Replacing

Or provide your own implementation:

ora_profile::client::packages:   my_profile::my_own_implementation

This mechanism can be used for all named stages and makes it easy to move from an easy setup with a running standard database to a fully customized setup using a lot of your own classes plugged in.

Here is an example:

contain ::ora_profile::client

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::client class:

• before_em_license
• em_license
• after_em_license
• before_groups_and_users
• groups_and_users
• after_groups_and_users
• before_packages
• packages
• after_packages
• before_software
• software
• after_software

before_em_license

Data type: Optional[String]

The name of the class you want to execute directly before the em_license class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_em_license:  my_module::my_class

Default value: undef

em_license

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage em_license.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::em_license:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::em_license:  skip

Default value: undef

after_em_license

Data type: Optional[String]

The name of the class you want to execute directly after the em_license class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_em_license:  my_module::my_class

Default value: undef

before_groups_and_users

Data type: Optional[String]

The name of the class you want to execute directly before the groups_and_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_groups_and_users:  my_module::my_class

Default value: undef

groups_and_users

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage groups_and_users.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::groups_and_users:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::groups_and_users:  skip

Default value: undef

after_groups_and_users

Data type: Optional[String]

The name of the class you want to execute directly after the groups_and_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_groups_and_users:  my_module::my_class

Default value: undef

before_packages

Data type: Optional[String]

The name of the class you want to execute directly before the packages class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_packages:  my_module::my_class

Default value: undef

packages

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage packages.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::packages:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::packages:  skip

Default value: undef

after_packages

Data type: Optional[String]

The name of the class you want to execute directly after the packages class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_packages:  my_module::my_class

Default value: undef

before_software

Data type: Optional[String]

The name of the class you want to execute directly before the software class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_software:  my_module::my_class

Default value: undef

software

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage software.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::software:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::software:  skip

Default value: undef

after_software

Data type: Optional[String]

The name of the class you want to execute directly after the software class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_software:  my_module::my_class

Default value: undef

ora_profile::client::software

ora_profile::client::software

Using this classe you can install the Oracle client software on your system.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::client::software class:

• version
• file
• oracle_base
• oracle_home
• db_port
• user
• user_base_dir
• group
• group_install
• download_dir
• temp_dir
• install_type
• install_options
• puppet_download_mnt_point
• bash_profile
• ora_inventory_dir
• logoutput
• allow_insecure

version

Data type: Ora_install::Version

The version that is installed in the used Oracle home. Puppet uses this value to decide on version specific actions.

file

Data type: String[1]

The source file to use.

oracle_base

Data type: Stdlib::Absolutepath

The base directory to use for the Oracle installation. The default is : /u01/app/oracle To customize this consistently use the hiera key ora_profile::database::install_group.

oracle_home

Data type: Stdlib::Absolutepath

A directory to be used as Oracle home directory for this software.

db_port

Data type: Integer

The IP port to use for database communication. The default value is: 1521

user

Data type: String[1]

The user used for the specified installation. The install class will not create the user for you. You must do that yourself. The default value is: oracle

user_base_dir

Data type: Stdlib::Absolutepath

The directory to use as base directory for the users.

group

Data type: String[1]

The os group to use for these Oracle puppet definitions. The default value is: dba

group_install

Data type: String[1]

The os group to use for installation. The default value is: oinstall

download_dir

Data type: Stdlib::Absolutepath

The directory where the Puppet software puts all downloaded files. Before Puppet can actually use remote files, they must be downloaded first. Puppet uses this directory to put all files in. The default value is: /install

temp_dir

Data type: Stdlib::Absolutepath

Directory to use for temporary files.

install_type

Data type: Enum['Administrator', 'Runtime', 'InstantClient', 'Custom']

Which type of client software should be installed.

install_options

Data type: Optional[Array[String]]

List of Client Components you would like to install. This property is considered only if INSTALL_TYPE is set to "Custom"

puppet_download_mnt_point

Data type: Optional[String[1]]

The base path of all remote files for the defined type or class. The default value is: puppet:///modules/ora_install

bash_profile

Data type: Boolean

Create a bash profile for the specified user or not. Valid values are true and false. When you specify a true for the parameter, Puppet will create a standard bash profile for the specified user. The bash profile will be placed in a directory named user_base_dir/user.

ora_install::client { 'Oracle client':
  ...
  bash_profile  => true,
  user          => 'oracle',
  user_base_dir => '/home',
  ...
}

This snippet will create a bash profile called /home/oracle/.bash_profile.

ora_inventory_dir

Data type: Optional[Stdlib::Absolutepath]

The directory that contains the oracle inventory. The default value is: /oracle_base/oraInventory

logoutput

Data type: Variant[Boolean, Enum['on_failure']]

log the outputs of Puppet exec or not. When you specify true Puppet will log all output of exec types. Valid values are:

• true
• false
• on_failure

allow_insecure

Data type: Boolean

Allow insecure SSL connection for downloading the software.

ora_profile::database

ora_profile::database

In it's core just adding:

contain ::ora_profile::database

Is enough to get an Oracle 19c database running on your system.

But sometimes you have specific uses cases that are not handled well by the standard classes. This profile class allows you to add your own code to the execution.

Steps

Defining and starting an Oracle database on you system goes through several steps :

• em_license (Enable and load the Enterprise Modules license files)
• fact_caching (Enable Puppet fact caching for Oracle)
• sysctl (Set all required sysctl parameters)
• disable_thp (Disable Transparent HugePages)
• limits (Set all required OS limits)
• packages (Install all required packages)
• groups_and_users (Create required groups and users)
• firewall (Open required firewall rules)
• asm_storage (Setup storage for use with ASM (skipped by default))
• asm_software (Install Grid Infrastructure/ASM (skipped by default))
• asm_diskgroup (Define all requires ASM diskgroups (skipped by default))
• db_software (Install required Oracle database software)
• db_patches (Install specified Opatch version and install specified patches)
• db_definition (Define the database)
• db_listener (Start the Listener)
• db_services (Define Database Services)
• db_tablespaces (Define all required tablespaces)
• db_profiles (Define all required Oracle profiles)
• db_users (Define all required Oracle users)
• db_startup (Make sure the database restarts after a reboot)

All these steps have a default implementation. This implementation is suitable to get started with. These classed all have parameters you can customize through hiera values. The defaults are specified in the module's data/default.yaml file.

before classes

But sometimes this is not enough and you would like to add some extra definitions, you can, for example, add a Puppet class to be executed after the systctl stage is done and before the limits is done. You can do this by adding the next line to your yaml data:

ora_profile::database::before_sysctl:   my_profile::my_extra_class

after classes

You can do the same when you want to add code after one of the stage classes:

ora_profile::database::after_sysctl:   my_profile::my_extra_class

Skipping

Sometimes organisation use different modules and mechanisms to implement a feature and you want to skip the class:

ora_profile::database::sysctl:   skip

Replacing

Or provide your own implementation:

ora_profile::database::sysctl:   my_profile::my_own_implementation

This mechanism can be used for all named steps and makes it easy to move from an easy setup with a running standard database to a fully customized setup using a lot of your own classes plugged in.

Look at the description of the steps and their properties.

At this level you can also customize some generic settings. Check the settings for:

• version
• dbname
• os_user
• dba_group
• install_group
• source
• oracle_base
• oracle_home

Here is an example on how you can do this:

class {'ora_profile::database':
  dbname  => 'EM',
  source  => 'http://www.example.com/database_files',
  version => '11.2.0.3',
}

Also check the set of common parameters that is passed to this class.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::database class:

• storage
• version
• dbname
• os_user
• dba_group
• install_group
• grid_user
• grid_admingroup
• source
• oracle_base
• oracle_home
• ora_inventory_dir
• grid_base
• grid_home
• db_control_provider
• download_dir
• temp_dir
• oracle_user_password
• master_node
• cluster_nodes
• em_license
• fact_caching
• asm_sysctl
• asm_limits
• authenticated_nodes
• asm_groups_and_users
• asm_packages
• asm_listener
• sysctl
• disable_thp
• limits
• packages
• groups_and_users
• firewall
• tmpfiles
• asm_storage
• asm_software
• asm_patches
• asm_setup
• asm_init_params
• asm_diskgroup
• db_software
• db_patches
• db_definition
• rman_config
• db_listener
• db_monitoring
• db_init_params
• db_services
• db_tablespaces
• db_profiles
• db_users
• db_startup
• before_em_license
• before_fact_caching
• before_asm_sysctl
• before_asm_limits
• before_authenticated_nodes
• before_asm_groups_and_users
• before_asm_packages
• before_asm_listener
• before_sysctl
• before_disable_thp
• before_limits
• before_packages
• before_groups_and_users
• before_firewall
• before_tmpfiles
• before_asm_storage
• before_asm_software
• before_asm_patches
• before_asm_setup
• before_asm_init_params
• before_asm_diskgroup
• before_db_software
• before_db_patches
• before_db_definition
• before_rman_config
• before_db_listener
• before_db_monitoring
• before_db_init_params
• before_db_services
• before_db_tablespaces
• before_db_profiles
• before_db_users
• before_db_startup
• after_em_license
• after_fact_caching
• after_asm_sysctl
• after_asm_limits
• after_authenticated_nodes
• after_asm_groups_and_users
• after_asm_packages
• after_asm_listener
• after_sysctl
• after_disable_thp
• after_limits
• after_packages
• after_groups_and_users
• after_firewall
• after_tmpfiles
• after_asm_storage
• after_asm_software
• after_asm_patches
• after_asm_setup
• after_asm_init_params
• after_asm_diskgroup
• after_db_software
• after_db_patches
• after_db_definition
• after_rman_config
• after_db_listener
• after_db_monitoring
• after_db_init_params
• after_db_services
• after_db_tablespaces
• after_db_profiles
• after_db_users
• after_db_startup

storage

Data type: Enum['local', 'asm']

The type of storage used. The default is local

version

Data type: Ora_Install::Version

The version of Oracle you want to install. The default is : 19.0.0.0 To customize this consistently use the hiera key ora_profile::database::version.

dbname

Data type: String[1]

The name of the database. The default is DB01 To customize this consistently use the hiera key ora_profile::database::dbname.

os_user

Data type: String[1]

The OS user to use for Oracle install. The default is : oracle To customize this consistently use the hiera key ora_profile::database::os_user.

dba_group

Data type: String[1]

The group to use for Oracle DBA users. The default is : dba To customize this consistently use the hiera key ora_profile::database::dba_group.

install_group

Data type: String[1]

The group to use for Oracle install. The default is : oinstall To customize this consistently use the hiera key ora_profile::database::install_group.

grid_user

Data type: String[1]

The name of the user that owns the Grid Infrastructure installation. The default value is: grid.

grid_admingroup

Data type: String[1]

The OS group to use for ASM admin. The default value is: asmadmin

source

Data type: String[1]

The location where the classes can find the software. You can specify a local directory, a Puppet url or an http url. The default is : puppet:///modules/software/ To customize this consistently use the hiera key ora_profile::database::source.

oracle_base

Data type: Stdlib::Absolutepath

The base directory to use for the Oracle installation. The default is : /u01/app/oracle To customize this consistently use the hiera key ora_profile::database::install_group.

oracle_home

Data type: Stdlib::Absolutepath

The home directory to use for the Oracle installation. The default is : /u01/app/oracle/product/#{version}/db_home1 To customize this consistently use the hiera key ora_profile::database::oracle_home.

ora_inventory_dir

Data type: Stdlib::Absolutepath

The directory that contains the oracle inventory. The default value is: /oracle_base/oraInventory To customize this consistently use the hiera key ora_profile::database::ora_inventory_dir.

grid_base

Data type: Stdlib::Absolutepath

The ORACLE_BASE for the Grid Infrastructure installation. The default is : /u01/app/grid/admin To customize this consistently use the hiera key ora_profile::database::grid_base.

grid_home

Data type: Stdlib::Absolutepath

The oracle home directory to use for the GRID software. The default value is: /u01/app/grid/product/19.0.0.0/grid_home1

db_control_provider

Data type: String[1]

Which provider should be used for the type db_control. The default value is: sqlplus To customize this consistently use the hiera key ora_profile::database::db_control_provider.

download_dir

Data type: Stdlib::Absolutepath

The directory where the Puppet software puts all downloaded files. Before Puppet can actually use remote files, they must be downloaded first. Puppet uses this directory to put all files in. The default value is: /install To customize this consistently use the hiera key ora_profile::database::download_dir.

temp_dir

Data type: Stdlib::Absolutepath

Directory to use for temporary files.

oracle_user_password

Data type: Optional[String]

The password for the oracle os user. Only applicable for Windows systems. To customize this consistently use the hiera key ora_profile::database::oracle_user_password.

Default value: undef

master_node

Data type: Optional[String]

The first node in RAC. This is the node where the other nodes will clone the software installations from. To customize this consistently use the hiera key ora_profile::database::master_node.

Default value: $facts['networking']['hostname']

cluster_nodes

Data type: Optional[Array]

An array with cluster node names for RAC. Example:

ora_profile::database::cluster_nodes:
- node1
- node2

Default value: undef

em_license

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage em_license.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::em_license:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::em_license:  skip

Default value: undef

fact_caching

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage fact_caching.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::fact_caching:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::fact_caching:  skip

Default value: undef

asm_sysctl

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_sysctl.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_sysctl:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_sysctl:  skip

Default value: undef

asm_limits

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_limits.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_limits:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_limits:  skip

Default value: undef

authenticated_nodes

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage authenticated_nodes.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::authenticated_nodes:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::authenticated_nodes:  skip

Default value: undef

asm_groups_and_users

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_groups_and_users.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_groups_and_users:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_groups_and_users:  skip

Default value: undef

asm_packages

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_packages.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_packages:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_packages:  skip

Default value: undef

asm_listener

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_listener.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_listener:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_listener:  skip

Default value: undef

sysctl

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage sysctl.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::sysctl:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::sysctl:  skip

Default value: undef

disable_thp

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage disable_thp.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::disable_thp:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::disable_thp:  skip

Default value: undef

limits

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage limits.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::limits:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::limits:  skip

Default value: undef

packages

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage packages.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::packages:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::packages:  skip

Default value: undef

groups_and_users

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage groups_and_users.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::groups_and_users:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::groups_and_users:  skip

Default value: undef

firewall

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage firewall.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::firewall:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::firewall:  skip

Default value: undef

tmpfiles

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage tmpfiles.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::tmpfiles:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::tmpfiles:  skip

Default value: undef

asm_storage

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_storage.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_storage:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_storage:  skip

Default value: undef

asm_software

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_software.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_software:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_software:  skip

Default value: undef

asm_patches

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_patches.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_patches:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_patches:  skip

Default value: undef

asm_setup

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_setup.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_setup:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_setup:  skip

Default value: undef

asm_init_params

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_init_params.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_init_params:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_init_params:  skip

Default value: undef

asm_diskgroup

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage asm_diskgroup.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_diskgroup:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::asm_diskgroup:  skip

Default value: undef

db_software

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_software.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_software:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_software:  skip

Default value: undef

db_patches

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_patches.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_patches:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_patches:  skip

Default value: undef

db_definition

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_definition.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_definition:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_definition:  skip

Default value: undef

rman_config

Data type: Optional[String]

Use this value if you want to use your own class, skip or enable for stage rman_config.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::rman_config:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::rman_config:  skip

This is the default from the ora_profile module. To enable the rman configuration class define the variable as undef:

ora_profile::database::rman_config:  ~

Default value: undef

db_listener

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_listener.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_listener:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_listener:  skip

Default value: undef

db_monitoring

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_monitoring.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_monitoring:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_monitoring:  skip

Default value: undef

db_init_params

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_init_params.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_init_params:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_init_params:  skip

Default value: undef

db_services

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_services.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_services:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_services:  skip

Default value: undef

db_tablespaces

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_tablespaces.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_tablespaces:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_tablespaces:  skip

Default value: undef

db_profiles

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_profiles.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_profiles:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_profiles:  skip

Default value: undef

db_users

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_users.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_users:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_users:  skip

Default value: undef

db_startup

Data type: Optional[String]

Use this value if you want to skip or use your own class for stage db_startup.

Use your own class

You can use hiera to set this value. Here is an example:

ora_profile::database::db_startup:  my_module::my_class

Skip

You can use hiera to set this value. Here is an example:

ora_profile::database::db_startup:  skip

Default value: undef

before_em_license

Data type: Optional[String]

The name of the class you want to execute directly before the em_license class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_em_license:  my_module::my_class

Default value: undef

before_fact_caching

Data type: Optional[String]

The name of the class you want to execute directly before the fact_caching class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_fact_caching:  my_module::my_class

Default value: undef

before_asm_sysctl

Data type: Optional[String]

The name of the class you want to execute directly before the asm_sysctl class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_sysctl:  my_module::my_class

Default value: undef

before_asm_limits

Data type: Optional[String]

The name of the class you want to execute directly before the asm_limits class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_limits:  my_module::my_class

Default value: undef

before_authenticated_nodes

Data type: Optional[String]

The name of the class you want to execute directly before the authenticated_nodes class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_authenticated_nodes:  my_module::my_class

Default value: undef

before_asm_groups_and_users

Data type: Optional[String]

The name of the class you want to execute directly before the asm_groups_and_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_groups_and_users:  my_module::my_class

Default value: undef

before_asm_packages

Data type: Optional[String]

The name of the class you want to execute directly before the asm_packages class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_packages:  my_module::my_class

Default value: undef

before_asm_listener

Data type: Optional[String]

The name of the class you want to execute directly before the asm_listener class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_listener:  my_module::my_class

Default value: undef

before_sysctl

Data type: Optional[String]

The name of the class you want to execute directly before the sysctl class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_sysctl:  my_module::my_class

Default value: undef

before_disable_thp

Data type: Optional[String]

The name of the class you want to execute directly before the disable_thp class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_disable_thp:  my_module::my_class

Default value: undef

before_limits

Data type: Optional[String]

The name of the class you want to execute directly before the limits class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_limits:  my_module::my_class

Default value: undef

before_packages

Data type: Optional[String]

The name of the class you want to execute directly before the packages class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_packages:  my_module::my_class

Default value: undef

before_groups_and_users

Data type: Optional[String]

The name of the class you want to execute directly before the groups_and_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_groups_and_users:  my_module::my_class

Default value: undef

before_firewall

Data type: Optional[String]

The name of the class you want to execute directly before the firewall class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_firewall:  my_module::my_class

Default value: undef

before_tmpfiles

Data type: Optional[String]

The name of the class you want to execute directly before the tmpfiles class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_tmpfiles:  my_module::my_class

Default value: undef

before_asm_storage

Data type: Optional[String]

The name of the class you want to execute directly before the asm_storage class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_storage:  my_module::my_class

Default value: undef

before_asm_software

Data type: Optional[String]

The name of the class you want to execute directly before the asm_software class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_software:  my_module::my_class

Default value: undef

before_asm_patches

Data type: Optional[String]

The name of the class you want to execute directly before the asm_patches class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_patches:  my_module::my_class

Default value: undef

before_asm_setup

Data type: Optional[String]

The name of the class you want to execute directly before the asm_setup class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_setup:  my_module::my_class

Default value: undef

before_asm_init_params

Data type: Optional[String]

The name of the class you want to execute directly before the asm_init_params class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_init_params:  my_module::my_class

Default value: undef

before_asm_diskgroup

Data type: Optional[String]

The name of the class you want to execute directly before the asm_diskgroup class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_asm_diskgroup:  my_module::my_class

Default value: undef

before_db_software

Data type: Optional[String]

The name of the class you want to execute directly before the db_software class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_software:  my_module::my_class

Default value: undef

before_db_patches

Data type: Optional[String]

The name of the class you want to execute directly before the db_patches class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_patches:  my_module::my_class

Default value: undef

before_db_definition

Data type: Optional[String]

The name of the class you want to execute directly before the db_definition class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_definition:  my_module::my_class

Default value: undef

before_rman_config

Data type: Optional[String]

The name of the class you want to execute directly before the rman_config class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_rman_config:  my_module::my_class

Default value: undef

before_db_listener

Data type: Optional[String]

The name of the class you want to execute directly before the db_listener class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_listener:  my_module::my_class

Default value: undef

before_db_monitoring

Data type: Optional[String]

The name of the class you want to execute directly before the db_monitoring class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_monitoring:  my_module::my_class

Default value: undef

before_db_init_params

Data type: Optional[String]

The name of the class you want to execute directly before the db_init_params class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_init_params:  my_module::my_class

Default value: undef

before_db_services

Data type: Optional[String]

The name of the class you want to execute directly before the db_services class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_services:  my_module::my_class

Default value: undef

before_db_tablespaces

Data type: Optional[String]

The name of the class you want to execute directly before the db_tablespaces class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_tablespaces:  my_module::my_class

Default value: undef

before_db_profiles

Data type: Optional[String]

The name of the class you want to execute directly before the db_profiles class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_profiles:  my_module::my_class

Default value: undef

before_db_users

Data type: Optional[String]

The name of the class you want to execute directly before the db_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_users:  my_module::my_class

Default value: undef

before_db_startup

Data type: Optional[String]

The name of the class you want to execute directly before the db_startup class. You can use hiera to set this value. Here is an example:

ora_profile::database::before_db_startup:  my_module::my_class

Default value: undef

after_em_license

Data type: Optional[String]

The name of the class you want to execute directly after the em_license class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_em_license:  my_module::my_class

Default value: undef

after_fact_caching

Data type: Optional[String]

The name of the class you want to execute directly after the fact_caching class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_fact_caching:  my_module::my_class

Default value: undef

after_asm_sysctl

Data type: Optional[String]

The name of the class you want to execute directly after the asm_sysctl class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_sysctl:  my_module::my_class

Default value: undef

after_asm_limits

Data type: Optional[String]

The name of the class you want to execute directly after the asm_limits class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_limits:  my_module::my_class

Default value: undef

after_authenticated_nodes

Data type: Optional[String]

The name of the class you want to execute directly after the authenticated_nodes class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_authenticated_nodes:  my_module::my_class

Default value: undef

after_asm_groups_and_users

Data type: Optional[String]

The name of the class you want to execute directly after the asm_groups_and_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_groups_and_users:  my_module::my_class

Default value: undef

after_asm_packages

Data type: Optional[String]

The name of the class you want to execute directly after the asm_packages class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_packages:  my_module::my_class

Default value: undef

after_asm_listener

Data type: Optional[String]

The name of the class you want to execute directly after the asm_listener class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_listener:  my_module::my_class

Default value: undef

after_sysctl

Data type: Optional[String]

The name of the class you want to execute directly after the sysctl class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_sysctl:  my_module::my_class

Default value: undef

after_disable_thp

Data type: Optional[String]

The name of the class you want to execute directly after the disable_thp class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_disable_thp:  my_module::my_class

Default value: undef

after_limits

Data type: Optional[String]

The name of the class you want to execute directly after the limits class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_limits:  my_module::my_class

Default value: undef

after_packages

Data type: Optional[String]

The name of the class you want to execute directly after the packages class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_packages:  my_module::my_class

Default value: undef

after_groups_and_users

Data type: Optional[String]

The name of the class you want to execute directly after the groups_and_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_groups_and_users:  my_module::my_class

Default value: undef

after_firewall

Data type: Optional[String]

The name of the class you want to execute directly after the firewall class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_firewall:  my_module::my_class

Default value: undef

after_tmpfiles

Data type: Optional[String]

The name of the class you want to execute directly after the tmpfiles class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_tmpfiles:  my_module::my_class

Default value: undef

after_asm_storage

Data type: Optional[String]

The name of the class you want to execute directly after the asm_storage class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_storage:  my_module::my_class

Default value: undef

after_asm_software

Data type: Optional[String]

The name of the class you want to execute directly after the asm_software class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_software:  my_module::my_class

Default value: undef

after_asm_patches

Data type: Optional[String]

The name of the class you want to execute directly after the asm_patches class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_patches:  my_module::my_class

Default value: undef

after_asm_setup

Data type: Optional[String]

The name of the class you want to execute directly after the asm_setup class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_setup:  my_module::my_class

Default value: undef

after_asm_init_params

Data type: Optional[String]

The name of the class you want to execute directly after the asm_init_params class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_init_params:  my_module::my_class

Default value: undef

after_asm_diskgroup

Data type: Optional[String]

The name of the class you want to execute directly after the asm_diskgroup class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_asm_diskgroup:  my_module::my_class

Default value: undef

after_db_software

Data type: Optional[String]

The name of the class you want to execute directly after the db_software class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_software:  my_module::my_class

Default value: undef

after_db_patches

Data type: Optional[String]

The name of the class you want to execute directly after the db_patches class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_patches:  my_module::my_class

Default value: undef

after_db_definition

Data type: Optional[String]

The name of the class you want to execute directly after the db_definition class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_definition:  my_module::my_class

Default value: undef

after_rman_config

Data type: Optional[String]

The name of the class you want to execute directly after the rman_config class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_rman_config:  my_module::my_class

Default value: undef

after_db_listener

Data type: Optional[String]

The name of the class you want to execute directly after the db_listener class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_listener:  my_module::my_class

Default value: undef

after_db_monitoring

Data type: Optional[String]

The name of the class you want to execute directly after the db_monitoring class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_monitoring:  my_module::my_class

Default value: undef

after_db_init_params

Data type: Optional[String]

The name of the class you want to execute directly after the db_init_params class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_init_params:  my_module::my_class

Default value: undef

after_db_services

Data type: Optional[String]

The name of the class you want to execute directly after the db_services class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_services:  my_module::my_class

Default value: undef

after_db_tablespaces

Data type: Optional[String]

The name of the class you want to execute directly after the db_tablespaces class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_tablespaces:  my_module::my_class

Default value: undef

after_db_profiles

Data type: Optional[String]

The name of the class you want to execute directly after the db_profiles class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_profiles:  my_module::my_class

Default value: undef

after_db_users

Data type: Optional[String]

The name of the class you want to execute directly after the db_users class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_users:  my_module::my_class

Default value: undef

after_db_startup

Data type: Optional[String]

The name of the class you want to execute directly after the db_startup class. You can use hiera to set this value. Here is an example:

ora_profile::database::after_db_startup:  my_module::my_class

Default value: undef

ora_profile::database::asm_diskgroup

ora_profile::database::asm_diskgroup

Here you can customize some of the attributes of your database.

When these customizations aren't enough, you can replace the class with your own class. See ora_profile::database for an explanation on how to do this.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::database::asm_diskgroup class:

• disks

disks

Data type: Hash

A hash with the diskgroups that will be created. The default value is:

ora_profile::database::asm_diskgroup::disks:
  DATA:
    disks:
    - diskname: 'DATA_0000'
      path: '/nfs_client/asm_sda_nfs_b1'
    - diskname: 'DATA_0001'
      path: '/nfs_client/asm_sda_nfs_b2'
  RECO:
    disks:
    - diskname: 'RECO_0000'
      path: '/nfs_client/asm_sda_nfs_b3'
    - diskname: 'RECO_0001'
      path: '/nfs_client/asm_sda_nfs_b4'

Default value: {}

ora_profile::database::asm_init_params

ora_profile::database::asm_init_params

When these customizations aren't enough, you can replace the class with your own class. See ora_profile::database for an explanation on how to do this.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::database::asm_init_params class:

• parameters

parameters

Data type: Hash

The Hash with parameters that need to be configured. You must specify a Hash of ora_init_param

ora_profile::database::asm_init_params::parameters:
  memory/asm_power_limit:
    ensure: present
    value: 1024
  spfile/asm_power_limit:
    ensure: present
    value: 1024

ora_profile::database::db_init_params::parameters:
  memory/archive_lag_target:
    ensure: present
    value: 1800
  spfile/archive_lag_target:
    ensure: present
    value: 1800

See: ora_init_params

Default value: {}

ora_profile::database::asm_listener

ora_profile::database::asm_listener

It installs the specified version of the SQL*net software and start's the listener.

When these customizations aren't enough, you can replace the class with your own class. See ora_profile::database for an explanation on how to do this.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::database::asm_listener class:

• oracle_home
• oracle_base
• sqlnet_version
• dbname

oracle_home

Data type: Stdlib::Absolutepath

The home directory to use for the Oracle installation. The default is : /u01/app/oracle/product/#{version}/db_home1 To customize this consistently use the hiera key ora_profile::database::oracle_home.

oracle_base

Data type: Stdlib::Absolutepath

The base directory to use for the Oracle installation. The default is : /u01/app/oracle To customize this consistently use the hiera key ora_profile::database::install_group.

sqlnet_version

Data type: Ora_install::ShortVersion

The SQLnet version to use. The default is: 19.0

dbname

Data type: String[1]

The name of the database. The default is DB01 To customize this consistently use the hiera key ora_profile::database::dbname.

ora_profile::database::asm_patches

ora_profile::database::asm_patches

It also contains the definition of the required Opatch version.

When these customizations aren't enough, you can replace the class with your own class. See ora_profile::database for an explanation on how to do this.

Also check the set of common parameters that is passed to this class.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::database::asm_patches class:

• level
• patch_file
• opversion
• patch_list
• logoutput

level

Data type: String[1]

The patch level the database or grid infrastructure should be patched to. Default value is: NONE Valid values depend on your database/grid version, but it should like like below:

• OCT2018RU
• JAN2019RU
• APR2019RU
• etc...

patch_file

Data type: String[1]

The file containing the required Opatch version. The default value is: p6880880_122010_Linux-x86-64

opversion

Data type: String[1]

The version of OPatch that is needed. If it is not installed, Puppet will install the specfied version. The default value is: 12.2.0.1.33

patch_list

Data type: Hash

The list of patches to apply. The default value is : {}

logoutput

Data type: Variant[Boolean, Enum['on_failure']]

log the outputs of Puppet exec or not. When you specify true Puppet will log all output of exec types. Valid values are:

• true
• false
• on_failure

Default value: lookup({ name => 'logoutput', default_value => 'on_failure' })

ora_profile::database::asm_setup

ora_profile::database::asm_setup

Here you can customize some of the attributes of your database.

When these customizations aren't enough, you can replace the class with your own class. See ora_profile::database for an explanation on how to do this.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::database::asm_setup class:

• version
• dirs
• file_name
• asm_sys_password
• disk_discovery_string
• asm_diskgroup
• asm_disks
• group
• oper_group
• asm_group
• configure_afd
• grid_type
• disk_redundancy
• bash_profile
• disks_failgroup_names
• cluster_name
• scan_name
• scan_port
• cluster_node_types
• network_interface_list
• storage_option

version

Data type: Ora_Install::Version

The version of Oracle you want to install. The default is : 19.0.0.0 To customize this consistently use the hiera key ora_profile::database::version.

dirs

Data type: Array[Stdlib::Absolutepath]

The directories to create as part of the setup. The default value is:

ora_profile::database::asm_setup::dirs:
- /u01
- /u01/app/grid
- /u01/app/grid/admin
- /u01/app/grid/product

file_name

Data type: String[1]

The file name containing the Oracle Grid Infrastructure software kit. The default is: linuxx64_12201_grid_home

asm_sys_password

Data type: Easy_type::Password

The sys password to use for ASM. The default is: Welcome01 To customize this consistently use the hiera key ora_profile::database::asm_software::asm_sys_password.

disk_discovery_string

Data type: String[1]

The disk discovery string for ASM. The default value is: /nfs_client/asm* To customize this consistently use the hiera key ora_profile::database::asm_software::disk_discovery_string.

asm_diskgroup

Data type: String[1]

The name of the ASM diskgroup to use. The default value is: DATA To customize this consistently use the hiera key ora_profile::database::asm_software::asm_diskgroup.

asm_disks

Data type: String[1]

List of disks to create a ASM DiskGroup. The default value is: /nfs_client/asm_sda_nfs_b1,/nfs_client/asm_sda_nfs_b2 To customize this consistently use the hiera key ora_profile::database::asm_software::asm_disks.

group

Data type: String[1]

The dba group for ASM. The default is : asmdba To customize this consistently use the hiera key ora_profile::database::asm_software::group.

oper_group

Data type: String[1]

The oper group for ASM. The default is : asmoper To customize this consistently use the hiera key ora_profile::database::asm_software::oper_group.

asm_group

Data type: String[1]

The admin group for ASM. The default is : asmadmin To customize this consistently use the hiera key ora_profile::database::asm_software::asm_group.

configure_afd

Data type: Boolean

Specify whether or not to configure ASM Filter Driver instead of ASMLib. The default value is: false To customize this consistently use the hiera key ora_profile::database::asm_software::configure_afd.

grid_type

Data type: Enum['CRS_CONFIG', 'HA_CONFIG', 'UPGRADE', 'CRS_SWONLY', 'HA_SWONLY']

The type of grid. Valid values are:

• HA_CONFIG
• CRS_CONFIG
• HA_SWONLY (versions > 11)
• UPGRADE
• CRS_SWONLY The default value is: HA_CONFIG To customize this consistently use the hiera key ora_profile::database::asm_software::grid_type.

disk_redundancy

Data type: Enum['EXTENDED', 'EXTERNAL', 'FLEX', 'HIGH', 'NORMAL']

The disk redundancy for the initial diskgroup to setup ASM. Valid values are:

• EXTENDED
• EXTERNAL
• FLEX
• HIGH
• NORMAL The default value is: EXTERNAL

bash_profile

Data type: Boolean

Whether or not to deploy bash_profile for $os_user or $grid_user The default is : true

disks_failgroup_names

Data type: Optional[String[1]]

A comma seperated list of device and failure group name. Valid values are:

• /dev/sdb,CRSFG1,/dev/sdc,CRSFG2,/dev/sdd,CRSFG3 (NORMAL redundancy)
• /dev/sdb,,/dev/sdc,,/dev/sdd,,/dev/sde, (EXTERNAL redundancy)
• /dev/sdb,CRSFG1,/dev/sdc,CRSFG2,/dev/sdd,CRSFG3,/dev/sde,CRSFG4,/dev/sdf,CRSFG5 (HIGH redundancy) The default value is: /nfs_client/asm_sda_nfs_b1,

cluster_name

Data type: Optional[String[1]]

The name of the cluster. The default value is: undef

scan_name

Data type: Optional[String[1]]

The hostname to use for the SCAN service. The default value is: undef

scan_port

Data type: Optional[Integer]

The IP portnumber to use for the SCAN service. The default value is: undef

cluster_node_types

Data type: Optional[String[1]]

The names of the nodes in the RAC cluster. Valid values are:

• node1:node1-vip,node2:node2-vip (version >= 11 <= 12.1)
• node1:node1-vip:HUB,node2:node2-vip:LEAF (version >= 12.1 Flex Cluster)
• node1,node2 (version = 12.2 Application Cluster)
• node1:node1-vip:HUB:site1,node2:node2-vip:HUB:site2 (version = 12.2 Extended Cluster) The default value is: undef

network_interface_list

Data type: Optional[String[1]]

The list of interfaces to use for RAC.The value should be a comma separated strings where each string is as shown belowInterfaceName:SubnetAddress:InterfaceTypewhere InterfaceType can be either "1", "2", "3", "4" or "5" (1 indicates public, 2 indicates private, 3 indicates the interface is not used, 4 indicates ASM and 5 indicates ASM & Private)The default value is: undef

storage_option

Data type: Optional[Enum['FLEX_ASM_STORAGE', 'CLIENT_ASM_STORAGE', 'LOCAL_ASM_STORAGE', 'FILE_SYSTEM_STORAGE', 'ASM_STORAGE']]

The type of storage to use. Valid values are:

• ASM_STORAGE (versions = 11)
• FILE_SYSTEM_STORAGE (versions <= 12.1)
• LOCAL_ASM_STORAGE (versions >= 12.1)
• CLIENT_ASM_STORAGE (versions >= 12.2)
• FLEX_ASM_STORAGE (versions >= 12.1) The default value is: undef

ora_profile::database::asm_software

ora_profile::database::asm_software

Here you can customize some of the attributes of your database.

When these customizations aren't enough, you can replace the class with your own class. See ora_profile::database for an explanation on how to do this.

See the file "LICENSE" for the full license governing this code.

Parameters

The following parameters are available in the ora_profile::database::asm_software class:

• version
• dirs
• file_name
• asm_sys_password
• disk_discovery_string
• asm_diskgroup
• asm_disks
• group
• oper_group
• asm_group
• configure_afd
• grid_type
• disk_redundancy
• install_task
• bash_profile
• bash_additions
• disks_failgroup_names
• cluster_name
• scan_name
• scan_port
• cluster_node_types
• network_interface_list
• storage_option

version

Data type: Ora_Install::Version

The version of Oracle Grid Infrastructure you want to install. The default is : 19.0.0.0 To customize this consistently use the hiera key ora_profile::database::asm_software::version.

dirs

Data type: Array[Stdlib::Absolutepath]

The directories to create as part of the installation. The default value is:

ora_profile::database::asm_software::dirs:
- /u01
- /u01/app/grid
- /u01/app/grid/admin
- /u01/app/grid/product

file_name

Data type: String[1]

The file name containing the Oracle Grid Infrastructure software kit. The default is: linuxx64_12201_grid_home

asm_sys_password

Data type: Easy_type::Password

The sys password to use for ASM. The default is: Welcome01 To customize this consistently use the hiera key ora_profile::database::asm_software::asm_sys_password.

disk_discovery_string

Data type: String[1]

The disk discovery string for ASM. The default value is: /nfs_client/asm* To customize this consistently use the hiera key ora_profile::database::asm_software::disk_discovery_string.

asm_diskgroup

Data type: String[1]

The name of the ASM diskgroup to use. The default value is: DATA To customize this consistently use the hiera key ora_profile::database::asm_software::asm_diskgroup.

asm_disks

Data type: String[1]

List of disks to create a ASM DiskGroup. The default value is: /nfs_client/asm_sda_nfs_b1,/nfs_client/asm_sda_nfs_b2 To customize this consistently use the hiera key ora_profile::database::asm_software::asm_disks.

group

Data type: String[1]

The dba group for ASM. The default is : asmdba To customize this consistently use the hiera key ora_profile::database::asm_software::group.

oper_group

Data type: String[1]

The oper group for ASM. The default is : asmoper To customize this consistently use the hiera key ora_profile::database::asm_software::oper_group.

asm_group

Data type: String[1]

The admin group for ASM. The default is : asmadmin To customize this consistently use the hiera key ora_profile::database::asm_software::asm_group.

configure_afd

Data type: Boolean

Specify whether or not to configure ASM Filter Driver instead of ASMLib. The default value is: false To customize this consistently use the hiera key ora_profile::database::asm_software::configure_afd.

grid_type

Data type: Enum['CRS_CONFIG', 'HA_CONFIG', 'UPGRADE', 'CRS_SWONLY', 'HA_SWONLY']

The type of grid. Valid values are:

• HA_CONFIG
• CRS_CONFIG
• HA_SWONLY (versions > 11)
• UPGRADE
• CRS_SWONLY The default value is: HA_CONFIG To customize this consistently use the hiera key ora_profile::database::asm_software::grid_type.

disk_redundancy

Data type: Enum['EXTENDED', 'EXTERNAL', 'FLEX', 'HIGH', 'NORMAL']

The disk redundancy for the initial diskgroup to setup ASM. Valid values are:

• EXTENDED
• EXTERNAL
• FLEX
• HIGH
• NORMAL The default value is: EXTERNAL

install_task

Data type: Enum['ALL', 'EXTRACT']

The installation task that should be executed.

bash_profile

Data type: Boolean

Whether or not to deploy bash_profile for $os_user or $grid_user The default is : true

bash_additions

Data type: String

The text to add at the end of the bash_profile. This parameter will only be used when you have specified true for the parameter bash_profile The default value is an empty string.

disks_failgroup_names

Data type: Optional[String[1]]

A comma seperated list of device and failure group name. Valid values are:

• /dev/sdb,CRSFG1,/dev/sdc,CRSFG2,/dev/sdd,CRSFG3 (NORMAL redundancy)
• /dev/sdb,,/dev/sdc,,/dev/sdd,,/dev/sde, (EXTERNAL redundancy)
• /dev/sdb,CRSFG1,/dev/sdc,CRSFG2,/dev/sdd,CRSFG3,/dev/sde,CRSFG4,/dev/sdf,CRSFG5 (HIGH redundancy) The default value is: /nfs_client/asm_sda_nfs_b1,

cluster_name

Data type: Optional[String[1]]

The name of the cluster. The default value is: undef

scan_name

Data type: Optional[String[1]]