Sponsored Content
Operating Systems AIX ORACLE Database running slow on AIX ( nmon / topas ) Post 302446456 by zxmaus on Wednesday 18th of August 2010 08:09:43 PM
Old 08-18-2010
Hi,

please run
Code:
vmstat -I 2 20 (uppercase i)

and YES you definitely need more memory ... you have only about 16 MB memory for your DB to work with, and I assume your freelist goes to 0 when you do queries - what equals to a halt on the system. Set your minperm to 3-5%, your maxperm to 90%. And add memory ! If you need more cpus depends on if your DB has more than 2 parallel queries at any given time - and what your queries are doing (like full tablescans).

Kind regards
zxmaus
 

8 More Discussions You Might Find Interesting

1. AIX

Memory usage statistic? (topas, nmon)

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

skgpspawn failed running oracle db 9.2.0.5.0 on aix 5.3

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

nmon vs topas

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

Top command in AIX 4.2 (no topas, no nmon, no top)?

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

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

Running script automatically when threshold limit met in one of the field in oracle database

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

Need to check long running processes on the database server and the os is 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

AIX server running very slow

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
LWRESD(8)							       BIND9								 LWRESD(8)

NAME
lwresd - lightweight resolver daemon SYNOPSIS
lwresd [-c config-file] [-C config-file] [-d debug-level] [-f] [-g] [-i pid-file] [-m flag] [-n #cpus] [-P port] [-p port] [-s] [-t directory] [-u user] [-v] [-4] [-6] DESCRIPTION
lwresd is the daemon providing name lookup services to clients that use the BIND 9 lightweight resolver library. It is essentially a stripped-down, caching-only name server that answers queries using the BIND 9 lightweight resolver protocol rather than the DNS protocol. lwresd listens for resolver queries on a UDP port on the IPv4 loopback interface, 127.0.0.1. This means that lwresd can only be used by processes running on the local machine. By default UDP port number 921 is used for lightweight resolver requests and responses. Incoming lightweight resolver requests are decoded by the server which then resolves them using the DNS protocol. When the DNS lookup completes, lwresd encodes the answers in the lightweight resolver format and returns them to the client that made the request. If /etc/resolv.conf contains any nameserver entries, lwresd sends recursive DNS queries to those servers. This is similar to the use of forwarders in a caching name server. If no nameserver entries are present, or if forwarding fails, lwresd resolves the queries autonomously starting at the root name servers, using a built-in list of root server hints. OPTIONS
-4 Use IPv4 only even if the host machine is capable of IPv6. -4 and -6 are mutually exclusive. -6 Use IPv6 only even if the host machine is capable of IPv4. -4 and -6 are mutually exclusive. -c config-file Use config-file as the configuration file instead of the default, /etc/lwresd.conf. -c can not be used with -C. -C config-file Use config-file as the configuration file instead of the default, /etc/resolv.conf. -C can not be used with -c. -d debug-level Set the daemon's debug level to debug-level. Debugging traces from lwresd become more verbose as the debug level increases. -f Run the server in the foreground (i.e. do not daemonize). -g Run the server in the foreground and force all logging to stderr. -i pid-file Use pid-file as the PID file instead of the default, /var/run/lwresd/lwresd.pid. -m flag Turn on memory usage debugging flags. Possible flags are usage, trace, record, size, and mctx. These correspond to the ISC_MEM_DEBUGXXXX flags described in <isc/mem.h>. -n #cpus Create #cpus worker threads to take advantage of multiple CPUs. If not specified, lwresd will try to determine the number of CPUs present and create one thread per CPU. If it is unable to determine the number of CPUs, a single worker thread will be created. -P port Listen for lightweight resolver queries on port port. If not specified, the default is port 921. -p port Send DNS lookups to port port. If not specified, the default is port 53. This provides a way of testing the lightweight resolver daemon with a name server that listens for queries on a non-standard port number. -s Write memory usage statistics to stdout on exit. Note: This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release. -t directory Chroot to directory after processing the command line arguments, but before reading the configuration file. Warning: This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance security on most systems; the way chroot(2) is defined allows a process with root privileges to escape a chroot jail. -u user Setuid to user after completing privileged operations, such as creating sockets that listen on privileged ports. -v Report the version number and exit. FILES
/etc/resolv.conf The default configuration file. /var/run/lwresd.pid The default process-id file. SEE ALSO
named(8), lwres(3), resolver(5). AUTHOR
Internet Systems Consortium COPYRIGHT
Copyright (C) 2004, 2005, 2007, 2008 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2000, 2001 Internet Software Consortium. BIND9 June 30, 2000 LWRESD(8)
All times are GMT -4. The time now is 11:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy