Aha, good. The schema files from 389-DS are in /usr/share/dirsrv/data if I
It may not be a good idea to completely replace all schema's because the
server uses some for it's own functionality.
What I did was identity the missing attribute and added it to the most
logical schema file.
You have the risk of having the schema files over written when the server
software is updated, so you should be carefull with that.
Another pitfall I came across by the way was indexes. Make sure that the
indexes are also on your new server for performance.
Glad I could help, good luck!
On Tue, Mar 18, 2014 at 12:28 AM, Dustin Rice <dustin(a)pdx.edu> wrote:
One of my co-workers actually pointed this out moments ago. Seems
some custom schema attributes we have weren't being pushed in the
replication. I already had pulled an ldif of our schema, loaded that,
re-initialized the replica and boom, looks like it works now.
On 03/17/2014 04:08 PM, Vincent Gerris wrote:
yes, I did before.
You need to copy some legacy schema stuff, for the rest it is pretty
Just make an ldif dump, setup the new directory server and try an import.
You will encounter any missing stuff by trial and error.
check the log files and see how you go :).
On Mon, Mar 17, 2014 at 10:34 PM, Dustin Rice <dustin(a)pdx.edu> wrote:
> Hello there, I wanted to see if anyone else out there has gone through a
> migration/upgrade from Sun One Directory 5.2 server to 389 DS?
> I'm currently working on doing just that at my organization and I've been
> running into a few snags. Ideally we'd want to setup a 389 consumer replica
> attached to our Sun One master. Over time we replace the Sun One replicas
> with 389 replicas until eventually all servers are 389 DS.
> Anywho, I do have a 389 DS consumer replica that appears to be
> replicating from our Sun One master, however I'm seeing a number of LDAP
> error 53 (server was unwilling) errors. When I upped the log level it looks
> like the master is trying to do an ldapadd when it should be doing an
> ldapmodify. So that's where I'm slightly stuck now, if anyone out there has
> any ideas.
> Dustin Rice
> UNIX System Administrator - CIS
> Portland State University
> 389 users mailing list
389 users mailing
UNIX System Administrator - CIS
Portland State University
389 users mailing list