UPDATE

This procedure changes the attributes that are assigned to the specified protected database.

Syntax

PROCEDURE update_db (
   db_unique_name IN VARCHAR2,
   protection_policy_name IN VARCHAR2 DEFAULT NULL,
   reserved_space IN VARCHAR2 DEFAULT NULL,
   db_timezone IN VARCHAR2 DEFAULT NULL,
   incarnations IN VARCHAR2 DEFAULT 'CURRENT',
   skip_initial_replication IN BOOLEAN DEFAULT FALSE,
   compliance_hold IN TIMESTAMP WITH TIME ZONE DEFAULT dbms_ra_misc.tsnull('pl'),
   comments IN VARCHAR2 DEFAULT NULL);

Parameters

Table 21-53 UPDATE_DB Parameters

Parameter	Description
`db_unique_name`	The `DB_UNIQUE_NAME` of the database.
`protection_policy_name`	The name of the protection policy to assign to the database. The protection policy must exist. The new protection policy controls new storage operations. If the old and new protection policies specify different storage locations, the Recovery Appliance starts a background task to move data from the old storage location to the new location. Recovery Appliance only moves backups that are not obsolete. If a move between storage locations is required, then the `RA_DATABASE` view does not show the new protection policy until the move has started. If the Recovery Appliance must perform higher priority work, then the Recovery Appliance may not start the move for several hours.
`reserved_space`	See `ADD_DB`.
`db_timezone`	The time zone where this database is located. By default, protected databases are assigned to the same time zone as the Recovery Appliance. If the protected database is in a different time zone, then use this procedure to assign the database to the correct time zone.
`incarnations`	Comma-delimited list of keys for all previous database incarnations to update the `db_timezone`. By default, this procedure updates the current incarnation. If the protected database administrator has not specified a `db_timezone` and this list contains the current incarnation key, then this procedure associates the time zone with the metadata for the current incarnation. If the time zone is set in the parameter file already for the incarnation, then the new `db_timezone` is ignored.
`skip_initial_replication`	If set to `TRUE`, the initial replication is skipped.
`compliance_hold`	The time from which backups may not be deleted from the Recovery Appliance or guaranteed tape or cloud storage. The database must be recoverable to the time specified by this `compliance_hold`. Specify the time as any valid `TIMESTAMP WITH TIME ZONE` expression, such as `SYSTIMESTAMP - NUMTODSINTERVAL(7, 'DAY')`, meaning "starting 7 days ago." If the database is being updated with `compliance_hold`, make sure that its associated protection policies do not have `autotune_reserved_space` configured.
`comments`	Optional user supplied comment describing reason for executing this command.