Netweaver 7.4 on windows - SAP HANA

[Former Member]

Hello

I try to install Netweaver 7.4 on windows 2008 R2 over SAP HANA, during the installation i receive a message that DDIC user cannot log, when i try to log on to the system using the sap logon I receive and error that say

Basis System: Runtime error "ZDATE_LARGE_TIME_DIFF " occurred.

I checked the timezone on the sap hana system and windows it seems ok.

any ideas,

Regards.

[karthikeyan_natarajan4]

Hi Zayed,

Just now i created a blog regarding this, please refer this blog

http://scn.sap.com/community/hana-in-memory/blog/2013/10/01/dump-zdatelargetimediff-in-hana-database

regards

kartik

[Former Member]

Thanks Pierre and Kartik for procedure to change.

[Former Member]

Hi,

got the same one. I had to adjust the timezone of <sid>adm user on the SAP Hana appliance with the TZ environment variable. Then reboot the appliance.

Mine is : TZ=Europe/Berlin to match the one on the application server.

Regards,

Pierre

[former_member182034]

hi Zayed,

please go through following sap notes. these might be helpful.

Note 101726 - Incorrect times and time zone setting

323954 ZDATE_ILLEGAL_LOCTIME when starting application

102088 Reducing downtime when changing from summer to winter time

447839 ZDATE_ILLEGAL_LOCTIME

Regards,

[former_member189546]

Hello,

The short dump ZDATE_LARGE_TIME_DIFF comes up if the database determines

a time difference to the application servers.

Please check if all your servers have the same time and are at the same

timezone.

Do you use NTP on Windows?

Are you using NTP to synchronise time.

Check note.

#447839 ZDATE_ILLEGAL_LOCTIME

regards,

John Feely

[bxiv]

What timezone do you have set?

Not only is time important, but is the date the app and DB servers set to the same day/month/year?

If you have a Windows domain configured, be aware that this will enforce certain time related settings; timezone is typically not one of them, however Windows will let the clock skew up to 8 mins before it will force the client to check with the domain and update the clock.