“[contact-form]

[oracle@LONDT778W-D4 ~]$ cat test_aud_del.sh
#!/usr/bin/ksh

ORACLE_SID=SANJAY
export ORACLE_SID
ORACLE_HOME=/sanjay/sw/oracle/database/11.2.0.2
export ORACLE_HOME

LOGFILE=”/tmp/delete_old_aud.log”

echo `date` >>$LOGFILE
if [ $ORACLE_SID = "SANJAY" ] >>$LOGFILE
then

echo “Deleting the audit files older than 90 days for database `echo $ORACLE_SID`” >>$LOGFILE

echo “Audit files older than 90 days are: `find /sanjay/sw/oracle/database/admin/SANJAY/adump/*.aud -type f -mtime +90| wc -l`” >>$LOGFILE

find /sanjay/sw/oracle/database/admin/SANJAY/adump/*.aud -type f -mtime +90 -ls -exec rm {} \;

echo “Space usage at this moment is:
`df -h /sanjay/sw/oracle/`” >>$LOGFILE
else
echo “Environment is not set properly” >>$LOGFILE

fi
exit

open a file in vi editor and save it with .sh extention
to run in backgrougn use nohup sh filename.sh &
to see the job status $jobs ( it will show runing or done etc)
to bring/send in forward/background. ctrl+z fg ctrl +z bg

below is a very simple example to start shell script.

“SHELL=/bin/ksh
export SHELL
export ORACLE_SID=instance_name
export ORACLE_HOME=/oraclehome ( can try $ORACLE_HOME also).
export ORACLE_BASE=/oraclebase
sqlplus /nolog <
connect username/password@instance_name
write full command here ;
exit ;

For example if you want to delete files older than 30 days.

find /u1/database/prod/udump/ -type f -mtime +30 -exec rm {} \;

Or as bash script:
Code:
#!/bin/bash

find /u1/database/prod/arch -type f -mtime +30 -exec rm {} \;
The only 2 commands used are find and rm.

Find looks for files older then 30 days (-type f -mtime +30). All its findings are given to rm (-exec rm {} \; ).

You can place the rm statement outside of find, which is supposed to be faster:

find /u1/database/prod/arch -type f -mtime +3 | xargs rm

Now you can crontab it to remove old files (more than 30 days) in a script.

“[contact-form]

We ‘ll walk through the process of building the command. To begin, we want to get a list of active processes on the server. We can do that using the following command:

>ps –ef

If we execute ps –ef on our server, we’ ll see a long list of processes – both for Oracle and for many other things. However, we want to limit your output to only those processes that are related to the Oracle Database. The grep command can be used to do this. Oracle background process names always begin with “ora_”, so piping the output of ps –ef through grep “ora_” will remove all but the Oracle background processes. For example:

>ps –ef |grep “ora_”
oracle 12011 1 0 06-Dec … ora_dbwr_JAP
oracle 12789 20202 0 12:10:55 00:00 grep ora_
oracle 13202 1 0 06-Dec … ora_smon_JAP
oracle 14983 1 0 06-Dec … ora_arch_JAP
oracle 10209 1 0 06-Dec … ora_pmon_JAP
oracle 2090 1 0 06-Dec … ora_reco_JAP
oracle 10404 1 0 06-Dec … ora_lgwr_JAP
oracle 10403 1 0 06-Dec … ora_dbwr_TEST
oracle 10401 1 0 06-Dec … ora_lgwr_TEST

In the above output as we can see it includes the process that’s running grep command. Pipe this output through grep –v grep to remove the grep command, so you don’t kill your own process. T

>ps –ef |grep “ora_”|grep –v grep
oracle 12011 1 0 06-Dec … ora_dbwr_JAP
oracle 13202 1 0 06-Dec … ora_smon_JAP
oracle 14983 1 0 06-Dec … ora_arch_JAP
oracle 10209 1 0 06-Dec … ora_pmon_JAP
oracle 2090 1 0 06-Dec … ora_reco_JAP
oracle 10404 1 0 06-Dec … ora_lgwr_JAP
oracle 10403 1 0 06-Dec … ora_dbwr_TEST
oracle 10401 1 0 06-Dec … ora_lgwr_TEST

Next, we should filter out all processes except those for the current ORACLE_SID. That way we delete the background processes only for that one instance instead of for all instances (if there are multiple database instance running). Do that by grepping for the SID name:

>ps –ef |grep “ora_”|grep –v grep|grep $ORACLE_SID
oracle 12011 1 0 06-Dec … ora_dbwr_JAP
oracle 13202 1 0 06-Dec … ora_smon_JAP
oracle 14983 1 0 06-Dec … ora_arch_JAP
oracle 10209 1 0 06-Dec … ora_pmon_JAP
oracle 2090 1 0 06-Dec … ora_reco_JAP
oracle 10404 1 0 06-Dec … ora_lgwr_JAP

Now that we have an accurate list of processes that you want to kill, you can use the awk command to get the process ID (PID) for each of these processes. The PID is in the second column, so we will use the awk ‘{print $2}’ command to display only that column:

>ps –ef |grep “ora_”|grep –v grep|grep $ORACLE_SID|awk ‘{print $2}’
12011
13202
14983
10209
2090
10404

Now we have a list of process Id numbers for the Oracle background processes. For the last step, we use the xargs command to pipe the list of PIDs to the kill command. For example:

>ps –ef |grep “ora_”|grep –v grep|grep $ORACLE_SID|awk ‘{print $2}’|xargs kill –9
Now that we’ve created this compound command, we can assign it to a Unix alias or we can put it in a file and make it a shell script so that we can execute it with a single short command.

===================
Find command usage:
===================

The Simplest Example
To print the names of all of the files in the directory and all subdirectories
find . -print
find ~ ~barnett /usr/local -print
find ~ ~barnett /usr/local -print
find / -print

Using find with other commands

ls -ld `find . -print`

Using xargs with find

ls -ld `find / -print`

find / -print | xargs ls -ld

Looking for files with particular names

find . -name *.o -print
find . -name ‘*.o’ -print
find . -name ‘[a-zA-Z]*.o’ -print

Looking for files by type

find . -type f -print | xargs ls -l

find . -type l -print | xargs ls -ld | awk ‘{print $10}’

Looking for files by sizes

find . -size 27 -print

find . -size +10000c -size -32000c -print

Searching for old files

find . -mtime 7 -print

find . -mtime +6 -mtime -8 -print

find . -type f -atime +30 -print

Searching for files by permission

find . -name *.o -perm 664 -print

find . -type d -perm 777 -print

find . -perm -20 -print

find . -perm -100 -print

Owners and groups

find . -user root -perm -4000 -print

find . -group staff -perm -2000 -print

find . -user 0 -perm -4000 -print
find . -group 10 -perm -2000 -print

Find and commands

find . -ls

find . -print | xargs ls -gilds

Find and Cpio

find . -depth -cpio >/dev/rmt0
find . -depth -ncpio >/dev/rmt0
find . -depth -print | cpio -oB >/dev/rmt0
find . -depth -print | cpio -ocB >/dev/rmt0

Using Find to Execute Commands

find . -exec echo {} ;

find . -exec echo {} ‘;’

find `pwd` -group staff -exec find {} -type l -print ;

find . -perm -20 -exec chmod g-w {} ;

or
find . -perm -20 -print | xargs chmod g-w

find . -inum 31246 -exec rm [] ‘;’

File comparisons

find /usr -newer /usr/FirstFile -print

Expressions

find /usr ! -newer /FirstFile -print
“find . ( -name a.out -o -name *.o ) -print
“

Keeping find from going too far

find * -type f -print -o -type d -prune

find . -print -o -name SCCS -prune

“[contact-form]

• Archived redo log files
• Backup pieces
• Control files
• Datafiles Spfile
• spfile.

Note: It is ABCDS

RMAN will back up full backups, incremental backups, control file autobackups, and archive redo
log files. Keep in mind that flashback logs, online redo log files, and the current control file are not backed up.

Note: Always enable the autobackup for spfile (only backed up if db starting using spfile) and control file feature.
=====

RMAN> configure controlfile autobackup on;

RMAN> configure spfile autobackup on;

========

How to configure RMAN to write to specific locations on disk.

RMAN> configure channel 1 device type disk format ‘/ora01/rman/rman1_%U.bk’;

Note: CONFIGURE command must be executed before you run the BACKUP command.

=========
Backup Database.
=========

The term “RMAN level 0 incremental backup” doesn’t exactly describe itself very well, either. A level
0 incremental backup is backing up the exact same blocks as a full backup. In other words, the following
two commands back up the exact same blocks in a database:

RMAN> backup as backupset full database;

RMAN> backup as backupset incremental level=0 database;

RMAN> backup database not backed up since time=’sysdate-1′;

RMAN> backup database skip readonly skip offline skip inaccessible; backup database skip offline;

RMAN> backup database skip readonly;

RMAN> backup database skip inaccessible;

————-

Backup Sets versus Image Copies

The default backup mode of RMAN instructs it to only back up blocks that have been used in a datafile;
these are known as backup sets. RMAN can also make byte-for-byte copies of the datafiles; these are
known as image copies. Creating a backup set is the default type of backup that RMAN creates. The next
command creates a backup set backup of the database:

RMAN> backup database; backup as backupset database;

You can instruct RMAN to create image copies by using the AS COPY command. The following
creates image copies of every datafile in the database:

RMAN> backup as copy database; backup incremental level=0 database plus archivelog;

=======
Backup tablespace.
======

RMAN> backup tablespace system, sysaux;

RMAN> configure exclude for tablespace users; configure exclude for tablespace users clear; <== to clear the excluded tablespace.

=======
Backup datafile.
======

RMAN> backup datafile ‘/app/sanjay/11R2/system01.dbf’;

RMAN> backup datafile 1,5;

RMAN> backup as copy datafile 3;

RMAN> backup incremental level 1 datafile 4;

RMAN> backup database not backed up; <== To backup the datafile not backed up.

=======
Backup controlfile.
======

RMAN> backup current controlfile;

RMAN> configure controlfile autobackup format for device type disk to ‘/app/sanjay/rman/rman_ctl_%F.bk’;

=======
Backup spfile.
======

RMAN> backup spfile;

Note: RMAN can only back up the spfile if the instance was started using a spfile.

=========
Backup Archive logs.
=========

RMAN> backup archivelog all;

RMAN> backup archivelog all delete input;

RMAN> backup archivelog sequence 300;

RMAN> backup archivelog sequence between 300 and 400 thread 1;

RMAN> backup archivelog from time “sysdate-7″ until time “sysdate-1″;

http://download.oracle.com/docs/cd/E11857_01/index.htm

OEM 10g Docs

http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/toc.htm

“[contact-form]

PL/SQL stands for Procedural Language extension of SQL. PL/SQL is a combination of SQL along with the procedural features of programming languages. It was developed by Oracle Corporation to enhance the capabilities of SQL.
What is PL/SQL Engine?

Oracle uses PL/SQL engine to processes the PL/SQL statements, A PL/SQL code can be stored in the client system (client-side) or in the database (server-side).

What are advantages of PL/SQL?

A. Block Structures: PL/SQL consists of blocks of code, which can be nested within each other. Each block forms a unit of a task or a logical module. PL/SQL Blocks can be stored in the database and reused.
B. Procedural Language Capability: PL/SQL consists of procedural language constructs such as conditional statements and loops.
C. Better Performance: PL SQL engine processes multiple SQL statements simultaneously as a single block, thereby reducing network traffic.
D. Error Handling: PL/SQL handles errors or exceptions effectively during the execution of a PL/SQL program. Once an exception is caught, specific actions can be taken depending upon the type of the exception or it can be displayed to the user with a message.

What are PL/SQL Placeholders?
Placeholders are temporary storage area, those can be any of Variables, Constants and Records. Oracle defines placeholders to store data temporarily, which are used to manipulate data during the execution of a PL SQL block. Depending on the kind of data you want to store, you can define placeholders with a name and a data type. Few of the data types used to define placeholders are as under.
Number (n,m) , Char (n) , Varchar2 (n) , Date , Long , Long raw, Raw, Blob, Clob, Nclob, Bfile

What is a PL/SQL Block?
Each PL/SQL program consists of SQL and PL/SQL statements which from a PL/SQL block and a PL/SQL block consist three sections:
A. The Declaration section (optional).
B. The Execution section (mandatory).
C. The Exception or Error handling section (optional).

A. The Declaration section (optional):
The Declaration section of a PL/SQL Block starts with the reserved keyword DECLARE. This section is optional and is used to declare any placeholders. Placeholders (may be any of below type) which stores data temporarily.
1. Variables
2. Constants
3. Cursors
4. Records
5. Records those are used to manipulate data in the execution section.

B. The Execution section (mandatory):
The Execution section of a PL/SQL Block starts with the reserved keyword BEGIN and ends with END. This is a MUST section where the program logic is written to perform any task/s. The programmatic constructs like form the part of execution section.
1. Conditional statement
2. SQL statements
3. Loops

C. The Exception or Error handling section (optional):
The Exception section of a PL/SQL Block starts with the reserved keyword EXCEPTION. Any errors in the program can be handled in this section, so that the PL/SQL Blocks terminates gracefully. If the PL/SQL Block contains exceptions that cannot be handled, the Block terminates abruptly with errors.
1. Every statement in the above three sections must end with ; (semicolon).
2. PL/SQL blocks can be nested within other PL/SQL blocks.
3. Comments can be used to document code.
This is how a sample PL/SQL Block looks.

1. HOW to count and group together.

select distinct(column_1),count(*) from table_name group by column_1 ;

run it on the box..

the output is available in:

cd /opt/SUNWexplo/output

1. to see the memory size.
prtconf

2. to see the details
========================
prtdiag and prtdiag -v for
1. CPU status
2. Memory configuration
3. IO Cards
4. Environment status
a. system temperature.
b. Front panel status
c. Disk status
d. Fan status
e. Power suply
f.
========================

3. to see file i/o
iostat -xtnM 5

show from time to time 2-3 procent %w , (for /var and /export)

The Database server is a V440 with 16 Gb ram / 4 x 1,3Ghz CPU Only 1 scsi bus

yesterday 1528 study / 92539 object arrive

sk@sanjay01:/usr/sk] $ prtconf
System Configuration: Sun Microsystems sun4u
Memory size: 16384 Megabytes
System Peripherals (Software Nodes):

4.
/var/adm/messages

5.
/etc/vfstab

6.
format (as root user will scan all disk (san disk from san server)
See below.

================================
HOW TO CHECK O.S. LEVEL FILES.
================================

/var/adm/messages

/var/opt/SUNWscor/oracle_server/messages.log.oracle

/var/opt/SUNWscor/oracle_listener/messages.log.listener

/var/opt/SUNWscor/oracle_listener

/var/opt/SUNWscor/oracle_server

/data/logs/impax.log

/data/logs/oracle/bdump/alert_sk.log

==============================
prtdiag -v SAMPLE OUTPUT
==============================

prtdiag -v

[sk@sanjay01:/usr/sk] $ prtdiag -v
System Configuration: Sun Microsystems sun4u Sun Fire V490
System clock frequency: 150 MHz
Memory size: 8192 Megabytes

========================= CPUs ===============================================

Run E$ CPU CPU
Brd CPU MHz MB Impl. Mask
— —– —- —- ——- —-
A 0, 16 1500 32.0 US-IV+ 2.2
A 2, 18 1500 32.0 US-IV+ 2.2

========================= Memory Configuration ===============================

Logical Logical Logical
MC Bank Bank Bank DIMM Interleave Interleaved
Brd ID num size Status Size Factor with
— — —- —— ———– —— ———- ———–
A 0 0 1024MB no_status 512MB 8-way 0
A 0 1 1024MB no_status 512MB 8-way 0
A 0 2 1024MB no_status 512MB 8-way 0
A 0 3 1024MB no_status 512MB 8-way 0
A 2 0 1024MB no_status 512MB 8-way 0
A 2 1 1024MB no_status 512MB 8-way 0
A 2 2 1024MB no_status 512MB 8-way 0
A 2 3 1024MB no_status 512MB 8-way 0

========================= IO Cards =========================

Bus Max
IO Port Bus Freq Bus Dev,
Type ID Side Slot MHz Freq Func State Name Model
—- —- —- —- —- —- —- —– ——————————– ———————-
PCI 8 B 3 33 33 3,0 ok SUNW,XVR-100 SUNW,375-3290
PCI 8 B 5 33 33 5,0 ok scsi-pci1000,30.1000.10c0.8/disk+ LSI,1030
PCI 8 B 5 33 33 5,1 ok scsi-pci1000,30.1000.10c0.8/disk+ LSI,1030
PCI 8 A 0 66 66 1,0 ok SUNW,qlc-pci1077,2312.1077.149.2+
PCI 8 A 1 66 66 2,0 ok SUNW,qlc-pci1077,2312.1077.149.2+

========================= Environmental Status =========================

System Temperatures (Celsius):
——————————-
Device Temperature Status
—————————————
CPU0 48 OK
CPU2 50 OK
DBP0 23 OK

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

Front Status Panel:
——————-
Keyswitch position: NORMAL

System LED Status:

LOCATOR FAULT POWER
——- ——- ——-
[OFF] [OFF] [ ON]

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

Disk Status:
————
DISK 0: [NO_FAULT]
DISK 1: [NO_FAULT]

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

Fan Status:
———–

Fan Tray Fan RPM Status
———– —- —– ———-
FAN_TRAY_0 CPU0_FAN 5454 [NO_FAULT]
FAN_TRAY_0 CPU1_FAN 4054 [NO_FAULT]
FAN_TRAY_0 CPU2_FAN 3947 [NO_FAULT]
FAN_TRAY_1 IO0_FAN 4054 [NO_FAULT]
FAN_TRAY_1 IO1_FAN 4166 [NO_FAULT]

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

Power Supplies:
—————

Supply Status Fault Fan Fail Temp Fail
—— ———— ——– ——— ———
PS0 [NO_FAULT ] OFF OFF OFF
PS1 [NO_FAULT ] OFF OFF OFF

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

========================= HW Revisions =======================================

System PROM revisions:
———————-
OBP 4.18.1 2005/06/13 11:39

IO ASIC revisions:
——————
Port
Model ID Status Version
——– —- —— ——-
Schizo 8 ok 7
Schizo 9 ok 7
[sk@sanjay01:/usr/sk] $

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
PERFORMANCE RELATED QUERIES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Introduction to iostat , vmstat and netstat

This document is primarily written with reference to solaris performance monitoring and tuning but these tools are available in other unix variants also with slight syntax difference.

iostat , vmstat and netstat are three most commonly used tools for performance monitoring . These comes built in with the operating system and are easy to use .iostat stands for input output statistics and reports statistics for i/o devices such as disk drives . vmstat gives the statistics for virtual Memory and netstat gives the network statstics .

Following paragraphs describes these tools and their usage for performance monitoring.

Table of content :
1. Iostat
* Syntax
* example
* Result and Solutions

2. vmstat
* syntax
* example
* Result and Solutions

3. netstat
* syntax
* example
* Result and Solutions

Input Output statistics ( iostat )
iostat reports terminal and disk I/O activity and CPU utilization. The first line of output is for the time period since boot & each subsequent line is for the prior interval . Kernel maintains a number of counters to keep track of the values.

iostat’s activity class options default to tdc (terminal, disk, and CPU). If any other option/s are specified, this default is completely overridden i.e. iostat -d will report only statistics about the disks.

syntax:
Basic synctax is iostat interval count
option – let you specify the device for which information is needed like disk , cpu or terminal. (-d , -c , -t or -tdc ) . x options gives the extended statistics .

interval – is time period in seconds between two samples . iostat 4 will give data at each 4 seconds interval.

count – is the number of times the data is needed . iostat 4 5 will give data at 4 seconds interval 5 times

Example

====================
$ iostat -xtc 10 5
====================
extended disk statistics tty cpu
disk r/s w/s Kr/s Kw/s wait actv svc_t %w %b tin tout us sy wt id
sd0 2.6 3.0 20.7 22.7 0.1 0.2 59.2 6 19 0 84 3 85 11 0
sd1 4.2 1.0 33.5 8.0 0.0 0.2 47.2 2 23
sd2 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0
sd3 10.2 1.6 51.4 12.8 0.1 0.3 31.2 3 31

The fields have the following meanings:
disk name of the disk
r/s reads per second
w/s writes per second
Kr/s kilobytes read per second
Kw/s kilobytes written per second
wait average number of transactions waiting for service (Q length)
actv average number of transactions actively being serviced
(removed from the queue but not yet completed)
%w percent of time there are transactions waiting
for service (queue non-empty)
%b percent of time the disk is busy (transactions
in progress)
Results and Solutions
The values to look from the iostat output are:
* Reads/writes per second (r/s , w/s)
* Percentage busy (%b)
* Service time (svc_t)

If a disk shows consistently high reads/writes along with , the percentage busy (%b) of the disks is greater than 5 percent, and the average service time (svc_t) is greater than 30 milliseconds, then one of the following action needs to be taken

1.) Tune the application to use disk i/o more efficiently by modifying the disk queries and using available cache facilities of application servers .

2.) Spread the file system of the disk on to two or more disk using disk striping feature of volume manager /disksuite etc.

3.) Increase the system parameter values for inode cache , ufs_ninode , which is Number of inodes to be held in memory. Inodes are cached globally (for UFS), not on a per-file system basis

4.) Move the file system to another faster disk /controller or replace existing disk/controller to a faster one.

========================================
Virtual Memory Statistics ( vmstat )
========================================

vmstat – vmstat reports virtual memory statistics of process, virtual memory, disk, trap, and CPU activity.

On multicpu systems , vmstat averages the number of CPUs into the output. For per-process statistics .Without options, vmstat displays a one-line summary of the virtual memory activity since the system was booted.

syntax
Basic synctax is vmstat interval count

option – let you specify the type of information needed such as paging -p , cache -c ,.interrupt -i etc.

if no option is specified information about process , memory , paging , disk ,interrupts & cpu is displayed .

interval – is time period in seconds between two samples . vmstat 4 will give data at each 4 seconds interval.

count – is the number of times the data is needed . vmstat 4 5 will give data at 4 seconds interval 5 times.

Example
The following command displays a summary of what the system
is doing every five seconds.

example% vmstat 5

procs memory page disk faults cpu
r b w swap free re mf pi p fr de sr s0 s1 s2 s3 in sy cs us sy id
0 0 0 11456 4120 1 41 19 1 3 0 2 0 4 0 0 48 112 130 4 14 82
0 0 1 10132 4280 0 4 44 0 0 0 0 0 23 0 0 211 230 144 3 35 62
0 0 1 10132 4616 0 0 20 0 0 0 0 0 19 0 0 150 172 146 3 33 64
0 0 1 10132 5292 0 0 9 0 0 0 0 0 21 0 0 165 105 130 1 21 78

The fields of vmstat’s display are
procs
r in run queue
b blocked for resources I/O, paging etc.
w swapped
memory (in Kbytes)
swap – amount of swap space currently available
free – size of the free list

page ( in units per second).
re page reclaims – see -S option for how this
field is modified.
mf minor faults – see -S option for how this
field is modified.
pi kilobytes paged in
po kilobytes paged out
fr kilobytes freed
de anticipated short-term memory shortfall (Kbytes)
sr pages scanned by clock algorithm
disk ( operations per second )
There are slots for up to four disks,
labeled with a single letter and number.
The letter indicates the type of disk
(s = SCSI, i = IPI, etc).
The number is the logical unit number.

faults
in (non clock) device interrupts
sy system calls
cs CPU context switches

cpu – breakdown of percentage usage of CPU time.
On multiprocessors this is an a
average across all processors.
us user time
sy system time
id idle time
Results and Solution from iostat

A. CPU issues
Following columns has to be watched to determine if there is any cpu issue

1. Processes in the run queue (procs r)
2. User time (cpu us)
3. System time (cpu sy)
4. Idle time (cpu id)

procs cpu
r b w us sy id
0 0 0 4 14 82
0 0 1 3 35 62
0 0 1 3 33 64
0 0 1 1 21 78
Problem symptoms

A.) Number of processes in run queue
1.) If the number of processes in run queue (procs r) are consistently greater than the number of CPUs on the system it will slow down system as there are more processes then available CPUs .
2.) if this number is more than four times the number of available CPUs in the system then system is facing shortage of cpu power and will greatly slow down the processess on the system.
3.) If the idle time (cpu id) is consistently 0 and if the system time (cpu sy) is double the user time (cpu us) system is facing shortage of CPU resources.

Resolution
Resolution to these kind of issues involves tuning of application procedures to make efficient use of cpu and as a last resort increasing the cpu power or adding more cpu to the system.

B. Memory Issues
Memory bottlenecks are determined by the scan rate (sr) . The scan rate is the pages scanned by the clock algorithm per second. If the scan rate (sr) is continuously over 200 pages per second then there is a memory shortage.

Resolution
1. Tune the applications & servers to make efficient use of memory and cache.
2. Increase system memory .
3. Implement priority paging in s in pre solaris 8 versions by adding line “set priority paging=1? in
/etc/system. Remove this line if upgrading from Solaris 7 to 8 & retaining old /etc/system file.

========================================
Network Statistics (netstat)
========================================

netstat displays the contents of various network-related data structures in depending on the options selected.

Syntax

netstat
multiple options can be given at one time.

Options
-a – displays the state of all sockets.
-r – shows the system routing tables
-i – gives statistics on a per-interface basis.
-m – displays information from the network memory buffers. On Solaris, this shows statistics
for STREAMS
-p [proto] – retrieves statistics for the specified protocol
-s – shows per-protocol statistics. (some implementations allow -ss to remove fileds with a value of 0 (zero) from the display.)
-D – display the status of DHCP configured interfaces.
-n do not lookup hostnames, display only IP addresses.
-d (with -i) displays dropped packets per interface.
-I [interface] retrieve information about only the specified interface.
-v be verbose

interval – number for continuous display of statictics.

Example
$netstat -rn

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
——————– ——————– —– —– —— ———
192.168.1.0 192.168.1.11 U 1 1444 le0
224.0.0.0 192.168.1.11 U 1 0 le0
default 192.168.1.1 UG 1 68276
127.0.0.1 127.0.0.1 UH 1 10497 lo0
This shows the output on a Solaris machine who’s IP address is 192.168.1.11 with a default router at 192.168.1.1

Results and Solutions

A.) Network availability
The command as above is mostly useful in troubleshooting network accessibility issues . When outside network is not accessible from a machine check the following

1. if the default router ip address is correct
2. you can ping it from your machine.
3. If router address is incorrect it can be changed with route add command. See man route for more information.

route command examples
$route add default
$route add 192.0.2.32

If the router address is correct but still you can’t ping it there may be some network cable /hub/switch problem and you have to try and eliminate the faulty component .

B.) Network Response
$ netstat -i

Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue
lo0 8232 loopback localhost 77814 0 77814 0 0 0
hme0 1500 server1 server1 10658 3 48325 0 279257 0
This option is used to diagnose the network problems when the connectivity is there but it is slow in response .

Values to look at:

* Collisions (Collis)
* Output packets (Opkts)
* Input errors (Ierrs)
* Input packets (Ipkts)

The above values will give information to workout

i. Network collision rate as follows :

Network collision rate = Output collision counts / Output packets

Network-wide collision rate greater than 10 percent will indicate

* Overloaded network,
* Poorly configured network,
* Hardware problems.

ii. Input packet error rate as follows :

Input Packet Error Rate = Ierrs / Ipkts.

If the input error rate is high (over 0.25 percent), the host is dropping packets. Hub/switch cables etc needs to be checked for potential problems.

C. Network socket & TCP Connection state

Netstat gives important information about network socket and tcp state . This is very useful in
finding out the open , closed and waiting network tcp connection .

Network states returned by netstat are following

CLOSED —- Closed. The socket is not being used.
LISTEN —- Listening for incoming connections.
SYN_SENT —- Actively trying to establish connection.
SYN_RECEIVED —- Initial synchronization of the connection under way.
ESTABLISHED —- Connection has been established.
CLOSE_WAIT —- Remote shut down; waiting for the socket to close.
FIN_WAIT_1 —- Socket closed; shutting down connection.
CLOSING —- Closed,
then remote shutdown; awaiting acknowledgement.
LAST_ACK —- Remote shut down, then closed ;awaiting acknowledgement.
FIN_WAIT_2 —- Socket closed; waiting for shutdown from remote.
TIME_WAIT —- Wait after close for remote shutdown retransmission..
Example

———————–
#netstat -a
———————–

Local Address Remote Address Swind Send-Q Rwind Recv-Q State
*.* *.* 0 0 24576 0 IDLE
*.22 *.* 0 0 24576 0 LISTEN
*.22 *.* 0 0 24576 0 LISTEN
*.* *.* 0 0 24576 0 IDLE
*.32771 *.* 0 0 24576 0 LISTEN
*.4045 *.* 0 0 24576 0 LISTEN
*.25 *.* 0 0 24576 0 LISTEN
*.5987 *.* 0 0 24576 0 LISTEN
*.898 *.* 0 0 24576 0 LISTEN
*.32772 *.* 0 0 24576 0 LISTEN
*.32775 *.* 0 0 24576 0 LISTEN
*.32776 *.* 0 0 24576 0 LISTEN
*.* *.* 0 0 24576 0 IDLE
192.168.1.184.22 192.168.1.186.50457 41992 0 24616 0 ESTABLISHED
192.168.1.184.22 192.168.1.186.56806 38912 0 24616 0 ESTABLISHED
192.168.1.184.22 192.168.1.183.58672 18048 0 24616 0 ESTABLISHED
if you see a lots of connections in FIN_WAIT state tcp/ip parameters have to be tuned because the
connections are not being closed and they gets accumulating . After some time system may run out of
resource . TCP parameter can be tuned to define a time out so that connections can be released and used by new connection.

==============
CPU information
==============

[sk@sanjay01:/tmp] $ psrinfo
0 on-line since 04/20/2011 22:22:44
1 on-line since 04/20/2011 22:22:44
2 on-line since 04/20/2011 22:22:44
3 on-line since 04/20/2011 22:22:42
16 on-line since 04/20/2011 22:22:44
17 on-line since 04/20/2011 22:22:44
18 on-line since 04/20/2011 22:22:44
19 on-line since 04/20/2011 22:22:44
[sk@sanjay01:/tmp] $ psrinfo -p
4
[sk@sanjay01:/tmp] $
[sk@sanjay01:/tmp] $ psrinfo -pv
The UltraSPARC-IV physical processor has 2 virtual processors (0, 16)
The UltraSPARC-IV physical processor has 2 virtual processors (1, 17)
The UltraSPARC-IV physical processor has 2 virtual processors (2, 18)
The UltraSPARC-IV physical processor has 2 virtual processors (3, 19)

“[contact-form]

[sanjay@rwgdbwf01:/tmp] $ ps -ef| grep LOCAL=NO| sort +5
sanjay 21148     1  0   May 01 ?       1886:04 oracleSanjay (LOCAL=NO)
sanjay  4480     1  0   Apr 03 ?       145:05 oracleSanjay (LOCAL=NO)
sanjay 1815     1  0   Apr 03 ?       305:34 oracleSanjay (LOCAL=NO)
sanjay 4394     1  0   Apr 03 ?       413:50 oracleSanjay (LOCAL=NO)

2. Different options with ‘find’.
2.1 To find a file named “wherewere.you” under all sub-directories of /usr/oracle
find /usr/oracle -name wherewere.you -print

2.2 To remove all the files under /usr/oracle which end with .tmp
find /usr/oracle -name “*.tmp” -print -exec rm -f {} \;

2.3 To list all files under /usr/oracle which are older than a week.
find /usr/oracle -mtime +7 -print

2.4 To list all files under /usr/oracle which are modified within a week.
find /usr/oracle -mtime -7 -print

2.5 To compress all files which end with .dmp and are more than 2 MB.
find /usr/oracle -size +2097152c -name “*.dmp” -print -exec compress {} \;

3. Shared memory segment sizes
ipcs -mb
ipcs -b
ipcrm -m       <== Use for the Shared Memory entry
ipcrm -s       <== Use for the Semaphore entry

4. How to see the users logged in to the server and their IP address
who -T

5. How to convert the contents of a text file to

A. UPPERCASE
tr “[a-z]” “[A-Z]” < filename > newfilename

6. How to convert the contents of a text file to  lowercase.
tr “[A-Z]” “[a-z]” < filename > newfilename

7. How to see lines 100 to 120 of a file
head -120 filename | tail -20

8. How to see the versions of all Oracle products installed on the server.
$ORACLE_HOME/orainst/inspdver