SAP Knowledge Base Article - Preview

2426912 - Repserver crashed due to all available memory was consumed - SRS

Symptom

  • The host machine running SAP Replication Server (SRS) crashed. All available memory was consumed.  A tail of the SRS errorlog does not show any errors:

I. 2017/01/12 12:21:55. The DSI thread for database 'DR_PRD_REG_1.DB1' is started.
I. 2017/01/12 12:30:04. ...... connected to server 'DR_EXT_REG_1' as user 'rep_maint'.
I. 2017/01/12 12:30:05. ...... connected to server 'DR_PRD_REG_1' as user 'rep_maint'.
I. 2017/01/12 12:35:05. Connection to server 'DR_EXT_REG_1' as user 'rep_maint' has been faded out (closed).
I. 2017/01/12 12:35:05. Connection to server 'DR_PRD_REG_1' as user 'rep_maint' has been faded out (closed).
I. 2017/01/12 12:50:03. ...... connected to server 'DR_EXT_REG_1' as user 'rep_maint'.
I. 2017/01/12 12:50:03. ...... connected to server 'DR_PRD_REG_1' as user 'rep_maint'.

  • OS resident set size (Top RES) for repserver process exceeds what SRS ‘admin stats, mem_in_use' shows.
  • Repserver process was killed by the OS OOM (out of memory) killer. The following message can be seen in the OS errorlog.
    For Linux:
    kernel: repserver invoked oom-killer:
    Out of memory: Kill process 12719 (repserver) score 646 or sacrifice child
    Killed process 12719 (repserver) total-vm:100574752kB, anon-rss:85081964kB, file-rss:436kB, shmem-rss:0kB


Read more...

Environment

  • SAP Replication Server (SRS) 15.7.1
  • SAP Replication Server (SRS) 16.0

Product

Sybase Replication Server 15.7, real-time loading edition

Keywords

Repserver, RS, CR 818442, CR 792057, memory_control, smart , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Problem

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.