The report RSDBTIME is a diagnostic tool to detect time and time zone inconsistencies in SAP system. Different time sources must supply consistent times.
Time sources are:
- UTC, seconds since 1970/1/1 Greenwich time
- Database, virtual database table with time info
- systemcall gettimeofday, enqueue/vb-timestamp
- systemcall time/localtime, abap-function ‘CLOCK’
- abap-variables SY-DATUM, SY-UZEIT
For a consistent and proper working, all times must contain the same values. Differences of few seconds are still tolerated.
You can perform the report using the transaction code SE38 or SA38.
The example of consistent output of report RSDBTIME,
Universal Time Coordinated UTC....: 1597805866
Date and time of database.........: 19.08.2020 10:57:46
Date and Time of R/3-Kernel.......: 19.08.2020 10:57:46
Date and Time of ABAP-Processor...: 19.08.2020 10:57:46
ABAP Timezone Setup ..............: 28800
Date and Time / localtime ........: 19.08.2020 10:57:46
No Time Inconsistencies detected !
Checking GET RUN TIME from 10:57:47 to 10:57:52 during 00:00:05
GET RUN TIME result ..............: 5,002,303 us
GET RUN TIME time measurement accuracy ok !
The example of inconsistent output of report RSDBTIME. The resolutions are also stated which you can refer as below,
Universal Time Coordinated UTC....: 1597661024
Date and time of database.........: 17.08.2020 17:45:52
Date and Time of R/3-Kernel.......: 17.08.2020 17:43:44
Date and Time of ABAP-Processor...: 17.08.2020 17:45:52
ABAP Timezone Setup ..............: 25200
Date and Time / localtime ........: 17.08.2020 17:43:44
WARNING: Time Differences detected !
What's to do now ?
1) compare all times with wall clock
2) find out, which time source is going wrong
3) check timezone setup of wrong-going time source
4) check if UTC contains correct number of seconds
since 1970/01/01 Greenwich time
5) check if default timezone setup is correct
Typical error reasons:
- different timezone setup for database and R/3 instances
- wrong UTC plus wrong timezone resulting in correct local time
(utc in all hosts over the world has to be the same)
Possible Solutions
set corrects TZ before starting database and R/3 servers
--- or ---
remove all explicit timezone-setups. Only practicable
if default setup is correct.
Checking GET RUN TIME from 17:45:53 to 17:45:58 during 00:00:05
GET RUN TIME result ..............: 5.000.000 us
GET RUN TIME time measurement accuracy ok !
Checking ABAP system timezone settings
ABAP system timezone settings consistent !
Reference
- 741734 – Incorrect times due to the time zone settings
- 101726 – Incorrect times and time zone setting
- 1165982 – Changes to time zone settings at operating system level
- 1260674 – Effectiveness of changes to time zone Customizing
