Database locks?

[VergeResources]

We are having a situation that is driving our DBA crazy... We have a test DB2 region (sits on an IBM mainframe). Since it is a test environment, the DBA creates new tables and alters existing ones on a regular basis. However, it seems that if anyone is connected to the test server using the DB2 client, he is prevented from making alterations. It appears that the entire database (only tables under the tableowner being queried) is locked from being changed. Once we kick all users off, his alterations work fine. Should this be happening? If so, is there a way to kick all users off without individually notifying them? I was hoping we could force the DB connection through a proxy server that we could shut down... We can't shutdown the datajoiner server because it is used to connect to other database regions.

 

[gregsimpson]

I have had similar problems on a different platform. Notes below sorted it for me.

List the active connections by issuing a DB2 LIST APPLICATIONS command.

Use the DB2 FORCE APPLICATION ALL command to terminate all DB2 connections.


Use the DB2 FORCE APPLICATION command to terminate selected DB2 connections. For example, issue the following command to terminate application handles 3, 45 and 87 (as determined by using the LIST APPLICATIONS command):


DB2 FORCE APPLICATION( 3,45 87)


Cheers
Greg

 

[VergeResources]

Thanks for the tip. I'm having trouble getting the DB2 LIST APPLICATIONS command to work:

db2 => list applications
SQL1096N The command is not valid for this node type.
db2 => list applications for database wfprod
SQL1427N An instance attachment does not exist.

But once I sort that out, it should help out!