DBCO - Secondary DB connections monitor

Data Description

In some cases SAP system might has secondary DB connections maintained in the DBCO tcode. The extractor helps to extract them and perform connection test to ensure the connection is still accessible. The extractor is inactive by default and needs to be activated if needed.

Potential Use Cases

This event could be used for the following scenarios:

• Have an overview on secondary DB connections maintained in the system

• Alert when some of secondary DB connections are not accessible

• Correlate connection accessibility with other processes in the system (depending on where they are used)

Splunk Event

The event will look like this in Splunk:

Following fields are used to describe connection health:

• PING_RC - contains 'X' when the ping was successful

• PING_ERROR - in case the connection ping was not successful, the field contains error description

SAP Navigation

DBCO transaction in SAP: