Clarity

Hi,

Since morning timslice job is running and seems like its stuck. BG log is showing the error as :

Statement Id: omp.dynamic.select-object.map::llist_obj_pls:NIKU.ALL:0:prodyears
WARN  2017-05-25 05:31:07,207 [Post Condition Transition Pipeline 2 (tenant=clarity)] com.niku (clarity:process_admin:222312001__5A4B7CB0-8B9C-4C38-B402-AA8E2DAB7EC3:none) SQL statement: SELECT  s0.id odf_pk,     (SELECT odf_ca_project.prodyears FROM odf_ca_project, odf_ca_llist_obj_pls WHERE  1=1 ) prodyears FROM   odf_ca_llist_obj_pls s0  WHERE (   s0.id=? )
WARN  2017-05-25 05:31:07,207 [Post Condition Transition Pipeline 2 (tenant=clarity)] com.niku (clarity:process_admin:222312001__5A4B7CB0-8B9C-4C38-B402-AA8E2DAB7EC3:none) Parameter 1: ######
INFO  2017-05-25 05:31:07,754 [Dispatch Time Slicing - 25/05 :  (tenant=clarity)] niku.blobcrack (clarity:GuptaA12:222351584__41DF0222-C3C6-4977-A7C4-218616F9B25C:Time Slicing - 25/05) ### Curve set size is 1000
WARN  2017-05-25 05:31:08,909 [Post Condition Transition Pipeline 0 (tenant=clarity)] com.niku (clarity:process_admin:222312001__5A4B7CB0-8B9C-4C38-B402-AA8E2DAB7EC3:none) For info only - SQL statement not supported by OMP:
WARN  2017-05-25 05:31:08,909 [Post Condition Transition Pipeline 0 (tenant=clarity)] com.niku (clarity:process_admin:222312001__5A4B7CB0-8B9C-4C38-B402-AA8E2DAB7EC3:none) SQL message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01427: single-row subquery returns more than one row

Kindly help!

Regards

Ritesh

The above ones seem to be related to a process

Do you see anything related to timeslicing ?

Did you bounce the bg service ?

NJ

Hi Ritesh

Those are not timeslicing errors. To fix the Timeslicing job please follow the article below:

https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec586757.html

This should help to get the TImeslicing job running again.

Please let us know how it goes. -Nika

I have found this error in the bg log:

WARN  2017-06-07 00:27:55,057 [Dispatch Time Slicing-gl 06-07-2017 :  (tenant=clarity)] niku.blobcrack (clarity:lig3:222561901__F47EFE22-BB96-4837-B592-EB275984644F:Time Slicing-gl 06-07-2017) Slice value is not in the valid range.  Object ID = 5975486 Request ID = 3 Date = 2017-03-28T00:00:00 Value = 5.120054752503818E-13. Value will be set to 0

Kindly help

HI RKP,

It looks like it's not the error of Time slice job. If it gets stuck, just cancel the job and delete all the Time slice CANCELLED job instances (otherwise job will directly go into waiting state). 

After that, restart the BG service and then re-execute the Time slice job.

Hope this may resolve the issue.

Best Regards

Shubham Bhatia