ora_config

the types and providers needed to manage all objects inside an Oracle database

Project URL RSS Feed Report issues

Module Stats

85,770 downloads

356 latest version

4.4 quality score

Version information

released Apr 23rd 2018

This version is compatible with:

Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
Puppet >= 4.0.0 < 6.0.0
, , , , , , , ,

Tasks:

profile

role

service

sql

tablespace

user

Start using this module

Installation method

Add this module to your Puppetfile:

mod 'enterprisemodules-ora_config', '2.6.0'

Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add enterprisemodules-ora_config

Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install enterprisemodules-ora_config --version 2.6.0

Tags: database, oracle, asm, ora, oracle11g, oracle12c, oracle18c, oracle19, oracle21

Documentation

enterprisemodules/ora_config — version 2.6.0 Apr 23rd 2018

Overview
License
Description - What the module does and why it is useful
Setup

Requirements
Installing the ora_config module

Usage - Configuration options and additional functionality
Reference - An under-the-hood peek at what the module is doing and how
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_rac To use Puppet to create and manage Oracle RAC installations.

License

This is a commercially licensed module. But you can use the module on VirtualBox based development systems for FREE. When used on real systems a license is required.

You can license our modules in multiple ways. Our basic licensing model requires a subscription per node. But contact us for details.

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:

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
Windows systems are NOT supported

Installing the ora_config module

To install these modules, you can use a Puppetfile

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

Then use the librarian-puppet or r10K 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:

Limitations

This module runs on Solaris and most Linux versions. It requires a puppet version higher than 4. The module does NOT run on windows systems.

What are tasks?

Modules can contain tasks that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.

Tasks in this module release

profile

Allows get the status, create or remove an Oracle profile

Parameters
action	The action you want to execute `Optional[Enum['list', 'status','create','remove']]`
profile_name	The name of the Oracle profile to use. `Optional[String[1]]`
properties	The properties to use when create a Oracle profile `Optional[Hash]`

Input method

stdin

role

Allows get the status, create or remove an Oracle role

Parameters
action	The action you want to execute `Optional[Enum['list', 'status','create','remove']]`
properties	The properties to use when create a Oracle role `Optional[Hash]`
role_name	The name of the Oracle role to use. `Optional[String[1]]`

Input method

stdin

service

Allows get the status, create or remove an Oracle service

Parameters
action	The action you want to execute `Optional[Enum['list', 'status','create','remove']]`
properties	The properties to use when create a Oracle service `Optional[Hash]`
service_name	The name of the Oracle service to use. `Optional[String[1]]`

Input method

stdin

sql

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

Parameters
password	The password to use. Only valid when specifying an Oracle username `Optional[String[1]]`
raw	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 `Optional[Boolean]`
sid	SID of the database to connect to `Optional[String[1]]`
sql	The SQL you want to execute `String[1]`
username	The Oracle username to use. When none is specfied, SYS will be used. `Optional[String[1]]`

Input method

stdin

tablespace

Allows get the status, create or remove an Oracle tablespace

Parameters
action	The action you want to execute `Optional[Enum['list', 'status','create','remove']]`
properties	The properties to use when create a Oracle tablespace `Optional[Hash]`
tablespace_name	The name of the Oracle tablespace to use. `Optional[String[1]]`

Input method

stdin

user

Allows get the status, create or remove an Oracle user

Parameters
action	The action you want to execute `Optional[Enum['list', 'status','create','remove']]`
properties	The properties to use when create a Oracle user `Optional[Hash]`
user_name	The name of the Oracle user to use. `Optional[String[1]]`

Input method

stdin

Types in this module release

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',
    }

Parameters
ensure
provider

Providers
prefetching	Manage Oracle synonyms in an Oracle Database via regular SQL

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',
    }

Parameters
ensure
provider

Providers
simple	Manage directory mappings in an Oracle Database via regular SQL

ora_profile

Providers
simple	Manage an Oracle profile in an Oracle Database via regular SQL

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
provider

Providers
simple	Enable/disable options in the Oracle kernel

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).

Parameters
ensure
provider

Providers
simple	This is the generic provider for a easy_type type

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
provider

Providers
prefetching	Manage Oracle object permissions via regular SQL

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'},
      ]
    }
  }

Parameters
ensure
provider

Providers
simple	Manage RAC ASM groups in an Oracle Database via regular SQL

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](https://forge.puppetlabs.com/hajee/ora_rac).


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

This enables thread 2 on instance named `sid`

Parameters
provider

Providers
simple	Manage Oracle users in an Oracle Database via regular SQL

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.

Parameters
ensure
provider

Providers
oracle11	Manage Oracle services using srvctl syntax in Oracle 11 provider.
oracle12	Manage Oracle services using srvctl syntax for Oracle 12

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',
    volume_device => '/mnt/oravolume',
  }

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

Parameters
ensure
provider

Providers
default_provider	This is the generic provider for a easy_type type

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](http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces002.htm#ADMIN11359) 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,
    }

Parameters
ensure
provider

Providers
simple	Manage an Oracle Tablespace in an Oracle Database via regular SQL

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
provider

Providers
sqlplus	Manage The schema definition

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},
      ]

Parameters
ensure
provider

Providers
simple	Manage an Oracle Database

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
provider

Providers
simple	Report on database feature usage

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).
```

Parameters
ensure
provider

Providers
simple	This is the generic provider for a easy_type type

ora_statement_audit

Providers
simple	Manage auditing in an Oracle Database via regular SQL

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.

Parameters
name	The sid of the listner to run.
provider

Properties
ensure	Whether a listener should be running. `This is a required property without any defaults.`

Providers
listener

ora_scheduler_job

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).

Parameters
ensure
provider

Providers
simple	This is the generic provider for a easy_type type

ora_user

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.

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

Parameters
ensure
provider

Providers
simple	This is the generic provider for a easy_type type

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'
    }

Parameters
ensure
provider

Providers
simple	Manage Oracle Instance Parameters in an Oracle Database via regular SQL

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
provider

Providers
sqlplus

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
provider

Providers
sqlplus	Manage a record in an Oracle table via regular SQL

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.

Parameters
ensure
provider

Providers
simple	Manage object auditing an Oracle Database via regular SQL

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://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_6012.htm#SQLRF01311) 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'],
    }

Parameters
ensure
provider

Providers
simple	Manage an Oracle role in an Oracle Database via regular SQL

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'
  }

Parameters
ensure
provider

Providers
simple	Manage ASM Directories in an Oracle Database via regular SQL

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
provider

Providers
simple	Manage ora settings through yaml file

History

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

Enterprise Modules License d.d. January 2018

This license (“License”) governs the terms and conditions under which ora_config module (“the Software”)
is licensed by Enterprise Modules B.V, a limited liability company in the Netherlands, registered in
the Dutch Chamber of Commerce: 63689537 (“Licensor”), to the user of the Software (“Licensee”).

Article 1. Grant of license

1.1 Licensor hereby grants to Licensee the right to use the Software for its internal business
purposes.

1.2 The license granted in the previous paragraph is limited to the use on VirtualBox Virtual
machines. For further use a commercial license must be directly obtained from Licensor.

Article 2. License limitations

2.1 All right, title and interest to the Software, the accompanying documentation and all
modifications and extensions thereto rest and remain with Licensor. Licensee only has the
rights and permissions explicitly granted by this License or granted in writing otherwise.
Licensee shall not use, copy, modify, distribute or publish the Software in any other manner.
Nothing in this License is intended to, and shall not be construed to, transfer to Licensee any
rights in intellectual property developed by Licensor.

2.2 In particular, Licensee shall not:
a) provide copies of the Software to third parties, including to entities controlling,
controlled by or under common control with Licensee;
b) sublicense the Software or otherwise make available the Software to such third parties,
including by rental, Software-as-a-Service models or otherwise;
c) remove indications of Licensor as copyright holder of the Software or to remove or render
illegible any part thereof.

2.3 The Software comprises third-party open source software. The respective third-party rights
holders grant Licensee the rights indicated in the applicable open source licenses. These
licenses can be found in the documentation. The License does not apply to this open source
software, and nothing in this License shall be construed as a limitation of any right granted
under an open source license.

Article 3. Trademark

3.1 This License does not grant permission to use the trade names, trademarks, service marks, or
product names of the Licensor, except as required for reasonable and customary use in
describing the origin of the Software.

Article 4. Limitation of Liability

4.1 Licensor provides the Software on an "AS IS" basis, and expressly disclaims all conditions,
representations or warranties, express or implied, including without limitation any implied
warranties of merchantability, fitness for a particular purpose, and non-infringement of third
party rights regarding the Software. Licensor is solely responsible for determining the
appropriateness of using the Software and assume any risks associated arising out of or in
connection with the Software and this License.

4.2 Licensor shall not be liable for any damages, including consequential, special, punitive and/or
incidental damages or fines imposed by regulatory bodies, arising out of or in connection with
the Software and this License.

4.3 Licensee shall release, defend, indemnify and hold harmless Licensor from and against any and
all claims, damages and liability arising in connection with the Software, including from
claims, damages or liability from customers of Licensee.

Article 5. Miscellaneous

5.1 Licensor reserves the right to change any or all parts of this License without prior notice.

5.2 The law of the Netherlands governs this License and the terms and conditions therein.

5.3 Any disputes arising between Licensor and Licensee in connection with the License will be
settled by the competent courts in the Netherlands for the principal place of business of the
Licensor.

Modules

Discover

Contribute

Resources

About Forge

Getting Started

ora_config

Version information

This version is compatible with:

Tasks:

Start using this module

Documentation

Table of Contents

Overview

License

Description

Setup

Requirements

Installing the ora_config module

Usage

Reference

Limitations

What are tasks?

Tasks in this module release

profile

role

service

sql

tablespace

user

Types in this module release

ora_synonym

ora_directory

ora_profile

ora_home_option

ora_procedure

ora_object_grant

ora_asm_diskgroup

ora_thread

ora_service

ora_asm_volume

ora_tablespace

ora_schema_definition

ora_database

ora_feature_usage

ora_trigger

ora_statement_audit

ora_listener

ora_scheduler_job

ora_user

ora_package

ora_init_param

ora_exec

ora_record

ora_object_audit

ora_role

ora_asm_directory

ora_setting

History

2.6.0

2.5.2

2.5.1

2.5.0

2.3.24

2.3.23

2.3.22

2.3.21

2.3.20

2.3.19

2.3.18

2.3.17

2.3.16

2.3.16

2.3.15

2.3.14

2.3.13

2.3.12

2.3.11

27-07-2017 Version 2.3.10

27-07-2017 Version 2.3.9