Skip to main content

Qlik Replicate

Discussion board for collaboration on Qlik Replicate.

Announcements
NEW webinar Dec. 7th: 2023 Outlook, A Pivotal Year for Data Integration SIGN ME UP!
cancel
Showing results for 
Search instead for 
Did you mean: 
GonzaloPerezPrim
Partner - Contributor II
Partner - Contributor II

Qlik Replicate propietary Log Miner Security access

Hi Guys:

We are trying to find documentation which explain how the Qlik Replicate propietary Log Miner security access  at Oracle is working in terms of security access.

I presume that it is based on the Oracle security but do you know if there are a set of authorizations to protect the data security or how data security is managed? I understand that it is a broad topic, but could you point me to the right documentation.

Kind regards

Gonzalo Perez-Prim

1 Solution

Accepted Solutions
Ted_Manka
Support
Support

Hello Gonzalo,

When you say "Qlik Replicate propietary Log Miner" Replicate has two methods either the proprietary Log Reader (sometimes refered to as Binary Reader) or the Oracle Log Miner.  It seems like you might be blending the two together?

The Replicate Oracle source endpoint can be configured to access online and archived Oracle redo log files using either Oracle LogMiner (Oracle’s built-in method) or Qlik Log Reader (Replicate’s high-speed redo log reader).
Generally, it is recommended to use Qlik Log Reader as it is more efficient, faster, and uses less resources.
Qlik Log Reader is especially recommended in the following situations:
1. The volume of changes in the redo log is more than 30GB/hour
2. The volume of changes is between 10GB/hour and 30GB/hour and the changes need to be processed (i.e. replicated to the target) as fast as possible.
3. There are multiple tasks replicating from the same source. Using Oracle LogMiner is less efficient in this case, as it accesses the redo logs via the database, thereby consuming additional database resources.
Both Qlik Log Reader and Oracle LogMiner are subject to certain limitations, support different compression methods, and require different access permissions. It is therefore strongly recommended to review the relevant sections before configuring the endpoint settings. In the end, your decision whether to use Qlik Log Reader or Oracle LogMiner may be based on a limitation that exists in one but not the other, the way your data is compressed, or the permissions that you are willing to grant the Replicate user.

 

Thank you,

Ted Manka

View solution in original post

1 Reply
Ted_Manka
Support
Support

Hello Gonzalo,

When you say "Qlik Replicate propietary Log Miner" Replicate has two methods either the proprietary Log Reader (sometimes refered to as Binary Reader) or the Oracle Log Miner.  It seems like you might be blending the two together?

The Replicate Oracle source endpoint can be configured to access online and archived Oracle redo log files using either Oracle LogMiner (Oracle’s built-in method) or Qlik Log Reader (Replicate’s high-speed redo log reader).
Generally, it is recommended to use Qlik Log Reader as it is more efficient, faster, and uses less resources.
Qlik Log Reader is especially recommended in the following situations:
1. The volume of changes in the redo log is more than 30GB/hour
2. The volume of changes is between 10GB/hour and 30GB/hour and the changes need to be processed (i.e. replicated to the target) as fast as possible.
3. There are multiple tasks replicating from the same source. Using Oracle LogMiner is less efficient in this case, as it accesses the redo logs via the database, thereby consuming additional database resources.
Both Qlik Log Reader and Oracle LogMiner are subject to certain limitations, support different compression methods, and require different access permissions. It is therefore strongly recommended to review the relevant sections before configuring the endpoint settings. In the end, your decision whether to use Qlik Log Reader or Oracle LogMiner may be based on a limitation that exists in one but not the other, the way your data is compressed, or the permissions that you are willing to grant the Replicate user.

 

Thank you,

Ted Manka