08-27-2010
AiX Memory upgrade
Hi,
I have just upgraded one of our AiX box's memory but my partition has not been able to use this extra 2gb - It seems to have a maximum memory size of around 6gb.
The system can see 8gb but I do not seem to be able to allocate this to the partition.
Any help would be gratefully received.
Regards
Adam
---------- Post updated at 02:27 PM ---------- Previous update was at 02:24 PM ----------
FYI -
I am running aix 5.3 on a P520 machine.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I would like to upgrade the memory in my Sun Blade 150 workstation. In reading through Sun's Blade 150 DIMM Installation Guide, it indicates that the memory must be "certified by Sun for the Sun Blade 150 system."
Does anyone know if any SDRAM, PC133 • CL=2 • Unbuffered • ECC • 133MHz • 3.3V ... (2 Replies)
Discussion started by: here2learn
2 Replies
2. SCO
HI,
I need to add more memory to a system running SCO Unix Open Server 5.0.7.
Will SCO automatically detect and start using the newly added memory module?
Do I need to reconfigure the system before it can take advantage of the
newly installed memory?
Thank you! (2 Replies)
Discussion started by: forumuser7
2 Replies
3. UNIX for Dummies Questions & Answers
Hello everyone, I have to do a ML upgrade on AIX 5.2 from 01 to 09
this is the first time iam going to do it.
are there any command i have to keep in mind??
thanks! (1 Reply)
Discussion started by: karthikosu
1 Replies
4. UNIX for Dummies Questions & Answers
Does anyone know any gotcha's on upgrading AIX from 5.1 to 5.3? Any interim steps on needs to do or ??? (3 Replies)
Discussion started by: capeme
3 Replies
5. AIX
I have an IBM P520 that I need to upgrade from 5.2 to 5.3. My background in Unix is from 15 years ago so I don't remember much. IBM documentation is hard to find. Any help would be appreciated. (1 Reply)
Discussion started by: bashtonmcse
1 Replies
6. Solaris
Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies
7. AIX
Hello Folks,
i am facing some weired issues.
case is like this :-
initially i was on AIX 5.3
i have installed filesets related to my application and those were in APPLY state.(COMMIT is set as NO)
Then i have taken lslpp -l| grep -i <apps name>
in that i confirmed whether the filesets are... (1 Reply)
Discussion started by: harsh_mulay
1 Replies
8. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
9. AIX
i upgrade aix ml 5.3.2.1 to 5.3.2.2 but when running commnd #oslevel -r
shows out put, again 5.3.2.1-- where should i chek???
2-can any one tell me when mknfs command run which files get updated?? (2 Replies)
Discussion started by: nayyer
2 Replies
LEARN ABOUT DEBIAN
pg_upgradecluster
PG_UPGRADECLUSTER(8) Debian PostgreSQL infrastructure PG_UPGRADECLUSTER(8)
NAME
pg_upgradecluster - upgrade an existing PostgreSQL cluster to a new major version.
SYNOPSIS
pg_upgradecluster [-v newversion] version name [newdatadir]
DESCRIPTION
pg_upgradecluster upgrades an existing PostgreSQL server cluster (i. e. a collection of databases served by a postmaster instance) to a new
version specified by newversion (default: latest available version). The configuration files of the old version are copied to the new
cluster.
The cluster of the old version will be configured to use a previously unused port since the upgraded one will use the original port. The
old cluster is not automatically removed. After upgrading, please verify that the new cluster indeed works as expected; if so, you should
remove the old cluster with pg_dropcluster(8). Please note that the old cluster is set to "manual" startup mode, in order to avoid
inadvertently changing it; this means that it will not be started automatically on system boot, and you have to use pg_ctlcluster(8) to
start/stop it. See section "STARTUP CONTROL" in pg_createcluster(8) for details.
The newdatadir argument can be used to specify a non-default data directory of the upgraded cluster. It is passed to pg_createcluster. If
not specified, this defaults to /var/lib/postgresql/version/name.
Please note that this program cannot upgrade clusters which use tablespaces. If you use those, you have to upgrade manually.
OPTIONS
-v newversion
Set the version to upgrade to (default: latest available).
--logfile filel
Set a custom log file path for the upgraded database cluster.
--locale=locale
Set the default locale for the upgraded database cluster. If this option is not specified, the locale is inherited from the old
cluster.
--lc-collate=locale
--lc-ctype=locale
--lc-messages=locale
--lc-monetary=locale
--lc-numeric=locale
--lc-time=locale
Like --locale, but only sets the locale in the specified category.
HOOK SCRIPTS
Some PostgreSQL extensions like PostGIS need metadata in auxiliary tables which must not be upgraded from the old version, but rather
initialized for the new version before copying the table data. For this purpose, extensions (as well as administrators, of course) can drop
upgrade hook scripts into /etc/postgresql-common/pg_upgradecluster.d/. Script file names must consist entirely of upper and lower case
letters, digits, underscores, and hyphens; in particular, dots (i. e. file extensions) are not allowed.
Scripts in that directory will be called with the following arguments:
<old version> <cluster name> <new version> <phase>
Phases:
init
A virgin cluster of version new version has been created, i. e. this new cluster will already have template1, but no user databases.
Please note that you should not create tables in this phase, since they will be overwritten by the dump/restore operation.
finish
All data from the old version cluster has been dumped/reloaded into the new one. The old cluster still exists.
The scripts are called as the user who owns the database.
SEE ALSO
pg_createcluster(8), pg_dropcluster(8), pg_lsclusters(1), pg_wrapper(1)
AUTHOR
Martin Pitt <mpitt@debian.org>
Debian 2012-10-08 PG_UPGRADECLUSTER(8)