7/28/2019 Sapnote_101726 - Incorrect Times and Time Zone Setting

http://slidepdf.com/reader/full/sapnote101726-incorrect-times-and-time-zone-setting 1/2

SAP Note 460268 - Could not find stored procedure

Note 101726 - Incorrect times & Time zone setting

Symptom

Error message ZDATE_LARGE_TIME_DIFF

Incorrect timesProblems during the daylight saving time change

Additional key words

Timezone, UTC, GMT, time, date, tz, rsdbtime

Cause and prerequisites

This is generally caused by an incorrect time zone setting by the database or R/3 processes.

 A correctly displayed local time, for example with 'date', does not ensure that the setting is correct because the time basis of the

operating system, the UTC timer, is set indirectly by 'date'. If the time zone setting is incorrect, then the value of the UTC timer 

must also be incorrect if the correct local time is set with 'date'.

The UTC timer counts the seconds since 01/01/1970, 00:00:00, Greenwich Mean Time. At the correct setting it contains the samevalue in all computers, regardless of their location.

Errors in the time zone setting inevitably cause problems in a switch to daylight saving time and in distributed systems.

Time zone and UTC timer are attributes at operating system level, not of application software, for example database or R/3.

Solution

To solve the problems proceed as follows:

1. Setting the UTC timer

• Stop database and R/3

• Log on as Superuser (root).

• Set the General Mean Time (GMT) time zone (Greenwich time) for example in the C-shell with

'setenv TZ GMT'.• Display the time with 'date'The time displayed must match Greenwich time.

Greenwich time is 2 hours behind compared to Central European Summer Time and 1 hour compared to Central EuropeanWinter Time.

• If this is not the case, you must correct the UTC timer with 'date'.Caution: you must enter the correct Greenwich time here

•  The UTC timer is now correctly set.

2. Setting the time zone

• Log on as the user for which you want to make or check the time zone setting, for exampleora<sid> or <sid>adm

• Display the time with 'date'. The displayed time must match the local time, both in daylightsaving time and standard time.

• If this is not the case, you must set a correct time zone, for example with C-shell 'setenv TZ

<zeitzone>'In you have questions regarding the correct time zone, contact your operating system manufacturer.

• Make sure that the correct time zone is set automatically in the login script of the user inquestion.

• It is even better to configure the correct time zone as a default in the operating system. You then

do not need to set a time zone in the login script.

• Make sure that processes which are not started in the normal login (for example via 'rexec',

'cron') also have a correct time zone setting. With rexec, an R/3 instance is started if it is startedfrom the CCMS system monitor (RZ03) or an R/3 start-up profile or a computer (instead of 'local').

The time zone is now set correctly for the databases and R/3 processes.

7/28/2019 Sapnote_101726 - Incorrect Times and Time Zone Setting

http://slidepdf.com/reader/full/sapnote101726-incorrect-times-and-time-zone-setting 2/2

SAP Note 460268 - Could not find stored procedure

3. Check the settings to R/3

• Start the database (DB) and R/3

• Start the R/3 report RSDBTIME, all times should now be displayed correctly.

• If times are displayed incorrectly, check the time zone setting in the environment variable TZ of the DB shadow processes and the R/3 processes, for example with 'ps eww <prozessnumber' or asuitable monitor of the operating system. 'ps' shows the contents of environment variables,however only in the Berkeley(BSD) mode that does not exist on all UNIX derivatives. If you have

questions contact your operating system manufacturer.