Linux

Install and configure the runtime server for the Source and Target on Linux.

Before you prepare your environment, it is assumed that you have downloaded the runtime engine.

Note: Listener must be stopped prior to reconfiguration.

Prior to installing Data Integration on a host:

Ensure that the file system where Data Integration is installed has at least 1 Gigabyte of disk space.
Database JDBC drivers must be installed on the installing host for non-Windows platforms.
Oracle Unicode target column values replicated to the target column can be truncated because the XML length is incorrect. To avoid this issue ensure that you use the following JDBC driver versions for Unix:
For Oracle 11g use 11.2.0.4 and above.
For Oracle12c, 18c, or 19c use 12.0 and above.

Note: The location of the JDBC drivers since they are needed during the install. Data Integration uses JDBC for connectivity. The user is required to obtain the chosen JDBC driver.

J2SE must be installed on both the installer and recipient hosts, for non-Windows platforms.
The PATH environment variable must be set up non-Windows platforms.
The following TCP/IP daemons must be available:
For remote installs, the FTP server must be running on the recipient host and an FTP client must be running on the originating host where the installer is run.
For remote installs and for installing Listener as a startup script, the rexec daemon must be active on the recipient host.
The GUI Installer must have access to the tmp directory since install attempts to detect an existing install of Data Integration on the installing host by creating a file in a well-known writeable system directory. The directory is the temporary I/O directory provided by the Java system property java.io.tmpdir. The file is either a link to the <host_name>.properties file in the host install directory, or a copy.


Platform	Temporary Directory	File Type
UNIX	/usr/tmp	Link to <host_name>.properties
Linux	/usr/tmp	Link to <host_name>.properties

License File

You will receive a license file in an email. The initial Data Integration install may be done without the license file. It is, however, required before you can commit a model.

Rename the Data Integration license file that you received to omnilicense.
Save the license file to the Kernel subdirectory. For example:

C:\PreciselyConnect\ConnectCDCV58\kernel\omnilicense

where omnilicense is the licensing file name.

Keep in mind the following when working with license files:

The license file has no extension.
If you FTP the license file, you must specify that the file is binary.
The Install Wizard will process the license file.

Database or Platform-specific setup tasks

Oracle

If you plan to install and use Data Integration in a configuration where Director will run on a different host than the one on which Oracle is installed, Data Integration requires the use of the sys user ID. The sys user ID must have privileges to create a database and is used only when you install the SQL metabase.

Oracle requires:

The sys user ID to be logged in with SYSDBA privileges.
A password file when a user logs in remotely with SYSDBA privileges. If you do not have a password file, it must be created before you start modeling in Director.
Shut down and restart Oracle when you create a password file.

Note: Since the Oracle DBMS must be rebooted once the password file has been created, prior planning is required to accomplish this essential step.

The database initialization parameter OPEN_CURSORS must be defined at a minimum of 50 if any Replication or Synchronization request contains a bidirectional mapping to an Oracle server. If the number is less than 50, you may receive the Oracle error message indicating you have exceeded the maximum number of cursors if you have many bidirectional mappings to an Oracle server.

Before you use the Change Selector

You must do the following setup activities before you can use the Oracle Change Selector:

Archive mode - Running in archive mode is a requirement for replication. If archive mode is not enabled during startup, the Change Selector issues an error and shuts down.

Additionally, the automatic archival option must be enabled by setting log_archive_start = TRUE in the Oracle parameter file and restarting the database. Data Integration cannot do this automatically because Oracle does not provide a way to do this programmatically.

Note: These parameters reside in SPFILES. For more information refer to http://www.orafaq.com/wiki/SPFILE

Storage requirements - The log-based changed data capture requires supplemental logging. Extra storage may be required for supplemental logging depending on a number of factors such as, the number of tables being replicated, the number of columns replicated within those tables, the size of the rows within the table and the overall volume of updates against replicated tables.

The best practice is to monitor the actions on the tables and to determine if the database continually requests more archive space. If so, then storage must be increased.


Statement	What happens to the redo logs
Inserts	No additional information is written to the redo logs.
Deletes	Additional information, which includes the old column for all replicated columns, is written to the redo logs. Without supplemental logging, normally only the old values for the key columns are written to the redo log. As a result of this additional information in the redo logs, more archive logs may be generated. These archive logs must be kept until they are no longer needed for replication and have been saved for backup.
Updates	Additional information, which includes the old column for all replicated columns, is written to the redo logs. Without supplemental logging, normally only the old values for the key columns are written to the redo log. As a result of this additional information in the redo logs, more archive logs may be generated. These archive logs must be kept until they are no longer needed for replication and have been saved for backup.

Privileges - If you plan to retain archive logs, the user who starts the kernel must have the privileges to create files in the primary Oracle archive destination directory.

This privilege is only required when you specify that you want to retain archive logs, as specified for the Oracle parameters during the install. For each processed archive log, Data Integration creates an empty file using the same archive name with the “.repdone” suffix appended to the name as a means to determine which logs Data Integration has processed. These logs can thus be backed up and deleted.

The user who is to use “Delete unneeded archive logs” needs delete privileges on Oracle’s archive log files.

When delete archive logs is specified Data Integration does not create the empty files. However the user must have the privileges to delete the archive log files.

If you plan to use Oracle’s fast loader, you must specify Oracle’s bin directory in your path. For information on the fast loader.