Kbase P43980: disconnected webspeed agent through promon but bi file still
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/09/2003 |
|
Status: Unverified
FACT(s) (Environment):
Sun Solaris SPARC
FACT(s) (Environment):
Progress 9.1C
SYMPTOM(s):
9.1C18
disconnected WebSpeed agent through promon but bi file still growing
parent pid of _progres session is 1
attempted kill -2
attempted kill -8 but no core or protrace generated
Large File Support is not enabled
FIX:
If you have attempted to disconnect a user from the database and the user hasn't fully died, i.e. it is still visible within the operating system process list but is not visible as a client to disconnect within promon then the process may be defunct.
Review the database log and see if any messages were posted related to that client disconnecting or beginning transaction backout.
If a reasonable amount of time has passed (3 - 5 minutes) and no message has been posted to the database log for that client then it may be necessary to issue a kill -9 against that PID.
There is a possibility that if the client is holding resources then killing the process may trigger an emergency shutdown of the database.
This may be unavoidable due to several circumstances:
1) If large file support for the database is not enable then eventually the BI will hit the 2 gig limit on file size then the database will shutdown
2) If the drive runs out of space to support additional BI growth then the database will be shutdown.
Under good conditions the client will be killed and a note will be posted in the database log that that users transactions (if it held any) are being backed out.
Under bad conditions the client will be killed and if it is holding a resource that can not be recovered by the WatchDog or the Borker then the broker will shutdown the database to preserve integrity.