Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
I have been trying to get UDC operational using an Oracle DB but not able to succeed. UDC is behaving inconsistent. It connected once and created the users stored in the DB table but it stopped working after that. After lot of debugging I added a Connect Timeout paramter to the visible conn string and it worked for a day or two but it stopped working again.
I am using the below conn string :-
Driver={Oracle in OraClient12home2};Dbq=<TNSEntry name>;Uid=<DB user>;Pwd=<pwd>;ConnectTimeout=60;
or
Driver={Oracle in OraClient12home2};Dbq=<ODBC DSN Name>;Uid=<DB user>;Pwd=<pwd>;Connect Timeout=60;
none of which seems to work. I keep getting below error after 30 seconds:-
Operation has timed out.
The log has the below error :-
ORA-01013: user requested cancel of current operation
I am able to connect to the same DB user using DB Client tool like Toad or SQL Plus and query the tables. Even tnsping to the Tns entry works fine.
Any pointers much appreciated.
Calling out korsikov , gwassenaar, jog, mto for any insights?
sorry but i not has any idea about this problem. And does not has Oracle environment to reproduce this situation
Hi Guys,
Any one has any insights in solving this?
Regards,
Kashif
Any reference to any Qlik Engineer who deals direclty with DB connectors?
Hi Kashif,
The Property your referring here ConnectTimeout=60 is not known to Oracle ODBC
I hope for refernce you can look into more properties here.
QTO | Query Timeout Option | T=Query Timeout Enabled. F=Query Timeout Disabled. |
To achieve your request i would request you to have a try with below requests:
Driver={Oracle in OraClient12home2};Dbq=<ODBC DSN Name>;Uid=<DB user>;Pwd=<pwd>;QTO=F;
//Suraj
Hi Suraj,
Thanks for the reply. Same thing was sugegsted by Qlik Support engineer but didnt help. Finally the support engineer spotted a timeout error which seems to have been fixed in 3.2. We would need to upgrade to 3.2.
Regards,
Kashif
Hi all,
I am using an access database for my User Directory Connector and came across this problem. the solution was to clear out the 'Synchronization timeout (seconds)' field and re-enter the number (Example: 300 or 500).
That worked for me, hope this helps.
Keep Qlikin
Anderson