The Time Slicing job is failing with errors in the logs. You have tried to restart BG services but the same repeated error can be seen in the BG logs. Here are examples:
Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer]Cannot insert duplicate key row in object 'dbo.PRJ_BLB_SLICES' with unique index 'PRJ_BLB_SLICES_U2'.
SQL error code: 3621
Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer]The statement has been terminated.
....
Using input:
{sliceDate=2015-02-01T00:00:00, sliceID=11438446, role_id=5005473, startDate=2015-02-01T00:00:00, objectID=5003935, resource_id=5005473, unit=0, finishDate=2015-03-01T00:00:00, requestID=6, slice=159.6, investment_id=5006074}
Caused by: java.sql.SQLIntegrityConstraintViolationException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00001: unique constraint (CLARITY.PRJ_BLB_SLICES_W_AVL_U1) violated
ORA-06512: at line 1
ORA-06512: at "CLARITY.PRJ_BLB_SLICE_MERGE_SP", line 128
ORA-06512: at line 1
The table name and constraint can vary, depending on the data being inserted. Examples include:
PRJ_BLB_SLICES_U1
PRJ_BLB_SLICES_U2
PRJ_BLB_SLICES_W_AVL
PRJ_BLB_SLICES_W_ALC_U2
PRJ_BLB_SLICES_D_ETC_U1
PRJ_BLB_SLICES_M_ALC_U1
PRJ_BLB_SLICES_W_ETC_U1
Clarity Time Slicing
The constraint error occurs because the Time Slicing job is attempting to add a record that is already there.
This issue can occur if contention appears in the database and the database session is not handled.
The BG logs will need to be obtained and reviewed to obtain the slice data table and its corresponding records necessary to construct SQL backup and delete statements to resolve the issue.
DBA team assistance is required for running queries below.
select id, request_name, table_name from PRJ_BLB_SLICEREQUESTS where table_name = '[TABLE_IN_BG_LOG]'
select slice_request_id, count(*) from
[Table_name]
where slice_request_id in
(x)
group by slice_request_id
Make a backup of the table with the slices.
Run the below query:delete from [TABLE_NAME]
where slice_request_id in (x);
commit;
Reset the dates to force a resliceupdate PRJ_BLB_SLICEREQUESTS
set expiration_date = null,
request_completed_date = null
where id in
(x);
commit;
A restart is usually not needed unless there was an issue with the Job scheduler
If the same error occurs, please contact the Support team for further assistance.
If the above isn't the cause of your issue, see also: