Unable to start the database with this error after forceful server reboot - "system error cannot attach shared memory with segment_id"

Solution Unverified - Updated -

Issue

  • Due to filesystem errors, Filesystem was mounted with read-only. Unable to umount to run fsck on this filesystem, also unable to stop database which was accessing this filesystem which led to forceful server reboot. Then, fsck was performed and filesystem mounted back in read-write mode. However, progress database was unable to start with this error - "system error cannot attach shared memory with segment_id"

Environment

  • Red Hat Enterprise Linux
  • Progress Database

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.