Version information
Release date: January 19, 2026
Version: V4.1.0
RPM package version: ob-deploy-4.1.0-2
New features
Supports visual upgrades for OceanBase Migration Service (OMS) to improve the migration service update efficiency.
Supports deployment of an AI Stack (including the OceanBase Database Standalone Edition, Model-as-a-Service, and PowerRAG), and provides an optimized infrastructure environment for AI all-in-one machines.
Quickly create standby tenants for an Oracle tenant to improve disaster recovery capabilities.
Add a component node relation visualization topological map for OceanBase Database. This will visually display the cluster architecture.
When you visualize deploy OceanBase Database, you can select the Distributed or Standalone deployment mode for configuration.
A configuration confirmation stage is added during the OCP upgrade and deployment process, reducing the likelihood of configuration errors.
Host Initialization: The host initialization process is optimized to be consistent with the OCP standard and improve deployment consistency.
Enhanced deployment parameter verification: The port range restriction is strengthened. The port range is now limited to 1025 to 65535.
Improved the UX of the Upgrade page in the Visualization page: The UX of the Upgrade page in the Visualization page is improved, and the operation is more intuitive and convenient.
Default path adjustment for slog: The default storage path for slog has been optimized to align with clog's configuration on the same disk, enhancing I/O performance and data consistency.
This module is available in OceanBase Database Community Edition 4.5.x and supports seamless upgrades from earlier versions to the latest Community Edition.
In OceanBase Cloud (OCP) MetaDB, you can use OceanBase Database 4.3.5.3 to use the AI assistant and document search feature in OCP 4.4.1.
Bug fixes
Fix the problem that the tenant log disk size and character set cannot be set in a special interactive mode.
Fixed the issue where OCP deployment fails due to the use of launch_user.
Fixed the issue that the custom obshell port does not take effect when you deploy OCP using the visualization tools.