connect system set serveroutput on EXECUTE DBMS_SCHEDULER.DISABLE(name=>'SCOTT.UPDATE_COMMISIONS');You cannot login as SYS to perform this operation, you need to be logged in as another user with the required preivileges (such as SYSTEM, in this case). Documented here
Minimalistic Oracle contains a collection of practical examples from my encounters with Oracle technologies. When relevant, I also write about other technologies, like Linux or PostgreSQL. Many of the posts starts with "how to" since they derive directly from my own personal experience. My goal is to provide simple examples, so that they can be easily adapted to other situations.
Showing posts with label Jobs. Show all posts
Showing posts with label Jobs. Show all posts
Friday, January 8, 2021
How to disable a scheduler job in a another schema
Use the syntax
Tuesday, February 12, 2019
How to remove a job from the job queue
Today I saw the following error message in the alert log of my database:
2019-02-12T13:27:30.506714+01:00 Errors in file /u01/oracle/diag/rdbms/proddb01/proddb01/trace/proddb01_j000_20661.trc: ORA-12012: error on auto execute of job 98 ORA-30967: operation directly on the Path Table is disallowedThis error was connected to a procedure I had made earlier, in this post.
In short, the procedure creates a job using dbms_jobs, and executes it thereafter. Because an error occured during job execution, the job appeared to be jamming connections to the database. The job needed to be dropped immediately.
To remove the job, use either the dbms_job.remove procedure, like this:
sqlplus username/password begin sys.dbms_job(98); commit; end; /
If you do not have the password for schema owning the job, Use the undocumented procedure sys.dbms_ijob, like this:
sqlplus / as sysdba begin sys.dbms_ijob(98); commit; end; /
Subscribe to:
Posts (Atom)