Mecanismo de upgrade de dados overviewThe Data Upgrade Engine (DUE) is used to update the customer data after a Feature Pack (FP) upgrade. To perform a data upgrade, you must execute a Data Upgrade Run. In some situations, LN automatically generates a data upgrade run. You can also manually create data upgrade runs. Each data upgrade run belongs to a particular package combination and performs a data upgrade for one or more companies that are linked to that package combination. A data upgrade run consists of upgrade tasks. Each task executes one upgrade program for one company. Each upgrade program upgrades a particular table. Exemplo Companies 410 and 411 are linked to package combination b61ua6. Data upgrade run 19 is linked to package combination b61ua6 and contains these upgrade tasks:
Nota You do not have to upgrade all companies of a package combination in one run. You can define multiple runs for different companies of the same package combination. For example, you can define different runs for live companies and for test companies, and execute these runs at different times. See the following example. Exemplo These companies are linked to package combination A:
You define these runs for package combination A:
See this figure: ![]() Data upgrade runs are executed in these situations:
Nota If a data upgrade run is generated, or created manually, the involved companies are locked. Normal users cannot access these companies anymore. In the Companhias (ttaad1100m000) session, these companies have the Atualização necessária status. You can start a run in simulation mode: the Data Upgrade Engine will run the upgrade without actualizing the transactions. Execution During a data upgrade run, various upgrade programs are executed. Some upgrade programs must have finished successfully before another program can start. To enhance the performance of the data upgrade process, you can run the DUE using multiple bshells. In this case multiple CPUs can be utilized. The DUE gathers the list of upgrade programs that must be executed and spreads the work over the different bshells. When you start a data upgrade run, you can specify the number of bshells you want to activate. The sequence in which the upgrade programs are executed depends on:
For details on how to create and execute a data upgrade run, see Executing a data upgrade run. Simulation mode You can start a run in simulation mode. During a simulation, the Mecanismo de upgrade de dados runs the upgrade without actualizing the transactions. This is useful for testing purposes. See the online help of the Data Upgrade Engine (ttspt2201m000) session. Performance and finetuning You can optimize the performance of the Mecanismo de upgrade de dados. See Performance and finetuning. Troubleshooting If one or more upgrade programs fail during a data upgrade run, use the troubleshooting procedure. See Troubleshooting. Error Recovery Each upgrade program runs in a separate process. The upgrade programs can return status information about the success or failure of the execution. Some statuses interrupt a part of the upgrade process. Other statuses only inform you that something went wrong, or that the upgrade program was executed successfully. If a fatal error occurs, such as error 606, "reference not found", only upgrade programs that are dependent on the failing upgrade program cannot be executed anymore. All other upgrade programs can still be executed. Logging Upgrade programs can generate reports of errors and changes. When you start a data upgrade run, you can indicate that only errors should be reported. You can access log information from the Data Upgrade Tasks (ttspt2520m100) session.
| ||||||||||||||||||||||||||||||||||||