32116 - TPD Server's Time Has Gone Backwards
- Alarm Group:
- PLAT
- Description:
- This alarm indicates that the server's current time precedes the timestamp of the last known time the servers time was good.
- Severity:
- Critical
- Instance:
- May include AlarmLocation, AlarmId, AlarmState, AlarmSeverity, and bindVarNamesValueStr
- HA Score:
- Normal
- Auto Clear Seconds:
- 0 (zero)
- OID:
- tpdNTPTimeGoneBackwards
- Alarm ID:
- TKSPLATCR17
Recovery:
- Verify NTP settings and that NTP sources are providing accurate time.
- Ensure ntpd service is running.
- Verify the content of the /etc/ntp.conf file is correct for the server.
- Verify the ntp peer configuration; execute ntpq -p and analyze the output. Verify peer data, (such as tally code (first column before "remote"), remote, refid, stratum (st), and jitter), are valid for server.
- Execute ntpstat to determine the ntp time synchronization status. If not synchronized or the stratum is not correct for server then ping the ntp peer to determine if peer can be reached.
- If ntp peer is reachable, restart the ntpd service.
- If the problem persists, contact My Oracle Support (MOS).