11 Replies Latest reply: Apr 26, 2017 3:41 AM by Rama Sai RSS

    Qlik ODBC Connector problem

    Markus Mortsiefer

      Hallo,

       

      Im using the new Qlik ODBC Connector and i keep geting Timeout issues.After just a few seconds  ERROR [HYT00] [Qlik][ODBC Oracle Wire Protocol driver]Timeout expired.

       

      Here is my ODBC Connection String

      CUSTOM CONNECT TO 'Provider=QvOdbcConnectorPackage.exe;driver=oracle;host=AAA.com;port=1521;servicename=AAA;Connection Timeout=0;EnableNcharSupport=1;XUserId=AAA;XPassword=AAA;';

       

      Does anyone have an idea what the cause it.

        • Re: Qlik ODBC Connector problem
          Mohammed Ashfaq Ali

          Hi,

           

          Try by changing timout to 60 and let me know if that worked.

           

          CUSTOM CONNECT TO 'Provider=QvOdbcConnectorPackage.exe;driver=oracle;host=AAA.com;port=1521;servicename=AAA;Connection Timeout=60;EnableNcharSupport=1;XUserId=AAA;XPassword=AAA;';

           

          Regards

          ASHFAQ

          • Re: Qlik ODBC Connector problem
            Manoj K

             

            If a longer timeout period is needed, increase the value of the QueryTimeout connection attribute or SQLSetStmtAttr(SQL_ATTR_QUERY_TIMEOUT)setting.

             

             

            Valid values are -1 | 0 | x where x is a positive integer that specifies a number of seconds.

            If set to -1, the query does not time out. The driver silently ignores the SQL_ATTR_QUERY_TIMEOUT attribute.
            If set to 0, the query does not time out, but the driver responds to the SQL_ATTR_QUERY_TIMEOUT attribute.
            If set to x, all queries time out after the specified number of seconds unless the application overrides this value by setting the SQL_ATTR_QUERY_TIMEOUT attribute.

             

            Default is 0

            • Re: Qlik ODBC Connector problem

              dear Koen,

              for me, it is just a test today, il will see tomorrow,

              i add in my connection 2 parameters:

               

              CUSTOM CONNECT TO "Provider=QvOdbcConnectorPackage.exe;driver=oracle;host=ADR_IP;port=1521;servicename=SERVICE_NAME;Connection Timeout=60;SQL_ATTR_LOGIN_TIMEOUT=60;EnableNcharSupport=1;XUserId=....

               

              It seem to work.

              jm

              • Re: Qlik ODBC Connector problem
                nate green

                Markus,

                Did you ever figure out the solve for this? I am having the same issue, too.

                Thanks

                Nate

                  • Re: Qlik ODBC Connector problem
                    Markus Mortsiefer

                    Hello,

                     

                    No never got it to work. I installed the Oracle 11 Drivers Directly onto the server to solve the time out problems

                     

                    Regards

                    Markus

                      • Re: Qlik ODBC Connector problem
                        Rama Sai

                        After installation of client version try to create a new ODBC connection.

                         

                        and use it in your QV.

                         

                        Control panel-->Administrative tools-->Data source ODBC--> create a new ODBC connection for your Oracle database.

                         

                        else check with Database admin team weather the server is UP or not? some times due to N/w issue also Timeout issue will come.

                         

                        Question: I'm getting the error "ORA-12170: TNS:Connect timeout occurred" when I try to connect to my database via OEM.  How do I resolve the "ORA-12170: TNS: Connect timeout occurred" error?

                         

                        Answer: The ORA-12170 error can be for many reasons, firewall issue, database down, listener down, bad sqlnet.ora parm, network trouble, etc.  The docs note:

                        ORA-12170: TNS:Connect timeout occurred

                         

                        Cause: The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.

                         

                        Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).

                        Your sqlnet.ora file can be found in your $ORACLE_HOME/network/admin directory.

                         

                        ORA-12170 and hosts file

                         

                        Verify that your /etc/hosts file has a DNS entry:

                        1. 190.1.1.20  diogenes

                        In Windows XP, make your hosts file is located at win/system32/driver/etc/ and on UNIX, Linux, check /etc/hosts.

                    • Re: Qlik ODBC Connector problem
                      nate green

                      I was able to get it to work with the help from this post: Qlik Oracle ODBC driver timeout after 30sec by adding as Advanced attribute to the connection named QueryTimeout with a Value of -1