SAP Knowledge Base Article - Preview

3368082 - Database or log dump not happening and process is stuck and fails with "'write' call failed" error - SAP ASE.


  • Backup Server is running, dump is not happening and process is stuck.
  • Database or transaction log dump with error number 32 (Broken pipe) with the following error messages printed to the Backup Server error log:

Backup Server Internal Error: Multibuffering subprocesses died, archive /sybase/PAP_DB310523.dmp.
Backup Server: Failed to start multibuffering subprocesses for archive device '/sybase/SID_DB310523.dmp'. Look at the Backup Server error log or standard error for more information.
Backup Server: [0] The 'write' call failed for database/archive device while working on stripe device '/sybase/SID_DB310523.dmp' with error number 32 (Broken pipe). Refer to your operating system documentation for further details.

>>killed the stale process at backup and sybmultibuf at OS level. 
>>Rebooted the SID backup and Data server.
>>Rebooted the OS
>>Tried the Dump command ( Still the Dump database is stucked) despite having memory and space at the Mountpoints.

Still dump is not happening and process is stuck.



  • SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite.
  • Running on Linux server.


SAP Adaptive Server Enterprise all versions ; SAP NetWeaver all versions


"backup server"; "sybmultbuf";dumping; copy; restore; tran; transaction; OS; Linux. , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.