Contact Us

Preparing Databases

SAP HANA Database Preparation

Warning: Before starting, review the Managed Systems Preparation and Maintenance Guide page.

TaskActions
Preparation Tool (optional)In order to automate certain tasks, you can use the Preparation Tool
Install SAP HANA DB version 80 or higher

You need at least SAP HANA DB version 80, optionally install the latest SAP HANA and latest Patches from Software Downloads.

Install SAP Note 2378916

Run Outside Discovery on the HostSet SAP HANA Network configurations according to SAP standard recommendationsFor example, host names of HANA-replicated DBs need to be unique.

SAP HANA SLD Parameterization

Correct SLDSYSTEMHOME SLDVIRTDBHOME (certain use cases) of HANA DB need to be sent with SLD

As SAP HANA <DBSID>adm user, at OS level:

Configure the HANA Technical System default.pfl profile parameters for SLDSYSTEMHOME and SLDVIRTDBHOME (only in case of replication scenarios) to match with the database identifier of technical systems using this HANA system. SLDVIRTDBHOME needs to be set on all SAP HANA DB clusters in the replication scenario to the same value as reported by the ABAP or JAVA system using this SAP HANA DB as database (virtualized DB host name). SLDSYSTEMHOME is to be set in order to ensure that it makes no difference which host is the master host in a SAP HANA scale out system and it needs to be set to the same value as reported by the ABAP or JAVA system using this SAP HANA DB as database (when replication and virtualized DB host name is used). If set incorrectly, SAP HANA needs to be restarted.

This should be a regular post-installation task, however, if it is not executed correctly at installation, it needs to be adapted. 

Usage of SLD relevant parameters in the global.ini

As of HANA revisions mentioned below, the recommendation is to set the parameters sldsystemhome and sldvirtdbhome in the global.ini instead of DEFAULT.PFL. This has one big advantage - the parameters can be applied dynamically, means no HANA restart required.

To do so, please add them under the section [system_landscape_hostname_virtualization].

sldsystemhome as of HANA 1.00.122.16, 2.00.012.04, 2.00.023 and higher.

sldvirtdbhome as of HANA 1.00.122.13, 2.00.012.02, 2.00.020 and higher. 

For HANA SR running on scale-out and/or by specifying any other values than internal hostnames (e.g. tenant specific) for sldsystemhome in a SR setup, consider to add an entry under [system_landscape_hostname_resolution] for all internal host names in the SR landscape on all sites! As a value have to enter the value from sldsystemhome of the particular SR site.

Example 1: 2-Tier System Replication with scale-out setup

  • SiteAHost1 = SiteAHost1
  • SiteAHost2 = SiteAHost1
  • SiteBHost1 = SiteBHost1
  • SiteBHost2 = SiteBHost1

Example 2: 3-Tier System Replication with tenant specific sldsystemhome values

  • SiteAHostName = SomeValueSiteA
  • SiteBHostName = SomeValueSiteB
  • SiteCHostName = SomeValueSiteC

Background: this parameter is required to ensure that each SR site can resolve the host name of other sites.

There is one more parameter which is called enable_virtdbhome. This parameter is responsible for the association between the virtual and physical databases. Once the sr_register command is executed, a secondary system will be registered with a primary system. This results in a parameter change enable_virtdbhome = yes for the primary and = no for the secondary system. Such a parameter change is done automatically (e.g. every time when a take over is executed) and in most of the cases does not require a manual adjustment.

This parameter (enable_virtdbhome) has been introduced with the following HANA revisions:

  • HANA 2.0 SPS02 Rev00  2.00.020
  • HANA 2.0 SPS01 Rev02  2.00.012.02
  • HANA 1.0 SPS12 Rev13  1.00.122.13

 Therefore, if the minimum required revision is installed, please check if the parameter really exists in nameserver.ini (section 'sld') and has the correct value as mentioned above.

SAP HANA Replication ScenariosFor SAP HANA revisions < 122.04 the handling of SAP HANA replication scenarios is not complete in the SAP HANA SLD data supplier and therefore manually adding of replication and virtual DB links in LMDB of Solution Manager is required. See section: manual adjustment of LMDB for SAP HANA replication scenarios.
Check if an SLD Data Router (SLDR) is neededAs prerequisites, you need to choose, according to your landscape, if an SLDR is required see page Preparing System Landscape Data Router.

Check Needed Data Suppliers

The SAP HANA DB can be used in stand-alone or associated to an ABAP or Java Stack

The SAP HANA DB can be used in stand-alone or associated to an ABAP or Java Stack. Therefore, the corresponding Data Supplier needs to be setup. See the SAP NetWeaver Application Server ABAP Preparation or SAP NetWeaver Application Server Java Preparation pages.

Note: To ensure that the Database supplied by the ABAP Data Supplier fits to the Database reported by the HANA Data Supplier, you shall set the parameter SLDSYSTEMHOME on the ABAP / JAVA Stack to the value of VIRTDBHOME (or SLDSYSTEMHOME) of the HANA Database.

In case you plan to use FQDN for the above mentioned parameters, consider the limitations in SAP Note 2607076.

Data Supplier

SAP HANA Database provides its own Data Supplier (SAP HANA Database Data Supplier)

HANA SLD Registration can be done in two ways:

1-Using HANA Studio:

Open the SAP HANA database lifecycle manager (HDBLCM) to configure the HANA SLD DS connection parameters (namserver.ini and Connection credentials) for the system registration in SAP Focused Run. This can be done via command line interface or Graphical User Interface. Check the SAP HANA Administration Guide in the "Configuring HANA System to Connect to the SLD" section.

Note: The Payload can be send also by switching the "nameserver.ini" parameter "SLD Active" in the HANA Studio.

2- Using the "hdblcm" command command line. Exemple As <sid>adm user, or root user, at OS level:

  • Generate slddest.cfg file by running: /hana/shared/<SID>/hdblcm
  • Choose Option 5 "configure_sld" and provide SLD parameters
  • If hdblcm was executed the first time, the Datatransfer is triggered immediately. If an existing configuration is changed, the data will be send within the next 12 hours.
  • Check the slddest.cfg: /usr/sap/<DBSID>/SYS/exe/hdb> sldreg -showconnect /usr/sap/<SID>/SYS/global/slddest.cfg
  • Restart the service to send the payload /usr/sap/<DBSID>/HDB<inst>/exe> sapcontrol -nr <instance> -function RestartService
  • Data transfer result  can be checked in sldreg.log located in the trace directory of the HANA installation.

See also the HANA Troubleshooting Guide

Create SAP HANA monitoring user and provide connection credentials.

SAP Focused Run uses SAP Host Agent Web methods to get DB monitoring data. 

Create a SAP HANA user on DB level with proper authorizations and maintain the hdbusertore with associated credentials.

You need to first confirm whether your SAP HANA Technical System it is based on a single DB, or part of a Multi Database Container (MDC) and this either on a system DB or on a tenant DB. If you are unsure, use one of the following ways to determine the type:

First of all in the HANA studio you see SYSTEMDB@<SID> for a system DB in a MDC, or you see <DBNAME>@<SID> for a tenant DB in a MDC.

If needed, you can also look-up the SAP HANA Technical System definition using the LMDB (Object Maintenance) from the Launchpad your SAP Focused Run system, since the SLD Data Supplier registration was already performed (see previous task). When you visualize the Technical system in LMDB, press the Details button.

When selecting the tab Properties, search for the property IsSystemDB. The value will be false for a single DB (and also for a tenant DB in a MDC).

Also you can select the tab Associated Instances, and sort on the Associations. If there is an association SAP_HDBSystemSubDatabase, then it is part of a MDC.

The SAP Host Agent provides a method to create this user and maintain the hdbuserstore within one single OS command. See also SAP Note 2023587.

 

Depending on the SAP HANA DB type:

  • For single DBs, or SYSTEMDB of a Multi Database Container (MDC):

Run OS command in context of user sapadm:

/usr/sap/hostctrl/exe/saphostctrl -dbname <SID>-SYSTEMDB -dbinstance HDB<instnr> -dbtype hdb -dbuser SYSTEM -dbpass <dbpassword> -function SetDatabaseProperty DBCredentials=SET -dboption User=SAPDBCTRL -dboption Password=<desiredPassword>

Note: In the hdbuserstore the following key will be updated: <SID>SAPDBCTRL

  • For tenant DBs of a Multi Database Container (MDC):

Run OS command in context of user sapadm: 

/usr/sap/hostctrl/exe/saphostctrl -dbname <DBNAME - Like displayed in HANA Studio>  -dbinstance HDB<instnr> -dbtype hdb -dbuser SYSTEM -dbpass <dbpassword> -function SetDatabaseProperty DBCredentials=SET -dboption User=SAPDBCTRL -dboption Password=<desiredPassword>

Note: In the hdbuserstore the following key will be updated: <SID>SAPDBCTRL<TenantSQLPort>

The <TenantSQLPort> is usually 30<instnr>41 for the first installed tenant, and 30<instnr>44 for the second, and so on.

In case this MDC was migrated from a single DB, then the <TenantSQLPort> for the first tenant DB is usually 30<instnr>15 as it keeps the port that had been used before the migration.

Options to Achieve Automation

Performed either manually or in OS script

  • Central SAP HANA user management
  • Local or remote call of SAP Host Agent function SetDatabaseProperty.
Switching the monitoring data collection mechanism (highly recommended)
Deploy system analysis data collectors

Download and deploy custom operation from SAP Note 255664. In order to get them installed you need to unpack the the file from this note using the user root into the directory /usr/sap/hostctrl/exe/operations.d on each host of the HANA DB system.

Example: Assuming the attachment file was copied to /tmp this can be done via the following shell command sequence:

  • cd /usr/sap/hostctrl/exe/operations.d
  • tar -xzvf /tmp/HANA_SQL_OPERATIONS.tar.gz
SAP HANA Webdispatcher Parameterization (since SAP Focused Run 1.0 FP01).

Since SAP Focused Run 1.0 FP01, the RUM Application is able to monitor XS Traffic.

Configure the HANA Webdispatcher from HANA Studio like following:

  • Open the configuration tab
  • Select the webdispatcher.ini parameter
  • Drilldown to profile
  • Right Click and select "Add Parameter"

icm/HTTP/logging_0 = PREFIX=/, LOGFORMAT=%t %h %u - "%r2" %s %b %L epp[%{sap-passport}i] fesr[%{SAP-Perf-FESRec}i] fesropt[%{SAP-Perf-FESRec-opt}i],  LOGFILE=$(DIR_INSTANCE)/trace/http_fe.log, MAXSIZEKB=25000, SWITCHTF=day, FILEWRAP=on

Review SAP Note for latest metric definitions (optional) 

If a specific metric is missing or there are issues with the existing set of HANA metrics, please review SAP Note 2422465.
Post-upgrade activities after HANA 1.x to HANA 2.x upgrade  

In case of HANA 1.0 to HANA 2.0 upgrade please perform the following steps: 

  • Adjustment of hdbuserstore (required due to introduction of MDC as of HANA 2.0).
    Reason: failed hdbconnectivity as the KEY for the System DB does not exist yet and the KEY for the tenant needs to be adjusted. 
    Solution: Refer to the note (2621457 - hdbconnectivity failure after upgrade to 2.0).
  • Removal of obsolete LMDB entries. 
    Reason: After the upgrade the old product version of HANA 1.0 still remains in the LMDB.
    Solution: Execution of clean up LMDB report (2733868 - Repair LMDB data for HANA system after HANA Upgrade).
  • Perform the Simple System Integration for SYSTEM DB.
  • Re-execute the Simple System Integration for the tenant DB.
Monitoring of SAP HANA XSAThe relevant steps can be found under the section SAP HANA XS Advanced on Preparing Managed Systems page.

SAP Adaptive Server Enterprise (ASE) Database Preparation

Warning: Before starting, make sure you studied the  Managed Systems Maintenance Guide page.

TaskActions
Install ASE DB 15.7 or higher

You need at least ASE DB 15.7, optionally install the latest ASE DB and latest Patches from support.sap.com/swdc -> Databases -> SAP Adaptive Server Enterprise

To check details which ASE DB monitoring feature is requiring which SAP Hostagent version please see SAP Note 2577046.

Check Security Guide and especially SAP Note 2236137 - SYB: saphostctrl/sapdbctrl - enable discovery for native ASE database installations.

SAP Focused Run supports monitoring of ASE HADR configurations with Replication Management Agents (RMA) accordingly to the documentation:

Run Outside Discovery on the Host

As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in page Preparing Outside Discovery.

Be aware the hostname interpreted as DB Hostname by Outside Discovery is the first entry set in file in $ASE_HOME$/interfaces

Note: This hostname should be the same as SLDSYSTEMHOME set in SAP NetWeaver ABAP or j2ee/dbhost in SAP NetWeaver JAVA (see also SAP Note 1052122).

ASE HADR cluster: The configuration of outside discovery for ASE HADR cluster is described in SAP Note 2577046 "SYB: saphostctrl - Changelog for ListDatabaseMetrics function of SAP Host Agent" in section “Setup”.

Check Needed Data Suppliers

The SAP ASE DB can be used in stand-alone or associated to an ABAP or Java Stack

The SAP ASE DB can be used in stand-alone or associated to an ABAP or Java Stack. Therefore, the corresponding Data Supplier needs to be setup. See the SAP NetWeaver Application Server ABAP Preparation or SAP NetWeaver Application Server Java Preparation pages.

Create DB monitoring user and provide connection credentials

SAP Focused Run utilizes SAP Host Agent Web methods to get DB monitoring data from sapsa as in rsecssfs secure store with key DB_CONNECT/SYB/SADB_USER.

  1. Create the DB monitoring user for the ASE database with the right authorization. 
  2. Create an entry for the monitoring user in the secure store.

    Note: The SAP Host Agent provides a simple method, for 1 and 2, following SAP Note 1797040.

  3. Initialize (once) the ASE DB monitoring

If the ASE DB monitoring was not initialized with the Transaction "DBACockpit" do the following: 

For all ASE DB, the execution of the SAP Host Agent method 

saphostctrl -function SetDatabaseProperty -dbname <SID> -dbtype syb SETUP_LIST_METRICS=saptools is recommended (easier than to configure a remote DBA Cockpit Connection to a remote ABAP System).

Note: All SAP Host Agent methods can be executed and scripted local or remote by a saphostctrl or any other webservice client.

Alternative process: The monitoring user can be created by ASE user management sqls using ISQL. The secure store can be maintained by OS command rsecssfx.

SAP MaxDB Database Preparation

Warning: Before starting, make sure you studied the page Managed Systems Maintenance Guide page.

TaskActions
PrerequisitesMinimum requirement for the SAP Host Agent is 7.21 SP22
Install SAP Max DB 7.9.08 Client Build 40 or higher

You need at least SAP Max DB 7.9.08 Client Build 40, optionally install the latest SAP MaxDB Client and latest Patches from support.sap.com/swdc -> Databases -> SAP MaxDB

The installation of the MaxDB Client is described in SAP Note 649814.

Create the User Store
  • If a sapdbctrl user is already created on Max DB, remove it.
  • As root User, add Write permissions to the /usr/sap/hostctrl/exe folder
  • Create the User Store for sapadm: /usr/sap/hostctrl/exe/saphostctrl -host <hostname> -user sapadm <password> -dbname <dbname> -dbtype ada -function SetDatabaseProperty DBCredentials=SET -dboption User=SUPERDBA -dboption Password=<SUPERDBA Password>
  • Delete the Write permissions to the /usr/sap/hostctrl/exe folder.

See also how to set connection information in SAP Note 2018919

Note: can be automated by os script

Check created User Store

Check created User Store: /sapdb/programs/bin/xuser list

Note: can be automated by os script

Check Database status

Optional (eg. for debugging)

/hostctrl/exe/saphostctrl -function ListDatabases
/hostctrl/exe/saphostctrl -function GetDatabaseStatus –dbname <DBNAME> -dbtype ada

Run Outside Discovery on the HostAs prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in page Preparing Outside Discovery.

Microsoft SQL Database Preparation

Warning: Before starting, make sure you studied the  Managed Systems Maintenance Guide page.

TaskActions
Install Database
Install MS-SQL 2008 or higher
You need at least MS-SQL 2008, optionally install the latest MS SQL DB and latest Patches from support.sap.com/swdc -> Databases -> MS SQL Server

Create DB monitoring user and provide connection credentials

SAP Focused Run uses SAP Host Agent Web methods to get DB monitoring data. For MSSQL DB, the connection credentials are part of windows authorizations.

Check that your MSSQL installation follows the recommendations in SAP Note 1877727 and SAP Note 1564275.

Be aware the hostname interpreted as DB Hostname by Outside Discovery discovery is the hostname as set in Windows registry as BackConnectionHostNames described in SAP Note 1564275 and should be the same as SLDSYSTEMHOME set in SAP NetWeaver ABAP or j2ee/dbhost in SAP NetWeaver JAVA (see also SAP Note 1052122).

Note: Can be automated by os script.

Run Outside Discovery on the HostAs prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in page Preparing Outside Discovery.
Get DB metrics from the OS

Optional operation to test the metric collection on OS level:

/usr/sap/hostctrl/exe/saphostctrl -function ListDatabaseMetrics -dbname <DBname> -dbinstance <Instname> -dbtype mss 

Support of MSSQL Always On scenario

Prerequisites: 

  • Listener configuration (1772688 - SQL Server Always On Availability Groups and SAP NetWeaver based applications)
  • SAP Focused Run 4.0 FP01 or higher
  • SAP Host Agent 7.22 PL62 or higher

Configuration steps on OS:

  • Create the http.server.settings file under C:\Program Files\SAP\hostctrl\exe\config.d folder on every replication host. 
  • Add following entry:

    OutsideDiscovery {​​​​​​
      DatabaseDiscoveryMethod : databasesystem
    }​​​​​​
  • Restart the Host Agent or execute C:\Program Files\SAP\hostctrl\exe\saphostctrl.exe -function ReloadConfiguration
  • Execute the Outside Discovery
  • Create  a sapdbctrl user on all AlwaysOn nodes by calling

     saphostctrl.exe -function SetDatabaseCredential -dbtype mss -dbname databasename Password="some password"

    For a named SQL instance, add the dbinstance, i.e.:
    saphostctrl.exe -function SetDatabaseCredential -dbtype mss -dbname databasename -dbinstance instancename Password="some password"
    Background: this command will create the default credential (SAPDBCTRL) in the credential vault and SQL, and it is used by the primary node to connect to secondaries to retrieve metrics.

    Remark: at the moment, if a failover occurs there will be no automatic detection triggered by the Outside Discovery. Means, in worst case, it could take up to 12 hours to detect and to reflect it in SAP Focused Run. In order to ensure that the monitoring getting reconfigured on a new primary as soon as possible, either set the Outside Discovery frequency to the highest supported - 60 minutes (by passing additional parameter "- frequency <minutes>" while executing the ConfigureOutsideDiscovery) or perform the ExecuteOutsideDiscovery manually.
    In the near future, in one of the upcoming SAP Host Agent patch levels, it is planned to introduce the failover detection mechanism.

IBM DB2 for LUW Database Preparation

Warning: Before starting, make sure you studied the  Managed Systems Maintenance Guide page.

TaskActions

Install database

Install IBM DB2 for LUW 9.7 or higher

You need at least IBM DB2 for LUW 9.7, optionally install the latest IBM DB2 for LUW 9.7 and latest Patches from support.sap.com/swdc -> Databases -> DB2
Configure Database for non-SAP NetWeaver systemsDatabase configuration according to SAP recommendations; especially all MON_* configuration parameters. See SAP Note 1334923.
Check the "db2greg" executable availability

Optional operation

The DB2 plugin of the SAP Host Agent calls the db2greg executable to detect installed IBM DB2 databases. This Plugin needs to be present on the filesystem, otherwise no IBM database can be detected by the SAP Host Agent during Outside Discovery Execution.

Search sequence is

/db2/%3[A-Z0-9]/sqllib/bin/db2greg
/db2/db2%3[A-Z0-9]/sqllib/bin/db2greg 
/usr/local/bin/db2ls

Note: %3[A-Z0-9] is the pattern for <SID>. 

Check that the "db2greg" plugin is properly deployed to this directory by SAP and IBM Standard (depending on version and product) for managed Systems on IBM DB2 or Standalone IBM DB2 with SAP Focused Run.

Check returned database properties

Optional operation

From the hostctrl exe folder execute: saphostctrl -function GetDatabaseProperties -dbname <DBSID> -dbtype db6

Web method returned successfully:

Database/DBRelease=09.07.xxxx
Database/ConfigurationDirectory/Default=/<DBTYPE>/<DBSID>/sapdbctrl-config
Database/InstanceList=Name=0;Host=<FDQN>;Port=xxxx
Database/ConnectAddress=
Database/ManagementHosts=<hostname>

IBM DB2 bug fix to implementIn case you are using SHA PL29, you might face a DB2 Defect related to db2gcf and the reporting of instances. Check the IBM DB2 Website
Run Outside Discovery on the HostAs prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in page Preparing Outside Discovery.

Check Needed Data Suppliers

The IBM DB2 DB can be used in stand-alone or associated to an ABAP or Java Stack

The IBM DB2 DB can be used in stand-alone or associated to an ABAP or Java Stack.

Therefore, the corresponding Data Supplier needs to be setup.

See the SAP NetWeaver Application Server ABAP or SAP NetWeaver Application Server Java pages.

LMDB database association

Virtualization relations of the database must be done manually

Optional operation

Open LMDB and search for your virtual DB. Check the assigned Physical / Logical Database. 

Oracle Database Preparation

Warning: Before starting, make sure you studied the Managed Systems Maintenance Guide page.

TaskActions
Install Oracle DatabaseOptionally install the latest Oracle DB and latest Patches from support.sap.com/swdc -> Databases -> Oracle

Create DB monitoring user and set connection credentials

 

No specific tasks are to do be performed for Oracle database. The SAP Host Agent can manage the connection to an Oracle DB by itself without additional credential.

In the case of connection problems, see SAP Host Agent Troubleshooting Guide (Oracle DB) page.

As of version 7.22 PL53, SAP Host Agent provides support for named logon to an oracle database system to execute read-only functions 
For details please refer to 3080093 - Manage Connect User Credentials for ORACLE databases in SAP Host Agent

Run Outside Discovery on the HostAs prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in Preparing Outside Discovery page.
Support of BR*tools based metricsPrerequisites: at least SAP Host Agent 7.22 PL57 and SAP Focused Run 3.0 monitoring content delivery version 17.
Monitoring of Oracle RAC 

Prerequisites:

  • at least SAP Host Agent 7.22 PL56 to be installed on all Oracle RAC hosts
Configuration steps:
  • create the http.server.settings file (2724592 - SAP Host Agent Outside Discovery ComputerSystem configuration --> http.server.settings permissions) under /usr/sap/hostctrl/exe/config.d folder on both hosts. There you have to maintain the following:

    OutsideDiscovery {​​​​​​​
        DatabaseDiscoveryMethod : databasesystem
        DatabaseOverride {​​​​​​​
            dbsystem : <dbtype>/<dbname>/<dbinstance>/<hostname> {​​​​​​​​​​​​​​
                set {​​​​​​​​​​​​​​​​​​​​​
                    no_addr_local_check {​​​​​​​​​​​​​​​​​​​​​
                        identicaldbhost : <virtual-hostname>*
                    }​​​​​​​​​​​​​​​​​​​​​
                }​​​​​​​​​​​​​​​​​​​​​
            }​​​​​​​​​​​​​​​​​​​​​
        }​​​​​​​​​​​​​​​​​​​​​
    }​​​​​​​​​​​​​​​​​​​​​
    * <virtual-hostname> should be = Logical host name for SAP Solution Manager mentioned in the SAP note 1738351.
    Remark: please do not use a scan listener hostname for that purpose!
  • Restart the Host Agent on both servers or execute  /usr/sap/hostctrl/exe/saphostctrl -function ReloadConfiguration.
  • Execute the Outside Discovery - as a result there should be one virtual DB linked to the physical DB containing both (all) instances.
  • Reconfigure the system monitoring by re-applying the database template or executing the Simple System Integration

Example of the configuration file for one DB running on two Oracle RAC nodes:

1 Oracle DB on host 1:
OutsideDiscovery {​​​​​​​​​​​​​​​​​​​​​
    DatabaseDiscoveryMethod : databasesystem
    DatabaseOverride {​​​​​​​​​​​​​​​​​​​​​
        dbsystem : ORA/ABC/ABC001/oraxdb01 {​​​​​​​​​​​​​​​​​​​​​
            set {​​​​​​​​​​​​​​​​​​​​​
                no_addr_local_check {​​​​​​​​​​​​​​​​​​​​​
                    identicaldbhost : orax-db
                }​​​​​​​​​​​​​​​​​​​​​
            }​​​​​​​​​​​​​​​​​​​​​
        }​​​​​​​​​​​​​​​​​​​​​
   }​​​​​​​​​​​​​​​​​​​​​
}​​​​​​​​​​​​​​​​​​​​​

 

1 Oracle DB on host 2:
OutsideDiscovery {​​​​​​​​​​​​​​​​​​​​​

    DatabaseDiscoveryMethod : databasesystem
    DatabaseOverride {​​​​​​​​​​​​​​​​​​​​​
        dbsystem : ORA/ABC/ABC002/oraxdb02 {​​​​​​​​​​​​​​​​​​​​​
            set {​​​​​​​​​​​​​​​​​​​​​
                no_addr_local_check {​​​​​​​​​​​​​​​​​​​​​
                    identicaldbhost : orax-db
                }​​​​​​​​​​​​​​​​​​​​​
            }​​​​​​​​​​​​​​​​​​​​​
        }​​​​​​​​​​​​​​​​​​​​​
   }​​​​​​​​​​​​​​​​​​​​​
}​​​​​​​​​​​​​​​​​​​​​

 

Remark: in case of multi DB installation, all relevant dbsystems must be maintained in this file!

Monitoring of Oracle Data Guardnot supported

SAP IQ Database Preparation

Warning: Before starting, make sure you studied the page Managed Systems Maintenance Guide page.

TaskActions
Install SAP IQ Database (formerly Sybase IQ)

You need at least SAP IQ DB 16.0, optionally install the latest version of the SAP IQ DB and latest Patches (please be aware there is an actual issue with 16.1, for more information check SAP KBA 2719876) from support.sap.com/swdc, Software Downloads, Search for SAP IQ 16.0 (see also SAP IQ installation guide).

Operating Systems:  AIX 64, HP-UX on IA64, Linux on IA64, Linux on POWER, Linux on X86_64, Solaris for X64, Solaris / Sparc 64, Windows Client 64-BIT, Windows for X86_64

When configuring the database, do not use the option "-sb 0" or "-sb 1". While it might be tempting to hide the database from discovery by the dblocate tool, you also hide it from discovery by the SAP Host Agent and thus cut it off from monitoring. Also avoid to let the database listen on the default port 2638 as this may lead to conflicts with a utility database or a demo database on the same host.

Set DBA User and Configure SAP IQ DB Server

1. Create siqconfig.cfg

1.1. collect the following data:

  • DB-NAME - The filename of the database file without path and without extension
  • DB-INSTANCE - The value of the startup parameter "-n" – see the database configuration file
  • DB-PORT - The listen port of the database, see startup parameter "-x"
  • IQ-HOME - The parent directory of the directory IQ-16_* which is parent of bin64, lib64 etc.
  • IQ-DIR - The name of the directory IQ-16_*
  • DB-LOCATION - The full path of the database file
  • CFG-LOCATION - The full path of the database configuration file
  • DBA-USER - User ID with DBA privileges
  • DBA-PASSWD - Password of above user

1.2. From /usr/sap/hostctrl execute:

exe/saphostctrl -function  SetDatabaseProperty -dbname <DB-NAME> -dbtype siq -dbinstance <DB-INSTANCE> -dboption port=<DB-PORT> -dboption iqhome=<IQ-HOME> -dboption iqdir=<IQ-DIR> -dboption dblocation=<DB-LOCATION> -dboption cfglocation=<CFG-LOCATION> SIQENTRY=INSERT

Example: IQ is installed in /usr/sap/sybase/server, database and configuration are in /usr/sap/sybase/data/db and named SAPIQDB.db and SAPIQDB.cfg, respectively. The instance is named SAPIQ_SERVER and listens on port 45678. Then the data looks like:

  • DB-NAME - SAPIQDB
  • DB-INSTANCE - SAPIQ_SERVER
  • DB-PORT - 45678
  • IQ-HOME - /usr/sap/sybase/server
  • IQ-DIR - IQ-16_0
  • DB-LOCATION - /usr/sap/sybase/data/db/SAPIQDB.db
  • CFG-LOCATION - /usr/sap/sybase/data/db/SAPIQDB.cfg
  • DBA-USER - DBA
  • DBA-PASSWD - sql

execute: exe/saphostctrl -function SetDatabaseProperty -dbname SAPIQDB -dbtype siq -dbinstance SAPIQ_SERVER -dboption port=45678 -dboption iqhome=/usr/sap/sybase/server -dboption iqdir=IQ-16_0 -dboption dblocation=/usr/sap/sybase/data/db/SAPIQDB.db -dboption cfglocation=/usr/sap/sybase/data/db/SAPIQDB.cfg SIQENTRY=INSERT

1.3. Check work/siqconfig.cfg:

iqhost123:/usr/sap/hostctrl # cat work/siqconfig.cfg

#---
instance=SAPIQ_SERVER
port=45678
database=SAPIQDB
host=iqhost123
started=0
dblocation=/usr/sap/sybase/data/db/SAPIQDB.db
cfglocation=/usr/sap/sybase/data/db/SAPIQDB.cfg
iqhome=/usr/sap/sybase/server
iqdir=IQ-16_0

2. Create credential store

2.1. From /usr/sap/hostctrl execute:

exe/saphostctrl -function  SetDatabaseProperty -dbname <DB-NAME> -dbtype siq -dboption user=<DBA-USER> -dboption password=<DBA-PASSWD> SIQUSERCREDENTIAL=INSERT

Example: execute exe/saphostctrl -function  SetDatabaseProperty -dbname SAPIQDB -dbtype siq -dboption user=DBA -dboption password=sql SIQUSERCREDENTIAL=INSERT

Check DB status

Optional operation

Execute: dblocate

Note: In order to run this (and other IQ related programs) you need to source the following script first:

<IQ-HOME>/IQ.sh for sh, ksh, bash or

<IQ-HOME>/IQ.csh for csh

The output of dblocate lists all sybase database servers, IQ, ASE, SQL Anywhere, with server name, IP address and listen port that respond to a network broadcast.

From /usr/sap/hostctrl execute: exe/saphostctrl -function ListDatabases

From /usr/sap/hostctrl execute: exe/saphostctrl -function Get DatabaseStatus -dbname <SAPIQDB> -dbtype siq

Run Outside Discovery on the HostAs prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in Preparing Outside Discovery page.