General discussion

Locked

Synthetic Time Revisited - Y2K?

By artcabot ·
I've inherited a 4.11 server that's displaying those annoying "Synthetic Time" messages. The hardware clock is correct, but issuing "Time" at the command line tells me that DST Start is April 4, 2038, DST End is October 31, 2038, today is Sunday, February 7, 1988 11:06p UTC and 6:06p EST. All this on Tuesday, January 2, 2001.

Is this a belated Y2K issue and, if so, what do I need to do? I've tried the stuff Steven Pittsley recommended and it hasn't helped.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Synthetic Time Revisited - Y2K?

by JimBb In reply to Synthetic Time Revisited ...

I presume your server is on the latest patch level? In that case, most likely it was not yet on 1/1/2000, and it then made a mess of its time. Since then the time of the server has been corrected, but NDS is running in the time you described, be it that its clock is running slower than the "real" one. Synthetic time just means that NDS has slowed down its clock until it is in sync with the real time. This is perfectly normal and acceptable, and could go on for several days/weeks. After all, NDS depends on timestamps and can't handle time being jumped backwards and forwards all the time. If you really want to get rid of it, try to "declare a new epoch" in DSREPAIR.

Collapse -

Synthetic Time Revisited - Y2K?

by artcabot In reply to Synthetic Time Revisited ...

No patches had ever been loaded on this box, as I stated.

Collapse -

Synthetic Time Revisited - Y2K?

by csn In reply to Synthetic Time Revisited ...

The NetWare OS relies on the hardware clock to initially set its own. Once SERVER.EXE loads it grabs hardware time once and sets two internally kept clocks. Cold-booting the server should correct the OS-time.

As for Synthetic Time I recommend youread Novell TID 10013670 (you can find it at http://support.novell.com/search/kb_index.htm)

Collapse -

Synthetic Time Revisited - Y2K?

by artcabot In reply to Synthetic Time Revisited ...

Got some more good stuff out of the Novell TID, but it led to more problems, which I'm going to post in a separate thread.

Collapse -

Synthetic Time Revisited - Y2K?

by jaolson40 In reply to Synthetic Time Revisited ...

Quickest and dirtiest way to reapair that is to run a quick DSREAPAIR to ensure database integrity, verify that the time displayed at the console prompt is the correct one, then under advanced options in DSREPAIR, partition and schema operations, select Repair All Timestamps and Declare a New Epoch. That'll set all the timestamps on every object to the current time and eliminate the error. All operations should proceed normally after that.

If you can't find that option, you may have to load DSREPAIR with the -A switch.

Hope this helps!

Collapse -

Synthetic Time Revisited - Y2K?

by artcabot In reply to Synthetic Time Revisited ...

The DSRepair on this server doesn't even HAVE an -A switch!

Collapse -

Synthetic Time Revisited - Y2K?

by artcabot In reply to Synthetic Time Revisited ...

This question was closed by the author

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums