2535959 - Dump ZDATE_ILLEGAL_LOCTIME occurs, what should be analyzed

Symptom

Runtime Errors ZDATE_ILLEGAL_LOCTIME
Date and Time

Short Text

The local time of the application server is not correct.

What happened?

Error in the SAP kernel.

The current ABAP "SAPMSSY6" program had to be terminated because the

ABAP processor detected an internal system error.

Error analysis

The ABAP interpreter always determines the local time relative to the

database time. To do so, it obtains both the time of the application

server and that of the database at regular intervals. The times must

meet specific plausibility criteria - for example, the time of the time

stamp obtained second cannot be earlier than that of the time stamp

obtained first.

In this case, the plausibility criteria for the local time of the

application server were not met.

Earlier time stamp: "See former similar dump: <Time> "

Later time stamp: "See former similar dump: <Time> "

How to correct the error

It is possible that the time of the application server was set forward

or back in the running system.

Ensure that the times and time zones of the application server and

database server match and restart the system.

In the same time, dump CALL_FUNCTION_NO_GUI_BUFFER.

Trace:

ERROR => dbsync[check_sync_interval]: xxx seconds passed since last synchronisation
ERROR => StatRecHook: time stamp in statistical record (xxXXxxXXxx) differs for more than xxx seconds from current time
ERROR => XX.zz.<Time> PID=<pid>, TID=<tid>#SapTimer error. Time errors detected xxx times. Time may be incorrect

Environment

All ABAP system in all type of OP

Keywords

CALL_FUNCTION_NO_GUI_BUFFER, ZDATE_ILLEGAL_LOCTIME, time difference , KBA , BC-ABA-LA , Syntax, Compiler, Runtime , BC-SRV-TIM-TZ , Time zones , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.