Using Oracle Services Tools Bundle for Sun Systems

Question:

Where can I find the log files of the Oracle Services Tools Bundle for Sun Systems installer?

Answer:

All STB installer events (success or failure) on a system are logged under /var/log/install_stb-v<STB_VERSION>.log

Question:

Will I be able to run the Oracle Services Tools Bundle for Sun Systems installer without any user intervention?

Answer:

Yes, the auto option can be used to run STB installer in a non-interactive mode; however, There is no auto mode available for the OpenSolaris version of STB. The OpenSolaris version can only be run interactively.

Question:

What is the default option for the Oracle Services Tools Bundle for Sun Systems installer?

Answer:

The default option for STB installer is manual, where installer runs in interactive mode.

Question:

Does the Oracle Services Tools Bundle for Sun Systems support command-line arguments?

Answer:

For information, consult the help option for usage; type: ./install_stb.sh -help.

Question:

Are there any pre-requisite packages for the Oracle Services Tools Bundle for Sun Systems installer?

Answer:

STB is nothing more than an intelligent installer script, the patch pre-requisites are that of its individual components and not of STB as a whole. Therefore, if a certain application patch dependency is not met, only that application will fail to get installed. Individual components dependencies has to be checked on patches before installing STB.

You can find documentation of each component along with STB download at http://www.sun.com/service/stb

Question:

If I do not have enough space in/tmp, can I still install STB?

Answer:

Yes, 5.2 and higher versions of STB facilitates an option to unpack STB temporary files in alternate location. This can be achieved by setting an environment variable STB_INST_PATH before running STB.

For example, if you want to utilize /var for temporarily unpacking and installing STB components:

export STB_INST_PATH=/var

./install_stb.sh

This will unpack all temporary files in/var/STBinstall directory.

---

Note –

You need 49 MB free space to unpack temporary files.

---

Question:

How do I extract STB packages to a non-default directory?

Answer:

STB, by default, extracts all its packages to /var/tmp/stb/extract directory. However, starting from STB 5.2, packages bundled in STB can be extracted into non default directory by exporting an environmental variable STB_EXT_PATH.

For example if one wants to extract the packages to user defined path such as /tmp/foo:

export STB_EXT_PATH=/tmp/foo

./install_stb.sh -runmode auto -ext

This will extract all STB packages to /tmp/foo/stb/extract directory.

Question:

Can I run STB from a non-global zone?

Answer:

Yes. STB can be run from non global zone. However, only Service Tags and SNEEP can be installed or extracted in non global zones. Oracle Explorer Data Collector and LWACT can be installed only from global zone.

Question:

As I try to install Service Tags using STB, I get the message "Service Tag dependency failed" and the installation of Service Tags is skipped. Why does this happen?

Answer:

Service Tags depends on a number of packages without which it may not function properly. STB 5.2 and higher versions checks for the list of all service tags dependency packages before installing it. If one or more of these dependent package is found missing, STB skips Service Tags installation with the information on the missing packages.

Question:

What happens if STB is interrupted while it is run?

Answer:

If STB is interrupted during installation of a package, it attempts to clean up any partial installation that it creates. Also, STB displays the list of already completed installations during that run. User can manually remove them, if needed. Similarly, if STB is interrupted during extraction of packages, a message is displayed asking the user to remove the extracted packages manually. If STB is interrupted while it performs other tasks, it updates the log file, removes the traces of any transient files that it placed on the system and exits gracefully.

Question:

After I interrupt the STB installation by pressing Ctrl+C continuously I find partially installed STB component in system. Why is that so?

Answer:

STB, when interrupted, attempts to clean up partial installation from the system. But if user interrupts the clean up process continuously, it can abort package removal process, leaving behind partial installation. In this case, user has to manually cleanup the partially installed packages.

Question:

If system has any STB component partially installed, can STB detect that? How are these packages handled by STB?

Answer:

Yes, STB when invoked, can detect partial installation of its components, if any. When STB is invoked in manual mode, user will be prompted for overwriting the partially installed package. If user agrees, STB will remove the corresponding partially installed component and install the bundled version completely. In auto mode, any partial installations of the components will automatically be overwritten by the corresponding bundled versions.

Question:

Does STB support handsoff/jumpstart installation?

Answer:

Yes. STB 6.0 and higher supports jumpstart installation. STB should be run in auto mode in the jumpstart script.

Question:

Do we have any uninstallation script for STB?

Answer:

STB does not provide a script to remove packages installed by it. This is due to the interdependency between the packages and also due to the criticality of the functionality rendered by these packages instances on the system.

Although STB does not provide any uninstaller script, one can manually remove the packages installed by STB using the Solaris pkgrm utility.

For example, one can remove LWACT from system by executing the below shown command:

pkgrm SUNWlwact