HP-UX SysFaultMgmt (System Fault Management) (SFM) Release Notes (766969-001, March 2014) (Edition: 2)

7 Known problems, workaround, and limitations
Following are the compilation of various issues from multiple releases.
• Problem:
Upgrade of SysFaultMgmt (System Fault Management) (SFM) and ProviderSvcsBase
(PSB) products, from prior to September 2012 release to September 2012 web release and
to later release, may fail due to disk full issues, caused by Postgres data backup file.
Description:
To upgrade the earlier SysFaultMgmt (System Fault Management) (SFM) and
ProviderSvcsBase (PSB) versions released before September 2012, pre-install scripts take
backup for diagnostic database. The size of these database backup files can vary and are
large in size, depending upon the size of the database on the systems.
This file gets created in /var. Installation of the products may fail due to lack of disk space
in /var.
Workaround:
To upgrade the products released before September 2012, it is advisable to empty the
diagnostic database before starting the product upgrade.
To empty diagnostic database, refer the following steps:
1. Note down the disk space under database directory.
◦ On IA: du -sk /var/opt/psb/db/pgsql/
◦ On PA: du –sk /var/opt/sfmdb/pgsql/
2. Gracefully shut down postmaster using the following command.
◦ On IA: /sbin/init.d/psbdb stop
◦ On PA: /sbin/init.d/sfmdb stop
3. Move or back up pgsql directory to a newly identified or user desired location.
◦ On IA: mv –if /var/opt/psb/db/pgsql <User desired location>
◦ On PA: mv –if /var/opt/sfmdb/pgsql <User desired location>
4. After moving database directory, note down the disk space under database directory.
◦ On IA: du -sk /var/opt/psb/db/pgsql/
◦ On PA: du –sk /var/opt/sfmdb/pgsql/
5. Start the postmaster which initializes the postgres database.
◦ On IA: /sbin/init.d/psbdb start
◦ On PA: /sbin/init.d/sfmdb start
6. Proceed with upgrade activity of the product.
22 Known problems, workaround, and limitations