Resolve error ”Invalid entry <entry>: com.rli.slapd.storage.store.HDAPCodec$HDAPCodecException: Invalid number format for <attribute>: For input string: "0F1414" by changing oid values (datatypes) in ldapschema.ldif file.

For the below error in cache initialization logs:

Invalid entry <entry>: com.rli.slapd.storage.store.HDAPCodec$HDAPCodecException: Invalid number format for <attribute>: For input string: "0F1414"

 

For example:

The vds_server/logs/scheduler/task.Cache_initialization.log show many of these warnings:

2023-01-12T13:52:04,571 WARN  com.rli.slapd.storage.utils.g$a$1:786 - Invalid entry CN=U0F1414,OU=Users,OU=Global,OU=HCSC,DC=adhcsctst,DC=net: com.rli.slapd.storage.store.HDAPCodec$HDAPCodecException: Invalid number format for uidnumber: For input string: "0F1414"

For the attribute "uidnumber", for which the values given are "0F1414", "C0427", "0R0632", etc.

 

ldapschema_xx.ldif

attributetypes: ( 1.3.6.1.4.1.40747.92.164701397.145794773.82 NAME 'uidNumber' DESC 'Standard Attribute' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )

in
objectclasses: ( 1.3.6.1.4.1.40747.92.141877704.168845900.173107669 NAME 'HCSCLDAPUser' 
objectclasses: ( 1.3.6.1.4.1.40747.92.154462160.141615320.177449679 NAME 'posixAccount' 
objectclasses: ( 1.3.6.1.4.1.40747.92.141877704.173107669 NAME 'HCSCUser'

The issue here is that when the refresh happens, VDS picks up the default LDAP schema for the attribute, in this case "uidnumber", which is defined as an Integer in ldapschema_50.ldif file.
 
While the input provided for that attribute, in this case, is a varchar or Directory String. (0F1414", "C0427", "0R0632", etc.)
 
As a solution for this: You can remove this attribute from the ldapschema.ldif file or you can just change its data type as follows.
 
The steps are:

  1. Open the ldapschema_xx.ldif file in a Notepad.
  2. Edit the below line and replace 1.3.6.1.4.1.1466.115.121.1.27 with 1.3.6.1.4.1.1466.115.121.1.15
attributetypes: ( 1.3.6.1.4.1.40747.92.164701397.145794773.82 NAME 'uidNumber' DESC 'Standard Attribute' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )

|
V

attributetypes: ( 1.3.6.1.4.1.40747.92.164701397.145794773.82 NAME 'uidNumber' DESC 'Standard Attribute' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

3. Save the file and restart all the servers.

4. After restart, a reinitialization or rebuild index is needed for the schema change to take effect at the HDAP layer.

 


 
 

Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

See more