Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

UDC ODBC Oracle. Connection String - The operation has timed out.

Hello,

I am working on the creation of UDC passing by ODBC Oracle.

System DSN is configured and I see this DSN in the HUB when I want to make a new connection.

It works.

I suppose that I have a problem in Visible Connection String or in User Table Name, Attributes Table name

Capture1.JPG

Tables Oracle:

Capture2.JPG

Driver name comes from windows ODBC DATA SOURCE ADMINISTRATOR ( 64 bit) => Drivers

UID and PWD it is an identifier for my database

DBQ it is the name of my ODBC Data Source, this name is the same in tnsnames.ora

I tested also a set of User Table Name and Attributes Table Name

  • [SCHEMA.USER_UDC]
  • [SCHEMA.”USER_UDC”]
  • SCHEMA.”USER_UDC”
  • USER_UDC
  • SCHEMA.USER_UDC

It changes nothing. I have the same message. The operation has timed out and UDC is not operational.

Thanks in advance for your help and any suggestions,

1 Solution

Accepted Solutions
Not applicable
Author

Hey Kashif,


I just resolved the issue too. You should restart all services of Qlik and restart the server.

Thanks a lot

Have a good day,

Mykhailo

View solution in original post

10 Replies
ansarikashif2017

We are also getting the same issue.

2220170517T072338.760-0400WARNP*******UserManagement.Repository.Repository.Users.Factories.UserDirectoryFactory1597315b805-7e42-4f05-9f62-bdeb339feda8NAEAST\***********************Setting up UDC'IBIEE' of type Repository.UserDirectoryConnectors.ODBC.ODBC unsuccessfulThe operation has timed out.   at Repository.Users.SafeUserDirectoryConnector.CallWithTimeout(Func`1 func, TimeSpan timeout)↵↓   at Repository.Users.SafeUserDirectoryConnector.Setup(Logger logger)↵↓   at Repository.Users.Factories.UserDirectoryFactory.TrySetupUserDirectory(UserDirectory userDirectory)7315b805-7e42-4f05-9f62-bdeb339feda8
2320170517T072338.931-0400ERRORP*******UserManagement.Repository.Repository.Users.Factories.UserDirectoryFactory34527a007ee-f606-468a-94db-7ac808161372NAEAST\*********************Error when validating tables: ERROR [HYT00] [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation↓27a007ee-f606-468a-94db-7ac808161372
ansarikashif2017

Hi @mykhailo_prosianyk,

Were you able to resolve this issue?

I raised a support ticket but no luck. Qlik Sense support is pushing this to Oracle driver issue whereas we can connect to the same Db using the same driver from all other ways.

I get the timeout error after 30seconds. What about your case? After how much time do you get the error?

Regards,

Kashif

ansarikashif2017

Hi chooco_co

Will you have some insight into this?

Regards,

Kashif

Not applicable
Author

Hi, no, I still looking for the solution

Oracle driver works good because I am able to make a Script Oracle Data Connection.

I have the error after 30 sec also

Thanks for your responses

Mykhailo

marcohadiyanto
Partner - Specialist
Partner - Specialist

Hi Kashif,

I never tried this, but you can try create an apps on hub then create connection to oracle and select your table.

After that search data connection on qmc and copy connection string from there and move it to UDC.

Hope it works.

For your reference about UDC:

https://help.qlik.com/en-US/sense/3.2/Subsystems/ManagementConsole/Content/ODBC-example.htm

Rgrds,

Marco

ansarikashif2017

Hi Marco,

Thanks for the quick revert.

I tired the steps mentioned by you but it didnt work out.The Conn string from the Data connection of QMC comes out to be a very long string with some weird parameters. But I have solved the issue. Pls see response below.

ansarikashif2017

Hey Mykhailo,

I finally resolved the issue. Please try adding the connect timeout parameter as shown below:-

Driver={Oracle in OraClient12home2};DBQ=<system DSN name>;Uid=<DB user>;Pwd=<pwd>;Connect Timeout=60;

It resolved the error for me. I had to create a System DSN and give its name in DBQ= parameter and add the Connect Timeout parameter.

Not applicable
Author

Hey Kashif,


I just resolved the issue too. You should restart all services of Qlik and restart the server.

Thanks a lot

Have a good day,

Mykhailo

marcohadiyanto
Partner - Specialist
Partner - Specialist

Hi Mykhalio, good to hear that, please mark as answer.