[Date Prev][Date Next]
The database format in OpenLDAP 2.3 is not the same as in OpenLDAP 2.2.
You cannot use the 2.3 tools with a 2.2 database (or vice versa).
Just patch your 2.2.28 source as I mentioned in my previous email. There
is no point in using 2.3.7 because even after you rebuild your database
the same problem exists in 2.3.7 slapcat.
> Sorry, it seems wrong again. Can I delete last mail?
> I try to use slapcat of Openldap 2.3.7. After changed some schema in core.schema and copy DB_CONFIG to db directory, slapcat runing. But the output is nothing, except below lines:
> slapcat startup: initiated.
> backend_startup_one: starting "o=kingsoft.com"
> bdb_db_open: o=kingsoft.com
> bdb_db_open: dbenv_open(./db/db1)
> # no data for entry id=01000000
> slapcat shutdown: initiated
> ====> bdb_cache_release_all
> slapcat destroy: freeing system resources.
> If I use -c, the output is more "no data for entry id=XX", but no ldif is printed.
> If no file DB_CONFIG, the output is very like that.
> My Berkerly DB is version 4.2.52. Is anything wrong?
> When I use slapcat ver 2.2.28, output is ok. The entry ID list as below:
> # id=00000001
> # id=00000002
> # id=00000003
> # id=00000004
> # id=00000005
> # id=00000006
> # id=00000007
> # id=00000008
> # id=00000009
> # id=0000000a
> # id=0000000b
> # id=0000000c
> # id=0000000d
> # id=0000000e
> # id=0000000f
> # id=00000010
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/