You use the program SDBINST to install/update installation profiles or individual components of the database software on UNIX. You specify all required information on the command line, together with the command for starting the installation program.
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.
Prerequisites
· You are logged on to your server as the root user.
· You have unpacked the required software (Unpacking the Software on UNIX).
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 follow:
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).
· If the path <independent_program_path>/bin is not yet entered in the environment variable PATH, enter it now.
...
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.
For the OLTP
software, start the installation/update process with the following
command:
./SDBINST [-b] -profile
<inst_profile> [,<inst_profile2>...]| -package
<package_name>[,<package_name2>...] -indep_data
<independent_data_path> -indep_prog <independent_program_path>
-depend <dependent_path> [-o <sdb_user> -g
<sdba_group>]
For the SAP liveCache software, start the installation/update process (in SAP APO systems only) with the following command:
¡
For the installation
profile APO liveCache
./SDBINST [-b] -profile
"APO LiveCache" -indep_data <independent_data_path> -indep_prog
<independent_program_path> -depend <dependent_path> [-o
<sdb_user> -g <sdba_group>]
¡
For the software
component APO LC APPS
./SDBINST [-b] -package
"APO LC APPS" -depend <dependent_path>
You only need to specify the special operating system user <sdb_user> and the group <sdba_group> when you install the software for the first time, or if you are upgrading the software to Version 7.5.00.
For an explanation of the options, see Overview of the Options for the Program SDBINST.
You must place any names of installation profiles and software components that contain blanks in double quotation marks.
For certain installation profiles or software components you do not need to specify the options –indep_prog, -indep_data, and –depend . If you do specify them, the system ignores them. See the overview of the options for more information.
You see a message about the successful completion of the installation.
The software packages are installed and registered. You can check the result of your installation in 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.)