Control Compliance Suite (CCS)
When running a CCS Query job or data collection, and it is not completing and it seems to be hung.
Release : 12.6.X
It could be the scope of the Query or the CCS Job, or it can be just a lot of data that is being collected making it appear that the job is hung.
Or could be a CCS Manager that is having problems.
Enable Job Traceability to help identify the CCS Manager(s) doing the collection. Can get details if the threads for the Manager are obsolete or not.
Option is available in CCS console’s jobs view to dump trace for an executing job. However, the option is not enabled by default. Following steps needs to be done to enable the option:
The job trace is dumped as an HTML/XML. The required data is present in a hierarchical way i.e. job can be traced from APS to DPS to WorkerProcess or parent job to child job. Traceability to the agent is not covered.
The trace is available only for running jobs\sub-jobs and not for completed jobs\sub-jobs.
Once the option is enabled in the console the trace can be dumped for the selected job or all running jobs. Use the 3 dots dropdown menu from the Jobs workspace to access the "Trace running jobs" option.
If the job is not showing up just select the option to dump all jobs.
NOTE: When in the Job workspace if you press the Alt key on the keyboard it will reveal a traditional file menu at the top of the CCS Console.
You may also find the "Trace running jobs" below under Tasks, see the screenshot below.