Hi,

>From your email it seems as if you still have a connection open to the
database, i.e. db2bp connection.  From the manual:
~~~~~~~~
The command line processor consists of two processes: the front-end process
(the DB2 command), which acts as the user interface, and the back-end
process (db2bp), which maintains a database connection. 
~~~~~~~~

Try a db2 list applications, make sure nothing is connected.  The 5
processes you see are standard instance processes which should be running
while the system is up.

If this isn't it, what does the db2diag.log have to say?

Cheers,
Mark


> -----Original Message-----
> From: Dimoline, Simon [SMTP:[EMAIL PROTECTED]]
> Sent: 15 November 2001 14:57
> To:   [EMAIL PROTECTED]
> Subject:      DB2EUG: db2 stalls on db2stop command
> 
> Dear All,
> Can anyone help on this.
> We are running scripts to update one instance of a database (d2), once
> updated it is then backed up and the backup used to refresh the live
> instance of the database(d1). (AIX and db2 version 5.2)
> 
> Occassionally, and this is only on the d2, during the final terminate,
> stop
> and start commands the instance stalls on the db2stop command.
> 
> The db2 processes running at that time are:
> db2gds
> db2tcpim
> db2sysc
> db2tcpcm
> db2ipccm                        
> 
> /db2/d2/sqllib/bin/db2bp 38120 5
> /db2/d2/sqllib/adm/db2stop2
> 
> We have to kill the first five processes and run a process to clean up the
> db resources using ipcs then ipcrm. The database is then manually stopped
> and started. 
> 
> Can anyone suggest why it stalls and how to rectify this. We suspect it is
> to do with buffer space or memory but we're not sure.
> One thing we have noticed is that there is a resource that ipcrn won't
> delete, it just says resource not found. There are also 2 messages
> produced
> in the script reports. The first, SQL1042C probably related to the db2stop
> and SQL1072C probably related to the next command, db2start. However,
> these
> are produced after the initial 5 db2 processes are killed so may be a red
> herring.
> 
> Simon.
> 
> 
> 
> 
> 
> "This communication is intended solely for the addressee and is
> confidential and not for third party unauthorised distribution."
> 
> =====
> To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> For other info (and scripts), see
> http://people.mn.mediaone.net/scottrmcleod

=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod

Reply via email to