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, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content