Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. System Backup and Restore
  13. Batch Utilities

lockmgr Utility

lockmgr Utility

This utility performs the following tasks:
  • Deletes a group of locks that have a common unique identifier (
    uq
    ).
  • Lists all the application locks for a system in ascending order by
    uq
    .
  • Lists the current Rulebase host in a Rulebase Server Group.
The lockmgr utility uses the following syntax:
%SSABIN%\lockmgr [list|del uq] -rRbName -hRbHost [-vpsu] [-l]
You must specify either the
list
or
del uq
option. Use the
list
option to list the application locks and their unique identifier values or the current Rulebase host. Use the
del uq
option to delete a group of locks that have a common unique identifier.
You can use the Rulebase Server connection details by using the
-h
option or the Rulebase Server Group name by using the
-g
option. You can use the
-l
option in conjunction with the
-g
option to list the Rulebase Server connection details in the
host:port
format.
The following example lists all the application locks for a system:
%SSABIN%\lockmgr list -rodb:0:userid/password@dbserver -hlocalhost:1668
sorted locks: uq: updsync,1,1:1370482219:6150 obj: idtsync id: system=mdm_customer idt= type: w lock: ip=127.0.33.1 pid=4560 host='rb.informatica.com' ps='2013/06/06 01:30:18.2132' uq: updsync,1,1:1370482219:6150 obj: idtsyncsystem id: system=mdm_customer type: r lock: ip=127.0.0.1 pid=4560 host='rb.informatica.com' ps='2013/06/06 01:30:18.2132'
The following example deletes a group of locks based on the specified common unique identifier:
%SSABIN%\lockmgr del updsync,1,1:1370482219:6150 -rodb:0:userid/password@dbserver -hlocalhost:1668
You must use this utility with caution. Removing the locks from a running process, such as Update Synchronizer, that requires exclusive use of certain system resources might lead to data corruption and errors.
If a process detects a conflicting lock, it tries to find out the status of the job that created the lock. It deletes the locks and creates its own if the original process has crashed.
In some instances, the new process might not be able find out the status of the original process. For example, if the original process runs on a different computer or is unresponsive. The
lockmgr
utility is useful in such scenarios to remove the lock manually.

0 COMMENTS

We’d like to hear from you!