Oracle tablespaces not visible in Identity Manager after target server changes - Identity Manager

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

This article explains the expected behavior regarding Oracle tablespace exploration in CA Identity Manager. When changes occur on the Oracle target server, these updates may not automatically appear in the Identity Manager environment after a standard exploration process.

Environment

Identity Manager 14.5

Cause

The Oracle connector caches the eTORATablespace attribute of the eTORADirectory object class during the initial endpoint activation. Because these values are not stored in the Provisioning Directory and are not discovered by the standard exploration process, they remain cached until the connector is re-activated.

Resolution

To make new or updated Oracle tablespaces visible in Identity Manager, follow these steps to re-activate the connector:

1. Create the new tablespace on the Oracle server as required.
2. Stop the Connector Server (JCS) service.
3. Restart the Connector Server (JCS) service.
4. Verify that the newly created tablespace is now visible in the LDAP browser (e.g., Jxplorer).

Note: As Oracle tablespaces are not volatile, the connector does not poll the Oracle system for changes during exploration to maintain optimal system performance.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.