on 05-10-2013 1:16 PM
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?
Hello Pandiyaraj,
Please check
Thanks,
Ranjith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
74 | |
10 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.