B
bsujata89
Guest
1. agentkill used with asbman should do some validations before abruptly disconnecting the appserver agent process. 2. "Users reported a performance problem. At that time one of the AppServer agent process was causing high CPU load and had status as RUNNING when checked with asbman - i -q So they performed asbman -name qadui_ASlive - agentstop > But this was not successful, the agent was still active and had the status RUNNING So they issued below command asbman -name qadui_ASlive - agentkill <>pid>> The agent process has ended but unfortunately, the database server was also shut down. Ideally - agentkill should do some validations before abruptly disconnecting agent process. 3. Progress Support is confirming (w.r.f. case - 00452356) that using asbman - agentkill in a shared memory process is something that can cause the database to shutdown to prevent data corruption in case that the process is holding latches or buffers. It looks like that agentkill sends a kill -9 to the process and this may cause an abnormal shutdown of the database. So the suggestion for cases like that is to (workaround): - submit asbman - agentstop - If the process is still alive after some minutes, then disconnect the user from all databases using promon . - If the process is still available, then the safer solution would be to plan an environment re-start so that the database is shutdown safely. asbman - agentkill can be used but it may provoke the database crash situation. Hence - agentkill shall do some pre-validation before abruptly disconnecting agent process.
Continue reading...
Continue reading...