3320131 - 8009 errors reported in sp_dump_history list report - SAP ASE

• sp_dump_history reporting an Error_8009 for multiple user databases.  This can be seen in several different ways:
  • On the client:
    Msg 8009, Level 16, State 1: Server 'userdb1', Line 1: Error encountered by Backup Server. 
  • In the dumphistory:
    TRAN         7 userdb1          0 Mar 14 20XX  4:18:35:680PM dump.error     *                         0 no       Error_8009 *    
    
    
• In the backupserver log examples:
  The 'WriteFile' call failed for database/archive device while working on stripe device 'R:\dbbackup\audit.XXXXXX.XX_XX_XX.XX.dmp' with error number 112 (There is not enough space on the disk). Refer to your operating system documentation for further details.
  ERROR: Emulator interprocess communication failed with error state = 16, error code=232, system message=The pipe is being closed.
  ERROR: Emulator interprocess communication failed with error state = 9, error code=109, system message=The pipe has been ended.
  
  The 'CreateFile' call failed for database/archive device while working on stripe device '\\<IP_ADDRESS>\<DIRECTORY_1>\<SUB_DIRECTORY_2>\<SUB_DIRECTORY_3>\\\dblogs\<DATABASE>.TRAN.<TIMESTAMP>' with error number 121 (The semaphore timeout period has expired). Refer to your operating system documentation for further details. Look for '<DATE_TIMESTAMP>: A00: ' in the backup server errorlog for additional information from SYBMULTBUF.

• SAP Adaptive Server Enterprise (ASE) 16.0
• Windows Operating System

 Error 8009, 8009, CreateFile, CreateFile call, archive device, archive, stripe device, stripe, error number 121, semaphore, timeout, timeout period, expired, sybmultbuf , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To