SAP Netweaver Business Intelligence BI / BW

Symptom

This note provides supplementary information about the version upgrade to MaxDB 7.7 and refers to all known problems.
Details about performing the version upgrade are contained in the upgrade guide: “Upgrade to MaxDB Version 7.7″.
For a current version of the upgrade guide, go to:
service.sap.com/instguides.
-> Other Documentation
-> Database Upgrades
-> MaxDB
The valid MaxDB DVD material numbers (MatNo) of Version 7.7 are:
Support Package 1 build 16: MatNo 51032880 all platforms
Support Package 2 build 10: MatNo 51032922 all platforms
Support Package 2 build 17: MatNo 51033248 all platforms
Support Package 4 build 25: MatNo 51034954 all platforms
Support Package 4 build 28: MatNo 51035704 all platforms
Support Package 6 build 07: MatNo 51036050 all platforms
Support Package 6 build 10: MatNo 51036887 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
The MaxDB 7.7 downward-compatible release has been granted for SAP products that are based on SAP kernel 46D_EXT or higher. In the Product Availability Matrix
(PAM), this downward-compatible release is displayed for the relevant products:
http://service.sap.com/pam
Within this MaxDB 7.7 downward-compatible release, the newest
of the listed DVDs can be downloaded or ordered in the following area of the SAP Software Distribution Center (SWDC):
http://service.sap.com/swdc
> Database Patches
> MaxDB and SAP DB (new window)
Section: Download a MaxDB or SAP DB RDBMS DVD for “Upgrade”.
See Note 382312 to check which CCMS adjustments (Basis Support Packages) are required for using the MaxDB Version 7.7 for products below NW 7.0 .

Other terms

7.7, version change, upgrade, DBUPDATE, SDBUPD, release upgrade

Reason and Prerequisites

You use SAP DB Version 7.3.00.25 or higher and want to carry out a version upgrade to MaxDB Version 7.7.
Bear in mind that the direct upgrade to 7.7 is not supported by databases of Version 7.3.00 with a non-Unicode database catalog. In this case, you must first carry out an interim upgrade to Version 7.6 (see Note 793550), with which the Unicode-catalog migration is carried out.
Use the following command to determine the catalog category of a database:
dbmcli -d -u , param_getvalue _UNICODE

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
whether the MaxDB Version 7.7 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).2. If a password containing more than nine characters is set for the DBM user (control), see Note 763222.3. 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.4. As of MaxDB Version 7.6, AWE for Windows is no longer supported. For more information, see Note 960331.5. As of MaxDB Version 7.6, the version numbering has changed. See Note 972785.6. For MaxDB databases of Version 7.6, you must have at least start Version 7.6.00.12 to change from Version 7.6 to Version 7.7.01. (SAP internal information PTS 1142692)7. MaxDB Version 7.7 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 40968. ! Important:
For security reasons, the authorizations for the registration file ‘/usr/spool/sql/ini/SAP_DBTech.ini’ are changed during the version upgrade to 7.7.03.23 or higher or 7.7.04.09 or higher. For applications that use the precompiler Version 7.4.03 or lower, you must execute the workaround described in Note 1144394 (using the EX2 kernel, or assign user sidadm to group sdba) to prevent the connect to the database from failing with error -888 after a version upgrade.9. To operate MaxDB 7.7, you must use transaction SNOTE to implement the changes specified in Note 1123603 (including Notes 916795 and 1002641) in the system. Otherwise, problems occur, especially when you import Support Packages and use transaction SPAM.10. ! Important:
The version change to MaxDB 7.7 is not released for database instances that use the table clustering released with Version 7.6. Especially BW systems use this feature (Note 983845).
Whether a database instance has clustered tables can be determined using the following SQL statement:
SELECT i.tablename, i.indexname
FROM files f, indexes i
WHERE i.fileid = f.fileid
AND i.owner = USER
AND f.clustered = ‘YES’
If this select returns results, you must not upgrade to MaxDB 7.7.
As soon as the 7.7 version change is available for database instances with table clustering, it will be announced here.11. ! Important:
The version change to MaxDB 7.7 is not released for database instances that use the prefetching released with Version 7.6.05 or higher.
You can use the following command to establish whether the database instance uses prefetching:
dbmcli -d -u control, param_getvalue READAHEAD_TABLE_THRESHOLD
Result:
0: prefetching not active
Greater than 0: Prefetching is active. Version change not permitted after 7.7.
As soon as the 7.7 version change is available for database instances with prefetching, it will be announced here.

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

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.7, 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.7. 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

***********************************************************************
Database start versions lower than 7.3.00.33.
The DBUPDATE script ends with the following error:
STDOUT: checking interferences to other packages
STDOUT: failed
STDERR: There are conflicts with installed packages:
STDERR: /sapdb/programs/bin/xuserUnicode is used by Server Utilities
[/sapdb/programs]
STDERR: /sapdb/programs/bin/xuserUnicode is used by Server Utilities
[/sapdb/programs]
STDERR: MaxDB instance update exited abnormally
Solution: Install a database client software version of Version 7.3.00.34. or higher on the server. Then repeat the database 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
folllowing SQL command:
select * from users where username = ‘SUPERDBA’
(> SINGLE)
Assign the ‘MULTIPLE’ Connect authorization to the SUPERDBA user with the
folllowing 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.
DB upgrade to Version 7.7.06.07
The following errors may occur.
1.) Error:
user_logon failed
read () for rtehdr failed (wanted 24, got 0): Bad file number
Solution:
chown -R sdb:sdba /sapdb/data/config
2.) Error:
param_directget INSTANCE_TYPE
ERR
-24994,ERR_RTE: runtime environment error
1,OS error: ‘Permission denied’
Solution:
chown -R sdb:sdba /data/sapdb
chown -R sdb:sdba /var/spool/sql
These errors are solved as of MaxDB Version 7.7.06.09 and higher.
(SAP internal information PTS 1161158)
***********************************************************************

V/ Activities after the upgrade

***********************************************************************
1. Before you start productive operation, implement the current MaxDB 7.7 patch from SAP Service Marketplace. You require at least Version 7.7.06.14 or higher (SAP Info: PTS 1175060).
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
For MaxDB Version 7.7.04.11 or higher, an SQLDBC client that has Version 7.6.04.10 or higher is required!
(SAP Info: PTS 1153836)
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. See Note 382312 to see which CCMS adjustments (Basis Support Packages) are required for using the MaxDB Version 7.7.5. 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)6. Use Note 1004886 to check the parameter settings for MaxDB Version 7.7 and familiarize yourself with the parameter name changes carried out as of Support Package 3.7. To ensure functionality of SAP systems with a kernel lower than 46D_EXT, make sure that the database parameter _PACKET_SIZE is set to the maximum value 131072.
***********************************************************************

VI/ Documentation

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