There is a great mis conception in DBA's who primarily work on OLTP about Job classes.
Job classes are one of the essentially used components in job definitions which people seldom use and seldom know about.
This blog however is a small and nice one which talks about how to see permissions to execute a job class.
Yes you read that right. You need execute permission for a job class.
Only if you have execute permission to job class, you will be able to add it to your create job.
the way to grant is same
Grant execute 'on job class' to <user>';
to verify you should use dba_tab_privs to know if your user has execute privilege on job class or not.
select * from dba_tab_privs where grantee = '<your user>' and type = 'JOB CLASS';
Example output below (from TOAD)
Job classes are one of the essentially used components in job definitions which people seldom use and seldom know about.
This blog however is a small and nice one which talks about how to see permissions to execute a job class.
Yes you read that right. You need execute permission for a job class.
Only if you have execute permission to job class, you will be able to add it to your create job.
the way to grant is same
Grant execute 'on job class' to <user>';
to verify you should use dba_tab_privs to know if your user has execute privilege on job class or not.
select * from dba_tab_privs where grantee = '<your user>' and type = 'JOB CLASS';
Example output below (from TOAD)
By default permission to execute 'DEFAULT JOB CLASS' is granted to PUBLIC, so you if you do not specify any job class name, default job class will be taken and it will be okay.
No comments:
Write comments