configure DNS for Installtion of Oracle Grid Infrastructure RAC cluster

1.create these files :-  forward.zone,reverse.zone and named.rfc1912.zones into /var/named/chroot/var/named

2.content of forward.zone :-
$TTL 86400
@          IN     SOA    rac.  rac. (
                         42 ; serial (d. adams)
                         3H ; refresh
                        15M ; retry
                         1W ; expiry
                         1D ) ; minimum
@          IN   NS     rac.
rac       IN   A      192.168.72.128
localhost                     IN A    127.0.0.1
rac2                          IN A    192.168.72.129
rac-vip                       IN A    192.168.72.102
rac2-vip                      IN A    192.168.72.104
rac-cluster-scan              IN A    192.168.72.106
rac-cluster-scan              IN A    192.168.72.107
rac-cluster-scan              IN A    192.168.72.108

3.content of reverse.zone :-
$TTL 86400
@        IN     SOA    rac.  rac. (
                         42 ; serial (d. adams)
                         3H ; refresh
                        15M ; retry
                         1W ; expiry
                         1D ) ; minimum
@         IN   NS   rac.
128.72.168.192      IN   PTR  rac.
1.0.0.127           IN   PTR  localhost.
129.72.168.192      IN   PTR  rac2.
102.72.168.192      IN   PTR  rac-vip.
104.72.168.192      IN   PTR  rac2-vip.
106.72.168.192      IN   PTR  rac-cluster-scan.
107.72.168.192      IN   PTR  rac-cluster-scan.
108.72.168.192      IN   PTR  rac-cluster-scan.

4.content of named.rfc1912.zones :-
zone "rac" IN {
                 type master; 
                 file "forward.zone"; 
                  
};
zone "72.168.192.in-addr.arpa" IN {
                 type master;
                 file "reverse.zone";
                 };
5.change the ownership and owner of these files by below command :-

chown named:named *.*

6.create the named.conf into /var/named/chroot/etc

7.content of named.conf :-

options {
listen-on port 53 { 192.168.72.128; };
# listen-on-v6 port 53 { ::1; };
        directory "/var/named";
        recursion yes;
        };
logging {
        channel default_debug {
        file "data/named.run";
        severity dynamic;
        };
};
  include "named.rfc1912.zones";

8.change the ownership and owner of these files by below command :-

chown named:named *.*

9.config the file /etc/resolv.conf

10.content of /etc/resolv.conf

search rac
nameserver 192.168.72.128

11.change the ownership and owner of these files by below command :-

chown named:named *.*

12. start the named service :-

service named start

chkconfig named on

13.Test the DNS IP reachability :-

nslookup rac

nslookup rac2

nslookup rac-cluster-scan

14. contents of /etc/hosts file :-

cat /etc/hosts
# that require network functionality will fail.
127.0.0.1       localhost.localdomain localhost
::1             localhost6.localdomain6 localhost6
#eth1 - PUBLIC
192.168.72.128 rac
192.168.72.129 rac2
#VIP
192.168.72.102 rac-vip
192.168.72.104 rac2-vip
#eth2 - PRIVATE
192.168.140.128 rac-pvt
192.168.140.129 rac2-pvt

Note :- Make all these changes to all node , by interchanging the node name .

VOILA ----> Now you ready to Oracle Grid Infrastructure Installation ;) Here I am sharing one snap :-


Comments

Post a Comment

Popular posts from this blog

Installing DBMS_JAVA package in Oracle and calling UTL_DBWS web services through Oracle database

Installing DBMS_JAVA package in Oracle following  files need to be run:-  sql> select comp_name, version, status from dba_registry where comp_name like '%JAVA%'; @?/javavm/install/initjvm.sql; @?/xdk/admin/initxml.sql; @?/xdk/admin/xmlja.sql; @?/rdbms/admin/catjava.sql; @?/rdbms/admin/catexf.sql; and verify your java installation in Oracle Database  sql> select comp_name, version, status from dba_registry where comp_name like '%JAVA%'; sql> select dbms_java.longname(object_name), status, object_type from all_objects where       object_type = 'JAVA CLASS'; ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ calling  UTL_DBWS  web services through Oracle Database :-  set the follwing parameters in .bash_profile of oracle user  export JAVA_HOME=$ORACLE_HOME/jdk ORACLE_BASE=/opt/oracle/product; export ORACLE_BASE ORACLE_HOME=/opt/oracle/product/11.2.0/dbhome_1; export ORACLE_HOME PATH=$PATH:/opt/o
Read more

stick the job to the specific instance in Oracle RAC

First method ( and easy one too ) :- note:-  must perform this activity on each instance one by one. ......stop jobs which is assigning to the specific instance..... $ export ORACLE_SID=SID connect database using job owner .... $ sqlplus username/password list of jobs and its instance....  sql> select JOB,INSTANCE from user_jobs;        JOB   INSTANCE ---------- ----------       2510          0       2951          0       2992          0       3091          0       3111          0       1570          0       1567          0       1568          0       1569          0       1571          0       1572          0 stick the job to the specific instance..... Syntax DBMS_JOB.INSTANCE (    job        IN BINARY_INTEGER,    instance   IN BINARY_INTEGER,    force      IN BOOLEAN DEFAULT FALSE); sql>execute dbms_job.instance(job=>1571, instance=>2,force=>true); verify from the instance number........
Read more

Starting background process GTX4 and GLOBAL_TXN_PROCESSES

Starting background process GTX4 Tue Jan 01 15:51:12 2012 GTX4 started with pid=64, OS id=11122 Tue Jan 01 15:51:43 2012 Auto-tuning: Starting background process GTX5 and Auto-tuning: Shutting down background process GTXi Like messages in alert log in RAC database This event is recorded in RAC environment only, which is normal.    Its normal for the database to automatically tune the number of these processes based on the workload of XA global transactions. If any application which using XA transaction and connecting to oracle RAC database, is it required. This normal behavior and you do not have to worry about this error messages.  If you are sure that you are not using XA and want to stop these messages. You can disable the GTXn background processes, then you must set GLOBAL_TXN_PROCESSES to 0 in your parameter file. Setting this parameter to 0 will disable the XA support on an Oracle RAC database. GLOBAL_TXN_PROCESSES specifies the initial numb
Read more