Every schema in Oracle is related to a corresponding user. Therefore, not every user needs to be migrated.
Oracle's rights management covers indices, tablespaces, materialized views, or ALTER PROCEDURE, for recompiling procedures in Oracle. These are not needed and therefore are not supported in Exasol. Most of the privileges for overlapping objects between Oracle and Exasol, such as tables and views, can be mapped easily.
In Oracle granting the right to select from all the tables within a schema to a user/role, requires grants on every individual table explicitly. This must be done for new tables as well as recreated/replaced tables.
GRANT SELECT ON "C##DB_MIG"."SALES" TO CORE_RO;
GRANT SELECT ON "C##DB_MIG"."STORES" TO CORE_RO;
GRANT SELECT ON "C##DB_MIG"."CUSTOMERS" TO CORE_RO;This can be done on a schema level on Exasol, so that even future tables do not have to be manually included.
To check users, roles, and rights, see the following:
- To get an overview of the privileges granted to users/roles, run the query in Appendix F: Privileges granted to roles/users on Oracle
- To get an overview which roles users have, run the query in Appendix G: Users and their roles on Oracle
- To get an overview of the system privileges of users/roles, run the query in Appendix H: System privileges on Oracle
See the following links for more information on rights management in Exasol and Oracle:
- Rights Management in Exasol
- Row level security in Exasol
- Resource Manager in Exasol
- Rights Management in Oracle
