Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 111 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 161 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 475 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
unable to initialize mutex: Function not implemented

356611
Member Posts: 5
Hello,
I've got the following error (I've specified --with-mutex=POSIX/pthreads/library on configure)
unable to initialize mutex: Function not implemented
/tmp/__db.001: unable to initialize environment lock: Function not implemented
while doing the following:
otsenv.open( db_dir.c_str() , DB_CREATE | DB_THREAD , 0);
Berkeley DB 4.4.20, configure with :
CC=gcc323 CXX=g++323 ~/work/src/db-4.4.20/dist/configure prefix=/users/home/lmarzullo/opt/db-4/4.4.20/ enable-cxx with-mutex=POSIX/pthreads/library enable-posixmutexes
Any idea please ?
Thanks a lot
Laurent Marzullo
I've got the following error (I've specified --with-mutex=POSIX/pthreads/library on configure)
unable to initialize mutex: Function not implemented
/tmp/__db.001: unable to initialize environment lock: Function not implemented
while doing the following:
otsenv.open( db_dir.c_str() , DB_CREATE | DB_THREAD , 0);
Berkeley DB 4.4.20, configure with :
CC=gcc323 CXX=g++323 ~/work/src/db-4.4.20/dist/configure prefix=/users/home/lmarzullo/opt/db-4/4.4.20/ enable-cxx with-mutex=POSIX/pthreads/library enable-posixmutexes
Any idea please ?
Thanks a lot
Laurent Marzullo
Comments
-
Hi Laurent,unable to initialize mutex: Function not implementedYou've forced Berkeley DB to use POSIX mutexes on a platform where they are not fully implemented. This error is most common on older Linux systems, which had basic POSIX threads but didn't implement sharing of mutexes between processes.
/tmp/__db.001: unable to initialize environment lock:
Function not implemented
To get around this, you will need to either:
* use a more recent Linux release;
* rebuild Berkeley DB without forcing the use of POSIX mutexes (but the fallback test-and-set mutexes perform poorly when there is contention); or
* only open private database environments (with the DB_PRIVATE flag, which prevents sharing between processes).
Regards,
Michael. -
Thanks for the answer ...
I Will try DB_PRIVATE.
What should I check for upgrade ?
I'm working on Redhat ES 3..
Here information about all 'glibc' (where I think pthread is implemented)
glibc-common-2.3.2-95.37
glibc-devel-2.3.2-95.37
glibc-2.3.2-95.37
And here the pthread library installed by the package glibc
/lib/i686/libpthread-0.10.so
/lib/i686/libpthread.so.0
/lib/libpthread-0.10.so
/lib/libpthread.so.0
/lib/tls/libpthread-0.60.so
/lib/tls/libpthread.so.0
Which version of glibc/pthread should I need in order to be able to use 'inter process' shared mutex ?
Thanks all -
Unfortunately we can't tell you which RedHat releases contain inter-process POSIX pthread mutex support and which do not. It's a combination of factors, but specifically, it's a combination of the GNU C library and the Linux Operating System release, and we haven't tracked RedHat releases closely enough to know which ones work and which ones don't.
Regards,
Keith Bostic
This discussion has been closed.