What do I do if an issue occurs during the data transfer?

If a step fails or the data transfer is interrupted, the error appears in the SQL*Plus window. The reason for failure determines your next step. Next steps include:

• Resuming the data transfer.

  For more information, see Resuming the data transfer.

• Editing the etl.properties file, dropping the destination account, installing again, and starting the data transfer over again.

  For more information, see Installing and transferring data again.

  Data transfer issues and possible solutions

  Issue	Resolution
  You see in the SQL*Plus window that the data transfer has been interrupted.	Reconnect to the network, and resume the data transfer.
  A step, such as an import step, the validate step, a transformation step, or the Create Config step fails. A transformation step begins with X-, such as X-Schema.	Query the ETL_STATUS table to determine the last step that was processed. The last step that was processed has a status of InProgress. Review start_etl.log for errors or messages, and correct the errors. Edit the properties file and start over, or resume the data transfer: If you change the value of a property in the etl.properties file, you must drop the destination account, install the ETL utility again, and start the data transfer over again. If your fix does not involve changing the etl.properties file, resume the data transfer.
  The log file says that a table creation issue has occurred.	Specify the correct source tablespace. How to troubleshoot: Check that the source_tablespaces property in the etl.properties file includes a comma-delimited list of the names of both tablespaces in the source account. Edit the properties file and start again. If you change the value of a property in the etl.properties file, you must drop the destination account, install the ETL utility again, and start the data transfer over again.
  A step fails with an out-of-space error.	If the process failed because you ran out of tablespace for the destination account, fix the tablespace issue, and resume the data transfer.
  The data transfer was successful, but some column names were renamed.	If you added columns to the OMOP Common Data Model, the column names might have collided with the columns added by the ETL utility. If a collision occurred, the existing source column names were renamed in the destination account. Columns are renamed to SRC_<original_name>. You do not need to take any corrective steps.