I would not worry about real memory reporting 99% with vmstat, nmon or such like, as AIX keeps real memory even when a process ends just in case the same data is needed later. You need to keep an eye on paging to see if you are really running out of real memory.
Code:
lsps -a
You also need to consider if your DB has a real-memory requirement. If you exceed the real memory, you system will start to page. Check vmstat for the pi & po columns to see read and writes to/from disks for paging.
If your DB requires (or is set for) large real memory, then that can be a problem too. This is an allocation that is not eligible for paging. if you run multiple instances, remember that they will each want their own allocation and that you may be exceeding the machine limits there. The settings in the DB startup parameters is not defining how big a machine you have, it's how much you are allocating to that instance - a mistake we have seen here.
Hi all,
I've got a question about an OS upgrade.
I'm planning to do a upgrade from AIX UNIX 4.3.2 to 4.3.3 in a few weeks.
I haven't got that much information.
Could someone give me some general tips or hints, things I should think of before? Things I should know, or general errors.
I know... (9 Replies)
Hi,
Am jus trying to find the Total RAM Size of a AIX m/c (in MB)..svmon works perfectly for a superuser...But i want to achive this as a normal user...Please help me out with correct command..
Best Regards,
Muthukumaran.M (3 Replies)
Hi All,
We are in the processing of upgrading our AIX server OS from 5.2.0.0 to 6.1. And we have a set of highly critical running C applications in AIX box. I have a question like whether this upgradation of OS will affect any C code compilation and C runtime enviornment...
how does AIX 6.1... (1 Reply)
Hi,
I am having 2 Hard disk one for os and another for data,I would like to know for Upgrading AIX 5.3 to 6.1,wheather I have to varry off datavg while upgrading, or any other files needs to be backup.
Please suggest
Regards,
Manoj (1 Reply)
We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC.
Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers.
My understandin going thru the manual ... (3 Replies)
Hey guys,
since AIX 5.3 reaches EOS on april 2012, I really need to update my systems asap.
Any experience on upgrading directly to 7.1, with sap/db2/oracle?
could do fresh installs and import my sap/db vgs, but this would be a lot of work
cheers Funksen (4 Replies)
Hello,
I am trying to update Samba on my AIX 7.1 system as there is an issues with it, the smbd process coredumps and I have had no luck figuring it out why.
My approach is to try to re-install a newer samba and I have found the latest 3.x package for samba in ppc.rpm format at perlz.org
... (6 Replies)
Hi All,
I was trying to know more about RAM disk concept in AIX. I found something on IBM site.
I was able to create and use/delete RAM disk as per IBM instructions.
But as you guys know, this RAM disk is a temporary storage. (*when ever we reboot the AIX LPAR, content/RAM disk will be... (4 Replies)
Hi all,
I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 Replies
LEARN ABOUT DEBIAN
kiokudb::linker
KiokuDB::Linker(3pm) User Contributed Perl Documentation KiokuDB::Linker(3pm)NAME
KiokuDB::Linker - Relinks live objects from storage entries
SYNOPSIS
# mostly internal
DESCRIPTION
The linker reconnects entry data, recreating the connected object graph in memory.
The linkage process starts with an ID (or several IDs) to be loaded passed to the "get_or_load_objects" method.
This ID will first be searched for in the live object set (KiokuDB::LiveObjects). If the object is already live, then it will be returned
as is.
If the object is not live, then the corresponding entry is fetched from the backend, and expanded into an actual instance.
Expansion consults the KiokuDB::TypeMap using KiokuDB::TypeMap::Resolver, to find the correct typemap entry (see "COLLAPSING STRATEGIES" in
KiokuDB::Collapser and KiokuDB::TypeMap), and that is used for the actual expansion.
Most of the grunt work is delegated by the entries back to the linker using the "inflate_data" method, which handles circular structures,
retrying of tied structures, etc.
Inflated objects are registered with KiokuDB::LiveObjects, and get inserted into the current live object scope
(KiokuDB::LiveObjects::Scope). The scope's job is to maintain a reference count of at least 1 for any loaded object, until it is destroyed
itself. This ensures that weak references are not destroyed prematurely, but allows their use in order to avoid memory leaks.
perl v5.12.4 2010-10-11 KiokuDB::Linker(3pm)