killing the IDS-database "softly".

Hello! I want to reboot a SLES10/SP2-Server with an IDS 7.31 Database running on it. I`ve got a cdr-problem and i must do a reboot, but i will stop the database first and i have the problem that the database is not accessible. A "cdr stop" does not come back, a "cdr connect" or "cdr disconnect", too. So i want to kill the database "softly" before i start the reboot. How can i kill my IDS-7.31 Database "softly" under Suse Linux Enterprise Server 10 SP2? Under our old Unix SCO-System we do this the following way: 1. KILL -TERM pid 2. KILL -PIPE pid Output in the online.log: "The Master Daemon Died" This is ok! I want this output under our Linux-System. This works every time under an Unix-System, but under SLES10 i can`t do this this way. I don`t wanna kill the database-process hard with "kill -9 pid", so i search for an alternative way to kill the database "softly". Every response is welcome and excuse me for my poor school-english. Greetings Sascha

Hello. Have you tried to put the database in quiescent mode, and then offline, after??? Can you open the onmonitor utility ??? The database responds to any onmode command??? Or it hangs everything???? (abnormal behaviour) Best regards. Em 23/09/2010 10:27, SASCHA KURATIS escreveu: > Hello! > > I want to reboot a SLES10/SP2-Server with an IDS 7.31 Database running on it. > I`ve got a cdr-problem and i must do a reboot, but i will stop the database > first and i have the problem that the database is not accessible. > A "cdr stop" does not come back, a "cdr connect" or "cdr disconnect", too. > So i want to kill the database "softly" before i start the reboot. > How can i kill my IDS-7.31 Database "softly" under Suse Linux Enterprise > Server 10 SP2? > > Under our old Unix SCO-System we do this the following way: > 1. KILL -TERM pid > 2. KILL -PIPE pid > > Output in the online.log: "The Master Daemon Died" > This is ok! I want this output under our Linux-System. > > This works every time under an Unix-System, but under SLES10 i can`t do this > this way. > I don`t wanna kill the database-process hard with "kill -9 pid", so i search > for an alternative way to kill the database "softly". > > Every response is welcome and excuse me for my poor school-english. > > Greetings > Sascha > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Alexandre Marini Tecnologia da Informação - DBA msn: alexandre_marini@hotmail.com SEFAZ-MS / SGI-UGSR / Sistemas IBM-Informix Cert-Info-Mgmt_color IBM Informix Dynamic Server Certified Professional V10 / V11

The Problem is that CDR hangs. The Status of one server is "Connecting" and the Status doesn`t change to "Connected". I can`t stop the Replication with a "cdr stop" and i can`t connect/disconnect the server which is in the "Connecting"-State. This command`s are coming not back. Output in the online.log: 14:54:07 CDR NIF a stop has been requested and no NIF context exists. 14:54:07 (12644) connection rejected - no calls allowed for sqlexec 14:54:07 CDR NIF shutdown waiting for 1 site(s) to disconnect If CDR is still waiting, i can`t shutdown the database. In 9 of 10 cases the database shows a behaviour like this. I think CDR is in an "infinite loop", because it wait`s for the disconnect of this one CDR-Client, so i have to kill the database and i don`t want to do this with a "kill -9". I search for a possibility to kill the database "soft". Any ideas? Sascha

onmode -ky This is the correct way to bring the engine offline killing off all client processes. If you want the engine to wait until client processes disconnect on their own before shutting down use: onmode -uy If that doesn't work, kill -9 the ADM VP (usually the second VP on the onstat -g glo report), if you do that the MSC VP will shutdown the enginecorrectly as soon as it fails to handshake with the ADM VP a few seconds later. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Sep 23, 2010 at 10:27 AM, SASCHA KURATIS < sascha.kuratis@westfleisch.de> wrote: > Hello! > > I want to reboot a SLES10/SP2-Server with an IDS 7.31 Database running on > it. > I`ve got a cdr-problem and i must do a reboot, but i will stop the database > first and i have the problem that the database is not accessible. > A "cdr stop" does not come back, a "cdr connect" or "cdr disconnect", too. > So i want to kill the database "softly" before i start the reboot. > How can i kill my IDS-7.31 Database "softly" under Suse Linux Enterprise > Server 10 SP2? > > Under our old Unix SCO-System we do this the following way: > 1. KILL -TERM pid > 2. KILL -PIPE pid > > Output in the online.log: "The Master Daemon Died" > This is ok! I want this output under our Linux-System. > > This works every time under an Unix-System, but under SLES10 i can`t do > this > this way. > I don`t wanna kill the database-process hard with "kill -9 pid", so i > search > for an alternative way to kill the database "softly". > > Every response is welcome and excuse me for my poor school-english. > > Greetings > Sascha > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --0016e64f91567cd3e704912a75a9