OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

OceanBase Developer Center

V4.3.1

  • Overview
    • What is ODC?
    • Features
    • Architecture
    • Limitations
    • ODC console
  • Quick Start
    • Client ODC
      • Overview
      • Install Client ODC
      • Use Client ODC
    • Web ODC
      • Overview
      • Deploy Web ODC
      • Use Web ODC
  • Data Source Management
    • Create a data source
    • Data sources and project collaboration
    • Database O&M
      • Session management
      • Global variable management
      • Recycle bin management
  • SQL Development
    • SQL editing and execution
    • Perform PL compilation and debugging
    • Use the command-line window
    • Edit and export the result set of an SQL statement
    • Execution analysis
    • Generate test data
    • Database objects
      • Table objects
        • Overview
        • Create a table
        • Manage tables
      • View objects
        • Overview
        • Create a view
        • Manage views
      • Function objects
        • Overview
        • Create a function
        • Manage functions
      • Stored procedure objects
        • Overview
        • Create a stored procedure
        • Manage stored procedures
      • Sequence objects
        • Overview
        • Create a sequence
        • Manage sequences
      • Package objects
        • Overview
        • Create a program package
        • Manage program packages
      • Trigger objects
        • Overview
        • Create a trigger
        • Manage triggers
      • Type objects
        • Overview
        • Create a type
        • Manage types
      • Synonym objects
        • Overview
        • Create a synonym
        • Manage synonyms
  • Import and Export
    • Import schemas and data
    • Export schemas and data
  • Database Change Management
    • User Permission Management
      • Users and roles
      • Automatic authorization
    • Project collaboration management
    • Risk levels, risk identification rules, and approval processes
    • SQL check specifications
    • SQL window specification
    • Database change management
    • Logical database change management
    • Batch database change management
    • Lock-free schema changes
    • Synchronize shadow tables
    • Schema comparison
  • Data Lifecycle Management
    • Archive data
    • Clean up data
    • Partitioning Plan Management
      • Manage partitioning plans
      • Set partitioning strategies
      • Examples
    • SQL plan task
  • Data Desensitization and Auditing
    • Desensitize data
    • Operation records
  • Notification Management
    • Overview
    • View notification records
    • Manage Notification Channel
      • Create a notification channel
      • View, edit, and delete a notification channel
      • Configure a custom channel
    • Manage notification rules
  • System Integration
    • Login integration
    • Approval integration
    • SQL approval integration
  • Deployment Guide
    • Deployment overview
    • Preparations before deployment
    • Load and run an ODC image
    • Deploy ODC in high-availability mode
    • Deployment verification
  • Upgrade Guide
    • Upgrade Overview
    • Preparations before upgrade
    • Update single-node ODC
    • Update high-avaliability ODC
    • Upgrade verification
    • Rollback after upgrade failed
  • Troubleshooting
    • ODC troubleshooting process
    • Collect Message
      • View the runtime environment and version information
      • View web ODC logs
      • View client ODC logs
      • View end-to-end ODC-related logs
      • View ODC MetaDB data
      • Query the index status in OceanBase Database V4.x
      • Query the index status in OceanBase Database V1.4.x to V3.2.x
      • Collect JVM runtime information
      • Use tcpdump to capture packets
    • Common Troubleshooting
      • Deployment Upgrade
        • Web ODC cannot be accessed after startup
      • Database Connection
        • Access denied in a connection trial or test
        • Connection is refused in a connection trial or test
        • Connection times out
        • `Connection reset` is reported for a time-consuming statement
        • `socket write error` or `closed by server` is reported for a connection
      • SQL Execution
        • Disconnection during SQL execution
        • `Over tenant memory limits` is reported during SQL execution
        • `Unknown thread id` is returned during SQL execution
        • `timeout` errors returned during SQL execution
        • `OutOfMemoryError` is returned during SQL execution
        • Incomplete result columns for the SELECT statement
        • Garbled Chinese characters in the SQL execution result set
        • Garbled Chinese data is returned for query of data in GBK encoding
      • PL Object
        • Debugging is not supported for invalid PL objects
        • `JSONException` is reported during PL debugging
        • Garbled variable values in debugging
        • Failed to view PL objects or garbled characters are returned
        • PL objects cannot be executed or an execution error is returned
        • ODC issues during PL debugging
        • PL anonymous block cannot be debugged
        • Alert information of a PL object is unavailable
      • Import and Export
        • Garbled Chinese characters in an imported file in GBK encoding
        • Invalid ZIP package reported during file import
        • Time-type data exported from an Oracle tenant cannot be imported
        • Mismatched columns reported during the import of a single-table CSV file
        • Failed to export a result set in ODC to an Excel file
        • Incorrect display in Excel for a result set exported in CSV format
        • Incomplete data in batch export of multiple tables
        • `javax.crypto.BadPaddingException: Given final block not properly padded` is returned for a data import or export failure
      • Client ODC Problems
        • Client ODC startup failure / H2 Database corruption: Chuck not found
        • Garbled Chinese characters in the command-line window of ODC
        • Failed to install client ODC
        • Client ODC startup failure or no response
        • `Not a valid secret key` is returned for connection creation in client ODC
        • `User does not exist` returned for connection creation in client ODC
        • High memory usage of client ODC
        • Client ODC fails to be installed or start due to a port conflict
      • Front Page Exception
        • JavaScript exception is thrown on the ODC page
        • No response in browser after opening ODC
        • White screen in ODC
      • Account Password Problem
        • Forgot the admin account password in ODC V3.2.0 or later
        • Forgot an account password in ODC V2.4.1 to V3.1.3
        • Forgot an account password in ODC V2.4.0 or earlier
    • FAQ
      • Installation of client ODC
      • Web ODC deployment and startup
      • FAQ
      • Command-line window
      • DDL statement display
  • Release Note
    • V4.3
      • ODC V4.3.2
      • ODC V4.3.1
      • ODC V4.3.0
    • V4.2
      • ODC V4.2.4
      • ODC V4.2.3
      • ODC V4.2.2
      • ODC V4.2.1
      • ODC V4.2.0
    • V4.1
      • ODC V4.1.3
      • ODC V4.1.2
      • ODC V4.1.1
      • ODC V4.1.0
    • V4.0
      • ODC V4.0.2
      • ODC V4.0.0
    • V3.4
      • ODC V3.4.0
    • V3.3
      • ODC V3.3.3
      • ODC V3.3.2
      • ODC V3.3.1
      • ODC V3.3.0
    • V3.2
      • ODC V3.2.3
      • ODC V3.2.2
      • ODC V3.2.1
      • ODC V3.2.0

Download PDF

What is ODC? Features Architecture Limitations ODC console Overview Install Client ODC Use Client ODC Overview Deploy Web ODC Use Web ODC Create a data source Data sources and project collaboration Session management Global variable management Recycle bin management SQL editing and execution Perform PL compilation and debugging Use the command-line window Edit and export the result set of an SQL statement Execution analysis Generate test data Import schemas and data Export schemas and data Users and roles Automatic authorization Project collaboration management Risk levels, risk identification rules, and approval processes SQL check specifications SQL window specification Database change management Logical database change management Batch database change management Lock-free schema changes Synchronize shadow tables Schema comparison Archive data Clean up data Manage partitioning plans Set partitioning strategies Examples SQL plan task Desensitize data Operation records Overview View notification records Create a notification channel View, edit, and delete a notification channel Configure a custom channel Manage notification rules Login integration Approval integration SQL approval integrationDeployment overview Preparations before deployment Load and run an ODC image Deploy ODC in high-availability modeDeployment verification Upgrade OverviewPreparations before upgrade Update single-node ODC Update high-avaliability ODCUpgrade verification Rollback after upgrade failed ODC troubleshooting process View the runtime environment and version information View web ODC logsView client ODC logsView end-to-end ODC-related logsView ODC MetaDB dataQuery the index status in OceanBase Database V4.xQuery the index status in OceanBase Database V1.4.x to V3.2.xCollect JVM runtime informationUse tcpdump to capture packetsInstallation of client ODCWeb ODC deployment and startupFAQCommand-line windowDDL statement display ODC V4.3.2 ODC V4.3.1 ODC V4.3.0 ODC V4.2.4 ODC V4.2.3 ODC V4.2.2 ODC V4.2.1 ODC V4.2.0 ODC V4.1.3 ODC V4.1.2 ODC V4.1.1 ODC V4.1.0 ODC V4.0.2 ODC V4.0.0ODC V3.4.0ODC V3.3.3 ODC V3.3.2 ODC V3.3.1 ODC V3.3.0 ODC V3.2.3 ODC V3.2.2
OceanBase logo

The Unified Distributed Database for the AI Era.

Follow Us
Products
OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
Resources
DocsBlogLive DemosTraining & Certification
Company
About OceanBaseTrust CenterLegalPartnerContact Us
Follow Us

© OceanBase 2026. All rights reserved

Cloud Service AgreementPrivacy PolicySecurity
Contact Us
Document Feedback
  1. Documentation Center
  2. OceanBase Developer Center
  3. V4.3.1
iconOceanBase Developer Center
V 4.3.1
  • V 4.4.2
  • V 4.4.1
  • V 4.4.0
  • V 4.3.4
  • V 4.3.3
  • V 4.3.2
  • V 4.3.1
  • V 4.3.0
  • V 4.2.4
  • V 4.2.3
  • V 4.2.2
  • V 4.2.1
  • V 4.2.0
  • V 4.1.3 and earlier

Create a data source

Last Updated:2024-11-08 08:55:33  Updated
share
What is on this page
Background information
Prerequisites
Procedure
Create a single data source
Import data sources in batches

folded

share

This topic describes how to create a data source in OceanBase Developer Center (ODC).

Background information

ODC allows you to connect to data sources to edit and manage the database objects and resources of connected data sources. ODC can connect to OceanBase Database in MySQL and Oracle modes on Apsara Stack and Alibaba Cloud, and connect to MySQL, Oracle, Doris, and PostgreSQL databases.

Prerequisites

For information about the functional limitations and version requirements on data sources, see Limitations.

  • You have deployed Web ODC.

  • You have logged on to Web ODC and gone to the data source management page.

  • You have obtained the connection information or connection string of the data source instance. The connection string of a MySQL tenant of OceanBase Database is in the following format:

    mysql -h host name -P port number -u database username@tenant name # cluster name -D default database -p 'database password'

    -hxxx.x.x.x -P8080 -uodc@mysql_tenant#odc_cluster -Dodc -p'******'
    

Procedure

Create a single data source

Create an OceanBase data source

Example: Create an OceanBase data source in MySQL mode named obmysql4.2.0 in ODC, and bind the data source to the odc_4.2.0 project.

Configuration item Example
Project name odc_4.2.0
Data source name obmysql4.2.0
Host IP address xxx.x.x.x
Port 8080
Cluster name odc_cluster
Tenant name mysql_tenant
Database username odc
Database password ******
sys tenant account test
sys tenant password ******
  1. Log on to Web ODC. In the left-side navigation pane of the project collaboration window, choose Data Sources > Create Data Source > OceanBase MySQL.

    ODC supports the following OceanBase Database instance types:

    • OceanBase MySQL or OceanBase Oracle: a database instance that you build in your own environment.

    • OB Cloud MySQL or OB Cloud Oracle: a database instance on Alibaba Cloud.

    • OB Sharding MySQL: a logical database, which supports only the MySQL mode.

  2. In the Create Data Source panel, specify the following information.

    Note

    If you have obtained the connection string of OceanBase Database, you can obtain the following information from the connection string or use the Intelligent Parsing tool provided on the tab to populate the information.

    Parameter Description
    Data Source Type By default, the selected data source type is displayed.
    Intelligent Parsing You can paste the connection string to the field. ODC automatically identifies the string and populates the corresponding fields.
    Endpoint
    • Host IP: the IP address of the server where the target database is located.
    • Port: the port number of the server where the target database is located.
    • Cluster: the name of the cluster where the target database is located. This parameter is not required for logical databases.
    • Tenant: the name of the tenant in which the target database is located. This parameter is not required for logical databases.

    Note

    • You can obtain the host name and port number from the details page of the tenant in which the target database is located, such as a tenant created on Alibaba Cloud or in OceanBase Cloud Platform (OCP).
    • The cluster name is required only when you connect to OceanBase Database by using OceanBase Database Proxy (ODP).
    Database Account
    • Database User Name: the username of an account created in the tenant. In MySQL mode, this account must have the permission to access the default database.
    • Password: the password of the account created in the tenant. You can click Test Connection next to the password field to test whether you can connect to the target database.

    Note

    • An error is returned if the configurations such as the username, password, or network settings are invalid.
    • You can connect only to a database in the current tenant. Otherwise, a test failure error is returned.
    • Before you save the configurations, you can click Test Connection to test the database connection. If the database username and password are correct, the system returns a message indicating that the connection succeeded. In ODC V4.0.0 and later, you can save the connection without setting the database account and password.
    Environment You can select an environment type as needed. Valid values: dev, sit, and prod.
    Project You can choose to bind the created data source to the specified project. After the data source is bound to the project, the databases created in the data source are automatically moved to the project.

    Note

    The system parameter odc.connect.database.sync.block-internal-database specifies whether to automatically synchronize built-in databases to the project. The default value is true, which specifies not to automatically synchronize built-in databases to the bound project. The built-in databases identified by ODC for different data sources are as follows:
    • OceanBase Oracle: SYS
    • OceanBase MySQL: information_schema, mysql, test, and oceanbase
    • MySQL: information_schema, mysql, and test
    Advanced Settings
    • sys Tenant Account: If you select Query Tenant Views with sys Tenant Account, you must specify Account and Password. When the database is a physical database, you can specify an account that has the permission to query the sys tenant views and the password. This field is automatically populated when sys is specified as the tenant in Endpoint.
      • Account: the username of an account that has the permission to query views in the sys tenant.
      • Password: the password of the account.
      After you specify the account username and password, you can click Test Connection next to the password field to verify whether the account information is valid.
    • SSL: Choose whether to enable SSL link encryption to ensure secure data transmission between clients and servers.
      Before you enable SSL in ODC, make sure that SSL is enabled for the OBServer nodes. If you connect to the OBServer nodes by using ODP, make sure that SSL is enabled for ODP. For more information about how to enable SSL for an OBServer node, see Transmission encryption of OBServer nodes and SSL link encryption.
    • Startup Script: You can configure a connection session by using an SQL statement. For example, you can execute the set session ob_query_timeout=60000000 statement to configure a connection session.
    • Driver: You can configure driver attributes to connect to OceanBase Database and implement specified features.

    Note

    • To use the import/export feature in ODC V2.3.0 and later, you must configure the root@sys account in Advanced Settings when you create a connection.
    • When you use the import/export feature to query views in ODC V2.4.1 and later, the root@sys account is not a must. Specifically, if you do not configure the root@sys account, some objects such as stored procedures and functions cannot be exported from ODC. If you configure the root@sys account, you can query views in the sys tenant to obtain the optimal data routing strategy, thereby increasing the export speed.
    • The account username and password of the sys tenant are the account username and password of a user in a cluster tenant. Do not specify the account username in the "@sys#cluster" format. For example, the root account can be used.
    • By default, the REQUIRE NONE option is specified when you create a user. The REQUIRE NONE option specifies that no encryption method is used. In this case, if you select Enable SSL, an SSL connection is created. Otherwise, a regular connection is created.
    • If the REQUIRE SSL option is specified when you create the user, you must select Enable SSL to create an SSL connection. Otherwise, the connection fails.
      If the user is created by specifying the REQUIRE SSL option, you do not need to upload the certificates, but you must select Enable SSL. Otherwise, the connection fails. We recommend that you upload the following certificates for identity verification:
      • CA certificate for the client to verify the identity of the server.
      • Client key and client certificate for the server to verify the identity of the client.
    • If the user is created by specifying the REQUIRE X509 option, you must select Enable SSL and upload the CA certificate, client key, and client certificate. The client and the server verify the identity of each other. If you do not select Enable SSL or upload the CA certificate, you cannot create the connection.
  3. After you specify the preceding information, click OK in the lower-right corner of the panel.

  4. In the dialog box that appears, enter the data source name and click OK. The data source is then saved to the data source list of ODC.

    Note

    • In the Create Data Source panel, click Copy Connection String in the lower-right corner to copy the current connection information as a connection string. This allows you to obtain the connection information with ease.
    • If you do not want to save the current connection configuration, click Cancel. In the dialog box that appears, confirm whether to exit the data source creation page.
  5. After the data source is created, you can view the created data source in the data source list.

Create a MySQL data source

Note

In ODC V4.2.2 and later, you can create a MySQL data source to manage the data in a MySQL database from ODC. For information about the limitations on features of MySQL data sources, see Limitations.

Example: Create a MySQL data source in ODC and bind the data source to the odc_4.2.0 project.

Configuration item Example
Project name odc_4.2.0
Data source name mysql4.2.2
Host IP address xxx.x.x.x
Port 8080
Database username odc
Database password ******
  1. Log on to Web ODC. In the left-side navigation pane of the project collaboration window, choose Data Sources > Create Data Source > MySQL.

  2. In the Create Data Source panel, specify the following information.

    Note

    If you have obtained the connection string of the MySQL database, you can obtain the following information from the connection string or use the Intelligent Parsing tool provided on the tab to populate the information.

    Parameter Description
    Data Source Type By default, the selected data source type is displayed.
    Intelligent Parsing You can paste the connection string to the field. ODC automatically identifies the string and populates the corresponding fields.
    Endpoint
    • Host IP: the IP address of the server where the target database is located.
    • Port: the port number of the server where the target database is located.
    Database Account
    • Database User Name: the username of an account created in the MySQL database.
    • Password: the password of the account created in the MySQL database. You can click Test Connection next to the password field to test whether you can connect to the target database.

    Note

    • An error is returned if the configurations such as the username, password, or network settings are invalid.
    • Before you save the configurations, you can click Test Connection to test the database connection. If the database username and password are correct, the system returns a message indicating that the connection succeeded. In ODC V4.0.0 and later, you can save the connection without setting the database account and password.
    Environment You can select an environment type as needed. Valid values: dev, sit, and prod.
    Project You can choose to bind the created data source to the specified project. After the data source is bound to the project, the databases created in the data source are automatically moved to the project.

    Note

    The system parameter odc.connect.database.sync.block-internal-database specifies whether to automatically synchronize built-in databases to the project. The default value is true, which specifies not to automatically synchronize built-in databases to the bound project. The built-in databases identified by ODC for different data sources are as follows:
    • OceanBase Oracle: SYS
    • OceanBase MySQL: information_schema, mysql, test, and oceanbase
    • MySQL: information_schema, mysql, and test
    Advanced Settings
    • Startup Script: You can configure a connection session by using an SQL statement. For example, you can execute the set session ob_query_timeout=60000000 statement to configure a connection session.
    • Driver: You can configure driver attributes to connect to OceanBase Database and implement specified features.

    Note

    When you create a MySQL data source in ODC V4.2.2, you can specify only the startup script and driver attributes.

  3. After you specify the preceding information, click OK in the lower-right corner of the panel.

  4. In the dialog box that appears, enter the data source name and click OK. The data source is then saved to the data source list of ODC.

    Note

    • In the Create Data Source panel, click Copy Connection String in the lower-right corner to copy the current connection information as a connection string. This allows you to obtain the connection information with ease.
    • If you do not want to save the current connection configuration, click Cancel. In the dialog box that appears, confirm whether to exit the data source creation page.
  5. After the data source is created, you can view the created data source in the data source list.

Create an Oracle data source

Note

In ODC V4.2.4 and later, you can create an Oracle data source to manage the data in an Oracle database from ODC. For information about the limitations on features of Oracle data sources, see Limitations.

Example: Create an Oracle data source in ODC.

Configuration item Example
Data source name oracle4.2.4
Host IP address xxx.x.x.x
Port 8080
Database SID test
Database username odc
Database password ******
  1. Log on to Web ODC. In the left-side navigation pane of the project collaboration window, choose Data Sources > Create Data Source > MySQL.

  2. In the Create Data Source panel, specify the following information.

    Parameter Description
    Data Source Type By default, the selected data source type is displayed.
    Endpoint
    • Host IP/Domain Name: the IP address of the server where the target database is located.
    • Port: the port number of the server where the target database is located.
    • Database: the SID or service name.
    Database Account
    • Role: the role of the database account. Valid values: Default, SYSDBA, and SYSOPER.
    • Database User Name: the username of an account created in the MySQL database.
    • Password: the password of the account created in the MySQL database. You can click Test Connection next to the password field to test whether you can connect to the target database.

    Note

    • An error is returned if the configurations such as the username, password, or network settings are invalid.
    • Before you save the configurations, you can click Test Connection to test the database connection. If the database username and password are correct, the system returns a message indicating that the connection succeeded. In ODC V4.0.0 and later, you can save the connection without setting the database account and password.
    Environment You can select an environment type as needed. Valid values: dev, sit, and prod.
    Project You can choose to bind the created data source to the specified project. After the data source is bound to the project, the databases created in the data source are automatically moved to the project.
    Advanced Settings
    • Startup Script: You can configure a connection session by using an SQL statement. For example, you can execute the set session ob_query_timeout=60000000 statement to configure a connection session.
    • Driver: You can configure driver attributes to connect to OceanBase Database and implement specified features.
  3. After you specify the preceding information, click OK in the lower-right corner of the panel.

  4. In the dialog box that appears, enter the data source name and click OK. The data source is then saved to the data source list of ODC.

Create a PostgreSQL data source

Note

In ODC V4.3.2 and later, you can create a PostgreSQL data source to manage the data in a PostgreSQL database from ODC. For information about the limitations on features of PostgreSQL data sources, see Limitations.

Example: Create a PostgreSQL data source in ODC.

  1. Log on to Web ODC. In the left-side navigation pane of the project collaboration window, choose Data Sources > Create Data Source > MySQL.

  2. In the Create Data Source panel, specify the following information.

    Parameter Description
    Data Source Type By default, the selected data source type is displayed.
    Endpoint
    • Host IP/Domain Name: the IP address of the server where the target database is located.
    • Port: the port number of the server where the target database is located.
    • Database: the name of the PostgreSQL database.
    Database Account
    • Database User Name: the username of an account created in the MySQL database.
    • Password: the password of the account created in the MySQL database. You can click Test Connection next to the password field to test whether you can connect to the target database.

    Note

    • An error is returned if the configurations such as the username, password, or network settings are invalid.
    • Before you save the configurations, you can click Test Connection to test the database connection. If the database username and password are correct, the system returns a message indicating that the connection succeeded. In ODC V4.0.0 and later, you can save the connection without setting the database account and password.
    Environment You can select an environment type as needed. Valid values: dev, sit, and prod.
    Project You can choose to bind the created data source to the specified project. After the data source is bound to the project, the databases created in the data source are automatically moved to the project.
    Advanced Settings
    • Startup Script: You can configure a connection session by using an SQL statement. For example, you can execute the set session ob_query_timeout=60000000 statement to configure a connection session.
    • Driver: You can configure driver attributes to connect to OceanBase Database and implement specified features.
  3. After you specify the preceding information, click OK in the lower-right corner of the panel.

  4. In the dialog box that appears, enter the data source name and click OK. The data source is then saved to the data source list of ODC.

Import data sources in batches

In ODC V4.2.0 and later, you can upload a configuration file to import data sources in batches. To do so, perform the following steps:

  1. On the Data Sources tab, choose Create Data Source > Batch Import.

    1

  2. In the Batch Import panel, click Download Template and specify the information about the data sources to be imported.

    Parameter Description
    Data Source Name Required. The name of the data source. The name cannot contain spaces and must be unique.
    Data Source Type Required. The type of the data source. Valid values: OceanBase Oracle, OceanBase MySQL, OB Cloud Oracle, OB Cloud MySQL, and OB Sharding MySQL.
    Host IP Address Required. The IP address of the server where the target database is located.
    You can obtain the host IP address from the details page of the tenant in which the target database is located, such as a tenant created on Alibaba Cloud or in OCP.
    Port Required. The port number of the server where the target database is located.
    You can obtain the port number from the details page of the tenant in which the target database is located, such as a tenant created on Alibaba Cloud or in OCP.
    Cluster Name Optional. The name of the cluster where the target database is located. This parameter is not required for logical databases.
    Tenant Name Required. The name of the tenant in which the target database is located. This parameter is not required for logical databases.
    The tenant name cannot contain spaces.
    Database User Name Required. The username of an account created in the tenant. In MySQL mode, this account must have the permission to access the default database.
    Database Password The password of the account under the tenant. If the Password parameter is left unspecified, it indicates that the password is an empty string.
    Environment You can select an environment type as needed. Valid values: dev, sit, and prod.
    Sys Tenant Account Optional. The account that has the permission to query views in the sys tenant.
    Sys Tenant Password Optional. The password of the account.
  3. Click the file pool in the Batch Import panel to open the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it.

  4. Click Import to import the data sources in batches. After the import, you can view the information about imported data sources in the data source list.

Previous topic

Use Web ODC
Last

Next topic

Data sources and project collaboration
Next
What is on this page
Background information
Prerequisites
Procedure
Create a single data source
Import data sources in batches