Installation scenarios of Postgres 8.4.8

Failures during the database restore operation
As like the database backup operation, sometimes the database restore operation may also fail due to
some reasons like connection problems etc. The successful upgrade installation with a failed restore
operation may result in unsuccessful migration of any user specific data from the previous versions of
postgres.
However, the case of restore failure does not mean the loss of end-user data. It only means that the
data is available from the previous version however the database with the newer version of postgres
8.4.8 cannot be updated with the old data records automatically. Therefore the data will not be visible
through the general queries to display data. Some manual steps are required to perform the restore
operation to update the database tables.
Failure during the database restore operation due to unknown scenarios
The end-user is informed about the restore operation failure by using the following WARNING message.
WARNING "Failed to restore the data from <DB_DATA_PATH*>/db_backup.sql.<pidswinstall>. Please
refer <INSTALL_LOG> for error details."
This warning message should be used as information that the end-user is expected to restore the data
in the newer version using the following manual steps.
The end-user may then use the following steps to restore the data in the newer version:
1. Look for the file
<DB_DATA_PATH*>/db_backup.sql.<pidswinstall>.Z
(NOTE: The backup file is often compressed in order to save the user space.)
2. Uncompress the file
<DB_DATA_PATH*>/db_backup.sql.<pidswinstall>.Z
using the following command
/usr/bin/uncompress <DB_DATA_PATH*>/db_backup.sql.<pidswinstall>.Z
(NOTE: steps 1 and 2 can be ignored if the compressed file is not found).
3. Start the postmaster (if not already running) using the following command
For IA
/sbin/init.d/psbdb start
For PA
/sbin/init.d/sfmdb start
4. Move the database into trust mode and reload it by using the following command
For IA
9