SAP Knowledge Base Article - Preview

2914518 - SAP ASE became non-responsive to the repserver - SRS

Symptom

  • The rep agent was stuck.  There are two known ways the non-responsive status can happen:
    • "suspend connection ... with nowait" 
    • or a timeslice issue from the ASE 
  • Recycled the rep server and tried to kill the agent, but after the error below it was still not responsive. 
  • Ended up having to reboot the ASE server to clear the following timeslice error and stack:

timeslice error: spid XXX  exhausted its 'time slice' of XXX milliseconds and additional 'cpu grace time' of XXX ticks (XXXX milliseconds). It has been marked for termination.

This Adaptive Server process has had XXXXXX major and XXXXXX minor page faults since boot.

sybnet__send_async
sybnet__complete_io
sybnet_read
np_io_read
ct__tds_recvpkt
ct__tds_get_bytes
ct__tds_read_token
ct__tds_resproc.fdpr
ct__chkpt_results
ct_async_exec_stack
ct__api_async
ct_results.fdpr
usctresults
ra_get_rs_truncpt


Read more...

Environment

  • SAP Adaptive Server Enterprise 16.x
  • SAP Adaptive Server Enterprise 15.7
  • SAP Replication Server 15.7
  • SAP Replication Server 16.x

Product

SAP Adaptive Server Enterprise 15.7

Keywords

KBA , BC-SYB-REP , Sybase Replication Server (standalone) , 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 ONE Support launchpad (Login required).

Search for additional results

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