IBM Support

Testing the Oracle data source in the Framework Manager model and getting errors: QE-DEF-0285, QE-DEF-0323, UDA-SQL-0532, etc

Troubleshooting


Problem

When testing the Framework Manager data source in a project, we are getting these errors below.  The Framework Manager project is using Compatible query mode.
QE-DEF-0285 The logon failed.
QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: ABCDE
UDA-SQL-0031 Unable to access the "ABCDE" database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.
UDA-SQL-0532 Data Source is not accessible: "XXX_ABCDE".
ORA-12154: TNS:could not resolve the connect identifier specified
Framework Manager is working fine for other projects and other data sources.
We have confirmed that the Oracle 32-bit client for Oracle 12 which matches the Oracle database version, is already installed on the machine where Framework Manager is installed.  We know that Framework Manager requires the 32-bit Oracle client.
We have also confirmed that both the ODBC and the JDBC data source connections for this data source test successfully within Cognos Administration > Configuration > Data Sources.  Since this Framework Manager project uses compatible query mode, it is not using the JDBC connection which is only for dynamic query mode.

What is causing these errors to occur?

Resolving The Problem

Search the machine where Framework Manager is installed for multiple tnsnames.ora files.  It is possible that multiple Oracle clients or tnsnames.ora files exist and that the connection string was not defined within the "active" copy of the tnsnames.ora.
If multiple files are located, then you can set the TNS_ADMIN environment variable to specify the directory that contains the version of the tnsnames.ora file you want to use.  Or else the expected connection alias can be defined within each tnsnames.ora to eliminate any possible inconsistencies.
The Oracle "tnsping" command can be used to test a connection alias. Running "tnsping ALIAS_NAME" from a command window obtains the client driver connection information from the current environment settings and then returns a success or failure message that indicates whether or not the ALIAS_NAME defines a valid Oracle connection.
If the connection can be established on one server in the IBM Cognos environment but it fails when tested on another server, then ensure that the tnsnames.ora on the failing server contains the same connection string as the successfully connected server.   Copying the tnsnames.ora file or the entry within the file to the failing environment ensures that the connection information is the same in both environments. 
Following an update to the tnsnames.ora file, test the connection by using tnsping on the problem server to validate the copied connection string works successfully.
Ensure that the alias in the tnsnames.ora file matches the alias in the IBM Cognos connection string for this data source defined in Cognos Administration > Configuration > Data Sources.
Once the above is confirmed to be correct, then launch Framework Manager and open the project whose data source had failed testing.  Test the data source again to confirm that the errors have been eliminated.

Document Location

Worldwide

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTSF6","label":"IBM Cognos Analytics"},"ARM Category":[{"code":"a8m50000000Cl4NAAS","label":"Modeling->Framework Manager"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Version(s)","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 July 2020

UID

ibm16254013