Oracle Server connector: When account deletion is initiated in IM, it drops all dependent objects in the database.

Products

• CA Identity Suite

Issue/Introduction

Our DB teams have informed us that when an Oracle Server Endpoint account is deleted from IM, the DROP command used by the connector includes the CASCADE clause, which in turn removes all objects dependent on the user being dropped.
Is it possible to remove the CASCADE clause from the DROP statement?

Environment

Identity Manager v14.5

Resolution

The out-of-the-box Oracle Server connector uses the CASCADE clause in the DROP statement when initiating account deletion. This behavior is hardcoded into the connector logic and is part of the design. Unfortunately, there is no way to modify this behavior, and no customization is possible at the connector level.

Additional Information

Additionally, the Oracle documentation supports the use of the CASCADE clause with the DROP USER statement. Without it, Oracle will not allow you to drop an object if other objects depend on it.

the CASCADE clause ensures that all dependent objects are removed, preventing orphaned objects or errors due to those dependencies, and it complies with the requirements of the DROP USER statement.

Link to Oracle documentation: http://docs.oracle.com/en/database/oracle/oracle-database/21/sqlrf/DROP-USER.html