ora asm directory

Overview

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

Experience the Power of Puppet for Oracle

If you want to play and experiment with Puppet and Oracle, please take a look at our playgrounds. At our playgrounds, we provide you with a pre-installed environment, where you experiment fast and easy.

For Oracle   here at our playground...

Attributes

asm_path

The directory name.

This is a required String parameter that is part of the title of the raw_resource.

ora_asm_directory { '+DATA/DIR/SUBDIR@+ASM1':
  ...
  asm_path    => '+DATA/DIR/SUBDIR',
  ...
}

In this example, the RECODG is de diskgroup name. Diskgroup names will always be uppercased by Puppet. This means in Puppet you can use either lower, upper or mixed case. In Oracle, it will be always be an upper case string.

Back to overview of ora_asm_directory

asm_sid

ASM SID to connect to.

All types have a name like resource@sid. The sid is optional. If you don’t specify the sid, the type will use the ASM instance from the /etc/ora_settings.yaml with the name default_asm. We advise you to either use @sid in all your manifests or leave it empty everywhere.

Back to overview of ora_asm_directory

disable_corrective_change

Disable the modification of a resource when Puppet decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_change parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not modify the resource and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of ora_asm_directory

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_ensure parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not create or remove the resource and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of ora_asm_directory

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ora_asm_directory

name

The name of the ora_asm_directory including SID.

ora_asm_directory { '+DATA/DIR/SUBDIR@+ASM1':
  ...
}

The SID is optional. When you don’t specify an SID, Puppet will take the ASM instance from ora_setting with property default set to true and use that as the SID. We recomend you to always use a full qualified name (e.g. a name including the SID) or not do it at all.

Back to overview of ora_asm_directory

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.Available providers are:

simple

Manage ASM Directories in an Oracle Database via regular SQL

Back to overview of ora_asm_directory

recurse

When you set this value to true, this ASM directory and all parent directories will be automatically created.

Valid values are true, false, yes, no, true, false.

Back to overview of ora_asm_directory