Importing database data
Use this procedure to import data to the database, for example, previously exported data.
-
Right-click your environment and select Database > Import Database Data.
You can also open the task by clicking Database > Import Database Data on the dashboard.
-
Perform either of these options depending on the status of the
environment:
-
If the environment is running, the message "Set M3 BE in maintenance mode" is displayed. Click Next.
-
If the environment is stopped, the environment will be started in maintenance mode.
Note: The environment is in maintenance mode until the application is stopped, started, or set online.
-
- Specify the user ID and password of the database administrator.
- Click Next. The Select Configuration Option window is displayed.
-
Select one of these options:
- Import Database Data
-
Select this option if you want to import specific data.
- Import Database Data using saved configuration
-
Select this option if you want to import specific data using saved configuration.
Note: It is recommended to save the settings or configuration related to certain data, such as tables, that you use frequently to prevent you from providing the same data over and over again. - Delete configuration
-
Select this option if you want to remove a saved configuration.
When the second and third options are selected, the Configuration field is enabled. It allows you to use or delete a saved configuration.
- Click Next. The Select data files window is displayed.
-
Select the source zip files to import. There are two
panes. The upper pane contains a list of source zip files uploaded
to LCM server. The lower pane contains source zip files stored locally
on your server.
It is possible to select several files. Select the Sort and filter source zip files check box to filter the list of available files depending on installed fixes.
Files will be sorted in this order:
-
Data zip files that are uploaded through Upload M3BE Packages, for example,
IA_DIS_1512_ XML.zip
-
Data zip files that are exported, for example,
exported_data/cpm900.zip
-
Components in alphabetical order. Then, the source zip files per component will be sorted in this order:
-
Base delivery data, for example,
MVX/15.1/delivery_data.zip
-
Base language data for all languages, for example,
MVX/15.1/languageS/delivery_data_ SE_1.zip
, sorted by language in alphabetical order -
FP delivery data, for example,
MVX/15.1/VFix/delivery_data_FP1.zip
, sorted by FP order such as FP1, FP2, FP3, and so on -
FP language data for all languages, for example,
MVX/15.1/VFix_deltalanguages/ delivery_data_FP1_GB.zip
, sorted by FP order and language in alphabetical order -
MCE and MCP language data for all languages, for example,
MVX/15.1/TFix_ deltalanguages/TFix_MVXCONGB_JT-826579.zip
, sorted by the order in which the MCEs were applied. When filtering is enabled, the view shows only the applied MCEs' data.
-
-
- Click Next. The Table Selection window is displayed.
-
Specify this information:
- Component
-
Select a component. For an additional component, select the component specified in the Environment Configurator Components pane (MNS104). For standard M3 BE without any modification, select the MVX component.
- Database schema
-
Depending on your selection of component, the correct schema is displayed in this field.
- Options
-
Select one of these options for Table selection:
-
Import all tables - Imports all the tables.
-
Enter table name - Imports one specific table. Specify the name of the table.
-
Select tables - Displays all tables in a list from where you may select the tables to import data from.
-
- Click Next. The Import Strategy window is displayed.
-
Specify this information:
- Replace existing records
-
The records in target that have a duplicate in the source are replaced by the ones imported.
- Keep existing records
-
The existing records in both source and target are left unchanged in the target.
- Copy tables without checking for duplicate keys
-
All records will be inserted without checking for duplicate keys. This can cause an exception if records already exists.
Note: This option is recommended when the target database is empty and in other situations when there is no risk of duplicate keys. This option increases the copy data performance significantly. - Clear target tables before import
-
For tables that exist in both source and target, data are cleared in target tables before import.
- Allow data mismatch
-
Select this option to allow the format of the existing table and the imported tables to differ without causing any errors.
- Click Next. The Save Configuration window is displayed.
- Specify a unique name for the configuration. The configurations for Import Database Data are saved in the M3BE file structure in M3BE\_db_data\configuration\import\.
- Click Next. The Summary window is displayed.
- Verify the values provided and click Finish.
- When the task is finished, a window is displayed. Click OK or click View log. You can also go to the Logs tab to view the log file.