OBLOADER & OBDUMPER V3.3.2

OBLOADER & OBDUMPER V3.3.2, released in November 2022, eliminates the need for a sys tenant account during export, improves database object schema export in limited mode (--no-sys), and optimizes data export performance.

Version information

• Current version: V3.3.2

• Previous version: V3.3.0

• Release date: November 12, 2022

Supported OceanBase Database versions

The following table lists the OceanBase Database versions supported by OBLOADER & OBDUMPER V3.3.2.

Feature updates

• Eliminated the dependency on the sys tenant account when exporting database object schemas. This feature applies to all OceanBase Database versions.

• Added support for exporting the following database object schemas in limited mode (--no-sys). This feature applies to all OceanBase Database versions:

  • In Oracle compatible mode, you can export TABLE (including table comments), TABLE GROUP, VIEW, TYPE/TYPE BODY, PACKAGE/PACKAGE BODY, TRIGGER, FUNCTION, PROCEDURE, and SYNONYM schemas.

  • In MySQL compatible mode, you can export TABLE (including table comments), TABLE GROUP, VIEW, FUNCTION, and PROCEDURE schemas. For more information, see OBDUMPER command-line options.

• Improved export performance by allowing non-partitioned tables with primary or unique keys to be exported in parallel batches.

Bug fixes

• Fixed the issue where OBLOADER failed to find a file when its path was specified directly for schema import.

• Fixed the issue where OBLOADER returned NULL when the --max-errors and --max-discards options were used together during data import.

• Fixed the issue where OBLOADER displayed an incorrect count after stopping an import because the specified number of errors or discarded rows had been reached.

• Fixed the issue where OBLOADER recorded an incorrect completion status and row count when --max-discards was set to an integer n.

• Fixed the issue where OBLOADER hung during data import.

• Fixed the issue where OBLOADER returned an error when the --skip-header and --cut options were used together.

• Fixed the issue where non-CSV data exported by a custom OBDUMPER query incorrectly included column names.

• Fixed the issue where the --thread option did not take effect during schema export with OBDUMPER.

Known issues

• OBLOADER:

  • When the partition key has a character data type and the character set is utf16 or gb18030, OBLOADER logs a WARN-level message indicating that it cannot calculate the partition information. This warning does not affect data import.

  • When you use a control file to import data, the table name specified by the --table option must be in the same case as the table name in the database. Otherwise, the control file does not take effect.

• OBDUMPER:

  • In limited mode (--no-sys), exported view schemas include schema information.

  • In limited mode (--no-sys), indexes in table schemas cannot be exported from OceanBase Database versions earlier than V2.2.50 in Oracle compatible mode.

  • In limited mode (--no-sys), table group schemas cannot be exported from OceanBase Database versions earlier than V2.2.70.

  • In limited mode (--no-sys), unique indexes on partitioned tables cannot be exported from OceanBase Database V2.2.70 and later.

  • Outside limited mode, OBDUMPER cannot export all table schemas from OceanBase Database versions earlier than V2.2.50 in Oracle compatible mode because partitioned tables without primary keys contain global indexes.

  • Outside limited mode, table group information is missing from table schemas exported from OceanBase Database V3.3.2 in MySQL or Oracle compatible mode.

  • In limited mode (--no-sys), consistent queries against OceanBase Database versions earlier than V2.2.70 do not produce a consistent snapshot (JDBC issue).

  • Outside limited mode, consistent queries against non-partitioned tables without primary keys in OceanBase Database versions earlier than V2.2.70 do not produce a consistent snapshot (JDBC issue).

  • Sequence objects cannot currently be exported from OceanBase Database in MySQL compatible mode.

Considerations

• The CUT format requires each data record to occupy a complete line. When --cut is specified and the field delimiter is a single character, OBDUMPER escapes delimiters, carriage returns, line breaks, and other special characters in the data. For example, if the data is abc|def and the delimiter is |, the exported data is abc\|def.

• The --logical-database option is used to import and export logical databases through ODP (Sharding). However, due to the limitations of ODP (Sharding), the table structure exported by OBDUMPER is a random physical table structure in the sharded database. Therefore, you cannot directly import the table structure to a logical database by using OBLOADER. You must manually modify the table structure.

• Limited mode (--no-sys) applies when the sys tenant password is unavailable in an OceanBase Database environment. Its behavior is equivalent to that of the --public-cloud option in earlier versions. Starting with OBLOADER & OBDUMPER V3.3.0, ApsaraDB for OceanBase and OceanBase Database environments are distinguished: --public-cloud applies only to ApsaraDB for OceanBase, whereas --no-sys applies only to OceanBase Database.