- About MDB
- Installation
- Upgrade
- Concepts
- User Interface
- Source Requirements
- Target Database Requirements
- Target Kafka Requirements
- Usage Restriction
- Frequently Exceptions
- Release Note
MDB Node Function
In the MDB system, a node is an endpoint in the replication process and corresponds to a database system.
A node can be a local (located in the server where the MDB system is deployed) or remote (located in a remote server) node.
A node can be used as a source database (for capturing data) or a target database (for synchronizing data).
Node List
Fuzzy search is supported by the node name, username, IP address, and service name. Currently, only MogDB and Oracle are supported.
Node Addition
-
Add an Oracle node
For the Oracle node, you can choose connection type
ServiceName
orSID
, and clickTest Connection
. After the test is successful, clickOK
. If a channel uses an Oracle node as a source node, see Oracle for database configuration and user permission description. If an Oracle node is used as a target node, see Target Database Requirement. -
Add a MogDB node
After a MogDB node is added, click
Test Connection
. After the test is successful, clickOK
. If a channel uses a MogDB node as a source node, see MogDB for database configuration and user permission description. If a MogDB node is used as a target node, see Target Database Requirement. -
Add a MySQL node
After a MySQL node is added, click
Test Connection
. After the test is successful, clickOK
. If a channel uses a MySQL node as a sourcenode, see MySQL for database configuration and user permission description. If a MySQL node is used as a target node,see Target Database Requirement. -
Add a PostgreSQL node
After a PostgreSQL node is added, click
Test Connection
. After the test is successful, clickOK
. If a channel uses a PostgreSQL node as a sourcenode, see PostgreSQL for database configuration and user permission description. If a PostgreSQL node is used as a target node,see Target Database Requirement. -
Add a SQL Server node
After a SQL Server node is added, click
Test Connection
. After the test is successful, clickOK
. If a channel uses a SQL Server node as a sourcenode, see SQL Server for database configuration and user permission description. If a SQL Server node is used as a target node,see Target Database Requirement. -
Add a DB2 node
After a DB2 node is added, click
Test Connection
. After the test is successful, clickOK
. If a DB2 node is used as a target node,see Target Database Requirement. -
Add datahub node
After a datahub node is added,Only used as a target node.
-
Add kafka node
After a kafka node is added,Only used as a target node.
Node Updating
If a node is not used by a channel, the connection test passes and is saved after node updating. If a node is used by a channel, pause data synchronization, and re-execute related tasks after node updating.
Connection Test
This is a node connection test. If the connection fails, abnormal connection information is returned.
Node Deletion
If a node is not used by a channel, delete it directly. If a node is used by a channel, delete the channel first and then delete the node.
Advanced configuration
Currently, only MogDB nodes are supported
Parameter | Default | Description |
---|---|---|
characterSet | Default current connection character set | Connection character set: GBK,UTF-8 |
internalHiddenColumns | CMAX,CMIN,CTID,TABLEOID,TID,XMAX,XMIN | Hide column name processing |