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

This article mainly introduces which node will survive when brain fissure occurs in oracle12c. The introduction in this article is very detailed and has certain reference value. Interested friends must read it!

APPLIES TO:Oracle Database-Enterprise Edition-Version 12.1.0.2 and laterInformation in this document applies to any platform.Oracle Enterprise Edition, from 12.1.0.2 and later, for any platform. PURPOSETo understand the new behavior, from 12.1.0.2, of which node will survive when split brain takes place. In order to better understand which node will survive brain fissure in versions from 12.1.0.2 onwards. DETAILSIn 11.2 or even older version, the lowest number node will survive when splitbrain takes place, however this has changed in 12.1.0.2 with the introduction ofnode weight. Started from 12.1.0.2, during split brain resolution, node withhigher weight will survive:-- 11.2 and earlier, when a brain fissure occurs, the smaller nodes will survive. However, it has changed since 12.1.0.2, and the concept of weight is introduced. When there is a brain fissure, the nodes with high weight will survive.

2014-11-24 14 node 25 CSSD:1117321536 41.140603: clssnmrCheckNodeWeight: node (1) has weight stamp (0), pebble (0)

2014-11-24 14 node 25 node 41.140609: CSSD:1117321536: node (2) has weight stamp (311972654), pebble (3)

2014-11-24 14 stamp 25 stamp 41.140612: CSSD:1117321536: clssnmrCheckNodeWeight: stamp (311972654), completed (1amp 2)

2014-11-24 1415 1415: CSSD:1117321536: clssnmrCheckSplit: Waiting for node weights, stamp (311972654)

2014-11-24 14 not evicted 25V 41.188880: CSSD:1084811584: clssnmvDiskKillCheck: not evicted, file / dev/raw/raw2 flags 0x00000000, kill block unique 0, my unique 1416805718

2014-11-24 14 Writing with status 0x3 25 CSSD:1114167616: 41.558921: clssnmvDiskPing: Writing with status 0x3, timestamp 1416810341Accord 1022717334

2014-11-24 14 node1: CSSD:1086388544: clssnmvDHBValidateNCopy: node1, node1, has a disk HB, but no network HB, DHB has rcfg 311972655, wrtcnt, 9527468, LATS 102 2717514, lastSeqNo 9527467, uniqueness 1416808381, timestamp 1416810341 1022722074

2014-11-24 14 manual shutdown of nodename node1 25V 41.731928: CSSD:1086388544: clssnmvReadDskHeartbeat: manual shutdown of nodename node1, nodenum 1 epoch 1416810341 msec 1022722074

2014-11-24 14 node 25V 41.732266: CSSD:1117321536: clssnmrCheckNodeWeight: node (2) has weight stamp (311972654), pebble (3)

2014-11-24 14 stamp 25V 41.732273: CSSD:1117321536: clssnmrCheckNodeWeight: stamp (311972654), completed (1ama 1)

2014-11-24 14 My cohort 2515 41.732294: CSSD:1117321536: clssnmCheckDskInfo: My cohort:

2014-11-24 14 Start 25lo 41.732299: CSSD:1117321536: clssnmRemove:

2014-11-24 14 clssnmrRemoveNode: CSSD:1117321536: (: CSSNM00007:) clssnmrRemoveNode: Evicting node1, node1, from the cluster in incarnation 311972655, node birth incarnation 311972654, death incarnation 311972655, stateflags 0x225000 uniqueness value 1416808381 The number of the resource executing on each node and others are considered by the weight. Reference

The above is all the contents of the article "which node will survive when a brain fissure occurs in oracle12c". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

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.