Try OpenEdge Now
skip to main content
Database Administration
Protecting Your Data : Recovering a Database : Releasing shared memory
 

Releasing shared memory

If the broker dies or is killed by some means other than the database shutdown command, it does not release attached shared-memory segments. Use PROUTIL -C DBIPCS to verify shared memory has not been released; use the UNIX command ipcrm -m to free it.
Use PROUTIL with the DBIPCS qualifier to display the status of shared-memory segments attached by all OpenEdge databases on the system:
proutil -C DBIPCS
You do not have to include a database name.
Here is an example of the status output:
OpenEdge SHARED MEMORY STATUS
 ID  ShMemVer  Seg#  InUse   Database
 68      -      -     -      (not OpenEdge)
100      3      0     Yes    /db/work5/sports
101      3      1     -      /db/work5/sports
120      3      0     No     /db/work5/test
150      2      -     -      (unsupported shared memory version)
The table below describes the display fields in the output.
Table 25. Shared-memory segment status fields
Field
Description
ID
Indicates the shared-memory ID.
ShMemVer
Specifies the shared-memory version.
Seg#
Indicates the shared-memory segment number. One database can own more than one segment.
InUse
Specifies whether the segment is in use. Yes or No values are displayed only if the segment is number 0. All other segments show a dash (-). To determine whether a set of segments is in use, check the InUse value of segment 0 for the relevant database.
Database
Represents the full path name of the database.