Consultor Eletrônico



Kbase 17746: How to find PID & Shared Memory used by a database on NT
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   5/10/1998
How to find PID & Shared Memory used by a database on NT

DRAFT COPY - Currently under review and edit.

INTRODUCTION:
=============
This Kbase describes how you with Progress utility's only finds the
PID of a server, either if it is crashed or in use. When using 8.2X
the PID is stored in the log file but in case this has been deleted
or that another version is being used use this KBase
WHY YOU NEED TO KNOW THIS:
===========================
If a database crashes and leaves processes hanging, knowing the PID
(Process ID) helps you clean out the memory. It is simple to see what
process to kill if only you have one _MPROSRV.EXE running but if more
databases are running it is not.

PROCEDURAL APPROACH:
====================
We strongly suggest that all databases are stopped and that the system
is examined so that the error can be pinpointed and fixed. It is NOT a
normal thing to have a chrashed database leaving processes hanging so
a check of the system is advised.

ONLINE PROCEDURES OR UTILITIES:
===============================
If this is not an option follow these steps;
CASE 1.
This case shows how to get the PID for a given database _before_ a
chrash with Progress tools.
Create a empty file with notepad, enter the following;
1 (after this a return)
1 (after this a return)
q (after this a return)
q (after this a return)
Save the file in the working directory as GETPID.TXT
Create a batch file (GETPID.BAT) with the following content
(environments must be set correctly)
C\DLC\PROMON C:\WORK\DATABASE < C:\WORK\GETPID.TXT > C:\WORK\DBPID.TXT

The GETPID.BAT can now be run whenever the databases are started and
will create the DBPID.TXT where all information should be displayed.

CASE 2
If more databases are running and you only have Progress tools, the
only way to find the PID on a _chrased_ database is to get the PID of
all the other databases using the same command as above. Then from the
Task Manager kill the Process.

Case 3.
Currently there are no information about commercialy provided programs
that does this, but FBE is developing a small utility to use. I will
update here when the program is finished.


REFERENCE TO WRITTEN MATERIAL
=============================
NT documentation.
(CFE&IMU 05/03-1998)

Progress Software Technical Support Note # 17746