Background documentationInstalling or Updating the Software Using SDBINST Locate this document in the navigation structure

 

You use the SDBINST program to install or update component groups, installation profiles, or individual components of the database software.

If you want to update an existing database software installation, the procedure varies depending on whether your source version is < 7.5.00 or ≥ 7.5.00.

If your source version is < 7.5.00, you must stop X Server (database communication server) and all databases before the installation or update process. Please note that this interrupts the communication between the clients and all local databases (see: Utilities, Stopping X Server).

If your source version is ≥ 7.5.00, X Server software supports an update of the database software while X Server is running. In this case, it is not necessary to stop X Server and all the databases. However, you do need to stop the databases that are assigned to the installation directory being updated.

You can choose the installation mode taking into account the advantages and disadvantages of interactive and background installations.

Interactive Installation or Update

In an interactive installation or update, you install complete component groups or installation profiles. The SDBINST installation program queries all necessary information and offers you default values and options for the software to be installed and for the installation paths. The program then installs the software packages and registers them.

Background Installation or Update

In a background installation or update, you use options to specify the information required by SDBINST. The actual installation process then runs in the background.

Advantages of a Background Installation
  • Performing an installation or an update in the background is less time-consuming.

  • You have the option of installing or updating individual software components.

  • You can create identical database software installations on different computers using call script embedding.

Disadvantages of a Background Installation
  • You have to enter all the required options in the call script correctly and in their entirety.

  • The system does not determine some options from the software packages until runtime. This means that the system cannot check the completeness of the information at the start of the installation. It starts the installation, and then interrupts it when it finds that some information is missing.

Installing or Updating Component Groups or Installation Profiles

You can choose between various combinations of software components. Each individual combination fulfills a different purpose. You choose the component group or installation profile that is appropriate for your needs. You do not need to worry about the sequence of the installation or any dependencies between software components to obtain a fully functioning software installation.

To perform a standard installation or update of the entire database software package, choose the component group Server+Client or the installation profile all.

Installing or Updating Software Components

If you want to update parts of your database software, you install individual components of the database software. We recommend this installation procedure in special cases only.

In this procedure, you must take into account the dependencies between the individual software components. Otherwise, an appropriate error message is displayed and the system terminates the installation process.

Example Example

Installing the DB Analyzer Software Component in the Background

You want to update only the DB Analyzer program in your existing software installation. You start the installation of the DB Analyzer software component. The system recognizes that this component requires a new version of the Base software component. You are reminded that the DB Analyzer package depends on the Base package, which must be installed first. The installation terminates.

This means that if there are many dependencies, you will have to restart the installation many times (with a different installation package each time).

You can avoid this problem by using, for example, the DB Analyzer installation profile.

End of the example.

More Information

Logging

Database Administration, Special Operating System Users and Groups

Glossary, Directory