lockdbase
Prevents all further users, except the database owner and (on UNIX) the super-user, from logging on to the specified database. The -a option also prevents the database owner from logging on.
Syntax
lockdbase {-a} {database}
Options
-a Prevents all users including the database owner from logging on. On UNIX, the super-user can still log on.
Parameters
database The identity of the database on the local host to be locked. This can be its path-name (absolute or relative), or the system name of the database, as defined in the . If omitted, the is locked.
Restrictions
Database owner or, on UNIX, super-user only.
If you are using Database Isolation, you must use realroot to select required instance of Reality before running lockdbase.
Comments
lockdbase only prevents users logging on. It does not log off currently logged-on users.
lockdbase without the -a option is not effective if users are allowed to log onto the database under the database owner's user-id. The database owner is the user-id under which the database was created.
The TCL command INHIBIT-LOGONS can also be used to lock the database. INHIBIT-LOGONS supports an A option, similar to lockdbase -a.
To unlock the database, use unlockdbase or the TCL command ENABLE-LOGONS.
UNIX
The database lock is maintained by a LOCK.FILE with zero permissions, created in the database directory by lockdbase. The lock is therefore maintained across a system re-boot or shut-down of the Reality daemons.
Recommendations on the management of UNIX user-ids for a Reality database are provided in the topic User-ids.
Windows
The database lock is maintained by lockdbase setting a Locked value in the database registry entry to zero. The lock is therefore maintained across a system re-boot or shut-down of the Reality services.