Uproc Aborted manually but underline SSIS package still running

[Anon Anon]

We had a situation with one of our jobs and wanted your inputs.

Job(x) is calling a SSIS package(a) , that SSIS package internally calls 4-5 SSIS packages.
Job(x) was in running status and for some reason we needed to abort the job manually , after which job went in Aborted Status.
But when we saw our custom logs(for SSIS packages), it showed respective packages are in running status.

Is there any way we can force abort all underline package when we abort $universe jobs ?

[Anon Anon]

Hi amolanilkale,

this rings a bell - not this specific case though. Can you specify the exact OS flavour and the interface used (UniViewer, Windows Global Console, etc.). How was the DU job stopped? With the GUI feature or DU command (uxend)?

Michel

[Anon Anon]

OS:Windows
UV:3.0.05
$Version : 5.6

job stopped with GUI feature(manually right click on running job and cancel)

[Anon Anon]

Great, still need the exact flavour of the OS (which version of Windows)?

[Anon Anon]

its windows server 2008 r2 (x64)

[Anon Anon]

Hi,

I checked this with ORSYP R&D and - as I feared - there is currently no solution within DU. Ceci dit, They will be planning some enhancements but the difficulty resides in keeping track of processes that are created from the Uproc script but are outside of the UPROC process tree (DU has no control on them).

I would recommend 2 actions on your side:

- open a Product Enhacement (PE) request on the Support site
- define a process for your Operations so they have a list of actions to stop the DU batch and also the SSIS packages.

Sorry I cannot be more helpful on this one for now...

Michel

[Octavie_Chakoute_1958]

Amolanikale,

Did you open a PE with Tech Support?

Octavie