Repository navigation
Action tracker
Oleg Gurov edited this page Sep 2, 2020
·
9 revisions
When the database conversion (migration) is started for the first time, four tables are created in the target database containing information about all applied packets, their steps and actions. This allows to save state of the applied packets and their statuses, and also allows to resume migrations in case they were interrupted abnormally or stopped by operator.
The dbc_packets table consists of fields:
-
name- the name of packet being executed -
status- packet status. Possible values: -
-
started- the conversion for this package has been started, but not completed, i.e. may have been interrupted or is in progress
-
-
-
exception- an exception occurred during conversion
-
-
-
done- deployment completed successfully
-
-
dt- date and time of the 1st start of conversion -
packet_hash- hash of all packet contents -
meta_data- jsonb format field to which the content of themeta_data.jsonfile is written