SAP Knowledge Base Article - Preview

2356869 - Syslogshold showing wrong spid with 'starttime' fixed on 'Jan 1 1900' for dump command - SAP ASE

Symptom

  • While executing a 'dump database' or 'dump transaction' command
  • The master..syslogshold table reports a spid number that is not executing the dump command
  • And an incorrect and fixed starttime of 'Jan 1, 1900' :
select * from syslogshold
go
dbid reserved spid  (..)  starttime            name            
---- -------- ----        -------------------  -------------          
   4        0  123        Jan  1 1900 12:00AM  DUMP DATABASE

select spid, cmd, dbid from sysprocesses where cmd = "dump%"
go
spid  cmd           dbid
----  ------------- ----
 456  DUMP DATABASE    4


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0 SP02 PL00 - PL04

Product

SAP Adaptive Server Enterprise 16.0

Keywords

"dump" , "dump tran" , " Jan  1 1900 12:00AM" , "01.01.1900 0:00:00" , syslogshold , ase , sybase , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.