When a job is stopped, only the current transaction is rolled back - Oracle DBA
Oracle (MCQ) questions and answers
Q. When a job is stopped, only the current transaction is rolled back. This can cause data inconsistency.
- Published on 27 Jul 15
Oracle DBA (
Oracle Replication (
Oracle Architecture (
Oracle Transaction (
Administering and Managing an Oracle Database (
Managing Oracle Database Processes (
Oracle Control Files (
Oracle Redo Log (
Oracle Tablespaces (
Oracle Datafiles and Tempfiles (
Oracle Managed Files (
Oracle Schema (
Oracle Tables (
Oracle Indexes and Partitioned Tables (
Oracle Clusters (
Oracle Views, Sequences, and Synonyms (
Oracle Distributed Database concepts (
-Posted on 26 Aug 15
-You stop one or more running jobs using the STOP_JOB procedure or Enterprise Manager.
-STOP_JOB accepts a comma-delimited list of jobs and job classes.
-If a job class is supplied, all running jobs in the job class are stopped.
-By default, the Scheduler tries to gracefully stop a job using an interrupt mechanism.
-This method gives control back to the slave process, which can collect statistics of the job run.
-If the force option is set to TRUE, the job is abruptly terminated and certain runtime statistics might not be available for the job run.
-Stopping a job that is running a chain automatically stops all running steps (by calling STOP_JOB with the force option set to TRUE on each step).
Post your comment / Share knowledge
Enter the code shown above:
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)