This section describes how to configure general connection properties. For an explanation of how to configure advanced connection properties, see Setting advanced connection properties.
To add an Oracle source endpoint to Qlik Replicate
- In Tasks view, click Manage Endpoint Connections to open the Manage Endpoints Connections dialog box. Then click the New Endpoint Connection button.
- In the Name field, type a name for your database. This can be any name that will help to identify the database being used.
- In the Description field, type a description that helps to identify the Oracle database. This is optional.
Select Source as the database role.
Select Oracle as the database Type.Information note
When this endpoint is used as a duplicated source in a Log Stream Staging setup, select the Read changes from log stream check box and then select the relevant Log Stream Staging task from the drop-down list.
For information on setting up and managing Log Stream Staging tasks, see Using the Log Stream.
Type the Oracle Connection String for the Oracle database you want to work with. You can type the connect string in any Oracle format, for example:
host: This is the name or IP address for the computer with the Oracle database that you are using. For example,
port: (optional) This is the TNS Listener Port number for the computer with the Oracle database that you are using. If you do not enter a port number the default Oracle TNS Listener port is used.
service name: (optional) This is the service name for the computer with the Oracle database you are using. If you do not enter a service name the default service name is used.
You can also enter an Oracle Net keyword-value pair. For example:
"(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=dlsun242) (PORT=5521))
Type the Oracle authentication information (User Name, Password) for the authorized user for this Oracle database. If you do not know this information, see your Oracle database Administrator (DBA).Information note
This information is case sensitive.Information note
Make sure that the Oracle user entered in the Oracle Authentication section has the correct access privileges. For information on how to provide the required privileges, see Required permissions.
To ensure that the password provided to Replicate is never used by any other principal, Replicate can be configured to automatically replace the user-entered password with a strong random password. For more information, see Configuring Replicate to Automatically Replace the User-Entered Password.
Working with RAC Instances
This section describes the different procedures that apply when working with RAC instances.
If the Oracle endpoint is configured to use Replicate Log Reader and the node to which Replicate is connected cannot access the logs created by the other cluster nodes, you need to specify a separate connection string for each RAC instance.
When the redo logs are stored in ASM, the connection string syntax is as follows:
[<common ASM connection string>,] <thread id> <thread ASM connection string>, <thread id> <thread ASM connection string>...
<common ASM connection string> is specified, all the RAC instances should be defined in the ASM connection.
When using Replicate Log Reader to access the redo logs, the connection string syntax is as follows:
<Oracle connection string>[, <thread id>, <thread BFILE connection string>, <thread id>, <thread BFILE connection string> ...]
<Oracle connection string> is mandatory. If specified, the <
thread BFILE connection string> will be used instead of the
<Oracle connection string>.
Capturing changes after a RAC switchover
If you need to run a switchover procedure on your RAC environment with multiple standby nodes, do the following steps to ensure the continuity of CDC.
Run a task using the primary RAC node as a source.
Stop the task.
Do the switchover procedure. This changes your primary RAC node to a standby role and makes your standby node your primary RAC node.
Change the credentials to those of your new primary RAC node.
Resume the task. All the events that were triggered when the task was stopped will be replicated automatically and the changes will be captured accordingly.