SAP Knowledge Base Article - Preview

3020873 - Server fails to start with error 840 on a device followed by error 3404 master database - SAP ASE

Symptom

  • ASE server bot fails with error 840 and error 3404
  • The 840 error can be seen on a system database device (likely sybsystemprocs device) or a user database device 
  • Log entries show:

    Error: 840, Severity: 17, State: 2
    Device 'sysprocsdev' (with physical name '$SYBASE/data01/sybprocs.dat', and virtual device number 1) has not been correctly activated at startup time.
    Error: 3404, Severity: 21, State: 1
    Rec_complete: Could not open controlling database (id 31514) of controlling database in multi-db transaction.
    Cannot recover the master database, exiting.
    ueshutdown: exiting

  • Generally, there are preceding errors at runtime that indicate (severe) corruption issues with the database, data and/or log device from the 840 error


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) - All versions

Product

SAP Adaptive Server Enterprise all versions

Keywords

master, transaction, Error: 840, Severity: 17, State: 2, Error: 3404, Severity: 21, State: 1, multi-db, device, OS, suicide, bypass , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.