Aix allows extending a filesystem on the fly. This feature has been around for over 15 years. I first used it with AIX 3.1. What an AIX system is intalled, it can be set up with minimal requirements and then each filesystem can be grown on the fly as needed. In fact the installer has an option to grow automatically any file system as needed during the install of a new package.
However, there is always a time when the physical limits of the available storage are reached. In that case, it is needed to either add a physical disk to the machine, or add a LUN from the SAN, or add a virtual disk to the LPAR. Next I show what to do once the additional physical storage has been added:
- First lets make sure that the new storage is recognized:
lspv will list the recognized storage units. If the new storage is regocnized, it will be visible on a line like:
hdiskX none none
“X” is a placeholder for a number, like “hdisk3.” If the new storage isn’t visible yet, then we need to tell AIX to look for it with:
cfgmgr this command should take only a few seconds to rescan the system. Once it returns list the physical volumes again, and you should see the new volume.
- Now we need to decide which logical volume to extend. The list of logical volumes is shown by
lsvg. On simple installs, all you will see is
rootvg. To extend
rootvg all you have to do is:
extendvg rootvg hdiskX
- Finally we can grow the file system that we needed to grow either with
smitty or the direct command
chfs. For example:
chfs -a size=+1048576 /opt
The IBM documentation has good information on how to do the upgrade in general, and how to go through the preparation steps. Unfortunately the information about XML Extender is sparse, and all you get is
ADM4104E One or more databases are enabled for XML Extender. You must remove the XML Extender functionality from the instance and databases before upgrading. Please refer to the DB2 Information Center for details on the steps to upgrade XML Extender including how to disable XML Extender in databases.
This is misleading at best, since chances are that the XML extender was installed with the default DB2 install and never used, which was the case for the first upgrade I had to do. You get this error message regardless of having any column, table, database, or instance using the XML Extender. However, to find out how to get rid of the XML Extender is quite a challenge.
Follow the instructions here until step 6: Upgrading a DB2 server with XML Extender to DB2 Version 9.7
Once you’re at step 6, here are the details, assuming you have installed DB 9.5 to the default path.
- First, check that XML Extender is installed:
db2ls -a -q -b /opt/ibm/db2/V9.5
- Then proceed to uninstall XML extender:
./db2_deinstall -F XML_EXTENDER -b /opt/ibm/db2/V9.5
This completes step 6 and you can proceed with the following step – step 7 – in the documentation. Make sure you use the correct
Even after fixing everything the upgrade tool complains about, you may still get odd error messages, that claim that you have not corrected the problems. That is some odd behavior of the error message reporting in DB2. For example, the front end was still complaining about VIEWs even though there weren’t any, and the back-end was still complaining about XML Extender even after it was uninstalled. Thus, if you are sure that all the issues are in fact fixed, you can go ahead and force the upgrade with the “-F” option.