My Oracle Support Banner

OUD 11g: Proxy RDBMS - Using a Table From Other Schema Than Schema Used For Connection (Doc ID 2225294.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Unified Directory - Version 11.1.2.3.0 and later
Information in this document applies to any platform.

Goal

On : 11.1.2.3.160719 version, Proxy & Load-Balancing

OUD Proxy RDBMS  - How to use a table from different schema than schema used for RDBMS connection

It is requested to configure the OUD proxy RDBMS to access a specific table from different schema than schema used for RDBMS connection.
DB connecting user/schema: OVD_LDAP
Table to be used in RDBMS: FTPRO.KATEGORIJA_KORISNIKA

Using full reference FTPRO.KATEGORIJA_KORISNIKA is not working. Always showing missing column/field.

[LDAP: error code 53 - The Directory Server is unwilling to add
configuration entry cn=XXXXXX,cn=Attribute
Mappings,...,cn=Workflow elements,cn=config because one of the
add listeners registered with the parent entry cn=Attribute
Mappings,...,cn=Workflow elements,cn=config rejected this
change with the message: The RDBMS column 'kategorija_id' is missing
from RDBMS table 'ftpro.kategorija_korisnika']


Reference:
Creating the Components to Communicate with the RDBMS

 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.