Support for Separate Oracle Schema and Application Accounts in Symantec DLP
Article ID: 160701
Updated On:
Products
Issue/Introduction
Many customers have corporate security policies that call for a separation of the database account that owns the application schema, and the account that the application uses to access the schema.
Resolution
While this is may be of concern, there is no separation of the Oracle schema owner and the application access account.
Creating a separate application account with access and synonyms will cause the system to become unsupportable due to the fact that the product installer and database migrator are designed with the schema and application user being one in the same.
If the migrator executes against a user that is not the schema it will cause the migrator to fail.
There are many other potential unknown possible problems as the product was not designed with that in mind.
If you find this is an important function for your environment please reach out through your support channel and ask to be added to feature request# PM-2632
Feedback
