Is there a v8 equiv of v7 db2_kill??

[allenj]

Red Hat AS

DB21085I Instance "md" uses "32" bits and DB2 code release "SQL08012"
with level identifier "02030106". Informational tokens are "DB2
v8.1.0.16", "s030508", "MI00048", and FixPak "2".

I am having various and sundry problems w/ my v8 DB not coming down
cleanly after a db2stop - It leaves mem segments lying around.. I
then have to reboot the server to clean up and db2start again...

In v7, I believe there was a db2_kill utility to help with this.

But I can't find db2_kill under v8 - is there an equivalent utility
or functionality?

TIA

allen

[Blair Adamache]

db2_kill exists on v8. Just ran it on fp4:

C:\tmp>db2_kill
rah: GRANITE3
GRANITE3: db2nkill /i:DB2 /n:0 completed rc=0

Search on db2_kill here:
http://publib.boulder.ibm.com/infoce...help/index.jsp

al****@ndr.com wrote:

Red Hat AS

DB21085I Instance "md" uses "32" bits and DB2 code release "SQL08012"
with level identifier "02030106". Informational tokens are "DB2
v8.1.0.16", "s030508", "MI00048", and FixPak "2".

I am having various and sundry problems w/ my v8 DB not coming down
cleanly after a db2stop - It leaves mem segments lying around.. I
then have to reboot the server to clean up and db2start again...

In v7, I believe there was a db2_kill utility to help with this.

But I can't find db2_kill under v8 - is there an equivalent utility
or functionality?

TIA

allen

[Knut Stolze]

al****@ndr.com <al****@ndr.com> wrote:

Red Hat AS

DB21085I Instance "md" uses "32" bits and DB2 code release "SQL08012"
with level identifier "02030106". Informational tokens are "DB2
v8.1.0.16", "s030508", "MI00048", and FixPak "2".

I am having various and sundry problems w/ my v8 DB not coming down
cleanly after a db2stop - It leaves mem segments lying around.. I
then have to reboot the server to clean up and db2start again...
You might want to use "ipcs" and "ipcrm" to cleanup shared memory segments
and queues. This can avoid the reboot.
In v7, I believe there was a db2_kill utility to help with this.

But I can't find db2_kill under v8 - is there an equivalent utility
or functionality?

It should be under sqllib/bin/. You should probably also verify your
installation if you don't have db2_kill and if you also have various other
problems.

--
Knut Stolze
Information Integration
IBM Germany / University of Jena

[allenj]

Well, I guess I'm hallucinating. It is *not* in my
FP4 DB2 Workgroup on Linux, either under ~/sqllib/bin
or /opt/IBM/db2/V8.1/...

What OS are you on?

On v7, it is in ~/sqllib/bin as an external executable.
Is it a DB2 SQL/CLP cmd in v8 (like CREATE TABLE)??

aj

On Thu, 20 Nov 2003 17:20:41 -0500, Blair Adamache
<ba*******@2muchspam.yahoo.com> wrote:

db2_kill exists on v8. Just ran it on fp4:

C:\tmp>db2_kill
rah: GRANITE3
GRANITE3: db2nkill /i:DB2 /n:0 completed rc=0

Search on db2_kill here:
http://publib.boulder.ibm.com/infoce...help/index.jsp

al****@ndr.com wrote:

Red Hat AS

DB21085I Instance "md" uses "32" bits and DB2 code release "SQL08012"
with level identifier "02030106". Informational tokens are "DB2
v8.1.0.16", "s030508", "MI00048", and FixPak "2".

I am having various and sundry problems w/ my v8 DB not coming down
cleanly after a db2stop - It leaves mem segments lying around.. I
then have to reboot the server to clean up and db2start again...

In v7, I believe there was a db2_kill utility to help with this.

But I can't find db2_kill under v8 - is there an equivalent utility
or functionality?

TIA

allen

[Mark A]

<al****@ndr.com> wrote in message
news:3f****************@news.supernews.com...

Well, I guess I'm hallucinating. It is *not* in my
FP4 DB2 Workgroup on Linux, either under ~/sqllib/bin
or /opt/IBM/db2/V8.1/...

What OS are you on?

On v7, it is in ~/sqllib/bin as an external executable.
Is it a DB2 SQL/CLP cmd in v8 (like CREATE TABLE)??

aj

On my DB2 for Linux ESE Fixpak 4, db2_kill is a script that is located here
(note that db2inst1 is the instance owner):
/home/db2inst1/sqllib/bin

However, the script will not work under bash, you need ksh.

[Mark A]

Here is the ksh script if you want it:

#! /bin/ksh -p
#-----------------------------------------------------------------------
# (C) COPYRIGHT International Business Machines Corp. 1997
# All Rights Reserved
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# NAME: db2_kill
#
# FUNCTION: db2_kill terminates all the engine processes drastically
# on all the nodes.
# It is never a formal way to terminate engine processes.
#
# db2_kill is supplied as-is as an example of how to perform this function.
# There is no warranty or support.
#-----------------------------------------------------------------------
RAHSLEEPTIME=86400
export RAHSLEEPTIME

#-----------------------------------------------------------------------
# Function : runningEE
#
# - Returns true if the system is running EE; false otherwise.
#-----------------------------------------------------------------------
function runningEE
{
ee=1

if [ -f "$userhome/sqllib/db2nodes.cfg" -o \
-n "$RAHOSTFILE" ]; then
#
# Make sure the db2nodes.cfg is not for single node environment
#
numberOfLines=`grep -v '^ *#' $userhome/sqllib/db2nodes.cfg | wc -l |
awk -F' ' '{print $1}'`
if [[ $numberOfLines -eq 1 ]]; then

hostFromFile=`cat $userhome/sqllib/db2nodes.cfg | awk -F' ' '{print
$2}'`
shortHostFromFile=${hostFromFile%%.*}

hostFromCommand=`hostname`
shortHostFromCommand=${hostFromCommand%%.*}

#
# Only execute the locally if the number of lines in db2nodes.cfg
is 1 and
# that the hostname specified is the same as the local hostname
#
if [[ $shortHostFromFile != $shortHostFromCommand ]]; then
echo "The short host name in db2nodes.cfg is not the same the
local hostname."
exit 2 ;
fi

else
ee=0
fi
fi

return $ee
}

# We expect DB2INSTANCE variable is set
if [ -z "$DB2INSTANCE" ]; then
echo "DB2INSTANCE environment variable is not set."
exit 1;
fi

# An easy way to find out the home directory
# of DB2INSTANCE
userhome=~${DB2INSTANCE}
eval userhome=$userhome

# Unset RAHOSTLIST environment
# variable since it will
# interfere with rah.
unset RAHOSTLIST

runningEE
if [[ $? -eq 1 ]]; then
exec db2nkill 0
else
exec rah "|>> db2nkill []"
fi

[Darin McBride]

al****@ndr.com wrote:

Well, I guess I'm hallucinating. It is *not* in my
FP4 DB2 Workgroup on Linux, either under ~/sqllib/bin
or /opt/IBM/db2/V8.1/...

What OS are you on?

On v7, it is in ~/sqllib/bin as an external executable.
Is it a DB2 SQL/CLP cmd in v8 (like CREATE TABLE)??

In v7, it was only part of EEE. In v8, then, it's only part of ESE.

[allenj]

Sorry, I'll have to disagree. I have a v7 WorkGroup Server (WSE)
running on Red Hat 7.3 under FP 9 that has db2_kill in ~/sqllib/bin

However, I suspect you are correct about db2_kill only being in ESE
under v8. Wonder why its not in the WorkGroup version?

aj

On Tue, 25 Nov 2003 17:32:15 GMT, Darin McBride
<dm******@naboo.to.org.no.spam.for.me> wrote:

al****@ndr.com wrote:

Well, I guess I'm hallucinating. It is *not* in my
FP4 DB2 Workgroup on Linux, either under ~/sqllib/bin
or /opt/IBM/db2/V8.1/...

What OS are you on?

On v7, it is in ~/sqllib/bin as an external executable.
Is it a DB2 SQL/CLP cmd in v8 (like CREATE TABLE)??

In v7, it was only part of EEE. In v8, then, it's only part of ESE.