All

For the RunOnceImmediately schedules , the NEXTRUNTIME value is being automatically set to '00000000000009223372036854775807'.

Which falls out of 12/31/9999.

I am checking for the next run date from the BOTSCHED table for each schedules.FOr other schedules say One Time, Weekly , Monthly i cude fetch the nextruntime successfully.

But whereas , for the RunOnceImmediately schedules i am getting an error .

I am using the following query to fetch the nextruntime value.

---------------
select TO_DATE('01/01/1970','MM/DD/YYYY')+((((to_number(NEXTRUNTIME))/1000)/(60*60*24))-8/24) nextrun
from botsched;

Please Advice

Hi Navin,

Has this issue been resolved?

If not, I am wondering, can you please let us know, for the RunOnceImmediately schedules, do you receive any error message? More details may be helpful in understanding the problem.

Thank you in advance for sharing with all.

Cheers,

Kerry

Sorry Kerry

I should have posted you all wen i got a solution.Sorry for the delay anyway.

Actually the reason is , the NEXTRUNTIME will be encrypted and stored for the schedules that are completed.That value can only be read by the distribution server . We should not apply our usual logic for retrieving the nextruntime value for the completed schedules.

SO i did a decode() function in my oracle query so that i get no error .
like,
(decode(b.nextruntime,'00000000000009223372036854775807','00000000000000003372036854775807')

So in the front end upon interpreting this i can handle it as completed