Database Upgrade GuideUpgrade to SAP MaxDB Database 7.7: Windows

Target Audience

n Technology Consultantsn System Administrators

PUBLICDocument version: 1.02 ‒ 08/15/2008

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version at the following location:

Only valid for: SAP NetWeaver

http://service.sap.com/instguides

End of: SAP NetWeaver

The following table provides an overview of the most important document changes.

Version Date Description

1.02 8/15/2008 Update to specify that Max DB 7.7 is released for SAP Basis 7.0 SR3

1.01 7/29/2008 Various changes, now including Database Studio

1.00 1/26/2007 Initial Version

2/36 PUBLIC 08/15/2008

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 51.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 61.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . 61.2.1 SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . 61.2.2 More Information on SAP Service Marketplace . . . . . . . . . . . 71.2.3 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Database Requirements . . . . . . . . . . . . . . . . . . . . 92.2 Operating System Requirements . . . . . . . . . . . . . . . . . 102.3 SAP System Requirements . . . . . . . . . . . . . . . . . . . 102.4 Upgrade Strategy . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Preparing for an Upgrade with In-Place . . . . . . . . . . . . . . 133.2 Preparing for an Upgrade with Patch Installation . . . . . . . . . . . 14

Chapter 4 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . 174.1 Performing an Upgrade for In-Place . . . . . . . . . . . . . . . . 174.2 Performing an Upgrade for Patch Installation . . . . . . . . . . . . 184.3 Upgrading the SAP MaxDB Client Software . . . . . . . . . . . . . 19

Chapter 5 Post-Upgrade . . . . . . . . . . . . . . . . . . . . . . . 215.1 Performing Post-Upgrade Steps After an In-Place Upgrade . . . . . . . 215.2 Updating the Database Software to the Current Release . . . . . . . . 225.3 Installing or Upgrading Database Studio for SAP MaxDB . . . . . . . . 225.4 Secure Sockets Layer Protocol for Database Server Communication . . . . 245.4.1 Installing the SAP Cryptographic Library . . . . . . . . . . . . . . 245.4.2 Generating the Personal Security Environment . . . . . . . . . . . 26

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 296.1 Database Directory Structure . . . . . . . . . . . . . . . . . . 296.2 Sample Directory Structure . . . . . . . . . . . . . . . . . . 306.3 Log Files for Troubleshooting . . . . . . . . . . . . . . . . . . 31

08/15/2008 PUBLIC 3/36

4/36 PUBLIC 08/15/2008

1 Introduction

1 Introduction

This documentation explains how to upgrade the SAP MaxDB database for the SAP system:

n From at least SAP DB version 7.3.00.25n To SAP MaxDB version 7.7

If you have SAP DB version 7.3 with a non-Unicode database catalog you must upgrade to 7.6separately before upgrading to SAP MaxDB version 7.7.

Note

If your initial SAP DB version is 7.3, you can check whether it has a non-Unicode database catalog inone of the following ways:

n In the Database Manager, choose Configuration Parameters Extended .

n In the Database Studio, choose Administration Parameters Extended .

n As user sidadm, enter the following command:dbmcli –d <DBSID> -u <dbm user>, <dbm password> param_directget _UNICODE

If you see _UNICODE = YES, this means that you have a Unicode database catalog, so you canupgrade directly to version 7.7.If you see _UNICODE =NO, this means that you have a non-Unicode database catalog, so you mustfirst upgrade to version 7.6, then later to 7.7. You can find SAP MaxDB RDBMS DVDs for the upgradeto 7.6 in the SAP Software Distribution Center (SWDC) at:https://service.sap.com/swdc Download Database Patches MaxDB and SAP DB

You can find the upgrade guide to version 7.6 at the link shown immediately below.

Caution

Make sure you have the latest version of this document. See the version number on the frontpage. You can always find the latest version at:https://service.sap.com/instguides Other Documentation Database Upgrades SAP MaxDB

Implementation Considerations

n Make sure that you read the relevant SAP Notes [page 6] before beginning the upgrade. Thesenotes contain the most recent information about the upgrade, as well as corrections to thedocumentation.

08/15/2008 PUBLIC 5/36

1 Introduction1.1 New Features

n The SAP DB database has been re-branded and is now being delivered as the SAP MaxDB database,starting with release 7.5.00. Therefore, as of SAP Web Application Server 6.40, SAP DB has beenreplaced by SAP MaxDB.

n For more information on SAP MaxDB, see the following:www.mysql.com/products/maxdb

1.1 New Features

For more information on the new features for SAP MaxDB version 7.7, see:https://www.sdn.sap.com/irj/sdn/maxdb

For more information on the most important enhancements and features for version 7.7, see SAPNote 1006496.

Note

As of SAP MaxDB version 7.6, support packages and patch levels have been introduced. For moreinformation, see SAP Note 820824.

1.2 Before You Start

Make sure that you read the following sections before you start the upgrade:

n SAP Notes for the Upgrade [page 6]n Information Available on SAP Service Marketplace [page 7]n Naming Conventions [page 7]

1.2.1 SAP Notes for the Upgrade

Read the SAP notes before you begin the upgrade. Make sure that you have the most recent versionof each SAP Note, which you can find at:http://service.sap.com/notes

The following notes contain information relevant to the upgrade:

SAP Note Subject

1004973 Additional Information for Upgrade to MaxDB 7.7

820824 Frequently Asked Questions (FAQ): MaxDB

498036 Overview note on importing database versions

34690 Add Devspace

201390 Database Backup

6/36 PUBLIC 08/15/2008

1 Introduction1.2 Before You Start

SAP Note Subject

508979 SAP DB/MaxDB/liveCache-Upgrade mit MSCSCluster Var.1

843560 SAP DB/MaxDB/liveCache-Upgrade mit MSCSCluster Var.2

Caution

Before you begin the upgrade, always make sure that you read the first SAP Note listed above,1004973, because it contains up-to-date information essential to the upgrade, including correctionsnot contained in this upgrade documentation.This note also contains the valid DVD numbers for SAP MaxDB 7.7.

1.2.2 More Information on SAP Service Marketplace

You can find more information on SAP Service Marketplace as follows:

Description Address

Database upgrade guides http://service.sap.com/instguidesOtherDocumentationDatabase UpgradesMaxDB

Product Availability Matrix (PAM) http://service.sap.com/pam

SAP Notes http://service.sap.com/notes

Support Packages and patches http://service.sap.com/patches MaxDBMAXDB GUI COMPONENTS/TOOLS

1.2.3 Naming Conventions

We use the following naming conventions in this documentation:

n ReleaseUnless otherwise specified, we use “release” to refer to the release of SAP NetWeaver

n SAP MaxDB nameDBSID refers to the SAP MaxDB name. For <DBSID> you need to substitute your SAP MaxDBname, for example, MDB.

n SAP system nameSAPSID refers to the SAP system name. Pay attention to lowercase or uppercase. If <SAPSID> is used,insert your SAP System name, for example, PRD.

n <SAPSID> user nameThe user name is written in uppercase and abbreviated with <SAPSID>ADM.

08/15/2008 PUBLIC 7/36

1 Introduction1.2 Before You Start

Caution

Always enter the user name <sapsid>adm in lowercase for the standalone database server.

n Support Packages and patchesFor more information, see:http://service.sap.com/patches

n SAP MaxDB operational statesThere are the following SAP MaxDB operational states:

SAP MaxDB State Identifier SAPDB<= 7.3.00 State Identifer Meaning

ONLINE WARM The database instance has beenstarted and users can log on.

ADMIN COLD The database instance is onlyavailable to administrators.

OFFLINE OFFLINE The database instance is notrunning.

In this documentation we use the SAPMaxDB state identifiers, not the outdated SAPDB identifiers.

8/36 PUBLIC 08/15/2008

2 Planning

2 Planning

Prerequisites

You have checked the SAP Notes for the upgrade [page 6].

Process Flow

You have to complete the following planning activities:

1. You check the database requirements [page 9].2. You check the operating system requirements [page 10].3. You check the SAP system requirements [page 10].4. You choose an upgrade strategy [page 11].

2.1 Database Requirements

As part of the upgrade planning [page 9], make sure that your database meets the following requirementsbefore you start the upgrade:

n The database is ready to run.n The system tables have been loaded at least once for the existing instance.n The database instance is the only instance that refers to the installation path of the software

version that you want to upgrade.n The database parameters of the database instance that you want to upgrade have not changed

since the last restart.n The upgrade is supported for your instance type. For the instance types supported with this

upgrade see SAP Note 1004973.n The database start version ‒ that is, before you start the upgrade ‒ is at least 7.3.00.25

Note

If your database start version is SAP DB version 7.3 with a non-Unicode database catalog you mustupgrade to 7.6 separately before upgrading to MaxDB version 7.7.For more information on how to check whether the database catalog is non-Unicode, see here [page 5].

08/15/2008 PUBLIC 9/36

2 Planning2.2 Operating System Requirements

Caution

If the database start version does notmeet the above requirement, youmust upgrade to this versionbefore starting the upgradeFor more information on how to upgrade to the correct database start version, see SAP Note 498036.

2.2 Operating System Requirements

As part of the upgrade planning [page 9], make sure that your operating system meets the followingrequirements before you start the upgrade:

Operating System Supported Version

Windows 2003

Windows IA64 2003

Windows X64 2003

For the most up-to-date SAP MaxDB-specific release information on the database and operatingsystem of your product, including required patch levels, check the SAP Product Availability Matrix(PAM) at:http://service.sap.com/pam

There you can also find additional information on required operating system patch levels andpatches for C++ RTE.

2.3 SAP System Requirements

As part of the upgrade planning [page 9], make sure that your SAP system meets the followingrequirements before you start the upgrade:

n SAP MaxDB Version 7.7 is initially released for SAP Basis Release 7.0 SR3, Release 7.10, andsubsequent releases.

n For previous database versions, the following SAP Notes describe the operating system releases foreach SAP release, but do not contain information about future releases:

Note Number Title

407320 Released operating systems SAP R/3 kernel 6.x SAP DB / MaxDB

156551 Released operating systems for SAP kernel 4.6x SAP DB / MaxDB

85841 Released operating systems for SAP Kernel 4.0x/4.5x SAP DB / MaxDB

23870 Released operating systems for R/3 3.0x/3.1x SAP DB / MaxDB

10/36 PUBLIC 08/15/2008

2 Planning2.4 Upgrade Strategy

Note

Not all the combinations of database and operating system specified in the above notes are releasedfor all solutions of SAP Business Suite based on SAP Basis, SAP Web Application Server, or SAPNetWeaver.The solutions of SAP Business Suite are based on the kernel technology of SAP Basis, SAP WebApplication Server, or SAP NetWeaver, but might have certain release restrictions.For more information, see the Product Availability Matrix (PAM) at:http://service.sap.com/pam

You can also find the information in the above SAP Notes at:http://service.sap.com/notes

2.4 Upgrade Strategy

As part of the upgrade planning [page 9], you choose an upgrade strategy, which depends on yourdatabase start version:

Your DatabaseStart Version Your Upgrade Strategy

7.3.00 or later In-Place UpgradeWith an In-Place upgrade, you upgrade the database instance and thedatabase software.The start version of the database software must be Version 7.3.00 or later andthe target version must be 7.7 or laterFor an In-Place upgrade, the software has a significant amount of newfunctionality that could cause incompatibilities between the existing dataand the new software.Therefore, the adaptations to the new database functionality and structuresare made internally during an In-Place upgrade.

7.7 Patch InstallationWith a patch installation, you only upgrade the database software.You can use this procedure if the only difference between the source andtarget version is the build number.For a patch installation, the software does not have a significant amount ofnew functionality that could cause incompatibilities between the existingdata and the new software.

08/15/2008 PUBLIC 11/36

This page is intentionally left blank.

3 Preparation

3 Preparation

Prerequisites

You have completed planning the upgrade [page 9].

Process Flow

You have to complete the following preparations:

1. If your upgrade strategy is In-Place, you prepare for an In-Place upgrade [page 13].2. If your upgrade strategy is Patch installation, you prepare for an upgrade with Patch installation [page 14].

3.1 Preparing for an Upgrade with In-Place

As part of the upgrade preparations [page 13] for an In-Place upgrade, you need to perform the preparationsdescribed below.

Procedure

1. Make sure that the operational state [page 7] of your database is ONLINE.2. In case you need to recover the database, make sure that you have an installation kit with the start

version of the database software. This means that you must have database Version 7.3.00, 7.4.03,7.5.00, or 7.6 with the same or a higher build.

3. Check the required free space in the database. You need at least 15% free space.4. Check that there are no bad indexes in the database, using the Database Studio or the Database

Manager GUI.For more information about how to remove bad indexes, see SAP Note 566883.

5. Shut down the SAP system using the SAP Microsoft Management Console (SAP MMC).For more information about SAP MMC, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library ‒ English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution MonitoringMonitoring in the CCMS SAP Microsoft Management Console: Windows

6. Bring the database to operational state OFFLINE using the Database Manager CLI commanddb_offline, Database Manager GUI, or Database Studio.If the existing X Server has a version lower than 7.5 (this is the case if you are installing the softwarefor SAP MaxDB version 7.5.00 for the first time), use this command to stop all SAP DB or SAPMaxDB database instances that exist on your system one by one.

08/15/2008 PUBLIC 13/36

3 Preparation3.2 Preparing for an Upgrade with Patch Installation

7. Bring the database to operational state ADMIN using Database Manager CLI command db_cold |

db_admin, Database Manager GUI, or Database Studio.8. Set up the database so that it can be recovered:n If you have a recent data backup, make an incremental data backup and a log backup.n Otherwise, make a complete data backup

Caution

If you do not have a backup, you might lose data in the event of a database failure that requiresdatabase recovery.After the backup, do not put the database in operational state ONLINE before the upgrade.

9. Exit the Database Manager CLI, GUI, or Database Studio and any other database applicationsthat are running.

10. Stop the X Server if it has a source version lower than 7.5:x_server stop

Caution

There must be no remote communication between the database and applications during theupgrade, since the V Server software (X Server service) might need to be switched, depending onthe source and target version of the upgrade.

11. If you need to upgrade your operating system do this now.

3.2 Preparing for an Upgrade with Patch Installation

As part of the upgrade preparations [page 13] for an upgrade with Patch installation, you need to performthe preparations described below.

Procedure

1. Make sure that the operational state [page 7] of your database is ONLINE, ADMIN, or OFFLINEwithout any errors.

2. Stop application software ‒ such as Database Studio, Database Manager CLI or GUI ‒ and thedatabase that you intend to upgrade, so that you can run a full backup. In this case, you do notneed to stop the X server.

14/36 PUBLIC 08/15/2008

3 Preparation3.2 Preparing for an Upgrade with Patch Installation

Caution

If your database version is 7.4.03 or higher, the upgrade tool does not check whether a databasebackup is available.However, always perform a database backup before the upgrade, so that you can recover thedatabase in the event of data loss.

08/15/2008 PUBLIC 15/36

This page is intentionally left blank.

4 Upgrade Process

4 Upgrade Process

Prerequisites

You have completed preparing for the upgrade [page 13].

Process Flow

You have to complete the following to perform the upgrade:

1. If your upgrade strategy [page 11] is In-Place, perform the upgrade for In-Place [page 17].2. If your upgrade strategy [page 11] is Patch installation, perform the upgrade for Patch installation [page 18].3. If required, you upgrade the SAP MaxDB client software [page 19].

4.1 Performing an Upgrade for In-Place

As part of upgrading the database [page 17], you perform this procedure to upgrade your database if yourchosen upgrade strategy [page 11] is In-Place.

Prerequisites

Note

If your start version has a non-Unicode database catalog, the upgrade can take a long time to finish,especially the following steps:

n Migrate database

n Migrate catalog to Unicode

Never terminate the upgrade.If you terminate the upgrade, you risk losing all your data. Your only option then is to use databackups to recover the database instance, which is risky and time-consuming.

Procedure

Caution

Start the upgrade at the command prompt. If you start it using the Explorer, error messages arenot always displayed.

1. Log on as a user with administrator rights.

08/15/2008 PUBLIC 17/36

4 Upgrade Process4.2 Performing an Upgrade for Patch Installation

2. Load the Max 7.7 DVD in the drive.3. Change the directory to:

<MaxDB DVD>:\

Note

If your DVDs are enabled for Media Independent Delivery (MID) 7.10, change instead to thefollowing directory:<MaxDB DVD>:\DATA_UNITS\UPDATE\

4. Start the upgrade as follows:DBUPDATE.BAT –d <DBSID> -u <DBM,DBM password> [ -dir <temporary directory> ]

Note

The default temporary directory is C:\temp. If you want to change this setting, use the –dirparameter.

ResultWhen you see the message confirming that the upgrade has completed successfully, this means that:

n The database instance and its software is now upgraded.n The database instance is in the operational state ONLINE.n The upgrade is flagged as complete.

4.2 Performing an Upgrade for Patch Installation

As part of upgrading the database [page 17], you perform this procedure to upgrade your database if yourchosen upgrade strategy [page 11] is Patch installation.

Procedure

Caution

Start the upgrade at the command prompt. If you start it using the Explorer, error messages arenot always displayed.

1. Log on as a user with administrator rights.2. Load the SAP MaxDB 7.7 DVD in the drive.3. Change the directory to:

<MaxDB DVD>:\

18/36 PUBLIC 08/15/2008

4 Upgrade Process4.3 Upgrading the SAP MaxDB Client Software

Note

If your DVDs are enabled for Media Independent Delivery (MID) 7.10, change instead to thefollowing directory:<MaxDB DVD>:\DATA_UNITS\UPDATE

4. Start the upgrade tool as follows:DBUPDATE.BAT –d <DBSID> -u <DBM,DBM password> [ -dir <temporary directory> ]

Note

The default temporary directory is C:\temp. If you want to change this setting, use the –dirparameter.

ResultWhen you see the message confirming that the upgrade has completed successfully, this means that:

n The database software is now upgraded.n The database instance is in the operational state ONLINE.n The upgrade is flagged as complete.

4.3 Upgrading the SAP MaxDB Client Software

If required, as part of upgrading the database [page 17], you can upgrade the database client software for thehost where the SAP central or dialog instance runs

PrerequisitesSAP Note 822239 describes how to check the client software version.You do not need to update the client software if:

n The database instance is on the same host as the SAP instance.

n You already have client software 7.6 (valid for SAP Basis 7.10 or higher) ‒ but in this case werecommend you to always use the latest client software.

n The SAP central or dialog instance only connects to an SAP content server running on SAPMaxDB.

If you need to get the latest client software, see SAP Note 649814, which describes how to download itfrom SAP Service Marketplace.Stop the following:

n The central and dialog instancen Any other SAP MaxDB instances that are running on the central or dialog instance server

In this case, also stop the server for Remote SQL using the following command:x_server stop

n All DBMGUI, SQL Studio, and DBMCLI sessions.

08/15/2008 PUBLIC 19/36

4 Upgrade Process4.3 Upgrading the SAP MaxDB Client Software

Procedure

1. Log on as a user with administrative rights.2. Load the SAP MaxDB 7.7 DVD in the drive.3. Start the client software upgrade:

<MaxDB DVD>:\DBUPDATE.BAT -client

Note

If your DVDs are enabled for Media Independent Delivery (MID) 7.10, enter the following insteadto start the client software upgrade:<MaxDB DVD>:\DATA_UNITS\UPDATE\DBUPDATE.BAT -client

4. Log on again as a user with administrator rights.

Note

Make sure that you log on from the beginning, because the environment of <sapsid>adm hasbeen changed.

5. Restart the SAP system using the SAP Microsoft Management Console (SAP MMC).For more information about SAP MMC, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library ‒ English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution MonitoringMonitoring in the CCMS SAP Microsoft Management Console: Windows

20/36 PUBLIC 08/15/2008

5 Post-Upgrade

5 Post-Upgrade

Prerequisites

You have completed the upgrade [page 17].

Process Flow

You have to complete the following post-upgrade steps:

1. If your upgrade strategy [page 11] is In-Place, perform post-upgrade steps after an In-Place upgrade [page 21].2. You update the database software to the current release [page 22].3. You install or upgrade Database Studio [page 22].4. If required, you set up Secure Sockets Layer (SSL) protocol for database server communication [page 24].

5.1 Performing Post-Upgrade Steps After an In-PlaceUpgrade

As part of the post-upgrade [page 21] steps, you perform this procedure if your chosen upgrade strategy [page11] is In-Place.

Procedure

1. Perform a complete backup of the database data so that you can recover the new database ifnecessary.

Caution

We do not guarantee that you can recover the database using backups from different versionsof the database.

2. If your start version was 7.3.00 delete the system devspace. This is no longer required from databaseversion 7.4 because the Converter is now set up in the data area. You can find the system devspacein the following directory:\<sapdb-directory>\<DBSID>\dbsys

3. Start the SAP system using the SAP Microsoft Management Console (SAP MMC).For more information about SAP MMC, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library ‒ English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution MonitoringMonitoring in the CCMS SAP Microsoft Management Console: Windows

08/15/2008 PUBLIC 21/36

5 Post-Upgrade5.2 Updating the Database Software to the Current Release

4. We recommend you to update the optimizer statistics, which is especially important whenupgrading to MaxDB version 7.6 or higher.

5.2 Updating the Database Software to the Current Release

After the upgrade and before you start production operation, we strongly recommend you to updatethe database software.

Procedure

1. Download the latest SAP MaxDB patches as follows:http://service.sap.com/swdc Download Database Patches MaxDB

For more information about upgrading to a MaxDB Support Package, see SAP Note 735598.

5.3 Installing or Upgrading Database Studio for SAP MaxDB

This section describes how to install or upgrade Database Studio for SAP MaxDB and SAP liveCacheon Windows front ends. Database Studio is the database administration tool for SAP MaxDB.For more information about Database Studio, see:https://www.sdn.sap.com/irj/sdn/maxdb SAP MaxDB Knowledge Center The Complete SAP

MaxDB Documentation Set SAP MaxDB 7.7 Library Glossary Database Studio

Note

Database Studio replaces Database Manager GUI and SQL Studio, which were available in previousreleases.

Prerequisites

n You can install Database Studio on Linux or Windows in your network, even if your database runson a different operating system. You can then remotely administer the database on a different host.The instructions below refer mainly to the Windows version.

Note

To run Database Studio on Linux, you need to meet the requirements for the MaxDB databaseserver.

n Your PC must meet the followingminimum requirements:l Software requirements:

22/36 PUBLIC 08/15/2008

5 Post-Upgrade5.3 Installing or Upgrading Database Studio for SAP MaxDB

Operating System Requirements for Database Studio

Operating System Version

Windows XP Professional Service Pack 2

Windows 2003 Server Service Pack 1

l Hardware requirements (currently only 32-bit platforms are supported):

uRAM: 512 MB ( recommended RAM: 1 GB)

uProcessor speed: 1.5 GHz

uFree disk space: 200 MB

uMonitor: 1024x768 pixels, 256 colorsn You can get the required files from one of the following:l The DVD for MaxDB RDBMS or SAP liveCache

l By downloading from:http://service.sap.com/patches Entry by Application Group Additional Components

MaxDB MaxDB GUI COMPONENTS/TOOLS MAXDB DATABASE STUDIO 7.7

n You need Java Runtime Environment (JRE) version 5 (also known as 1.5) or higher.To check your Java version, enter the following command:java -version

To download Java, go to http://java.com/en/download.n To uninstall the database manager GUI, which is the tool replaced by Database Studio, choose

Start Settings Control Panel - Add/Remove Programs .

Procedure

1. Start the installation or upgrade as follows:n If you are using theMaxDB RDBMS DVD:

<DVD>:\MAXDB_WINDOWS_I386\SDBSETUP.EXE

n If you are using the liveCache DVD:<DVD>:\LC_WINDOWS_I386\SDBSETUP.EXE

n If you are using the downloaded files, simply execute the downloaded SDBSETUP.EXE file.The Installation Manager starts.

2. Choose Start Installation/Upgrade and then Custom.You see a list of the components to be installed.

3. Deselect all components except Database Studio.4. Choose Install.

The installation manager installs Database Studio.5. If you are prompted to restart your computer after the installation, make sure that you first shut

down any databases that are running.

08/15/2008 PUBLIC 23/36

5 Post-Upgrade5.4 Secure Sockets Layer Protocol for Database Server Communication

More InformationFor more information about Database Studio, including troubleshooting, see SAP Note 1097311.

5.4 Secure Sockets Layer Protocol for Database ServerCommunication

The SAP MaxDB database server supports the Secure Sockets Layer (SSL) protocol. You can use thisprotocol to communicate between the database server and its client, here the Application Server(AS). SSL guarantees encrypted data transfer between the SAP MaxDB database server and its clientapplications. In addition, the server authenticates itself to the client.

Caution

There is a performance cost for SSL since the data has to be encrypted, which requires time andprocessing power.

To use SSL you need to:

1. Install the SAP cryptographic library [page 24] on the client host and on the server host machines2. Generate the Personal Security Environment [page 26] (PSE) on the server (SSL Server PSE) and on the

client (SSL Client PSE).

5.4.1 Installing the SAP Cryptographic Library

The SAP Cryptographic Library supplies the cryptographic functions required to build a databaseserver-client connection using Secure Sockets Layer (SSL). Therefore, you need to install theSAP Cryptographic Library on the host machine of the SAP MaxDB database server and the SAPApplication Server (AS).The installation package sapcrypto.car consists of the following:

n SAP Cryptographic Library: sapcrypto.dlln License ticket: ticket

n Configuration tool: sapgenpse.exeYou use the configuration tool to generate key pairs and PSEs.

Caution

The SAP Cryptographic Library is subject to German export regulations and might not be availableto some customers. In addition, the library might be subject to the local regulations of your country.These regulations might further restrict import, use, and export or re-export of cryptographicsoftware.For more information, contact your local SAP representative.

24/36 PUBLIC 08/15/2008

5 Post-Upgrade5.4 Secure Sockets Layer Protocol for Database Server Communication

PrerequisitesDownload the appropriate SAP Cryptographic Library installation package for your operating systemfrom http://service.sap.com/swdc.

Procedure

1. Unpack the installation package for the SAP Cryptographic Library using sapcar.exe, which youcan find for example on your Installation Master DVD, using the following command:car -xvf SAPCRYPTO.CAR

Note

The remainder of the procedure (as described below) does not apply to client applications such asSQL Studio, which do not recognize an “independent” directory. In this case, you must copy theSAPCRYPTO installation package to the installation directory of the application. In this directoryyou need to create a directory sec, into which you copy the ticket file.

2. Copy the sapcrypto library to the lib subdirectory of the “independent program” directory.You can find the value of the independent program directory by entering the following command:dbmcli dbm_getpath IndepProgPath

Example

The independent program directory might be called the following:<drive>:\sapdb\programs\lib

3. Copy the configuration tool sapgenpse.exe to the directory <independent program>\lib.4. Create a subdirectory called sec under the “independent data” directory and copy the ticket

file into it.

Example

The result might look like the following:<drive>:\sapdb\data\sec\ticket

5. Make sure that only the local system account is allowed to possess access rights to the secdirectory and the files it contains ‒ including the ticket file and the SSL Server PSE ‒ and thataccess is restricted to read&write. Only members of the administrator group can own the files.

ResultThe system copies the SAP Cryptographic Library to the application server and correctly configuresthe environment so that the server can find the library at runtime.

08/15/2008 PUBLIC 25/36

5 Post-Upgrade5.4 Secure Sockets Layer Protocol for Database Server Communication

5.4.2 Generating the Personal Security Environment

The information required by the database server or client application to communicate using SecureSockets Layer are stored in the Personal Security Environment (PSE). The required information differsaccording to whether SSL PSE is for the server or client:

n SSL Server PSEThis PSE contains the security information from the database server, for example, thepublic-private cryptographic key pair and certificate chain. To install the SSL Server PSE, youneed to generate the PSE. You can either do this for a single database server or system-wide. TheSSL Server PSE is called SDBSSLS.exe.

n SSL Client PSEThe client requires an anonymous certificate called SDBSSLA.exe, which contains the list of thepublic keys of trustworthy database servers.

ProcedureTo generate the SSL Server PSE, proceed as follows:

Note

You need to know the naming convention for the distinguished name of the database server.The syntax of the distinguished name, which you enter in the procedure below, depends on theCertification Authority (CA) that you are using.

1. Change to the <independent programs>\lib directory.2. Set up the following environment variable:

SECUDIR=<independent data>\sec

3. Create an SSL Server PSE, SDBSSLS.pse, and generate a certificate request file, certreq, in thedirectory defined by SECUDIR (see previous step):sapgenpse gen_pse -v -r <SECUDIR>\certreq -p SDBSSLS.pse “<your distinguised name>”

For each database server that uses a server-specific PSE, you must set up a unique certificaterequest. If you are using a valid system-wide SSL Server PSE, you only need to set up a singlecertificate request for all servers.

4. Send the certificate request to the CA for signing. You can either send it to the SAP CA or toanother CA.You must make sure that the CA offers a certificate corresponding to the PKCS#7 certificate chainformat. Thawte CA at www.thawte.com offers a suitable certificate, either SSL Chained CA Certor PKCS#7 certificate chain format.The CA validates the information contained in the certificate request, according to its ownguidelines, and sends a reply containing the public key certificate.

5. After you have received the reply from the CA, make sure that the contents of the certificaterequest have not been destroyed during download.

26/36 PUBLIC 08/15/2008

5 Post-Upgrade5.4 Secure Sockets Layer Protocol for Database Server Communication

For example, if you requested the certificate on a UNIX system and stored it on a Windows frontend, the formatting (that is, line indents and line breaks) is affected.To check the contents, open the certificate request with a text editor (such as Notepad) and repairthe line indents and the line breaks.

Example

This is an example of a certificate request:-----BEGIN CERTIFICATE

REQUEST-----MIIBPzCBqQIBADAAMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD/302IT+/Y

wpignSw7U9FWneyWz3Wil0S18aFCYkRo00wCpD8UwcaC4dds4uGT6hl2WlJ0/FOtUg+EQxonZbaRrk9sTalkn1mqx3YAUe/gEaGdf1wvuYkb0gjMk81iM/jb9BJd8srMPyoBy9jMC7v5u7+TZWmWa6RjnvClvYGgMwIDAQABoAAwDQYJKoZIhvcNAQEFBQADgYEAx2zuaTAOKPdGmxUKYlWdasUpim4vhfaHa7ZDBwipvKJ8akYCT+dpmVjhcph9E7cUjL80/6Rup5cnLAAO5FhVt5MS6zNJa9YYSN9XP+5/MPF6Q4ayJ0VryTkSpbbPrWLbKh1Dds97LQVuQ/myKIAHECwyW6t7sAFJWn4P0fdxmKo=

-----END CERTIFICATE REQUEST-----

6. Import the reply to the SSL Server PSE:a) Copy the text to a temporary file called srcert.b) Enter the following command:

sapgenpse import_own_cert -c srcert -p SDBSSLS.pse

You have generated the SSL Server PSE. You can now start the XServer as usual (if it is alreadyrunning, you must stop and restart it).

7. To check whether the SSL functionality is working correctly, view the trace file niserver_<localcomputer name>.trace in the <independent data>\wrk directory.

To generate the SSL Client PSE, proceed as follows:

1. Change to the <independent programs>\lib directory.2. Set up the following environment variable:

SECUDIR=<independent data>\sec

3. Create an anonymous client SSL Client PSE, SDBSSLA.pse in the directory defined by SECUDIR (seeprevious step):sapgenpse gen_pse -v -noreq -p SDBSSLA.pse

You can leave the distinguished name empty.Before you can establish an SSL connection to a database server, the server certificate must beentered in the PK list of the anonymous client certificate.

4. To see the database server certificate, enter the following command:„x_ping -n <servermode> -c[apture]

You can check whether to trust the database server certificate. The client certificate is not affectedby this.

5. Start the import with this command:„x_ping -n <servermode> -i[import]

6. To administer the PSE, use the configuration tool sapgenpse. For more information, enter thefollowing command:sapgenpse -h

08/15/2008 PUBLIC 27/36

5 Post-Upgrade5.4 Secure Sockets Layer Protocol for Database Server Communication

Note

For applications such as SQL Studio replace the independent data or independent program in theabove description with the installation directory.

28/36 PUBLIC 08/15/2008

6 Additional Information

6 Additional Information

6.1 Database Directory Structure

As of SAP DB Release 7.2.4, you can set up several database instances with different releases in one userenvironment. For this the database services are split into the following areas:

n Release-independent programs: IndependentProgPathThis area contains all services that are only allowed to exist once per computer and are downwardcompatible (for example, the server for Remote SQL, x_server). Therefore, only programs ofthe most recent installed version exist here.You can check the path for IndepdendentProgPath with the following dbmcli command:dbm_getpath IndepProgPath

By default, IndependentProgPath is set as follows for the installation:<DB drive>:\sapdb\programs

The subdirectory bin and, for Windows, the extra directory pgmmust be specified in theenvironment variable path.

n Instance data: IndependentDataPathThis area contains all data necessary for an instance, including run directories and their parameterfiles. The directory containing this data is called the IndependentDataPath.You can check the path for IndepdendentDataPath with the following dbmcli command:dbm_getpath IndepDataPath

By default, IndependentDataPath is set as follows for the installation:<DB drive>:\sapdb\data

The subdirectory bin and, for Windows, the extra directory pgmmust be specified in theenvironment variable path.

n Instance-dependent programs: INSTROOTThis area contains all programs necessary for a running instance. The programs must allcorrespond to the instance version and are installed once per instance. The programs include,for example, kernel, console, dbmsrv, and so on. The storage location is known as the INSTROOTof the instance.The installation sets up the directory as follows:<DB drive>:\sapdb\<DBNAME>\db

You can display instance names and associated INSTROOTs on a computer with the followingdbmcli command:db_enum

08/15/2008 PUBLIC 29/36

6 Additional Information6.2 Sample Directory Structure

n Client-runtime libraries and dllsThis area contains shared libraries and dlls required by clients at runtime, including runtimeprecompilers, ODBC, and so on. The runtime libraries are installed on each computer, butdifferent versions must be possible.The directories for the runtime software are set up during the installation beneath IndepProgPath

as follows:<DB_DRIVE>:\<IndepProgPath>\runtime\<version>

n Client programsThis area contains all client tools supported by SAP MaxDB, including, for example, dbmgui andSQL Studio. These tools are currently only available on Windows.You can install them on the database server, although this is not absolutely necessary. The GUIclients are installed once on each computer. The settings for each user are stored individually. Youcan choose any directory for the tools during the installation, independently of the directoriesnamed above.

6.2 Sample Directory Structure

The following graphic shows a sample directory structure:

Figure 1:

30/36 PUBLIC 08/15/2008

6 Additional Information6.3 Log Files for Troubleshooting

6.3 Log Files for Troubleshooting

All steps of the upgrade and the associated software installation are logged in the fileMaxDBUpgrade_install-<date>-<time>.log with the following name:<independent_data_path>\wrk\MaxDBUpdate_install-<date>-<time>.log

If the directory <independent_data_path> is not known at the time of failure, the log is written tothe current directory.

Note

If you are updating the MaxDB client software, you can find the log files here instead:<independent_data_path>\wrk\MaxDBRuntimeForSAPAS_install-<date>-<time>.log

08/15/2008 PUBLIC 31/36

Typographic Conventions

Example Description

< > Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address, for example, http://www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

32/36 PUBLIC 08/15/2008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

08/15/2008 PUBLIC 33/36

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: https://service.sap.com/instguides

34/36 PUBLIC 08/15/2008

This page is intentionally left blank.

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2008 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.