cancel
Showing results for 
Search instead for 
Did you mean: 

Internal kernel error - ZDATE_ILLEGAL_LOCTIME

0 Kudos

Hi Everyone,

I have SAP servers in Active directory. but recently, i am getting the following Runtime error in 2 servers.

Runtime error - Description of Exception

Category                       Internal Kernel Error

Runtime Error                ZDATE_ILLEGAL_LOCTIME

Application component  BC-ABA-LA

Short text

The local time of the application server is not correct.

The database and the application are installed in a same server.

Steps taken:

1. Trying to sync the time between active directory server and the application server.

2. Checked the time zone and all are OK.

3. Finally, I restarted the server and it is working now temporarily.

I got this error few times and only the last step has helped me. I think, this is not recommended.

Is anyone have idea about this issue and any other checklist to verify?

Accepted Solutions (1)

Accepted Solutions (1)

Ranjith418
Contributor
0 Kudos

Hello Pandiyaraj,

Please check

Note 447839 - ZDATE_ILLEGAL_LOCTIME

Thanks,
Ranjith

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

ZDATE_ILLEGAL_LOCTIME means TIME of your local application server (where SAP instance runs) was set BACKWARD by time service or users, which will always be considered as 'ILLEGAL' by SAP kernel.This is also a way of protecting your system from creating inconsistent data. If you open the dump ZDATE_ILLEGAL_LOCTIME in ST22, you will see the time-stamps captured by kernel. This is not an SAP error but occures when the time on the operating system gets reset to the past. 

As per my experience this is always caused by either a manual change of the system time on the OS or the use of a so-called time utility which adjusts the OS system time to keep it in sync with some external time reference. If your system uses such a utility you must ensure it conforms the restrictions outlined in note 447839. Making the parameter abap/time = strict will tell the system to trigger the short dump if the time inconsistencies are less that 2 seconds. This will make the short dump more likely.

You can also check SAP Note 989963

Regards,
Sachin

Reagan
Advisor
Advisor
0 Kudos

Hello

Had this issue in the past which was due to the NTP daemon was not running at the OS level and that put the systems out of sync with time.

Cheers

RB

former_member201800
Participant
0 Kudos

Hi,

You can refer the note:

Note 198411 - Current data and information about time zones

Regards,

Shyam

0 Kudos

Hi Pandiyaraj,

The reason of this dump is described details as in note 447839:

Reason and Prerequisites

The system time of the server was reset to the past, while the SAP

application server was running.

In this case, it does not matter whether this was done manually (with

operating system commands) or automatically (with a "time service", for

example).

If the runtime error ZDATE_ILLEGAL_LOCTIME has occurred, the most

important information is contained in the dump.

When the runtime error ZDATE_ILLEGAL_LOCTIME occurs, the relevant

application server should be shut down immediately.

1.Make sure your OS and SAP has the same timezone.

  Ohterwise dumps like ZDATE_ILLEGAL_LOCTIME will happen.

2.The tool "SapTimeTrace" is added to note 447839. This is a small

executable which you can simply execute in a command line as follows:

SapTimeTrace 5

Now the operating system time is analyzed every five seconds and a trace

file (SAPTTrc.trc) is written into the current directory that contains

information about the time changes. For more information, call the

"SapTimeTrace" without parameters.

Thank You.

Regards,

Deepika