DT314 Migration rule

DI062142 UUID

Primary key of this table in the form of a Universally Unique Identifier

DI062195 Last run

Displays the value from the Time field for the last execution of this migration packet

DI062152 Created on

Contains the date on which the migration packet was imported into the system

DI062327 Packet release

Shows to which release this packet belongs

DI062324 Short description

Contains a phrase that briefly summarizes the information on the migration packet.

DI062325 Description

May contain a longer description of the migration packet

DI062328 Packet name

Contains the name of the migration packet. This corresponds to the name of the Python class.

DI062154 Version

Version of the packet

DI062155 Python path

Path to the Python class

Example

• The standard migration packets of version S 39.5.0 are located under .../migration/planta_de/S_39_5_0/...

DI062156 Upon system start

Specifies whether the packet is to be run when the server is migrated

DI062157 Completed

Indicates whether the migration package has been completed, regardless of whether the migration packet was automatically completed during the migration or was manually marked as completed.

DI062326 Packet category

Specifies whether the packet is a help packet, a mandatory packet or an optional packet

DI062200 Traffic light: Last status

Traffic light which indicated to which status the package was set after the last run

Legend

• 

  signalizes that this migration packet has not yet been executed.

• 

  means that the migration packet has run successfully.

• 

  signalizes that this migration packet is still pending and waits for another migration packet to reach a certain status before it can be executed.

• 

  Signalizes that this migration packet is not relevant for the current update type due to version dependencies.

• 

  signalizes that the migration packet has failed. There may be several causes for a packet to fail:
  • Many migration packages check whether the customizing on which the fix is based has changed before they are executed.
    • If this is the case, the change to the package is not made and the package is deemed to have failed.
      • In such a case, you have to check in the customizing whether and how the respective change can be made.
      • If the change has been made or if the change is not necessary, the package can be manually set to completed by activating the Completed checkbox.
      • This will move it from the Failed/pending packets area to the Completed Packets module.

• Many auxiliary packets check the customizing for problems.

  • If they fail, this means that the customizer must act.
  • The locations listed in the log file must be checked and adjusted if necessary.
  • Once the cause of the failure has been eliminated, the migration packet can be executed again by clicking on the Execute packet button in the Overview of All Previous Runs module.

DI062187 Traffic light: Valid Python path

Traffic light DI which specifies whether the value in the Python path field points to a migration packet

DI063718 Minimum database version

Specifies the lower minimum value of the database version that must be present for the specified migration packet to be classified as relevant and executed.

DI063719 Maximum database version

Specifies the upper maximum value of the database version that must be present for the specified migration packet to be classified as relevant and executed.

DI064804 DBMS dependency

Indicates whether the packet is dependent on a database management system.

Values

• DBMS independent
• Oracle
• MSSQL
• Invalid DBMS

DI064805 Dependency: Expected status

Traffic light for the visualization of the expected status of the packet on which the current package depends.