OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Best Practices

All Versions
  • Deploy
    • Configuration guide for read-write splitting in AP scenarios
    • Best practices for read-write splitting
  • Migrate
    • Data transfer solutions in OceanBase Database
    • Overview on data migration
    • Best practices for importing data files to OceanBase Database
    • Best practice for migrating data from other databases to OceanBase Database
    • Massive data migration strategy
    • Best practices for migrating data from MyCat to OceanBase Database
    • Best practices for migrating PostgreSQL to OceanBase MySQL-compatible mode
  • Route
    • ODP routing best practices
  • Table Design
    • Best practices for table design and index optimization
    • Best practices for creating indexes on large tables
    • Best practices for database development
  • Develop
    • Best practices for connecting Java applications to OceanBase Database
    • Best practices for integrating Spark Catalog with OceanBase Database
    • Best practices for achieving optimal performance in batch DML using JDBC and OBServer
    • Best practices for bulk data cleanup in OceanBase Database
    • Best practices for PDML processing in OceanBase Database
    • Best practices for hot tables in OceanBase Database
    • Best practices for auto-increment columns and sequences in OceanBase Database
  • Manage
    • Best practices for resource throttling
    • Best practices for data load balancing
    • Best practices for security certification
    • Best practices for access control
    • Best practices for data encryption
  • Diagnose
    • Best practices for log interpretation in common scenarios
    • Best practices for end-to-end tracing
    • Best practices for using obdiag to collect performance information
    • Best practices for using obdiag to collect diagnostic information of parallel and slow SQL statements
    • Best practices for troubleshooting OceanBase Database performance issues
  • Performance Tuning
    • Best practices for handling slow queries
    • Best practices for collecting statistics to generate an efficient execution plan
    • Best practices for updating hotspot rows
    • Best practices for large object storage performance
    • Best practices for semi-structured storage performance
    • Best practices for OceanBase materialized views
  • Cloud Database
    • Best practices for achieving high availability through cross-cloud active-active deployment
    • High availability through primary and standby databases across clouds
    • High host CPU usage
    • Best practices for read/write splitting in OceanBase Cloud

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Best Practices
  3. master

Best practices for data encryption

Last Updated:2026-10-13 12:45:10

MySQL tenant
Enable TLS data transmission encryption
Enable TDE
Oracle tenant
Enable TLS data transmission encryption
Enable TDE

As data security governance becomes an increasingly important global concern, ensuring the security of databases, foundational software for storing and managing critical data assets, has become a key challenge that requires collaboration between database vendors and customers. OceanBase has always prioritized product security. Over the years, it has actively complied with regulatory requirements, established a comprehensive security management system, and focused on building stable, reliable, secure, and open data infrastructure. Through continuous technological innovation, OceanBase helps customers protect the confidentiality, integrity, and availability of their data, earning its reputation as a trusted provider of foundational software. However, ensuring database security is not just the responsibility of vendors—it also requires close collaboration with customers.

Security is a key factor in evaluating the performance of a database. A database management system must prevent unauthorized access to safeguard the files and data it contains.

This topic provides the best practices for achieving data encryption.

MySQL tenant

Enable TLS data transmission encryption

OceanBase Database supports communication encryption to prevent the communication traffic among nodes from being intercepted or tampered with.

Related operations

  • Self-check

    Log in to OceanBase Command-Line Client (OBClient) and run \s to check whether SSL is enabled based on the SSL field for the OBServer node. If not, Not in use is displayed.

    obclient> \s
    

    The return result is as follows:

    obclient  Ver 2.2.6 Distrib 10.4.18-MariaDB, for Linux (x86_64) using readline 5.1
    
    Connection id:          3221487667
    Current database:       oceanbase
    Current user:           root@100.88.114.135
    SSL:                    Not in use
    Current pager:          stdout
    Using outfile:          ''
    Using delimiter:        ;
    Server version:         OceanBase 4.3.2.1 (r201000012024080617-2ecfa3a5c430a582c4884b287b9234a9a8553bf7) (Built Aug  6 2024 18:01:40)
    Protocol version:       10
    Connection:             xxx.xxx.xxx.xxx TCP/IP
    Server characterset:    utf8mb4
    Db     characterset:    utf8mb4
    Client characterset:    utf8mb4
    Conn.  characterset:    utf8mb4
    TCP port:               2881
    Protocol:               Compressed
    Active                  --------------
    
  • Security hardening

    For more information, see OBServer transmission encryption.

Enable TDE

OceanBase Database allows you to enable transparent data encryption (TDE) at the tablespace level to implement secure data storage.

Related operations

  • Self-check

    For a MySQL tenant, execute the following statement:

    obclient> SELECT table_name,encryptionalg,encrypted FROM oceanbase.V$OB_ENCRYPTED_TABLES;
    
  • Security hardening

    For more information, see Enable transparent data encryption for new tables in MySQL mode.

Oracle tenant

Enable TLS data transmission encryption

OceanBase Database supports communication encryption to prevent the communication traffic among nodes from being intercepted or tampered with.

Related operations

  • Self-check

    Log in to OBClient and run \s to check whether Transport Layer Security (TLS) is enabled based on the SSL field for the OBServer node. If not, Not in use is displayed.

    obclient> \s
    

    The return result is as follows:

    obclient  Ver 2.2.6 Distrib 10.4.18-MariaDB, for Linux (x86_64) using readline 5.1
    
    Connection id:          3221487669
    Current database:       SYS
    Current user:           SYS
    SSL:                    Not in use
    Current pager:          stdout
    Using outfile:          ''
    Using delimiter:        ;
    Server version:         OceanBase 4.3.2.1 (r201000012024080617-2ecfa3a5c430a582c4884b287b9234a9a8553bf7) (Built Aug  6 2024 18:01:40)
    Protocol version:       10
    Connection:             xxx.xxx.xxx.xxx via TCP/IP
    Server characterset:    utf8mb4
    Db     characterset:    utf8mb4
    Client characterset:    utf8mb4
    Conn.  characterset:    utf8mb4
    TCP port:               2881
    Protocol:               Compressed
    Active                  --------------
    
  • Security hardening

    For more information, see OBServer transmission encryption.

Enable TDE

OceanBase Database allows you to enable TDE at the tablespace level to implement secure data storage.

Related operations

  • Self-check

    For an Oracle tenant, execute the following statement:

    obclient> SELECT table_name,encryptionalg,encrypted FROM V$OB_ENCRYPTED_TABLES;
    

    If the value of the ENCRYPTED field is YES, TDE has been enabled.

  • Security hardening

    For more information, see Enable transparent data encryption for new tables in Oracle mode.

Previous topic

Best practices for access control
Last

Next topic

Best practices for log interpretation in common scenarios
Next
on this page
MySQL tenant
Enable TLS data transmission encryption
Enable TDE
Oracle tenant
Enable TLS data transmission encryption
Enable TDE