Symptom
This note contains questions that are frequently asked by SAP staff and customers
about MaxDB interfaces. It provides answers and refers you to other information sources.
The note is in no way complete.
1. What are MaxDB interfaces?
2. What MaxDB interfaces are there?
3. What is the MaxDB precompiler or precompiler runtime?
4. Which version of the precompiler runtime is used in which SAP versions?
5. Does the precompiler runtime also have to be installed on the application server?
6. How can I determine which versions of the precompiler runtime are installed on a host?
7. Can I also use irconf to determine the installed precompiler runtime versions?
8. Where does irconf receive the information from?
9. How can I register a precompiler runtime version?
10. How can I determine which precompiler runtime is currently in use in the SAP system?
11. How do I install or update the precompiler runtime?
12. How do I activate or deactivate the precompiler trace?
13. What is the SQLDBC interface?
14. Which SQLDBC runtime version is used in which SAP versions?
15. Does the SQLDBC runtime also have to be installed on the application server?
16. How can I determine which versions of the SQLDBC runtime are installed on a host?
17. How can I determine which version of the SQLDBC runtime is currently in use?
18. How do I install or upgrade the SQLDBC runtime?
19. How do I activate or deactivate the SQLDBC trace?
20. What is the ODBC interface?
21. What is the ODBC interface used for in the SAP environment?
22. How can I determine which ODBC version is installed on the host?
23. How do I install or upgrade the MaxDB ODBC driver?
24. How can I create an SQL trace in the content server?
25. What is the JDBC interface?
26. What is the JDBC interface used for in the SAP environment?
27. How can I determine which JDBC version is installed on the host?
28. How do I install or upgrade the MaxDB JDBC driver?
29. How do I activate the JDBC trace?
30. You want to increase the number of J2EE instances. What do I have to consider in the database?
31. Where do I find additional information about MaxDB interfaces?
Other terms
FAQ, precompiler, ODBC, SQLDBC, JDBC, interfaces, could not load libpcr, ODBC trace
Reason and Prerequisites
You use MaxDB as of Version 7.5 in an OLTP, BW or liveCache environment.
Further FAQ notes about MaxDB/live Cache are available on SDN (SAP Developer Network):
https://wiki.sdn.sap.com/wiki/x/GkM
Solution
1. What are MaxDB interfaces?
Database applications (such as SAP systems, for example) use interfaces to access MaxDB database instances.
If the database application (and therefore the MaxDB interface) is located on a different host to the database instance, the database system also requires the MaxDB X server (communications server) for communication purposes. The JDBC interface also requires the MaxDB X server for local communication.
2. What MaxDB interfaces are there?
In the MaxDB documentation (see Note 767598), a list of all MaxDB interfaces is available under the key word 'interface'. In this note, only the interfaces that are used in the SAP environment are explained in greater detail:
- C Precompiler
- SQL Database Connectivity (SQLDBC): Object-oriented C++ interface for accessing the MaxDB database system
- ODBC (3.5.1): MaxDB ODBC driver for accessing the MaxDB database system
- JDBC (2.0/3.0): MaxDB JDBC driver for accessing the MaxDB database system
3. What is the MaxDB precompiler or precompiler runtime?
The interface between the MaxDB database system and application programs (such as the SAP kernel) is the database language SQL (Structured Query Language). SQL statements embedded into the application program (Embedded SQL) allow communication with the database instance. Parameter values are exchanged through special program variables, which are known as host variables.
The C/C++ Precompiler prepares C/C++ source code with embedded SQL statements for the compilation into an executable application program. It checks the embedded statements syntactically and semantically, converts them into calls of precompiler runtime procedures and creates a C/C++ file, which can then be compiled.
When the application program is running, the precompiler runtime assumes the following functions:
- Setting up the database connections and opening the database sessions according to the specified connection options
- Assigning parameter values
- Converting data types
- Executing the precompiler statements
- Signaling NULL values (undefined values) using indicator variables
- Displaying confirmations from the database system in the structure sqlca
- Writing the trace file according to the specified trace options
In the SAP environment, the precompiler runtime is required for the database-dependent part of the SAP kernel, which is known as the DBSL (dbadaslib).
4. Which version of the precompiler runtime is used in which SAP kernel versions?
The precompiler runtime (libpcr) versions that are used do not depend on your SAP DB/MaxDB kernel version.
a) 31I extended kernel
The precompiler runtime version required by the DBSL (dbadaslib) is 7.3.00, Build 33 or higher (on Windows), or Build 26 or higher (on UNIX).
b) 40B extended kernel
The precompiler runtime version required by the DBSL (dbadaslib) is 7.3.00, Build 33 or higher (on Windows), or Build 26 or higher (on UNIX).
c) 45B extended kernel (including APO 1.1, APO 2.0)
The precompiler runtime version required by the DBSL (dbadaslib) is in all cases 7.3.00, Build 33 or higher (on Windows), or Build 26 or higher (on UNIX).
d) 46D extended kernel (including APO 3.0, APO 3.1)
The precompiler runtime versions required by the DBSL (dbadaslib) are:
- 7.3.01 Build 10 or higher (Windows NT and UNIX)
- 7.4.03 Build 5 or higher (NT IA64)
- 7.4.03 Build 17 or higher (Linux IA64)
- 7.4.03 Build 26 or higher (HP IA64)
- 7.5.00 Build 16 or higher (Linux AMD X86_64)
e) Kernel Version 6.20 Basis, 4.70 (including APO 4.0, Web AS 6.20 and 6.30)
The precompiler runtime versions required by the DBSL (dbadaslib) are:
- 7.3.01 Build 10 or higher (Windows NT and UNIX)
- 7.4.03 Build 5 or higher (NT IA64)
- 7.4.03 Build 17 or higher (Linux IA64)
- 7.4.03 Build 26 or higher (HP IA64)
f) Version 6.40 Basis, 6.40 AKK (including NetWeaver 04, Web AS 6.40, SCM 4.1, 6.30 J2EE)
The precompiler runtime versions required by the DBSL (dbadaslib) are:
- 7.4.03 Build 11 or higher (Windows NT and UNIX)
- 7.4.03 Build 17 or higher (Linux IA64)
- 7.4.03 Build 26 or higher (HP IA64)
- 7.5.00 Build 16 or higher (LINUX PPC64 and LINUX AMD64)
- 7.5.00 Build 15 or higher (LINUX s390)
- 7.5.00 Build 24 or higher (NT AMD64)
g) Version 6.40 Ext-2
As of this kernel version, the SQLDBC interface is used instead of the precompiler runtime. The assignment of the SAP kernel to the relevant SQLDBC versions can be found under point 14 in this note.
5. Does the precompiler runtime also have to be installed on the application server?
Yes, the precompiler runtime has to be installed on all application servers and on the database server.
6. How can I determine which versions of the precompiler runtime are installed on a host?
You can use the 'sdbregview' program to determine which MaxDB software component are installed on the relevant host. If precompiler runtime versions are installed on the host, they are displayed as follows.
a) On UNIX platforms:
At operating system level, start 'sdbregview -l | grep -i PCR'
The system displays a list of the precompiler versions that are installed on the host.
For example:
PCR 7300 /program files/sdb/programs 7.3.00.53 valid
PCR 7301 /program files/sdb/programs 7.3.01.18 valid
PCR 7500 /program files/sdb/programs 7.5.00.29 32 bit valid
PCR 7104 /program files/sdb/programs 7.1.04.45 valid
PCR 7240 /program files/sdb/programs 7.2.04.17 valid
PCR 7600 /program files/sdb/programs 7.6.00.11 32 bit valid
PCR 7250 /program files/sdb/programs 7.2.05.24 valid
PCR 7403 /program files/sdb/programs 7.4.03.40 32 bit valid
b) On Windows platforms:
At operating system level, start
'sdbregview -l | find /I "PCR"'
The system displays a list of the precompiler runtime versions that are installed on the host.
For example:
PCR 7300 c:/program files/sdb/programs 7.3.00.60 valid
PCR 7301 c:/program files/sdb/programs 7.3.01.22 valid
PCR 7500 c:/program files/sdb/programs 7.5.00.50 32 bit valid
PCR 7104 c:/program files/sdb/programs 7.1.04.45 valid
7. Can I also use irconf to determine the installed precompiler runtime versions?
Yes, you can use the call 'irconf -a' to determine which precompiler runtime versions are installed on a host. For example, the system issues the following when you call an irconf of the MaxDB Version 7.5 on Unix:
/sapdb/programs/runtime/7500 -> 7.5.0.0 from global registration
/sapdb/programs/runtime/7240 -> 7.2.4.0 from old registration
/sapdb/programs/runtime/7250 -> 7.2.5.0 from old registration
/sapdb/programs/runtime/7300 -> 7.3.0.0 from old registration
/sapdb/programs/runtime/7301 -> 7.3.1.0 from old registration
/sapdb/programs/runtime/7403 -> 7.4.3.0 from old registration
Note the following: You must also specify the option -g if you want to see cross-user registrations.
8. Where does irconf receive the information from?
Between the MaxDB Versions 7.4 and 7.5 the storage of information has changed on Unix.
a) up until and including precompiler Version 7.4
/sapdb/programs/runtime/7240 -> 7.2.4.0 from old registration
/sapdb/programs/runtime/7250 -> 7.2.5.0 from old registration
/sapdb/programs/runtime/7300 -> 7.3.0.0 from old registration
/sapdb/programs/runtime/7301 -> 7.3.1.0 from old registration
/sapdb/programs/runtime/7403 -> 7.4.3.0 from old registration
the information about which versions are installed on a host is determined from the file SAP_DBTECH.ini in the /usr/spool/sql/ini/ directory on Unix platforms.
On Windows, the information is determined from the registry under HKLM\software\SAP\SAP DBTECH.
If an entry is missing in this file or in the registry, or if the file is missing, the system cannot find the precompiler runtime. The following error message, for example, is displayed:
Could not load libpcr (No registered version (7.4.3)
b) As of precompiler Version 7.5
/sapdb/programs/runtime/7500 -> 7.5.0.0 from global registration
the information is determined from the runtimes.ini file in the INDEP_DATA/config directory on Unix.
On Windows, the information is determined from the registry under
HKEY_LOCAL_MACHINE:Software\SAP\SAP DBTech.
Comment:
This new storage is known only by SAP kernel 6.40 on the following platforms:
- LINUX: X86_64, PPC64, S390x
- Windows X86_64
SAP kernel 6.40 or lower on all other platforms do NOT know this new storage, and these kernels therefore search for the old registration.
9. How can I register a precompiler runtime version?
You can use the command 'irconf -i -p /sapdb/programs/runtime/7403' to register, for example, a precompiler runtime Version 7.4.03.
Here, the version (below 7.5 or 7.5 and higher) of the irconf determines where the precompilers are registered.
For example: If a precompiler runtime Version 7.4.03 is registered using an irconf Version 7.4, it is registered in SAP_DBTech.ini. If an irconf Version 7.5 or higher is used for the registration, the precompiler runtime Version 7.4.03 is registered under /sapdb/programs/runtime/7.4.03.
10. How can I determine which precompiler runtime is currently in use in the SAP system?
The version of the precompiler runtime that is currently being used by the SAP application is logged on each application server in the developer trace logs (dev_w* files). In transaction SM50, select a work process and choose the menu option 'Process -> Trace -> Display File' to go to the log. In the log, search for the following string:
C Precompiler Runtime :
For example:
Precompiler Runtime : C-PreComp 7.3.1 Build 011-000-091-899
Specify this version string in your message when reporting an error to SAP.
11. How do I install or update the precompiler runtime?
The precompiler runtime is part of the MaxDB client software package. Use Note 649814 to install or upgrade the MaxDB precompiler runtime.
12. How do I activate or deactivate the precompiler trace?
a) R/3 Basis Release 4.6D and earlier or precompiler versions earlier than 7.2.04:
The precompiler trace is activated using a parameter in the instance profile of the SAP system (file <SID>_DVEBMGS<INSTANCENR>_<host name>, in the directory /usr/sap/<SID>/SYS/profile/). After you have set the parameter, you must restart the SAP system, or at least the application server for which you are activating the trace. *.pct files are then written in the work directory of the SAP system.
The following options exist:
- dbs/ada/sql_trace = 2
This is a detailed trace; the PCT files may become very large, but there is no risk of the required information being overwritten.
- dbs/ada/sql_trace = <X>
<X>: a number larger than 2: this is an alternate trace; X commands are logged for each PCT file, and then the relevant file is overwritten. There is no risk of the file system becoming full (if you do not select too large a number for X), but if the trace is not deactivated in time or the file is saved, the error may have already been overwritten when the analysis is carried out.
b) Irtrace (Precompiler versions >= 7.2.04 (as of R/3-Basis 6.10))
As in the earlier versions, the precompiler trace can also be activated by setting the profile parameter. However, you can also activate the trace using irtrace WITHOUT having to restart the system or the application server.
The tool offers the following options for changing the behavior of the trace:
- Activating/deactivating/changing the trace for a particular process:
irtrace -p <prozess-id> -t <trace_type>
The following trace types are available:
- long : long trace,
- short : short trace and off: deactivate trace.
Further information about the precompiler trace is provided in the support guide (Note 692274).
13. What is the SQLDBC interface?
Up to and including Database Version 7.5, the precompiler served as an interface between MaxDB database instances and C/C++ application programs. As of Database Version 7.6, the SQLDBC interface replaces the precompiler.
SQL Database Connectivity (SQLDBC) is a runtime library for the development of database applications and database interfaces for MaxDB. Applications can use SQLDBC to access MaxDB database instances, execute SQL statements and edit data. It consists of the runtime library libSQLDBC, the Software Development Kit SQLDBC SDK and the tool sqldbc_cons.
The runtime library libSQLDBC is also called SQLDBC runtime. In the SAP environment, the SQLDBC runtime is required for the database-dependent part of the SAP kernel (the DBSL (dbsdbslib)).
14. Which SQLDBC runtime version is used in which SAP versions?
As of SAP kernel Version 6.40 EXT-2, the precompiler runtime is replaced by the SQLDBC interface. The SQLDBC runtime (libSQLDBC) versions do not depend on your SAP DB/MaxDB kernel version.
As of Version 7.00, DBADASLIB is replaced by DBSDBSLIB.
a) SAP kernel Version 6.40 EXT-2
The SQLDBC runtime is delivered for the first time in SAP kernel Version 6.40 EXT-2.
This downward-compatible SAP kernel is used with a DBSL that requires the following SQLDBC versions:
- 7.6.00 Build 2 or higher (Windows NT, NT IA64)
- 7.6.00 Build 7 or higher (NT AMD64)
- 7.6.00 Build 2 or higher (LINUX, LINUX IA64, LINUX X86_64)
- 7.6.00 Build 2 or higher (TRU64, HP64, HP-IA64, AIX64, SUN64)
- 7.6.00 Build 7 or higher (LINUX PPC64, LINUX S390x)
- 7.6.00 Build 22 or higher (SUN X86_64)
b) SAP kernel version 7.00 (including NW04s, NW 7.00 Support Package x, 6.45 J2EE and SCM 5.0)
The SQLDBC runtime versions required by the DBSL (dbsdbslib) are:
- 7.6.00 Build 2 or higher (Windows NT, NT IA64)
- 7.6.00 Build 7 or higher (NT AMD64)
- 7.6.00 Build 2 or higher (LINUX, LINUX IA64, LINUX X86_64)
- 7.6.00 Build 2 or higher (HP64, HP-IA64, AIX64, SUN64)
- 7.6.00 Build 7 or higher (LINUX PPC64, LINUX S390x)
- 7.6.00 Build 22 or higher (SUN X86_64)
- 7.6.3 >= build 08 (iSeries OS/400 PASE)
c) SAP kernel version 7.01 (including NW 7.00 Enhancement Package 1)
The SQLDBC runtime versions required by the DBSL (dbsdbslib) are:
- 7.6.00 Build 2 or higher (Windows NT, NT IA64)
- 7.6.00 Build 7 or higher (NT AMD64)
- 7.6.00 Build 2 or higher (LINUX, LINUX IA64, LINUX X86_64)
- 7.6.00 Build 2 or higher (HP64, HP-IA64, AIX64, SUN64)
- 7.6.00 Build 7 or higher (LINUX PPC64, LINUX S390x)
- 7.6.00 Build 22 or higher (SUN X86_64)
- 7.6.3 >= build 08 (iSeries OS/400 PASE)
d) SAP kernel version 7.10 (including NW05, NW 7.10 Support Package x and SCM 6.0)
The SQLDBC runtime versions required by the DBSL (dbsdbslib) are:
- 7.6.1 Build 10 and higher (Windows NT and Unix)
- 7.6.1 Build 10 and higher (NT AMD 64)
- 7.6.1 Build 10 and higher (LINUX PPC 64 and LINUX s390)
- 7.6.3 >= build 08 (iSeries OS/400 PASE)
e) SAP kernel version 7.11 (including NW 7.11, NW 7.1 Enhancement Package x)
The SQLDBC runtime versions required by the DBSL (dbsdbslib) are:
- 7.7.04 Build 9 or higher all available platforms
f) SAP kernel version 7.20 (including NW 7.20)
The SQLDBC runtime versions required by the DBSL (dbsdbslib) are:
- 7.7.04 Build 9 or higher all available platforms
15. Does the SQLDBC runtime also have to be installed on the application server?
Yes, SQLDBC runtime must be installed on all application servers and the database server.
16. How can I determine which versions of the SQLDBC runtime are installed on a host?
You can use the program 'sdbregview' to determine which SQLDBC versions are installed on the relevant host.
a) On UNIX platforms:
At operating system level, start
'sdbregview -l | grep -i SQLDBC'
The system displays a list of the SQLDBC versions that are installed on the host.
For example:
SQLDBC /program files/sdb/programs 7.6.00.19 valid
b) On Windows platforms:
At operating system level, start
'sdbregview -l | find /I "SQLDBC"'
For example:
SQLDBC c:/program files/sdb/programs 7.6.00.19 32 bit valid
17. How can I determine which version of the SQLDBC runtime is currently in use?
The SQLDBC version that is currently being used by the SAP application is logged on each application server in the developer trace logs (dev_w* files). In transaction SM50, select a work process and choose the menu option 'Process -> Trace -> Display File' to go to the log. In the log, search for the following strings:
C SQLDBC SDK Version :
C SQLDBC Library Version :
C SQLDBC client runtime is
For example:
SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 002-121-083-965
SQLDBC Library Version : libSQLDBC 7.6.0 BUILD 016-123-109-428
SQLDBC client runtime is MaxDB 7.6.0.016 CL 109428
Specify these version strings in your message when reporting an error to SAP.
18. How do I install or upgrade the SQLDBC runtime?
Use Note 649814 to install or upgrade the SQLDBC runtime.
19. How do I activate or deactivate the SQLDBC trace?
An SQLDBC trace contains the SQL statements that are sent to the database core by the application, their parameters and the results. All SQLDBC traces contain profile and time stamp information, among other things.
The trace files are stored in the <independent_data_path>/wrk (Microsoft Windows) or <user_home>/.sdb (UNIX/Linux) directories as sqldbctrace-<pid>.prt files, in which <pid> is the process ID. The files are cyclically overwritten.
Use the tool SQLDBC_CONS to configure, start and stop the SQLDBC traces. Start SQLDBC_CONS without additional options, so that all SQLDBC trace options (and trace commands) are displayed.
You can also change the name and the path of the file. You can use the SHOW ALL or SHOW CONFIG SQLDBC trace commands to display the current setting.
Further information about the SQLDBC trace is provided in the support guide (Note 692274).
In Windows, the R/3 processes usually run as SAPService<SID>. Therefore, you must specify the -u option when you activate the trace at operating system level:
sqldbc_cons -u SAPService<SID> TRACE SQL ON
This is not required in DB50 or in SM49, since the environment of the SAPService<SID> already exists there.
20. What is the ODBC interface?
To access the database system MaxDB using the ODBC, you can use the MaxDB ODBC driver. The MaxDB ODBC driver allows you to access MaxDB database instances using the ODBC interface. You can use the MaxDB ODBC driver on all operating systems that are supported by the database system.
Operating system ODBC driver/ACII ODBC driver/UNICODE
Microsoft Windows sqlod32.dll sqlod32w.dll
UNIX/Linux libsqlod.a|so libsqlodw.a|so
The MaxDB ODBC driver is a part of the MaxDB software.
The MaxDB ODBC driver supports the complete ODBC SQL syntax. For detailed information about the ODBC function calls, see the documentation 'ODBC Programmer's Reference' at msdn.microsoft.com.
In order to use the MaxDB ODBC driver, you have the following options:
Registering the MaxDB ODBC driver in a driver manager. You can use the following driver managers:
a) Microsoft Windows: Microsoft ODBC Driver Manager 3.52 or higher
b) UNIX/Linux: unixODBC 2.0.9 or higher, ODBC 3.0.5 or higher
c) UNIX/Linux: link custom-built ODBC applications directly with the MaxDB ODBC driver
Prerequisite: On Microsoft Windows, you require Microsoft Data Access Components (MDAC) Version 2.7 or higher. You installed the MaxDB ODCB driver. On UNIX/Linux, you do not have to install a driver manager. On Windows, a driver manager is generally part of the operating system installation.
21. What is the ODBC interface used for in the SAP environment?
The SAP Content Server, which is a server component of the Knowledge Provider (Kpro), uses ODBC as an interface for MaxDB.
The MaxDB Database Analyzer requires ODBC in order to connect to the MaxDB database.
22. How can I determine which ODBC version is installed on the host?
You can use the 'sdbregview' program to determine which ODBC versions are installed on the relevant host.
a) On UNIX platforms:
At operating system level, start
'sdbregview -l | grep -i ODBC'
The system displays the version of the ODBC driver that is installed on the host.
For example:
ODBC /program files/sdb/programs 7.6.00.20 valid
b) On Windows platforms:
At operating system level, start
'sdbregview -l | find /I "ODBC"'
For example:
ODBC c:/program files/sdb/programs 7.6.00.20 32 bit valid
The ODBC library is linked statically for the SAP content server on UNIX, which means that it does not matter which ODBC driver version is installed on the host.
23. How do I install or upgrade the MaxDB ODBC driver?
See Note 698915 for information about how to install or upgrade the ODBC driver.
24. How can I create an SQL trace in the content server?
To obtain an SQL trace in the content server environment, you activate the ODBC trace.
The ODBC trace must be activated on the server on which the Web server runs.
* On Windows, the ODBC trace (sqltrace) is activated with the file "contentserver.ini" and the relevant parameters as described in Note 329473 (key word: Name=sqltrace). The file "contentserver.ini" is in the content server installation directory.
* On Unix, the ODBC trace (sqltrace) is set using the file "cs.conf" and the parameter 'Sqltrace= 1'. The file "cs.conf" is in the content server installation directory.
You can activate the trace for all repositories or for certain repositories only.
Recommended: Activate the trace only for the repository for which you want to analyze a problem using sqltrace.
The Web server (Windows: IIS; Unix: Apache) must be restarted after you activate the ODBC traces to start writing the trace.
25. What is the JDBC interface?
You can use the MaxDB JDBC driver and the MaxDB Java classes to incorporate MaxDB database instances into Java applications (to execute SQL statements, for instance). The MaxDB JDBC driver and the MaxDB Java classes are included in the software component JDBC.
26. What is the JDBC interface used for in the SAP environment?
The Java Engine of the Web Application Server (J2EE) requires the JDBC driver to communicate with the database.
27. How can I determine which JDBC version is installed on the host?
You can use the 'sdbregview' program to determine which JDBC version is installed on the relevant host.
a) On UNIX platforms:
At operating system level, start
'sdbregview -l | grep -i JDBC'
The system displays the version of the JDBC driver that is installed on the host.
For example:
JDBC /program files/sdb/programs 7.6.00.12 valid
You can currently (PTS:1149235) obtain the complete version string with the command
/usr/runtime/jar/java -jar sapdbc.jar -V
b) On Windows platforms:
At operating system level, start
'sdbregview -l | find /I "JDBC"'
For example:
JDBC c:/program files/sdb/programs 7.6.00.12 valid
You can currently (PTS:1149235) only obtain the complete version string with the command
<drive>\sapdb\programs\runtime\jar\java -jar sapdbc.jar -V
28. How do I install or upgrade the MaxDB JDBC driver?
The JDBC driver is a part of the MaxDB client software package. Use Note 649814 to install or upgrade the JDBC driver.
29. How do I activate the JDBC trace?
See Note 903018 for information about how to activate the trace.
30. You want to increase the number of J2EE instances. What do I have to consider in the database?
If new J2EE instances are connected to a database, then the requirement for parallel user sessions (Parameter MaxUserTasks) in the database increases. Refer to Note 1173395 to correctly calculate MaxUserTasks.
31. Where do I find additional information about MaxDB interfaces?
In the glossary of the MaxDB documentation (see Note 767598), use the key word 'interface' to find further information.
Alternatively, you can use the SDN to access the MaxDB documentation.
https://www.sdn.sap.com/irj/sdn/maxdb