Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to handle 11g RAC Node second Mmon process exception

2025-01-17 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

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

This article mainly explains "how to deal with 11g RAC node second Mmon process exception". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to deal with 11g RAC node second Mmon process exception".

Early in the morning, it was found that the DBtime monitoring threshold of the core system had been shifting at a certain point, which felt something was wrong.

Because our script relies on the SNIP that dba_hist_snapshot tries to do. Then the AWR report is generated to see if there are any anomalies in its SNAP_ID.

21220 19 Sep 2018 09:00 1 21221 19 Sep 2018 10:00 1 21222 19 Sep 2018 11:00 1 21223 19 Sep 2018 12:00 1 21224 19 Sep 2018 13:00 1 21225 19 Sep 2018 14:00 1 21226 19 Sep 2018 15:00 1 21227 19 Sep 2018 16:00 1 21228 19 Sep 2018 17:00 1 21229 19 Sep 2018 18:00 1 21230 19 Sep 2018 19:00 1

Specify the Begin and End Snapshot Ids

Enter value for begin_snap: there was a CBC-related wait on the system last night, but it quickly recovered. What is this, is the database file full, or is the mm process down? Try to generate a SNAP_ID manually. It's okay to find out. [oracle@bapdb2 trace] $sqlplus / as sysdbaSQL*Plus: Release 11.2.0.4.0 Production on Thu Sep 20 10:40:33 2018Copyright (c) 1982, 2013, Oracle. All rights reserved.Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.4.0-64bit ProductionWith the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,Data Mining and Real Application Testing options10:40:33 SYS@bapdb2 (bapdb2) > set line 300 pages 100010 64bit ProductionWith the Partitioning 40 SYS@bapdb2 (bapdb2) > BEGIN10:40:37 2 DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT (); 10:40:37 3 END;10:40:37 4 / PL/SQL procedure successfully completed. There are also plenty of archive directories in the system, and there is no case in which an archive exception leads to a process exception. 10:43:57 SYS@b2 (db2) > select group_number,block_size,name,allocation_unit_size,state,type,total_mb,free_mb,offline_disks from v$asm_diskgroup GROUP_NUMBER BLOCK_SIZE NAME ALLOCATION_UNIT_SIZE STATE TYPE TOTAL_MB FREE_MB OFFLINE_DISKS-- -1 4096 SAS_ARCH 1048576 CONNECTED EXTERN 1024000 617921 0 Node 1 View process: [oracle@db1 ~] $ps-ef | grep mmgrid 6634 10 2017? 00:33:47 asm_mman_+ASM1grid 6648 10 2017? 01:52:06 asm_mmon_+ASM1grid 6650 10 2017? 2-00:53:46 asm_mmnl_+ASM1oracle 8610 10 2017? 00:33:56 ora_mman_db1oracle 8650 10 2017? 3-11:28:35 ora_mmon_db1oracle 8655 11 2017? 4-07:20:56 ora_mmnl_db1 Node 2 View Progress: [oracle@bapdb2 ~] $ps-ef | grep mmoracle 54354 53982 0 11:09 pts/1 00:00:00 grep mmgrid 105256 10 2017? 00:23:52 asm_mman_+ASM2grid 105295 10? 01:15:06 asm_mmon_+ASM2grid 105312 10? 1-03:49:26 asm_mmnl_+ASM2oracle 106889 10 2017? 00:28:00 ora_mman_db2oracle 106927 10 2017-3-04:47:42 ora_mmnl_db2 found the MMON process DOWN of Node 2. Search from the ALERT log: Tue Sep 19 03:49:00 2017MMON started with pid=36, OS id=8650Tue Sep 19 03:49:00 2017MMNL started with pid=37, OS id=8655 Tue Sep 19 04:01:47 2017MMON started with pid=36, OS id=106923Tue Sep 19 04:01:47 2017MMNL started with pid=37, OS id=106927 this process with an id of 106923 is indeed an exception. In similar cases, you can start MMON-related processes directly in Node 2; SQL > alter system enable restricted session; System altered. SQL > alter system disable restricted session; System altered. At the same time, Alert log also gives feedback. Thu Sep 20 11:10:28 2018Stopping background process MMNLStarting background process MMONStarting background process MMNLThu Sep 20 11:10:29 2018MMON started with pid=37, OS id=55936 Thu Sep 20 11:10:29 2018MMNL started with pid=236, OS id=55938 ALTER SYSTEM enable restricted session;minact-scn: Inst 2 isa slave inc#:16 mmon proc-id:55936 status:0x2minact-scn status: grec-scn:0x0026.4dcf0d36 gmin-scn:0x0026.4dcf0d36 gcalc-scn:0x0026.4dcf1208Thu Sep 20 11:11:05 2018ALTER SYSTEM disable restricted session Thu Sep 20 11:13:25 2018LGWR: Standby redo logfile selected for thread 2 sequence 154126 for destination LOG_ARCHIVE_DEST_3 check again that the process starts normally 11:10:29 SYS@db2 (xxxdb2) >! ps-ef | grep mmoracle 55936 10 11:10? 00:00:00 ora_mmon_db2oracle 55938 10 11:10? 00:00:00 ora_mmnl_db2grid 105256 10 2017? 00:23 52 asm_mman_+ASM2grid 105295 10 2017? 01:15:06 asm_mmon_+ASM2grid 105312 10 2017? 1-03:49:26 asm_mmnl_+ASM2oracle 106889 10 2017? 00:28:00 ora_mman_db2 traced the trc file of the MMON process It is found that there is this one at the bottom: * 2018-09-19 18:46:41.432minact-scn slave-status: grec-scn:0x0026.4db016c0 gmin-scn:0x0026.4db016c0 gcalc-scn:0x0026.4db0273cminact-scn slave-status: grec-scn:0x0026.4dbdde59 gmin-scn:0x0026.4dbdde59 gcalc-scn:0x0026.4dbdf492*** 2018-09-19 18:56:44.302minact-scn slave-status: grec-scn:0x0026.4dca45db gmin-scn:0x0026.4dca45db gcalc-scn:0x0026. 4dca5990 19:01:37.026error * 2018-09-19 detected in background processOPIRIP 28: Uncaught error 447. Error stack:ORA-00447: fatal error in background processORA-00028: your session has been killed Thank you for reading, the above is the content of "how to deal with 11g RAC Node 2Mmon process exception". After the study of this article, I believe you have a deeper understanding of how to deal with 11g RAC Node second Mmon process exception, and the specific usage still needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report