Exporting data to the data lake
The data lake settings are preconfigured. You can immediately export the data from the Planon application to the data lake.
Before exporting data, make sure the Data lake TSI is added to the System Settings navigation group.
For more information about the data lake settings, see Data lake fields.
Procedure
1. Go to > step and click Export to data lake.
A message appears informing that the export is started as a background action.
The data is assessed and the application calculates the number of jobs required to export the data to the data lake.
 | While the application is performing the analysis and executing the background jobs, any changes made to the Planon data will cause synchronization errors. The issues causing these errors can be resynchronized manually after the export to data lake. Note that putting business objects Under construction will cause the export to data lake to fail. |
Two things happen:
◦ Jobs are created that run as a background action.
◦ The jobs synchronize the data from the Planon database to the data lake.
2. Go to Export jobs level to monitor the jobs' progress.
For more information about the jobs, select one and go to Job details level.
Click Refresh to update the list.
After the jobs have completed, all data between Planon and the data lake is kept in sync. Updates in the Planon application will subsequently be reflected in the data lake with only a short time delay.
Recovery
 | Note that the Planon data lake does not have the same recovery policy as the Planon operational database. The Planon data lake only contains information that is available in the operational database, so it can be restored from the operational database. This means that in case of a restore of the operational database (for whatever reason), the data lake needs to be recreated as if you are starting with Planon Connect for Analytics for the first time, requiring a full initial synchronization. The time this takes depends on the amount of data in the operational database, it can be several hours. |
Synchronization disabled
Synchronization is disabled if the data lake is unreachable for longer than 1 hour or if the number of BO changes while the data lake is unreachable is greater than 1000. When synchronization is disabled, an event log is created to notify the system administrator. To enable the data lake functionality again, a new data lake export needs to be executed.