Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Omer Khan, running several IDS 10.0 FC4 instances on Solaris 10, asked how to find which oninit PID belongs to a hung instance. Mike Magie suggested the pid column of onstat -g sch and calling Informix support; others recommended onstat -g glo, where the first CPU-class process can be killed. Fernando Nunes urged investigating the cause of the hang. Solved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello All,
I am running multiple IDS instances on one server and i am using IDS10.0 FC4
on Solaris 10.
Sometimes due to any reason, the instances gets hangs and it didn't gets
stopped by using onmode -ky. So in that case we need to kill the Informix PID
running in the Operating System. using command kill -9 <PID>
So i need to know that in the output of 'ps -ef|grep oninit' command, it gives
long list of PIDs, so how to related those process ids with the various
instances? Is there any command in IDS which tell me that which PID i need to
kill to stop that instance. As i am running multile instances so i dont want
to kill any other instance?
Can anyone help me? Thanks in advance.
Regards,
Omer Saeed Khan
↪ replying to OMER KHAN
MIKE MAGIE — — source: IIUG Forums & Mailing Lists
I would first of all call into Informix Support when you have an instance that
is hung and not responding to onmode -ky. You should be able to get to the
Down Systems group in this scenario and one of the engineers there can help
you diagnose why the engine is in that state.
You can use the 'pid' column from the output of onstat -g sch to map the pids
to the Unix ps output.
Mike
"onstat -g glo" is another easy way to list all oninit pids for a given IFX
environment.
--
Bob
-------------- Original message --------------
From: "MIKE MAGIE" <jmmagie@yahoo.com>
> I would first of all call into Informix Support when you have an instance
that
> is hung and not responding to onmode -ky. You should be able to get to the
> Down Systems group in this scenario and one of the engineers there can help
> you diagnose why the engine is in that state.
>
> You can use the 'pid' column from the output of onstat -g sch to map the pids
> to the Unix ps output.
>
> Mike
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
↪ replying to OMER KHAN
ravi vijay — — source: IIUG Forums & Mailing Lists
You can do :
onstat -g gloThe first cpu class process id you can kill to bring down the server.
Thanks
Ravi
On 8/27/08, OMER KHAN <oskhan@i2cinc.com> wrote:
>
> Hello All,
>
> I am running multiple IDS instances on one server and i am using IDS10.0
> FC4
> on Solaris 10.
>
> Sometimes due to any reason, the instances gets hangs and it didn't gets
> stopped by using onmode -ky. So in that case we need to kill the Informix
> PID
> running in the Operating System. using command kill -9 <PID>
>
> So i need to know that in the output of 'ps -ef|grep oninit' command, it
> gives
> long list of PIDs, so how to related those process ids with the various
> instances? Is there any command in IDS which tell me that which PID i need
> to
> kill to stop that instance. As i am running multile instances so i dont
> want
> to kill any other instance?
>
> Can anyone help me? Thanks in advance.
>
> Regards,
> Omer Saeed Khan
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
As someone else already pointed out, "onstat -g glo" will list all the
oninit created OS processes.
I'd like to add that in no way you should need to kill the processes. If the
instance hangs you should contact technical support and you should start by
figuring out what is a "hang"...
. Do the existing sessions still work?
. Are you able to create new sessions?
. Are the sessions "just" waiting for locks?
. Is the instance "locked" during checkpoints?
. Is the instance "locked" because the logical logs are full?
. Is the instance "locked" because of a long transaction that is being
rolled back and enters the exclusive high water mark?
These "hangs" can be caused by several situations:
. Bad configuration
. Bad application coding
. Informix BUG
. OS BUG
so, killing the instance can be a temporary workaround, but please don't
take that as a final solution.
Informix should not "hang". Wether it has reasons to do so or not must be
investigated, but don't EVER consider it as normal.
Regards.
On Wed, Aug 27, 2008 at 8:52 AM, OMER KHAN <oskhan@i2cinc.com> wrote:
> Hello All,
>
> I am running multiple IDS instances on one server and i am using IDS10.0
> FC4
> on Solaris 10.
>
> Sometimes due to any reason, the instances gets hangs and it didn't gets
> stopped by using onmode -ky. So in that case we need to kill the Informix
> PID
> running in the Operating System. using command kill -9 <PID>
>
> So i need to know that in the output of 'ps -ef|grep oninit' command, it
> gives
> long list of PIDs, so how to related those process ids with the various
> instances? Is there any command in IDS which tell me that which PID i need
> to
> kill to stop that instance. As i am running multile instances so i dont
> want
> to kill any other instance?
>
> Can anyone help me? Thanks in advance.
>
> Regards,
> Omer Saeed Khan
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.