Cognos Analytics

 View Only
Expand all | Collapse all

Getting error "UDA-SQL-0432" in cognos FM while connecting to a datasource

  • 1.  Getting error "UDA-SQL-0432" in cognos FM while connecting to a datasource

    Posted Thu June 10, 2021 10:42 AM
    Hi,
    I am trying to connect cognos FM to a datasource and I am getting the following error in the process:
    ------------------------------------------------------
    QE-DEF-0285 The logon failed.
    QE-DEF-0325 The logon failed for the following reason:
    RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
     TEST

    UDA-SQL-0432 Unable to locate the gateway "cogudaor".
    ------------------------------------------------------
    This datasource is working fine from cognos connection and I am able to create data modules and reports based on this.
    I am creating the model using DQM, but I am still getting this error.
    I have installed Cognos FM (V1.1.7 )and  there are no existing model.
    Can you please help me with this issue.
    Could it be a FM configuration issue?

    Thanks,

    ------------------------------
    Tushar Gaurav
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Getting error "UDA-SQL-0432" in cognos FM while connecting to a datasource

    Posted Thu June 10, 2021 11:44 AM
    Hi Tushar,
    It appears that the project in the FM model is using compatible query mode. It is a property at the project level. You can switch it to dynamic. That will then use the jdbc connection instead.

    // Henk

    ------------------------------
    Kind regards,
    HENK CAZEMIER
    ------------------------------

    Original Message


  • 3.  RE: Getting error "UDA-SQL-0432" in cognos FM while connecting to a datasource

    Posted Thu June 10, 2021 12:20 PM

    Your FM model is set to use compatible query versus dynamic Query.

    Hence, FM is attempting to load the 32 bit ORACLE (OCI) client and failing to find it on the OS path.

    When you tested your connection, that activity occurred on the CA server, where it was able to locate the applicable ORACLE client connectivity.



    ------------------------------
    NIGEL CAMPBELL
    ------------------------------

    Original Message