サポートと今すぐチャット
サポートとのチャット

Stat 6.3 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Setting Up Maintenance Steps

Sometimes the instructions for an Oracle patch require that you perform maintenance steps before or after you apply the patch to an environment. These steps may include running a particular command from the adadmin utility or running a script against the target environment. Stat provides a number of predefined maintenance steps that you can schedule before or after the Oracle Agent processes a patch application request. These predefined steps are displayed in the Maintenance Steps tab.

When scheduling maintenance steps and patch application requests, you can enforce that steps are performed as scheduled by specifying dependent events. A dependent event is an event that has to be completed before the current event is submitted to the Oracle Agent. For example, if a certain maintenance step should be run after a patch has been applied to an environment, you can make that patch application request a dependent event for the maintenance step. This way, the maintenance step cannot be executed until after the Oracle Agent has first processed the patch application request.

Editing Maintenance Steps

You can modify the default parameters of predefined maintenance steps. These include both general adadmin parameters as well as command-specific parameters (if any).

Ignore Restart - Selecting this option configures the Oracle Agent to ignore the restart files if previous adadmin session failed
Batch Size - Default value is set to 1000
Workers - Number of workers used to run an adadmin session. Recommended number is between 4 to 8 workers.
Products - Enter all to run the step for all products, or enter a space separated list of products
4

Defining Command Maintenance Steps

You can define maintenance steps in the form of custom commands. These are operating system commands executed by the client server Stat is running on. All drive mappings and file paths are relative to the client server.

When defining a command, you can include predefined parameters as well as user and server-based parameters. This provides a convenient way to specify values commonly invoked by operating system commands, such as server names and download directories. Also, parameters offer a way to secure sensitive information by encrypting values that you do not want visible to users such as passwords.

<<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

<<<YYYY>>>-<<<MM>>>-<<<DD>>> <<<HH>>>:<<<NN>>>:<<<SS>>>
2
In the Command with parameters field, enter the command you want Stat to run.
5
Click Interpret >>.
6
7

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.

2
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.
3
(Optional) In the Servers field, deselect any server that you do not want to run the step against.
4
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.
5
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.
8
Click Save.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択