08-07-2010
ORACLE Database running slow on AIX ( nmon / topas )
Hello,
How can I know if ORACLE Database is running slow due to Memory or due to processing power ?
I have only Oracle Database running on a P4 with 4GB RAM.
Could anyone suggest any tools which can help me determine exactly if it is memory issue or processor issue.
8 More Discussions You Might Find Interesting
1. AIX
hi,
how can i diplay:
- the ammount RAM used /free
- ammount of ram used from a pid or prozess
we have the problem, that malloc is returing a NULL pointer errno = 12 ( not enough space).
but i think there is still ram free.
nmon : shows all memory used ?
Memory Use Physical Virtual... (7 Replies)
Discussion started by: Lazzar
7 Replies
2. Filesystems, Disks and Memory
Hi,
I am running an oracle db 9.2.0.5.0 on ibm p5 550 aix 5.3 with 10g ram, 10G swap space 3 database instances each SGA about 500Meg.
I am getting the following error in my alert log file from time to time:
skgpspawn failed:category = 27142, depinfo = 11, op = fork, loc = skgpspawn3
... (0 Replies)
Discussion started by: hawkerpacific
0 Replies
3. AIX
good morning
what is the better solution to examen a P570 ?
because i use topas and nmon, and the results are totally different !!!
with nmon, i have 80% free cpu, and with nmon, i have 90% of used cpu !!!!!!
i take a shot with an intervall of 10s during 10 mn.
thank you (0 Replies)
Discussion started by: pascalbout
0 Replies
4. AIX
Is there a 'top' command equivalent in AIX 4.2 ?
I already checked and I do not see the following ones anywhere:
top
nmon
topas (1 Reply)
Discussion started by: Browser_ice
1 Replies
5. Solaris
what is the command to see which database ie..oracle in running on solaris 10 (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
6. Shell Programming and Scripting
Hi Guys,
Need you help in one point!
I am working on one shell script which takes following steps :
1. Taking one query result from oracle database
2. Exporting that result to Xls file
3. Mailing that file to my own mail ID
Now, I want to give a threshold limit to one of the column... (0 Replies)
Discussion started by: Agupte
0 Replies
7. AIX
Hello,
Please help me with a script with which I can check long running processes on the database server and the os is AIX.
Best regards,
Vishal (5 Replies)
Discussion started by: Vishal_dba
5 Replies
8. AIX
Hello,
All the commands on AIX are running very slow.
Below is few stats but I didn't find any issue in cpu or memory reosurces
vmstat
System configuration: lcpu=4 mem=6144MB ent=1.00
kthr memory page faults cpu
----- -----------... (2 Replies)
Discussion started by: Vishal_dba
2 Replies
LEARN ABOUT DEBIAN
bup-margin
bup-margin(1) General Commands Manual bup-margin(1)
NAME
bup-margin - figure out your deduplication safety margin
SYNOPSIS
bup margin [options...]
DESCRIPTION
bup margin iterates through all objects in your bup repository, calculating the largest number of prefix bits shared between any two
entries. This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.
For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45. That means a 46-bit
hash would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
its first 46 bits.
The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects. Since SHA-1 hashes have 160 bits,
that leaves 115 bits of margin. Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
with far fewer objects.
If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see if
you're getting dangerously close to 160 bits.
OPTIONS
--predict
Guess the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
from the guess. This is potentially useful for tuning an interpolation search algorithm.
--ignore-midx
don't use .midx files, use only .idx files. This is only really useful when used with --predict.
EXAMPLE
$ bup margin
Reading indexes: 100.00% (1612581/1612581), done.
40
40 matching prefix bits
1.94 bits per doubling
120 bits (61.86 doublings) remaining
4.19338e+18 times larger is possible
Everyone on earth could have 625878182 data sets
like yours, all in one repository, and we would
expect 1 object collision.
$ bup margin --predict
PackIdxList: using 1 index.
Reading indexes: 100.00% (1612581/1612581), done.
915 of 1612581 (0.057%)
SEE ALSO
bup-midx(1), bup-save(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-margin(1)