Location of Log files in Exadata

On the cell nodes

============

1. Cell alert.log file

/opt/oracle/cell/log/diag/asm/cell/{node name}/trace/alert.logorif the CELLTRACE parameter is set just do cd $CELLTRACE

2. MS logfile

/opt/oracle/cell/log/diag/asm/cell/{node name}/trace/ms-odl.log.

orif the CELLTRACE parameter is set just do cd $CELLTRACE

3. OS watcher output data

/opt/oracle.oswatcher/osw/archive/

To get OS watcher data of specific date :

#cd /opt/oracle.oswatcher/osw/archive

#find . -name '*12.01.13*' -print -exec zip /tmp/osw_`hostname`.zip {} ;

where 12- year 01- Month 13-day

4. Os message logfile

/var/log/messages

5. VM Core files

/var/log/oracle/crashfiles

More details can be found in the following note:

Where / How to find OS crashcore file in Exadata Systems [Linux] (Doc ID 1389225.1)

6. SunDiag output files.

/tmp/sundiag_.tar.bz2

7. Cell patching issues related logfiles:

/var/log/cellos

The major logfile of patch application output you will find in the db node from where you are patching in the location /tmp/<cell version>/patchmgr.stdout and patchmgr.err

8. Disk controller firmware logs:

/opt/MegaRAID/MegaCli/Megacli64 -fwtermlog -dsply -a0

Download Free Oracle Exadata Certification Exam Dumps

On the Database Nodes

================

1. Database alert.log

$ORACLE_BASE/diag/rdbms/{DBNAME}/{sid}/trace/alert_{sid}.log

Ex: /u01/app/oracle/diag/rdbms/dbfs/DBFS2/trace/alert_DBFS2.log

2. ASM alert.log

$ORACLE_BASE/diag/asm/+asm/+ASM{instance number}/trace/ alert_+ASM {instance number}.log

Ex: /u01/app/oracle/diag/asm/+asm/+ASM2/trace/alert_+ASM2.log

3. Clusterware CRS alert.log

$GRID_HOME/log/{node name}/alert{node name}.log

Ex: /u01/app/11.2.0/grid/log/dmorldb02/alertdmorldb02.log

4. Diskmon logfiles

$GRID_HOME/log/{node name}/diskmon/diskmon.lo*

Ex: /u01/app/11.2.0/grid/log/dmorldb02/diskmon/diskmon.log

5. OS Watcher output files

/opt/oracle.oswatcher/osw/archive/

To get OS watcher data of specific date :

#cd /opt/oracle.oswatcher/osw/archive

#find . -name '*12.01.13*' -print -exec zip /tmp/osw_`hostname`.zip {} ;

where 12- year 01- Month 13-day

6. Os message logfile

/var/log/messages

7. VM Core files for Linux

/u01/crashfiles

More details can be found in the following note:Where / How to find OS crashcore file in Exadata Systems [Linux] (Doc ID 1389225.1)

8. Disk controller firmware logs:

/opt/MegaRAID/MegaCli/Megacli64 -fwtermlog -dsply -a0


What are the Exadata Installation Activities ?

ASR Installation and Registration procedure with Oracle

Plateforms:

RHEL 3 or latter x86
SUSE Linux 9 or latter x86
OEL 4 or latter x86

Software Requirement (08/10/2013) :

1. Oracle Automated Service Manager (OSAM) Package (Patch Number p17270592_150_Linux-x86-64.zip)
2. Oracle Automated Service Request (ASR) Package (Patch Number p17199302_45_Linux-x86-64.zip)
3. Service Tools Bundle (STB) (Patch Number p12757884_10000_Generic.zip)

Here we have taken rpm and patch for testing purpose, it's always best practice to use latest RPMs and patch.

All the installation must be done by super User

1. Install STB on ASR Manager Server

          #rpm -i sun-hardware-reg-1.0.0-1.i386.rpm
          #rpm -i sun-servicetag-1.1.5-1.i386.rpm

   2. Verify created service tag execute below command

         #/opt/sun/servicetag/bin/stclient -x

  3. Install OSAM on ASR Manager Server

        #rpm -i SUNWsasm-1.5.0-112.rpm

  4. Install ASR Package on ASR Manager Server

       #rpm -ivh SUNWswasr-4.5-20130703104534.rpm

  5. Add asr path in .bash_profile file:

      PATH=$PATH:/opt/SUNWswasr/bin/asr
      export PATH

Register ASR Manager :

Error while mounting NFS file system on Exadata -- reason given by server: Permission denied

One of our colleague faced below issue while mounting NFS file system on Exadata.

[root@nfsclient /]# mount -t nfs 192.168.100.11:/nfs_server /nfs_client
mount: 192.168.100.11:/nfs_server failed, reason given by server: Permission denied

Solution:

NFS_Server IP - 192.168.100.11
NFS_Client IP - 192.168.100.10

Go to NFS Server. In our case NFS server is 192.168.100.11

ssh 192.168.100.11

Check the /etc/exports file

#cat /etc/exports

/nfs_server 192.168.100.*(*)

Edit /etc/exports file

#vi /etc/exports

/nfs_server 192.168.100.10 (rw,sync)

Restart the NFS services.

#service nfs restart

Now check on NFS Client server which is 192.168.100.10

ssh 192.168.100.10

#Service nfs restart
#Service portmap restart

#showmount -e nfsclient ----Here nfsclient is the server name

output:/nfs_server 192.168.100.10      

Now mount the nfs filesystem

[root@nfsclient /]# mount -t nfs 192.168.100.11:/nfs_server /nfs_client

Now it has been mounted successfully.

Pre-login Message / Banner Configuration in Linux

Banner is used to display  welcome message while login to the particular system which may includes warning for unauthorized users and agreement for the user who used to login to the system.

Create a text file with banner description

#vi /etc/ssh/ssh-banner-message.txt

WARNING: Unauthorized access to this system is forbidden and will be prosecuted by law. By accessing this system, you agree that your actions may be monitored if unauthorized usage is suspected

# edit below line in /etc/ssh/sshd-config file

Banner /etc/ssh/ssh-banner-message.txt

#service sshd restart

SSH Login with any user :

Now it will show the pre-login message.