Possible cause: If you have missed to backup the database before upgrading the server to OES 11 SP3, postgresql 9.x fails to start with the following error:
LOG: skipping missing configuration file "/var/opt/novell/arkmanager/data/postgresql.auto.conf" LOG: unrecognized configuration parameter "max_fsm_pages" in file "/var/opt/novell/arkmanager/data/postgresql.conf" line 121 FATAL: configuration file "/var/opt/novell/arkmanager/data/postgresql.conf" contains errors
Action: To recover the database, do the following:
Install the old version of postgresql 8.3 and postgresql server 8.3, which is available as part of the SLES 11 SP4.
Start the postgresql 8.3 using the command su arkuser -c "/usr/lib/postgresql83/bin/postmaster -D /var/opt/novell/arkmanager/data -h 127.0.0.1 -p 5432 -i &".
Backup the database by following the steps in Section 5.3.1, Before You Upgrade.
Stop the postgresql.
Configure and restore the database by following the steps in Section 5.3.2, Post-Upgrade.
Possible cause: The username, password or database port number is invalid.
Action: Ensure that the PostgreSQL credentials are valid.
Possible cause: Linux operating system is case sensitive. Archive server fails to start if the archive path is not in appropriate case.
Action: Ensure the volume name is in uppercase. For example, ARKVOL:\archive_directory
Possible cause: The migration tool fails randomly to migrate Archive and Version Services to OES 11 SP3 server.
Action: To migrate Archive and Version Services, run the sys:\system\arkmig.ncf file on your NetWare server, then run the migration tool on the OES 11 SP3 server. Archive and Version service migrates successfully.
Possible cause 1: ArkConfig.xml file name is case sensitive. Migration fails if the file name is not appropriate.
Possible cause 2: The spelling of the ArkConfig.xml file is incorrect.
Action: The file name is case-sensitive. Ensure you have specified the file name as ArkConfig.xml.