This module allows you to manage users, tablespaces and schemas and much more in an existing database. 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_profile
• ora_record
• ora_role
• ora_schema_definition
• ora_service
• ora_setting
• ora_statement_audit
• ora_synonym
• ora_tablespace
• ora_thread
• ora_trigger
• ora_user

Getting started

Puppet helps a lot to install and manage installations . Especially in large enterprise installations. But we know from our customers, that it is difficult to get started. There is so much to configure and so much install. It is hard to figure out where to start.

To help you get going, we have implemented some extensive examples. We are working to make these example so comprehensive that they can serve as a reference implementation.

Learn on your own PC

We have structured these examples so that you can run them on your own PC. We use VirtualBox and Vagrant to get the systems up and running and after the initial boot, we let Puppet do the rest.

Masterless or using Puppet Enterprise

Most of our clients use Puppet Enterprise. So the examples contain a full blown implementation using Puppet Enterprise 2005.2. But sometimes it is easier to get started using a masterless approach. So you can run the examples masterless as well.

Check it out…

Effortless switch from Public Domain modules

Maybe you are using the Public Domain modules right now and want to switch to using our supported versions. To allow for a seamless transition we have developed a conversion tool.

Our emconvert software will scan all your Puppet code and replace all code calling the Public Domain modules into code calling the supported Enterprise Modules. After this conversion, you are ready to enjoy the improved Enterprise Modules Puppet software and receive our support.

Check it out…

To use this module, you need a running Oracle database and/or a running asm database. You can get the ora_install module from Enterprise Modules to install the database and Grid software. To install these modules, you can use a Puppetfile

forge "http://forge.enterprisemodules.com"

mod 'enterprisemodules/ora_config'               ,'2.0.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
    --module_repository=http://forge.enterprisemodules.com 
    enterprisemodules-ora_config

When it fails on a Master-Agent setup you can do the following actions:

• Check the time difference/timezone between all the puppet master and agent machines.
• Update oracle and its dependencies on the puppet master.
• After adding or refreshing the easy_type or oracle modules you need to restart all the PE services on the puppet master (this will flush the PE cache) and always do a puppet agent run on the Puppet master
• To solve this error “no such file to load – easy_type” you need just to do a puppet run on the puppet master when it is still failing you can move the easy_type module to its primary module location ( /etc/puppetlabs/puppet/module )

When the ora_database creation fails:

• First remove all config_scripts. Then start again. If the database creation run’s fine, check the scripts.
• Check if all the path’s in the script exist and log file directories are writable by the specified Oracle user.