相关文章推荐
捣蛋的皮带  ·  【Oracle错误处理】java ...·  2 天前    · 
狂野的荒野  ·  C# Stopwatch详解-CSDN博客·  11 月前    · 
强健的太阳  ·  Elastic Search ...·  1 年前    · 
爱喝酒的抽屉  ·  Qt | ...·  1 年前    · 
How to stop Database Autobackup Every Day At 02:00 Am which was configured during Database creation using DBCA ? ( ID 1992075.1)

-- Identify the Backup Job name

select JOB_OWNER, JOB_NAME

from SYSMAN.MGMT_JOB

where JOB_NAME like '%BACKUP%';

How to stop Database Autobackup Every Day At 02:00 Am which was configured during Database creation using DBCA ? ( ID 1992075.1)

In this Document

Enterprise Manager for Oracle Database - Version 10.2.0.1 to 11.2.0.4 [Release 10.2 to 11.2] Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.4 [Release 10.2 to 11.2] Information in this document applies to any platform.

In step 4, Management options screen, you have the option to choose "Configure the database with Enterprise Manager". If you choose this , then you have the option to use Grid control or Database control.

If you choose "Use Database Control for Database Management" ,then there is an option to setup automatic database daily backups. Hence the Database might automatically shutdown daily for backup. Is there a way to disable the automatic database shutdown for backup ? If the DB console is down and unable to access, We can delete the Backup job from the DBconsole repository.

-- Identify the Backup Job name

select JOB_OWNER, JOB_NAME from SYSMAN.MGMT_JOB where JOB_NAME like '%BACKUP%';

JOB_OWNER             JOB_NAME ---------------- -------------------------------------------------------- BACKUP_QASEPOMS.BWI40G.VZBI.CAAS_000001

-- Delete the Job from DB Control Jobs repository

begin sysman.mgmt_jobs.delete_job('BACKUP_QASEPOMS.BWI40G.VZBI.CAAS_000001','SYS'); Manager Base Platform - Version 10.2.0.1 to 11.1.0.1 [Release 10.2 to 11.1] Information in this document applies to any platform.

Using 10.2 Grid Console. A scheduled Job Run is stuck in the 'Running' / 'Status Pending' status for many days without any progress. This may occur if the target or the agent on that target machine is down and cannot be reached.

-  Trying to Suspend / Stop this job returns :

All executions of the job were stopped successfully. Currently running steps will not be stopped. <Job Name is displayed here>

-  After this, the particular Job Execution remains in 'Stop Pending' status. Trying to Stop this job execution returns :

The specified job, job run or execution is still active. It must finish running, or be stopped before it can be deleted. Filter on status 'Active' to see active executions.

-  Choosing the Job and clicking on 'Retry' returns :

"The specified job can not be re-submitted. It either has active executions, or it has no failed executions."

This document provides the steps to forcefully stop the executions of this job and delete it.

If the stuck job is seen in the above output, please log an SR with Oracle Support to obtain more information regarding these tests. If the job is not shown in the above output, then follow the remaining steps in this document. It is important to exercise caution when running any manual commands against the repository database, if necessary a valid backup can be taken. + Connect to database as SYSMAN and run:

select job_id, job_name, job_owner from mgmt_job where job_name like '%<name of job as seen in the console>%';

Make note of the JOB_ID returned by the above query.

+  Stop all the executions and the current runs of the job :

exec mgmt_diag.stopcurrentjobexec('<job ID as returned by above query>');

exec mgmt_job_engine.stop_all_executions_with_id('<job ID as returned by above query>');

Check the output select EXECUTION_ID, status from MGMT_JOB_EXEC_SUMMARY where job_id ='<job ID returned by the 1st query>' ;

If the execution has been stopped successfully, the status should have a value : 18 i.e SKIPPED.

- You can also try stopping the executions forcefully using :

exec mgmt_job_engine.stop_all_executions_with_id('<job ID as returned by above query>',TRUE);

-  From EMDIAG, you can use :

exec mgmt_diag.stopjob('<job ID as returned by above query>');

- You can also stop the job using Emcli : Setup emcli as doumented in Installation and Setup of emcli From the command line run :

emcli stop_job -name=<specify the name of the job>

-  If EM level auditing has been enabled, then you may face ORA-01422 from the above commands. To resolve these errors, refer to :

Note.401479.1 : Problem Setting Up the Auditing System for Enterprise Manager prevents job deletion

+  Check in the Grid console, that the Job Run / Execution is no longer in Running / Stop Pending status respectively. The Job Execution should have a 'Skipped' status.

+  Choose this job and click on the 'Delete' button in the Grid console. The Job deletion should go fine now. If you still face any issue, login to the repository as the SYSMAN user and run :

SQL> exec mgmt_job_engine.delete_job('<job ID as returned by above query>');

+  If the job still cannot be deleted :

-  Shutdown the OMS and take a valid backup of the repository database. This is mandatory as the next step will perform manual operations against the repository and it is essential to have a backup, to revert back to, incase of any problems.

-  In the repository database, login as the sysman user and execute :

SQL> UPDATE mgmt_job_exec_summary SET status = 8, end_time = (sysdate - 1) WHERE job_id ='<job ID as returned by above query>';

Then 1 row should be updated. If no errors do a commit, else rollback. -  Once this update is successful, try to delete the jobs from the Console and it should go through without any errors.

If using 10.2.0.5 Grid Control, there is an option to 'Force Stop' the job.

Note 838857.1 : New Features related to Jobs in 10.2.0.5 Enterprise Manager Grid Control Also refer to : Note 413005.1 : Problem: Unable To Delete Job From Grid Control ORA-20414 Note 605071.1 : Grid Control Job Is stuck in 'Scheduled' status and unable to Remove / Stop the Job Note 401479.1 : Problem: Setting Up the Auditing System for Enterprise Manager prevents job deletion

NOTE:401479.1 Problem: Setting Up the Auditing System for Enterprise Manager prevents job deletion
NOTE:413005.1 Problem: Unable To Delete Job From Grid Control ORA-20414 NOTE:421053.1 EMDIAG Troubleshooting Kits Master Index NOTE:605071.1 Grid Control Job Is stuck in 'Scheduled' status and unable to Remove / Stop the

广播电视节目制作经营许可证(京) 字第1234号 中国互联网协会会员