Page tree
Skip to end of metadata
Go to start of metadata

Remote Database (using ADBC)

Run Mode: BACKGROUND AND DIALOG Aggregation: NATIVE Iteration: SUPPORTED Duplicate Check: SUPPORTED 

Metadata retrieval: SUPPORTED Extraction Strategy: INDUVIDUAL SELECTION AND KEY BASED SELECTION Special Permissions: REQUIRED Please check here

 

You choose this for a non-ABAP system where you can establish a direct remote database access. The data is read via a secondary database connection using a native SQL statement with ADBC (ABAP Database Connectivity). This works for all SAP-supported RDBMS including HANA.

Parameters

ParametersDescription
Database Connection NameSpecify the connection that is used to read the data for the comparison. It is maintained in transaction DBACOCKPIT.
Database Schema NameSpecify the name of the database schema from which the data is read.
The following fields are non-editable and generated by the tool:
SQL Statement (Count)The SQL statement used to count the number of expected objects is displayed after generation.
SQL Statement (Extract)The SQL statement used to extract the source data is displayed after generation.
SQL Statement (Duplicates)Generated SQL Statement to Extract a List of Duplicate Objects

 

Direct remote database access 

In addition to its own local database, the Solution Manager can also create secondary database connections to “remote” (external) databases of other non-ABAP or non-SAP systems. The connection to a remote database uses ADBC (ABAP Database Connectivity), which is an ABAP/OO-based API and supports all official SAP-supported Database Management Systems (DBMS). It allows running native SQL queries from the ABAP stack. CDC can generate such native SQL extraction queries to read and compare the data with other data sources. The corresponding secondary database connection must be maintained with transaction DBACOCKPIT. The old method of using transaction DBCO is still supported but less user-friendly.

From a technical point of view, you need an installation of an appropriate Database Client and Database Shared Library (DBSL), for each type of SAP-supported DBMS, if not already installed. For example, if the Solution Manager runs on a MaxDB database, and you want to connect to some external application using also a MaxDB database, there is no additional installation necessary. However, if this external application runs on MS-SQL, you would need to install an additional DBSL and DB-Client from Microsoft.

The following SAP Notes provide additional information on how to setup the secondary database connections (also known as database multiconnect) for the different supported DBMS.

DBMS codeDescription SAP Note
ADA

SAP MaxDB/liveCache

955670 DB multiconnect with SAP MaxDB as secondary database
1371928 DBA Cockpit: SAP MaxDB/liveCache as remote database

DB2DB2 UDB for OS/390

160484 DB2/390: Database multiconnect with EXEC SQL
1382952 DB2-z/OS:CCMS: DBA Cockpit: DB2 for z/OS as Remote Database

DB4DB2 UDB for AS/400

146624 IBM i: Database Multiconnect for IBM DB2 for i
2033326 IBM i: Enhancements in the DBA Cockpit for the SAP Database Performance Collector

DB6DB2 UDB for LUW

200164 DB6: DB multiconnect with DB6 as target database
1267189 DBA Cockpit: DB2 for LUW as Remote Database

HDBSAP HANA database

1597627 SAP HANA connection
1664432 DBA Cockpit: SAP HANA database as remote database

MSSMicrosoft SQL Server

178949 MSSQL: Database MultiConnect
1601608 How to access an external Microsoft SQL Server database

ORAOracle

339092 DB MultiConnect with Oracle as secondary database
1261329 DBA Cockpit: Oracle as a remote database

SYBSAP ASE

1507573 External DB connect to an SAP ASE database
1532253 SYB: Remote DB Monitoring for SAP Sybase ASE

SIQSAP IQ

1737415 Sybase IQ: Enable remote/secondary connect to SAP IQ
1999431 SIQ: Setting up SSL for connections to IQ

Using SAP HANA SDA (Smart Data Access) you can connect to further remote sources not listed here, such as Hadoop, Teradata, etc. The HANA DB exposes them as virtual tables, and CDC can consume them with the source type ADBC or HANA as well. So the access path from CDC point-of-view would be SolMan/CDC => ADBC => HANA => SDA => RemoteDB.

Please see here for further information: https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.01/en-US/a07c7ff25997460bbcb73099fb59007d.html

 




  • No labels