Forge Home

oracle

Manage the oratab through puppet

9,515 downloads

9,515 latest version

4.6 quality score

Version information

  • 1.0.0 (latest)
released Jan 22nd 2015
This version is compatible with:
  • ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'stschulte-oracle', '1.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add stschulte-oracle
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install stschulte-oracle --version 1.0.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: oracle, oratab

Documentation

stschulte/oracle — version 1.0.0 Jan 22nd 2015

Puppet Oracle Module

Build Status

This repository aims to ease the configuration of Oracle Databases with custom types and providers

New facts

(currently none)

New functions

(currently none)

New custom types

oratab

The oratab file stores information about the home directory of your databases and whether the different instances should be automatically started and stopped by the dbstart and dbshut scripts or not.

The oratab type now allows you to treat a single entry as a resource:

oratab { 'PROD_DB':
  ensure => present,
  home   => '/u01/app/oracle/product/10.1.0/db_1',
  atboot => yes,
}

The example above will lead to the following entry in the file /etc/oratab (or /var/opt/oracle/oratab on Solaris)

PROD_DB:/u01/app/oracle/product/10.1.0/db_1:Y

You can also specify an inline comment with the description property. This is however optional.

oratab { 'PROD_DB':
  ensure      => present,
  home        => '/u01/app/oracle/product/10.1.0/db_1',
  atboot      => yes,
  description => 'managed by puppet'
}

will lead to

PROD_DB:/u01/app/oracle/product/10.1.0/db_1:Y # managed by puppet

If you do not specifiy the description property, puppet will not touch the current inline comment. This might interest you because newer versions of oracle always update the comment as line added by agent on each instance stop and start.