Boa tarde a todos !
Estou com o seguinte problema , aqui na minha empresa estou selecionando determinadas permissões para os usuarios pois estava uma bagunça , portanto preciso saber como dar permissão para os usuarios verificarem o plano de execução para pegarem dados sobre o custo dos selects...
Atualmente uso as seguintes permissões:
GRANT ALTER DATABASE TO USUARIO;
GRANT DEBUG ANY PROCEDURE TO USUARIO;
GRANT CREATE ANY INDEX TO USUARIO;
GRANT ALTER ANY INDEX TO USUARIO;
GRANT DROP ANY INDEX TO USUARIO;
GRANT CREATE ANY JOB TO USUARIO;
GRANT CREATE MATERIALIZED VIEW TO USUARIO;
GRANT DROP ANY MATERIALIZED VIEW TO USUARIO;
GRANT CREATE PROCEDURE TO USUARIO;
GRANT ALTER ANY PROCEDURE TO USUARIO;
GRANT DROP ANY PROCEDURE TO USUARIO;
GRANT EXECUTE ANY PROCEDURE TO USUARIO;
GRANT CREATE SEQUENCE TO USUARIO;
GRANT ALTER ANY SEQUENCE TO USUARIO;
GRANT DROP ANY SEQUENCE TO USUARIO;
GRANT SELECT ANY SEQUENCE TO USUARIO;
GRANT CREATE SYNONYM TO USUARIO;
GRANT CREATE TABLE TO USUARIO;
GRANT ALTER ANY TABLE TO USUARIO;
GRANT DELETE ANY TABLE TO USUARIO;
GRANT DROP ANY TABLE TO USUARIO;
GRANT INSERT ANY TABLE TO USUARIO;
GRANT SELECT ANY TABLE TO USUARIO;
GRANT UPDATE ANY TABLE TO USUARIO;
GRANT CREATE TRIGGER TO USUARIO;
GRANT ALTER ANY TRIGGER TO USUARIO;
GRANT DROP ANY TRIGGER TO USUARIO;
GRANT CREATE TYPE TO USUARIO;
GRANT ALTER ANY TYPE TO USUARIO;
GRANT DROP ANY TYPE TO USUARIO;
GRANT EXECUTE ANY TYPE TO USUARIO;
GRANT CREATE VIEW TO USUARIO;
GRANT DROP ANY VIEW TO USUARIO;
GRANT CREATE SESSION TO USUARIO;
GRANT UNLIMITED TABLESPACE TO USUARIO;
GRANT SELECT ON V_$SESSION TO USUARIO;
Obrigado;
Permissão plano de execução
-
- Moderador
- Mensagens: 1177
- Registrado em: Qui, 15 Out 2009 10:28 am
- Localização: Recife
GRANT ALL ON sys.plan_table TO public;
The visual explain plan feature is supported for Oracle 9i and later versions. Unlike many other products, DB Solo does not require you to have a PLAN_TABLE in place for this feature. Instead, the V$SQL_PLAN table is used which is more accurate since it contains the actual plan, not a predicted one like the PLAN_TABLE approach does.
For a user to be able to read the V$SQL_PLAN and V$SESSION tables, she must be granted the SELECT_CATALOG_ROLE role or the SELECT ANY DICTIONARY system privilege. The difference between these two is that SELECT_CATALOG_ROLE is a role that contains several privileges whereas SELECT ANY DICTIONARY is a single system privilege. You can check to see if you have the necessary privileges by issuing the 'SELECT COUNT(*) FROM V$SQL_PLAN' SQL statement in the query window. If you get the ORA-00942 (table or view does not exist) error, you need to ask your DBA to grant the necessary privileges.
The visual explain plan feature is supported for Oracle 9i and later versions. Unlike many other products, DB Solo does not require you to have a PLAN_TABLE in place for this feature. Instead, the V$SQL_PLAN table is used which is more accurate since it contains the actual plan, not a predicted one like the PLAN_TABLE approach does.
For a user to be able to read the V$SQL_PLAN and V$SESSION tables, she must be granted the SELECT_CATALOG_ROLE role or the SELECT ANY DICTIONARY system privilege. The difference between these two is that SELECT_CATALOG_ROLE is a role that contains several privileges whereas SELECT ANY DICTIONARY is a single system privilege. You can check to see if you have the necessary privileges by issuing the 'SELECT COUNT(*) FROM V$SQL_PLAN' SQL statement in the query window. If you get the ORA-00942 (table or view does not exist) error, you need to ask your DBA to grant the necessary privileges.
-
- Informação
-
Quem está online
Usuários navegando neste fórum: Nenhum usuário registrado e 1 visitante