Entering content frame

 Interactive Installations/Updates on UNIX 

Use

You use the program SDBINST to install/update installation profiles of the database software on UNIX. The program queries all necessary information during the installation process.

If you want to update an existing database software installation, the procedure depends on whether your source version is 7.5.00 or higher, or is lower than 7.5.00.

If your source version is lower than 7.5.00, then you must stop the X Server and all database instances before the installation or update. Remember that this interrupts the communication between the clients and all local database instances. If your source version is 7.5.00 or higher, then the X Server software supports an update of the database software while the X Server is running. In this case, you no longer need to stop the X Server and all database instances. However, you do need to stop the database instances that are assigned to the installation directory that is being updated.

Conventions

Variables

Prerequisites

·        You are in a root shell.

·        You have downloaded the installation package, and unpacked it in a local directory of your choice (Unpacking the Software on UNIX).

Preparations

If the following conditions apply to your system, you must perform the specified steps before a new installation:

·        The installation program enters the services sql6, sql30 and sapdbni72 in the file /etc/services, if they do not already exist there. If these services are managed centrally for your system on your network (NIS), you must enter them there as follows:
sql6 7210/tcp
sql30  7200/tcp
sapdbni72 7269/tcp

·        During the installation, the database software must be assigned to a special operating system user, <sdb_user>, as the owner of the software and to the group <sdba_group>.
We recommend that you define the group and the owner in advance. Only users with the correct authorizations can generate the database instances later (see also Authorization Concept for UNIX Operating Systems for software versions from 7.5.00).
The special operating system user must not log on to the operating system. For this reason, take this authorization away from this user. For information on how to do this, see your operating system documentation (lock account).

If you manage user groups and owners locally on your host, we recommend that you register the names of the user groups and the owner in the operating system before you start the installation. However, you can also specify this information during the installation process.
If you manage user groups and owners for your system centrally in the network, you must create them here before you start the installation. For more information on creating operating system users and user groups, see your operating system documentation.

The primary group of the owner of the database software is the administrator group.

For SAP systems, you must use the names sdb and sdba for the owner <sdb_user> and the group <sdba_group>.

For consistency, especially if you need to contact the support team, we recommend that you also use the names sdb and sdba for the owner and group in other systems.

·        If the path <independent_program_path>/bin is not yet entered in the environment variable PATH, enter it now. (For information on setting environment variables, see your operating system documentation.)

Procedure

...

       1.      If you want to update an existing database software installation,

¡        If necessary, stop each database instance assigned to the installation directory that you want to update with the command
dbmcli –d <database_name> -u <dbm_user>,<password> db_offline

¡        If necessary, stop the X Server program ( vserver process) with the command
x_server stop

For a new installation, start at step 2.

       2.      Switch to the directory
maxdb-<inst_profile>-<os>-64bit-<arch>-<version>_<build>,
which contains the installation software for your chosen installation profile.
Enter
./SDBINST to start the installation/update program.

       3.      The system proposes your chosen installation profile.
If your chosen installation profile (all, for example) contains other installation profiles, you can also select one of these profiles. Specify the appropriate ID. Confirm your selection.

       4.      If you are installing the software for the first time, or if you are updating the software to Version 7.5.00, then the system prompts you to enter the following details:

¡        the special operating system user <sdb_user> (the owner of the database software)

¡        the group <sdba_group>

If you are installing or updating older software versions, the system prompts you to enter the group <group> and owner <owner> of the database software.

If the group and owner have already been created, enter and confirm the correct values. The system compares this information with the values stored locally or in the network. If your information does not match these values, then the installation terminates.

If the group and owner have not yet been created, the system asks you whether you want to create them. Specify your chosen values, or confirm the defaults. When you specify these values, the group and owner are created locally on your host.

       5.      The system now checks your server for installations of the database software that can be updated.

It lists any relevant installations.

¡        If you want to update an existing installation, specify its ID.
The system then updates the software in
<independent_program_path>. Depending on your chosen profile, the software in <dependent_path> is also updated, if the installation package contains newer versions of the files.

¡        If you want to perform a new installation of the database software in parallel with the existing installation, specify none. You then have the option of specifying a new installation path. Define an installation path in parallel with the existing installation path.

If no installation of the database software exists yet on your server, the software components in the installation profile are now installed, one by one. Depending on your chosen installation profile, the system prompts you for the following paths:

¡        Path for saving data, configurations, and run directories of database instances and database applications (system default is /var/opt/sdb/data)

¡        Path for saving programs and libraries shared by database instances and database applications (system default is /opt/sdb/programs)

¡        Path for saving the server software that is dependent on the database version.
The specified path must be unique. Multiple directories containing different versions can exist simultaneously (system default is
/opt/sdb/<version>)

Specify paths, or confirm the defaults.

       6.      If there has not been an installation of the database software on your server up to now, add the entry <independent_program_path>/bin to the environment variable PATH for each user that wants to use the database system.

You see a message about the successful completion of the installation.

Result

The chosen installation profile of the database software has been installed and registered in the new version on your server. You can check the result of your installation using the log (Logging).

You can now create new database instances with the Database Manager

(See:

·        Creating a Database Instance in Database Manager CLI or

·        the Web DBM documentation.)

 

 

Leaving content frame