AnsweredAssumed Answered

Cron jobs are running on time But  in aveksa monitoring page it showing different time

Question asked by Rajkiran Paul on Jan 12, 2017
Latest reply on Jan 15, 2017 by Boris Lekumovich
  • Comment • 7

Hi Experts,

we have 3 different time slots for running IDC and ADC. Time slot 1 is set  from aveksa itself.For other 2 time slots we have scheduled it from cron job.
 
Time slot 2:  (it is scheduled  at 18.00 every day  for identity data collection/identity data and 18.30  every day for Account data collection)
 

     


                                                                       
 Time slot 3:  (it is scheduled  at 22.00 every day  for identity data collection/identity data and 22.30  every day for Account data collection)
   

    

     


 
   For time slot 2 and time slot 3 the following are the cron job we scheduled .

   

    The cron jobs are running on time . i have verified it? But  in aveksa monitoring page it showing different time.

  - As you can see Time slot 2 is scheduled at 18.00(6 pm) for Identity collection  and 18.30(6.30 pm) for account collection every      day. Then why it is showing  on 7.30 and 8.00 clock?

 

  - As you can see Time slot 3 is scheduled at 22.00(10 pm) for Identity collection  and 22.30(10.30 pm) for account collection          every day. Then why it is  showing on 11.30 and 12.00 clock?
              

Boris Lekumovich
Boris Lekumovich Employee Jan 13, 2017 12:03 AM
Correct Answer

see the following KB articles:

000029596 - IMG: Changing Oracle Timezone File to Resolve Stuck Workflows and Change Request Timing Issues 

000031682 - Change requests take a long time to complete using any Workflow and get stuck at each node in RSA Identity Management and Governance (IMG) 6.9.1 

See the reply in context
No one else had this question

Outcomes