Shulou(Shulou.com)05/31 Report--

Editor to share with you what to do when Oracle sysman.mgmt_jobs causes the database to restart automatically. I hope you will get something after reading this article. Let's discuss it together.

Oracle sysman.mgmt_jobs causes the database to restart automatically

Problem phenomenon

Newly taken over the database, check the alarm log and find that the database automatically restarts at 2: 00 a. M. every day

Tue Jun 12 02:00:28 2018

Shutting down instance (immediate)

Stopping background process SMCO

Shutting down instance: further logons disabled

Database environment:

OS:Windws Server 2012

DB:Oracle 11.2.0.1.0

Problem analysis:

No colleague has ever set the task of automatic database restart.

The operating system planned tasks, and no 2-point JOB was found in the database.

Alarm log did not report wrong before automatic restart

Check all the trace logs generated at 2: 00 and find that the daily trace logs are related to OEM, some of which are as follows:

* MODULE NAME: (OEM.CacheModeWaitPool)

-Dumping Sorted Master Trigger List-

Trigger Owner: SYSMAN

Trigger Name: JOB_SUMM_INS_TRIGGER2

Trigger Owner: SYSMAN

Trigger Name: JOB_SUMM_INS_TRIGGER

……

Check the corresponding trigger and no exception is found.

The cause of the problem:

Finally, according to the final analysis, it is likely that when colleagues created an instance using DBCA, the fourth step was to select "configure Enterprise Manager". This configuration will have an option of daily disk backup, and the default time is 2 o'clock every day. It is precisely because of this reason that the database automatically restarts at 2 o'clock every day, because the database is in non-archived mode, and Oracle automatically shuts down the library at 2 o'clock every day to do cold backup through RMAN.

The files that are automatically backed up through OEM are as follows:

SELECT start_time, end_time, operation, status

FROM V$RMAN_STATUS

Order by start_time desc

-most automatic RMAN backups via OEM fail because the flashback area is insufficient

Solution:

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

-- Identify the Backup Job name

Select JOB_OWNER, JOB_NAME

From SYSMAN.MGMT_JOB

Where JOB_NAME like'% BACKUP%'

-- Delete the Job from DB Control Jobs repository

Begin

Sysman.mgmt_jobs.delete_job ('BACKUP_EASORCL_000001',' SYS')

End

The following error is reported when deleting:

-can be solved through the following documentation

How to Force Stop a Stuck Job in Grid Console (document ID 430626.1)

Begin

Sysman.mgmt_job_engine.stop_all_executions_with_id ('F01FFCEEC1DD42EB94B6D12622E25EB4'

TRUE)

End

Begin

Sysman.mgmt_jobs.delete_job ('BACKUP_EASORCL_000001',' SYS')

End

Select JOB_OWNER, JOB_NAME,JOB_ID

From SYSMAN.MGMT_JOB

Where JOB_NAME like'% BACKUP%'

After reading this article, I believe you have a certain understanding of "how to automatically restart the database caused by Oracle sysman.mgmt_jobs". If you want to know more about it, you are welcome to follow the industry information channel. Thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.