Table of Contents

1. Overview
2. Experience the Power of Puppet for Oracle databases
3. License
4. Description - What the module does and why it is useful
5. Setup

• Requirements
• Installing the ora_config module

6. Usage - Configuration options and additional functionality
7. Reference - An under-the-hood peek at what the module is doing and how
8. Limitations - OS compatibility, etc.

Overview

This module allows you to configure and manage Oracle databases and Oracle ASM instances. It is part of our family of Puppet modules to install, manage and secure Oracle databases with Puppet. Besides the ora_config module, this family also contains:

• ora_install For installing an Oracle database and other database related Oracle products
• ora_cis To secure your databases according to the CIS benchmarks.
• ora_profile The ora_profile module allows an easy path from first simple installation to a fully customized Enterprise setup.

All of these modules support Oracle versions 11, 12, 18, 19 and 21.

Experience the Power of Puppet for Oracle databases

Managing the configuration of your Oracle databases can be hard. With Puppet at your side, you get super-powers when installing and managing Oracle Databases. If you want to play and experiment with this please take a look at our playgrounds.

Experience the Power of Puppet for IBM MQ

Installing IBM MQ software and managing your IBM MQ configuration can be hard. With Puppet at your side, you get super-powers when installing and managing IBM MQ. If you want to play and experiment with this please take a look at our playgrounds.

License

This is a commercially licensed module. But you can use the module on VirtualBox based development systems for FREE. You can request a FREE trial license here

Check the License for details.

Description

This module allows you to manage everything there is to manage in an Oracle database. For example you can manage: users, tablespaces and schemas and much more. The module contains the following types:

• ora_asm_directory
• ora_asm_diskgroup
• ora_asm_volume
• ora_database
• ora_directory
• ora_exec
• ora_init_param
• ora_listener
• ora_object_audit
• ora_object_grant
• ora_package
• ora_procedure
• ora_profile
• ora_record
• ora_role
• ora_scheduler_job
• ora_schema_definition
• ora_service
• ora_setting
• ora_statement_audit
• ora_synonym
• ora_tablespace
• ora_thread
• ora_trigger
• ora_user

Check here to see the full documentation for this module.

Setup

Requirements

The ora_config module requires:

• Puppet module enterprisemodules-easy_type installed.
• Puppet version 3.0 or higher. Can be Puppet Enterprise or Puppet Open Source
• Oracle 11 higher
• A valid Oracle license
• A valid Enterprise Modules license for usage.
• Runs on most Linux systems.
• Runs on Solaris
• Runs on Windows systems

Installing the ora_config module

To install these modules, you can use a Puppetfile

mod 'enterprisemodules/ora_config'               ,'3.7.x'

Then use ther10K to install the software.

You can also install the software using the puppet module command:

puppet module install enterprisemodules-ora_config

Usage

Building a total Oracle setup requires quite some work. To help you, we have built some examples. The repo contains a demonstration of a simple database installation.

Reference

Here you can find some more information regarding this puppet module:

• The ora_config documentation

Here are a related blog posts:

• How to ensure you only use Oracle features you paid for
• Oracle 12.2 support added to our Oracle modules
• Secure your Oracle Database
• Manage Oracle containers with Puppet
• Manage your oracle users with Puppet
• Reaching into your Oracle Database with Puppet
• Manage your Oracle database schemas with Puppet
• Managing your Oracle database size with Puppet
• Using Puppet to manage Oracle

Limitations

This module runs on Solaris, AIX, Windows and most Linux versions. It requires a puppet version higher than 4. Other configurations are no supported.

Reference

Table of Contents

Classes

• ora_config: ora_config See the file "LICENSE" for the full license governing this code.
• ora_config::clear_caches: This class contains the puppet code that implements the default facter cache invalidation rules.
• ora_config::fact_caching: This class ensure's that the ora_config facts that can be cached and are cached with the correct settings.

Resource types

• ora_asm_directory: This type allows you to manage your ASM Directories. Like the other Oracle types, it's not mandatory to specify a SID here. In that case it
• ora_asm_diskgroup: This type allows you to manage your ASM diskgroups. Like the other Oracle types, you must specify the SID. But for this type it must be the
• ora_asm_volume: This type allows you to manage ASM volumes. Here is an example on defining an ACFS volume: ora_asm_volume{diskgroup:my_volume@+ASM1":
• ora_audit_policy: This resource allows you to manage the Unified Audit policies. This Puppet type supports managing the next policy types: - privileges - role
• ora_autotask: This resource allows you to manage auto tasks in the (pluggable) database It allows you to enable/disable individual tasks (sql_tuning_advis
• ora_awr_settings: This resource allows you to manage AWR settings in an Oracle database. This type allows you to set retention, interval and topnsql or
• ora_database: This resource allows you to manage an Oracle Database. This type allows you to create a database. In one of it's simplest form: ora_dat
• ora_directory: This resource allows you to manage directory mappings from inside an Oracle database to a directory outside of the database. Here is an examp
• ora_exec: This type allows you run a specific SQL statement or an sql file on a specified instance sid. ora_exec{"drop table application_users@sid
• ora_feature_usage: This resource allows you to report on Database feature usage ora_feature_usage { '@': max_usage => 200, w
• ora_function: This resource allows you to manage PL/SQL functions in the Oracle database. ora_function { 'testuser.return_some_value': ensure =
• ora_home_option: This resource allows you to manage(enable/disable) options in an Oracle database home. ora_home_option { '/u01/app/oracle/product/12.1.0
• ora_init_param: This resource allows you to manage Oracle parameters. this type allows you to manage your init.ora parameters. You can manage your spfile
• ora_listener: This manages the oracle listener process. It makes sure the Oracle SQL*Net listener is running. ora_listener {'SID': ensure => '
• ora_object_audit: This type allows you to enable or disable auditing inside an Oracle Database. Here is an example to set auditing on the SYS.AUD$ table:
• ora_object_grant: This type allows you to grant users rights to specified database objects. To grant user SCOTT execute and debug rights on on the `sys.
• ora_package: This resource allows you to manage PL/SQL packages in the Oracle database. ora_package { 'testuser.pkg_manage_my_objects': ensure
• ora_procedure: This resource allows you to manage PL/SQL procedures in the Oracle database. ora_procedure { 'testuser.proc_manage_my_objects': en
• ora_profile: This resource allows you to manage a user profile in an Oracle database. Here is an example on how to use this: ora_profile { 'DEFAULT@
• ora_record: This resource allows you to manage a record in an Oracle database table. Use ora_record to make sure a record with a specified primary key e
• ora_rman_config: This type allows you to manage the RMAN configurration in an Oracle database ora_rman_config { 'SID': archivelog_deletion_policy
• ora_role: This type allows you to create or delete a role inside an Oracle Database. It recognises a limit part of the options that [CREATE ROLE](http
• ora_scheduler_job: This resource allows you to manage schedulaed jobs in the Oracle database. Here is an example on how to use this: ora_scheduler_job{'sys
• ora_schema_definition: This resource allows you to manage a schema definition. This includes all tables, indexes and other DDL that is needed for your application.
• ora_service: This resource allows you to manage a service in an Oracle database. It has support for serices on single instance databases, but also suppor
• ora_setting: This resource allows you to set the defaults for all other ora types. All ora types need a ora_setting definition. This is a pointer to a
• ora_statement_audit: This type allows you to enable or disable auditing inside an Oracle Database.
• ora_synonym: This resource allows you to manage a synonym an Oracle database. You can create both public synonyms or private synonyms. To create a public
• ora_tablespace: This type allows you to manage an Oracle tablespace. The datafile and num_datafiles properties are mutually exclusive. When specifying multip
• ora_thread: This resource allows you to manage threads in an Oracle database. This type allows you to enable a thread. Threads are used in Oracle RAC i
• ora_trigger: This resource allows you to manage PL/SQL packages in the Oracle database. ora_trigger { 'testuser.my_trigger': ensure => 'presen
• ora_user: This type allows you to manage a user inside an Oracle database. It recognises most of the options that [CREATE USER](https://docs.oracle.co
• ora_validation: This type allows you to validate the contents of your Oracle database. Here is an example on how you can use this: ora_validation { 'Ens

Functions

• ora_config::available_sids: See the file "LICENSE" for the full license governing this code. This function will return an array of all sids registered in the ora_settin
• ora_config::generated_password: See the file "LICENSE" for the full license governing this code.
• ora_config::is_cluster: See the file "LICENSE" for the full license governing this code. Function to fetch the fact ora_is_cluster and based on that information de
• ora_config::is_container_db: See the file "LICENSE" for the full license governing this code. Function to fetch the fact ora_is_container_db and based on that informati
• ora_config::is_pluggable_db: See the file "LICENSE" for the full license governing this code. Function to fetch the fact ora_is_pluggable_db and based on that informati
• ora_config::is_primary_db: See the file "LICENSE" for the full license governing this code. Function to fetch the fact ora_is_primary_db and based on that information
• ora_config::is_root_db: See the file "LICENSE" for the full license governing this code. Function to fetch the fact ora_is_root_db and based on that information de
• ora_config::is_seed_db: See the file "LICENSE" for the full license governing this code. Function to fetch the fact ora_is_seed_db and based on that information de
• ora_config::on_sid: See the file "LICENSE" for the full license governing this code.

Tasks

• extract: Extracts the current config from a source database in hiera settings
• extract_data_bu: Extracts the data from a database using rman backup
• extract_data_dp: Extracts the data from a database using datapump
• insert_data_bu: Restores a database from an rman backup
• insert_data_dp: Inserts the data from a database using datapump
• profile: Allows get the status, create or remove an Oracle profile
• role: Allows get the status, create or remove an Oracle role
• service: Allows get the status, create or remove an Oracle service
• sql: Allows you to execute arbitraryarbitary SQL and return the output as raw text or an array of values
• tablespace: Allows get the status, create or remove an Oracle tablespace
• user: Allows get the status, create or remove an Oracle user

Plans

• ora_config::extract: See the file "LICENSE" for the full license governing this code. ++--++ --++--
• ora_config::extract_as_node: See the file "LICENSE" for the full license governing this code. ++--++ --++--

Classes

ora_config

ora_config

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

ora_config::clear_caches

::clear_caches

Whenever a certain set of Puppet classes or defined types is applied, it will clear the facter caches for those facts that are implemented.

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

ora_config::fact_caching

::fact_caching

You can change all TTL settings for the facts if an other setting is more fitting for your setup.

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

Parameters

The following parameters are available in the ora_config::fact_caching class:

• enabled
• ora_asm_diskgroups_ttl
• ora_asm_running_ttl
• ora_asm_volumes_ttl
• ora_is_cluster_ttl
• ora_is_container_db_ttl
• ora_is_pluggable_db_ttl
• ora_is_primary_db_ttl
• ora_is_root_db_ttl
• ora_is_seed_db_ttl
• ora_version_ttl

enabled

Data type: Boolean

When set to true, this enables facter caching for the ora_install module facts. Beware that you need to have Facter version 4.1.0 or higher to enabled this. When you set this value to true, automatically TTL settings for most of the ora_install facts are set to a default value. For most installations, the default settings are fine. When you set this value to true, the facter setting force-dot-resolution is enabled. You have to ensure that all of your facts keep on working with this setting.

ora_asm_diskgroups_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_asm_diskgroups fact.

ora_asm_running_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_asm_running fact.

ora_asm_volumes_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_asm_volumes fact.

ora_is_cluster_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_is_cluster fact.

ora_is_container_db_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_is_container_db fact.

ora_is_pluggable_db_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_is_pluggable_db fact.

ora_is_primary_db_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_is_primary_db fact.

ora_is_root_db_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_is_root_db fact.

ora_is_seed_db_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_is_seed_db fact.

ora_version_ttl

Data type: Optional[String[1]]

The Time to Live for the ora_version fact.

Resource types

ora_asm_directory

This type allows you to manage your ASM Directories.

Like the other Oracle types, it's not mandatory to specify a SID here. In that case it will use the ora_setting entry for ASM with the default property set to true If you do specify a SID it must be an ASM sid. Most of the times, this is +ASM

ora_asm_directory {'+DATA/DIR/SUBDIR@+ASM':
  ensure          => 'present',
  path            => '+DATA/DIR/SUBDIR'
}

Properties

The following properties are available in the ora_asm_directory type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_asm_directory type.

• provider

provider

The specific backend to use for this ora_asm_directory resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_asm_diskgroup

This type allows you to manage your ASM diskgroups.

Like the other Oracle types, you must specify the SID. But for this type it must be the ASM sid. Most of the times, this is +ASM1

ora_asm_diskgroup {'REDO@+ASM1':
  ensure          => 'present',
  redundancy_type => 'normal',
  compat_asm      => '11.2.0.0.0',
  compat_rdbms    => '11.2.0.0.0',
  disks           => {
    'FAILGROUP1' => [
      { 'diskname' => 'REDOVOL1', 'path' => 'ORCL:REDOVOL1'}
    ],
    'FAILGROUP2' => [
      { 'diskname' => 'REDOVOL2', 'path' => 'ORCL:REDOVOL2'},
    ]
  }
}

Properties

The following properties are available in the ora_asm_diskgroup type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_asm_diskgroup type.

• provider

provider

The specific backend to use for this ora_asm_diskgroup resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_asm_volume

This type allows you to manage ASM volumes.

Here is an example on defining an ACFS volume:

ora_asm_volume{diskgroup:my_volume@+ASM1":
  size          => '10G',
}

Before you can issue this definition, the diskgroup must already exists.

Properties

The following properties are available in the ora_asm_volume type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_asm_volume type.

• provider

provider

The specific backend to use for this ora_asm_volume resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_audit_policy

This resource allows you to manage the Unified Audit policies. This Puppet type supports managing the next policy types:

• privileges
• roles
• actions (Anly standard actions)
• object (only partly)

Here is an example on how to use this:

ora_audit_policy { 'ORA_DATABASE_PARAMETER@TEST':
  ensure   => 'present',
  actions  => ['ALTER DATABASE', 'ALTER SYSTEM', 'CREATE SPFILE'],
}

Properties

The following properties are available in the ora_audit_policy type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_audit_policy type.

• provider

provider

The specific backend to use for this ora_audit_policy resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_autotask

This resource allows you to manage auto tasks in the (pluggable) database

It allows you to enable/disable individual tasks (sql_tuning_advisor, auto_optimizer_stats_collection, auto_space_advisor) or enable/disable all the auto tasks (auto_task)

ora_autotask { 'DBNAME': auto_optimizer_stats_collection => 'enabled', auto_space_advisor => 'enabled', auto_task => 'enabled', sql_tuning_advisor => 'enabled', }

Parameters

The following parameters are available in the ora_autotask type.

• provider

provider

The specific backend to use for this ora_autotask resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_awr_settings

This resource allows you to manage AWR settings in an Oracle database.

This type allows you to set retention, interval and topnsql

ora_awr_settings { 'DBNAME':
  retention     => 60,
  snap_interval => 8,
  topnsql       => 'DEFAULT',
}

This will set the default AWR settings for database 'DBNAME'

Parameters

The following parameters are available in the ora_awr_settings type.

• provider

provider

The specific backend to use for this ora_awr_settings resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_database

This resource allows you to manage an Oracle Database.

This type allows you to create a database. In one of it's simplest form:

ora_database{'oradb':
  ensure          => present,
  oracle_base     => '/opt/oracle',
  oracle_home     => '/opt/oracle/app/11.04',
  control_file    => 'reuse',
}

The ora_database type uses structured types for some of the parameters. Here is part of an example with some of these structured parameters filled in:

ora_database{'bert':
  logfile_groups => [
      {file_name => 'test1.log', size => '10M'},
      {file_name => 'test2.log', size => '10M'},
    ],
  ...
  default_tablespace => {
    name      => 'USERS',
    datafile  => {
      file_name  => 'users.dbs',
      size       => '1G',
      reuse      =>  true,
    },
    extent_management => {
      type          => 'local',
      autoallocate  => true,
    }
  },
  ...
  datafiles       => [
    {file_name   => 'file1.dbs', size => '1G', reuse => true},
    {file_name   => 'file2.dbs', size => '1G', reuse => true},
  ],
  ...
  default_temporary_tablespace => {
    name      => 'TEMP',
    type      => 'bigfile',
    tempfile  => {
      file_name  => 'tmp.dbs',
      size       => '1G',
      reuse      =>  true,
      autoextend => {
        next    => '10K',
        maxsize => 'unlimited',
      }
    },
    extent_management => {
      type          => 'local',
      uniform_size  => '1G',
    },
  },
  ....
  undo_tablespace   => {
    name      => 'UNDOTBS',
    type      => 'bigfile',
    datafile  => {
      file_name  => 'undo.dbs',
      size       => '1G',
      reuse      =>  true,
    }
  },
  ....
  sysaux_datafiles => [
    {file_name   => 'sysaux1.dbs', size => '1G', reuse => true},
    {file_name   => 'sysaux2.dbs', size => '1G', reuse => true},
  ]

Properties

The following properties are available in the ora_database type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_database type.

• provider

provider

The specific backend to use for this ora_database resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_directory

This resource allows you to manage directory mappings from inside an Oracle database to a directory outside of the database. Here is an example:

ora_directory { 'ORACLE_OCM_CONFIG_DIR2@test':
  ensure         => 'present',
  directory_path => '/opt/oracle/app/11.04/ccr/state',
}

Properties

The following properties are available in the ora_directory type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_directory type.

• provider

provider

The specific backend to use for this ora_directory resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_exec

This type allows you run a specific SQL statement or an sql file on a specified instance sid.

ora_exec{"drop table application_users@sid":
  username => 'app_user',
  password => 'password,'
}

This statement will execute the sql statement drop table application_users on the instance names instance.

You can use the unless parameter to only execute the statement in certain states. If the query specified in the unless parameter returns one or more records, the main statement is skipped.

ora_exec{ "create synonym ${user}.${synonym} for USER.${synonym}":
  unless  => "select * from all_synonyms where owner='${user}' and synonym_name='${synonym}'",
}

You can also execute a script.

ora_exec{"@/tmp/do_some_stuff.sql@sid":
  username  => 'app_user',
  password  => 'password,'
  logoutput => on_failure,  # can be true, false or on_failure
}

This statement will run the sqlscript /tmp/do_some_stuff.sql on the sid named sid. Use the unless parameter to just execute the script in certain situations.

When you don't specify the username and the password, the type will connect as sysdba.

Parameters

The following parameters are available in the ora_exec type.

• provider

provider

The specific backend to use for this ora_exec resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_feature_usage

This resource allows you to report on Database feature usage

ora_feature_usage { '<feature>@<database>':
  max_usage => 200,
  when_used => 'warning|error',
}

Managable features are:

- 'active_data_guard'
- 'advanced_analytics'
- 'advanced_compression'
- 'advanced_security'
- 'change_management_pack'
- 'configuration_management_pack_for_oracle_database'
- 'data_masking_pack'
- 'database_gateway'
- 'database_in-memory'
- 'database_vault'
- 'diagnostics_pack'
- 'exadata'
- 'goldengate'
- 'hw'
- 'label_security'
- 'multitenant'
- 'olap'
- 'partitioning'
- 'pillar_storage'
- 'provisioning_and_patch_automation_pack'
- 'provisioning_and_patch_automation_pack_for_database'
- 'rac_or_rac_one_node'
- 'real_application_clusters'
- 'real_application_clusters_one_node'
- 'real_application_testing'
- 'secure_backup'
- 'spatial_and_graph'
- 'tuning_pack'
- 'webLogic_server_management_pack_enterprise_edition'

Parameters

The following parameters are available in the ora_feature_usage type.

• provider

provider

The specific backend to use for this ora_feature_usage resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_function

This resource allows you to manage PL/SQL functions in the Oracle database.

ora_function { 'testuser.return_some_value':
  ensure  => 'present',
  source => '/vagrant/tests/function.sql',
}

This puppet definition ensures that the function testuser.return_some_value is available in the database and that its content matches the content defined in the specified source.

To decide if the function needs an update, the puppet type compares the content in the database, with the content in the source file. This comparison is done insenitive to case, white spacing and used quote's (the " or the ` ).

When you have specified report_errors => true (which is the default), the type will fail on PL/SQL compilation errors. functions with compilation errors do however end up in the database. On a second Puppet run the won't be updated. Puppet reports a warning these resources though?

Warning: function TESTUSER.RETURN_SOME_VALUE@test up-to-date, but contains 4 error(s).

Properties

The following properties are available in the ora_function type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_function type.

• provider

provider

The specific backend to use for this ora_function resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_home_option

This resource allows you to manage(enable/disable) options in an Oracle database home.

ora_home_option { '/u01/app/oracle/product/12.1.0/db_home1':
  datamining               => 'disabled',
  direct_nfs               => 'disabled',
  olap                     => 'disabled',
  partitioning             => 'disabled',
  real_application_testing => 'disabled',
}

Parameters

The following parameters are available in the ora_home_option type.

• provider

provider

The specific backend to use for this ora_home_option resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_init_param

This resource allows you to manage Oracle parameters.

this type allows you to manage your init.ora parameters. You can manage your spfile parameters and your memory parameters. First the easy variant where you want to change an spfile parameter on your current sid for your current sid.

ora_init_param{'SPFILE/PARAMETER':
  ensure  => present,
  value   => 'the_value'
}

To manage the same parameter only the in-memory one, use:

init_param{'MEMORY/PARAMETER':
  ensure  => present,
  value   => 'the_value'
}

If you are running RAC and need to specify a parameter for an other instance, you can specify the instance as well.

init_param{'MEMORY/PARAMETER:INSTANCE':
  ensure  => present,
  value   => 'the_value'
}

Having more then one sid running on your node and you want to specify the sid you want to use, use @SID at the end.

init_param{'MEMORY/PARAMETER:INSTANCE@SID':
  ensure  => present,
  value   => 'the_value'
}

Managing parameters of pluggable database is also supported. This behaves like regular databases.

init_param{'MEMORY/PARAMETER:INSTANCE@SID':
  ensure  => present,
  value   => 'the_value'
}

Properties

The following properties are available in the ora_init_param type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_init_param type.

• provider

provider

The specific backend to use for this ora_init_param resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_listener

This manages the oracle listener process.

It makes sure the Oracle SQL*Net listener is running.

ora_listener {'SID':
  ensure  => 'running',
  require => Exec['db_install_instance'],
}

The name of the resource MUST be the sid for which you want to start the listener, unless instance_name is specified.

Properties

The following properties are available in the ora_listener type.

ensure

Valid values: stopped, running, false, true

Aliases: "false"=>"stopped", "true"=>"running"

Whether a listener should be running.

This is a required property without any defaults.

Parameters

The following parameters are available in the ora_listener type.

• instance_name
• name
• provider

instance_name

The database instance name.

The instance_name parameter MUST be the sid for which you want to start the listener.

name

namevar

The sid of the listener to run.

provider

The specific backend to use for this ora_listener resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_object_audit

This type allows you to enable or disable auditing inside an Oracle Database.

Here is an example to set auditing on the SYS.AUD$ table:

ora_object_audit { 'SYS.AUD$@test':
  ensure            => 'present',
  alter_failure     => 'by_access',
  alter_success     => 'by_access',
  audit_failure     => 'by_access',
  audit_success     => 'by_access',
  comment_failure   => 'by_access',
  comment_success   => 'by_access',
  flashback_failure => 'by_access',
  flashback_success => 'by_access',
  grant_failure     => 'by_access',
  grant_success     => 'by_access',
  index_failure     => 'by_access',
  index_success     => 'by_access',
  insert_failure    => 'by_access',
  insert_success    => 'by_access',
  lock_failure      => 'by_access',
  lock_success      => 'by_access',
  rename_failure    => 'by_access',
  rename_success    => 'by_access',
  select_failure    => 'by_access',
  select_success    => 'by_access',
  update_failure    => 'by_access',
  update_success    => 'by_access',
}

Some audit options only apply to some types of database records. Specify only those options that apply to the object you want to audit.

Properties

The following properties are available in the ora_object_audit type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_object_audit type.

• provider

provider

The specific backend to use for this ora_object_audit resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_object_grant

This type allows you to grant users rights to specified database objects.

To grant user SCOTT execute and debug rights on on the sys.dbms_aqin packgage, you can use:

ora_object_grant{'SCOTT->sys.dbms_aqin@SID':
  permissions => ['execute', 'debug'],
}

If you want to make sure the user only has execute rights, use:

ora_object_grant{'OTHER_USER->sys.dbms_aqin@SID':
   permissions => ['execute'],
}

If you want to make sure no permissions are granted, you can use an empty array like this:

ora_object_grant{'OTHER_USER->sys.dbms_aqin':
   permissions => [],
}

Parameters

The following parameters are available in the ora_object_grant type.

• provider

provider

The specific backend to use for this ora_object_grant resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_package

This resource allows you to manage PL/SQL packages in the Oracle database.

ora_package { 'testuser.pkg_manage_my_objects':
  ensure  => 'present',
  source => '/vagrant/tests/package.sql',
}

This puppet definition ensures that the package testuser.pkg_manage_my_objects is available in the database and that its content matches the content defined in the specified source.

To decide if the package needs an update, the puppet type compares the content in the database, with the content in the source file. This comparison is done insenitive to case, white spacing and used quote's (the " or the ` ).

When you have specified report_errors => true (which is the default), the type will fail on PL/SQL compilation errors. Packages with compilation errors do however end up in the database. On a second Puppet run the won't be updated. Puppet reports a warning these resources though?

Warning: package TESTUSER.PKG_MANAGE_MY_OBJECTS@test up-to-date, but contains 4 error(s).

Properties

The following properties are available in the ora_package type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_package type.

• provider

provider

The specific backend to use for this ora_package resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_procedure

This resource allows you to manage PL/SQL procedures in the Oracle database.

ora_procedure { 'testuser.proc_manage_my_objects':
  ensure  => 'present',
  source => '/vagrant/tests/procedure.sql',
}

This puppet definition ensures that the procedure testuser.proc_manage_my_objects is available in the database and that its content matches the content defined in the specified source.

To decide if the procedure needs an update, the puppet type compares the content in the database, with the content in the source file. This comparison is done insenitive to case, white spacing and used quote's (the " or the ` ).

When you have specified report_errors => true (which is the default), the type will fail on PL/SQL compilation errors. procedures with compilation errors do however end up in the database. On a second Puppet run the won't be updated. Puppet reports a warning these resources though?

Warning: procedure TESTUSER.PROC_MANAGE_MY_OBJECTS@test up-to-date, but contains 4 error(s).

Properties

The following properties are available in the ora_procedure type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_procedure type.

• provider

provider

The specific backend to use for this ora_procedure resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_profile

This resource allows you to manage a user profile in an Oracle database.

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ensure                    => 'present',
  composite_limit           => 'UNLIMITED',
  connect_time              => 'UNLIMITED',
  cpu_per_call              => 'UNLIMITED',
  cpu_per_session           => 'UNLIMITED',
  failed_login_attempts     => '10',
  idle_time                 => 'UNLIMITED',
  logical_reads_per_call    => 'UNLIMITED',
  logical_reads_per_session => 'UNLIMITED',
  password_grace_time       => '7',
  password_life_time        => '180',
  password_lock_time        => '1',
  password_reuse_max        => 'UNLIMITED',
  password_reuse_time       => 'UNLIMITED',
  password_verify_function  => 'NULL',
  private_sga               => 'UNLIMITED',
  sessions_per_user         => 'UNLIMITED',
  inactive_account_time     => '120',
  container                 => 'ALL'
}

Parameters

The following parameters are available in the ora_profile type.

• provider

provider

The specific backend to use for this ora_profile resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_record

This resource allows you to manage a record in an Oracle database table.

Use ora_record to make sure a record with a specified primary key exists in the specified table. Here is an exaple:

ora_record{'set_external_service_name':
  ensure     => 'present',
  table_name => 'CONFIG_DATA',
  key_name   => 'CONFIG_ID',
  key_value  => 10,
  username   => 'ORACLE_USER',
  password   => 'verysecret',
  data       => {
    'CONFIG_NAME'  => 'service_name',
    'CONFIG_VALUE' => 'http://external.data-server.com',
    ...
  }
}

This Puppet code tells you that the table CONFIG_DATA from user ORACLE_USER must contain a record where the primary key CONFIG_ID is 10. If Puppet notices that this record doesn't exist, It will create the record and fill its data with the data specified in the data property. If Puppet sees that the key already exists, it does nothing. This code will make sure your database contains the record, but it will not ALWAYS set the data. This code is useful for example in use cases where there is a set of management screens to manage these settings. Puppet makes sure the setting exists, but will leave the settings as they are after the system is running and applications managers might have changed the values.

If you always want to make sure the record contains the specified data, use updated for the ensure property.

ora_record{'set_external_service_name':
  ensure     => 'updated',
  table_name => 'CONFIG_DATA',
  username   => 'ORACLE_USER',
  password   => 'verysecret',
  key_name   => 'CONFIG_ID',
  key_value  => 10,
  data       => {
    'CONFIG_NAME'  => 'service_name',
    'CONFIG_VALUE' => 'http://external.data-server.com',
    ...
  }
}

Now Puppet will not only check if the record exists, but it will also always make sure the specified columns contain the specified values. If there are columns you don't want to manage, then just leave them blank.

Parameters

The following parameters are available in the ora_record type.

• provider

provider

The specific backend to use for this ora_record resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_rman_config

This type allows you to manage the RMAN configurration in an Oracle database

orarman_config { 'SID': archivelog_deletion_policy => 'BACKED UP 1 TIMES TO DISK', controlfile_autobackup => 'ON', controlfile_autobackup_format_for_device_type_disk => 'SID%F', device_type_disk => 'PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET', maxsetsize => '1024G', }

Parameters

The following parameters are available in the ora_rman_config type.

• provider

provider

The specific backend to use for this ora_rman_config resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_role

This type allows you to create or delete a role inside an Oracle Database.

It recognises a limit part of the options that CREATE ROLE supports.

ora_role {'just_a_role@sid':
  ensure    => present,
}

You can also add grants to a role:

ora_role {'just_a_role@sid':
  ensure    => present,
  grants    => ['create session','create table'],
}

Properties

The following properties are available in the ora_role type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_role type.

• provider

provider

The specific backend to use for this ora_role resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_scheduler_job

This resource allows you to manage schedulaed jobs in the Oracle database. Here is an example on how to use this:

ora_scheduler_job{'sys.cleanup_audit_job@SID':
  ensure          => 'present',
  job_type        => 'PLSQL_BLOCK',
  job_action      => 'begin cleanup_audit; end;',
  start_date      => '18-10-2018 23:45:00',
  repeat_interval => 'FREQ=DAILY',
  comments        => 'Purge Audit Logs',
  enabled         => 'TRUE',
}

Properties

The following properties are available in the ora_scheduler_job type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_scheduler_job type.

• provider

provider

The specific backend to use for this ora_scheduler_job resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_schema_definition

This resource allows you to manage a schema definition. This includes all tables, indexes and other DDL that is needed for your application.

ora_schema_definition{'MYAPP':
    ensure      => '1.0.0',
    schema_name => 'MYAPP,
    password    => 'verysecret',
    source_path => '/opt/stage/myapp/sql',
}

In this example we tell Puppet, we need schema version 1.0.0 for MYAPP in the database. In layman's terms now the following things will happen:

• The Puppet type will log in to the database using username myapp and the very secret password and it will look at the version of the schema already available.
• If the current version is lower than the specified version, Puppet will execute the upgrade SQL scripts in the source path until the correct version is reached.
• If the current version is higher than the requested version, Puppet will execute the downgrade scripts until the requested version is reached.

Schema version?

What is this concept of a schema version? To administer the current version, Puppet uses a table called SCHEMA_VERSION. Here is the definition of this table:

CREATE TABLE schema_version
(  id                NUMBER
  ,application       VARCHAR2(255)
  ,version           VARCHAR2(255)
  ,description       VARCHAR2(255)
  ,installation_time TIMESTAMP(6)
);

Puppet uses this table to store the history of all schema versions applied. If the table doesn't exists, Puppet will create it for you. Using this information, Puppet can tell what the state of the current schema in the database is. Puppet creates this table for every single schema/user you manage. This means, you can have multiple schemas with different versions in your database.

What about these upgrade and downgrade scripts.

In order for Puppet to do it's magic, the upgrade and downgrade scripts, need to have specific names. Here is a listing of some upgrade scripts:

upgrades/0000_myapp_0.0.1_initial-schema.sql
upgrades/0001_myapp_0.0.2_add-user-table.sql
upgrades/0002_myapp_0.1.0_initial-release.sql

As you can see, all the file names have the following structure:

• a four-digit sequence number
• application name
• version number
• description

All fields are separated by an underscore. The upgrade scripts contain all SQL statements needed to upgrade the database schema to the desired state. In general upgrade scripts contain statements to create tables and indexes and add or remove columns, but you can also insert data into the lookup-tables or create database packages.

The downgrades directory contains scripts with the same names. The downgrade scripts contain the SQL statements needed to put the database in the state it was before. So if you add a column in an upgrade script, you'll have to remove this column in the downgrade script.

Parameters

The following parameters are available in the ora_schema_definition type.

• provider

provider

The specific backend to use for this ora_schema_definition resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_service

This resource allows you to manage a service in an Oracle database.

It has support for serices on single instance databases, but also supports creating services on a RAC cluster. Here is an example on setting a service on a RAC cluster.

ora_service { 'MYSERVICE.DEVELOPMENT.ORG@SID1':
  ensure              => 'present',
  aq_ha_notifications => 'false',
  clb_goal            => 'LONG',
  dtp                 => 'false',
  failover_delay      => '0',
  failover_method     => 'NONE',
  failover_retries    => '0',
  failover_type       => 'NONE',
  lb_advisory         => 'THROUGHPUT',
  management_policy   => 'AUTOMATIC',
  preferred_instances => ['O2DEVEL1'],
  server_pool         => ['O2DEVEL_STAM.DEVELOPMENT.ORG'],
  service_role        => 'PRIMARY',
  status              => 'running',
  taf_policy          => 'NONE',
}

On a single instance Oracle database, most of the above options are ignored. So a simple version of the manifest for such a database would be:

ora_service { 'MYSERVICE.DEVELOPMENT.ORG@SID1':
  ensure              => 'present',
}

ora_service doesn't manage the internal services created by Oracle.

Properties

The following properties are available in the ora_service type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_service type.

• provider

provider

The specific backend to use for this ora_service resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_setting

This resource allows you to set the defaults for all other ora types.

All ora types need a ora_setting definition. This is a pointer to a local or remote database. You need to create one for every local, remote or pluggable database you want to manage. When you don't provide a ora_setting identifier in the title of the oracle type then it will use default as identifier. The connect string is according to the EZCONNECT naming method.

Here is an example on how to create the default settings:

ora_setting { '<SID>':
  default        => true|false,
  user           => '<username>',
  password       => '<password>',
  syspriv        => 'sysdba|sysasm|sysoper|sysbackup|sysdg|syskm',
  oracle_home    => '<path>',
  connect_string => "[//]host[:port][/service_name][:server][/instance]",
  pluggable      => true|false,
}

If you want to manage a remote database, like for instance DB1. You will have to specify a local oracle_home from where sqlplus can be started. You use ora_setting like this:

ora_setting { 'DB1':
  default        => true,
  user           => 'sys',
  password       => 'password',
  syspriv        => 'sysdba',
  oracle_home    => '/opt/oracle/12.1.0.2/db',
  connect_string => '//host1:1522/DB1',
  pluggable      => false,
}

Parameters

The following parameters are available in the ora_setting type.

• provider

provider

The specific backend to use for this ora_setting resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_statement_audit

This type allows you to enable or disable auditing inside an Oracle Database.

Properties

The following properties are available in the ora_statement_audit type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_statement_audit type.

• provider

provider

The specific backend to use for this ora_statement_audit resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_synonym

This resource allows you to manage a synonym an Oracle database. You can create both public synonyms or private synonyms. To create a public synonym use:

ora_synonym { 'PUBLIC.SYNONYM_NAME@SID':
  ensure      => 'present',
  table_name  => 'TABLE_NAME',
  table_owner => 'TABLE_OWNER',
}

To create a private synonym, you'll have to specfy the owner in the title:

ora_synonym { 'OWNER.SYNONYM_NAME@SID':
  ensure      => 'present',
  table_name  => 'TABLE_NAME',
  table_owner => 'TABLE_OWNER',
}

Properties

The following properties are available in the ora_synonym type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_synonym type.

• provider

provider

The specific backend to use for this ora_synonym resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_tablespace

This type allows you to manage an Oracle tablespace. The datafile and num_datafiles properties are mutually exclusive. When specifying multiple datafiles(or num_datfiles > 1) all datafiles will get the same settings for size, autoextend, next and max_size.

It recognises most of the options that CREATE TABLESPACE supports.

ora_tablespace {'my_app_ts@sid':
  ensure                    => present,
  datafile                  => 'my_app_ts.dbf',
  size                      => 5G,
  logging                   => yes,
  autoextend                => on,
  next                      => 100M,
  max_size                  => 20G,
  extent_management         => local,
  segment_space_management  => auto,
  encryption                => 'AES256',
}

Tablespace with multiple datafiles:

ora_tablespace {'my_app_ts@sid':
  ensure                    => present,
  datafile                  => ['my_app_ts01.dbf', 'my_app_ts02.dbf'],
  size                      => 5G,
  logging                   => yes,
  autoextend                => on,
  next                      => 100M,
  max_size                  => 20G,
  extent_management         => local,
  segment_space_management  => auto,
  encryption                => 'AES256',
}

Tablespace with multiple datafiles using Oracle Managed Files:

ora_tablespace {'my_app_ts@sid':
  ensure                    => present,
  num_datafile              => 3,
  size                      => 5G,
  logging                   => yes,
  autoextend                => on,
  next                      => 100M,
  max_size                  => 20G,
  extent_management         => local,
  segment_space_management  => auto,
  encryption                => 'AES256',
}

You can also create an undo tablespace:

ora_tablespace {'my_undots_1@sid':
  ensure                    => present,
  contents                  => 'undo',
}

or a temporary tablespace:

tablespace {'my_temp_ts@sid':
  ensure                    => present,
  datafile                  => 'my_temp_ts.dbf',
  contents                  => 'temporary',
  size                      => 5G,
  autoextend                => on,
  next                      => 100M,
  max_size                  => 20G,
  extent_management         => local,
  segment_space_management  => auto,
}

Properties

The following properties are available in the ora_tablespace type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_tablespace type.

• provider

provider

The specific backend to use for this ora_tablespace resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_thread

This resource allows you to manage threads in an Oracle database.

This type allows you to enable a thread. Threads are used in Oracle RAC installations. This type is not very useful for regular use, but it is used in the Oracle RAC module.

ora_thread{"2@sid":
  ensure  => 'enabled',
}

This enables thread 2 on instance named sid

Parameters

The following parameters are available in the ora_thread type.

• provider

provider

The specific backend to use for this ora_thread resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_trigger

This resource allows you to manage PL/SQL packages in the Oracle database.

ora_trigger { 'testuser.my_trigger':
  ensure  => 'present',
  source => '/vagrant/tests/triger.sql',
}

This puppet definition ensures that the trigger testuser.my_trigger is available in the database and that its content matches the content defined in the specified source.

To decide if the package needs an update, the puppet type compares the content in the database, with the content in the source file. This comparison is done insenitive to case, white spacing and used quote's (the " or the ` ).

When you have specified report_errors => true (which is the default), the type will fail on PL/SQL compilation errors. Packages with compilation errors do however end up in the database. On a second Puppet run the won't be updated. Puppet reports a warning these resources though?

Warning: trigger TESTUSER.MY_TRIGGER@test up-to-date, but contains 4 error(s).

Properties

The following properties are available in the ora_trigger type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the ora_trigger type.

• provider

provider

The specific backend to use for this ora_trigger resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_user

This type allows you to manage a user inside an Oracle database.

It recognises most of the options that CREATE USER supports. Besides these options, you can also use this type to manage the grants and the quota's for this user.

ora_user{user_name@sid:
  temporary_tablespace      => temp,
  default_tablespace        => 'my_app_ts',
  password                  => 'verysecret',
  require                   => Ora_tablespace['my_app_ts'],
  grants                    => ['SELECT ANY TABLE', 'CONNECT', 'CREATE TABLE', 'CREATE TRIGGER'],
  quotas                    => {
                                  "my_app_ts"  => 'unlimited'
                                },
}

Parameters

The following parameters are available in the ora_user type.

• provider

provider

The specific backend to use for this ora_user resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

ora_validation

This type allows you to validate the contents of your Oracle database. Here is an example on how you can use this:

ora_validation { 'Ensure All Default Passwords Are Changed@CNTNR':
  check                   => "SELECT DISTINCT A.USERNAME FROM DBA_USERS_WITH_DEFPWD A, DBA_USERS B WHERE A.USERNAME = B.USERNAME  AND B.ACCOUNT_STATUS = 'OPEN'",
  expected_number_of_rows => 0,
  fail_message            => 'User %<username>s still has a default password.',
  report_as               => 'command',
  fail_command            => "/bin/send_to_montoring --node ${::fqdn} '%<messages>s'",
}

The Puppet statement executes a query on the database and report a warning when more the 0 records are found. It uses the returned records of the query to generate a good reading error or warning message.

Parameters

The following parameters are available in the ora_validation type.

• provider

provider

The specific backend to use for this ora_validation resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

Functions

ora_config::available_sids

Type: Ruby 4.x API

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

This function will return an array of all sids registered in the ora_settings file

ora_config::available_sids()

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

This function will return an array of all sids registered in the ora_settings file

Returns: Array

ora_config::generated_password

Type: Ruby 4.x API

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

ora_config::generated_password(Optional[Integer] $password_length)

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

Returns: String

password_length

Data type: Optional[Integer]

ora_config::is_cluster

Type: Ruby 4.x API

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

Function to fetch the fact ora_is_cluster and based on that information decide if the specified sid is a cluster e.g. RAC database or not.

ora_config::is_cluster(String $sid)

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

Function to fetch the fact ora_is_cluster and based on that information decide if the specified sid is a cluster e.g. RAC database or not.

Returns: Any

sid

Data type: String

ora_config::is_container_db

Type: Ruby 4.x API

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

Function to fetch the fact ora_is_container_db and based on that information decide if the specified sid is a container database or not.

ora_config::is_container_db(String $sid)

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

Function to fetch the fact ora_is_container_db and based on that information decide if the specified sid is a container database or not.

Returns: Any

sid

Data type: String

ora_config::is_pluggable_db

Type: Ruby 4.x API

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

Function to fetch the fact ora_is_pluggable_db and based on that information decide if the specified sid is a pluggable database or not.

ora_config::is_pluggable_db(String $sid)

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

Function to fetch the fact ora_is_pluggable_db and based on that information decide if the specified sid is a pluggable database or not.

Returns: Any

sid

Data type: String

ora_config::is_primary_db

Type: Ruby 4.x API

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

Function to fetch the fact ora_is_primary_db and based on that information decide if the specified sid is a container database or not.

ora_config::is_primary_db(String $sid)

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

Function to fetch the fact ora_is_primary_db and based on that information decide if the specified sid is a container database or not.

Returns: Any

sid

Data type: String

ora_config::is_root_db

Type: Ruby 4.x API

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

Function to fetch the fact ora_is_root_db and based on that information decide if the specified sid is a root database or not.

ora_config::is_root_db(String $sid)

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

Function to fetch the fact ora_is_root_db and based on that information decide if the specified sid is a root database or not.

Returns: Any

sid

Data type: String

ora_config::is_seed_db

Type: Ruby 4.x API

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

Function to fetch the fact ora_is_seed_db and based on that information decide if the specified sid is a seed database or not.

ora_config::is_seed_db(String $sid)

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

Function to fetch the fact ora_is_seed_db and based on that information decide if the specified sid is a seed database or not.

Returns: Any

sid

Data type: String

ora_config::on_sid

Type: Ruby 4.x API

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

ora_config::on_sid(Variant[Array, Undef] $values, String $select_sid)

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

Returns: Any

values

Data type: Variant[Array, Undef]

select_sid

Data type: String

Tasks

extract

Extracts the current config from a source database in hiera settings

Supports noop? false

Parameters

sid

Data type: String[1]

The SID of the database.

oracle_home

Data type: String[1]

The Oracle home this database is runing from.

os_user

Data type: String[1]

The os user Oracle is running under.

cdb

Data type: Boolean

Is the database a container database.

pluggable

Data type: Boolean

Is the database a pluggable database.

contained_by

Data type: String

If it is a pluggable the name of the container

system_password

Data type: Optional[String]

The SYSTEM password to be used for the exported database

sys_password

Data type: Optional[String]

The SYS password to be used for the exported database

os_user_password

Data type: Optional[String]

The OS password for the OS user (e.g. Oracle) to be used on the exported database

extract_data_bu

Extracts the data from a database using rman backup

Supports noop? false

Parameters

sid

Data type: String[1]

The SID of the database.

oracle_home

Data type: String[1]

The Oracle home this database is runing from.

os_user

Data type: String[1]

The os user Oracle is running under.

directory

Data type: String[1]

The directory where the backup should be written to

extract_data_dp

Extracts the data from a database using datapump

Supports noop? false

Parameters

sid

Data type: String[1]

The SID of the database.

oracle_home

Data type: String[1]

The Oracle home this database is runing from.

cdb

Data type: Boolean

Is the database a container database. NOT IMPLEMENTED YET

pluggable

Data type: Boolean

Is the database a pluggable database. NOT IMPLEMENTED YET

contained_by

Data type: String

If it is a pluggable the name of the container. NOT IMPLEMENTED YET

database_user

Data type: String

The database user used for the datapump export

database_user_password

Data type: String

The password of the 'database_user'

os_user

Data type: String[1]

The OS user used for the datapump export

directory

Data type: String[1]

The directory where the export file should be written to

schemas

Data type: Array

Array of schemas to be exported

insert_data_bu

Restores a database from an rman backup

Supports noop? false

Parameters

sid

Data type: String[1]

The SID of the database.

oracle_home

Data type: String[1]

The Oracle home this database is runing from.

oracle_base

Data type: String[1]

The Oracle base for this database.

os_user

Data type: String[1]

The os user Oracle is running under.

os_group

Data type: String[1]

The os group Oracle is running under.

directory

Data type: String[1]

The directory where the backup file should be read from

verbose

Data type: Optional[Enum['debug', 'info', 'notice', 'warning', 'err', 'alert', 'emerg', 'crit']]

The level of verbosity to use.

format

Data type: Optional[Enum['pretty','json']]

Format of the output.

insert_data_dp

Inserts the data from a database using datapump

Supports noop? false

Parameters

sid

Data type: String[1]

The SID of the database.

oracle_home

Data type: String[1]

The Oracle home this database is runing from.

cdb

Data type: Boolean

Is the database a container database. NOT IMPLEMENTED YET

pluggable

Data type: Boolean

Is the database a pluggable database. NOT IMPLEMENTED YET

contained_by

Data type: String

If it is a pluggable the name of the container. NOT IMPLEMENTED YET

database_user

Data type: String

The database user used for the datapump export

database_user_password

Data type: String

The password of the 'database_user'

os_user

Data type: String[1]

The OS user used for the datapump export

directory

Data type: String[1]

The directory where the import file is located

profile

Allows get the status, create or remove an Oracle profile

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

profile_name

Data type: Optional[String[1]]

The name of the Oracle profile to use.

properties

Data type: Optional[Hash]

The properties to use when create a Oracle profile

role

Allows get the status, create or remove an Oracle role

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

role_name

Data type: Optional[String[1]]

The name of the Oracle role to use.

properties

Data type: Optional[Hash]

The properties to use when create a Oracle role

service

Allows get the status, create or remove an Oracle service

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

service_name

Data type: Optional[String[1]]

The name of the Oracle service to use.

properties

Data type: Optional[Hash]

The properties to use when create a Oracle service

sql

Allows you to execute arbitraryarbitary SQL and return the output as raw text or an array of values

Supports noop? false

Parameters

sid

Data type: Optional[String[1]]

SID of the database to connect to

username

Data type: Optional[String[1]]

The Oracle username to use. When none is specfied, SYS will be used.

password

Data type: Optional[String[1]]

The password to use. Only valid when specifying an Oracle username

sql

Data type: String[1]

The SQL you want to execute

raw

Data type: Optional[Boolean]

When true, it returns the output as a raw string. When false, it returns the value as an array of values. Default valu is true

tablespace

Allows get the status, create or remove an Oracle tablespace

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

tablespace_name

Data type: Optional[String[1]]

The name of the Oracle tablespace to use.

properties

Data type: Optional[Hash]

The properties to use when create a Oracle tablespace

user

Allows get the status, create or remove an Oracle user

Supports noop? false

Parameters

action

Data type: Optional[Enum['list', 'status','create','remove']]

The action you want to execute

user_name

Data type: Optional[String[1]]

The name of the Oracle user to use.

properties

Data type: Optional[Hash]

The properties to use when create a Oracle user

Plans

ora_config::extract

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

++--++ --++--

Parameters

The following parameters are available in the ora_config::extract plan:

• target
• sid
• oracle_home
• output_file
• os_user
• cdb
• pluggable
• contained_by

target

Data type: TargetSpec

sid

Data type: String[1]

oracle_home

Data type: String[1]

output_file

Data type: String[1]

os_user

Data type: String[1]

Default value: 'oracle'

cdb

Data type: Boolean

Default value: false

pluggable

Data type: Boolean

Default value: false

contained_by

Data type: String

Default value: ''

ora_config::extract_as_node

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

++--++ --++--

Parameters

The following parameters are available in the ora_config::extract_as_node plan:

• target
• sid
• oracle_home
• output_file
• system_password
• sys_password
• os_user_password
• role
• patch_level
• version
• database_type
• os_user
• cdb
• pluggable
• contained_by

target

Data type: TargetSpec

sid

Data type: String[1]

oracle_home

Data type: String[1]

output_file

Data type: String[1]

system_password

Data type: Sensitive

sys_password

Data type: Sensitive

os_user_password

Data type: Sensitive

role

Data type: String[1]

Default value: 'ora_profile::extracted_database'

patch_level

Data type: String[1]

Default value: 'NONE'

version

Data type: String[1]

Default value: '19.0.0.0'

database_type

Data type: String[1]

Default value: 'EE'

os_user

Data type: String[1]

Default value: 'oracle'

cdb

Data type: Boolean

Default value: false

pluggable

Data type: Boolean

Default value: false

contained_by

Data type: String

Default value: ''

History

3.23.1

• [ora_user] Remove the default of false for schema_only property

3.23.0

• [core] Support for Puppet 8
• [ora_user] Add support for schema only users (#275)

3.22.3

• [ora_schema_definition] Allow spaces in title

3.22.2

• [release] Update stdlib dependency

3.22.1

• [ora_record] Fix idempotency issue on ensure => update

3.22.0

• [ora_record] Fix support for table with just one column
• [ora_schema_definition] Fix default value for parameters
• [ora_validation] Add skip and control parameters
• [core] Generate correct error when ora_settings.yaml is empty
• [ora_rman_config] Fix bug in channel property related to case (#273)

3.21.0

• [ora_validation] Initial implementation
• [ora_rman_config] Add new custom type

3.20.4

• [ora_database] Save database creation logs on failed run

3.20.3

• [ora_service] Add support for value auto on failover_restore and session_state

3.20.2

• [release] Fix dependency version on ora_install

3.20.1

• [ora_database] Remove requirement for upcase database names

3.20.0

• [release] Add support for AlmaLinux and Rocky

3.19.0

• [core] Add fact caching to ora_config

3.18.5

• [core] Prefer our own path above the available path when executing SQL
• [core] Don’t execute container check when Oracle is not running

3.18.4

• [core] Fix incidental ‘No lines in SQL buffer’ error

3.18.3

• [core] Change Filepath object in LOAD_PATH to String

3.18.2

• [core] Also detect ORA-03114 for daemon restart
• [ora_exec] No container checks on ASM instances
• [core] Add Oracle 21c to several use cases in different types
• [ora_exec] Handle shutdown command in ora_exec
• [core] Don't check for correct container on ASM instances

3.18.1

• [ora_service] Add warning when available_instances are unknown
• [core] Don't check for correct container on ASM instances
• [ora_home_options] Add ora_install as a dependency
• [ora_home_option] Add Oracle Advanced Analytics as

3.18.0

• [core] Add support for Oracle 21c database (#256)
• [doc] Updated docs and REFERENCE.md
• [ora_exec] Ensure daemon is connected to correct container

3.17.2

• [ora_role,ora_user] Fix mixing grants, granted and revoked properties
• [docs] Add Super powers link to playgrounds

3.17.1

• [ora_object_grant] Fix when the privs column contain many entries
• [ora_audit_policy] Fix when some of the policies contain many entries

3.17.0

• [ora_asm_volume] Add support for resizing
• [ora_role] Add read only property oracle_maintained and warn when changing such roles
• [ora_object_grant] More robust against errors
• [ora_user, ora_role] More sane check on specified grants and revokes
• [ora_object_audit] Fix delete and execute auditing. Also add data_type checking
• [ora_user] Add read only property oracle_maintained and warn when changing such users
• [ora_audit_policy] Fix issues when object auditing already exists
• [ora_audit_policy] Improve performance on index query
• [ora_procedure] Add support for heredocs using the content property
• [ora_package] Add support for heredocs using the content property
• [ora_function] Content property updated
• [ora_function] Add support for heredocs using the content property

3.16.1

• [ora_audit_policy] Fix idempotency issues
• [ora_audit_policy] Fix order and error when creating actions based policys
• [core] Fix redefinition messages on ruby 2.7 and higher

3.16.0

• [ora_init_param] Fix ‘No configuration found’ on initial run
• [ora_init_param] Fix spurious if statement casing warning
• [ora_audit_policy] Initial implementation
• [ora_profile] Add INACTIVE_ACCOUNT_TIME profile limit option
• [core] Use Oracle12 plus sql statements also for Oracle 19 and Oracle 20 (#237)
• [core] Don’t cache the open pdb’s (#236)
• [ora_init_parameter] Fix handling of pluggable databases
• [core] Only query container for pdb state after ensuring it is a pluggable
• [core] Skip not opened pluggable databases on index (#235)
• [ora_tablespace] Fail when setting property on wrong tablespace type (#232)
• [ora_user] Fix setting SYS passsword on versions of Oracle 19 higher then 19.4 (#233)

3.15.0

• [release] Add playgrounds to README
• [core] functions generated_password and available_sids updated to the new Puppet standard.

3.14.3

• [core] Fix ‘end of file reached’ error when oracle restarted during run
• [ora_autotask] Fix ORA-00972: identifier is too long

3.14.2

• [ora_init_param] Fix missing values with long names when using daemon
• [daemon] Add support for restarting after detecting disconnect from Oracle

3.14.1

• [release] cleaup content of package

3.14.0

• [ora_database] Fix removing stopped database & daemons running
• [ora_database] Acquire oracle_base from db parameter in on_destroy and fix database_properties bug
• [ora_init_param] Fix error when nil value found in database
• [ora_database] Make daemonized the default
• [ora_database] Change shell variable to template variable
• [core] Fix default SID detection

3.13.0

• [release] Add support for puppet 7 in metadata
• [ora_tablespace] Workaround listagg length limitation
• [tasks] Add tasks to export/backup/import/restore a database

3.12.3

• [ora_database] Handle OMF in ASM and FS in the same way

3.12.2

• [plans/extract_as_node] Make passwords mandatory

3.12.1

• [plans/extract_as_node] Fix password handling

3.12.0

• [ora_tablespace] Fix undefined method `downcase' for nil:NilClass for when not using OMF
• [extract_as_node] Initial implementation
• [ora_tablespace] Fix logging property on temp and undo tablespaces
• [ora_database] Change some parameters into readonly properties
• [ora_user] Fix SQL error when default roles is empty array
• [grants] Issue warning when using container on non container database
• [extract] Initial task and plan implementation to extract ALL oracle configuration
• [ora_database] Don’t show file_name in logfile_group when omf enabled
• [ora_tablespace] Don’t allo puppet resource to see data file name when omf enabled
• [ora_autotask] Add confinement

3.11.4

• [ora_object_grant/ora_tablespace] Apply fix to index 12 version of script too
• [ora_object_grant] Fix when used with max_string_size to "EXTENTED"
• [ora_tablespace] Fix when used with max_string_size to "EXTENTED"
• [directories] Remove the correct passwordfile
• [ora_exec] Recognise the a sensitive statement in notice on refresh

3.11.3

• [ora_listener] Add instance_name parameter
• [ora_user] Fix idempotency issue on password when user is SYS in Oracle 12 and higher
• [ora_awr_settings] Fix index on pluggables and RAC instances

3.11.2

• [ora_schema_definition] Fix second pass on database with empty connection_string in ora_settings (#194)

3.11.1

• [release] Fix stdlib dependency metadata

3.11.0

• [core] Fix undefined method error in rare cases
• [ora_home_option] Add Unified Auditing option
• [ora_awr_settings] Fix documentation bug (#189)
• [ora_autotask] Add custom type to manage autotasks
• [core] Set pause off
• [ora_database] Handle archivelog and flashback properties as group

3.10.0

• [release] Add support for RedHat 8 and remove support for RHEL 4 and 5
• [ora_database] Add flashback property (#185)
• [ora_awr_settings] Add ora_awr_settings custom type (#184)
• [ora_listener] Fix puppet resource methods

3.9.10

• [core] Fix default sid detection for Oracle RAC databases

3.9.9

• [release] Add free trial banner to README

3.9.8

• [ora_user] Fix data type of create_only
• [ora_user] Fix error handling on quota
• [ora_user] Fix error handling when integer value is passed to grants field
• [ora_record] Fix data type issues
• [ora_asm_volume] Allow flexible sizes and fix idempotency
• [ora_asm_diskgroup] Handle dismounted diskgroup state (#182)
• [settings] Empty connect_string implies local
• [ora_init_param] Fix idempotency when for_sid is equal to sid on SPFILE param
• [ora_database] Make autostart better idempotent
• [ora_init_param] Fix support for setting memory parameters for a different sid
• [mungers] Resource api excludes upcase munger
• [ora_service] Properly set the db and sid when calling srvctl
• [ora_init_param] No more checks on for_sid parameter when scope is memory
• [core] Handle invalid UTF8 characters in the sql output

3.9.7

• [ora_service] Lookup container for pdb's, take undef value into account and conditionally stop service

3.9.6

• [ora_service] Handle preferred_instances and available_instances as group
• [settings] Container database is also a 'normal' database

3.9.5

• [ora_scheduler_job] Fix when repeat_interval contains values with comma’s
• [ora_database] Bring spfile parameter in line with where we create the spfile
• [ora_tab] Conditionally add newline

3.9.4

• [ora_tablespace] Workaround for Puppet issue with external types
• [tasks::tablespace] Add support for new bolt version
• [tasks::sql] Add support for new bolt version
• [tasks::user] Add support for new bolt version
• [tasks::service] Add support for new bolt version
• [tasks::role] Add support for new bolt version
• [tasks::profile] Add support for new bolt version
• [information] Bring in line with facts (v$pdbs doesn't contain rootdb anymore in 19c)
• [ora_service] TAF failover delay and retries renamed in 19c
• [ora_service] status fix symbol compare + case insensitive search
• [ora_service] preferred_instances fix data_type
• [ora_database] catbundleapply doesn't exist anymore in 19c
• [ora_database] Run datapatch on container databases
• [ora_database] Cannot expire password on externally identified users
• [core] Use NLS_LANG=english to always use english
• [ora_object_grant] Fix ora_object_grant.permissions expects a String value, error
• [ora_exec] Fix data type for mark_as_error
• [core] unset TWO_TASK added (#170)

3.9.3

• [core] Fix when using NLS support for non-english language
• [ora_asm_diskgroup] Remove data_type since VALIDATION will handle it
• [ora_database] No more default for oracle_home

3.9.2

• [ora_database] Fix issue with switching logfiles in RAC environment

3.9.1

• [ora_asm_diskgroup] Less strict types for compat_* properties
• [ora_database] Remove global oracle_home method
• [ora_database] Fix pdb connect string generation when no domain specified
• [ora_database] Fix when database longer then 10 characters
• [ora_database] Fix data types for passwords
• [ora_database] Don’t use data type for sysaux_datafiles parameter
• [ora_database] Don’t use data type for datafiles parameter
• [ora_exec] revert the refresh message from debug to notice
• [core] Add compatible data type checks on older Puppet versions

3.9.0

• [ora_exec] Change refresh notice into debug message
• [ora_service] Change warning into debug message on non clustered services
• [core] Specify REAL data types for all properties and parameters
• [ora_database] Fix bug in logfile_groups

3.8.1

• [core] Don’t connect to pluggable when container not up
• [ora_database] Make contained_by a property
• [ora_database] Don’t fetch logfile_groups when database is down
• [ora_database] Make state better idempotent
• [ora_database] make autostart better idempotent
• [ora_database] Fix occasional Ora_setting redefine
• [ora_database] Don’t make a oratab entry for.a pluggable database

3.8.0

• [ora_database] Add overwrite parameter and check
• [core] Fix when ora_settings file is empty.
• [ora_user] quotas ignore dropped tablespaces

3.7.0

• [core] Add Windows support
• [ora_database] Fix logfile_groups when used with Puppet 6 and resource_api loaded

3.6.4

• [ora_settings] Fix manageing default instances

3.6.3

• [ora_user] Fix password creation when no current salt is available

3.6.2

• [ora_user] Fix type compare on crreate_only properties
• [core] Add support for Oracle 19 password hashing

3.6.1

• [ora_exec/ora_tablespace] Change info to debug messages
• [ora_database] Fix force_logging property with Puppet 6

3.6.0

• [ora_database] Fix idempotency on acrhivelog property on puppet 6 and higher
• [core] Add Oracle 19 support

3.5.3

• [ora_service] Correctly identify pluggable databases.

3.5.2

• [core] cotainer support is backwards compatible with Oracle 12.1 and Oracle 11
• [core] Add support for Regexp styrings in versioned queries

3.5.1

• [ora_job_scheduler] No default value for start_date property
• [ora_job_scheduler] Fix idempotency on enabled property

3.5.0

• [facts] Confine the ora_version fact to running Oracle database
• [ora_user] Add check for double values in common_granted_with_admin
• [core] Fix puppet6 compatibility issues
• [ora_object_grant] Fix wildcard permissions on container database
• [ora_schema_definition] Fix when running in container database
• [core] Fix symbol comparison
• [ora_object_grant] Fix container permissions
• [ora_object_grant] Fix updating with_grant_permission
• [ora_object_grant] Fix error in container processing
• [ora_role] Add support for container common grants
• [ora_user] Add support for container common grants
• [core] Add support for container common grants
• [ora_object_grant] Fix persmissions when used with container databases
• [ora_profile] Fix container property
• [ora_user] Fix container property

3.4.0

• [ora_user] Add support for raw_password property
• [core] Only fetch pluggable status when we are a container db
• [ora_service] Add support for services on pluggable databases
• [settings] Fix detection of pluggable databases
• [ora_service] Add support for plugable database services on cluster

3.3.2

• [core] unset TNS_ADMIN variable
• [ora_object_grant] Fix container property

3.3.1

• [ora_init_param] Fix data type issues
• [core] Allow pluggable databases without extra licence

3.3.0

• [core] Reintroduce the sqlplus daemon to decrease load on server
• [ora_init_param] Puppet version dependent value resources
• [ora_database] Report database name when using RAC
• [core] Allow pluggable databases without extra licence

3.2.5

• [ora_database] add format for name column
• [ora_database] Add datapatch to creation

3.2.4

• [information] database is falsely identified as being OMF enabled

3.2.3

• [ora_tablespace] Fix symbol issue
• [ora_tablespace] Multiple fixes string versus symbols compare
• [ora_init_param] Determine data type of the value
• [ora_database] handle situation where db_name differs from SID

3.2.2

• [ora_service] Fix mechnism for getting defaullt value for status

3.2.1

• ora_service] Fix invalid command when unkown instances are found #149
• [ora_service] Add support for managing status on standby modes

3.2.0

• [core] Skip windows systems until Windows support is adequate
• [functions] Add helper function to determine if instance is a RAC cluster
• [facts] Add ora_is_cluster fact to signal if node is RAC cluster node

3.1.0

• [ora_function] Initial implementation
• [ora_user] Signal error when any of the grants or revoke properies contains double values

3.0.2

• [ora_user] Fix small bug in quotas and add qcceptance tests
• [ora_user] Case insensitive compare of unlimited quotas value
• [ora_service] Fix state property
• [core] Add initial support for running on windows
• [core] Make settings file location different for windows

3.0.1

• [listener] Fix issue caused by using undefined Oracle home
• [acceptance] Start using Puppet 6 for automated acceptance
• [core] Use puppet 6 in development container

3.0.0

• [core] Add support for Puppet 6
• [core] Add unittests for Puppet6
• [core] Update summary text to include Oracle versions
• [ora_service] Fix bug where the services of all databases are created in each database when having multiple databases in one system

2.10.1

• [core] Fetch database role also on older Oracle versions
• [ora_exec] Fix report_errors behaviour

2.10.0

• [ora_schema_definition] Fixed empty up and downgrade & downgrades in general
• [ora_schema_defintion] Added acceptance tests
• [ora_trigger] Fix typo in to_get_raw_resources
• [core] Add support for standby databases
• [core] Use version from v$instance
• [ora_statement_audit] Fix documentation

2.9.0

• [core] Add support for Oracle 18 password hashes
• [ora_tablespace] Add Oracle18 support
• [ora_profile] Add Oracle18 support
• [ora_object_grant] Add Oracle 18 support

2.8.0

• [release] Update the README
• [feature] Add Oracle 18c to oracle12 provider

2.7.0

• [functions] Added easy functions for checking certain facts

2.6.8

• [core] Fix selection of default sid when used with ora_database creation

2.6.7

• [ora_database] Use the specfied oracle os_user for database creation
• [ora_service] Add 12.2 properties for Application Continuity/Transaction Guard
• [ora_service] Only skip unknown instances

2.6.6

• [ora_service] Change warning to info. Closes #139
• [ora_tablespace] Fix ignored unlimited max_size setting. Closes #138

2.6.5

• [core] Make support for Suse more explicit

2.6.4

• [ora_service] Fix missing -preferred option in srvctl cluster command on initial run
• [core] Don’t cache ora_settings information
• [core] Add debug messages to feature resolution
• [ora_object_grants] Fix issue on wildcard matching Oracle 11
• [ora_object_grant] guard against messages without called insync?
• [ora_scheduler_job] Add documentation

2.6.3

• [core] Fix error’s in detecting running Oracle

2.6.2

• [facts] Fix ASM running detection
• [ora_object_grant] Check syntax of object_name

2.6.1

• [core] Fix bug when fetching empty ora_init parameter

2.6.0

• [ora_object_grant] Implement wildcard objectgrant for new grants
• [core] Use egrep for finding processes
• [core] Added some more debugging
• [core] Add AIX support
• [ora_object_grant] Add support for wildcard tables
• [core] Moved support for multiple versions of aquery doen to the lowest level
• [core] Optimize memory usage and speed by using trimspool

2.5.2

• [ora_object_grant] Fixed performance
• [ora_service] Fix incorrect command and other bugfixes. Closes #126
• [ora_scheduler_job] bugfixes in on_create and templates

2.5.1

• [ora_user] Fix error when current password field in the database is NULL

2.5.0

• [core] loossen requirements for easy_type version
• [ora_scheduler_job] New type initial commit
• [ora_procedure] New type

2.3.24

• [core] Add longchuncksize value to all SQL executes
• [test] Update tested Puppet versions

2.3.23

• [core] Fix executing statements without parse
• [ora_record] Fix invalid invalid multibyte char
• [core] Add support for remote access
• Don't remove everything when there is a cluster error

2.3.22

• [tasks] Update the sql task to use more standard pattern for ruby loading
• [tasks] Update user task
• [tasks] Add tablespace task
• [tasks] Add service task
• [role] Add role task
• [tasks] Add profile task
• [develop] copy lib files to cache
• [core] Cleanup some old files

2.3.21

• [tasks] Remove task folder from the ignore list

2.3.20

• [tasks] Add taks sql and user
• [core] Add support for sql with no processing of the output
• [ora_database] Remove ruby 1.8.7 fix.
• [ora_database] Make check to add instance more specfic

2.3.19

• [ora_exec] Fix operation when using refreshonly

2.3.18

• [ora_exec] Fix when refreshonly is set to true
• [release] Fix link to license i readme
• [release] Fix module name in license text

2.3.17

• [release] Update License text

2.3.16

• [release] Add license text and commercial license text

2.3.16

• [core] Fix textual typo in many sources
• [ora_exec] Add onlyif parameter
• [ora_user] Set a better default password
• [docs] Update docs

2.3.15

• [README] Updated for publishing on the forge
• [ora_database][core] Fix incompatibility with ruby 1.8.7
• [core] Fix incompatibility with ruby 1.8.7

2.3.14

• [core] Fix detection of root database
• [ora_service] Persist services_names on regular databases

2.3.13

• [ora_database] Fix undefined Puppet::Type::Ora_setting

2.3.12

• [ora_database] Fix 'Attempt to redefine entity error'

2.3.11

• [ora_service] Fix warning "preferred_instances has no effect..."
• [ora_database] Only add instance for local node
• [ora_database] Manage properties for RAC databases
• [schemas] Handle Integer. Closes #116

27-07-2017 Version 2.3.10

• [core] Update easy_type dependency

27-07-2017 Version 2.3.9

• [ora_database] Fix logfile_groups when database does not (yet) runs.
• [ora_service] Add support for removing instanced from running service
• [ora_database] Set privileges on dbca directory correctly. Closes #113
• [ora_service] Fix default value that breaks first run
• [ora_tablespace] Fix validation that breaks first run
• [ora_database] Manage redologs
• [ora_service] Fix unit tests

14-06-2017 Version 2.3.8

• [ora_service] Make available instances default for preferred_instances
• [ora_tablespace] treat datafiles property like a parameter when OMF enabled
• [asm_facts] Only run these facts on a Linux system
• [ora_service[ Better error message on starting
• [ora_service] Fix changing preferred_instances

10-05-2017 Version 2.3.7

• [ora_database] manage state of database
• [ora_tablespace] Convert the other way as well for max_size unlimited
• [ora_tablespace] Fix puppet resource issue. Closes #106
• Fix bigfile issue and don't allow removing datafiles

21-04-2017 Version 2.3.6

• [ora_database] Fix error when using force_logging
• [ora_tablespace] Fix bugs and add spec tests
• [ora_tablespace] remove byebug gem
• [ora_tablespace] Add separate queries to index query
• [ora_feature_usage] show all features
• [ora_tablespace] Add support for multiple datafiles

10-03-2017 Version 2.3.5

• [ora_tablespace] Fix ruby 1.8.7 issue on encrypted tablespaces
• [core] Use timeout value specified
• [ora_service] Fix the check for db_domain when no dabase yet
• [ora_service] Fix spec
• [ora_service] Allow simple names when db_domain not set
• [ora_home_option] Add pathname for puppet server
• [ora_feature_usage] Add pathname for puppet server

10-03-2017 Version 2.3.4

• [ora_tablespace] Add support for encrypted tablespaces
• [ora_database] Don't remove directories when pluggable database creaetion fails Closes #97
• [ora_user] Fix double identified by issue. Closes #90
• [ora_database] Add default value for temporary_tablespace in template
• [ora_user] Fix bug related to current_hashed_password
• [ora_feature_usage] Add where clause
• [ora_feature_usage] Remove where condition and cleanup
• [ora_feature_usage] Add type
• [ora_home_option] Remove debug statements

28-02-2017 Version 2.3.3

• [ora_database] sqlplus variable sysPassword and systemPassword only set for container databases. Closes #96

28-02-2017 Version 2.3.2

• [core] Fix name clash on Hash
• [ora_home_options] Initial version
• [ora_trigger] Fix problems with triggers containing special characters
• [ora_init_param] Extract the hex_to_raw function from ora_init_param
• [ora_setting] Ensure correct loading on PE

08-02-2017 Version 2.3.1

• [ora_service] Fix Oracle12 provider
• [ora_tablespace] Fix unit tests
• [ora_profile] Fix spec
• [ora_tablespace] Fix next property
• [ora_asm_diskgroup] Fix properties
• [ora_asm_directory] Fix used sid parameter

30-01-2017 Version 2.3.0

• [ora_role] Add container property
• [ora_service] Add confinement to have Oracle running
• [ora_database] Always uppercase database names
• [ora_user] autorequire tablespaces in quotas
• [ora_user] Allow container based profiles
• [ora_profile] Allow container based profiles
• [core] Allow container based grants
• [core] Allow passwordless connect to normal and containers
• [ora_service] Remove default value for preferred_instances
• [ora_service] Add support for services in pluggable database
• [ora_service] Service name must be a full qualified name
• [ora_service] Only provide default for preferred_instances when cluster
• [facts] Make ASM facts compatible with older puppet versions
• [ora_database] Create oratab entry for pdb
• [ora_database] Fix connect string for pdb
• [ora_service] Make properties case-insensitive
• [core] Better handling of default sids for all database types
• [ora_database] Handle cluster databases
• [core] include path in all informational and warning messages
• [ora_database] Fix setting the default when only one database is present
• [ora_database] Fix archiving detection. And fix settings name when cluster
• [ora_service] Make casing of properties less strict
• [ora_service] Make it work in first run when Oracle will be installed
• [core] include resource name in warnings and info messages
• [ora_database] Allow modification of archive mode
• [ora_setting] Reset default on other entries when new default added
• [ora_database] Compatible for Oracle 11
• [core] Make grant_property ruby 1.8.7 compatible
• [core] Make settings ruby 1.8.7. compatible
• [information] Make information block Oracle 11 compatible
• [core] No permissions on /root for os_user
• [facts] Fix is_container_db fact
• [facts] Don’t allow the facts to import information into Object
• [ora_object_grant] Add container scope to sql statement
• [core] Use container only on Oracle12 versions
• [core] Fix containerdb information
• [ora_object_grant] Add container property
• [ora_profile] Used versioned statement for to_get_raw_resources
• [ora_user] Add the container property
• [ora_profile] Add support for container property
• [facts] Add plugable db facts
• [ora_database] Silently ignore archivelog, autostart and force_logging for pluggable databases
• [ora_database] Fix several issues with pluggable databases
• [facts] Add support for array and record facts. Also add support for asm, and mgmt facts
• [parser] Add functions generated_password and available_sids
• [ora_init_param] fix default for_sid implementation
• [ora_init_param] Fix default for_sid when SPFILE parameter
• [core] Add support for setting the os_user in the ora_settings
• [ora_init_param] Start using the new map_titles_to_attributes
• [core] Start using the new map_titles_to_attributes
• [providers] confine to work only when ora_settings.yaml is present
• [ora_asm_directory] Fix typo
• [core] Better error reporting when an error occurs in a command. Closes #76
• [core] No default for username
• [ora_role] Allow updates of roles
• [ora_object_grant] Fix typo in the documentation
• [ora_user] Better password generation
• [ora_settings] Display message after generate
• [core] Fix output logging in relation with error handling
• [ora_database] Remove sid as parameter
• [core] MAke adm_sid and sid namevars
• [ora_object_audit] Initial implementation
• [ora_statement_audit] Added intial implementation
• [ora_user] Remove default for profile
• [core] Fix issue when password is empty
• [ora_settings] Implement conversion utility
• [core] Implement output logging. Closes #87
• [ora_database] Generate random passwords and don't fail if they are not specified
• [ora_service] Fix creation of non-clustered service
• [ora_database] Make force logging manageable
• [ora_database] Make autostart manageable
• [ora_database] Call the perl from the ORACLE_HOME
• [ora_database] Added options parameter
• [ora_database] Made container database creation
• [ora_database] Add support for pluggable databases initial commit
• [ora_database] Fix file_name_convert in template
• [ora_database] Move to simple provider
• [ora_database] Manage ora_settings entry on create and destroy
• [ora_database] Fix logging for destroy operations
• [core] Fix database running detection
• [core] Fix variable expansion in sql command
• [ora_setting] Use the easy_type yaml_type as implementation.
• [ora_database] Create container database initial commit
• [core] Add default property and remove oracle_sid property
• [ora_database] Make ora_database manageable
• [core] Remove all references to oratab which moved to ora_setting or were not needed anymore
• [core] Refactor access to settings
• [core] Removed sysdba and added syspriv property to ora_setting and other stuff
• [ora_databae] Add pluggable property, true boolean properties and don't fail on invalid sid(for remote connections
• [ora_setttings] Initial implementation
• [ora_object_grant] Add support for grants with grant option
• [ora_role] Added support for grants_with_admin, granted_with_admin and revoked_with_admin
• [ora_user] Added support for grants_with_admin, granted_with_admin and revoked_with_admin
• [core] Added support for with_admin grants
• [ora_role] Added granted and revoked property
• [ora_user] Added granted and revoked property
• [ora_user] Added property revoked and granted
• [ora_service] Port to new easy_type
• [facts] Allow all sorts of structures facts
• [ora_service] Also include the last service
• [core] Remove some leftovers from command_builder
• [ora_asm_volume] use new easy_type features
• [ora_asm_diskgroup] use new easy_type features
• [ora_database] use new easy_type features
• [ora_trigger] use new easy_type features
• [ora_thread] use new easy_type features
• [ora_synonym] use new easy_type features
• [ora_service] use new easy_type features
• [ora_schema_definition] use new easy_type features
• [ora_record] use new easy_type features
• [ora_profile] use new easy_type features
• [ora_package] use new easy_type features
• [ora_object_grant] use new easy_type features
• [ora_directory] use new easy_type features
• [ora_init_param] use new easy_type features
• [ora_role] use new easy_type features
• [ora_asm_disk] Fix handling of unsorted entries
• [ora_asm_disk] Fix handling of unsorted entries
• [ora_tablespace] use new easy_type features
• [ora_service] Set default value to running
• [ora_service] Make the current instances the default for preferred_instances
• [ora_database] Add support for report_errors parameter
• [ora_service] Use features to decide on provider
• [core] Add Oracle11 and Oracle 12 features
• [ora_asm_volume] Fix usage of asm_sid
• [ora_asm_diskgroup] Fix usage of asm_sid
• [ora_service] Implementation of all cluster properties
• [ora_service] index shows all cluster properties
• [ora_service] Add support for all srvmgr properties
• [ora_service] Fix issue in detecting partly stopped services
• [ora_profile] Support K/M etc on private_sga property. Closes #74
• [ora_profile] Fix casing problem. Closes #75
• [ora_service] Add support for running property
• [ora_asm_diskgroup] Fix issue in ordering of disk_group
• [ora_exec] Trigger refresh always when no unless is specified
• [core] use base sid for determining autorequires
• [ora_init_param] Fix parameters with values containing , and other exotic characters
• [core] remove bare named elements on autorequire when sid is set
• [ora_trigger] Fix autorequire
• [ora_package] Fix autorequires
• [ora_trigger] Fix autorequires
• [ora_record] Fix autorequires
• [ora_schema_definition] Fix autorequires
• [ora_synonym] Fix autorequires
• [ora_object_grant] Fix autorequires
• [ora_exec] Fix autorequires
• [ora_user] Fix autorequires
• [core] Added ora_autorequire function for compex autorequires
• [ora_record] Fix documentation
• [ora_exec] Fixed respecting the unless parameter on refresh
• [ora_asm_diskgroup] Fix when removing multiple diskgroups
• [ora_asm_diskgroup] Fix when adding multiple diskgroups
• [ora_tablespace] Add support for resizing smallfile tablespaces
• [ora_asm_diskgroup] Fix multiple issues
• [ora_asm_disk] Add acceptance tests
• [core] Make vagrant development bxo same as acceptance test box
• [ora_user] Better implementation of the default_roles property
• [ora_user] Fix ordering issue on default_roles property
• [ora_user] Improved handling of default roles value ALL and NONE
• [ora_sql_schema_definition] Fix error because of non existing directory
• [core] Move validation of sid down in stack
• [ora_schema_definition] Add support for remote files in source_path
• [ora_asm_diskgroup] Fix ruby 1.8.7 problem
• [ora_schema_version] Add better documentation
• [ora_schema_definition] Add default empty value for parameters
• [ora_schema_definition] Better error message when file name syntax in incorrect.
• [ora_record] Add autorequire for user
• [ora_package] Add autorequire for user
• [ora_exec] Add autorequire for user
• [ora_database] Fixed problems in logfile_groups
• [ora_user] Fix missing quote in docs
• [ora_asm_diskgroup] Add update support

12-09-2016 Version 2.2.7

• [ora_database] Support Oracle Managed Files for log file groups

08-09-2016 Version 2.2.6

• [ora_database] Fix multifile fixed number log groups
• [docs] Update docs

07-09-2016 Version 2.2.5

• [ora_database] Add support for multiple log files per loggroup
• [ora_trigger] Add support for (non)editionable create scripts
• [ora_package] Add support for (non)editionable create scripts

26-08-2016 Version 2.2.4

• [ora_init_param] Update content quoting to latest version of easy_type
• [ora_exec] Add support for mark_as_error parameter,
• [ora_package] Add difference reporting on source
• [ora_package] Update the documentation
• [ora_trigger] Initial implementation

20-08-2016 Version 2.2.3

• [ora_init_param] Handle quites in the values
• [ora_package] Fix provider name
• [core] Add support to manage mgnt database
• [core] Fix all usage of template function
• [ora_package] Implemented error checking and updated the documentation
• [core] Add support for catching additional errors
• [ora_package] Use refactered sql routine with raw access
• [ora_package] Initial implementation
• [ora_schema_definition] Implement empty instances method
• [facts] Add generic setup for making your own facts
• [core] set all files modes to correct values
• [core[ Handle -MGMTDB database
• [docs] Added documetation for using non-standard os users

13-07-2016 Version 2.2.2

• [core] Add correct geppetto project file
• [ora_object_grant] Fix autorequire in ora_object_grant
• [core] Add geppetto project file
• [ora_tablespace] Fix managing properties of temporary tablespaces
• [ora_object_grant] If object name has a user, autorequire it
• [ora_object_grant] Add autorequire to grantee
• [ora_user] Fix error when quota is empty
• [ora_user] Fix error in multiple properties when just one change
• [ora_object_grant] Use a prefetching provider to spare memory

29-06-2016 Version 2.2.1

• [ora_user] Fix error when only grants change

28-06-2016 Version 2.2.0

• [core] Better checking on db sid
• [core] moved all shared properties to named directory
• [ora_asm_volume] Fix the index operation
• [ora_asm_disk_group] Fix index operation
• [ora_schema_definition] Fix error in creation sql
• [core] Load profile but reset path to wd of parent proces
• [ora_user] Fix when default_roles and grants are specified
• [ora_user] Add properties locked & expired
• [core] Don't load profile for oracle commands
• [core] Better error reporting on all sql
• [ora_synonym] Replace simple provider by prefetching one
• [ora_instance] Initial implementation
• [ora_synonym] First implementation
• [ora_directory] Initial implementation

26-05-2016 Version 2.1.0

• [ora_asm_diskgroup] Make sure the disks are in sync
• [ora_init_param] Fix when running in a RAC cluster
• [ora_user] fix default_roles property
• [ora_user] Make profile an uppercase property
• [ora_user] Remove user_id
• [core] Remove temporary files after we have used it.
• [ora_user] Add support for default_roles
• [ora_tablespace] Make size updates work with Oracle Managed Files
• [ora_user] Fix Puppet deprecation warning
• [ora_role] Fix Puppet deprecation warning
• [ora_profile] Fix Puppet deprecation warning
• [ora_object_grant] Fix Puppet deprecation warning
• [ora_init_param] Fix Puppet deprecation warning
• [ora_exec] Fix Puppet deprecation warning
• [ora_tablespace] Fix usage of oracle named files
• [ora_profile] Add new type to manage Oracle user profiles
• [ora_user] Added profile property
• [ora_schema_definition] Fix downgrade paths
• [ora_asm_diskgroup] Remove empty lines in create statement
• [ora_tablespace] Fix typo in help text
• [ora_asm_diskgroup] Use the au_size propery on creating the diskgroup
• [ora_user] Fix issue with default password
• [core] Adhere to puppetlabs guidelines for libraries
• [ora_user] Generate a radnom password for a user when password is not specified
• [core] Update used gems
• [core] Fix security issues with world readable files
• [ora_user] Make password a manageble property
• [ora_object_grants] Change resource name and added default permissions
• [ora_object_grant] Fix possible error on insync?. Closes #72
• [ora_object_permissions] Fix case sensitivity for permissions. Closes #71
• [ORA_RECORD] Updated documentation
• Improved documentation for several types
• [ORA_OBJECT_GRANT] renamed the type ora_object_permission to ora_object_grant
• [ORA_INIT_PARAM] Fix error in idempotence when value is a real number
• Some generic fixes
• Add support for modified_only acceptance tests
• [ORA_USER] Added checks for object_rights
• Removed the check for old sid syntax.
• [ORA_OBJECT_PERMISSION] Added type to manage object permissions
• [ORA_EXEC] Add support for ignoring SQLPlus errors
• Add better documentation
• Move acceptance tests over to Oracle 12C
• Update travis for Puppet 4.2.3
• Fix test versions
• [ORA_DATABASE] Fix test manifest
• ORA_TABLESPACE] Fix creation of temporary tablespaces
• [ORA_INIT_PARAM] Quote the parameter name
• [ORA_TABLESPACE]Fix autoextending and changing size
• Acceptance tests running in enterprisemodules context
• Add identity files
• Update of the Gems. This allows us to run rake acceptance again
• [ORA_TABLESPACE] Add support fot specifying block_size

30-10-2015 version 2.0.0.0

---

• Renamed to ora_config

27-10-2015 version 1.7.22

---

• Fix when using ora_init_param on multiple instances

27-10-2015 version 1.7.21

---

• Fix when using ora_init_param when one of the instances is a ASM instance

26-10-2015 version 1.7.20

---

• Fix when using ora_init_param on a node with multiple databases
• Fix when using ora_init_param without a specified database.

26-08-2015 version 1.7.19

---

• timeout parameter was not honoured. Now fixed

26-08-2015 version 1.7.18

---

• Fix undefined method sort for ora_init_param

25-08-2015 version 1.7.17

---

• Fix null quota's for ora_user.
• Fix idempotence for autoextend and maxsize

10-08-2015 version 1.7.16

---

• Added support for multiple values in ota_init_parameter

10-08-2015 version 1.7.15

---

• Allow letters in versionnumber of ora_racord upgrade and downgrade scripts

16-07-2015 version 1.7.14

---

• Set ownership for some more directories when creating a database

06-07-2015 version 1.7.13

---

• refreshonly on ora_exec now only logs a message when something is done.

06-07-2015 version 1.7.12

---

• Fix dropping triggers when reinstalling schema

01-07-2015 version 1.7.11

---

• Use instance name instead of database name for orapwd name.

19-06-2015 version 1.7.10

---

• only use lb_advisory on RAC clusters

17-06-2015 version 1.7.9

---

• added lb_advisory property to ora_service

17-06-2015 version 1.7.8

---

• Added refreshonly for ora_exec
• Check if the cwd specified for ora_exec is valid

09-06-2015 version 1.7.7

---

• Add support for timezone parameter on Ora_database

04-06-2015 version 1.7.6

---

• Small fixes in ora_schema_definition

02-06-2015 version 1.7.5

---

• Better cleanup of schema_definition

- Translate latest version to real number

02-06-2015 version 1.7.4

---

• Better logging of script that are running
• Ignore characters in versions of upgrade and downgrade scripts

27-05-2015 version 1.7.3

---

• Small fix for ora_schema_defintion removing occasional error's

22-05-2015 version 1.7.2

---

• Better error checking on data attribute of ora_schema_defintion

21-05-2015 version 1.7.1

---

• Small fixes to ora_schema_definition and ora_record.

20-05-2015 version 1.7.0

---

• Added ora_schema_definition type. This type helps in managing the table defintions of your applications
• Added ora_record. This type supports manageing configuration records in database

13-05-2015 version 1.6.6

---

• Fixed creating a tablespace when no datafile is specified

24-04-2015 version 1.6.5

---

• Fixed changing tablespaces
• Added support for Puppet 4

08-04-2015 version 1.6.4

---

• Now realy works on RAC...

04-04-2015 version 1.6.3

---

• ora_service now works on RAC systems
• ora_service noew presists the services on non RAC systems

23-03-2015 version 1.6.2

---

• Quick bugfix

23-03-2015 version 1.6.1

---

• Small fix for ora_exec when unless is specified without a username

23-03-2015 version 1.6.0

---

• Removed the oracle daemon. Totaly. This makes the code easier to read.
• some small changes in ora_database for RAC support.
• improved error handling of sql code. This may lead to error's not seen before.
• Support for multiple disks in ora_asm_diskgroups.

04-03-2015 version 1.5.4

---

• Fixed spfile creation on RAC nodes
• Made direct sql the default for sql commands. This is the first step in removing the daemon.

07-02-2015 version 1.5.3

---

• Allow ora_init_param to manage ASM instances

03-02-2015 version 1.5.2

---

• Added the unless parameter to ora_exec

30-01-2015 version 1.5.1

---

• ora_tablespace max_size property now supports value unlimited

29-01-2015 version 1.5.0

---

• Support for asm_volumes
• Added a fact to get asm volume information (With help from Corey Osman)
• Fixed ora_asm_diskgroup attribute au_size

19-01-2015 version 1.4.0

---

• Add grant privileges function to ora_role (Thanks to Edward Groenenberg)
• Now works on Oracle XE (Thanks to Andreas Wegmann)
• ora_database can now remove clustered databases

12-01-2015 version 1.3.0

---

• Re-enginered the ora_database
• make the fact use of os_user work for both Oracle and ASM

07-01-2015 version 1.2.0

---

• Added the initial implementation of ora_database
• Add functionality to use a fact to specify os_user for oracle and asm. Fixes #36

07-01-2015 version 1.1.0

---

• Cleaned up contents of distributed package
• autorequire the oracle users tablespace
• Some fixes and clarifications for ora_asm_diskgroup. BEWARE: The api has changed. Check the README for details.
• Added support for oratab on Solaris.

16-12-2014 version 1.0.0

---

• Fixed some bugs

27-11-2014 version 0.7.0

---

-Big API change. Change all type names to ora_..

• Have the sid at with @ at the back instead with a slach at the front. eg. it used to be SID/HAJEE. Now it is HAJEE@SID

27-11-2014 version 0.6.0

---

• init params now works with a different syntax for specifying the name. Check the readme for details
• Added support for 'growing' small file tablespaces. the type doesn't try to downscale a grown tablespace
• Added support for running under a different os_user.

07-10-2014 version 0.5.0

---

• Added custom type asm_diskgroup. This group supports creating and removing ASM disk groups. Parts of it are writen by Remy van Berkum (remy.vanberkum@vermont24-7.com). Also added support for connecting to the ASM instances with the sysasm user

24-09-2014 version 0.4.0

---

• Added some types needed for Oracle RAC

08-09-2014 version 0.3.1

---

• defaults SID's now work for all types.
• Changed documentation to show use with SID

08-09-2014 version 0.3.0

---

• Added support for multiple SID's.
• The listener now needs a sid as title. This is potential incompatible with previous versions where the name could be anything.
• Added support for specifying the SID for init_param

Before this, history not really recorded. Look at git history for details