Prerequisites and information to collect before you begin

For information about the requirements for the OMOP Common Data Model, see Requirements for the OMOP Common Data Model.

Information to collect for all installations

• The name of the tablespace in the Empirica Healthcare Analysis database where the imported data for the destination account will be stored. Oracle recommends using separate tablespaces for the imported data and the main Empirica Healthcare Analysis data.
• User name for each of the following accounts:
  • Data account in the source database.

    This account contains data and sometimes vocabulary information.

  • Vocabulary account in the source database, if the vocabulary account is separate from the data account.

    This account contains vocabulary information if the information is not included in the data account.

• The names of the tablespaces used by the accounts in the source database.
• Connect string to the Empirica Healthcare Analysis database from the server on which you will be running the ETL utility.

Additional information to collect for importing using a database link

• Password for each of the following accounts:
  • Data account in the source database.
  • Vocabulary account in the source database, if the account exists.
• Value of the global_names initialization parameter in the Empirica Healthcare Analysis database.

  To determine the value, in SQL*Plus, type the following command:

  SQL> show parameter global_names;

• If the value of the global_names initialization parameter is TRUE, obtain the global name of the source database using the following command:

  SQL > select * from global_name;

• Connect string from the Empirica Healthcare Analysis database to the source database.

  The connect string is either a net service name or an EZCONNECT connection.

  If the value of the Empirica Healthcare Analysis database parameter global_names is TRUE, the net service name used to connect from the Empirica Healthcare Analysis database to the source database must use the source global_name.

Additional information to collect for importing data using files

You created the data files and import directory when you exported source data. For more information, see Exporting source data and making the data files accessible.

• Name of the data file you exported from the source database.
• (If the vocabulary account is separate from the data account) Name of the vocabulary file you exported from the source database.
• Location of the import directory on the Empirica Healthcare Analysis database server. You can use an existing directory or create a new directory. For instructions on creating a directory, see Exporting source data (Only for importing using files).

Prerequisites for all installations

• Empirica Healthcare Analysis Release 1.0.2 or later must be installed.
• The data you are transferring must use the OMOP Common Data Model Version 4.
• The Empirica Healthcare Analysis database must have sufficient available tablespace for the data and vocabulary information that is being transferred.

  The Empirica Healthcare Analysis database requires approximately 2.5 times the amount of space required for the source tables. You can use an existing tablespace or a newly created tablespace.

• You must have access to a privileged account, such as sys or system, for logging in to the source database.

  The account must have privileges to create and edit a user and grant basic privileges.

• If you are working on a network that limits your connection time, the limit must be greater than the time required for each step to complete.

  Different factors affect the time required for each step. Oracle recommends working on a network with no limits for connection times.

Additional prerequisites for installations using a database link

If the value of the Empirica Healthcare Analysis database parameter global_names is TRUE, the following prerequisites apply:

• The source data account and the source vocabulary accounts must be in a single account. If they are not, you must copy the CONCEPT table in the source vocabulary account into the data account before installing.
• The source database global name must contain a domain component, for example, orcl.us.acme.com.