Skip to main content



Oracle Odbc Connectivity Very Very Slow



  • Avatar
    Shotaro Ito

    Hi Dude,

    I recon OLEDB / ODBC connection might get very slow when you connect to very big table - don't know why.

    Try Oracle setting in BarTender database connection setup (that's OLEDB.)

    Try Options > [Use client cursor] if haven't tried.


    Usually when you have complex query in Database connection and that makes database connection slow,

    create a equivalent view in database and connect to the view from BarTender.

    Also, I suppose you're using Query prompt already, but if not - use query prompt to filter records, demonstrated in below.

  • Avatar
    Legacy Poster

    Sorry to resurect an old thread, however, I also have a similar problem AND a issue with how BarTender is pulling in all the tables from Oracle.

    I am only using a few tables and clearly defined join conditions (though, for one of the joins BarTender calls it a circular reference when it clearly is not). I am finding that it looks to be pulling in ALL records prior to running any filters on the query?


    I decided to commit to a custom query instead of the query derived via the tables/joins/filters as it was putting in certian fields twice into the query. (e.g. ORDER_NUMBER, ATTRIBUTE1, HEADER_ID and then reprating this again - ORDER_NUMBER, ATTRIBUTE1, HEADER_ID) yet are only used once on the template.


    Also, I have to actually bring in one table at a time, make the join, close the template and then repeat this for each table used.

    This is for Oracle EBS R12 as the datasource. So I am unsure why there is such a huge performance hit when BarTender links to Oracle? We did create materialized views to try to increase the performance but to no avail. Performance is exactly the same as the SQL Query (and in some cases, worse). we have tuned the main query to create the view, have the correct indexes and the like. This is operating in an enterprise realm and the performance is not on par with what we would like.


    It is almost like it is trying to bring back the top 1000 records and then performing any filter related data. Any insight would be most appreciated. Other than this issue with Oracle connectivity, the rest of what we use the application for is nothing short of amazing!


Please sign in to leave a comment.