Need info for Oracle Autonomous Database on Azure.

[Sukanya2]

We have an existing replication setup in Qlik Replicate with Oracle as the source, using Oracle Client 19.3.0, and the following TNS_ADMIN variables are configured in site_arep_login.sh

export PATH=$ORACLE_HOME/bin:$PATH

export TNS_ADMIN=$ORACLE_HOME/network/admin

Now, for a new requirement, we need to set up an additional replication where the source remains Oracle, but the target will be an Oracle Autonomous Database on Azure.

Does the existing Oracle Client 19.3.0 support connecting to an Oracle Autonomous Database target?

For the target configuration, we understand that the wallet files need to be downloaded and the TNS_ADMIN should point to the wallet location. Since our current setup already has TNS_ADMIN defined for the source, how should we handle this for the new target connection?

Should we modify the existing site_arep_login.sh file?

Or is there a recommended way to reference both the source and target TNS configurations without impacting the existing Oracle source replication?

[Sukanya2]

Any inputs on this?

[john_wang]

Hello @Sukanya2 ,

You are correct — Oracle Client 19.3.0 can be used to connect to an Oracle Autonomous Database.

Please note that the TNS_ADMIN variable is optional when connecting to either an Oracle on-premises database or an Oracle Autonomous Database.
In particular, when using the Oracle Instant Client, you don’t need to define any environment variables — you can simply specify the connection string directly in the Qlik Replicate endpoint. For example:

• EZConnect format:

  host:port/serviceName

  (No need to include “//” at the beginning of the string.)

• Oracle Net keyword-value format:

  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dlsun242)(PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=bjava21)))

  Regards,

  John.

[Sukanya2]

Hi @john_wang 

Thanks for the inputs. Could you please confirm the role of SQLNET.ORA? The guide mentions it should specify the wallet location for connecting to the Oracle target database on Azure. Is it possible to simply append the necessary wallet-related entries to the existing sqlnet.ora file to enable the target connection?