Sponsored Content
Top Forums Programming Berkeley database + row level locking Post 302429916 by vino on Wednesday 16th of June 2010 05:47:54 AM
Old 06-16-2010
Did you check the Getting Started Guide at Appendix*A.*Concurrent Processing in Berkeley DB Java Edition ? This is BDB JE 4.0.103
 

6 More Discussions You Might Find Interesting

1. UNIX Benchmarks

ocs_vtsup: error locking odm database

Someone know something about this error ? We have 5.2 and HACMP Cluster. (1 Reply)
Discussion started by: hjara
1 Replies

2. Solaris

Difference between run level & init level

what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies

3. Shell Programming and Scripting

how to split the row(array) in to fields and store in to oracle database in unix

Hi, the csv file with the delimeter #. A#B#C#D#E#F#G#H 1#2#3#4#5#6#7#8 Z#x#c#V 7#2#8#9 N. I want to read the file line by line and store in rowarray. then the rowarray content should be spilt or made to fields using the delimeter #. i am not sure can we store the fields in to... (3 Replies)
Discussion started by: barani75
3 Replies

4. Solaris

compiling Berkeley db.

Hi there, I need to install a later version of Berkeley DB on a solaris 10 server but I can not remove the previous version. I've used the configure option of --with-uniquename. It looks like the make has worked. I'm worried that the make install may interfer with the current... (0 Replies)
Discussion started by: Mickey G2
0 Replies

5. UNIX for Dummies Questions & Answers

Shell Script: Traverse Database Table Row by Row

Hello Everyone, My issue is that I want to traverse a database table row by row and do some action on the value retrieved in each row. I have gone through a lot of shell script questions/posts. I could find row by row traversal of a file but not a database table. Please help. Thanks &... (5 Replies)
Discussion started by: ahsan.asghar
5 Replies

6. Red Hat

SSL certificate generation on OS level or application level

We have a RHEL 5.8 server at the production level and we have a Java application on this server. I know of the SSL certificate generation at the OS (RHEL) level but it is implemented on the Java application by our development team using the Java keytool. My doubt is that is the SSL generation can... (3 Replies)
Discussion started by: RHCE
3 Replies
SLAPD-BDB(5)							File Formats Manual						      SLAPD-BDB(5)

NAME
slapd-bdb - BDB backend to slapd SYNOPSIS
/etc/openldap/slapd.conf DESCRIPTION
The BDB backend to slapd(8) is the recommended backend for a normal slapd database. It uses the Sleepycat BerkelyDB package to store data. It makes extensive use of indexing and caching to speed data access. CONFIGURATION
These slapd.conf options apply to the BDB backend database. That is, they must follow a "database bdb" line and come before any subsequent "backend" or "database" lines. Other database options are described in the slapd.conf(5) manual page. cachesize <integer> Specify the size in entries of the in-memory cache maintained by the BDB backend database instance. The default is 1000 entries. checkpoint <kbyte> <min> Specify the frequency for checkpointing the database transaction log. A checkpoint operation flushes the database buffers to disk and writes a checkpoint record in the log. The checkpoint will occur if either <kbyte> data has been written or <min> minutes have passed since the last checkpoint. Both arguments default to zero, in which case they are ignored. See the Berkeley DB reference guide for more details. dbnosync Specify that on-disk database contents should not be immediately synchronized with in memory changes. Enabling this option may improve performance at the expense of data security. directory <directory> Specify the directory where the BDB files containing this database and associated indexes live. A separate directory must be speci- fied for each database. The default is /var/db/openldap/openldap-data. dirtyread Allow reads of modified but not yet committed data. Usually transactions are isolated to prevent other operations from accessing uncommitted data. This option may improve performance, but may also return inconsistent results if the data comes from a transac- tion that is later aborted. In this case, the modified data is discarded and a subsequent search will return a different result. index {<attrlist>|default} [pres,eq,approx,sub,<special>] Specify the indexes to maintain for the given attribute (or list of attributes). Some attributes only support a subset of indexes. If only an <attr> is given, the indices specified for default are maintained. Note that setting a default does not imply that all attributes will be indexed. A number of special index parameters may be specified. The index type sub can be decomposed into subinitial, subany, and subfinal indices. The special type nolang may be specified to disallow use of this index by language subtypes. The special type nosubtypes may be specified to disallow use of this index by named subtypes. Note: changing index settings requires rebuilding indices, see slapindex(8). lockdetect {oldest|youngest|fewest|random|default} Specify which transaction to abort when a deadlock is detected. The default is the same as random. mode <integer> Specify the file protection mode that newly created database index files should have. The default is 0600. searchstack <depth> Specify the depth of the stack used for search filter evaluation. Search filters are evaluated on a stack to accomodate nested AND / OR clauses. An individual stack is assigned to each server thread. The depth of the stack determines how complex a filter can be evaluated without requiring any additional memory allocation. Filters that are nested deeper than the search stack depth will cause a separate stack to be allocated for that particular search operation. These allocations can have a major negative impact on server performance, but specifying too much stack will also consume a great deal of memory. Each search stack uses 512K bytes per level. The default stack depth is 16, thus 8MB per thread is used. FILES
/etc/openldap/slapd.conf default slapd configuration file SEE ALSO
slapd.conf(5), slapd(8), slapadd(8), slapcat(8), slapindex(8). OpenLDAP 2.1.X RELEASEDATE SLAPD-BDB(5)
All times are GMT -4. The time now is 11:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy