Oracle Load Balancing RAC

-

In Oracle RAC we have 2 types of listeners 

Remote Listener 

Local Listener 

Remote Listener always updated with scan IP and local listener with Local VIP of the instance. When ever user process makes a connection request to the scan listener it uses LBA(load Balance Advisory ) to redirect the connection to the  local listener of the least node of the cluster in Round Robin fashion.

Oracle Load balancing is of 2 types 

client side and server side 

Client-side load balancing balances the connection requests across the listeners. With server-side load balancing

server-side load balancing, the SCAN listener directs a connection request to the best instance currently providing the service by using the load balancing advisory.

Note: In Oracle RAC the default  connection is dedicated connection , however we can specify shared connection during DBCA configuration




Comments

Post a Comment

Popular posts from this blog

ZDLRA

-
  RPO focuses on the maximum acceptable data loss  RTO focuses on the maximum acceptable downtime. Oracle DG - RTO Active DG - RTO RAC  - RTO Golden Gate - RPO Flashback - RPO ZDRLA - RPO Oracle Zero Data Loss Recovery Appliance (ZDLRA) deliver to you the capacity to improve the reliability of your environment in more than one way. You can improve the RPO. It has  lot of new cool features  virtual backups Real-time redo Tape and cloud DG/MAA integration Incremental forever backup strategy ZDLRA is one Engineered System built over Exadata. Contains Exadata Storage and Database nodes, InfiniBand network, SAS drivers Exadata, it is not just hardware, it is software too. ZDLRA solve problems in more than one topic, it is not just a backup appliance where you redirect your backups, it is an appliance that provides zero data loss. To do that the key features are: Virtual backups: Based on the input backups (incremental) generate a virtual full backup for you. Real-tim...
Read more

DB Wait events

-
  CPU Time: Scenario: A SQL query is taking a long time to execute, causing the CPU Time wait event to occur. The query is using a full table scan instead of an index, which is causing a high CPU load and slowing down other processes. fixes: ===== Adding indexes Query rewrites  limiting number of sessions  I/O Related Wait Events: Scenario: A database application is experiencing slow I/O operations, causing the I/O Related Wait Event to occur. The storage systems are not optimized and there is heavy contention for storage resources. Fixes: =====  Review your Storage system  Check for disk usage  Check for storage replacement for a high end hardware Locks: Scenario: A database application is experiencing slow performance due to excessive locking. The application is using table-level locking, causing a high contention for resources and slowing down other processes. fixes : ==== switch to row level locking Make sure to use frequent commits in the code  Ne...
Read more

database Auditing

-
Every time a user attempts anything in the database where audit is enabled the Oracle kernel checks to see if an audit record should be created or updated (in the case or a session record) and generates the record in a table owned by the SYS user called AUD$. This table is, by default, located in the SYSTEM tablespace. This itself can cause problems with potential denial of service attacks. If the SYSTEM tablespace fills up, the database will hang. init parameters Until Oracle 10g, auditing is disabled by default, but can be enabled by setting the AUDIT_TRAIL static parameter in the init.ora file. From Oracle 11g, auditing is enabled for some system level privileges. SQL> show parameter audit NAME TYPE VALUE ---------------------- ------------ ------------- audit_file_dest string ?/rdbms/audit audit_sys_operations boolean FALSE audit_syslog_level string NONE audit_trail string DB transaction_auditing boolean TRUE AUDIT_TRAIL can have the following values....
Read more