Sun Fire 4810 Server
 
Sun Fire 3800 Server
 
Sun Fire E6900 Server
 
Sun Fire 6800 Server
 
Sun Fire V1280 Server
 
Sun Fire 4800 Server
 
Sun Fire E2900 Server
 
Sun Fire E4900 Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-x8x0/Ex900
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange V and Netra Servers
 

Applies to:

Symptoms

On certain Sun Fire[TM] systems, a System Controller (SC) running ScApp versions 5.18.X, 5.19.X or 5.20.X. with extended uptime may experience an abrupt clock change.

The changes have been seen where the clock jumps forward to 828 days, or where the clock becomes unstable upon reaching 828 days. The forward jump has been seen jumping 60 days forward to 828 days. This clock change can affect the domain time, database applications, customer data, or any other clock related operations.

Cause

 Clock becomes unstable upon reaching 828 days

Solution

Resolution
See the following:

Resolution is in Patch ID: 114527-12 ScApp 5.20.7 or higher


Relief/Workaround

1. Add these lines to the /etc/system file for all domains to disable the domains from getting their time from the SC:


set tod_broken=1
set dosynctodr=0

2. Enable NTP on the domain, and SNTP on the system controller. Refer to the appropriate Solaris Systems Administration Guide for your Solaris Release, and the appropriate Platform Administration Guide for your ScApp Release.

3. Reboot the system controllers.

4. Reboot the domain at next available maintenance window prior to reaching 575 Days uptime on the system controller.

If uptime is greater than 575 days:

1. Add these lines to the /etc/system file for all domains to disable the domains from getting their time from the SC:


set tod_broken=1
set dosynctodr=0

2. Manually disable the running domain from getting it's time from the SC. Either reboot the domain with the /etc/system changes listed in step 1, or run the script below. The following script can be invoked as "root" on the running domain to change the value of "tod_broken" and "dosynctodr" in the running domain's kernel:

#!/bin/sh
#
# Set tod_broken and dosynctodr
#
echo "tod_broken ?W 1" | adb -w -k /dev/ksyms /dev/mem
echo "dosynctodr ?W 0" | adb -w -k /dev/ksyms /dev/mem
#
# exit 0

3. Enable NTP on the domain, and SNTP on the system controller. Refer to the appropriate Solaris Systems Administration Guide for your Solaris Release, and the appropriate Platform Administration Guide for your ScApp Release.

4. Reboot the system Controllers

(see "Additional Information" for determination of uptime on the SC).

Note: The domain will still get it's initial time from the SC on boot even with the /etc/system setting. This functionality cannot be fully disabled.

If the domain experiences this issue and the domain time has already changed, a reboot of the SC will be necessary. The time will also need to be adjusted manually on both the domain and SC. A reboot of the affected domain may also be necessary.


Additional Information
To see how long the SC has been up, and what version of ScApp it is running use the 'showsc' command:


f6800b-ssc0:SC> showsc

SC: SSC0
Main System Controller
SC Failover: enabled and active.
Clock failover enabled.

SC date: Tue Jun 26 09:28:36 EST 2007
SC uptime: 828 days 18 hours 44 minutes 53 seconds

ScApp version: 5.19.3 Build_01
RTOS version: 45


The following is strictly for the use of Oracle employees:
See Bug ID: 6567546 or Bug ID: 6585200

References

This solution has no attachment