You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Sathish Kumar <sa...@gmail.com> on 2019/06/16 12:21:10 UTC
ApacheDS Migration
Hi Team,
We are running an ApacheDS 1.5.4 and would like to migrate to ApacheDS
2.0.0.AM25 on our Production Environment.
If I export .ldif and import .ldif in the new server will it work correctly?
We have around 25k entries on the existing LDAP server. Is it good to use
JDBM partition or Mavibot Partition for large datasets. I think existing
server Partition data is on JDBM.
Please let me know on how to migrate it to the new LDAP server.
Thanks & Regards
Sathish Kumar.V
Re: ApacheDS Migration
Posted by Sathish Kumar <sa...@gmail.com>.
Hi,
I have replaced example.com to abc.com in config.ldif for testing and
started the LDAP server and getting below error.
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsDomainName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsDomainName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class: apacheDnsTtl
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsDomainName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsAbstractRecord
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsServicePriority
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsServiceWeight
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsServicePort
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsDomainName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsAbstractRecord
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsIpAddress
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsAbstractRecord
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsDomainName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsIpAddress
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsAbstractRecord
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsSoaMName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsSoaRName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsSoaMinimum
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsAbstractRecord
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsClass
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsSoaSerial
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsSoaRefresh
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsSoaRetry
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsSoaExpire
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsDomainName
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsAbstractRecord
[12:24:25] ERROR [org.apache.directory.api.ldap.model.entry.Value] -
ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to
handle NameAndOptionalUID normalization with objects of class:
apacheDnsDomainName
While Importing LDIF, I am getting below warning message but it looks like
the data is imported.
[12:46:40] WARN [org.apache.directory.api.ldap.model.entry.Value] -
MSG_13202_AT_IS_NULL ()
[12:46:40] WARN [org.apache.directory.api.ldap.model.entry.Value] -
MSG_13202_AT_IS_NULL ()
[12:46:40] WARN [org.apache.directory.api.ldap.model.entry.Value] -
MSG_13202_AT_IS_NULL ()
[12:46:40] WARN [org.apache.directory.api.ldap.model.entry.Value] -
MSG_13202_AT_IS_NULL ()
Please let me know, how to proceed further.
Thanks & Regards
Sathish Kumar.V
On Sun, Jun 16, 2019 at 10:09 PM Emmanuel Lécharny <el...@gmail.com>
wrote:
>
> On 16/06/2019 14:21, Sathish Kumar wrote:
> > Hi Team,
> >
> > We are running an ApacheDS 1.5.4 and would like to migrate to ApacheDS
> > 2.0.0.AM25 on our Production Environment.
> >
> > If I export .ldif and import .ldif in the new server will it work
> correctly?
>
>
> It should, as soon as you don't export the operational attributes.
>
>
> You will have to configure the server though (you can do that with
> Studio) because we have switched from a Spring based config (aka XML) to
> a LDIF based one.
>
> >
> > We have around 25k entries on the existing LDAP server. Is it good to use
> > JDBM partition or Mavibot Partition for large datasets. I think existing
> > server Partition data is on JDBM.
>
> Mavibot is not ready yet. JDBM should work, but I would tell you to wait
> befor going to production, because the coming version is going to have
> transaction which will protect your data against DB corruption
> (something that plagued the server since the beginning and that is
> hopefully fixed in 2.0.0.AM26). We currently are working on closing as
> much JIRA as possible in order to cut a release in the coming weeks.
>
> You can still start a migration as a test with the current version, so
> that the process will be ready for the new release.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
> For additional commands, e-mail: users-help@directory.apache.org
>
>
Re: ApacheDS Migration
Posted by Emmanuel Lécharny <el...@gmail.com>.
On 16/06/2019 14:21, Sathish Kumar wrote:
> Hi Team,
>
> We are running an ApacheDS 1.5.4 and would like to migrate to ApacheDS
> 2.0.0.AM25 on our Production Environment.
>
> If I export .ldif and import .ldif in the new server will it work correctly?
It should, as soon as you don't export the operational attributes.
You will have to configure the server though (you can do that with
Studio) because we have switched from a Spring based config (aka XML) to
a LDIF based one.
>
> We have around 25k entries on the existing LDAP server. Is it good to use
> JDBM partition or Mavibot Partition for large datasets. I think existing
> server Partition data is on JDBM.
Mavibot is not ready yet. JDBM should work, but I would tell you to wait
befor going to production, because the coming version is going to have
transaction which will protect your data against DB corruption
(something that plagued the server since the beginning and that is
hopefully fixed in 2.0.0.AM26). We currently are working on closing as
much JIRA as possible in order to cut a release in the coming weeks.
You can still start a migration as a test with the current version, so
that the process will be ready for the new release.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
For additional commands, e-mail: users-help@directory.apache.org