Product:
Planning Analytics 2.0.9.3
Microsoft Windows 2019 server
Issue:
In tm1server.log file there is reference to wrong ODBC connection. Like this
TM1.Process Process “second.process” run from process “main.process” by user “AD/donald”
TM1.SQLAPI Checking Driver Capabilities for database “TEST”
TM1.SQLAPI Driver supports SQLFetchScroll
Possible solution:
As the Data Source tab is pointing to the TEST odbc connection, a test connection is made and written in the log file.
Change the ODBC name in the Data Source tab to the expected ODBC connection like: PROD
You can still have the TI process change the ODBC connection to correct one in the prolog tab, with code like this:
#-------------------------------------------------- # Set source with values from variables you have defined before #-------------------------------------------------- DataSourceType='ODBC'; DatasourceNameForClient=sODBCConnection; DatasourceNameForServer=sODBCConnection; DatasourceUsername=sUser; DatasourcePassword=sPassword; DatasourceQuery = sDataSourceQuery ; #----------------------------------------------------------------------------- # open the connection to the database ODBC connection #----------------------------------------------------------------------------- ODBCOpen(sODBCconnection, sUser , sPassword );
# this will change the ODBC connection, and the metadata and data tab will use the new ODBC source.
The DatasourceNameForServer= variable will set the ODBC source used by the process when run from a chore.
More Information:
https://www.ibm.com/docs/en/cognos-tm1/10.2.2?topic=variables-datasourcenameforserver
https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=tv-turbointegrator-local-variables