NaturalOracle DataGaurd tutorial Series Coming Soon!! Natural
For Any queries, please mail us at support@funoracleapps.com

Setup DNS server using BIND on OEL/Linux

No comments
In this post, I am going to share the steps for setup of DNS server. It will be used in my upcoming posts for RAC 12c setup.

Pre-req:
Virtual Box is installed and a Machine is prepared. Below is the configuration of the machine.

Virtual DNS OS Configuration:
RAM: 1GB
HardDisk Size : 12 GB

Operating System: Oracle Enterprise Linux

The installation of the Server would be a basic installation with Option selected as Software Development Workstation to get a GUI. Once the OS installation is done you can optionally install Guest Addition as it helps for easy mouse movements and sharing a file from host system to this guest virtual system.






Steps to configure DNS Server.

  • ·         Install DNS Package
  • ·         Assign static IP to the server
  • ·         Assign FQDN(Fully Qualified Domain Name) for server
  • ·         Configure /etc/hosts
  • ·         Configure /etc/resolv.conf        
  • ·         Configure /etc/named.conf
  • ·         Configure Forward and reverse zone
  • ·         Change the group ownership  of Forward and reverse zone file
  • ·         Restart DNS Server.
  • ·         Change permission of the resolv.conf

Installation of the DNS server (BIND)


From the command line issue the following command.
# yum install bind-libs bind bind-utils

Assign static IP


cd /etc/sysconfig/network-scripts
I am using my adapter 2 so I have changed the entry in eth1.
Change ifcfg-eth1 file and add below entry

cd /etc/sysconfig/network-scripts
vi ifcfg-eth1

BOOTPROTO=static
IPADDR=192.168.56.101
GATEWAY=255.255.255.0
NETMASK=255.255.255.0

Assign FQDN for server

 Add any fully qualified name which you want to give. 
vi /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=himvirtualdns.lab

Change /etc/resolv.conf


Change /etc/resolv.conf and also change it permission so that it will be not overwritten once server is restarted.
This resolv.conf entry has to be made on all the client systems as well.

[root@himvirtualdns network-scripts]# cat /etc/resolv.conf
# Generated by NetworkManager
search himvirtualdns.lab
nameserver 192.168.56.101

Permission change
chattr +i resolv.conf



Change /etc/named.conf  File


Edit the contents of the "/etc/named.conf" file. Depending on the setup you require, you may need to make lots of changes, or none at all. For my home network I use "himvirtualdns.lab" as my domain and the IP range "192.168.56.*", so this is what I will show here.
We are adding both forward and reserve lookup
I will show lines which needs to be updated and added

            listen-on port 53 { 127.0.0.1;192.168.56.101; };
            
            allow-query     { any; };
        

        type master;
        file "himvirtualdns.lab.zone";
        allow-update { none; };
};

zone "56.168.192.in-addr.arpa." IN {
        type master;
        file "56.168.192.in-addr.arpa";
        allow-update { none; };
};


Create Forward and Reverse zone files

Create forward and reverse lookup file


cd  /var/named
touch 56.168.192.in-addr.arpa himvirtualdns.lab.zone
Add below entry in respective files.
[root@himvirtualdns named]# cat himvirtualdns.lab.zone
$TTL    86400
@               IN SOA  localhost root.localhost (
                                        42              ; serial (d. adams)
                                        3H              ; refresh
                                        15M             ; retry
                                        1W              ; expiry
                                        1D )            ; minimum
                IN NS           localhost
               
localhost       IN A            127.0.0.1
himvirtualdns   IN A    192.168.56.101

[root@himvirtualdns named]# cat 56.168.192.in-addr.arpa
$ORIGIN 56.168.192.in-addr.arpa.
$TTL 1H
@       IN      SOA     himvirtualdns.lab.     root.himvirtualdns.lab. (      2
                                                3H
                                                1H
                                                1W
                                                1H )
56.168.192.in-addr.arpa.         IN NS      himvirtualdns.lab.

101     IN PTR  himvirtualdns.lab.

 Change Ownership of the forward and reverse file.

cd /var/named
chown named:named 56.168.192.in-addr.arpa himvirtualdns.lab.zone

To Make sure Bind is started every time server is restarted.


chkconfig named on

Restart named

service named restart

Check if DNS is working fine


[root@himvirtualdns named]# nslookup himvirtualdns
Server:             192.168.56.101
Address:          192.168.56.101#53

Name:  himvirtualdns.himvirtualdns.lab
Address: 192.168.56.101

[root@himvirtualdns named]# nslookup 192.168.56.101
Server:             192.168.56.101
Address:          192.168.56.101#53

101.56.168.192.in-addr.arpa      name = himvirtualdns.lab.


No comments :

Post a Comment

Running Autoconfig in R12.2

No comments
In R12.2 we have 2 file systems RUN and PATCH. Whenever we are making any changes in context file always make those in both RUN and PATCH context file to keep them in sync.

Below are the steps to execute autoconfig in R12.2 Environments
In below example I am making changes to forms trace directory.

Steps:

1.Make sure your application services are down.
2.Database services and Listener should be up and running.
3.Identify the Context which needs to be modified.
4.In R12.2 make sure you run Autoconfig on both run and patch file.
5.Getting context file use below
Source Run File system
. EBSapps.env run
echo $CONTEXT_FILE ( This will give you full path with Context file name in run file system)

Source Patch File System
. EBSapps.env patch
echo $CONTEXT_FILE ( This will give you full path with Context file name in patch file system)
6.Make the necessary parameter changes in Both the context files. But always ensure to take a copy of the respective context files(Run and  Patch) before changing.
7.Connect to putty as applmgr.
8.Change Run Context file

[applmgr@sebs admin]$ diff SEBS122_sebs.xml_orig SEBS122_sebs.xml
142c142
<          <forms_trace_dir oa_var="s_forms_trace_dir">/u01/application/SEBS122/fs2/inst/apps/SEBS122_sebs/logs/ora/10.1.2/forms</forms_trace_dir>
---
>          <forms_trace_dir oa_var="s_forms_trace_dir">/u01/application/SEBS122/trace</forms_trace_dir>
[applmgr@sebs admin]$ echo $FILE_EDITION
run

Change the Patch Context file

[applmgr@sebs admin]$ diff SEBS122_sebs.xml_orig SEBS122_sebs.xml
142c142
<          <forms_trace_dir oa_var="s_forms_trace_dir">/u01/application/SEBS122/fs1/inst/apps/SEBS122_sebs/logs/ora/10.1.2/forms</forms_trace_dir>
---
>          <forms_trace_dir oa_var="s_forms_trace_dir">/u01/application/SEBS122/trace</forms_trace_dir>

9.Verify all application services are down.
10.Run autoconfig
Source RUN file system 
cd $ADMIN_SCRIPTS_HOME
./adautocfg.sh

Make sure it completes successfully.

11.Connect to sqlplus using system user.
sqlplus system/manager
alter trigger ebs_logon disable;

12.Run autoconfig
Source Patch file system 
cd $ADMIN_SCRIPTS_HOME
./adautocfg.sh

Make sure it completes successfully.


13.Connect to sqlplus using system user.
sqlplus system/manager

alter trigger ebs_logon enable;

1     


No comments :

Post a Comment

Addition of New node in R12.2 having shared file system

No comments

Pre-Reqs


  • User ID and Group ID should be consistent across all nodes to avoid file access permission issues.
  • The same absolute path must be retained for the shared file system mount points on each node.
  • The value for the context variable "s_atName" must be same across all the application tier node context files.
  • Password less ssh between the nodes.
  • The database and TNS listener must be running before the steps listed below are performed.


Steps:

1. Ensure that value of the AutoConfig variable s_shared_file_system is set to true on the primary application node.(Node Where you weblogic admin server runs)
Please change it to true if not already present and run AutoConfig on both RUN & PATCH FS

2. Source Run Filesystem make sure all services are down.

3.Execute adpreclone Utility on the Run and Patch File System

On the run file system:

$ cd <inst-top-run-fs>/admin/scripts 
$ ./adadminsrvctl.sh start
$ ./adpreclone.pl appsTier
Once the utility completes, shut down the application tier processes:
$ ./adstpall.sh <apps-user-name>/<apps-password>


On the patch file system:

$ cd <inst-top-patch-fs>/admin/scripts 
$ ./adadminsrvctl.sh start forcepatchfs 
$ ./adpreclone.pl appsTier
Once the utility completes, shut down the application tier processes.
$ ./adstpall.sh <apps-user-name>/<apps-password> forcepatchfs



The AD/TXK D7 patch introduce a new flow that adds both the run and patch edition file system with a single command. The steps given below configures both Run and Patch edition file system for a new node that is going to be added to the farm. 

1. Ensure the correct perl utility is in the $PATH. You must use the perl utility installed in the Fusion Middleware Oracle Home.

For example:

$ export PATH=/u01/12.2/fs1/FMW_Home/webtier/perl/bin:$PATH

2. Ensure the WebLogic Administration Server is running from both run and Patch file system on the primary application tier node.

3. A sample pairsfile for the run/patch file system is instantiated into the instance home on the primary application tier node. The file is called <SID>_<primary_node_name>_.txt, and located in the <inst_top>/appl/admin/ directory. For a configuration with an instance name of VIS, the pairsfile will be /u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.txt.

4.Create the required directories and copy the pairsfile into a directory of your choice on the secondary application tier node. For example:

$ /bin/mkdir -p /u01/12.2/pairsfiles
$ cd /u01/12.2/pairsfile
$ /bin/cp /u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.txt mypairsfile.txt
Make changes to pairs file as needed
5. Execute adclonectx utility to configure both run and Patch file system

$ cd /u01/12.2/fs1/EBSapps/comn/clone/bin
$ /u01/12.2/fs1/FMW_Home/webtier/perl/bin/perl ./adclonectx.pl \
addnode contextfile=/u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.xml \ 
pairsfile=/u01/12.2/pairsfile/mypairsfile.txt \
dualfs=yes
4. Review the log files displayed by the add node utility to ensure that the add node operation has gone through successfully. 


Reference:
Sharing The Application Tier File System in Oracle E-Business Suite Release 12.2 (Doc ID 1375769.1)

No comments :

Post a Comment

Running Autoconfig in R12.2

1 comment
If we are changing any parameter in the Context file in R12.2 environment then the parameter should be change in both the RUN and PATCH file system context file and then we should run the Autoconfig.


Steps:

Stop all the Services

On RUN File System
1. Source the RUN file system environment.
2. Modify the Parameter in Context File
3. Run Autoconfig on RUN Filesystem
  cd $ADMIN_SCRIPTS_HOME
  ./adautocfg.sh
  
Important Steps
Disable the EBS LOGON TRIGGER
Connect to System User
  conn system/manager
  alter trigger ebs_logon disable;
  
On Patch File System  
1. Source the PATCH file system environment.
2. Modify the Parameter in Context File
3. Run Autoconfig on PATCH Filesystem
  cd $ADMIN_SCRIPTS_HOME
  ./adautocfg.sh
  
Important Steps
Enable the EBS LOGON TRIGGER
Connect to System User
  conn system/manager
  alter trigger ebs_logon enable; 
  
  
Start all services  
  

1 comment :

Post a Comment