36.2.User Permission | ||||
36.2.1. | To connect to the database a user must be granted the permission to create a session, which is the CREATE SESSION system privilege. | |||
36.2.2. | CREATE USER userName IDENTIFIED BY password and grant permission | |||
36.2.3. | Create user and grant permission | |||
36.2.4. | Grant all possible permissions | |||
36.2.5. | REVOKE CREATE TABLE, CREATE CLUSTER, CREATE SYNONYM, CREATE VIEW, CREATE SEQUENCE, CREATE DATABASE LINK FROM CONNECT | |||
36.2.6. | Grant CREATE SYNONYM, CREATE VIEW, CREATE DATABASE LINK, CREATE PUBLIC SYNONYM, DROP PUBLIC SYNONYM | |||
36.2.7. | Grant connect and resource permission to a user | |||
36.2.8. | Grant connect permission to a user | |||
36.2.9. | Grant with admin option | |||
36.2.10. | Grant connect to permission to all name in a table | |||
36.2.11. | grant select on tableName to userName | |||
36.2.12. | grant administer database trigger to userName | |||
36.2.13. | grant execute on dbms_rls to userName | |||
36.2.14. | grant create any context to userName | |||
36.2.15. | Revoke Permissions | |||
36.2.16. | Revoke Permissions with Cascade | |||
36.2.17. | Get user name from all_users |
GRANT CREATE ANY TRIGGER TO &&AdminLogin;
, which is required for the triggers used by transactional replication. If you will use only snapshot replication, remove this line from the script.