! MaxDB Software Installation !

This document is meant to created for installation of MaxDB database software only.

I assume that you have downloaded the software from market place and keep it somewhere in your system. (My Case I kept it "C:\MaxDB")

To understand what exactly change in Registry File, we can take a snap of below location.

Run --> REGEDIT-->HKEY_LOCAL_MACHINE-->SOFTWARE-->SAP-->SAP DBTech--> Installation (You will find nothing except one default file)

--> Here I kept my software file. ( I am using 64 Bit software as my OS is 64 bit )

--> Double Click in the software installation file.

--> You will find the License Acceptance window --> No doubt, you will have to accept it

As your system is not having any other MaxDB software, you can see only "INSTALL" option is enabled else you could see both are enabled.

--> Next

--> I have not selected the 3rd option as it was not required for me... You can select based on requirement.

--> Specify the installation path as per your requirement and provide the database name as well.

I have not selected the "Create a New Database" option as I will take this as a separate task.

-->Here you will find all the parameters which you have selected during your installation. Review and Confirm.

--> Press Next --> You can see the below screen, this will show the progress of installation.

--> Your MaxDB software is installed successfully.

Please Note that you have only installed the software. You have not installed the Database.

Go to registry tool and see the difference. Here you can find the software information.

I will create another document for installation of MaxDB Studio, that will be useful for you to administer the MaxDB database. Search with "MaxDB Studio Installation !"

! MaxDB Studio Installation !

<<As I have communicated in my document "MaxDB Software Installation !", here is document for MaxDB studio installation>>

This document is meant to created for installation of MaxDB studio only.

I assume that you have downloaded the software from market place and keep it somewhere in your system. (My Case I kept it "C:\MaxDB")

--> Go to your software location

.

--> You will ask for License agreement confirmation .

--> Provide the installation path.

--> It will give you installation path and other information to confirm before you start.

--> Below you can see the progress of the installation..

Once you see the finish message successfully you can start MaxDB studio from Start--> Database Studio (Before that please make sure you have installed JAVA software in the system and set JAVA_HOME as a environment veriable.

I will create another document for creation of MaxDB Database, Search with "MaxDB Database Creation ! "

Enjoy !

Dear All,

As I have communicated you in my previous post "MaxDB Studio Installation !", here I am creating new document for MaxDB Database creation.

This document is meant to created for creation of MaxDB Database only.

I assume that you have already installed MaxDB Software and MaxDB Studio. Now we can continue with database creation part.

--> Log on to Database studio like below.

--> You will find below screen that is called work place. You will find one symbol in the left corner, just click there, it will give you option as below.

--> Click on Explain. This will take you in below screen.

--> Right Click on "Server" -->Administrative Task -->Create Database.

--> You will find below screen.

--> Select "Create a database in advance Mode" --> Next

--> Database server will be Local as you are creating database locally else give server name and make sure server is reachable.

--> Database Name, please make sure you provide 3 letters name as per SAP standard.

--> Here you are able to see 2 options because PRD was already created. Forget about that, just select your DB name. --> Next

--> You can select and deselect the option as per your requirement.

--> Provide password for DBM (Database Manager) user.

--> As it was my new system, I have taken default values.

Below is the confirmation screen, if you want to adjust the value, this can be done now.

One Data Volume has been taken by system itself. You can add more as per your requirement.

--> Provide password for DBADMIN

--> Select as per your requirement

--> Below is the summary of Database Configuration.

--> Below is the successful of DB creation screen.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Once you are done with creation of Database, you can connect to Database as below:

Log on to MaxDB Studio like we did in first phase above.

You will find screen as below.

--> Now you will have to configure the DB detail as below.

Right Click on Server --> Login

--> Here you will have to provide the credentials  in yellow places below.

--> Server --> If DB is not located in your local host then provide HOST Name else keep it LOCAL only.

--> Database Name --> ?

--> User Name --> Control

--> Password --> ?

You can check whether credentials are working fine by pressing Test Login Button. It will give you our Successful OR failed.

If successful then Press Finish.

You will get screen as below on successful completion.

Enjoy Research and Development Now

Hi folks,

the next free of charge MaxDB Online Training:

12.11.2013 - 10 am CET

Please don't forget to register

S-Users:

https://websmp110.sap-ag.de/~sapidb/011000358700000253962013E

NON-S-Users:

https://sap.emea.pgiconnect.com/e13558746/event/registration.html

We are looking forward to teaching you

Regards, Christiane

you just built a system with MaxDB and  post check requirement is to check DB59 connection test is successful. However, when you go to DB59, you get this error

You look at the work process to find the error cause and the log says

ERROR => CONNECT failed : sqlcode=-4008     (Unknown user name/password combination)

Resolution:

As per note 955610, you have to maintain the db connection parameters in tcode DBCO, for every database that is listed in the table dbcon. Connection parameter include schema name/password. However, as per the note:

CAUTION: In Transaction DBCO, you have to enter the password in UPPERCASE letters. If you enter the password with lowercase letters, the system issues error -4008 "Unknown user name/password combination" when trying to connect.

Once this is done, you can go back to db59 and test the connection again

Download the latest software from the following link

http://www.sdn.sap.com/irj/scn/maxdb-downloads

Before installing make sure your PC ins installed with Java 1.5 or 1.6 (Database Studio 7.9 requires)

• Ensure that the version is the same with regard to the host architecture. Database Studio 32-bit requires a Java runtime environment 32-bit. Database Studio 64-bit requires a Java runtime environment 64-bit.

after uncar the maxdb studio software, double click the “SDBSETUP” file

Follow the onscreen instructions to complete the installation

For the first time the Database Studio must has to be started with “Run as administrator” option.

If you have any issues in starting the Database Studio make sure java plugin was enabled in explorer options.

IE --> Tools --> Internet Options >  Programs (tab) --> Manage add-ons

if you face any issues while starting the tool, do the following

remove the folder "DatabaseStudio" from   <Drive>:\users\<username\sdb\DatabaseStudio.

and start the database studio again, it will create a new  "DatabaseStudio" folder

For more information on how to configure database studio refer :-    SAP Library - MaxDB

Hi Folks,

Reminder: We will have 2 online Trainings in March - both trainings are free of charge but registration is necessary.

SAP MaxDB & Content Server  Housekeeping - March, 11 2014 9:00 - 10:00 GMT +1

Registration: https://websmp203.sap-ag.de/~sapidb/011000358700001169752013E (Registration ends at 10.03.2014)

Non-S-Users:2014_03_11_SAP_MaxDB_and_Content _09CET_EN - Adobe Connect

This session will handle the recommended housekeeping tasks for SAP MaxDB Content Server

databases. We rcommend to prepare yourself to this session by using the recording of Database Studio Expert session.

You can download the material ->

• Session 2: Basic Administration with Database Studio
  Recording (.wrf file, 25 MB), Script (.pdf file, 9 MB)

SAP MaxDB & Content Server ODBC Driver - March, 18 2014 9:00 - 10:00 GMT +1

Registration: https://websmp204.sap-ag.de/~sapidb/011000358700001169732013E (Refgistration ends at 17.03.2014)

Non-S-Users: 2014_03_18_SAP_MaxDB_ODBC_Driver_09CET_EN - Adobe Connect

We are looking forward to teaching you.

Regards, Christiane

After configuring the workcenter or the landscape in your newly installed SAP MaxDB Database Studio and when you want to close the Database studio, never close the highlighted explorer tab if you do so you will not be able to see or bring back your configuration, instead you close the window directly.

We can use command line tool DBMCLI to take backup of MAX-DB database. If you are facing problems while taking backup from MAX-DB GUI tools you can opt this option.

Steps:

               1. Open DBMCLI from commandprompt

                         dbmcli -d <SID> -u superdba,<password>

               2. Stop Database (For Offline backup)

                         db_offline

                         (or)

                         db_admin

               3. Create Backup template for data and logs.

                         For data

                              medium_put <templatename1> drive:\<location>\<filename> FILE DATA

                         For Log

                              medium_put <templatename2> drive:\<location>\<filename> FILE LOG

               4.   Connect Database

                         db_connect  

               5.  Take Complete data backup

                         backup_start <templatename1>

               6.  Take log backup

                         backup_start <templatename2>

               7.  Check backup status after completion

                         backup_state

                         (and)

                         medium_label <templatename>

               8. Start database

                         db_online       

After installing SAP MaxDB, you can immediately start using the software using the command line tools that are part of the software packages. If you prefer using a GUI tool for database administration, we recommend that you install Database Studio.

• The SAP MaxDB documentation contains information about managing SAP MaxDB databases, using the Database Studio administration tool, developing database applications using the SAP MaxDB interfaces, and much more.
• The SAP MaxDB wiki provides troubleshooting information, including a large FAQ section.
• The SAP MaxDB download area is available now via SAP Store.

In the first part of this series I discussed, how to configure a database connection to a MaxDB database instance from a SAP system (Solman 7.1 in our case) running on a non MaxDB database instance for the purpose of configuring DBACOCKPIT with MaxDB as the remote database instance to be managed.

Part-I talked about  how to setup this connection manually once we have installed and configured MaxDB client libraries as well as MaxDB database library.

In this part, I will describe how to setup  complete Technical Monitoring integration of MaxDB database in to Solman MAI , how to register the instance with SLD and configure Dbacockpit database connection through automated Managed system setup in Solman 7.1.

A valid MaxDB client and database library is required in this case as well and should be installed in same way as described in the first part of this series.

We will also be able to monitor the availability, backup status, log backup status and other KPIs for a MaxDB database through Solman

If your MaxDB is running standalone or as a database for content server , livecache or a SAP system , we first have to install a SAP diagnostic agent and a SAP hostagent on the server running the MaxDB database and register it with the SLD of solman or a central SLD.

SAP Host Agent is installed automatically during the installation of new SAP instances with SAP kernel 7.20 or higher.

How to install and configure diagnostics agent and connect it to SLD of the solution manager system and the per-requisites are described clearly here.

Home - SAP Solution Manager Setup - SCN Wiki

Once the diagnostics agent has been successfully installed and configured, for sap hostagent to successfully discover the maxdb instance and collect data related to MaxDB instance monitoring and administration, we have to configure a XUSER for the user running the diagnostic agent(smdadm) and the host agent( runs with root and sapadm user on unix)

To know more about xuser concept, check  XUSER - SAP Documentation

& sapnotes 39439 - XUSER entries for SAP MaxDB, 1997186 - sapdbctrl: SAP MaxDB XUSER logon on Unix as user sapadm

Create xuser with keys c, c_J2EE and <SID>. ( SID of Maxdb instance).

xuser -u control,"passwd" -d <SID> -n hostname -U <key>

You need to logon with the corresponding OS user and then run the command to create a key for the logged on OS user.( xuser utility is located in /sapdb/programs/bin ). Do this for the root and smdadm user.

Once this is done, the database instance should be visible in LMDB after sometime.

Now , we are ready to do the managed system setup for the Maxdb database instance in solman Technical monitoring setup.

Check the document (page 73) on how to perform managed system setup  https://websmp202.sap-ag.de/~sapidb/011000358700000482292011E

In the 2nd step provide values as below and save.DBA cockpit connection should be successfully created. Otherwise check the maxdb client and database library configuration.

After completing the managed system setup. We have to apply a technical monitoring database template of Maxdb type. ( create a new template copying from the standard). We can change threshold values in the template metrics.( like for backups, database check).

Once the template has been created and assigned to the managed object of type maxdb database. we are now ready to monitor the remote MaxDB database in Solution Manger 7.1.

Below metrics are available to be monitored and alerts can be generated in case of errors ( Email notifications, SNMP traps)

Now that we have seen and learnt how to setup Solution Manager monitoring and DBACOCKPIT for a MaxDB database , in the next part of this series, I will discuss on how to setup MaxDB database backups , create backup templates, backup mediums and a DBA planning calendar centrally in Solman which can be easily maintained and monitored as for any other database like oracle

Thanks

You have a requirement of setting up central administration of your MaxDB database to be monitored by SOLMAN 7.1 system, running on Oracle/Linux or any other DB/OS other than MaxDB.

MaxDB database instance might be standalone or an SAP application may be running on it. Content server, live cache or complete SAP system.

Also you would like to configure DBA planning calendar to schedule database backups and other DB related task centrally from solution Manager.

To achieve this, we should be able to connect to the MaxDB database instance from the solution manager 7.1 system to access database information. To realize this connection, we need to have a compatible version of MaxDB client libraries installed on all the application servers of the solution manager system.

Maxdb client is not installed by default if you are running the DBACOCKPIT on a  SAP system which is running on a database other than MaxDB.

How to check if the client is installed or not on your system.

1. Check for the Maxdb client installation on all  application servers of system using Tcode SE38/SA38 and program RSADA_CHECK_SERVERS

2. Download and Install the MaxDB Client Libraries.

822271 - FAQ: SAP MaxDB client software

Download the maxdb client runtime package from service market place. File with name MAXDBART<XXXX_XX-XXXXXXXX.SAR

Once it has been downloaded , install it as shown in steps below and run the installation using command  ./SDBINST

Set group to "sapsys" and owner to "sidadm" and continue. You can also create standard group and user but make sure that sidadm user has access to read client libraries .

Set the environment variables PATH and LD_LIBRARY_PATH and include the path of the lib and programs/bin for MaxDB client on all application servers. Logoff and login again from the shell so that the changes can take effect.

3. Download the Maxdb database library ( this is different from Maxdb client libraries) , depending upon your kernel version and uncar it to the SAP kernel directory

In my case as I am running on linux, we downloaded the linux compatible library.

Uncar and copy the library dbsdbslib.so to the SAP kernel directory

Once the environment variables have been set, and the MaxDB library copied to the SAP kernel, for the changes to take effect, restart the application servers.

Now test the client installation using the program RSADA_CHECK_SERVERS again

4. Now we are all set to define a database connection in DB59 to a remote MaxDB database

Once this has been setup , we are all set to monitor the database in DBACOCKPIT.

In the next document related to  MaxDB, i will explain how to setup DBA planing calendar to schedule activities like DB backup , log backup , check database and other activities central from the DBACOCKPIT for a remote MaxDB database.

Also I will explain, how to create the database connection from SOLMAN 7.1 managed system setup instead of creating it manually and how to setup and configure diagnostics agent and outside discovery for a Maxdb database instance and how to configure monitoring for a MaxDB remote database in SOLMAN 7.1 MAI , which is running standalone or as part of content server or livecache database.

Thanks

Amit

Hi all,

here is a list including most features and patches for our latest update of 7.8 (also part of SAP note 1364181).
For further details about the referred 'PTS' incidents you can access our 'Problem Tracking System'.

Thorsten

SP 2 Patch 41 (7.8.02.41) (January 05, 2015) (9 Features, 37 Patches)

Kernel

• Volume balancing now starts even when a new volume is added to a large number of existing volumes. Previously, this would not have changed the average filling threshold enough to trigger volume balancing (PTS 1242644).
  
• New column LOBCOLUMNCOUNT in system view FILES shows the number of defined LOB columns in the that file (PTS 1252717).
  
• The allowed maximum number of correlated columns in one SQL statement has been increased from 64 to 256 (PTS 1252781).
  
• Fix for database parameter value MaxServerTasks unwantedly increasing during param_checkall operation, if database parameter CheckDataParallelServerTasks> 0 (PTS 1252452).
  
• Fix to reduce probability of undetected deadlocks on database parameter settings involving a large MaxSQLLock value (MaxSQLLocks * RowLocksPerTransactionThreshold > 2147483647) (PTS 1252478)
  
• Fix for performance issue during insert transactions with LOB columns and database parameter EnableLobTransactionConsistency = YES (PTS 1242167).
  
• possible crashes fixed (crash at ALTER TABLE DROP FOREIGN KEY statement, PTS 1251839).
  
• Fix for error BD Buffer limit while using a hash join with extension records and missing SQL optimizer statistics (PTS 1252611).
  
• Possible kernel crash caused by killing the task starting the database analyzer is fixed (PTS 1252487).
  
• Microsoft Windows: Fix for failing backups (Access denied) when writing to a network share (UNC-path) caused by an invalid entry in the access control list of the backup file (PTS 1252703).
  
• Microsoft Windows: fix for database kernel service hanging in state starting, if started via Microsoft Windows Service Manager or Microsoft Cluster Manager (PTS 1252865).

  Interfaces 

• SQLDBC: fix for error -10811 due to numerical overflows on floating point values; to prevent this error, SQLDBC now truncates values with a negative exponent above 64 (PTS 1252847). Fix for possible error -109, LOB file dropped at INSERT statement with IGNORE DUPLICATES, if LOB content size was larger then value in database parameter CommandBufferSize (PTS 1252690).
  
• ODBC (Content Server): fixed crash in reconnect phase (PTS 1252258); fixed crash during startup (PTS 1252346).
  
• ODBC: the SQLExecute/SQLExecDirectcall now returns SQL_NO_DATA_FOUND on a non positional UPDATE or DELETE statement instead of returning SQL_SUCCESS_WITH_INFO and message cursor operation conflict (PTS 1253008).

  Tools 

• Database Analyzer: startup info message changes to add number of tables with packed unicode columns, removed detailed list of tables requiring an UPDATE STATISTICS run (PTS 1252398) and warning added if number of UKTs with user tasks exceeds value of database parameter MaxCPUs (PTS 1252572); new warning added if one of the TaskCluster* database parameters is user modified (PTS 1252663); removed warning messages for high average write times by correcting the thresholds in IOTHREAD_HIGH_READTIME and IOTHREAD_HIGH_WRITETIME (PTS 1252600).
  
• DBM Server: Handling of parameter changes improved - if a database parameter is usermodified (userdefined) a newly entered value that violates the parameter constraint implicitly drops the usermodified/userdefined flag;
  The table ACTIVECONFIGURATION now has a column that shows the database parameter modification by user;
  The database parameter ouput lines in file knlmsg have additional database parameter modification information: '(U)';
  A new DBM command param_resetusermod allows to remove the usermodified/userdefined flag for a single database parameter by resetting the value to its default and recalulating all database parameter dependencies (PTS 1252010).
  
• DBM Server: Fixed X server protocol file being flooded with repeated Cannot flush file error lines if the dbmsrv process crashes and writes a call stacktri into the dbmsrv_<host>.err file) (PTS 1223052).
  
• DBM Server: Fix for a hanging DBM server process waiting for setting a resource lock (PTS 1252224).
  
• DBMCLI: After DBM command recover_config as database system administrator, the wrong user is flagged as DBM operator, which may lead to failing commands like load_systab or db_restart (PTS 1252964) (note 2081702).
  
• DBMCLI: Fixed incomplete information for DBM command dban_state which could lead to missing status information for Database Analyzer in DBA Cockpit (transaction DBACOCKPIT)/Database Assistant (transaction DB50)/liveCache Assistant (transaction LC10) (PTS 1252379).
  
• Loader: bug fix for syntax error when calling the Loader using -n and the -U switch (PTS 1252854).

For installing or uninstalling the SAP MaxDB software in SAP systems please refer to the following information (login required):

• http://support.sap.com/installations
• SAP Note 767598

Note: The following description only applies to SAP MaxDB as a standalone database or when used for developing your own applications using the SAP MaxDB interfaces. You can download the SAP MaxDB Community edition from the SAP MaxDB download area in SCN. 

SAP MaxDB is easy to install. If you accept the default installation values, the complete SAP MaxDB software will be installed and a demo database will be created. The default software installation initially uses about 500 MB of storage space. Please note that the required storage space grows while using the database. The initial database size is extended automatically as soon as the fill level of the data area reaches 90%. For the current system requirements, see SAP MaxDB - Supported Platforms and Architectures.

After installing SAP MaxDB, you can immediately start using the software using the command line tools that are part of the software packages. If you prefer using a GUI tool for database administration, we recommend that you install Database Studio.

For more information on how to proceed after installing the software, see Getting Started with SAP MaxDB.

Installing the Database Software and Creating a Database

Microsoft Windows

1. Download the software package for Microsoft Windows to a local directory.

2. Go to the directory that contains the SAP MaxDB package you have downloaded.

3. Double-click the package.

4. Choose Start installation/upgrade.

5. Follow the instructions of Installation Manager.

6. If you want to use the database for the SAP MaxDB tutorials, enter DEMODB as the database name, and DBADMIN with the password SECRET as the database system administrator.

7. To start the installation, choose Install.

8. After finishing the installation, reboot Microsoft Windows.

Note: In some system environments you may encounter an error message when closing the Installation Manager. You can avoid this by unpacking the software package after downloading it and starting the Installation Manager directly by executing SDBSETUP.exe.

Linux

Requirements: glibc >= 2.3.3, gtk 2.x, X server (the root user must be able to access a display). Additionally, Linux i386 requires glibc with TLS (thread local storage) support.

1. Download the SAP MaxDB software package for your Linux platform.

2. Open a root shell.

3. Change to the directory that contains the SAP MaxDB package you have downloaded.

4. Unpack the SAP MaxDB package.

5. To start Installation Manager, enter ./SDBSETUP

6. Choose Start SAP MaxDB Installation.

7. Follow the instructions of Installation Manager.

8. After finishing the installation, exit the root shell.

9. Update the PATH environmental variable for the operating system user who is going to operate SAP MaxDB, for example using the following command:
export PATH=/opt/sdb/programs/bin:$PATH

10. If necessary, add it to the login profile of the operating system user as well (for example, .bash_profile in the user's home directory).

Installing Database Studio

Database Studio is the SAP MaxDB GUI tool for managing databases. From SAP MaxDB version 7.7, Database Studio replaces the tools Database Manager GUI and SQL Studio, and also offers a GUI for the Loader tool. Database Studio can also be used for managing databases of versions 7.5 and 7.6.

Database Studio uses the Eclipse platform (Eclipse 3.2); the required Eclipse software is part of the Database Studio installation package. To use Database Studio, you also need Java version 1.5 or higher.

Microsoft Windows

1. Stop all databases. For example, use the Database Manager CLI command line tool to stop a database on the local computer:
dbmcli -d ‹database_name› -u ‹database_system_administrator›,‹password› db_offline

2. Stop the SAP MaxDB X server (communication server) by entering the following command on the command line:

x_server stop

3. Download the Database Studio software package for Microsoft Windows to a local directory.

4. Go to the directory that contains the software package you have downloaded.

5. Double-click it.

5. Follow the instructions of the Installation Manager.

Linux

1. Stop all databases. For example, use the Database Manager CLI command line tool to stop a database on the local computer:
/opt/sdb/programs/bin/dbmcli -d ‹database_name› -u ‹database_system_administrator›,‹password›

For the following steps, you need root privileges. 

2. Stop the SAP MaxDB X server (communication server) by entering the following command on the command line:

/opt/sdb/programs/bin/x_server stop

3. Download the Database Studio software package for Linux to a local directory and extract it.

4. Go to the directory where you have extracted the software package.

5. Enter the following command:

‹directory_with_extracted_package›/SDBSETUP

6. Follow the instructions of the Installation Manager.

Note: Linux system environments vary greatly, meaning that you might have to install additional system software for Database Studio to run properly. If you are having trouble starting Database Studio, we recommend that you have a look at the posts in the SAP MaxDB forum (for example this one: Re: DatabaseStudio 7.8.01.10 on Linux doesn't start).

Uninstalling SAP MaxDB

To uninstall the SAP MaxDB software, including databases and tools, you also use SAP MaxDB Installation Manager.

1. Exit all SAP MaxDB programs.

2. On Linux only: open a root shell.

3. Change to the directory where you have extracted the SAP MaxDB Installer package.

4. To start Installation Manager, run SDBSETUP.

5. Choose Remove MaxDB components.

6. Follow the instructions.

Note: To uninstall the legacy tools Database Manager GUI and SQL Studio, use the standard Microsoft Windows Add and Remove Programs dialog window (Microsoft Windows only)