TM1 Forum

Hi all!

In a project, we make parallel processes to take data from a database.
And sometimes we want to cancel the process while TI is trying to wait database response. (in case of when we realize anything wrong in code).
When we hit 'c' and try to cancel parallel processes while waiting database, we cannot cancel processes and nothing happens.

We cannot kill from Services and Task Manager due to some security conventions.

Is there any way to solve this issue?

Regards.

The only way I have found to do this is to kill the process via TM1Top then kill the associated process running on the database server i.e. the SQL Query/Stored Proc. Until the database releases the query, your TM1 will thread will be locked.

My preferred way of working around this during the development phase is the following:

• Write your SQL query outside of the ODBC connection (i.e. SQL Developer for Oracle, pgAdmin III for PostgreSQL, etc.)

• When you're positive the data coming out of your DB is correct, export it from the database to a csv or other flat file format

• Use the flat file extract as the datasource in your TI until you are positive your TI code is correct

• Merge your SQL query into your TI, hold your breath, think happy thoughts, and pray that you don't lock up the system for 3 hours

Hi

For info, TM1Top (or for that matter Ops Console) can only cancel a process after the current API call has been completed. Check the TM1 API documentation for a list of API functions. In this case it is probably TM1ProcessExecuteSQLQuery. Since the SQL that you send is all getting executed within a single API call, if that SQL never completes then the TM1 side will hang waiting for it to finish. As others have said, the solution is to stop TM1 waiting by killing the process on the SQL side.

Regards

Paul Simon