Find another process and kill it.

Change the default schema/database.

schema:gisq

Sometimes users set off queries that may take a very long time to complete. We may want to find such long running processes and stop them. Some kind of administrative account is usually required.

SHOW PROCESSLIST;
KILL 16318

LIST APPLICATION;
-- 294 and 306 are "Appl Handle" values
FORCE APPLICATION (294,306)

SELECT * FROM pg_stat_activity;

SELECT sid, serial#, username,
       TO_CHAR(logon_time,'Month dd hh24:mi:ss')
  FROM sys.v_$session;
ALTER SYSTEM KILL SESSION '12,33'
-- 12,33 is the sid and serial#

USE master;
SELECT spid , nt_username,
       datediff(s,login_time,GETDATE())
   FROM sysprocesses;
DECLARE @var1 int
SELECT @var1 = spid 
  FROM sysprocesses
 WHERE nt_username='andrew'
   AND spid<>@@spid
EXEC ('kill '+@var1);
SELECT spid , nt_username,
       datediff(s,login_time,GETDATE())
   FROM sysprocesses;

SHOW PROCESSLIST;
KILL 16318

These commands may be executed by a system administrator using the CLP (command line processor - enter db2 at the prompt).

Use the KILL command. Does what it says.

We can list the processes with the operating system command

miminfo -u

We can kill process number 123 in database GISQ with the command

mimcontrol -l 123 GISQ

sysprocesses in the master database includes all the SQL statements that are currently running. @@spid is your process. @var1 is a local variable.

Users

Create a new user

Read tables from another schema/database

Change the default schema/database.

Find another process and kill it.

Set a timeout.

Change my own password

Who am I?