CHANGE_SBX

Allows changing all parameters of an existing sandbox except the sandbox name, tablespace and quota. Parameters that are not provided (left NULL) remain unchanged. Use procedure change_sbx_quota to change tablespace and quota settings.

Parameter Name

Required

DefaultValue

Values

Description

p_sbx_name

yes

The name of the sandbox.

The sandbox name is case sensitive.

p_lifetime

no

NULL

The lifetime of the sandbox in days.

Possible values are NULL, 1 to 9999 and -1, which means unlimited lifetime.

If a NULL value is provided, the existing value remains unchanged.

p_desc

no

NULL

A description of the sandbox.

If a NULL value is provided, the existing value remains unchanged.

p_requestor_name

no

NULL

The name of the sandbox requestor for documentary purposes.

If a NULL value is provided, the existing value remains unchanged.

p_requestor_mail

no

NULL

The email address of the sandbox requestor.

Email notifications will be sent to the sandbox requestor at the following events:

  • When the sandbox is ready for use

  • Before expiration

  • After expiration

  • After the sandbox is dropped

  • After the lifetime of a locked sandbox is changed to unlock it again

For details on expiration notifications, see SCURTY Concepts Guide, paragraph “Sandbox lifetime”.

If a NULL value is provided, the existing value remains unchanged.

p_restricted_master

no

NULL

Should the sandbox masters be restricted? Restricted means all sandbox masters will see only the intersection of their access rights. For details on restricted sandboxes see SCURTY Concepts Guide, paragraph “Restricted Sandboxes”.

Possible values:

  • TRUE to allow restricted masters only,

  • FALSE to allow unrestricted masters.

If a NULL value is provided, the existing value remains unchanged.

Example

Change the lifetime of sandbox ‘MIGR’ to 120 days. All other parameters remain unchanged:

EXEC p_sbx_admin.change_sbx
    ( 'MIGR'
    , 120 );