Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Studio 12.3 Installation Guide Oracle Solaris Studio 12.3 Information Library |
2. Installing the Oracle Solaris Studio 12.3 Software
3. Uninstalling the Oracle Solaris Studio 12.3 Software
GUI Installer Will Fail If TMPDIR Points to Non World-Writable Directory
GNOME Errors Might Occur When Starting GUI Installer
Installer Lock File Might Prevent Installer From Starting
Fixing a Failed Installation or Uninstallation
Fixing a Failed Uninstallation Using the Uninstaller
Fixing a Failed Installation or Uninstallation on Solaris Platforms
Fixing a Failed Installation or Uninstallation on Linux Platforms
Installation Will Fail on an NFS-Mounted Filesystem If Write Permission is Not Set
Viewing the Installation Log File
A. Command-Line Options for the Installer,Uninstaller,and install_patches Utility
C. Oracle Solaris 12.3 Components and Packages
D. Patch Identification Numbers and Descriptions
E. Version Numbers of the Oracle Solaris Studio 12.3 Components
On Solaris platforms, the installer stores information on which Oracle Solaris Studio 12.3 packages it has installed in two places:
On Linux platforms, the installer stores information on which Oracle Solaris Studio 12.3 packages it has installed in two places:
The database of installed packages
The /root/.nbi directory
If some packages were not properly installed, you will have problems using the Oracle Solaris Studio software, and you might have problems installing additional components or uninstalling the software.
For example, if the installer quit before installation was complete, the uninstaller (uninstall.sh) might not be present in your installation directory. Or if you used the pkgadd command to install any of the packages, the productregistry file or the product-cache directory in the /root/.nbi directory might be corrupted. In such cases, the uninstaller cannot uninstall the packages and you need to remove them in the correct way in order to be able to rerun the installer.
If the uninstaller quits before all the product files are deleted, rerunning the uninstaller will not delete the remaining files and you need to remove them in the correct way to complete the uninstallation of the product.
Do not uninstall the product by removing the installation directory. Packages will still be registered in the productregistry database and the /root/.nbi directory, and the installer will not run.
In some cases, the Oracle Solaris Studio packages might be correctly installed and the uninstaller is present in the installation directory, but the uninstaller fails because the /root/.nbi is corrupted. In this situation, you can force the uninstaller to remove the Oracle Solaris Studio packages and the installation directory by specifying the --force-uninstall when you start the uninstaller.
When you run the uninstaller with this option, it does not delete the package entries from the /root/.nbi directory, which has the following consequences:
When you run the installer to reinstall the Oracle Solaris Studio release you uninstalled, it does not allow you to specify which components to install, and installs all of the packages that were previously installed.
When you run the installer for any Oracle Solaris Studio release, it warns you that the /root/.nbi directory is corrupted, and gives you the option of proceeding with the installation or cancelling it.
su Password: root-password
/usr/bin/prodreg &
rm -r /.nbi
su Password: root-password
rpm -q -a | grep solarisstudio12.3
rpm -e package-name
Oracle Solaris Studio 12.3 rpm packages have the suffix 12.3, for example, solarisstudio12.3-cc-12.3-1. Be careful not to remove packages from Sun Studio releases, which have different suffixes.
rm -r /.nbi