. de IX . ds #H ((1u-(\\n(.fu%2u))*.13m) . ds ’ \k:' test veritas logo


vxsfadm-oracle-checkpoint(1M)

NAME

Checkpoint service using the vxsfadm utility for the Oracle application.

SYNOPSIS

vxsfadm -s checkpoint -a oracle -o <operation>
[ -c config-file ]
[ -r Respository-host ]
[--<checkpoint_name> <value>]
[--<oracle_sid> <Value>]
[--<oracle_home> <Value>]

DESCRIPTION

The checkpoint service is used to create a point in time copy the oracle database mounts using VxFS checkpoints. The point in time copies can be used to create clone or be mounted for backups.

Configuration Options

Below is an explanation of the configuration parameters specific for the oracle application supported by the checkpoint service, which can be specified in the configuration file or the environment. Also specified are the command line option for the same.
ORACLE_SID The value is the Oracle Instance name to be used.
commandline --oracle_sid/--S

This is a mandatory parameter.

ORACLE_HOME The value is the ORACLE_HOME path for the database instance.
commandline --oracle_home/--H

This is a mandatory option.

APP_MODE This parameter specifies if the oracle database would be online/offline/instant when the checkpoint is created for the applicaiton.
online: The oracle database is put in backup mode before the checkpoint is created on the database mounts. The database is released from backup after the checkpoint is created. The archive log sequence is used for recovery.
instant: The oracle database is not put in backup when the checkpoint is created. The redo log information is used at the tme of recovery.
offline: The oracle database is offline at the time the checkpoint is created.
commandline --app_mode=online/offline/instant/
commandline --online/--instant/--offline

This is a not a mandatory option. The default mode is online .

CLONE_NAME This parameter specifies the name with which the cloned database would be got up.
commandline --clone_name

This is not a mandatory option.

PFILE This paramater can be used to specify the pfile used by the primary database. If not specified the default pfile is assumed
commandline --pfile

This is not a mandatory option

PFILE_MOD This paramater specifies the file containing the modified pfile attributes to e used in the clone database.
commandline --pfile_mod

This is not a mandatory option

DATAFILE_ROLLBACK This parameter would be a comma separated list of datafiles that would be rolled-back when the restore operation is used.
commandline --datafile_rollback

This is not a mandatory option.

TABLESPACE_ROLLBACK This parameter is the name of the tablespace that would be rolled-back when the restore operation is used.
commandline --tablespace_rollback
DATAFILE_LIST_ROLLBACK This parameter is the name of a file that contains a list of datafiles separated by newline characters that would be rolled-back when the restore operation is used.
commandline --datafile_list_rollback
Service Specific parameters The paramameters below are specific for the checkpoint service, please refer the vxsfadm-checkpoint(1M) man page for more information:
CHECKPOINT_NAME
CLONE_PATH
SNAPSHOT_REMOVABLE

Data gathering for offline mode checkpoints

vxsfadm -s checkpoint -a oracle -o getappdata --oracle_sid=SID

The above operation would gather all the information necessary for checkpoint creation when the database is offline.

The above command must be run when the database is up. If an offline checkpoint is attempted to be created without performing the data gathering operation then offline checkpoint creation would fail.

Example Operations

Checkpoint create:
online mode checkpoints vxsfadm -s checkpoint -a oracle -o create --oracle_sid=SID --checkpoint_name=xxx

The above operation would create a removable online checkpoint over all the mounts of the database SID

instant mode checkpoints vxsfadm -s checkpoint -a oracle -o create --oracle_sid=SID --checkpoint_name=xxx --instant

The above operation would create a removable instant checkpoint over all the mounts of the database SID

Checkpoint Destroy
Destroy a cloned database vxsfadm -s checkpoint -a oracle -o destroy --oracle_sid=SID --checkpoint_name=xxx --clone_name=clone1

The above command would shutdown the clone database clone1 and proceed with unmount and destroy of the checkpoint xxx_rw_yyyy

Destroy a checkpoint vxsfadm -s checkpoint -a oracle -o destroy --oracle_sid=SID --checkpoint_name=xxx

The above command would destroy of the checkpoint xxx, if mounted the same would be unmounted before the checkpoint is destroyed.

Checkpoint Unmount
Unmount a clone database vxsfadm -s checkpoint -a oracle -o umount --oracle_sid=SID --checkpoint_name=xxx --clone_name=clone1

The above command would shutdown the clone database clone1 and proceed with unmount of the checkpoint xxx_rw_yyyy

Unmount a checkpoint vxsfadm -s checkpoint -a oracle -o umount --oracle_sid=SID --checkpoint_name=xxx

The above command would unmount of the checkpoint xxx, if mounted the same would be unmounted.

Mount a checkpoint in read_only mode vxsfadm -s checkpoint -a oracle -o mount --oracle_sid=SID --checkpoint_name=xxx --clone_path=/tmp/mnt1

The above operation would simply mount the checkpoint xxx in read_only mode at /tmp/mnt1

Mount a checkpoint in read_write mode vxsfadm -s checkpoint -a oracle -o mountrw --oracle_sid=SID --checkpoint_name=xxx --clone_path=/tmp/clone1

The above operation would simply create a checkpoint of the checkpoint xxx and mount the same in read_write mode at /tmp/clone1

Clone the database using a checkpoint vxsfadm -s checkpoint -a oracle -o clon --oracle_sid=SID --checkpoint_name=xxx --clone_name=clone1 --clone_path=/tmp/clone1

The above operation would clone the database SID to the name clone1 and have the database clone mounted at /tmp/cone1

Oracle Database Configuration Support

The following Oracle Databases releases are supported :
12cR2
18c
19c
The database should have the following configurations:
1 The database should have its datafiles and archive log on separate volumes and they should be mounted on a vxfs filesystem
2 The database should be in archive log mode and must have atleast one valid archive log destination
3 All of the redolog files and control files should be residing on a vxfs filesystem
Databases with the configurations listed below are not supported
1 OMF configured databases are not supported
2 Standby databases are not supported
3 Flashback enabled databases may not work correctly

SEE ALSO

vxsfadm(1M), vxsfadm-oracle(1M), vxsfadm-checkpoint(1M)

vxsfadm-flashsnap(1M), vxsfadm-sos(1M), vxsfadm-filesnap(1M) vxsfadm-oracle-flashsnap(1M), vxsfadm-oracle-sos(1M), vxsfadm-oracle-filesnap(1M)


Storage Foundation vxsfadm-oracle-checkpoint(1M)