ZDATE_LARGE_TIME_DIFF (After migrating DB2 8.2 / 9.5)

[Former Member]

Hello,

AIX 6.1

After migrating DB2 8.2 / 9.5 and upgrade the kernel (640-374 (level)) in the SAP logon appears the dump:

ZDATE_LARGE_TIME_DIFF (Large Time Difference Between Application Server and Database).

The local clock may have been set incorrectly or the application server

and the database may be operating in different time zones. Check that

the times and time zones of the application server and database server

match. Then restart the system.

Local time in internal format................ 1303740690

Database time................................ 20110425151130

SAP Release.............. "620"

Character set............ "en_US.ISO8859-1"

The error probably occurred when installing the

R/3 system.

There is a considerable time difference between the local time of the

application server and that of the database, which prevents your SAP

System from operating correctly.

Time difference between DB and appl. server.. 3600 s

Local time zone.............................. "UTC+0 sec (GRNLNDST )"

Local time................................... "2011/04/25 14:11:30 "

UTC time..................................... "2011/04/25 14:11:30"

Local time in internal format................ 1303740690

Database time................................ 20110425151130

get the error corrected immediately.

Local time................................................ "2011/04/25 14:11:30

"

UTC time.................................................. "2011/04/25

14:11:30"

Local time in internal representation..................... 1303740690

Database time............................................. 20110425151130

I checked the date with the root users, db2 <sid> ,<sid> adm and are equal. I checked the environment variable TZ = GRNLNDST.

Bank and SAP have already stopped and left Stopped 01:00 pm. The error continues.

Any ideas?

[Former Member]

Hi,

I solved the problem as follows:

in / etc/environment, I removed the variable TZ = GRNLNDST, reboot and start the database and SAP.

tks

[Former Member]

can you try to restart your application servers , so that its time is in sync with th central instance. Have faced similar problems an usually a application server restart fixed it.

Thanks

Rishi

[Former Member]

Hi Hishi,

I don´t have application servers.

tks

[gabriele_mutti]

Hi,

Sorry I did not see who was aix

[Former Member]

Hi Gabrielle

No problems.

tks

[gabriele_mutti]

Hi,

but the database run on Vsphere?

9. Timekeeping in Virtual Machines

Most operating systems track the passage of time by configuring the underlying hardware to provide periodic interrupts. The rate at which those interrupts are configured to arrive varies for different operating systems. High timer-interrupt rates can incur overhead that affects a virtual machine's performance. The amount of overhead increases with the number of vCPUs assigned to a virtual machine.

For many Linux operating systems, the default timer interrupt-rate is high and can lead to time synchronization errors in SAP applications running in virtual machines:

Error messages in the SAP Syslog: "System time was set externally to a time in the past. Wait 1 second(s)."

At the operating system level, the clock of the virtual machine may run either too quickly or too slowly.

Time drift between the application and database server can cause ABAP short dumps with the error message ―ZDATE_LARGE_TIME_DIFF.‖

To address timekeeping issues when running SAP solutions on Linux guest operating systems:

Use Novell SLES 9 and later versions, or Red Hat RHEL 5.1 and later, since these operating system versions allow the frequency of timer interrupts to be reduced.

Follow the guidelines in SAP Note 989963 u2013 Linux: VMware timing problem.