| Executing a data upgrade run (OP-CE)Step 1. Display the run information- Start the Data Upgrade Runs (ttspt2500m000) session.
Go to the Run Information tab.
Step 2. If the data upgrade run already exists, initialize the
runPerform this step only if the data upgrade run you want to
execute already exists, for example because it was generated
automatically. To initialize an existing run: - Select the run and on the appropriate menu, select Initialize Data Upgrade Run. The Initialize Data Upgrade Run (ttspt2200m000) session starts.
Fill out the fields in the session. Among other things,
specify this information: If applicable, an Upgrade Task Source For example, you can specify a PMC Solution on which the initialization will be
based. - The companies you want to upgrade
The Source Feature Pack is already filled in. Caution! Ensure the correct source feature pack number is
filled in. The data upgrades to be performed will be based on the specified
source feature pack number: - If the number is too low, too much data is converted.
Possibly data will be overwritten with wrong values.
- If the number is too high, not all data is converted.
Possibly data will not be consistent.
Note - The initialization process assigns the specified
feature pack number to all upgrade tasks in the run.
- After an incorrect initialization, you can correct the Source Feature Pack for the upgrade tasks/ upgrade programs in the run. To perform this
correction, use the Global Change Source Feature Pack (ttspt2220m000) session.
- Click Initialize.
- When the initialization is finished, a "Process completed"
message is displayed. To remove the message box, click OK.
- Close the Initialize Data Upgrade Run (ttspt2200m000) session.
Step 3. If the data upgrade run does not exist yet, create and
initialize a new runPerform this step only if the data upgrade run does not
exist yet. To create and initialize a new run: - In the Data Upgrade Runs (ttspt2500m000) session, click New. The Initialize Data Upgrade Run (ttspt2200m000) session starts.
Fill out the fields in the session. Among other things,
specify this information: If applicable, an Upgrade Task Source For example, you can specify a PMC Solution on which the initialization will be
based. - The companies you want to upgrade
The number of the Source Feature Pack, such as 6 in case of FP6 Caution! Ensure the correct source feature pack number is
filled in. The data upgrades to be performed will be based on the specified
source feature pack number: - If the number is too low, too much data will be
converted. Possibly data will be overwritten with wrong values.
- If the number is too high, not all data will be
converted. Possibly data will not be consistent.
Note - The initialization process assigns the specified
feature pack number to all upgrade tasks in the run.
- After an incorrect initialization, you can correct
the Source Feature Pack for the upgrade tasks/ upgrade programs in the run. To perform this
correction, use the Global Change Source Feature Pack (ttspt2220m000) session.
Note: if you select the Start Data Upgrade Engine After Initialization check
box, the run starts automatically after the initialization is finished. You
cannot check the source feature pack or finetune the run before it is
started. - Click Initialize.
- When the initialization is finished, a "Process completed"
message is displayed. To remove the message box, click OK.
- Close the Initialize Data Upgrade Run (ttspt2200m000) session. The new run is displayed in the Data Upgrade Runs (ttspt2500m000) session.
Step 4. Finetune the run.To finetune the run, you can select these actions on the appropriate menu in the Data Upgrade Runs (ttspt2500m000) session: Companies by Data Upgrade Run | Starts the Companies by Data Upgrade Run (ttspt2510m000) session. By default, all companies of a package combination
are processed in the same run. To split the upgrade process, you can move
companies to other runs. In this way you can, for example, process a package
combination's live companies and archive companies in two separate
runs. To move companies to another run: - In the Companies by Data Upgrade Run (ttspt2510m000) session, select the companies you want to
move.
- On the appropriate menu, select Move Companies to Another Run. The Move Companies to Another Run (ttspt2210m000) session starts.
- Enter the required information:
- Optionally, change the company
selection.
- Specify the destination run. You can create a
new run, or select an existing run.
- Click Move.
Note: companies that are related to each other must
be linked to the same run. You can only move a company to another run, if you
also move its related companies. If the company selection does not contain all
related companies, an error message is displayed. The message specifies the
missing companies that must be included in the selection. Click Make Valid to automatically select the
missing companies. | Data Upgrade Tasks | Starts the Data Upgrade Tasks (ttspt2520m000) session. Double-click an upgrade task to start the Data Upgrade Tasks (ttspt2520m100) details session. Use this session to change, for example,
these properties of an upgrade task: - The Source Feature Pack
The Runtime Class Note - Set the Runtime Class to Huge, Large, Medium,
or Small.
The Real Run Status Caution! - Only change this status in case of troubleshooting. See Troubleshooting (OP-CE).
- If you set the Real Run Status to Released, the task will not be processed. In this way you
can skip tasks that would fail during execution, and ensure the run succeeds
anyway. This can cause unpredictable results or even data corruption. Therefore
setting the Real Run Status to Released is at your own risk.
For more information, refer to the session help. |
Step 5. Execute the run- Select the run in the Data Upgrade Runs (ttspt2500m000) session.
- On the appropriate menu, select Data Upgrade Engine. The Data Upgrade Engine (ttspt2201m000) session starts.
Fill out the fields in the session and click Continue. See the session help. Note: If a task fails during the execution of the
run, an error message is displayed in the progress bar. In case of a fatal
error, the failing upgrade program stops. All dependent upgrade programs cannot
be executed anymore. The run continues to execute all other upgrade
programs. You can solve the problem that caused the error and
start the failed task again. See Troubleshooting (OP-CE).
| |