Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
While connecting Qlik Replicate (6.6.0.384) to Oracle 12.2.0.1.0 we are getting the below error,
Below is the characterset parameter set in oracle,
NLS_CHARACTERSET
AL32UTF8
Thank you in advance!!
Regards,
Sagar Puri
Hey Sagar,
Yeah the issue is resolved now. The file that was in System32 was moved but it didn't reflected unless the Server was restarted. Post which this issue was resolved.
Thanks for the Help.
Thanks,
Bhavin
Hi @kishetty03 ,
Not very sure your RHEL env however if possible, you may remove the existing Oracle client installation and then re-install instant client , it's easy and no need to config TNS or anything, you can use it directly in Qlik Replicate.
In general 2 packages are good enough (choose a version which suited your Replicate version), for example 2 below files in page download Version 19.17 :
oracle-instantclient19.17-basic-19.17.0.0.0-1.x86_64.rpm
oracle-instantclient19.17-sqlplus-19.17.0.0.0-1.x86_64.rpm
where SQL*Plus is optional, it can be used to test the connectivity eg "SQLPlus scott/tiger@<ip>:<port>/<inst>".
Adds the instant client lib library to LD_LIBRARY_PATH in file "site_arep_login.sh" file see Install Oracle Instant Client for Linux (x86-64) Version 12.0 or later , then restart Replicate services.
Hope this helps.
Regards,
John.
Hello @sagar_puri ,
Good day. In general this error caused by Oracle client installation/configuration. Please let us know more detailed info:
1. The Replicate Server platform (Windows , or Linux)
2. The Oracle client installation type and version
The Oracle Instance Client is highly recommended if your replication data type does not include XMLTYPE.
3. The best practice is using SQLPlus to do troubleshoot. If SQLPlus client (sits on Replicate Server) program can establish the connection to Oracle server successfully then Replicate should work too.
If SQLPlus does not work either, you can remove the existing Oracle client and install a fresh Instance Client. This is a pure Oracle client/server issue.
4. If you need additional assistance please attach task log file, or repsrv.log.
All the Best,
John.
Hi John,
Please find the details ,
Also we are able to successfully connect to Oracle server using SQL*Plus.
Please find the repsrv.log and NLS Parameter of Oracle.
Thanks,
Sagar Puri
Hi @sagar_puri ,
Can you let me know what's your connection string in the SQLPLus ? how about if you use the same connection string in Replicate?
From server log file I saw:
2020-11-06T14:18:11:576726 [SERVER ]I: Going to connect to Oracle server localhost:1521\orcl.5bfzmyo25mfutjqfmvvj0cmrya.rx.internal.cloudapp.net with username system (oracle_endpoint_imp.c:1294)
it means the Oracle sit on the as same server as Replicate. is that right?
thanks,
John.
Hi John,
Yes Oracle and Replicate are on the same server.
Also, we are using the same connection string that which we are getting in SQLPLUS. We are able to connect to Oracle SQL Developer too using this string.
Thanks,
Sagar
Hello,
Can you try this -
Please check if oci.dll is under SYSTEM32. If yes, can you remove this file? We saw a similar case before and when this file is removed, it solved the issue.
This problem is hard to trace because sqlplus works fine. Even re-install Oracle client still does not help. So, if you find the symptoms below,
- NLS error but cannot find any ORA-xxxx code in the repsrv.log
-
then please check oci.dll if it exists in SYSTEM32.
Thanks,
Lyka
The same problem occurred when i tried this.
I also got the same error without having oci.dll file in SYSTEM32 Folder. Is this issue resolved ?
Hi Bhavin,
We are not facing this issue anymore.
Try upgrading your Replicate version to more recent one if you haven’t already, also do a global search for OCI.dll file on your machine and remove it from all the folders.
In my case we had few old copies of the file in Bin, deleting them did the trick.
Regards,
Sagar
Hey Sagar,
Yeah the issue is resolved now. The file that was in System32 was moved but it didn't reflected unless the Server was restarted. Post which this issue was resolved.
Thanks for the Help.
Thanks,
Bhavin