Overview

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

Attributes

Attribute Name Short Description
disable_corrective_change Disable the modification of a resource when Puppet decides it is a corrective change.
disable_corrective_ensure Disable the creation or removal of a resource when Puppet decides is a corrective change.
ensure The basic property that the resource should be in.
name The synonym name
   
owner The owner of the synonym.
provider resource.
sid SID to connect to.
synonym_name The synonym name.
table_name The table name the synonym references.
table_owner The table owner the synonym references.

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_synonym

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_synonym

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ora_synonym

name

The synonym name

Back to overview of ora_synonym

owner

The owner of the synonym. This is the first part of the title string. The first part before the ..

    ora_synonym { 'OWNER.SYNONYM_NAME@SID':
    	...
    }

Back to overview of ora_synonym

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

prefetching
Manage Oracle synonyms in an Oracle Database via regular SQL

Back to overview of ora_synonym

sid

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 database from the /etc/ora_setting.yaml with the property default set to true. We advise you to either use @sid in all your manifests or leave it empty everywhere.

Back to overview of ora_synonym

synonym_name

The synonym name. This is the part of the title between the `.` and the `@`

ora_synonym { ‘PUBLIC.SYNONYM_NAME@SID’: … }

Back to overview of ora_synonym

table_name

The table name the synonym references.

ora_synonym { ‘PUBLIC.SYNONYM_NAME@SID’: … table_name => ‘TABLE_NAME’, … }

Back to overview of ora_synonym

table_owner

The table owner the synonym references.

ora_synonym { ‘PUBLIC.SYNONYM_NAME@SID’: … table_owner => ‘TABLE_OWNER’, … }

Back to overview of ora_synonym