OUD12c - Adding RDBMS Table Using Different DB Schema Results In The Error "LDAP: error code 53..."
(Doc ID 2469421.1)
Last updated on JUNE 01, 2023
Applies to:
Oracle Unified Directory - Version 12.2.1.3.180626 and laterInformation in this document applies to any platform.
Symptoms
RDBMS Work Flow Element cannot map attribute to table from different DB schema.
Perform dsconfig to configure the RDBMS table attribute mapping,
>>>> Configure the properties of the RDBMS Table
Property Value(s)
-----------------------------------------------------------
1) cascade-delete-on-relation false
2) db-table-name NEW_SCHEMA.SALESUSERS_tbl <--- here
3) join-rule No join rules would be defined
4) join-type No Join Type will be configured
5) outer-join-required true
6) primary-key-field USERNAME
?) help
f) finish - apply any changes to the RDBMS Table
c) cancel
q) quit
Enter choice [f]:
The Attribute Mapping could not be created because of the following reason:
* [LDAP: error code 53 - The Directory Server is unwilling to add
configuration entry cn=USERNAME,cn=Attribute
Mappings,cn=salesdb2,cn=Objectclass
Mappings,cn=salesdb2_wfe,cn=Workflow elements,cn=config because one of
the add listeners registered with the parent entry cn=Attribute
Mappings,cn=salesdb2,cn=Objectclass
Mappings,cn=salesdb2_wfe,cn=Workflow elements,cn=config rejected this
change with the message: The RDBMS column 'username' is missing from
RDBMS table 'new_schema.salesusers_tbl']
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |