![]() For example, we create a schema owner called SCHEMA_OWNER using the following command.Ĭreate user schema_owner identified by secret_password Instead they access it to do schema changes via a proxy connection, allowing you to audit which users performed which tasks. It's a common practice to restrict direct access to a schema owner, preventing people accessing it using shared credentials. It's not about how to set up users for application connections. The rest of this article is focused on how you control access to the schema owner, when people need to connect to perform maintenance. This is described in the following articles. Applications should log in using a separate user with privileges on the schema objects. You should only be logged in as the schema owner because you are making DDL changes to the schema objects. Schema Only Accounts in Oracle Database 18c OnwardĪpplications should never have access to the schema owner, either directly or via a proxy connection.Schema only accounts don't allow direct connections, so administration of their objects is done via a DBA user or a proxy user. Home » Articles » 18c » Here Schema Only Accounts in Oracle Database 18c
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |