Symptom
- One or more dump database and/or dump transaction commands are sleeping and not finishing
- A dbcc stacktrace on the sleeping dump transaction command will look something like this
upsleepgeneric
dmpld_wait_lock_hist_file
dmpld_upd_dump_history_file
dmpx_truncatemain
dmpxact
- A dbcc stacktrace on a sleeping dump database command will look something like this
upsleepgeneric
dmpld_wait_lock_hist_file
dmpld__add_dump_record
- The stored procedure sp_dump_history is being executed to purge history and it is not completing
- A dbcc stacktrace on the sleeping sp_dump_history spid might look something like this
upsleepgeneric
fio__p_sema
ufopen
dmpld__read_and_expire_history
dmpld_purge_dump_hist
- Alternate dbcc stacktrace on the sleeping sp_dump_history spid might look something like this
upsleepgeneric
dmpld_wait_lock_hist_file
dmpld_save_dmphistfd
dmpld_write_dump_record
dmpld__read_and_expire_history
dmpld_purge_dump_hist
- A timeslice message is seen in the SAP ASE errorlog with the failure in the module write and a stacktrace similar to this
ufwrite
ufprintf
dmpld_write_dump_record
dmpld__read_and_expire_history
dmpld_purge_dump_hist
- In cases of the sleeping spids, a kill of the sleeping spid will not be responsive and a reboot is necessary to clear them.
- The configuration parameter "enable dump history" is enabled.
Read more...
Environment
- SAP Adaptive Server Enterprise 16.0 (ASE)
- SAP Adaptive Server Enterprise 15.7 (ASE)
Product
Keywords
CR817868, CR#817868, 817868, dumphist, purge_dump_history, deadlock , 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.