Cross-Release Packets MOD009CEP

Access

Information

This module contains release independent and cross release migration packets.
- The RebuildTableIndicesVenusMSSQL migration packet creates a new construction of the indexes under MSSQL in order to improve performance. It can be run any number of times.
- The FillMigrationruleTable migration packet serves to search for individually written packets in the file directory, save them in the database and load them in the module.
- The CreateFolderPacket migration packet creates an import wrapper for all Python files and packets in order for them to be available for the PLANTA Server. Further information

Buttons and Links

Via the Read packet from file system button, individually written packets can be searched in the file directory and be loaded in the module.
Migration packets with Upon system start = will automatically be run after update via installer when the Run migration? parameter has been set accordingly.
For migration packets that are not run automatically you also have the option to switch to the Overview of all Previous Runs module by clicking on the link on the packet name.
- There you can run the packet and have a look at further information about it (e.g. logfile of the runs, etc.).

Legend

indicates that the migration packet has not been run yet.
indicates that a migration packet has run successfully.
indicates that this migration packet is still open and waits for another migrationpacket to reach a particular status before it can be run.
indicates that this migration packet is not relevant for the current update type due to version dependencies.
indicates that the migration packet has failed. The failure of a migration packet may have several reasons:
- Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
  - If this is the case, the packet will not be run and is considered failed.
    - In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
    - If the modification was carried out or the modification is not necessary, the packet may be set to completed manually by activating the Completed checkbox.
    - As a result, it is moved from the Failed/open packets area to the Completed Packets module.

Many help packets check the customizing for problems.
- If they fail, this means that there is work to do for the customizer.
- As a result, the positions listed in the logfile have to be checked and modified.
- If the cause for the failure has been fixed, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.