Installation problems with Netbackup on Unix
|Article:TECH137603|||||Created: 2010-08-11|||||Updated: 2012-01-25|||||Article URL http://www.symantec.com/docs/TECH137603|
When performing a new installation of Netbackup on Unix it is possible to encounter numerous issues related to the shell environment used when performing the installation. For example, there may be issues with tar failures during the extract phase, or there may be issues with the OS ld related to loading shared libraries for the Netbackup executables.
Start ASA Server Failed! error code: 137
/usr/openv/db//bin/dbspawn -f "/usr/openv/db//bin/NB_dbsrv" @"/usr/openv/var/global/server.conf" @"/usr/openv/var/global/databases.conf"
ld.so.1: dbspawn: fatal: libdbtool9_r.so: open failed: No such file or directoryKilled
Could not start server instance. Please check error.
Installation has failed!
The VxDBMS server install failed. Rerun
/usr/openv/netbackup/bin/install_bp when the problem has been resolved.
If the shell used has non-standard values in the environment, the installation may find non-standard versions of tar, sed, or other OS utilities than expected. As well, the Netbackup executables may find shared libraries in directories than intended. For example, the PATH environment variable may find a version of GNU tar that has different responses than the install script expects to receive, or the LD_LIBRARY_PATH may have library directories prior to the Netbackup library directories that have libraries with identical names, or the Netbackup library directories may be missing completely.
To create a minimal environment, run the following commands, assuing the shell is sh compatible:
# env - ksh
# PATH=/usr/bin; export PATH
It may be necessary to completely remove all traces of the previous installation attempts in case the system was left in an inconsistent state. Once that is complete, attempt the installation again with the minimal shell.
Article URL http://www.symantec.com/docs/TECH137603