topic Re: application's poor performence in Operating System - HP-UX

application's poor performence

Nikhil Mistry — Tue, 26 Sep 2000 16:43:33 GMT

I have Oracle Application 10.7(database 7.3.4)running on HP-UX 10.20.
recently application performence have gone to bottom.any suggestion how to free up unneccessary diskspace? or any way to bring server performence upto normal level?

Re: application's poor performence

CHRIS_ANORUO — Tue, 26 Sep 2000 17:03:00 GMT

Use this command to find out oracle log files for deleting.
find / -name '*.log' -print > /tmp/filename

What is your swap space like, can you send a copy of swapinfo -tm?
Check if swapmem_on=1; nbuf =0 and bufpages=0 in kernel configuration thro SAM

Re: application's poor performence

Nikhil Mistry — Tue, 26 Sep 2000 17:14:37 GMT

Hi Chris,
here is outcome
hp-k260:/
#find / -name '*.log' -print > /tmp/filename
(cursor is blinking here)

when u reply please give detail info. of all command since i am not a sy.admin and not familiar with many unix commands.thanks again.
Nikhil

Re: application's poor performence

Nikhil Mistry — Tue, 26 Sep 2000 17:22:38 GMT

Hi Chris,
here is swapinfo -tm

#swapinfo -tm
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1000 0 1000 0% 0 - 1 /dev/vg00/lvol2
reserve - 452 -452
total 1000 452 548 45% - 0 -
hp-k260:/

Re: application's poor performence

CHRIS_ANORUO — Tue, 26 Sep 2000 17:55:39 GMT

Hi Nikhil,
The swap is not 100%, but if you set swapmem_on=1 you will get memory values from swapinfo -tm. What this does is to give you 75% of Physical memory as pseudo memory. What is your total Physical memory? (Use dmesg or cat /var/adm/syslog/syslog.log|grep Phy).
Check the output of the /tmp/filename, select the oracle log files in the /tmp/filename. You can specify that these logs be deleted with this command(find /oraclefilesystems -name '*.log' -exec rm {} \;. Pls back them up before removing them.

Re: application's poor performence

Irine Gibilisco — Tue, 26 Sep 2000 17:58:37 GMT

NIkhil,
When you say 'recently', I assume that previously the performance was good. If that is the case, what has changed. Have you added new screens or reports. Also find out if new tables or indexes were recently added. Also check if any talbles or indexes were moved. If so, identify which ones, and have your DBAs run an analisys on their database queries. Performance of Oracle database is very data-dependant. If your problem is due to i/o contention (where both data and index are on the same disk, thus competing for I/O), one of these should be relocated to another disk. It can also be, that a new application function was added that results in sequential access to a table, and it is slowing everyone down when it is in heavy use. In that case, an Index would resolve the problem. Talk to your DBAs.
If there were no changes to data or applications, and you suddenly experience extreme slow-down, check to make sure one of your Oracle disks is not dying. For that, examine /usr/adm/syslog/syslog.log file to make sure there are no I/O errors.

Re: application's poor performence

Nikhil Mistry — Tue, 26 Sep 2000 18:53:32 GMT

Hi Chris,Hi Irene,
here is the memory result please let me know what to do.

#dmesg

Sep 26 15:49
vuseg=2c75000
inet_clts:ok inet_cots:ok 8 ccio
10 ccio
10/0 c720
10/0.6 tgt
10/0.6.0 sdisk
10/0.7 tgt
10/0.7.0 sctl
10/4 bc
10/4/0 mux2
10/4/4 scsi1
10/4/4.5 target
10/4/4.5.0 tape2
10/4/4.6 target
10/4/4.6.0 tape2
10/8 c720
10/8.0 tgt
10/8.0.0 sdisk
10/8.7 tgt
10/8.7.0 sctl
10/12 bus_adapter
10/12/5 c720
10/12/5.2 tgt
10/12/5.2.0 sdisk
10/12/5.7 tgt
10/12/5.7.0 sctl
10/12/6 lan2
10/12/0 CentIf
ps2_readbyte_timeout: no byte after 500 uSec
ps2_readbyte_timeout: no byte after 500 uSec
10/12/7 ps2
32 processor
49 memory
Networking memory for fragment reassembly is restricted to 48222208 bytes
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 2048000
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x6000; start = 551775, size = 524289
Starting the STREAMS daemons.
9245XB HP-UX (B.10.20) #1: Sun Jun 9 06:31:19 PDT 1996

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 524288 Kbytes, lockable: 418256 Kbytes, available: 447188 Kbytes

Using 1008 buffers containing 7968 Kbytes of memory.