Page Comparison

To enable the database user management functionality, set Sys Item 239 (Database Users screen visibility in User Administration Center) to 1. You can also allow different access based on the type of environment (DEV, TEST, PROD) via Sys Item 201. Depending on the type of environment, the system will display code values of one of these three categories as allowed roles: DB_USER_DEV, DB_USER_QA, and DB_USER_PROD.

If you have the appropriate permissions, In Center Roles, you can use the User Administration Center roles to specifically grant users access to any or all of the following: View DB Users, Create DB Users, Edit DB Users, Lock/Unlock DB Users, and Delete DB Users. For example, UA Admin role has all permissions.

About the Proxy Feature

For DEV environments only (Sys Item 201=DEV), you can also use the proxy feature (Add write permissions and Remove write permissions) to connect to the database either as an ESTAR or PACE_MASTERDBO user. To connect with this type of access, users have to be granted appropriate permissions in User Administration. The Add Write Permissions command should be applied in the DB Users window. The Remove Write Permissions command should be used to remove this access. 

New DB Users are now assigned to predefined DB Roles which are selected according to Sys Item 201 which specifies whether it is a PROD, DEV, or TEST system. Additionally, the EA_PROFILE profile is now applied when a new DB user is created.

DB Users Feature - Audit trail - BUILT ONLY IN SMC??

Full audit history of any Manage DB User activity initiated from within User Admin UI is shown in 'DB Users Administration Audit' report
Location: System management Center > Diagnostics > Queries > Query name - UA Security - DB Users Administration Audit 

You can manage Oracle database users as follows:

Image Removed

back to top

...