pread is a read of a file... 341 should be the file descriptor. If you have the proc tools installed (/usr/proc/bin), you might be able to find more information about this file by using pfiles. Also, pstack can give you the call stack for the process, and might give you a good idea of exactly...
Your values for shmmax and shmseg are already set to the maximum allowed value. The value for shmmni (number of shared memory identifiers) can be set as high as 2147483648 (2GB).
The main effect of setting these values too high is that you are using more kernel memory than necessary. If you...
This should be controlled by the ulimit on virtual memory. If it is set to "unlimited", a single process could potentially take over your whole box.
Here's an old list that I've used in the past... Insure++ is the only tool I've used on AIX.
http://www.cs.colorado.edu/homes/zorn/public_html/MallocDebug.html
If you are using different terminal types, you might be able to use the value of $TERM to determine where you are coming from. Otherwise, you are probably just doing an "rexec" from your PC, so there's no way (I know of) for the server to know what software is sending that command.
It looks like it is intending to process a list of files that is contained in "sourcename.txt". However, the code above will not do that. The line:
[code]for f in sourcename.txt[code]
will assign the value "sourcename.txt" to the variable "f", and only process...
If you are adding a volume group, don't you want to be using vgcreate? You cannot modify the lmvtab file directly, it must be done with the vg commands. You can check current definitions in lvmtab using the strings command - what does that show? Is c2t0d0 already in there?
Another suggestion...
Workshop uses tooltalk to send display information to your PC. Usually this message means your PC already has the tooltalk port in use.
Check on the server for a process called "ttsession". If you see one of these processes that is referencing your DISPLAY, you may be able to kill...
The "s" or "S" both indicate the set-uid or set-gid bit is on. Lower case means the file is executable (or directory is searchable), while upper case means it is not executable (or searchable).
This is most likely an oracle client configuration issue rather than AIX...
- Make sure you can successfully ping the <hostname> above.
- Make sure your ORACLE_HOME and PATH environment variables is set correctly.
- Make sure your tnsnames.ora and sqlnet.ora entries is correct.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.