sfae_state_op - Utility to update the fsm state in the repository

sfae_state_op -s <service> -a <application> [ -r <repositoryHost> ] [ -c <configFile> ] [ --<service_key>=<value>] [ --<application_key>=<value>] [ -p | --new_state=<newstate name> [ --previous_state=<previous state name>]]

This utility is intended to be used by support engineers to manually rectify the state information in the SFAE repository sfae_state_op is a utility to update the state information in the repository for a service application pair. Only valid state names are accepted.

The following options are supported:

-s Service_Type	Specifies service type for the operation. Supported service types are Checkpoint - Filesystem checkpoints. FileSnap - File level snapshots. Flashsnap - Volume level Snapshots. SOS - Space optimized volume level snapshots. This is a mandatory option.
-a Application-Name	Specifies the application for which point in time services should be used. Currently supported application is oracle database 10gr2, 11gr1 and 11gr2. This is a mandatory option.
-r repositoryHost	Specifies the host where the repository information is to be updated.
-c Configuration-File	All the command line options, specific to applications, apart from service_type, application_name and operations can be provided in Configuration file. Information in the configuration file should be in format <PARAMETER_NAME>=<VALUE>. Information about supported parameters are described in man pages for appropriate service types. This parameter is optional, if the application and service key is provided in command line.
--<Service_name>	Service_Name parameter uniquely identifies the point in time copy for the application. For e.g. If a user wants to create a 3rd mirror breakoff type snapshot(flashsnap), service key parameter would be flashsnap_name=dailysnap or flashsnap_name=hourlysnap. This would create a unique identifier for a that copy which should be used for all operations on it. This is a mandatory parameter which can be entered in configuration file as <Service_Name>=<Value> or on the command line as --<service_name> value. For more details please refer examples in man pages for services.
--<application_key>	Application_Key parameter uniquely identify application_instance. For e.g if there are two database running on the system, application_key for the database would be oracle_sid. This parameter should be used for all the point in time operation for specific application instance. This is a mandatory parameter which can be entered in the configuration file or on command line.For more details please refer examples in man pages for services.
-p	This would update the current state to the previous state. This is not a mandatory parameter
--new-state new state name
--previous-state previous state name	The --new-state parameter sets the current state to the specified state. The --previous-state parameter sets the previous state to the specified state. If the --previous-state parameter is not specified then the previous state and the current state in the repository gets updated to the state specified by --new-state NOTE The -p option and the --new-state, --previous-state par cannot be used together.

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