ora profile

Overview

This resource allows you to manage a user profile in an Oracle database.

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ensure                    => 'present',
  composite_limit           => 'UNLIMITED',
  connect_time              => 'UNLIMITED',
  cpu_per_call              => 'UNLIMITED',
  cpu_per_session           => 'UNLIMITED',
  failed_login_attempts     => '10',
  idle_time                 => 'UNLIMITED',
  logical_reads_per_call    => 'UNLIMITED',
  logical_reads_per_session => 'UNLIMITED',
  password_grace_time       => '7',
  password_life_time        => '180',
  password_lock_time        => '1',
  password_reuse_max        => 'UNLIMITED',
  password_reuse_time       => 'UNLIMITED',
  password_verify_function  => 'NULL',
  private_sga               => 'UNLIMITED',
  sessions_per_user         => 'UNLIMITED',
  inactive_account_time     => '120',
  container                 => 'ALL'
}

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

composite_limit

Allows you set the composite_limit value in a profile.

Maximum weighted sum of: CPU_PER_SESSION, CONNECT_TIME, LOGICAL_READS_PER_SESSION, and PRIVATE_SGA. If this limit is exceeded, Oracle aborts the session and returns an error.

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ensure                    => 'present',
    ...
  composite_limit           => 'UNLIMITED',
    ...
}

Back to overview of ora_profile

connect_time

Allows you set the connect_time value in a profile.

Allowable connect time per session in minutes

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  connect_time              => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

container

Allows you to specify the scope of the object.

This property is only supported on version 12 and higher. It allows you to specify if the user will be seen through all portable containers (e.g. global) of just in the current pluggable database.

You can use container on:

• ora_user
• ora_profile
• ora_object_grant

Here is an example on how to use this:

ora_... { '...@sid':
  ...
  container       => 'local',
  ...
}

Valid values are local, common.

Back to overview of ora_profile

cpu_per_call

Allows you set the cpu_per_call value in a profile.

Maximum CPU time per call (100ths of a second)

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  cpu_per_call              => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

cpu_per_session

Allows you set the cpu_per_session value in a profile.

Maximum CPU time per session (100ths of a second)

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  cpu_per_session => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

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_profile

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_profile

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ora_profile

failed_login_attempts

Allows you set the failed_login_attempts value in a profile.

The number of failed attempts to log in to the user account before the account is locked

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  failed_login_attempts     => '10',
  ...
}

Back to overview of ora_profile

idle_time

Allows you set the idle_time value in a profile.

Allowed idle time before user is disconnected (minutes)

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  idle_time                 => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

inactive_account_time

Allows you set the inactive_account_time value in a profile.

Setting determines the maximum number of days of inactivity (no logins at all) after which the account will be locked.

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  inactive_account_time        => '120',
  ...
}

Back to overview of ora_profile

logical_reads_per_call

Allows you set the logical_reads_per_call value in a profile.

Maximum number of database blocks read per call

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  logical_reads_per_call    => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

logical_reads_per_session

Allows you set the logical_reads_per_session value in a profile.

Maximum number of database blocks read per session

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  logical_reads_per_session => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

name

The profile name

Back to overview of ora_profile

password_grace_time

Allows you set the password_grace_time value in a profile.

The number of days after the grace period begins during which a warning is issued and login is allowed. If the password is not changed during the grace period, the password expires.

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  password_grace_time       => '7',
  ...
}

Back to overview of ora_profile

password_life_time

Allows you set the password_life_time value in a profile.

The number of days the same password can be used for authentication

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  password_life_time        => '180',
  ...
}

Back to overview of ora_profile

password_lock_time

Allows you set the password_lock_time value in a profile.

the number of days an account will be locked after the specified number of consecutive failed login attempts defined by FAILED_LOGIN_ATTEMPTS

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  password_lock_time        => '1',
  ...
}

Back to overview of ora_profile

password_reuse_max

Allows you set the password_reuse_max value in a profile. The number of times a password must be changed before it can be reused

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  password_reuse_max        => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

password_reuse_time

Allows you set the password_reuse_time value in a profile.

The number of days between reuses of a password

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  password_reuse_time       => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

password_verify_function

Allows you set the password_verify_function value in a profile.

Verify passwords for length, content, and complexity

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  password_verify_function  => 'NULL',
  ...
}

Back to overview of ora_profile

private_sga

Allows you set the private_sga value in a profile.

Maximum integer bytes of private space in the SGA (useful for systems using multi-threaded server MTS)

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  private_sga               => 'UNLIMITED',
  ...
}

Back to overview of ora_profile

profile_name

The profile name

Back to overview of ora_profile

provider

The specific backend to use for this ora_profile resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:

simple

Manage an Oracle profile in an Oracle Database via regular SQL

Back to overview of ora_profile

sessions_per_user

Allows you set the sessions_per_user value in a profile.

Number of concurrent multiple sessions allowed per user

Here is an example on how to use this:

ora_profile { 'DEFAULT@sid':
  ...
  sessions_per_user         => 'UNLIMITED'
  ...
}

Back to overview of ora_profile

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_profile