Shulou(Shulou.com)06/01 Report--

When my colleague generated a performance report on the rac cluster, he found that one instance of the rac cluster did not generate an awr snapshot, and the other instance snapshot was normal. The following are the specific processing steps.

No awr snapshot was generated for instance 1.

SQL > select SNAP_ID,END_INTERVAL_TIME,instance_number from dba_hist_snapshot where instance_number=1;no rows selected

No. 2 snapshot is normal.

SQL > set long 200SQL > set linesize 200SQL > select * from (select SNAP_ID,END_INTERVAL_TIME,instance_number from dba_hist_snapshot where instance_number=2 order by SNAP_ID desc) where rownum < = 10 SNAP_ID END_INTERVAL_TIME INSTANCE_NUMBER -- 24405 17-AUG-19 07.00.47.595 PM 2 24404 17-AUG-19 06.00.42.150 PM 2 24403 17-AUG-19 05.00.37.041 PM 2 24402 17-AUG-19 04.00.31.774 PM 2 24401 17-AUG-19 03.00.26.414 PM 2 24400 17-AUG-19 02.00.21.176 PM 2 24399 17-AUG-19 01.00.16.316 PM 2 24398 17-AUG-19 12.00.10.997 PM 2 24397 17-AUG-19 11.00.05.446 AM 2 24396 17-AUG-19 10.00.59.801 AM 210 rows selected.

The mmon process is related to awr snapshots, and mmnl is related to ash. To view the mmon and mmnl processes of two instances,

No. 2 example

[root@db2] # ps-ef | grep mmonroot 128329 127956 018: 11 pts/2 00:00:00 grep mmonoracle 201527 10 2018? 17:17:11 ora_mmon_ RLZY2 [root @ db2 ~] # ps-ef | grep mmnlroot 131772 127956 018: 17 pts/2 00:00:00 grep mmnloracle 201531 10 2018? 1-06:06:24 ora_mmnl_RLZY2

No. 1 instance

[root@db1 ~] # ps-ef | grep mmonroot 239020 238963 0 18:52 pts/2 00:00:00 grep mmon [root@db1 ~] # ps-ef | grep mmnlroot 239052 238963 0 18:52 pts/2 00:00:00 grep mmnl

You can see that instance 1 has no mmon and mmnl processes.

To view the trace file of the mmon process of instance 1

[root@db1 trace] # ls-lrt * mmon*.trc-rw-r- 1 oracle asmadmin 1351052 Jan 19 2018 RLZY1_mmon_20073.trc-rw-r- 1 oracle asmadmin 173031 Jan 22 2018 RLZY1_mmon_ 49119.trc [root @ db1 trace] # more RLZY1_mmon_49119.trcTrace file / u01/app/oracle/diag/rdbms/rlzy/RLZY1/trace/RLZY1_mmon_49119.trcOracle 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 optionsORACLE_HOME = / u01/app/oracle/product/11.2.0/db_1System name: LinuxNode name: db1Release: 3.8.13-68.3.4.el6uek.x86_64Version: # 2 SMP Tue Jul 14 15:03:36 PDT 2015Machine: x86_64Instance name: RLZY1Redo thread mounted by this instance: 1Oracle process number: 36Unix process pid: 49119 Image: oracle@db1 (MMON) * * oracle@db1 (MMON) * * SESSION ID: (1369.1) 2018-01-19 13purl 5520. 030mm * CLIENT ID: () 2018-01-19 131515 5520.030mm * SERVICE NAME: () 2018-01-19 1355515 purge 20.030mm * MODULE NAME: () 2018-01-19 131515 5520.030mm * ACTION NAME: () 2018-01-19 13 13 : 55 14:00:20.643minact-scn master-status 20.030 minact-scn slave-status: grec-scn:0x0000.00000000 gmin-scn:0x0000.00000000 gcalc-scn:0x0000.00000000*** 2018-01-19 14:00:20.643minact-scn master-status: grec-scn:0x0e0e.55ad96ef gmin-scn:0x0e0e.55abf256 gcalc-scn:0x0e0e.55ac2a0a.KEBM: MMON action policy violation. 'Block Cleanout Optim, Undo Segment Scan' viol=1 Err=12751minact-scn master-status: grec-scn:0x0e0e.5f0ebf8c gmin-scn:0x0e0e.5f0eac2e gcalc-scn:0x0e0e.5f0ead91DDE rules only execution for: ORA 12751 Sync * 2018-01-22 007 06Parade 04.060-START Event Driven Actions Dump-END Event Driven Actions Dump-START DDE Actions Dump-Executing SYNC actionsExecuting ASYNC actions- START DDE Action: 'ORA_12751_DUMP' (Sync)- -Runtime exceeded 300 secondsTime limit violation detected at:ksedsts () + 465 <-kspol_12751_dump () + 145

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.