Skip to main content

Setting advanced connection properties using Oracle LogMiner

ON THIS PAGE

Setting advanced connection properties using Oracle LogMiner

This section describes which properties are available in the Advanced tab when using Oracle LogMiner to access the redo logs. For information on which properties are available in the Advanced tab when using Replicate Log Reader to access the redo logs, see Setting advanced connection properties using Replicate Log Reader.

  • Retry interval: Use the counter or type the number of seconds that the system waits before resending a query.
  • Archived redo logs destination ID: The destination of the archived redo logs. The value should be the same as the DEST_ID number in the V$archived_log table.

    When working with multiple log destinations (DEST_ID), you should specify an Archived redo logs location identifier that represents archived logs that can be accessed by Replicate. If the Archived redo logs location identifier is not specified, Replicate will use the ID specified in the Alternate archived redo logs destination ID field. If no alternate ID is specified, then Replicate will use the minimal existing DEST_ID.

  • Alternate archived redo logs destination ID: The archive destination in the event of a failure to read from the primary destination.

  • Expose NUMBER as: Select one of the following:

    • A precision-scale combination
    • FLOAT
    • VARCHAR

    Notes  

    • If precision is 39 or greater, select VARCHAR
    • By default, the NUMBER data type is converted to precision 38, scale 10
    • The "Expose NUMBER" definition in the Oracle database is used for the NUMBER data type only (without the explicit precision and scale definition)
  • Use archived redo logs only: When this option is selected, Qlik Replicate will only access the archived redo logs. If the archived redo logs ares stored on ASM only, the Qlik Replicate user needs to be granted the ASM privileges described in Required ASM privileges.
  • Support nested tables: Select this option if you need to replicate Oracle tables containing columns that are nested tables or defined types.

    For more information on this feature and its prerequisites, see Replicating Nested Tables.

  • Support invisible columns: Select this option to replicate invisible columns. This option is supported from Oracle 12c and Oracle Instant Client version 12.

Internal parameters

Internal parameters are parameters that are not exposed in the UI. You should only use them if instructed by Qlik Support.

To add internal Qlik Replicate parameters:

  1. Click the Internal Parameters link.

    The Internal Parameters dialog box opens.

  2. In the edit box, type the name of the parameter you need to add and then click it.
  3. The parameter is added to the table below the search box with its default value.
  4. Change the default value as required.
  5. To reset the parameter value to its default, click the "Restore default value" icon at the end of the row.

Settings summary

You can view a summary of your settings by clicking the Setting Summary link. This is useful if you need to send a summary of your settings to Qlik Support.

Finding the wallet entry used for TDE column encryption in a specific table

This section describes how to find the correct encryption key used for TDE column encryption in a specific table.

To find the Oracle Wallet entry:

  1. On the Oracle database, run the following query to return the object_id (e.g. the. table ID) according to a given owner and table name:

    Select object_id from all_objects where owner='<table owner>' and object_name='<table name>' and object_type='TABLE';
  2. Use the retrieved object_id in the following query to return the relevant master key:

    select mkeyid from sys.enc$ where obj#=OBJECT_ID;
  3. Select the key value from the Oracle Wallet as follows:

    mkstore –wrl <full_wallet_name> -viewEntry <entry_name>
    Note:

    For more information, see Step 5 in Finding the wallet entries used for TDE Encryption.

  4. Copy the master key entry and its value into the Names and Values fields respectively.