Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

ZDATE_ILLEGAL_LOCTIME

Hi all,

Recently we have migrated our data center to other location which is occupied in other time zone. Before cut over, we synced entire database from source to target server.

After migration we have changed the time zone and time.

But we are facing critical issue with dumps. These are coming very frequently.

Please look into this and suggest ASAP.

Runtime Errors ZDATE_ILLEGAL_LOCTIME

Date and Time 08.04.2009 08:54:23

-


Short text

The local time of the application server is not correct.

What happened?

Error in the SAP kernel.

The current ABAP "SAPLSLVC_FULLSCREEN" program had to be terminated because the

ABAP processor detected an internal system error.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Error analysis

The ABAP interpreter always determines the local time relative to the

database time. To do so, it obtains both the time of the application

server and that of the database at regular intervals. The times must

meet specific plausibility criteria - for example, the time of the time

stamp obtained second cannot be earlier than that of the time stamp

obtained first.

In this case, the plausibility criteria for the local time of the

application server were not met.

Earlier time stamp: "Wed Apr 08 08:56:53 2009 "

Later time stamp: "Wed Apr 08 08:54:22 2009 "

How to correct the error

It is possible that the time of the application server was set forward

or back in the running system.

Ensure that the times and time zones of the application server and

database server match and restart the system.

System environment

SAP-Release 700

Application server... "pepwav71238"

Network address...... "11.192.240.178"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "2x Intel 801586"

Character length.... 8 Bits

Pointer length....... 32 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "PEPWAV71238"

Database type..... "ORACLE"

Database name..... "SOL"

Database user ID.. "SAPSR3"

Char.set.... "English_United State"

SAP kernel....... 700

created (date)... "Apr 2 2006 23:01:26"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "OCI_10103_SHARE "

Patch level. 52

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory consumption

Roll.... 8112

EM...... 10452960

Heap.... 0

Page.... 1966080

MM Used. 7109816

MM Free. 205248

User and Transaction

Client.............. 400

User................ "T_SMISHRA"

Language key........ "E"

Transaction......... "CRM_DNO_MONITOR "

Program............. "SAPLSLVC_FULLSCREEN"

Screen.............. "SAPLSLVC_FULLSCREEN 0500"

Screen line......... 0

Information on where terminated

Termination occurred in the ABAP program "SAPLSLVC_FULLSCREEN" - in

"SYSTEM-EXIT".

The main program was "CRM_DNO_SERVICE_MONITOR ".

In the source code you have the termination point in line 0

of the (Include) program " ".

Regards

Nick Loy

Former Member
Not what you were looking for? View more on this topic or Ask a question