Stat 6.2 - User Guide


	NOTE: User and server-based parameters are also used by system administrators to define custom commands for pre and post migration steps. For more information on pre and post migration parameters, see Chapter 4, “General Maintenance Tables” in the Stat System Administration Guide.

To define a maintenance step:

Select the maintenance step EXECUTE_COMMAND and click Edit.

This opens the Maintenance Step Edit window for the EXECUTE_COMMAND step.

Click the browse button to open the Maintenance Step Command Editor window.

Predefined parameters specify values used to login to a target environment during a migration (database name, user name and password), whereas user and server-based parameters generally invoke values associated with the users and file servers defined in Stat. Also, certain parameters may be defined so that their values are different depending on which user or server they are being applied to.

The Maintenance Step Command Editor also supports special symbols representing different variables:


Symbol	Interpretation	Example
<<YY>>	The current year, 2-digit format	01
<<YYYY>>	The current year, 4-digit format	2001
<<MM>>	The current month, 2-digit format	01
<<DD>>>	The current day of month, 2-digit format	31
<<DDD>>	The current day of week	Monday
<<HH>>	The current hour, 2-digit format	13
<<NN>>	The current minutes, 2-digit format	45
<<SS>>	The current seconds, 2-digit format	23
<<ENV>>	The target environment of the migration	PROD
<<SDCD>>	The service domain that the CSR belongs to	HR
<<CSRID>>	The CSR ID number	6086
<<OBJTYPE>>	The object type the maintenance step is defined for	Panel

For example, if you are defining a command that invokes the current date and time, you could enter the following special symbols:

<<<YYYY>>>-<<<MM>>>-<<<DD>>> <<<HH>>>:<<<NN>>>:<<<SS>>>

In the Command with parameters field, enter the command you want Stat to run.

If you want to include parameters in the definition of the command, click the location where you want to insert the parameter and then double-click the parameter you want to insert. When included in a command, parameters are enclosed in %% signs, for example, “%%GL_PWD%%”.

Certain users and file servers may have parameters that have been defined specifically for them, or the value of a particular parameter may be different depending on which user or server it is being applied to. When the Maintenance Step Command Editor is first opened, the parameters are listed as they have been defined for the local client server and the current user. If you want to include parameters defined for a different server, click in the Server field and select the server you want. Although you cannot select a different user in the User field, when a user executes the command, they will have the option of inserting their own parameters or overriding default values.

(Optional) To define additional commands, click <Enter> to create a new line in the Command with parameters field and repeat step #2.

If you are defining a command for an object type in an archive set, select one or more object types in the Objects field.


	NOTE: If you do not select an object type when using any of the TARGET_OBJECT_NAME predefined parameters, you will receive an error message.

Click Interpret >>.

The Interpreted Command field displays how the command is interpreted by the client server. The values of interpreted parameters in the command definition are enclosed in angle brackets. Encrypted values are not displayed but replaced with asterisks.

Click OK.

The Maintenance Step Edit window for the EXECUTE_COMMAND step now displays the command statement you just defined.


	NOTE: If you inserted parameters defined for a server other than the local client server in the command statement, the name of the server is displayed in the Maintenance Step Edit window.

Click OK.

Scheduling Maintenance Steps

When you schedule the Oracle Agent to run a maintenance step, you specify when you want the Oracle Agent to execute the step (immediately or at some later time) as well as the environment and servers you want the step executed against.

You can also ensure that the maintenance step is executed only after the patch it is associated with has been applied by designating the patch application request as a dependent event. This way, the Oracle Agent will not execute the step until it has first applied the patch.

To edit a maintenance step:

Select the maintenance step you want and click Schedule.

This opens the Schedule Request window.

In the Environment field, select the environment you want to run the step against.

The Servers field displays all the servers included in the selected environment. You can run the step against each server in an environment, or you can run it against just the servers you select. You must select at least one server, however.

(Optional) In the Servers field, deselect any server that you do not want to run the step against.

In the Run Time field select either Immediate if you want the Agent to process the request right away (or if you specify a dependent event, immediately after the Oracle Agent processes that event) or select Select Datetime if you want to the request to be processed at some future date.

If you selected Select Datetime, browse for the date you want. You can also specify the time you want the request processed in terms of hour and minute.

Next, if you want to configure the Oracle Agent to execute the maintenance step after a certain patch has been applied, you can designate the corresponding Patch Apply request as a dependent event. The Patch Apply request you want to designate as a dependent event must have a status of “Received by Agent,” “Pending/New,” “In Process,” or “Send to Agent.” Patch Apply requests that have already been processed by the Oracle Agent cannot be selected as dependent events.


	TIP: You can configure the Oracle Agent to execute a maintenance step before a patch application is applied by designating the maintenance step as a dependent event when scheduling a patch application request. For more information, see the section, Scheduling Patch Applications and Impact Analysis .