Category: rac

OLR and GPNP Profile

OLR

ls -ltr /etc/oracle/olr.loc
viz. $GIHOME/cdata/<hostname>.olr

$ cat olr.loc
olrconfig_loc=/u01/app/oracle/grid/11.2.0/cdata/<hostname>.olr
crs_home=/u01/app/oracle/grid/11.2.0

$ ./ocrcheck -local

$ ./ocrcheck -local -config

Oracle Local Registry configuration is :
Device/File Name         : /u01/app/oracle/grid/11.2.0/cdata/<hostname>.olr

 


GPNP

GPnP Deamon (GPnPD)

GRID_HOME/gpnp/<hostname>/profiles/peer/profile.xml

[root@host01 peer]# gpnptool get

Advertisements

SCAN KeyPoints

 

$ /usr/sbin/nslookup rac-scan.example.com

$GRID_HOME/bin/srvctl config scan
$GRID_HOME/bin/srvctl config scan_listener

$ SRVCTL STATUS SCAN_LISTENER

$ lsnrctl services LISTENER_SCAN2

using EZConnect : *.REMOTE_LISTENER=rac-scan.example.com:25000

The keyword REMOTE SERVER, indicating that the LISTENER_SCAN2 listener will redirect the connection requests to the rac2 node VIP listener, thereby forwarding the connection to the RAC2 instance.

The lsnrctl services command output of a VIP listener will print services as LOCAL SERVER
keyword, indicating that the VIP listener will handle the connection for that service.

The local_listener parameter should refer to the VIP listener running on the
local node, and the remote_listener parameter should refer to the SCAN listeners using EZConnect syntax specifying the DNS alias of the SCAN IP address and port number

The initialization parameter remote_listener is set to the TNS alias of SCAN listener or EZConnect syntax using the SCAN IP address and port number.

SCAN IP is a new “layer” network (oracle) with high availability that allows you to change the characteristics of your cluster (i.e add/remove nodes) without the need to make configuration changes in their clients “Grid concept”.

The IP SCAN and VIP have different goals, therefore working together :
The VIP IP provides high availability at the level of the Cluster.
The SCAN IP provides high availability at the level of the Clients.

Clusterware and ASM upgrade (GI Upgrade) – Bits & Pieces

 

Upgrade from old (11.1, or 10G) to 11gR2

The upgrade to Oracle Clusterware 11gR2 will be an out of place upgrade hence a new CRS_HOME including ASM will be created which will be referred as the new GRID_Infrastructure home. If an existing ASM_HOME is present in 10gR1/10gR2 or 11gR1 then ASM will be upgraded automatically as well.

SQL> startup upgrade

SQL> @catupgrd.sql

SQL> startup

SQL> @utlu112s.sql
SQL> @catuppst.sql

SQL> SELECT count(*) FROM dba_invalid_objects;
SQL> SELECT distinct object_name FROM dba_invalid_objects;

SQL> @utlrp.sql

srvctl upgrade database -d db-unique-name -o oraclehome

ocrconfig -upgrade

# GRID_Home/rootupgrade.sh
(to be run from all nodes)

 

You can refer to below for more details :

http://askdba.org/weblog/2010/10/upgrading-grid-infrastructure-11201-to-11202-on-rhel4/

Oracle Clusterware (CRS or GI) Rolling Upgrades (Doc ID 338706.1)