jump to article
...intermittent thoughts

Oh no: "Database xxx time is too far in the future"

With installing the ND 6.5 pre release I got the problem of getting such messages on the Domino server console:
"Database
time is too far in the future". I always thought this is a problem of the beta release. When I was upgrading to ND6.5.1 the problem disappeared and I was happy again. Last week I had another look in my log and there it was again. Many of my most important databases promote this error on the servers log.
This time I started to google a bit for learning more about it - and yes the hints showed me there are others having the same problem. But now I am convinced not Domino is the time cracker, it is my Tardis time service which occasionally sets time to some date in the year 2020. If this happens Domino gets this date too and you get databases with documents as of the year 2020 already in 2004 ( ey, the try to spam you in 2020 too :-) )

But what to do, if you have this problem too?

The last times I had this prob, I just made a local replica of all those databases, shut down the Domino server, deleted the damaged ones, replicated the local replicas back and started the server again. Now I know more. To avoid the loss of data do the following on all those databases:
  • delete the replication history on all replicas
  • delete the cutoff-date in the replication settings on all replicas
  • reactivate all scheduled agents (the last run date may be affected)
  • re-create all full text indexes
  • for mail databases there is the hint of copying the ($inbox) folder to a protected temp one, moving all contained documents over there, delete the ($inbox) folder, replace the design, move all documents back to the reappeared ($inbox) and delete the temp folder to avoid non appearing of mails in the inbox (sounds really hard and seems to be not required to me - my inbox is working)

For fixing the date values of already deliverd mails, I have written some small agent fixing the year-time stamp of mails seeming to be delivered in the future. If you are interested in getting it, just contact me! (Don't care - I won't charge you for it)
  1. 1) Litty Joseph said: (19.05.2008 10:00:43 GMT)
    Domino - Time is too far in future

    Thanks for your post on "Time is too far in future". I am scared reading this solution. It's almost like setting up the server, all databases and fixing all documents once again...

  2. 2) niels de bree said: (16.07.2013 15:26:25 GMT)
    Oh no: Database xxx time is too far in the future

    Hi Michael,

    Please send me the code for correcting some maildatabase. Domino Server was started with date 10-06-2033 (al litle bit too far in the future).

    Many thanks,

    Niels de Bree

  3. 3) antone Baioni said: (02.11.2014 22:12:53 GMT)
    Oh no: Database xxx time is too far in the future

    Can you send me the code for the mailbox date changes. I know this is old but I just ran into this issue and need it fixed.

  4. 4) Michael Gollmick Said: (03.11.2014 6:30:12 GMT)

    re: Oh no: Database xxx time is too far in the future

    Sorry, I just looked around and did not find the mentioned code anymore - sorry :-(

  5. 5) tadacip said: (19.04.2017 18:07:47 GMT)
    cialis tadacip cipl

    Anadia daily { Link } , Ovar viagra medicamento Vale de Cambra v is for viagra Ovar cialis o que ?


Add Comment
 
Subject:
   
Name:
E-mail:
Web Site:
 
Comment:  (No HTML - Links will be converted if prefixed http://)
 
Remember Me?