- Successful growing business for more than 10 years \n- Served many customers with complex requirements/infrastructure just like yours. \n- Operate globally for 24 x 7 “always awake” services\n
\n
\n
Clusterware is generic with customizations for Oracle resources.\nOnly Clusterware accesses OCR and VD.\nOnly DB instances access shared database files.\nOCR is accessed by almost every Clusterware component - configuration read from OCR.\nVIP is part of OC.\nEmphasize shared access to data!!!\n
Clusterware is generic with customizations for Oracle resources.\nOnly Clusterware accesses OCR and VD.\nOnly DB instances access shared database files.\nOCR is accessed by almost every Clusterware component - configuration read from OCR.\nVIP is part of OC.\nEmphasize shared access to data!!!\n
Clusterware is generic with customizations for Oracle resources.\nOnly Clusterware accesses OCR and VD.\nOnly DB instances access shared database files.\nOCR is accessed by almost every Clusterware component - configuration read from OCR.\nVIP is part of OC.\nEmphasize shared access to data!!!\n
Clusterware is generic with customizations for Oracle resources.\nOnly Clusterware accesses OCR and VD.\nOnly DB instances access shared database files.\nOCR is accessed by almost every Clusterware component - configuration read from OCR.\nVIP is part of OC.\nEmphasize shared access to data!!!\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
OPROCD - pre 10.2.0.4 - hangcheck-timer\n
Node membership and group membership for instances, ASM diskgrops\n
Node membership and group membership for instances, ASM diskgrops\n
CSSD cannot talk to each other -> operations are not synchronized -> shared data access -> corruption\n
CSSD cannot talk to each other -> operations are not synchronized -> shared data access -> corruption\n
CSSD cannot talk to each other -> operations are not synchronized -> shared data access -> corruption\n
CSSD cannot talk to each other -> operations are not synchronized -> shared data access -> corruption\n
CSSD cannot talk to each other -> operations are not synchronized -> shared data access -> corruption\n
CSSD cannot talk to each other -> operations are not synchronized -> shared data access -> corruption\n
CSSD cannot talk to each other -> operations are not synchronized -> shared data access -> corruption\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
In addition to NHB, Oracle introduced DHB.\nIO Fencing needed on split brain to avoid evicted node doing any further IO’s.\nOracle doesn’t rely on any hardware - need compatibility with all palatform/hardware.\n
\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
Oracle can’t shoot another node without remote control and can’t rely on one type of IO fencing (HBA/SCSI reservations).\nWhat’s left - beg another another - please shoot yourself!\n
What if CSSD is not healthy? It’s very possible that it’s not network problem but CSSD just doesn’t reply for some reason. OCLSOMON comes to the scene.\n
What if CSSD is not healthy? It’s very possible that it’s not network problem but CSSD just doesn’t reply for some reason. OCLSOMON comes to the scene.\n
Worse yes, the whole node is sick and even OCLSOMON can’t function properly. Like CPU execution is stall.\n
Worse yes, the whole node is sick and even OCLSOMON can’t function properly. Like CPU execution is stall.\n
Worse yes, the whole node is sick and even OCLSOMON can’t function properly. Like CPU execution is stall.\n
Worse yes, the whole node is sick and even OCLSOMON can’t function properly. Like CPU execution is stall.\n
Worse yes, the whole node is sick and even OCLSOMON can’t function properly. Like CPU execution is stall.\n
Worse yes, the whole node is sick and even OCLSOMON can’t function properly. Like CPU execution is stall.\n
Losing access to voting disks - CSSD commit suicide.\nWhy? Cluster must have two communication paths + VD is the media for IO fencing.\n
Losing access to voting disks - CSSD commit suicide.\nWhy? Cluster must have two communication paths + VD is the media for IO fencing.\n
Losing access to voting disks - CSSD commit suicide.\nWhy? Cluster must have two communication paths + VD is the media for IO fencing.\n
All nodes can reboot if voting disk is lost.\nGood time to discuss voting disk redundancy? 1 vs 2 vs 3\n
All nodes can reboot if voting disk is lost.\nGood time to discuss voting disk redundancy? 1 vs 2 vs 3\n
All nodes can reboot if voting disk is lost.\nGood time to discuss voting disk redundancy? 1 vs 2 vs 3\n
All nodes can reboot if voting disk is lost.\nGood time to discuss voting disk redundancy? 1 vs 2 vs 3\n
All nodes can reboot if voting disk is lost.\nGood time to discuss voting disk redundancy? 1 vs 2 vs 3\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
diagwait -> not set by default (assumed 0)\nreboottime -> 3 seconds\nmargin = reboottime - diagwait\n\nSee init.cssd for more details\n
\n
\n
\n
\n
\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
When Clusterware autostart is disabled (crsstart -> disable) then “init.cssd autostart” doesn’t do anything. In this case a DBA can initiate the start later using “init.crs start” (10.1+) or crsctl start crs (10.2+).\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Configuration data - voting disks, ports, resource profiles (ASM, instances, listeners, VIPs and etc).\n
\n
\n
\n
\n
\n
DEMO - existing dependencies\n
DB is in CRS Home\nLog files would be in appropriate Oracle home:\n{home}/log/{host}/racg/{resource_name}.log\nDEMO - log files and action script home match!\nDEMO - IMON logs\n
DEMO - stop DB + rename spfile + start DB\nold way if have time with .cap file\n