DBA Cockpit:Non-ABAP/Java Oracle databases

Technology Blogs by Members

Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!

We have many applications in our SAP productive landscape apart from regular ABAP and JAVA stack systems, which have oracle or other database technology as the underlying database platform.

An example of this type of application can be SAP MDM or SAP business objects..

These type of application's databases can not be monitored by CCMS or SAP Solution Manager as they don't have have the underlying pre-requisites such as BRTOOLS configured or do not meet the name and structure of a standard SAP Database.

Step 1

First and foremost pre-requisite in achieving the goal of monitoring a remote non ABAP/JAVA SAP oracle database is to configure brtools so that we can use regular brtools features or DB13 planning calendar to take backups and do other actions.(check, delete logs). Please check SAP note 320457 for further details on how to configure it and what other types of applications are supported.

Broad steps involved are as follows:

Create a separate tablespace and user and grant proper authorizations.

Creating a backup profile* init<DBSID>.sap (Copy a backup profile from standard SAP system and edit it)

Create OPS$ users and implement SAPDBA role.

Once this has been configured, we can create a new database connection in DBACOCKPIT transaction in SAP solman system and monitor the oracle database.

Use SAP note 1139623 , and install/run the scripts>rz20_nonabap.sql and dbcheckoraxx_oltp as per your database version and create synonyms for schema user as mentioned in the sap note.

Use SAP note 706927 and run script dbac_install.txt for your database schema user to be able to use ST04/Dbacockpit t-code for your database.

Once the above steps have been executed successfully on the remote non ABAP/JAVA database, checkbox "Collect Alert Data" becomes active and selectable in DBACOCKPIT otherwise it's non selectable

The CCMS related data for the database would be available used remote database MTEs in RZ20.

Step 2:

For the purpose of configuring a DBA planning calendar and to be able to execute DB13 actions from the SAP solman system, there might be need to install a standalone SAP gateway.

The user which is running the standalone SAP gateway ( <sid>adm) should be able to run and execute brtools commands and should be part of groups "dba" and "oper" in case of unix platform.

Configure the environment profiles of gateway user as well, to be able to run and execute BRTOOLS commands and menu.

Once this has been configured/installed , create a database connection from solman system to the remote oracle database. either manually or if using solman 7.0 SP18 or above or solman 7.1 use transaction solman_setup to create the connection.

Please check SAP note 1261329 on how to create the connection.

Note:It might also be necessary to install a SAP diagnostics agent to be able to use the monitoring and alerting feature in solman 7.1 MAI.

Once the connection has been created, it will generate an RFC as well of type Tcp/ip(T) namely SAPXPG_DBDEST_<Server_Name>. The RFC should have proper details maintained for sap gateway host and service and correct path to sapxpg utility.

sapxpg utility should be available in the environment profile PATH of the gateway user.( user with which the gateway is running).

Step 3

For receiving automated alerts/tickets , you can assign the oracle database to an appropriate monitoring template in solman technical monitoring and activate monitoring.