Hi, reg. Node eviction I have one doubt. Could you help me to resolve. How to identify node eviction? In which demon or process logs have that information? and what are the key words would help us to identify the node eviction?
Thank you for your question! Node eviction in Oracle RAC is a crucial topic for ensuring the stability and availability of your cluster. Here's how you can identify and investigate node eviction: Identifying Node Eviction:Node eviction is primarily detected in the CSSD (Cluster Synchronization Services Daemon) logs. These logs provide detailed information about why a node was evicted, including whether it was due to network issues, heartbeat problems, or other critical errors.
Hi, I have one more doubt, regarding GI rolling patch. I have noticed some DBs have not brought up post GI rolling patch. i.e on node1 5 DBs are present. post patching on node1 only 2 DBs have brought up. remaining 3 I have started manually. is this expected? And noticed any errors or failures in both DB as well as CRS alert logs.
from where you have downloaded patch files not getting link and how you directly got all package / installable on /media/ directory
Very informative video . Will this video applicable on RHEL 9.4. ?
I am I don't have oracle RHEL version
Yes
How about using ASM FD?
Hi,
reg. Node eviction I have one doubt. Could you help me to resolve.
How to identify node eviction? In which demon or process logs have that information? and what are the key words would help us to identify the node eviction?
Thank you for your question! Node eviction in Oracle RAC is a crucial topic for ensuring the stability and availability of your cluster. Here's how you can identify and investigate node eviction: Identifying Node Eviction:Node eviction is primarily detected in the CSSD (Cluster Synchronization Services Daemon) logs. These logs provide detailed information about why a node was evicted, including whether it was due to network issues, heartbeat problems, or other critical errors.
@@OracleDBAOnlineTraining Thank you very much.
Hi, I have observer one of my CDB is 19.22 and its PDB is 19.16. how can we fix this?
Apply datapatch -verbose make sure all pdbs are in read write mode
@@OracleDBAOnlineTraining Thank you for your timely help.
Hi, I have one more doubt, regarding GI rolling patch. I have noticed some DBs have not brought up post GI rolling patch. i.e on node1 5 DBs are present. post patching on node1 only 2 DBs have brought up. remaining 3 I have started manually. is this expected? And noticed any errors or failures in both DB as well as CRS alert logs.
you can check if any misconfiguration might be there at db level. otherwise it should autostart.
@@OracleDBAOnlineTraining Thank you for your quick reply.