SAP Netweaver Business Intelligence BI / BW

Symptom

This note provides supplementary information about the version upgrade to MaxDB 7.8 and refers to all known problems.
Details about performing the version upgrade are contained in the upgrade guide: “Upgrade to MaxDB Version 7.8″.
For a current version of the upgrade guide, go to:
http://service.sap.com/instguides
-> Other Documentation
-> Database Upgrades
-> MaxDB
The valid MaxDB DVD material numbers (MatNo) of Version 7.8 are:
Support Package 0 build 18: MatNo 5103XXXX all platforms
The DVDs listed are contained in the SAP upgrade DVD packages for SAP upgrades. You can download or order them through the Software Distribution Center (SWDC).
http://service.sap.com/swdc
-> Download
-> Installations and Upgrades

Other terms

7.8, version change, upgrade, DBUPDATE, SDBUPD, release upgrade

Reason and Prerequisites

You use MaxDB Version 7.5 or higher and want to carry out a version upgrade to MaxDB Version 7.8.

Solution

***********************************************************************
Topics:
I/ Important general information
II/ Errors in the guide
III/ Activities prior to the upgrade
IV/ Errors during the upgrade
V/ Activities after the upgrade
VI/ Documentation
***********************************************************************

I/ Important general information

***********************************************************************
1. Using the Product Availability Matrix (PAM) at
http://service.sap.com/pam
check whether MaxDB Version 7.8 has been released for your product version.
See the application system releases of this product overview on the “Database Platform” tab for the number of the note that specifies the system prerequisites (OS patch level, C++ runtime version, and so on) for your application system. This number is attached as a comment to every MaxDB application system entry (red exclamation mark).
If you plan to use MaxDB Version 7.8 via a special release for the SAP upgrade, note the following:
a) 640: (!) Only SAP Kernel 640_EX2 has been released for Version 7.8, not SAP Kernel 6.40. Before the MaxDB version upgrade to Version 7.8, you must install a sufficient SAP kernel.
b) Errors may occur when you use CCMS.
(Special releases are provided in the MaxDB-specific notes for the relevant SAP upgrade and are not contained in the PAM.)2. See Note 382312 to see which CCMS adjustments (Basis Support Packages) are required for using the MaxDB Version 7.8.3. If a password containing more than nine characters is set for the DBM user (control), see Note 763222.4. For systems with EarlyWatch/GoingLive Servicetool Add-on ST-A/PI with Version 01G* or lower (older than May 2006), you must implement the source code corrections in your system that are described in Note 914188 to avoid short dumps in the RTCCTOOL report or in the SDCC data collection.5. As of MaxDB Version 7.6, AWE for Windows is no longer supported. For more information, see Note 960331.6. As of MaxDB Version 7.6, the version numbering has changed. See Note 972785.7. For MaxDB databases of Version 7.6, you must have at least start Version 7.6.00.12 for the version upgrade.
(SAP internal information PTS 1142692)8. MaxDB Version 7.8 requires a greater limit for file descriptors for the users adm and sqd on Solaris SPARC and Solaris X64 systems.
Use one of the following commands to check the limit currently set for both users:
csh: limit descriptors
sh: ulimit -n
The value must be at least 4096.
Insert the following commands to raise this limit for both users, if required, in their login environment files:
csh: limit descriptors 4096
sh: ulimit -n 4096

***********************************************************************

II/ Errors in the guide

***********************************************************************
***********************************************************************

III/ Activities prior to the upgrade

***********************************************************************
1. For SAP systems with BW functions (BW, SEM, APO):
It is absolutely necessary to delete the temporary BW views immediately before starting the upgrade, otherwise the catalog migration may fail. To do this, execute the SAP_DROP_TMPTABLES report. Select the checkbox “Temporary view (all, type 03)”.2. Before you upgrade to Version 7.8, check whether the database contains indexes that are indicated as BAD. You must either delete or recreate these indexes. If the source version is lower than Version 7.6, indexes lose their status BAD during the upgrade to Version 7.8. This may later lead to problems. See Note 1154601. (In transaction DB50 or in the Database Manager, the system displays BAD indexes under Information.) However, we recommend that you carry out the check for all source versions in general.
***********************************************************************

IV/ Errors during the upgrade

***********************************************************************
Error -8022: User already connected
The following error may occur:
STDOUT: load_systab
-24964,ERR_EXECUTE: error in program execution
loader.LoaderError: loader.LoaderError: [-25005] user (SUPERDBA)
logon to database failed : ODBC-Error: [MySQLMaxDB][SQLOD32DLL][MaxDB]
Unable to connect to data source;-8022 POS(1)
User already connected
return-code: SQL_ERROR (-8022).
Reason for this is that the user SUPERDBA only has ‘SINGLE’ connect
authorization, however, for the update of the system tables, the
‘MULTIPLE’ connect authorization is required.
You can check the settings of the connect authorization with the
following SQL command:
select * from users where username = ‘SUPERDBA’
(> SINGLE)
Assign the ‘MULTIPLE’ Connect authorization to the SUPERDBA user with the
following SQL command:
dbmcli -d -u ,
sql_connect ,
sql_execute alter user superdba not exclusive
sql_execute commit work
sql_release
Alternatively, you can also use the SQL Studio to execute the “alter user” statement.
Then restart the MaxDB version change.
***********************************************************************

V/ Activities after the upgrade

***********************************************************************
1. Before you start production operation, you must apply the current MaxDB 7.8 patch from SAP Service Marketplace.
MaxDB patches are available in the Software Distribution Center of SAP Service Marketplace:
http://service.sap.com/swdc
-> Download
-> Support Packages and Patches
-> Entry by Application Group
-> Additional Components
-> MaxDB
If you use the Database Manager Studio for DB administration, we recommend that you import the version that is currently available.
-> Navigate as described above.
-> MAXDB GUI COMPONENTS/TOOLS2. To ensure that the problems mentioned in Note 1128989 do not occur when you use transactions DB13, DB50, LC10 and RZ20, you must install the minimum version of the MaxDB Client Software mentioned here on your application server.3. To operate the DB Analyzer on Windows, you require MDAC Version 2.7 or higher. For more information, see Note 748582.4. UNIX only: Make sure that the operating system user of the MaxDB instance (standard sdb) has the authorization to create new files in the following directories:
-> Directory of data volumes and log volumes
-> Directory of data backup and log backup (including AutoLog)5. Use Note 1308217 to check the parameter settings for MaxDB Version 7.8.
***********************************************************************

VI/ Documentation

***********************************************************************
***********************************************************************