About Database Users
Schema User (Oracle and Oracle Autonomous Database only)
Default: ADMUSER
Description: The administrative user owns most database objects within the schema including tables, indexes and constraints, procedures, triggers, and functions, and is primarily used during database creation and upgrades.
Privileged User
Default: PRIVUSER
Description: The following is true for the privileged user:
- Owns views to most of the schema user tables that filter out logically deleted data.
- Has SELECT, INSERT, UPDATE, and DELETE privileges on all of the tables owned by the schema user.
- Has EXECUTE privileges on all schema procedures.
- Is used to facilitate communication between P6 EPPM and P6 Professional.
- Owns the synonyms for objects that do not have a view, which means that references to tables that are owned by the schema owner do not have to be fully qualified (Oracle database only).
Public User
Default: PUBUSER
Description: The public user has few permissions in the P6 EPPM database. It has SELECT privileges on the PUBUSER table, which is used to connect a P6 EPPM to the database.
Background Job User (Oracle database only)
Default: BGJOBUSER
Description: The background job user initiates and runs P6 EPPM background jobs.
Reporting User
Default: PXRPTUSER
Description: The reporting user owns views to the P6 EPPM extended schema for enterprise reporting.
Read-Only Administrative User (Oracle database only)
Default: ROADMUSER
Description: The read-only user has read-only access to the tables owned by the schema user. The read-only user has the same views as reporting user.
Last Published Thursday, October 3, 2024