2
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
3
<!--All rights reserved.-->
4
<!--See the file LICENSE for redistribution information.-->
7
<title>Berkeley DB: DB_ENV->set_lk_max_locks</title>
8
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
9
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
12
<a name="2"><!--meow--></a>
13
<table width="100%"><tr valign=top>
15
<h1>DB_ENV->set_lk_max_locks</h1>
18
<a href="../api_c/c_index.html"><img src="../images/api.gif" alt="API"></a><a href="../reftoc.html"><img src="../images/ref.gif" alt="Ref"></a>
26
DB_ENV->set_lk_max_locks(DB_ENV *dbenv, u_int32_t max);
29
<p>Set the maximum number of locks supported by the Berkeley DB lock subsystem.
30
This value is used by <a href="../api_c/env_open.html">DB_ENV->open</a> to estimate how much space to
31
allocate for various lock-table data structures. The default value is
32
1000 locks. For specific information on configuring the size of the lock
33
subsystem, see <a href="../ref/lock/max.html">Configuring locking:
34
sizing the system</a>.
35
<p>The DB_ENV->set_lk_max_locks method configures a database environment, not only operations
36
performed using the specified <a href="../api_c/env_class.html">DB_ENV</a> handle.
37
<p>The DB_ENV->set_lk_max_locks interface may not be called after the <a href="../api_c/env_open.html">DB_ENV->open</a>
39
If the database environment already exists when
40
<a href="../api_c/env_open.html">DB_ENV->open</a> is called, the information specified to DB_ENV->set_lk_max_locks
42
<p>The DB_ENV->set_lk_max_locks method returns a non-zero error value on failure and 0 on success.
43
<p>The database environment's maximum number of locks may also be set using the environment's
44
<b>DB_CONFIG</b> file. The syntax of the entry in that file is a
45
single line with the string "set_lk_max_locks", one or more whitespace characters,
46
and the number of locks. Because the <b>DB_CONFIG</b> file is read when the database
47
environment is opened, it will silently overrule configuration done
50
<p>The DB_ENV->set_lk_max_locks method may fail and return a non-zero error for the following conditions:
52
<p><dt>EINVAL<dd>An invalid flag value or parameter was specified.
53
<p>Called after <a href="../api_c/env_open.html">DB_ENV->open</a> was called.
55
<p>The DB_ENV->set_lk_max_locks method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions.
56
If a catastrophic error has occurred, the DB_ENV->set_lk_max_locks method may fail and
57
return <a href="../ref/program/errorret.html#DB_RUNRECOVERY">DB_RUNRECOVERY</a>,
58
in which case all subsequent Berkeley DB calls will fail in the same way.
60
<a href="../api_c/env_class.html">DB_ENV</a>, <a href="../api_c/lock_class.html">DB_LOCK</a>
62
<a href="../api_c/lock_list.html">Locking Subsystem and Related Methods</a>
64
<table width="100%"><tr><td><br></td><td align=right>
65
<a href="../api_c/c_index.html"><img src="../images/api.gif" alt="API"></a><a href="../reftoc.html"><img src="../images/ref.gif" alt="Ref"></a>
67
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>