*** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE

[Former Member]

Hi Team,

Our BPC System is down. In MMC message server & Dispatcher were running fine in green. But we are unable to open the GUI.

We found the log

As per log we checked both the Application and database time & time zones ., both are running in the same time. But we are unable to login into sap.

Kindly help us to resolve this issue.

A  The local time of the application server is not correct..

A 

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

M  *** WARNING => PfStatWrite: missing STAT_END for opcode STAT_COMMIT [pfxxstat.c   4239]

E  *** ERROR => EnqMemMakeNewStamp: negative local time progress: Utc = 1358063864, LastUtc = 1358064281, Diff: -417 [enxxmgen.h   988]

E  *** ERROR => EnqMemMakeNewStamp: negative time progress: shared 1 358064282 6000 local 1 358063864 [enxxmgen.h   1037]

E  EnqMemMakeNewStamp: try to compensate internally

E  *** ERROR => EnqMemMakeNewStamp: negative time progress: shared 1 358064282 7000 local 1 358063864 [enxxmgen.h   1037]

E  EnqMemMakeNewStamp: try to compensate internally

B 

B Sun Jan 13 19:22:26 2013

B  Disconnected from connection 1, con_da={++DBO++0010,13000490}

A 

A Sun Jan 13 19:57:27 2013

A  *** ERROR => zdate_gettime: Service for ABAP time in EMERGENCY MODE. [zdate.c      1409]

B 

B Sun Jan 13 20:57:28 2013

B  Connect to ++DBO++0010 as  with MSSQL_SERVER=SSGMELDQDB2\BPQ MSSQL_DBNAME=BPQ OBJECT_SOURCE=bpq

C  Thread ID:4664

C  Network connection used from SSGMELBPQCI1 to SSGMELDQDB2\BPQ using tcp:SSGMELDQDB2\BPQ

C  Network connection used from SSGMELBPQCI1 to SSGMELDQDB2\BPQ using tcp:SSGMELDQDB2\BPQ

C  GetDbRelease: 10.50.2769

C  GetDbRelease: Got DB release numbers (10,50,2769)

B  Connection 1 opened (DBSL handle 1)

B 

B Sun Jan 13 21:17:26 2013

B  Disconnected from connection 1, con_da={++DBO++0010,13000492}

B 

B Sun Jan 13 22:57:30 2013

B  Connect to ++DBO++0010 as  with MSSQL_SERVER=SSGMELDQDB2\BPQ MSSQL_DBNAME=BPQ OBJECT_SOURCE=bpq

C  Thread ID:4664

C  Network connection used from SSGMELBPQCI1 to SSGMELDQDB2\BPQ using tcp:SSGMELDQDB2\BPQ

C  Network connection used from SSGMELBPQCI1 to SSGMELDQDB2\BPQ using tcp:SSGMELDQDB2\BPQ

C  GetDbRelease: 10.50.2769

C  GetDbRelease: Got DB release numbers (10,50,2769)

B  Connection 1 opened (DBSL handle 1)

B 

B Sun Jan 13 23:17:26 2013

B  Disconnected from connection 1, con_da={++DBO++0010,13000494}

Regards

Raghu

[Sajid]

Hi Raghu,

Were you able to resolve this issue?

Thanks

Sajid

[Former Member]

I Hope the issue fixed for you in time. In our scenario the time changed on HANA DB server to Old DST. This is due to ntp service went down. After starting ntp service, Issue resolved.

[Former Member]

Hi,

Please stop both SAP services & DB services.

Make sure no SAP or DB services are running. Then try to start the DB Services & SAP Services and check whether your issue is resolved or not.

Thanks and Regards,

Vimal

[JPReyes]

Seems like you need to patch your kernel

Read,

Note 1730322 - Tracing the time synchronization with the database server

Regards

Juan