Product

Brisque^® Serve 4.0

Platform

• F50—Wildcat (2 and 4 CPUs)
• 44P–170—Hammerhead
• 6F1—Condor (2, 4, and 6 CPUs)

Operating system

IBM^® AIX^® 4.3.3

Symptoms

A database lock message appears in the SQLtrans.err file indicating that a database lock (an exclusive lock) has been created and prevents access to other users. The database lock message appears when you try to connect while Brisque Serve is starting, or when FTC is running.

Cause

Sometimes when Brisque Serve is starting, the DBAdmin does not respond, and users cannot connect. This is a known problem that has been fixed and a solution will be released in the next Brisque Serve version.

Solution

1. At the command line, type root as user.
2. Type >onstat -k to display information on database locks.
3. Locate the row that contains a HDR+X lock type, which indicates an exclusive database lock, and write down the OWNER value.
4. Type >onstat -u to display information on database users.
5. Locate the row where address=OWNER (the value located in step 3), and write down the SESSID value (this is the session that caused the database lock).
6. Before proceeding to the next step, find the UNIX^® process that created the lock:
   • Type >onstat -g ses to display information on database sessions.
   • Locate the row where Session id=SESSID and write down the PID (UNIX Process ID).
   • Type >ps -ef | grep pid to display information on the UNIX process that created the lock.
     
7. Type >onmode -z to abort the session that created the lock. The exclusive lock is released.
   Note: Aborting the process from UNIX does not assure that the database process will be aborted.

Technical contact(s)

Lev Weissman

Submitted by

Lev Weissman

Date submitted

08 Dec 2003