SA Tenant Refresh - Data Import Report overview

System Administrator > Administration > SAA Reports > SAATI

Function acronym: SAATI

Use this report to import data from a source environment, such as a production environment, to a target environment, such as a training or testing environment.

This report deletes the data in existing tables in the target environment and replaces it with the data from the source environment. The replacement data is contained in the zip file that was created by the SA Tenant Refresh - Data Export Report. The largest tables are loaded inside the threads first to maximize the time that the threads are in use.

Caution: 
When you run this report, all data in the target tenant is overwritten. Before you start the import, confirm that you reviewed the data in the target tenant. Copy or export any important data so that you can restore the data in the target tenant after the cloning process is complete.

Only zip files that are fewer than 25 days old are eligible for import. Zip files and related data files are deleted from the TenantRefresh directories after 25 days. Old files are also deleted each time you run the SA Tenant Refresh - Data Export Report or the SA Tenant Refresh - Data Import Report. This ensures that only the most recent files are available for import.

Note: Do not use the expire date for the zip file that is included in export.YYYYMMDD.log to determine if the file is eligible for import. This date is used to determine when the file is unavailable for use in S3.

The Elasticsearch and word indexes are automatically rebuilt in the target tenant when you run the SA Tenant Refresh - Data Import Report. As soon as a table that is related to a Elasticsearch or word index is loaded, it is validated by a conversion process. The appropriate report, SA Index Rebuild Report, SA Word Index Rebuild Report, or both, is then run for the index table. The SA Tenant Refresh - Data Import Report remains active for up to 5 hours after the last import so that conversions can finish. After 5 hours, Report Scheduler remains in 'import mode' to process any remaining conversions, and to run the SA Word Index Rebuild Report and SA Index Rebuild Report.

Note: If all tables related to Elasticsearch will be imported into the target tenant when you run the SA Tenant Refresh - Data Import Report, then the existing Elasticsearch data is cleared before the new tables are loaded. If only a subset of the tables will be loaded, then the existing data is not cleared.

Report logs are emailed every 30 minutes during the import process and at its completion. The reports are sent to the email address that you specify in the Printing Information section on the Information page of the report. If you do not specify an email address on the report, the logs are sent to the email address on your SA Operator Setup record.

If a data in a table fails to delete or load during the import process, an error occurs. Contact Infor Support for assistance.

You must have security level of 5 on your SA Operator Setup record to run this report.

Maintenance windows

These maintenance windows affect when you can perform a refresh:

  • Non-production update

    Typically, the non-production update is scheduled for the second Friday of the month. Three days before the non-production update, a programatically enforced moratorium prevents you from refreshing an environment. The moratorium ensures that the updates are performed within the scheduled maintenance window. It also ensures that your data imports are completed without interruption.

    If you attempt to run the SA Tenant Refresh - Data Import Report during the moratorium, the import is aborted and you receive these error messages:

    • Preproduction update happening within 3 days.
    • Tenant Import has been cancelled.

    You can reschedule the after the update is complete.

  • Production update

    Typically, the production update occurs the third Saturday of the month. During the eight days between the non-production and production updates, the refresh process is subject to a version check. If the version is different between the source and target environments, the refresh process is prevented because it can cause data load errors due to a mismatched database schema.

    To check the version, select More > Advanced > About in the navigation menu bar of Distribution SX.e.

See the Infor CloudSuite Distribution Configuration Guide.