OBLOADER & OBDUMPER V4.2.5

OBLOADER & OBDUMPER V4.2.5 released in August 2023 allows you to import data in the direct load mode and import files containing duplicate data in Oracle compatible mode of OceanBase Database, and provides preprocessing functions.

Version information

• Current version: V4.2.5

• Previous version: V4.2.4

• Release date: August 9, 2023

Supported OceanBase Database versions

The following table lists the OceanBase Database versions supported by OBLOADER & OBDUMPER V4.2.5.

Feature updates

• OBLOADER:

  • The --direct and --rpc-port options are added. You can use these options to specify the RPC port of an OBServer node for direct load. For more information, see Command-line options of OBLOADER.

• When you use OBLOADER to import data in Oracle compatible mode of OceanBase Database, you can specify the --replace-data option to process files that contain duplicate data.

• OBDUMPER:

  • The --enable-hidden-pk option is added. It specifies to use a hidden primary key for a table without a primary key to accelerate export. For more information, see Command-line options of OBDUMPER.

• OBLOADER and OBDUMPER:

  • The ob.sql.mode session variable is added. It allows you to modify the sql_mode variable of a session in MySQL compatible mode of OceanBase Database during import. For more information, see Connection configuration.

  • You can access an Amazon Simple Storage Service (S3) bucket from an endpoint.

  • Preprocessing functions are added, including CHR, NCHR, ASCII, RAWTOHEX, HEXTORAW, and TRUNC. For more information, see Preprocessing functions.

Bug fixes

• Fixed an issue that when you use OBLOADER to import a CSV file, empty strings in enum fields are displayed as NULL values.

• Fixed an issue that when you use OBLOADER to import a DDL definition file, the parsing fails if the default or comment field contains comment characters.

• Fixed an issue that when you use OBLOADER to import a DDL definition file, the import fails if the --exclude-table option is specified.

• Fixed an issue that when you use OBLOADER to import a PL file, multi-line comments that are empty cannot be processed.

• Fixed an issue that when you use OBLOADER to import logs with duplicate primary keys, the imported logs are inaccurate.

• Fixed an issue that when you use OBDUMPER to export a data file in the Parquet format, an error is returned if the path contains Hadoop verification files.

• Fixed an issue that when you use OBDUMPER to export a file, the --max-file-size option cannot take effect globally.

Known issues

• The exported database object definitions may contain the name of the database to which the object belongs.

• OBDUMPER cannot export PL object definitions from OceanBase Database of versions earlier than V2.2.30 in MySQL compatible mode.

• If you do not specify the password of the sys tenant on the command line, OBDUMPER cannot export table group definitions from OceanBase Database of versions earlier than V2.2.70.

• If you do not specify the password of the sys tenant on the command line, OBDUMPER cannot export index definitions from OceanBase Database of versions earlier than V2.2.50 in Oracle compatible mode.

• If you do not specify the password of the sys tenant on the command line, OBDUMPER cannot export partition information of unique indexes from OceanBase Database of versions earlier than V2.2.70 in Oracle compatible mode.

• If you do not specify the password of the sys tenant on the command line, OBDUMPER cannot export unique index definitions of partitioned tables from OceanBase Database V2.2.70 and later versions in Oracle compatible mode.

• When you use OBLOADER to import data, if the specified file format, such as --sql and --csv, does not match the actual file format, an error occurs.

• In MySQL compatible mode of OceanBase Database, when you explicitly specify object names, such as the names of tables and views, in a case-sensitive manner to import or export only objects of the case-sensitive names, objects are imported or exported in a case-insensitive manner.

• If you forcibly terminate the OBLOADER process during direct load, tables may be locked.

Considerations

• In a CUT file, each data record is stored in an entire line. When you specify the --cut option on the OBDUMPER command line, if the exported data contains a single-character field separator, OBDUMPER escapes special characters in the data, such as separators, carriage returns, and line breaks. For example, if the data is abc|def and the separator is |, the exported data is abc\|def.

• When you specify the --cut option on the OBLOADER command line, do not use the --trail-delimiter option if no field separator or separator string exists at the end of the data line in the file. Otherwise, a serious error occurs on OBLOADER.

• If you specify the --logical-database option on the command line, the definition of a random physical database shard is exported and the shard cannot be directly imported into the database. You need to manually convert the exported physical shard to a logical one before you import it to the database for business use.

• When you specify the --partition option on the command line to export data in a partition, you need to specify the name of the subpartition for a composite partitioned table. OBDUMPER cannot export data in a partition of a composite partitioned table. If the specified partition name does not exist, OBDUMPER returns an error.

• If you specify the --add-extra-message option on the command line to export table definitions, OBDUMPER exports the name of the table group to which each table belongs. This option depends on privileges of the sys tenant. If OBDUMPER does not have privileges of the sys tenant, do not specify this option.

• Before you use OBDUMPER & OBLOADER on OceanBase Database V3.2.4 or later, set the system parameter open_cursors to a large value. Otherwise, an error may occur during the import or export. After the data is imported or exported, reset the system parameter to the initial value, for example, ALTER SYSTEM SET open_cursors = 65535;.

• If the schema of a table has been changed in OceanBase Database V4.0.0 or later, you cannot use OBDUMPER to export the baseline data, namely the consistent snapshot data, obtained after the last major compaction. You can manually initiate a major compaction and then re-export the most recent baseline data.

• When you use OBDUMPER of a version earlier than V4.2.0 to export data from OceanBase Database in MySQL compatible mode, OceanBase Connector/J converts the zero values of date and time columns in the database to NULL. If a column has a NOT NULL constraint, an error is reported during the export. OBDUMPER V4.2.0 can export zero values of date and time columns, but cannot identify whether the original data is NULL or zero values during export and forcibly converts the data to zero values by default. In addition, exported zero values of the DATETIME and TIMESTAMP data types may be distorted into approximate non-zero values. If the sql_mode variable in the database is specified with the NO_ZERO_DATE or NO_ZERO_IN_DATE constraint, an error is reported when zero values are imported.

  Take note of this consideration on zero values when you export data of the DATE, DATETIME, TIME, YEAR, or TIMESTAMP type from OceanBase Database in MySQL compatible mode.

• Feature differences in schema export in the MySQL compatible and Oracle compatible modes:

  Compatibility Mode	Password of the sys tenant provided	Password of the sys tenant not provided
  MySQL compatible	Tables, views, table groups, stored procedures, and functions are supported.	The export behavior is basically the same as that when the password of the sys tenant is provided, except for the following known issues: Table group definitions cannot be exported for OceanBase Database of a version earlier than V2.2.70. Partition information of unique indexes cannot be exported for OceanBase Database of a version earlier than V2.2.70. Index definitions cannot be exported for Oracle-compatible tenants of OceanBase Database V2.2.30 or earlier. Definitions of unique indexes on partitioned tables cannot be exported for Oracle-compatible tenants of OceanBase Database of a version ranging from V2.2.70 (included) to V4.0.0.
  Oracle compatible	Tables, views, triggers, synonyms, sequences, stored procedures, functions, packages, table groups, and types are supported.