instman eng

8/11/2019 Instman Eng

http://slidepdf.com/reader/full/instman-eng 1/45

Installation ManualMySQL MaxDB

Ve r s i o n 7 . 5



SAP AG March 2004

Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help → General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library .

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,

and menu options.Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Installation Manual MySQL MaxDB Version 7.5 3



SAP AG March 2004

Installation Manual..................................................................................................................... 5

Installing and Updating the Database Software..................................................................... 6

Installing/Updating Software on UNIX................................................................................ 8

Unpacking the Software on UNIX................................................................................... 8

Interactive Installations/Updates on UNIX...................................................................... 9

Background Installations/Updates on UNIX ................................................................. 12

Installing/Updating Software on Linux.............................................................................. 14

Installations/Updates with SDBINST ............................................................................ 14

Installations/Updates with the Red Hat Package Manager .......................................... 15

Installing/Updating Software on Microsoft Windows ........................................................ 16

Unpacking the Software on Microsoft Windows........................................................... 16

Interactive Installations/Updates on Microsoft Windows .............................................. 17

Background Installations/Updates on Microsoft Windows............................................ 19

Uninstalling the Database Software..................................................................................... 21

Uninstallations with SDBUNINST on UNIX, Linux and Microsoft Windows..................... 21

Uninstallations with the Red Hat Package Manager........................................................ 22

Upgrading Database Instances and Their Software............................................................ 22

Selection of the Upgrade Strategy ................................................................................... 23

Patch Installation with SDBUPD................................................................................... 24

Patch Installation with SDBINST and Follow-Up Actions ............................................. 26

In-Place Migration with SDBUPD ................................................................................. 28

In-Place Migration with SDBINST and Follow-Up Actions ........................................... 29

Upgrade with APO Extract/Load................................................................................... 32

Authorization Concept for UNIX Operating Systems........................................................... 33

Troubleshooting ................................................................................................................... 34

Errors in the Execution of the Program SDBINST ........................................................... 34

Errors in the Execution of the Program SDBUPD............................................................ 35

Case 1: No Database Instances Exist Yet.................................................................... 35

Case 2: Downgrade for Dependent Software............................................................... 36

Case 3: Downgrade for Independent Software ............................................................ 38

Detailed Information............................................................................................................. 39

Installation Profiles ........................................................................................................... 39

Software Components...................................................................................................... 40

Logging............................................................................................................................. 42

Overview of Options for the Program SDBINST.............................................................. 43

Overview of Options for the Program SDBUNINST......................................................... 43

Overview of Options for the Program SDBUPD............................................................... 44




SAP AG March 2004

Installation Manual

PurposeThis documentation provides you with detailed information on the following topics: installing

and uninstalling MaxDB software with Version 7.5, updating the database software, andupgrading database instances to Version 7.5, on the operating system platforms [Extern] supported by MaxDB.

It is particularly concerned with the following programs:

• SDBINST for the installation/update of installation profiles [Seite 39 ] and individualsoftware components [Seite 40 ], while taking into account dependencies between thecomponents

• SDBUNINST for uninstalling software components, while taking into accountdependencies between the components

• SDBUPD for upgrading database instances and their software [Seite 22 ]

.

For a short description of the standard installation/update, and standarduninstallation, of the entire MaxDB software package outside of SAP systems ,see the documentation Database Software Installation Guide [Extern] .

For general information about the database system, see the documentationDatabase Administration [Extern] .

The description of upgrading database instances and their software also applies to databaseinstances in SAP systems .

ConstraintsThis documentation is not relevant for installing or uninstalling MaxDB software in SAPsystems . The installation or uninstallation of the MaxDB software required for SAP systemsis described in SAP-specific guides. SAP customers can find these guides in the SAP ServiceMarketplace, at http://service.sap.com .

Implementation ConsiderationsThe programs SDBINST, SDBUNINST and SDBUPD are part of the database softwarepackage.

Open source users can download the entire database software free of charge fromhttp://www.mysql.com/downloads .

SAP customers receive the MaxDB software with the SAP installation CD or in the ServiceMarketplace at http://service.sap.com .

The following description is based on using the software available online athttp://www.mysql.com/downloads and the SAP Service Marketplace.

Installing and Updating the Database Software [Seite 6]

Uninstalling the Database Software [Seite 21 ]

Upgrading Database Instances and Their Software [Seite 22 ]




SAP AG March 2004

Installing and Updating the Database Software

Implementation ConsiderationsYou can install or update the database software either interactively, or in the background.

You can install complete installation profiles [Seite 39 ], or just install or update individualsoftware components [Seite 40 ]. The installation pr ogram itself decides whether it is dealingwith a new installation or an update.

The system logs [Seite 42 ] the installation process.

Before you start the installation or upgrade of the database software:

• Make sure you have taken precautions against the most common errors that can causean installation or update to crash (see Troubleshooting [Seite 34 ]).

• Inform yourself about the advantages and disadvantages of interactive and backgroundinstallations.

• Decide whether you need one or more database instances.

If you plan to run multiple database instances, we recommend a separate(parallel) software installation for each database instance. This makessubsequent updates easier, since any errors will only affect one databaseinstance.

• Choose an appropriate installation profile, or decide whether, in special cases, you onlyneed to install or update one or more individual software components. However, youcan install individual components in the background only.

We recommend strongly that you always perform your installation or update withinstallation profiles. This is a simple and secure way of choosing the databasesoftware installation that meets your needs.

ConventionsSee Variables [Extern] , Supported Operating Systems and Platforms [Extern] , AuthorizationConcept for UNIX Operating Systems [Seite 33 ]

Interactive Installation/Update In an interactive installation or update, you install complete installation profiles. The

installation program SDBINST queries all necessary information, and offers you defaults andoptions for the installation profiles and installation paths. The program then installs thesoftware package and registers it.

Background Installation/Update In a background installation or update, you use options to specify the information needed bySDBINST. The actual installation process then runs in the background.

Advantages of Installation in the Background

• Performing an installation or an upgrade in the background takes less time.

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

installation profiles).




SAP AG March 2004

• You can use an embedding in a call script to generate identical database softwareinstallations on different servers.

Disadvantages of Installation in the Background

• You must enter all the required options in the call script correctly and completely.

• The system determines some options from the software packages only at runtime. Thismeans that the system cannot check the completeness of the information at the start ofthe installation. It starts the installation, and then interrupts it only when any informationis missing.

Installation/Update with Installation ProfilesYou can choose between various combinations of software components. Each individualcombination fulfils a different purpose. You choose the installation profile that is appropriatefor your needs, and do not need to worry about the sequence of the installation, or anydependencies between software components, to obtain a fully functioning softwareinstallation.

To perform a standard installation or update of the entire database software package ,choose the installation profile all .

For a short description of the standard installation or update of the entiredatabase software package , see the documentation Database SoftwareInstallation Guide [Extern] .

Installation/Update of Software ComponentsYou install individual components of the database software to just update parts of yourdatabase software installation. We recommend this installation procedure in special casesonly.

In this procedure, you must take into account the dependencies between the individualsoftware components. Otherwise, you see an error message that tells you about this, and thesystem terminates the installation.

Background Installation of the Software Component Precompiler (CPC<version>)

You want to update only the C++ Precompiler in your existing softwareinstallation. You start the installation of the software component CPC SDK<version> . The system recognizes that this component requires a new versionof the software component CPC Base . You are reminded that the package CPCSDK <version> depends on the package CPC Base , which must be installedfirst. The installation terminates.

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

You can avoid this problem by using, for example, the installation profileC Precompiler .

Installing/Updating Software on UNIX [Seite 8]

Installing/Updating Software on Linux [Seite 14 ]

Installing/Updating Software on Microsoft Windows [Seite 16 ]




SAP AG March 2004

Installing/Updating Software on UNIX

Use You install or update a chosen installation profile [Seite 39 ] or database software component

[Seite 40 ]. Use the following procedure for updates only if no database instances [Extern] refer to the installation path of the software that you want to update.

If database instances refer to the installation path of the software, you mustupgrade the database instances together with the software (see UpgradingDatabase Instances and Their Software [Seite 22 ]). Otherwise, you risk makingthe database instances incompatible with the database software, and you maynot be able to restart them.


Procedure...

1. First, unpack the database software to a local directory.

Unpacking the Software on UNIX [Seite 8]

2. Now decide whether you want to perform an interactive installation (only possible forinstallation profiles) or a background installation.

Interactive Installations/Updates on UNIX [Seite 9]

Background Installations/Updates on UNIX [Seite 12 ]

For the advantages and disadvantages of these installation procedures, seeInstalling and Updating the Database Software [Seite 6].

Unpacking the Software on UNIXConventions

Variables [Extern]

Procedure...

1. Choose the appropriate software package for your operating system architecture, yourdatabase instance type, and the installation profile [Seite 39 ].

If you want to install or update an individual software component [Seite 40 ] only, thenselect an installation profile that contains this software component.

Installation from the SAP Service Marketplace (service.sap.com , for SAP customersonly)

For the OLTP [Extern] database instance type, chooseSAP Software → Download → SAP Support Packages & Patches → MaxDB → MaxDB OLTP 64-BIT → MaxDB <version> OLTP → <os> → MAXDB<version>_<build>-<GUID>.SAR

For liveCache [Extern] database instance type (SAP APO system), chooseSAP Software → Download → SAP Support Packages & Patches → SAP APO → SAP APO <apo_version> → Binary Patches → APO

LC<version>/LCAPPS<apo_version>→

<os>→

LC<version>A<apo_version>_<apo_build>-<GUID>.SAR




SAP AG March 2004

Installation from http://www.sapdb.org

For the OLTP database instance type onlyGo to Software , choose your operating system, and follow the instructions fordownloading the software packagemaxdb-<inst_profile>-<os>-64bit-<arch>-<version>_<build>.tgz

2. Copy the software package to a local directory of your choice.

3. Unpack the software with the following command:

For an installation from the SAP Service Marketplace (service.sap.com ):

SAPCAR –xvf MAXDB<version>_<build>-<GUID>.SAR


tar xvzf maxdb-<inst_profile>-<os>-64bit-<arch>- <version>_<build>.tgz

ResultThe system creates the following subdirectories in the local directory

• for OLTP software, the subdirectorymax db-<inst_profile>-<os>-64bit-<arch>-<version>

• for SAP liveCache, the subdirectoryapo<apo_version>_livecache-<os>-64bit-<arch>-<version>

and saves the software to them.

Interactive Installations/Updates on UNIX

UseYou use the program SDBINST to install/update installation profiles [Seite 39 ] of the databasesoftware on UNIX. The program queries all necessary information during the installationprocess.

If you want to update an existing database software installati on, the proceduredepends on whether your source version is 7.5.00 or higher, or is lower than7.5.00.

If your source version is lower than 7.5.00, then you must stop the X Server[Extern] and all database instances before the installation or update. Rememberthat this interrupts the communication between the clients and all local databaseinstances. If your source version is 7.5.00 or higher, then the X Server softwaresupports an update of the database software while the X Server is running. Inthis 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 theinstallation directory that is being updated.

ConventionsVariables [Extern]




SAP AG March 2004

Prerequisites• You are in a root shell.

• You have downloaded the installation package, and unpacked it in a local directory ofyour choice ( Unpacking the Software on UNIX [Seite 8]).

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

• The installation program enters the services sql6, s q l30 and sapdbni72 in the file/etc/services , if they do not already exist there. If these services are managedcentrally for your system on your network (NIS), you must enter them there as follows:sql6 7210/tcpsql30 7200/tcpsapdbni72 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 withthe correct authorizations can generate the database instances later (see also

Authorization Concept for UNIX Operating Systems [Seite 33 ] for software versionsfrom 7.5.00).The special operating system user must not log on to the operating system. For thisreason, take this authorization away from this user. For information on how to do this,seeyour operating system documentation (lock account).

If you manage user groups and owners locally on your hos t, we recommend that youregister the names of the user groups and the owner in the operating system beforeyou start the installation. However, you can also specify this information during theinstallation process.If you manage user groups and owners for your system centrally in the network, youmust create them here before you start the installation. For more information oncreating operating system users and user groups, see your operating systemdocumentation.

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, werecommend that you also use the names sdb and sdba for the owner andgroup in other systems.

• If the path <independent_program_path>/bin is not yet entered in theenvironment variable PATH , enter it now. (For information on setting environmentvariables, 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 directorythat you want to update with the commanddbmcli –d <database_name> -u <dbm_user>,<password>db_offline




SAP AG March 2004

If necessary, stop the X Server program ( vserver process) with the commandx_server stop

For a new installation, start at step 2.

2. Switch to the directorymaxdb-<inst_profile>-<os>-64bit-<arch>-<version>_<build> , which contains the installation software for your chosen installation profile [Seite 39 ].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 yo urselection.

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

the special operating system user <sdb_user> (the owner of the databasesoftware)

the group <sdba_group>

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

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

If the group and owner have not yet been created, the system asks you whether youwant to create them. Specify your chosen values, or confirm the defaults. When youspecify 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 alsoupdated, 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 ofspecifying a new installation path. Define an installation path in parallel with theexisting installation path.

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

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

Path for saving programs and libraries shared by database instances anddatabase 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 differentversions can exist simultaneously (system default is /opt/sdb/<version> )

Specify paths, or confirm the defaults.




SAP AG March 2004

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 variablePATH for each user that wants to use the database system.

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

ResultThe chosen installation profile of the database software has been installed and registered inthe new version on your server. You can check the result of your installation using the log(Logging [Seite 42 ]).

You can now cr eate new database instances with the Database Manager

(See:

• Creating a Database Instance [Extern] in Database Manager CLI or

• the Web DBM [Extern] documentation.)

Background Installations/Updates on UNIX

Use You use the program SDBINST to install/update installation profiles [Seite 39 ] or individualcomponents [Seite 40 ] of the database software on UNIX. You specify all r equired informationon the command lin e, together with the command for startin g the installation program.

If you want to update an existing database software installation, the proceduredepends on whether your source version is 7.5.00 or higher, or is lower than7.5.00.

If your source version is lower than 7.5.00, then you must stop the X Server[Extern] and all database instances before the installation or update. Rememberthat this interrupts the communication between the clients and all local databaseinstances. If your source version is 7.5.00 or higher, then the X Server softwaresupports an update of the database software while the X Server is running. Inthis 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 theinstallation directory that is being updated.

Conventions

Variables [Extern]

PrerequisitesYou are logged on to your server as the root user.•

• You have unpacked the required software ( Unpacking the Software on UNIX [Seite 8]).

PreparationsIf 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 managedcentrally for your system on your network (NIS), you must enter them there as follow:




SAP AG March 2004

sql6 7210/tcpsql30 7200/tcpsapdbni72 7269/tcp

• During the installation, the database software must be assigned to a special operatingsystem 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 inadvance. Only users with the correct authorizations can generate the databaseinstances later (see also Authorization Concept for UNIX Operating Systems [Seite 33 ] for software versions from 7.5.00).

• If the path <independent_program_path>/bin is not yet entered in theenvironment variable PATH , enter it now.

Procedure...

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

If necessary, stop each database instance assigned to the installation directorythat 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 commandx_server stop


2. For the OLTP software, start the installation/update process with the followingcommand:./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 APOsystems only) with the following command:

For the installation profile [Seite 39 ] APO liveCache ./SDBINST [-b] -profile "APO LiveCache" -indep_data

<independent_data_path> -indep_prog <independent_program_path> -dep end <dependent_path> [-o

<sdb_user> -g <sdba_group>]

For the software component [Seite 40 ] 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 firsttime, or if you are upgrading the software to Version 7.5.00.

For an explanation of the options, see Overview of the Options for theProgram SDBINST [Seite 43 ].

You must place any names of installation profiles and software components thatcontain blanks in double quotation marks.

For certain installation profiles or software components you do not need tospecify the options –indep_prog , -indep_data , and –depend . If you dospecify them, the system ignores them. See the overview of the options for moreinformation.





SAP AG March 2004

ResultThe software packages are installed and registered. You can check the result of yourinstallation in the log ( Logging [Seite 42 ]).

You can now create new database instances with the Database Manager

(See:• Creating a Database Instance [Extern] in Database Manager CLI or

• the Web DBM [Extern] docum entation.)

Installing/Updating Software on Linux

UseYou choose a software component [Seite 40 ], and install it.

Use the following procedure for updates only if no database instances [Extern] refer to theinstallation path of the software that you want to update.

If database instances refer t o the installation path of the software, you mustupgrade the database instances together with the software ( UpgradingDatabase Instances and Their Software [Seite 22 ]). Otherwise, you risk makingthe database instances incompatible with the database software, and you willnot be able to restart them.

If you have already installed the database software on your server with the RedHat Package Manager (installation with rpm package), then you can now usethis program only for subsequent installations and updates.You cannot use the SDBINST program for inst allations and updates (installationwith tgz package).

Two programs are available for installations on Linux:

• Installations/Updates with the Red Hat Package Manager [Seite 15 ]

• Installations/Updates with SDBINST [Seite 14 ]

Installations/Updates with SDBINSTUseYou install or update components [Seite 40 ] of the database software on Linux. You specifyall required information on the command line, together with the command for starting theinstallation program.

You must take into account the dependencies between the software components toguarantee that the software installation can function.

If you have already installed the database system on your server with the RedHat Package Manager (installation with rpm package), then you can now usethis program only for subsequent installations and updates.




SAP AG March 2004

You cannot use the SDBINST program for installations and updates (installationwith tgz package).

ProcedureProceed as described under Installing/Updating the Software on UNIX [Seite 8].

Installations/Updates with the Red Hat PackageManager

UseYou install or update components [Seite 40 ] of the database software on Linux. You specifyall required information on the command line, together with the command for starting theinstallation program.

You must take into account the dependencies between the software components toguarantee that the software installation can function.

Prerequisites• You are in a root shell.

• You can access the rpm packages that you want to install from your computer.

Procedure

First Installation of the Database Software...

1. Execute the installation command:

rpm -Uhv maxdb<package_name>.rpm 2. Add the entry /opt/sdb/programs/bin to the environment variable PATH for each

user that wants to use the database system.

Updating the Database Software

Stop all existing database software on the server where you want to update thesoftware version.

Stop the X Server [Extern] program ( vserver process). Remember that thisinterrupts the communication between the clients and all local database

instances....

1. Stop all database instances assigned to the installation directory that you want toupdate with the commanddbmcli –d <database_name> -u <dbm_user>,<password> db_offline

2. Execute the installation command:rpm -Uhv maxdb<package_name>.rpm

ResultThe software components in the installation directory have been installed and registered intheir new version.

You can now create new database instances with the Database Manager

See:




SAP AG March 2004

• Creating a Database Instance [Extern] in Database Manager CLI or

• the Web DBM [Extern] documentation

Installing/Updating Software on MicrosoftWindows

Use You install or update a chosen installation profile [Seite 39 ] or database software component[Seite 40 ]. Use the following procedure for updates only if no database instances [Extern] refer to the installation path of the software that you want to update.

If database instances refer to the installation path of the software, you mustupgrade the database instances together with the software (see UpgradingDatabase Instances and Their Software [Seite 22 ]). Otherwise, you risk makingthe database instances incompatible with the database software, and you maynot be able to restart them.


Procedure...

1. First, unpack the database software to a local directory.

Unpacking the Software on Microsoft Windows [Seite 16 ]

2. Now decide whether you want to perform an interactive installation (only possible forinstallation profiles) or a background installation.

Interactive Installations/Updates on Microsoft Windows [Seite 17 ]

Background Installations/Updates on Microsoft Windows [Seite 19 ]

For the advantages and disadvantages of these i nstallation procedures, seeInstalling and Updating the Database Software [Seite 6].

Unpacking the Software on Microsoft WindowsConventionsVariables [Extern]

Procedure......

1. Select the database software package that is appropriate for your installation profileand operating system architecture.

If you want to install or update an individual software c omponent [Seite 40 ] only, thenselect an installation profile that contains this software component.

Installation from the SAP Service Marketplace (service.sap.com , for SAP customersonly)

For the OLTP [Extern] database instance type, choose




SAP AG March 2004

For the 32 bit version SAP Software → Download → SAP Support Packages & Patches → MaxDB → MaxDB OLTP → MaxDB <version> OLTP → <os> → MAXDB<version>_<build>-<GUID>.SAR

For the 64 bit version

SAP Software → Download → SAP Support Packages & Patches → MaxDB → MaxDB OLTP 64-BIT → MaxDB <version> OLTP → <os> → MAXDB <version>_<build>-<GUID>.SAR

For liveCache [Extern] database instance type (SAP APO system), chooseSAP Software → Download → SAP Support Packages & Patches → SAP APO → SAP APO <apo_version> → Binary Patches → APOLC<version>/LCAPPS<apo_version> → <os> → LC<version>A<apo_version>_<apo_build>-<GUID>.SAR


OLTP instance type onlyGo to Software , choose your operating system, and follow the instructions fordownloading the software packagemaxdb-<inst_profile>-win-<32|64>bit-<arch>-<version>_<build>.zip

2. Copy the software package to a local directory of your choice.

3. Unpack

a sar package with the program SAPCAR

a zip package with the program Winzip

to a local directory of your choice.

ResultThe system creates the following subdirectories in the local directory

• for OLTP software, the subdirectorymaxdb-<inst_profile>-win-<32|64>bit-<arch>-<version>

• for SAP liveCache software, the subdirectoryapo<apo_version>_livecache-win-<32|64>bit-<arch>-<version>

and saves the software to them.

Interactive Installations/Updates on MicrosoftWindows

Use

You use the program SDBINST to install/update installation profiles [Seite 39 ] of thedatabase software on Microsoft Windows. The program queries all necessary informationduring the installation process.




SAP AG March 2004

You must stop the program X Server [Extern] before you update the databasesoftware. Remember that this interrupts the communication between the clientsand all local database instances.


Prerequisites• You have administrator rights for your server.

• You have downloaded and unpacked the installation package ( Unpacking the Softwareon Microsoft Windows [Seite 16 ]).

Procedure...

1. If you want to update an existing installation of the database system,

Stop each database instance of all installed versions of the database systemwith the commanddbmcli –d <database_name> -u <dbm_user>,<password>db_offline

Stop the X Server program ( Xserver service) with the commandx_server stop


2. Open a command prompt and navigate to the local directory that contains theinstallation files:

for OLTP software, the directorymaxdb-<inst_profile>-win-<32|64>bit-<arch>-<version>

for liveCache software, the directory

apo<apo_version>_<livecache>-win-<32|64>bit-<arch>-<version>

3. Enter sdbinst to start the installation/update program.

4. The system proposes your chosen installation profile [Seite 39 ]. If your installationprofile ( all , for example) contains other installation profiles, you can also select one ofthese profiles.Specify the appropriate ID. Confirm your selection.

5. The system now checks your server for installations of the database system that canbe 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 alsoupdated, 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 ofspecifying a new installation path. Define an installation path in parallel with theexisting installation path.

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

Path for saving data, configurations, and run directories of database instancesand database applications (system default is C:\Program Files\sdb\data )




SAP AG March 2004

Path for saving programs and libraries shared by database instances anddatabase applications (system default is C:\ProgramFiles\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 C:\ProgramFiles\sdb\<version> )

Specify paths, or confirm the defaults.


6. If no database software has been installed on your server up to now, we recommendthat you shut down your server, and restart it, so that the system can recognize the<independent_program_path> .

This is not necessary if you have updated the database software.

Result

The chosen installation profile of the database software has been installed and registered inits new version. You can check the result of your installation using the log ( Logging [Seite42 ]).

You can create new database instances with the Database Manager

(See:

• Creating or Initializing a Database Instance [Extern] in Database Manager GUI

• Creating a Database Instance [Extern] in Database Manager CLI

• or the Web DBM [Extern] documentation.)

Background Installations/Updates on MicrosoftWindows

Use You use the program SDBINST to install/update installation profiles [Seite 39 ] or individualcomponents [Seite 40 ] of the database software on Microsoft Windows. You specify allrequired information on the command line, together with the command for starting theinstallation program.

You must stop the program X Server [Extern] before you update the databasesoftware. Remember that this interrupts the communication between the clientsand all local database instances.

Conventions

Variables [Extern]

Prerequisites • You have administrator rights for your server.

• You have downloaded and unpacked the installation package ( Unpacking the Software

on Microsoft Windows [Seite 16 ]).




SAP AG March 2004

Procedure 7. If you want to update an existing installation of the database system,

Stop each individual database instance with the commanddbmcli –d <database_name> -u <dbm_user>,<password>db_offline

Stop the X Server program ( Xserver service) with the commandx_server stop


8. Start the installation/update process for the OLTP software 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>

Start the installation/update process for the liveCache software (in SAP APO systems

only) with the following command: For the installation profile [Seite 39 ] APO liveCache

sdbinst [-b] -profile "APO LiveCache" -indep_data <independent_data_path> -indep_prog <independent_program_path> -

depend <dependent_path>

For the software component [Seite 40 ] APO LC APPSsdbinst [-b] -package "APO LC APPS" -depend <dependent_path>

For an explanation of the options, see Overview of the Options for the ProgramSDBINST [Seite 43 ].

You must place any names of installation profiles and software components thatcontain blanks in double quotation marks.

For certain installation profiles or software components you do not need tospecify the options –indep_prog , -indep_data , and –depend . If you dospecify them, the system ignores them. See the overview of the options for moreinformation.


ResultThe software packages are installed and registered. You can check the result of yourinstallation in the log ( Logging [Seite 42 ]).

You can create new database instances with the Database Manager

(See:

• Creating or Initializing a Database Instance [Extern] in Database Manager GUI

• Creating a Database Instance [Extern] in Database Manager CLI

• or the Web DBM [Extern] documentation.)




SAP AG March 2004

Uninstalling the Database Software

Implementation ConsiderationsDepending on the procedure you used to install the database software, you can now use

either the SDBUNINST program or the Red Hat Package Manager to uninstall the software.In both cases, you can uninstall the entire database software, individual installation profiles, orindividual software components.

If you used the Red Hat Package Manager (rpm package) to install thedatabase software on your server, you can uninstall the software with thisprogram only.


Uninstallations with SDBUNINST on UNIX, Linux and Microsoft Windows [Seite 21 ]

Uninstallations with the Red Hat Package Manager [Seite 22 ]

Uninstallations with SDBUNINST on UNIX, Linuxand Microsoft Windows

Implementation ConsiderationsYou use the uninstall program SDBUNINST to uninstall some or all of the softwarecomponents [Seite 40 ], while taking into account the dependencies between them. Thisprogram is included in the database software from Version 7.3.00 Build 033.

You can use it to uninstall the software of the database system from Version 7.2.

Overview of Options for the Program SDBUNINST [Seite 43 ]

For a short description of the standard uninstallation of the entire databasesoftware package with SDBUNINST, see the documentation Database SoftwareInstallation Guide [Extern] .

ConventionsVariables [Extern] , Supported Operating Systems and Platforms [Extern]

Prerequisites • One or more versions of the database software are installed on your server. These

include at least one installation of Version 7.3.00, Build 033 or higher, which includesSDBUNINST.

• You have administrator rights for your server.

Procedure...

1. On UNIX/Linux: Switch to the root shell.




SAP AG March 2004

On Microsoft Windows: Open the command prompt on your server.

2. Stop the database instances on your server one by one with the command:dbmcli –d <database_name> -u <dbm_user>,<password> db_offline

3. Delete the database instances on your server one by one with the command:dbmcli –d <database_name> -u <dbm_user>,<password> db_drop

4. Call the uninstall program with your chosen option:

If you want to uninstall all software components, specify the option –all ;otherwise, specify your chosen component with the option –package .

Uninstallations with the Red Hat Package Manager

UseYou install or update components of the database software on Linux. You specify all requiredinformation on the command line, together with the command for starting the installationprogram.

PrerequisitesYou are in a root shell.

Procedure1. Stop and delete each database instance one by one by executing the following

commands:dbmcli –d <database_name> -u <dbm_user>,<password> db_offline dbmcli –d <database_name> -u <dbm_user>,<password> db_drop

2. Execute the uninstall command:rpm -e maxdb<package_name | *>.rpm

ResultThe specified software component(s) are uninstalled.

Upgrading Database Instances and Their SoftwareImplementation ConsiderationsYou upgrade database instances [Extern] from one version to another, and update theirdatabase software at the same time. The following information refers to this procedure as anupgrade.

The strategy you choose depends on the database instance type [Extern] and the source andtarget versions. For help on choosing a suitable upgrade strategy, see the tables underSelection of the Upgrade Strategy [Seite 23 ].

Each time you upgrade database instances, we recommend that you takeprecautions to avoid errors. Make sure that you have made complete backups of




SAP AG March 2004

all data in the relevant database instances, and also have the database softwareof the source version. Only then can you return to the source version straightaway, if necessary, and avoid long periods of system downtime.

Before you start, make sure that you have excluded the most common sources of errors inthe upgrade (see Troubleshooting [Seite 34 ]).

Whenever possible, use the SDBUPD program to perform the upgrade. This program givesyou comprehensive support for an upgrade without problems. However, you can only use it ifyou fulfill certain prerequisites. Otherwise, you must use a different upgrade strategy.

Prerequisites for Using SDBUPDSAP customers can use the program SDBUPD for upgrading database instances in SAPsystems . The SDBUPD program makes all required checks during the upgrade process.

You can also use this program to upgrade database instances that are not part of an SAPsystem . To do this, however, the following prerequisites must be fulfilled:

• The program SDBINST was used to install the existing software.

• Each of the existing database instances refers to a separate software installation.

ConventionsSee Variables [Extern] , Supported Operating Systems and Platforms [Extern]

Selection of the Upgrade Strategy

ProcedureSelect an upgrade strategy that is appropriate to the instance type [Extern] of the database

instance, and the source and target versions of the database software. Proceed as describedfor your chosen upgrade strategy.

If your database instance fulfills the necessary prerequisites, we recommendthat you use the program SDBUPD, since an upgrade with this programremoves the need for most of the user interaction, and is quicker and safer.

Upgrade Strategies for OLTP Database Instances

Target Version 7.5.x

Source Version from7.3.00 Build 025

In-Place Migration with SDBUPD [Seite 28 ] or*In-Place Migration with SDBINST [Seite29 ]

Source Version 7.4.03 Patc h Installation with SDBUPD [Seite 24 ] or*Patch Installation with SDBINST [Seite 26 ].

Source Version 7.2.00 Patch Installation with SDBUPD [Seite 24 ] or*Patch Installation with SDBINST [Seite 26 ]

* Use the SDBUPD program if your database instance is part of an SAP system.In special cases, you can use SDBUPD even if the database instance is not part of an SAP

system. See Prerequisites for Using SDBUPD under Upgrading Database Instances andTheir Software [Seite 22 ].




SAP AG March 2004

Upgrade Strategies for liveCache Database Instances

Target Version 7.5.00/410

Source Version 7.2.05/30A Upgrade with APO Extract/Load [Seite32 ]

Source Version 7.4.02/30A Upgrade with APO Extract/Load [Seite32 ]

Source Version 7.4.02/310 Upgrade with APO Extract/Load [Seite32 ]

Source Version 7.4.03/400 Upgrade with APO Extract/Load [Seite32 ]

Source Version 7.5.00/410 Patch Installation with SDBUPD [Seite24 ]

Patch Installation with SDBUPD

UseYou use the program SDBUPD to upgrade the database instance. When you do this, only thedatabase software is replaced.

You can use this procedure for software with Version 7.5x if only the build number of theversion [Extern] has changed between the source and target version, and also for upgrades

from 7.4.03 to 7.5x (see also Selection of the Upgrade Strategy [Seite 23 ]).You use this upgrade strategy if your database instance is part of an SAP system.

You can use this procedure even if the database instance is not combined with an SAPsystem. To do this, however, the following prerequisites must be fulfilled:

• The program SDBINST was used to install the existing software (that is, with a tgz package or a zip file, and not an rpm package)

• Each database instance refers to a separate software installation.

The procedure depends on whether your source version is lower than 7.5.00 or

7.5.00 or higher, and on which operating system you work.If you work on UNIX or Linux and your source version is lower than 7.5.00, thenyou must stop the X Server [Extern] and all database instances before theupgrade. Remember that this interrupts the communication between the clientsand all local database instances. If your source version is 7.5.00 or higher, thenthe X Server software supports an update of the database software while the XServer is running. You no longer need to stop the X Server. The databaseinstance that you want to upgrade is stopped by SDBUPD during the upgrade.

If you work on Microsoft Windows , you must always stop the X Server and alldatabase instances.




SAP AG March 2004

Prerequisites

Before you start upgrading a database instance, make sure that you have up-to-date log backups [Extern] and/or data backups [Extern] for recovering this

database instance in the event of errors.The database parameters of the database instance you want to upgrade mustnot have been changed since the last restart [Extern] .

• The database instance that you want to upgrade is the only instance that refers to theinstallation path of the software you want to update.

• The database instances is in one of the three defined operational states [Extern] , whichmeans that there are no errors.

Procedure...

1. If necessary, stop each database instance with the following command:

dbmcli –d <database_name> -u <dbm_user>, <password> db_offline 2. If necessary, stop the X Server.

x_server stop

3. Start the program SDBUPD for the database instance by entering the followingcommands:

UNIX, Linux: Microsoft Windows:

./SDBUPD –d <database_name> -u <dbm_user>,<password>[-o <sdb_user>-g <sdba_group>]

sdbupd –d <database_name> -u <dbm_user>,<password>

You only need to specify the special operating system user <sdb_user> andthe group <sdba_group> (according to the Authorization Concept for UNIXOperating Systems [Seite 33 ]) if you are upgrading to software version 7.5.00.

SDBUPD performs the upgrade, and displays a success message if the upgrade is completedsuccessfully. It then flags the installation as complete.

ResultThe database instance and its software have been upgraded.

If you have upgraded a liveCache [Extern] database instance, it is now in the operationalstate OFFLINE.

If you have upgraded an OLTP [Extern] database instance, it is now in the operational stateONLINE.




SAP AG March 2004

Patch Installation with SDBINST and Follow-UpActions

UseYou use the program SDBINST to upgrade database instances. When you do this, only thedatabase software is replaced. You must then perform the necessary follow-up actions in thecommand line with the Database Manager CLI [Extern] .

This upgrade strategy is valid for database instances of the type OLTP [Extern] only (seeSelection of the Upgrade Strategy [Seite 23 ]). It is valid for all supported operating systemplatforms [Extern] .

The procedure depends on whether your source version is lower than 7.5.00 or7.5.00 or higher, and on which operating system you work.

If you work on UNIX or Linux and your source version is lower than 7.5.00, thenyou must stop the X Server [Extern] and all database instances before theupgrade. Remember that this interrupts the communication between the clientsand all local database instances. If your source version is 7.5.00 or higher, thenthe X Server software supports an update of the database software while the XServer is running. In this case, you no longer need to stop the X Server and alldatabase instances. However, you do need to stop the database instance that isassigned to the installation directory that is being updated.


Prerequisites

Before you start the upgrade process, make sure that you have up-to-date logbackups [Extern] and/or data backups [Extern] for recovering the databaseinstances in the event of errors.

• All database instances that you want to upgrade refer to the same software installation.

Procedure...


dbmcli –d <database_name> -u <dbm_user>, <password> db_offline

2. If necessary, stop the X Server.

x_server stop

3. Start the SDBINST program with the options for installing the installation profile [Seite39 ] Server . Make sure that, for the <dependent_path> , you enter the correctsoftware installation path of the database instance or instances that you want toupgrade.

UNIX/Linux: Microsoft Windows:

./SDBINST [-b] -profile server -indep_data <independent_data_path> -indep_prog

<independent_program_path> -depend <dependent_path>

[-o <sdb_user> -g <sdba_group>]

sdbinst [-b] -profile server -indep_data <independent_data_path> -indep_prog

<independent_program_path> -depen d <dependent_path>




SAP AG March 2004

When you upgrade the software to Version 7.5.00, specify the special operatingsystem user <sdb_user> and the group <sdba_group> according to theauthorization concept for UNIX operating systems [Seite 33 ].

4. Start the X Server with the following command:x_server start

5. Log on again to each of the database instances in sequence as the DBM operator[Extern] , and perform the specified actions:

Procedure Command ...

1. Log on to the Database Manager CLIwith the data of the database instancethat you want to upgrade.

dbmcli –d <database_name> -u <dbm_user>, <password>

1. Update the software version of thedatabase instance.

db_reg

2. Update the parameters of thedatabase instance.

param_checkall

3. If you are upgrading to databaseversion 7.5.00 on a UNIX operatingsystem, then perform the followingsteps:

a. Log off from the Database ManagerCLI.

b. Call the program chvolperm . Thisprogram changes the owner, group,and access rights to the volumes ofthe database instance according to theauthorization concept for UNIXoperating systems.

c. Log on to the Database ManagerCLI again.

exit | release | quit | bye

<dependent_path>/bin/chvolperm –d <database_name>


4. Transfer the database instance to theoperational state WARM (up toVersion 7.3) or ONLINE (from Version7.4).

db_online | db_warm

5. Load the system tables.

You see a message about thesuccessful completion of theprocedure.

load_systab

6. Exit the Database Manager CLI. exit | re lease | quit | bye

ResultThe specified OLTP database instance and its software have been updated.

It is in the operational state ONLINE.




SAP AG March 2004

In-Place Migration with SDBUPD

UseYou use the program SDBUPD to upgrade the database instance [Extern] .

Use this procedure if the database instance is part of an SAP system.

This upgrade strategy is valid for the instance type OLTP [Extern] only. It is valid for allsupported operating system platforms [Extern] .

Prerequisites• The database instance you want to upgrade is part of an SAP system.

• The database instance is in the operational state [Extern] ONLINE.

• The database instance is the only instance that refers to the installation path of thesoftware version you want to update.

• The database parameters [Extern] of the database instance you want to upgrade havenot changed since the last restart.

• The source version of the database software is Version 7.3 Build 025 or higher, thetarget version is 7.5.00 or higher ( Selection of the Upgrade Strategy [Seite 23 ]).

Procedure...

Description Command

1. Log on to the Database Manager CLI and stopthe database instance that you want to upgrade.

If the existing X Server has a version lower than7.5, then use this command to stop all databaseinstances one by one.

dbmcli –d <database_name> -u <dbm_user>,<password>

db_offline

2. Transfer the database instance that you want toupgrade to the operational state COLD (up toVersion 7.3) or ADMIN (from Version 7.4).

db_cold | db_admin

3. If you have a newer data backup, make anincremental data backup and a log backup.Otherwise, make a complete data backup (seeBacking Up the Database Instance [Extern] ).

backup_start <medium> [<type>][AUTOIGNORE]

4. Exit the Database Manager CLI. exit | release | quit | bye

5. If the source version is lower than 7.5.00, stopthe X Server.

If your source version is 7.5.00 or higher, thenthe X Server software supports an update of thedatabase software while the database isrunning. In this case, you no longer need to stopthe X Server.

x_server stop

6. Stop the X Server if it has a source versionlower than 7.5.

x_server stop

7. Start SDBUPD.SDBUPD performs the upgrade, and displays a

UNIX/Linux:./SDBUPD –d <database_name> -u




SAP AG March 2004

success message if completed successfully. Itthen flags the installation as complete.

The execution of this command can take a longtime. Under no circumstances must youterminate it. If you do, you risk losing all yourdata. Your only option in this event is to usedata backups to go back to the state of thedatabase instance that is stored in thesebackups.

<dbm_user>,<password>[-o <sapdb_user>-g <sapdb_admin>]

You only need to specify the specialoperating system user <sdb_user> andthe group <sdba_group> (according tothe Authorization Concept for UNIXOperating Systems [Seite 33 ]) if you areupgrading to software version 7.5x.

Microsoft Windows:


ResultThe specified OLTP database instance and its software have been upgraded.

The database instance is in the operational state ONLINE.

In-Place Migration with SDBINST and Follow-Up

ActionsUseYou use the program SDBINST to upgrade database instances [Extern] from Version 7.3 to7.5. First you install the new version of the database software. Then you migrate the databaseinstance(s).

The source version of the database software is Version 7.3.00 Build 025 or higher, the targetversion is 7.5.00 or higher (see also Selection of the Upgrade Strategy [Seite 23 ]).

Use this procedure for database systems that are not part of an SAP system, particularly ifmultiple database instances refer to the same installation path.

This upgrade strategy is valid for database instances of the type OLTP [Extern] only. It is validfor all supported operating system platforms [Extern] .

Prerequisites• The database instance you want to upgrade is not part of an SAP system.

• You have a backup medium [Extern] for a complete data backup [Extern] .

Procedure

To guarantee the security of your data if any errors occur in the migration, werecommend that you make a complete data backup of the instance in step 6, inthe operational state [Extern] COLD. This causes downtime because thedatabase instance has to be stopped. However, in the event of an error, the




SAP AG March 2004

resulting data backup can be used to recover the database instance [Extern] inboth Version 7.3 and the target version.

Alternatively, you can make a complete data backup in the operational stateWARM before you start the migration. However, in the event of an error, you canuse this backup to recover the source version of the database instance only.Therefore, it is not equivalent to a data backup in the operational state COLDduring the migration process.

...

1. Install [Seite 6] the source version of the software with SDBINST ( zip file or tgz package) in the installation path <dependent_path><target_version> inparallel with the installation path of Version 7.3.

or

Install the software of the target version with the Red Hat Package Manager ( rpm package).

If you have installed Version 7.3 of the database software on your server with

the Red Hat Package Manager, you can now perform subsequent installationswith this program only. You can not use the SDBINST program for subsequentinstallations.

2. Perform the following migration steps for each of your database instances with thesource version.

Procedure Command...

1. Call the Database Manager CLI as theDBM operator and connect to the databaseinstance that you want to migrate.


1. Stop the database instance correctly

Use the commanddb_offline and notdb_stop . This is the onlyway of making sure you canrestart the database instanceif an error occurs.

db_offline

2. Transfer the database instance to theoperational state COLD.

db_cold

3. Execute the command that prepares themigration.

util_execute migrate

4. Open a utility session. util_connect

5. Make a complete data backup in theoperational state COLD.

backup_start <medium>

6. Exit the utility session. util_release

7. Transfer the database instance to theoperational state OFFLINE.

db_offline

8. UNIX:

Assign the database instance to the newsoftware version <target_version> .

Microsoft Windows:

Delete the registration of the database

UNIX:

db_reg –R <dependent_path><target_version>

Microsoft Windows:




SAP AG March 2004

instance. db_drop WITHOUTFILES

9. Exit the Database Manager CLI.

For Microsoft Windows only:

Register the installation path of the new

database software with the DatabaseManager and create a database instanceof this new software version.


dbmcli –R

<dependent_path><target_version>db_create –d <database_name> -u <dbm_user>,<password>

10. Log on to the Database Manager CLIagain.


11. Start the migration of the databaseparameters.

param_checkall

12. If you are upgrading to database version7.5.00 or higher on a UNIX operatingsystem, then perform the following steps.Otherwise, proceed as described underpoint 14:

a. Log off from the Database ManagerCLI.

b. Call the program chvolperm . Thisprogram changes the owner, group, andaccess rights to the volumes of thedatabase instance according to theauthorization concept for UNIX operatingsystems [Seite 33 ].

c. Log on to the Database Manager CLIagain.


<dependent_path>/bin/chvolperm –d <database_name>


13. Transfer the database instance to theoperational state ADMIN.

db_admin

14. Execute the migration command.

The execution of thiscommand may take sometime, depending on the size ofthe database instance. Do notcancel it under any

circumstances.

util_execute migrate database

15. Transfer the database instance to theoperational state OFFLINE.

db_offline

16. Restart the database instance. Thedatabase catalog is migrated from 7.3 tothe target version.

db_online

17. Reload the system tables.

You see a message about the successfulcompletion of the procedure.

load_systab

ResultYou have migrated your database instance from software version 7.3 to the required targetversion.




SAP AG March 2004

It is in the operational state ONLINE.

Upgrade with APO Extract/Load

Use You use the SDBUPD program for an upgrade with APO Extract/Load. You must first back upthe transaction data of the application system from the liveCache database instance to the

APO database, and then substitute the software ( Selection of the Upgrade Strategy [Seite23 ]).

This procedure is currently valid only for the instance type liveCache [Extern] in the SAP APOsystem. It is valid for all operating system platforms [Extern] supported by the databasesystem.

The procedure depends on whether your source version is lower than 7.5.00 or7.5.00 or higher, and on which operating system you work.

If you work on UNIX or Linux and your source version is lower than 7.5.00, thenyou must stop the X Server [Extern] and all database instances before theupgrade. Remember that this interrupts the communication between the clientsand all local database instances. If your source version is 7.5.00 or higher, thenthe X Server software supports an update of the database software while the XServer is running. In this case, you no longer need to stop the X Server and thedatabase instances.


Prerequisites• You have backed up the liveCache transactions to the APO database.

SAP customers can find information on this in the Service Marketplace underhttp://service.sap.com/instguides → Installation → Installation & UpgradeGuides → mySAP SCM → Using SAP SCM 4.1Server... → Upgrade Information→ Upgrade for SAP SCM 4.1: SAP liveCache 7.5 → Upgrade Preparations .

• The database parameters [Extern] of the database instance you want to upgrade havenot changed since the last restart [Extern] .

• The database instance can be in any operational state [Extern] .

Procedure...


dbmcli –d <database_name> -u <dbm_user>, <password> db_offline

2. If necessary, stop the X Server.

x_server stop

3. Start the SDBUPD program with the following command:UNIX, Linux: Microsoft Windows:




SAP AG March 2004

./SDBUPD –d <database_name> -u <dbm_user>,<password>[-o <sapdb_user>-g <sapdb_admin>]


You only need to specify the special operating system user <sdb_user> andthe group <sdba_group> (according to the Authorization Concept for UNIXOperating Systems [Seite 33 ]) if you are upgrading to software version 7.5.00.

4. SDBUPD performs the upgrade, and displays a success message if completedsuccessfully. You are prompted to start liveCache.

5. Start liveCache ( Starting liveCache [Extern] ).

6. Recover the data from the APO system to liveCache (see the above link to Upgrade forSAP SCM 4.1: SAP liveCache 7.5 .).

ResultThe specified liveCache database instance in the SAP APO system and its software havebeen upgraded.

liveCache is in the operational state ONLINE.

Authorization Concept for UNIX OperatingSystems

UseFor the execution of MaxDB programs and access to database files, the database softwarepackage contains a preconfigured authorization concept as of Version 7.5.00 . This conceptapplies to both installations within SAP systems, and to open source installations.

This concept includes the special operating system user <sdb_user> and the operatingsystem user group <sdba_group> .

If you manage operating system users and user groups locally on your host, werecommend that you register the names of the special operating system userand the user groups in the operating system before you start the installation.However, you can also do this during the installation process.

If you manage operating system users and user groups for your systemcentrally in the network , you must create them here before you start theinstallation.

For more information on creating operating system users and user groups, seeyour operating system documentation.

Special Operating System UserThe special operating system user is the owner of all the database software and databaseprocesses, which also makes this user the owner of, for example, the volumes [Extern] ,database trace [Extern] , and the database logs. This user is created once during the initial

installation of a database software package with version 7.5.00 or higher. The system defaultfor the user name is sdb .




SAP AG March 2004

3. You have attempted to update a 64 bit database kernel with software for a 32 bit kernel.This is not possible.

4. You are attempting to update the software with SDBINST. However, you have ignoredthe dependencies between the software components [Seite 40 ]; these dependenciesconcern the versions of the components or the order in which they need to be installed.

User ActionRemove the cause of the error and execute the program again.

Errors in the Execution of the Program SDBUPDIf errors occur when you execute the program SDBUPD, the program terminates with amessage about the cause of the error.

Frequent Causes of Errors...

1. An unexpected error occurred when you executed SDBUPD.

2. You are attempting to use SDBUPD to switch to a software version that is lower thanyour current version (in the following called a downgrade). Examples of this situation:

You have selected the wrong software version by mistake.

The upgrade of the database instance terminated with an error. You then tried touse SDBUPD to return to the original software version.

The database instance upgrade was successful, however, you want to return toa lower software version for other reasons.

You cannot use SDBUPD to downgrade software. If you want to use SDBUPD, the newsoftware must have at least a higher build number ( Version Notation [Extern] ).

User ActionProceed as follows in each case.

Case 1: [Seite 35 ]

No database instances exist that refer to a higher software version.

Case 2: [Seite 36 ]

Database instances exist that refer to a higher software version. You want to downgrade thesoftware that is used exclusively by the database instance (Dependent Software).

Case 3: [Seite 38 ]

Database instances exist that refer to a higher software version. You want to downgrade thesoftware that is not used by the database instance, or whose version is not relevant for thedatabase instance (Independent Software).

Case 1: No Database Instances Exist Yet

UseNo database instances exist that refer to a higher software version.

Procedure Either uninstall the entire database software with SDBUNINST




SAP AG March 2004

• If the downgrade is combined with a change of version (minor or major release, seealso: Version Notation [Extern] ) of the database software, proceed as follows:

Procedure Command

Call the Database Manager CLI asthe DBM operator and connect tothe database instance.


1. Delete the database instance db_drop

2. Exit the Database Manager CLI. exit | release | quit | bye

3. Uninstall at least the databasekernel and the chosen softwarecomponent(s) with the higherversion.

sdbuninst –package "Database Kernel"[, <package_name2>…]

4. Install your chosen installationprofile with the lower version (forOLTP database instances at leastServer , for liveCache databaseinstances at least APO liveCache ).

If you are installing thesoftware in SAP systems, read theimportant note below.

sdbinst –profile Server | "APOLiveCache" [, <inst_profile2>…]

5. Start the Database Manager GUI.Use the Installation Wizard tocreate a new database instance byusing the parameter file from abackup.

Choose Instance → Install.Follow the instructions for creating or initializing adatabase instance [Extern] . For the newdatabase instance, specify the databaseadministrator that is saved in the backupparameter file.

6. Exit the Database Manager GUI. Choose File → Exit .

If you want to use this procedure in SAP systems , do not accept the systemdefaults. Specify the following settings instead:

<group> For target version 7.5.00 or higher: sdba

For all previous database versions: sapsys

<owner> For target version 7.5.00 or higher always: sdb

For all previous database versions

• For OLTP database instances: sqdsid • For liveCache database instances:

sidad m

<independent_data_path> UNIX/Linux: /sapdb/data

Microsoft Windows: <drive>:\sapdb\data

<independent_program_path> UNIX/Linux: /sapdb/programs

Microsoft Windows:<drive>:\sapdb\programs

<dependent_path> UNIX/Linux: /sapdb/<SID>/db

Microsoft Windows:<drive>:\sapdb\<SID>\db




SAP AG March 2004

Case 3: Downgrade for Independent SoftwareUseDatabase instances exist that refer to a higher software version. You want to downgrade thesoftware that is not used by the database instance, or whose version is not relevant for thedatabase instance (Independent Software).

ProcedureAction Command

...

1. Uninstall at least the database kernel and

the chosen software component(s) with thehigher version.

sdbuninst –package "Database

Kernel" [, <package_name2>…]

2. Install your chosen installation profile withthe lower version (for OLTP databaseinstances at least Server , for liveCachedatabase instances at least APOliveCache ).

If you are installing the software in SAPsystems, read the important note below.

sdbinst –profile Server | "APOLiveCache" [, <inst_profile2>…]

If you want to use this procedure in SAP systems , do not accept the systemdefaults. Specify the following settings instead:

<group> For target version 7.5.00 or higher: sdba

For all previous database versions: sapsys

<owner> For target version 7.5.00 or higher always: sdb

For all previous database versions

• For OLTP database instances: sqdsid

• For liveCache database instances: sidadm

<independent_data_path> UNIX/Linux: /sapdb/data

Microsoft Windows: <drive>:\sapdb\data

<independent_program_path> UNIX/Linux: /sapdb/programs

Microsoft Windows: <drive>:\sapdb\programs

<dependent_path> UNIX/Linux: /sapdb/<SIS>/db

Microsoft Windows: <drive>:\sapdb\<SID>\db




SAP AG March 2004

Detailed InformationInstallation Profiles [Seite 39 ]

Software Components [Seite 40 ]

Logging [Seite 42 ] Overview of Options for the Program SDBINST [Seite 43 ]

Overview of Options for the Program SDBUNINST [Seite 43 ]

Overview of Options for the Program SDBUPD [Seite 44 ]

Installation ProfilesInstallation profiles are different combinations of individual software components [Seite 40 ],which meet different requirements. An installation profile provides you with a fully functioningsoftware installation, regardless of which profile you choose.

If you install individual software components (parts of installation profiles), you must take intoaccount the dependencies between the components to guarantee that the softwareinstallation can function.

Choose from the following installation profiles:

Name Included Software Components Installation/Update of

all All software components Complete softwarepackage

Server Base, multiple PCR <version>,server utilities, ODBC, DB Analyzer,database kernel, JDBC, Loader

Server software andclient software of theOLTP database system

Web Tools Base, ODBC, Web Tools, XMLIndexing Engine

Web Tools

DB Analyzer Base, ODBC (for MS Windowsonly), DB Analyzer

Database Analyzer

Runtime for SAP AS Base, multiple PCR <version>,JDBC, Loader

Client software for theSAP application server

APO LiveCache For liveCache in the SAP APOsystem only

Base, multiple PCR <version>,Server Utilities, ODBC (MSWindows only), DB Analyzer,Database Kernel, APO LC APPS or

APO COM (up to APO Version 4.0)

Server software andclient software of theliveCache database

system

C Precompiler Base, multiple PCR <version>, CPCBase, CPC SDK <version>

Software required fordeveloping precompilerapplications

Script Interface Base, Perl Interface, PythonInterface

Runtimes for applicationsthat use programminginterfaces

XML Indexing Engine Base, ODBC, XML Indexing Engine XML Indexing Engine

Loader Base, Loader Loader tool




SAP AG March 2004

JDBC Base, JDBC MaxDB JDBC Driver

You must place any names of software components that contain blanks indouble quotation marks.

Software Components

UseYou install installation packages that contain only individual components of the databasesoftware. You can do this to install missing components without updating components thatyou do not need.

The installation of software components is more complex than the installation of installationprofiles [Seite 39 ], and demands that the user understands and takes into account thedependencies determined by the content or versions of the software.

Since this installation is not interactive and can run in the background only, you must inadvance determine any other components you need to install first, and in which order. Theinstallation program terminates the installation as soon as it recognizes that a dependencyhas been ignored. For this reason, use this installation type in special cases only.

The database software is split into the following components:

Name Description

Base Programs for registering the installation, uninstallation tool,InstallRegistryViewer, and programs that the SAP application server needsto access the database system (including XUSER and SQLCLI)

PCR<version> Precompiler Runtime PackageContains runtime libraries for applications created with the C/C++Precompiler for Embedded SQLCan exist in multiple versions in the local installation directory

Server Utilities Tools for the administration of the database kernel (including DatabaseManager CLI, XPU and XCONS)

Database Kernel Database kernel with runtime environment

CPC Base C++ Precompiler base (call programs for the precompiler)

CPC SDK <version> C++ Precompiler

ODBC

ODBC driver

DB Analyzer Database Analyzer: Tool for analyzing database performance

Web Tools Web Server and Web-based database tools (WebDBM, WebSQL,WebDAV)

Python Interface Python interface

Perl Interface Perl interface

XML IndexingEngine

XML Indexing Engine; can be installed on a computer other than thedatabase host to improve performance

Loader Loader: tool for loading and unloading data

JDBC

MaxDB JDBC driver for accessing the MaxDB database system

APO LC APPS (from For SAP liveCache in the SAP APO system only: Libraries with APO




SAP AG March 2004

APO Version 4.0) or APO COM

liveCache routines

You must place any names of software components that contain blanks in

double quotation marks.

DependenciesThe following dependencies exist between software components:

Base → PCR <version>Base → Server Utilities → Database Kernel → APO LC APPS | APO COMBase [ → ODBC]* → DB AnalyzerBase → ODBC → Web ToolsBase → CPC BaseBase → CPC Base → CPC SDK <version>Base → PerlBase → PythonBase → ODBC → XML Indexing Engine Base → LoaderBase → JDBC

* Required for DB Analyzer on Microsoft Windows only

Explanation of Dependencies• The Base software component is independent of all other packages.

• PCR <version> cannot be installed until Base has been installed.

• Server Utilities cannot be installed until Base has been installed.

Database Kernel cannot be installed until Server Utilities has been installed.

APO LC APPS or APO COM cannot be installed until Database Kernel hasbeen installed

• DB Analyzer cannot be installed until you have installed Base (on UNIX) or Base andODBC (on Microsoft Windows).

• ODBC cannot be installed until Base has been installed.

Web Tools cannot be installed until ODBC has been installed.

• CPC Bases cannot be installed until Base has been installed.

CPC SDK <version> cannot be installed until CPC Base has been installed.

• Perl cannot be installed until Base has been installed.

• Python cannot be installed until Base has been installed.

• ODBC cannot be installed until Base has been installed.

XML Indexing Engine cannot be installed until ODBC has been installed.

• Loader cannot be installed until Base has been installed.

• JDBC cannot be installed until Base has been installed.




SAP AG March 2004

Logging

Use All installation/update [Seite 6] steps and the steps involved in upgrading database instances

and their software [Seite 22 ] are saved in log files. The name of the log file containsinformation on the product name MaxDB or SAP liveCache.

Conventions

Variables [Extern]

Location of Log Files for Installations/Updates

• UNIX/Linux ( tgz package):<independent_data_path>/wrk/MAXDB<profile>_install-<date>-<time>.log

or

<independent_data_path>/wrk/SAPliveCache<profile>_install-<date>-<time>.log

• Microsoft Windows:<independent_data_path>\wrk\MAXDB<profile>_install-<date>-<time>.log

or

<independent_data_path>\wrk\SAPliveCache<profile>_install-<date>-<time>.log

If the <independent_data_path> directory is not yet known when the installation processcrashes, the log will be created in the current directory.

If you have installed/updated individual software components, the steps arelogged in the fileMAXDBSoftware_install-<date>-<time>.log

or

SAPliveCacheSoftware_install-<date>-<time>.log

Location of the Log File for Updates of Database Instances and Their Software(Upgrades)

• UNIX/Linux ( tgz package):<independent_data_path>/wrk/MAXDBUpgrade_install-<date>-<time>.log or

<independent_data_path>/wrk/SAPliveCacheUpgrade_install-<date>-<time>.log

• Microsoft Windows:<independent_data_path>\wrk\MAXDBUpgrade_install-<date>-<time>.log

or

<independent_data_path>\wrk\SAPliveCacheUpgrade_install-<date>-<time>.log




SAP AG March 2004

Overview of Options for the Program SDBINSTYou can specify the following options when you use the program SDBINST to install orupdate database software:

Option Description-b | -batch Use installation program in the background

If you specify this option, the installation programterminates with an error if any information is missing.

If you do not specify this option, the program stops ifany information is missing, and prompts you to act.

-profile <inst_profile> Installation profile [Seite 39 ]

You must place any names that contain blanks indouble quotation marks.

-package <package_name> Logical name of the software component [Seite 40 ] (not file name)

You must place any names that contain blanks indouble quotation marks.

-indep_data <independent_data_path>

Can be specified for an initial SAP DB installation only.Otherwise, the system ignores it. You can change thispath only after completely uninstalling the databasesoftware.

-indep_prog <independent_program_path>

Can be specified for an initial SAP DB installation only.Otherwise, the system ignores it. You can change thispath only after completely uninstalling the databasesoftware.

-depend <dependent_path> Needs to be specified for a new installation only, andonly for the installation profiles all , Server and APOLiveCache and the software components DatabaseKernel and APO LC APPS (from APO Version 4) or

APO COM . Otherwise, the system ignores it.

-o | -owner <sdb_user> UNIX only: Software owner

-g | -group <sdb_group> UNIX only: Group of the software (administrator group)

-h | -help List of options and descriptions

-v | -version Version number of the SDBINST installation program

-l | -list Display all possible installation profiles and softwarecomponents

See also: Variables [Extern]

Overview of Options for the Program SDBUNINST You can specify the following options when you use the program SDBUNINST touninstall database software:

Option Description




SAP AG March 2004

-all Uninstalls all software registered for MaxDB

-package <package_name>

Logical name of the software component [Seite 40 ] (not filename) that you want to uninstall

-package_dir <package_directory>

Directory of the specified software componentSpecify this information only if there are multiple softwarepackages with the same name

-autoresolve As well as the specified software component, the systemalso uninstalls all dependent components.

-package ODBC –autoresolve

On Microsoft Windows, the component ODBC and its dependent component Web Tools areuninstalled.


-v | -version Version number of the uninstallation program SDBUNINST

-l | -list Display all possible software components

Overview of Options for the Program SDBUPDYou can specify the following options when you use the program SDBUPD to upgradedatabase instances from Version 7.3 to Version 7.4:

Option Description

-b | -batch Use SDBUPD in the background

If you specify this option, the installation program terminateswith an error if any information is missing.

If you do not specify this option, the program stops if anyinformation is missing, and prompts you to act.

-d <database_name> Name of the database instance [Extern]

-u <dbm_user>,<password> Name and password of the DBM operator [Extern]


-v | -version Version number of SDBUPD

-l | -list Display all possible installation profiles [Seite 39 ] and softwarecomponents [Seite 40 ]

-o <sdb_user> Owner of the software (UNIX only) when you upgrade thesoftware to Version 7.5.00, according to the authorizationconcept [Seite 33 ]

-g <sdba_group> Administrator group (UNIX only) when you upgrade thesoftware to Version 7.5.00




SAP AG March 2004

instman eng

Documents