SYMPTOM:
Users running Strategy Intelligence Server have several ways to cancel Job execution. Those methods are described in the technote shown below:
KB17934 (KB5300-8X-2811): Different methods of cancelling an executing report job on the Strategy Intelligence Server 10.x
However, while trying to cancel some specific jobs users can see the following errors displayed in the DSSErrors logs:
MSIPU::Kill: PU:SQLEngine: Could not cancel task (may be not supported): job:####, step:3, thread:####
CAUSE:When a job is created in the Strategy Intelligence Server it goes through several processing units (PU) that execute different tasks in order to generate SQL statements, get results from Warehouse, manage subtotals, etc.
Generally when Strategy jobs are canceled Intelligence Server logs entries similar to the ones shown below into DSSErrors log to identify those jobs:
2011-06-24 15:29:30.031-05:00 MSIPU::Kill: PU:QueryExecution: Signalled cancellation to component task: job:1199, step:4, thread:4156, will wait for timeout later.
2011-06-24 15:29:30.218-05:00 (SQL Generation CompleteJob 1199 canceled.Job 1199 canceled.)
When a job is in the SQL execution stage (the processing unit is called QueryExecution PU), and the job is canceled, a SQLCancel is issued to the database to stop the execution of the query. However, when the job is in any other PU, it cannot be canceled immediately. In other words, Intelligence Server cannot cancel the job there and has to wait for the task to finish executing in that processing unit. Since execution in all other PUs (other than QueryExecution PU) is usually not time consuming and resource intensive as compared to the query execution step against the database , it is acceptable if a task actually completes execution instead of cancelling immediately. This is the reason why Strategy Intelligence Server logs an error message like the one shown below for cancelled jobs in all PUs other than the QueryExecution PU:
MSIPU::Kill: PU:SQLEngine: Could not cancel task (may be not supported): job:####, step:3, thread:####
ACTION:In conclusion, both messages are being logged correctly to track Job cancel requests.
