Need to change las_name field on the Resource Object so it allows the LDAP to import the LAST_NAME field with more then 32 characters..
The db length of the field is among other things for allowing double byte characters.
Increasing the length of OOTB fields is not supported nor recommended as you must be aware of.
In addition of causing problems with the updates (which are now more or less quarterly) the last name field may be referenced in various places in the application.
Do you know if the LDAP import will handle more than the standard length?
Interestingly, a Role Name can have more than 32 characters, a Resource can't. The data is stored in the same table (srm_resources), and same attribute.
It may be a limitation on cmn_sec_users which also stores last_name for resources.
Either way, you can't change the length as it is an OOTB attribute. You may want to consider raising a CA Support ticket to see if there is a solution.
The last_name field in the SRM_RESOURCES Table is defined as VARCHAR2(96) in Oracle database.
Double byte character like Japanese will need 3 bytes length in UTF8 encoding.
32 Japanese characters will use 96 bytes (3 bytes * 32 characters).
It seems to check if last_name field is within 32 characters. (It does not mean 32 bytes, it means 32 characters)
PPM support double byte character, so such field in table should be defined as triple length.
I added additional information.
You will be able to see below comment under Maximum Size field for attribute properties.
PPM allows maximum size 2000 for 2 byte Unicode character. (Single byte character like English)
This field is defined as VARCHAR2(4000) in table.
So, maximum size for 3 byte Unicode character is not 2000. It is 4000/3 = 1333.
Retrieving data ...