Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2238724.1
Update Date:2017-03-23
Keywords:

Solution Type  Problem Resolution Sure

Solution  2238724.1 :   Domain time may drift after an abrupt system down  


Related Items
  • Fujitsu M10-1
  •  
  • Fujitsu M10-4S
  •  
  • Fujitsu M10-4
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Fujitsu M10
  •  




In this Document
Symptoms
Changes
Cause
Solution


Created from <SR 3-14345623861>

Applies to:

Fujitsu M10-1 - Version All Versions and later
Fujitsu M10-4 - Version All Versions and later
Fujitsu M10-4S - Version All Versions and later
Oracle Solaris on SPARC (64-bit)

Symptoms

After a power outage, domain time drifted back for 8 hours, more than NTP can handle. Applications were greatly impacted.

Changes

 From console log, it's found domain time had been changed long before.

Cause

XSCF records the base time and the time difference to the domain time.
Upon power on, the domain is able to calculate the right time of its own, based on the XSCF time.

If the domain time is changed (such as being modified by command date), a normal domain reboot is required to adjust the time difference in the XSCF.

In this case, there had not been a normal reboot since the domain time experienced the big change.

After the unexpected power outage, the time difference was lost.

When the domain booted up, its time was set to be equal to the XSCF time, which had been 8 hours behind the domain time.

Solution

To prevent such a problem:

1. It's better to have the XSCF and the domain to keep the same time.

2. If the XSCF and the domain have different time setting, reboot the domain whenever changing the domain time.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback