diff --git a/.aci.yml b/.aci.yml
new file mode 100644
index 00000000..a0ad1525
--- /dev/null
+++ b/.aci.yml
@@ -0,0 +1,36 @@
+
+stages:
+ - build
+
+beforeScript:
+ - |
+ export PATH=$PWD/node_modules/.bin:/root/.cli:$PATH
+ echo $PATH
+ tnpm -v
+
+build:
+ stage: build
+ aciTags: DOCKER
+ agent:
+ docker:
+ image: reg.docker.alibaba-inc.com/odc-front/odc-e2e:node14
+ resourceRequirements:
+ cpu: 4
+ memory: 12
+ ephemeral-storage: 30
+ script:
+ - |
+ export PATH=$PWD/node_modules/.bin:/root/.cli:$PATH
+ node -e "console.log('%j, %j', process.versions, process.execPath)"
+ tnpm i @alipay/ob-yuque2book-front@2 -g
+ ob-md2book -p ./ -n "${ACI_VAR_docName}" -o ./ -r
+ tar -zcvf output.tar.gz output
+ echo 'open doc' > ./index.html
+ publisher:
+ archiveArtifacts:
+ artifacts: 'output.tar.gz, index.html'
+ allowEmptyArchive: true
+ html:
+ index: index.html
+ displayName: '在线预览'
+
\ No newline at end of file
diff --git a/en-US/1.oceanbase-developer-center-documentation-odc-v3-3-0.md b/en-US/1.oceanbase-developer-center-documentation-odc-v3-3-0.md
new file mode 100644
index 00000000..f29a097c
--- /dev/null
+++ b/en-US/1.oceanbase-developer-center-documentation-odc-v3-3-0.md
@@ -0,0 +1,9 @@
+Document Overview
+======================================
+
+OceanBase Developer Center (ODC) is an enterprise-class database development platform tailored for OceanBase. ODC is connected to MySQL and Oracle databases in OceanBase. ODC also provides database developers with various features, such as daily development operations, WebSQL, SQL diagnostics, session management, and data import and export.
+
+
+| Quick Start | Common Operations | FAQ |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [Overview](4.quickstart/1.quickstart-overview.md) [Install ODC](7.client-odc-user-guide/1.client-odc-install-odc.md) [Log on to ODC with an account](6.web-odc-user-guide/1.log-on-to-odc/1.log-on-to-odc-account.md) [Create a private connection](6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md) [Export data](5.tutorials/3.tutorials-export.md) [Import data](5.tutorials/4.tutorials-import.md) [Use the SQL Window](6.web-odc-user-guide/5.web-odc-use-workspace/2.web-odc-sql-window.md) | [Private connection management](6.web-odc-user-guide/3.web-odc-connect-database/2.web-odc-manage-connections.md) [Public resource management](6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/1.web-odc-manage-public-connection.md) [Use the workspace](6.web-odc-user-guide/5.web-odc-use-workspace/1.web-odc-use-workspace-overview.md) [Use tools](6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/1.web-odc-data-export-and-import-overview.md) [Task management](6.web-odc-user-guide/9.web-odc-task-management/1.web-odc-task-management-overview.md) [Session management](6.web-odc-user-guide/10.web-odc-session-management.md) [Database objects management](6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/1.web-odc-database-objects-overview.md) [Use recycle bin](6.web-odc-user-guide/7.web-odc-recycle-bin.md) [View operating record](6.web-odc-user-guide/8.web-odc-view-operation-records.md) | [FAQ](10.faq.md) |
\ No newline at end of file
diff --git a/en-US/10.faq.md b/en-US/10.faq.md
new file mode 100644
index 00000000..2a2b79b5
--- /dev/null
+++ b/en-US/10.faq.md
@@ -0,0 +1,259 @@
+FAQ
+========================
+
+
+
+ODC client installation
+--------------------------------------------
+
+1. Q: What items are pre-checked when I install the ODC client?
+
+ A: The following items are pre-checked:
+
+
+2. Q: How do I view the logs when the installation or startup of the ODC client fails?
+
+ A: You can view the error information in the main.log file. The storage path of the file varies with the OS.
+
+
+3. Q: What do I do when the installation or startup of the ODC client fails and an error message is returned indicating that a port conflict issue has occurred?
+
+ A: You need to check the process that occupies port 8989, kill the process, and then reinstall or restart the ODC client. Dynamic ports are used in ODC V2.3.0 and later to avoid this problem.
+
+ - On macOS, run the following command to check the use status of port 8989:
+
+ ```JavaScript
+ lsof -i tcp:8989
+ ```
+ - On Windows, run the following statement to check the use status of port 8989:
+ ```JavaScript
+ netstat -ano|findstr 8989
+ ```
+
+
+ ODC V3.2.0 allows you to set custom ports.
+
+ - On Mac OS, set environment variables and run the corresponding command to enable the port:
+
+ 
+
+ 
+
+ - On Windows, set the ODC_PORT parameter to enable the specified port:
+
+ 
+
+
+4. Q: What do I do when the installation or startup of the ODC client fails and an error message is returned indicating that the Java version is not supported?
+
+ A: You can run the following command to check the Java runtime environment. We recommend that you install JDK1.8.0_242 or a later version. If you have installed JDK of an earlier version, upgrade JDK, restart the computer, and then reinstall or restart the ODC client.
+
+ ```javascript
+ java -version
+ ```
+
+
+5. Q: What do I do when the installation or startup of the ODC client fails and an error message is returned indicating that the software package is damaged?
+
+ A: You can run the `sudo spctl --master-disable` command and select any source.
+
+ 
+
+
+6. Q: What do I do when the following message appears while I am installing the ODC client on macOS? A: The ODC client cannot be directly installed on Mac OS because it is not downloaded from the App Store. For more information about how to safely open an app that is not downloaded from the Apple Store, see [Safely open apps on your Mac](https://support.apple.com/zh-cn/guide/mac-help/mchleab3a043/mac).
+
+
+
+
+
+
+Launch of Web ODC
+--------------------------------------
+
+1. Q: What do I do when the username (such as admin) conflict occurs during the upgrade of ODC from an earlier version to V3.2.0 or later, and the startup fails?
+
+ A:
+
+ **Example error:**
+
+ 
+
+ **Solution** :
+
+ This example shows how to solve the admin conflict.
+ 1. Open the rename.properties file in the ../odc/static/tmp/ directory, and edit the rename.properties in the following format:
+
+ ```unknow
+ admin=a new username
+ ```
+
+
+
+ 2. Save the change and start ODC again.
+
+
+
+
+
+
+
+
+
+Connection information
+-------------------------------------------
+
+1. Q: What do I do when ODC is disconnected during the execution of an SQL query?
+
+ A:
+
+ The disconnection is caused by a proxy server timeout. You can send an `sql-execute` request in the browser debugging mode and check the response.
+
+ To ensure sufficient proxy server timeout, modify the load balancing configurations. The following example shows how to modify the NGINX configuration:
+
+ a. Add the following proxy configuration.
+
+ ```shell
+ proxy_read_timeout 1800;
+ proxy_send_timeout 1800;
+ proxy_connect_timeout 75;
+ proxy_next_upstream off;
+ ```
+
+
+ > **Note**
+ > We recommend that you set the `proxy_connect_timeout` parameter to a value of no longer than 75 seconds. For more information, see [proxy_connect_timeout](http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_connect_timeout).
+ > If you do not set the `proxy_next_upstream` parameter to off, the NGINX proxy will forward your requests to the next ODC node. In this case, you need to log on to ODC again, and cannot use features related to file upload and download, such as downloading the result set of an asynchronous task.
+
+
+ b. After the modification, restart the NGINX proxy.
+
+
+2. Q: How do I back up the connection information in ODC?
+
+ A:
+
+ * A: If you are using Web ODC, you can directly migrate or back up the MetaDB that you created during ODC deployment.
+ * If you are using the ODC client, you can back up the `odc2.0.mv.db` file in the user directory. When you need to restore the connection, you can copy this file to the original directory.
+
+
+3. Q: What do I do when the execution of an SQL query times out?
+
+ A: When the execution of an SQL query times out, you can manually set the timeout value. In Advanced Configuration on the connection information editing page, you can set **SQL Query Timeout Value** to a larger value. This configuration item is supported in ODC since V2.2.0. If you are using an earlier version, upgrade to ODC V2.2.0 or a later version.
+
+
+4. Q: What do I do when an error is returned indicating that the proxyro user does not exist?
+
+ A: You need to set **Query sys Tenant View** to a user with the permission to query sys tenant views in Advanced Configuration on the connection information editing page. This configuration item is supported in ODC since V2.2.0. If you are using an earlier version, upgrade to ODC V2.2.0 or later.
+
+
+
+
+
+Command-line window
+----------------------------------------
+
+1. Q: After I connect to a database by using the ODC client on Windows, the connection is stuck and then disconnected, as shown in the following figure. How do I solve this problem? A: This problem is caused by the lack of the system library files of msvcp120.dll and msvcr120.dll. Please install the official [Visual Studio patch](https://www.microsoft.com/en-us/download/details.aspx?id=40784).
+
+ > **Note**
+ > You do not need to restart ODC after installing the Visual Studio patch. It is recommended to update ODC to the latest version. The current ODC version has a corresponding DDL file, so you do not need to install the patch separately.
+
+
+
+
+
+Encoding
+-----------------------------
+
+1. Q: What do I do when the result set of a query is full of garbled characters?
+
+ A: This problem is caused by the inconsistency between the encoding format used by the ODC client and that expected by the database. The ODC client allows you to encode data in SQL windows or command-line windows
+
+
+ | Location | Linux | macOS | Windows |
+ |---------------------|-------|-------|---------|
+ | SQL window | UTF8 | UTF8 | UTF8 |
+ | Command-line window | UTF8 | UTF8 | GBK |
+
+
+
+ You can run the following command to query the encoding format expected by the database:
+
+ ```sql
+ show variables like '%character_set_c%';
+ show variables like '%character_set_r%';
+ ```
+
+
+
+ The following table shows the encoding formats.
+
+ 
+
+ You can run the following command to modify the encoding format expected by the database:
+
+ ```sql
+ set names gbk;
+ ```
+
+
+
+
+ | Scenario | Solution |
+ |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | The result set of an SQL statement executed in an SQL window contains garbled Chinese characters. - OS on the server where the ODC client is installed: Mac OS - Character set used by OBServer: GBK | - Symptom Run the following command in the database: ```sql show variables like '%character%'; ``` The following variables are displayed: ```sql character_set_client gbk character_set_connection gbk character_set_filesystem binary character_set_results gbk character_set_system gbk ``` It can be learned that the data is encoded in GBK format and the database expects that the ODC client uses the GBK character set. - Cause The character set the database expects the client to use is GBK. However, the ODC client uses UTF8, which is different from GBK. - Solution Modify the character set expected by the database so that it is compatible with the character set actually used by the ODC client. ```sql set names utf8mb4; ``` After the character set is modified, execute the SQL statement in the current session again and view the result set. The result set contains no garbled Chinese characters. |
+ | The result set of an SQL statement executed in a command-line window contains garbled Chinese characters. - OS on the server where the ODC client is installed: Windows - Character set used by OBServer: UTF8MB4 | - Symptom Run the following command in the database: ```sql show variables like '%character%'; ``` The following variables are displayed: ```sql character_set_client utf8mb4 character_set_connection utf8mb4 character_set_filesystem binary character_set_results utf8mb4 character_set_system utf8mb4 ``` It can be learned that the data is encoded in UTF8MB4 and the database expects that the ODC client uses the UTF8MB4 character set. - Cause The character set the database expects the client to use is UTF8MB4. However, the ODC client uses GBK, which is different from UTF8MB4. - Solution Modify the character set expected by the database so that it is compatible with the character set actually used by the ODC client. ```sql set names gbk; ``` After the character set is modified, execute the SQL statement in the current session again and view the result set. The result set contains no garbled Chinese characters. |
+ | The result set of an SQL statement executed in a command-line window contains garbled Chinese characters. - OS on the server where the ODC client is installed: Windows - Character set used by OBServer: UTF8MB4 | - Symptom Run the following command in the database: ```sql show variables like '%character%'; ``` The following variables are displayed: ```sql character_set_client utf8mb4 character_set_connection utf8mb4 character_set_filesystem binary character_set_results utf8mb4 character_set_system utf8mb4 ``` It can be learned that the data is encoded in UTF8MB4 and the database expects that the ODC client uses the UTF8MB4 character set. - Cause The character set the database expects the client to use is UTF8MB4. However, the ODC client uses GBK, which is different from UTF8MB4. - Solution Modify the character set expected by the database so that it is compatible with the character set actually used by the ODC client. ```sql set names gbk; ``` After the character set is modified, execute the SQL statement in the current session again and view the result set. The result set contains no garbled Chinese characters. |
+ | The result set of an SQL statement executed in a command-line window contains garbled Chinese characters. - OS on the server where the ODC client is installed: Windows - Character set used by OBServer: UTF8MB4 | - Symptom Run the following command in the database: ```sql show variables like '%character%'; ``` The following variables are displayed: ```sql character_set_client utf8mb4 character_set_connection utf8mb4 character_set_filesystem binary character_set_results utf8mb4 character_set_system utf8mb4 ``` It can be learned that the data is encoded in UTF8MB4 and the database expects that the ODC client uses the UTF8MB4 character set. - Cause The character set the database expects the client to use is UTF8MB4. However, the ODC client uses GBK, which is different from UTF8MB4. - Solution Modify the character set expected by the database so that it is compatible with the character set actually used by the ODC client. ```sql set names gbk; ``` After the character set is modified, execute the SQL statement in the current session again and view the result set. The result set contains no garbled Chinese characters. |
+ | A file imported to the database contains garbled Chinese characters. - Encoding standard: GBK - OS on the server where the ODC client is installed: Mac OS - Character set used by OBServer: UTF8MB4 | - Symptom Run the following command in the database: ```sql show variables like '%character%'; ``` The following variables are displayed: ```sql character_set_client utf8mb4 character_set_connection utf8mb4 character_set_filesystem binary character_set_results utf8mb4 character_set_system utf8mb4 ``` It can be learned that the data is encoded in UTF8MB4 and the database expects that the ODC client uses the UTF8MB4 character set. - Cause In this case, the data is written into the database by importing a file, which is independent of the encoding of the ODC client. Instead, the encoding standard of the imported file must be consistent with the character set expected by the database. - Solution Transcode the file from the GBK format to the UTF8 format, and import it again. |
+
+
+
+
+
+
+Data export and import
+-------------------------------------------
+
+1. Q: When the data import or export fails and the task summary information includes the following error information: `javax.crypto.BadPaddingException: Given final block not properly padded`. What do I do?
+
+ A: This exception is caused because the OBProxy password failed to be decrypted. You can solve this problem in the following three ways:
+
+
+
+
+
+
+
+DDL statement display
+------------------------------------------
+
+1. Q: What do I do when the DDL statements are incomplete in the table structure?
+
+ A: The existing DDL statements include those for querying indexes and constraints. You can use the `DBMS_METADATA.get_ddl` function or run the `SHOW CREATE TABLE` command to query the DDL statements.
+
+ Example:
+
+ ```sql
+ -- Sample DDL statement for querying table indexes.
+ SELECT dbms_metadata.get_ddl('INDEX', 'indexname', 'username') from dual;
+ -- Sample DDL statement for querying table comments.
+ SELECT 'comment on table ' || table_name || ' is ' || '''' || comments || ''';'
+ FROM all_tab_comments where owner='USER1' AND table_name='T_1' ;
+ -- Sample DDL statement for querying table comments.
+ comment on table T_1 is 'desc 2';
+
+ -- Sample DDL statement for querying column comments.
+ SELECT 'comment on column ' || table_name || '.' || column_name || ' is ' || '''' || comments || ''';'
+ FROM all_col_comments where owner='USER1' AND table_name='T_1' ;
+ -- Sample DDL statement for querying column comments.
+ comment on column T_1.ID is 'ID 3';
+ ```
+
+
+2. Q: Why are the displayed statements truncated when I check the DDL statements of a view or table on the view or table management page?
+
+ A: This is because that the DDL tab of the database object management page calls the content of the `text` field in the `all_views` table. In versions earlier than OBServer V2.2.70, if the content of the `text` field in the `all_views` table is too long, it will be truncated. This problem has been solved in OBServer V2.2.70 and later versions. You can run the `SHOW CREATE VIEW/TABLE` statement to directly query the complete structure statements of the target view or table.
+
+
+
+
diff --git a/en-US/2.what-s-new/1.product-updates.md b/en-US/2.what-s-new/1.product-updates.md
new file mode 100644
index 00000000..6d32f527
--- /dev/null
+++ b/en-US/2.what-s-new/1.product-updates.md
@@ -0,0 +1,13 @@
+# What's New
+
+OceanBase Developer Center (ODC) V4.0.0 released in October 2022 is adapted to support OceanBase Database V4.0.0, allows you to manage partitions and approve the synchronization of shadow tables, and optimizes features such as connection creation and parameter settings of PL objects.
+
+## Updated modules and features
+
+
+| Feature | Module | Description |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|
+| Partition plan | [Create a partition plan](../6.web-odc-user-guide/6.web-odc-use-tools/3.web-odc-partition-scheme.md) | The partition plan feature supports automatic creation of new partitions and deletion of expired partitions. |
+| Shadow table synchronization | [Create a shadow table synchronization project](../6.web-odc-user-guide/6.web-odc-use-tools/5.web-odc-shadow-table-synchronization.md) | The shadow table synchronization feature supports automatic creation of shadow tables in the same database based on the schema of the source table. |
+| Interactions during connection creation | [Create a private connection (Web ODC)](../6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md) [Create a connection (ODC client)](../7.client-odc-user-guide/3.client-odc-connect-database/1.client-odc-create-connection.md) | You can save a connection without specifying the database account or password. The interactions during the configuration of the sys tenant are optimized. |
+| Parameter settings of PL objects | [Manage functions](../6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/3.web-odc-manage-functions.md) [Manage stored procedures](../6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/3.web-odc-manage-stored-procedures.md) [Manage program packages](../6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/3.web-odc-manage-program-packages.md) | When you debug a PL object, you can set its parameters to DEFAULT, NULL, or a null string. |
\ No newline at end of file
diff --git a/en-US/3.odc-overview/1.what-is-oceanbase-developer-center.md b/en-US/3.odc-overview/1.what-is-oceanbase-developer-center.md
new file mode 100644
index 00000000..47a63fd6
--- /dev/null
+++ b/en-US/3.odc-overview/1.what-is-oceanbase-developer-center.md
@@ -0,0 +1,7 @@
+What is ODC?
+=================================
+
+OceanBase Developer Center (ODC) is an enterprise-class database development platform tailored for OceanBase. ODC is connected to MySQL and Oracle databases in OceanBase. ODC also provides database developers with various features, such as daily development operations, WebSQL, SQL diagnostics, session management, and data import and export.
+
+ODC adopts the mature browser/server architecture, which supports cross-platform capabilities and is lightweight and easy to deploy. ODC also provides a client version to help individual developers get started with OceanBase. It also improves the collaboration efficiency between developers and database administrators (DBAs).
+
diff --git a/en-US/3.odc-overview/2.benefits.md b/en-US/3.odc-overview/2.benefits.md
new file mode 100644
index 00000000..66b60b11
--- /dev/null
+++ b/en-US/3.odc-overview/2.benefits.md
@@ -0,0 +1,100 @@
+Benefits
+=============================
+
+OceanBase Developer Center (ODC) is an enterprise-class development platform for OceanBase Database. In ODC, you can edit and manage database objects and resources.
+
+Database object management
+-----------------------------------
+
+* ODC provides instructions to help you create various database objects. In ODC, you can modify database objects in a visualized manner.
+
+
+
+* In addition, ODC provides the recycle bin feature for you to restore or clear deleted objects.
+
+
+
+
+
+
+Enterprise-class partitioning feature
+----------------------------------------------
+
+* ODC supports all types of partitioning in OceanBase in the MySQL and Oracle modes.
+
+
+
+* ODC also provides user-friendly instructions on the entire partitioning process. This makes the partitioning feature easy to use.
+
+
+
+
+
+
+Web console
+--------------------
+
+* The ODC console supports Data Definition Language (DDL), Data Manipulation Language (DML), and secure data update.
+
+
+
+* The ODC console supports Web SQL to help you use the various OceanBase features for development.
+
+
+
+* The ODC console provides user-friendly features, such as syntax highlighting, formatting, and smart tips, that suit the MySQL and Oracle modes of OceanBase.
+
+
+
+* The ODC console allows you to edit data in a visualized manner, which is similar to data editing in Excel.
+
+
+
+
+
+
+Data import and export
+-------------------------------
+
+* ODC provides data import and export features, which are designed for OceanBase.
+
+
+
+* ODC allows you to import and export files of various formats.
+
+
+
+
+
+
+Database variable editing
+----------------------------------
+
+* ODC allows you to modify session variables and global variables in a visualized manner.
+
+
+
+* ODC makes variables easier to remember.
+
+
+
+* ODC increases the efficiency of customizing variables based on business scenarios.
+
+
+
+
+
+
+Resource performance
+-----------------------------
+
+* ODC allows you to manage and control database sessions in real time. You can also view and terminate sessions.
+
+
+
+* ODC provides the features of SQL execution plan analysis and SQL tuning.
+
+
+
+
+
diff --git a/en-US/3.odc-overview/3.product-architecture.md b/en-US/3.odc-overview/3.product-architecture.md
new file mode 100644
index 00000000..de8a88f7
--- /dev/null
+++ b/en-US/3.odc-overview/3.product-architecture.md
@@ -0,0 +1,65 @@
+Architecture
+=================================
+
+The architecture of OceanBase Developer Center (ODC) consists of three parts:
+
+* **Basic features**
+
+
+
+* **Core features**
+
+
+
+* **Advanced features**
+
+
+
+
+
+
+The following figure shows the architecture of ODC.
+
+
+
+Basic features
+-----------------------
+
+* User Management: This feature provides services such as account creation, system logon, and password modification.
+
+
+
+* Connection Management: This feature allows you to manage connections to OceanBase Database in MySQL and Oracle modes. You can create, save, copy, and delete database connections.
+
+
+
+
+
+
+Core features
+----------------------
+
+* Object Management: This feature allows you to follow the instructions to create database objects, such as tables, views, functions, stored procedures, and sequences. This makes OceanBase Database easier to use. In addition, you can edit the online table data that you are currently viewing.
+
+
+
+* Console: In the console, you can save and edit the content in a SQL window and reuse the scripts that you have saved. You can also format SQL scripts and display structured SQL statements. The SQL editor supports auto-complete when you write SQL statements to save your effort. You can edit and export the result set returned from SQL execution. ODC V2.2.0 and later versions support PL and allow you to format, compile, run, and debug PL objects.
+
+
+
+
+
+
+Advanced features
+--------------------------
+
+* Toolkit: This feature includes session management, recycle bin management, and import and export tools. Session Management: The session management tool enables you to edit database sessions and global properties and terminate specified database sessions. Recycle Bin Management: The recycle bin management tool allows you to empty and restore database objects in the recycle bin. Import and Export: The import and export tools enable you to import or export data of various formats in one or more tables.
+
+
+
+* SQL Diagnostics: This feature allows you to diagnose SQL execution plans and view resource consumption during SQL execution. It can help you locate problems in SQL scripts.
+
+
+
+
+
diff --git a/en-US/3.odc-overview/4.product-features.md b/en-US/3.odc-overview/4.product-features.md
new file mode 100644
index 00000000..f0349d87
--- /dev/null
+++ b/en-US/3.odc-overview/4.product-features.md
@@ -0,0 +1,96 @@
+Features
+=============================
+
+OceanBase Developer Center (ODC) is an enterprise-grade database development platform tailored for OceanBase Database. It supports both MySQL and Oracle modes of OceanBase Database and provides database developers with features such as database development, WebSQL-based workspace, SQL diagnostics, session management, and data import and export.
+
+Manage database connections
+------------------------------------------------
+
+ODC allows you to connect to database instances in MySQL or Oracle mode of OceanBase Database. After you enter the required information on the connection creation page of ODC, you can test the connection and save the connection configuration. ODC allows you to save the connections to multiple databases.
+
+On the homepage of ODC, the Connections section displays the connections that you created and saved. You can open, edit, copy, and delete a saved connection.
+
+
+
+Workspace
+------------------------------
+
+ODC provides a WebSQL-based workspace where you can edit and diagnose SQL and PL/SQL statements.
+
+* In the SQL window of the workspace, you can run and save your SQL scripts.
+
+
+
+* In the anonymous block window, you can edit, run, debug, and save anonymous blocks.
+
+
+
+* The workspace also provides diagnostics information, such as execution details and execution results, in the corresponding tabs.
+
+
+
+* You can also use the Snippets feature to search for and save the frequently used command code.
+
+
+
+
+
+
+Create and manage database objects
+-------------------------------------------------------
+
+Object creation and management is a common task in database development. In ODC, you can create and manage database objects such as tables, views, functions, stored procedures, sequences, triggers, types, and synonyms.
+
+In addition to object creation and management by using SQL statements, ODC provides a concise and clear visualized interface where you can create objects and manage their properties.
+
+
+
+Session management and properties
+------------------------------------------------------
+
+A session is a connection between an application and a database. On the Session Management tab, you can view the details about all sessions of a database.
+
+The Session Properties tab of ODC provides a visualized interface where you can view and modify the session variables and global variables that the current database supports.
+
+
+
+Data import and export
+-------------------------------------------
+
+To make database maintenance easier, ODC supports importing and exporting a single table or multiple tables. You can export files in SQL and CSV formats and import SQL files and ZIP packages of files in SQL or CSV format.
+
+* ODC allows you to select multiple tables to import or export their data at a time.
+
+
+
+* You can also import or export the data of a single table.
+
+
+
+
+
+
+
+
+
+
+Command-line window
+----------------------------------------
+
+The OceanBase client (OBClient) is the recommended command-line client for OceanBase Database.
+
+As a graphical user interface (GUI) development tool for OceanBase Database, ODC integrates OBClient in the form of a command-line window. The command-line window allows you to use command lines to develop and manage database features without downloading and installing OBClient.
+
+You can execute SQL or PL/SQL statements and view the execution results in real time. You can also use the `SOURCE` command to run files uploaded to your servers.
+
+
+
+Data mocking
+---------------------------------
+
+ODC provides the data mocking feature that can generate data based on field types in a table. This can meet your requirement for a large amount of data during database performance tests or feature verification.
+
+ODC generates data based on the field types and rules that you specified in the Mock Data panel.
+
+
+
diff --git a/en-US/3.odc-overview/5.product-limits.md b/en-US/3.odc-overview/5.product-limits.md
new file mode 100644
index 00000000..4b1e5330
--- /dev/null
+++ b/en-US/3.odc-overview/5.product-limits.md
@@ -0,0 +1,148 @@
+Limits
+===========================
+
+This topic describes the limits that you may encounter when you use features of OceanBase Developer Center (ODC) V2.2.0.
+
+Supported database versions
+------------------------------------------------
+
+
+
+| Database | Supported versions |
+|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OceanBase Database versions supported by ODC V3.2.0 |
OceanBase Database V1.4.x
OceanBase Database V2.0.x
OceanBase Database V2.1.x
OceanBase Database V2.2.x
OceanBase Database V3.1.x
OceanBase Database V3.2.x
OceanBase Database CE (PL-related feactures are not supported)
|
+
+
+
+The following table shows the OceanBase Database versions that support PL.
+
+
+| Feature | Supported versions |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Compilation of PL objects (functions, stored procedures, and packages) Debugging of PL objects (functions and stored procedures) Debugging of anonymous blocks | V2.2.7, V3.0.0, and later |
+| Execution of PL objects (functions, stored procedures, and packages) Execution of anonymous blocks | V2.0.x and later |
+
+
+
+Supported browser versions
+-----------------------------------------------
+
+The following table lists browser versions supported by Web ODC.
+
+
+| Browser | Supported versions |
+|--------------------|----------------------------------------------------------------------------------------------|
+| Supported browsers | Chrome 76 and later Firefox 60 and later Edge 79 and later |
+
+
+
+Recommended installation environment
+---------------------------------------------------------
+
+The following table describes the recommended environment for installing the ODC client.
+
+
+| Environment | Requirements |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------|
+| Operating system (OS) | Windows: Win 7/Win10 Mac: 10.13.6 (17G65) |
+| Java environment | JDK 1.8.0_242 or later |
+| Port number | Thanks to the dynamic port detection technology, you do not need to reserve port 8989 for ODC V2.3.0 and later. |
+| CPU | 64-bit x86 processor, dual core or above |
+| Memory | 4 GB or more |
+
+
+
+Account management
+---------------------------------------
+
+To change your account password in ODC, log on to ODC, find your username in the upper-right corner of the top navigation bar.
+
+Click the username and select **Change Password** .
+
+Database connection
+----------------------------------------
+
+* Oracle connections are designed to share one session. Whether you commit or roll back a transaction, or trigger a transaction either by creating, modifying, or deleting a database object, or by executing a DDL statement, the transaction takes effect on all windows.
+
+
+
+* In manual-commit mode, make sure to set `ob_trx_idle_timeout` to a value greater than the timeout value of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of `ob_trx_idle_timeout`, the connection will be terminated. However, if `ob_trx_idle_timeout` is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you need to set this parameter to a proper value.
+
+
+
+
+
+
+Workspace
+------------------------------
+
+* The anonymous block window is available only in Oracle mode.
+
+
+
+* The debugging feature is unavailable when you use OBProxy to connect to an instance. Connect to the target instance directly in ODC.
+
+
+
+* You have installed the debugging packages such as DBMS_DEBUG and DBMS_OUTPUT in the connected database.
+
+
+
+* PL object debugging is supported only when OBServer V2.2.70, V3.0.00, or later is connected. Kernel debugging is supported only in an x86 architecture.
+
+
+
+* In ODC, multiple identical connections share one single session. In ODC V2.3.2 and above, automatic committing is disabled by default for the Oracle mode. You must manually commit transactions. You can modify the value of the autocommit parameter on the **Session Properties** page to change this setting. For more information, see [Session management](../7.client-odc-user-guide/9.client-odc-session-management.md).
+
+
+
+
+
+
+Data import and export
+-------------------------------------------
+
+* OceanBase V2.2.30 and later versions support the following character sets: UTF8, GBK, GB18030, and UTF16. Instances earlier than OceanBase V2.2.30 only support UTF8.
+
+
+
+* In ODC V2.2.0 and later, you can use the import and export feature when the target instance is directly connected to ODC or by using OBProxy.
+
+
+
+* The maximum size of data exported in one batch in Web ODC cannot exceed 2 GB before compression. To export data of a larger size, use the data export tool OBDUMPER.
+
+
+
+* The maximum size of files imported in one batch in Web ODC cannot exceed 2 GB after compression. To import data of a larger size, use the data import tool OBLOADER.
+
+
+
+* ODC allows you to run up to three import or export tasks in parallel. Subsequent tasks will wait in the queue.
+
+
+
+* In ODC V2.4.1 and later, you can use the sys tenant account to accelerate the import and export tasks. To export objects other than tables and views, you must configure the sys tenant account.
+
+
+
+
+
+
+Database objects
+-------------------------------------
+
+* Currently, you cannot modify indexes that are already created in a table.
+
+
+
+* You can only create sequence and package objects in Oracle mode.
+
+
+
+* The sys user has the read permission to view partition information. You need to set the sys user in Advanced Configuration during connection creation.
+
+
+
+
+
diff --git a/en-US/4.quickstart/1.quickstart-overview.md b/en-US/4.quickstart/1.quickstart-overview.md
new file mode 100644
index 00000000..3260efb0
--- /dev/null
+++ b/en-US/4.quickstart/1.quickstart-overview.md
@@ -0,0 +1,23 @@
+Overview
+=============================
+
+OceanBase Developer Center (ODC) is an enterprise-class database development platform tailored for OceanBase Database. This topic describes some basic operations for new users to quickly get started with ODC.
+
+To know how to use ODC, perform the following steps:
+
+1. [Install ODC](../7.client-odc-user-guide/1.client-odc-install-odc.md): You can manage your database from either the web-based ODC console or an ODC client. If you do not use an ODC client, skip the Install ODC topic.
+
+
+
+2. [Log on to ODC](../6.web-odc-user-guide/1.log-on-to-odc/1.log-on-to-odc-account.md): After you register an ODC account, enter the username and password to log on to ODC.
+
+
+
+3. [Create a connection](../6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md): After you log on to ODC, you need to create a connection for the target instance to access the management page of the target database instance.
+
+
+
+
+
+
+After you finish the preceding steps, you can proceed to the development and management of your OceanBase Database instance in ODC. For more information about how to use ODC, see the User Guide of the corresponding version.
diff --git a/en-US/4.quickstart/2.quickstart-install-odc.md b/en-US/4.quickstart/2.quickstart-install-odc.md
new file mode 100644
index 00000000..b868f3c9
--- /dev/null
+++ b/en-US/4.quickstart/2.quickstart-install-odc.md
@@ -0,0 +1,49 @@
+Install ODC
+================================
+
+To manage your database, you can either access the web-based OceanBase Developer Center (ODC) console from OceanBase, or download the ODC client. Unlike the web-based ODC console that provides a logon portal, the ODC client uses a default user account for user identification. You just need to install the client and [create a connection](/zh-CN/6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md) to connect to your database.
+
+Recommended installation environment
+---------------------------------------------
+
+
+
+| Item | Requirement |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------|
+| Operating system (OS) | Windows: Windows 7 or Windows 10 Mac: 10.13.6 (17G65) |
+| Java environment | JDK 1.8.0_242 and later. |
+| Port number | Thanks to the dynamic port detection technology, you do not need to reserve port 8989 for ODC V2.3.0 and later. |
+| CPU | X86-64 processor with 2 or more cores. |
+| Memory | 4GB or above. |
+
+
+
+Procedure
+------------------
+
+1. Download [ODC Client](https://help.aliyun.com/document_detail/212816.html).
+
+
+
+2. Double-click the installation file you downloaded to start the installation.
+
+
+
+3. The setup wizard prompts you to select an installation directory.
+
+
+
+4. When you run the client after installation, it checks the environment. If the environment does not meet the requirements, the client displays an error message, indicating that you can either continue using the application, or end the process to fix the problem of the environment. If ODC passes the environment check and operates normally, you can create a connection.
+
+
+
+
+
+ > **Notice**
+ >
JRE installation packages for Mac and 64-bit Windows are included in the installation package of ODC V3.2.0. You can install it as needed.
+ >
For more information about installation or startup failures, see [Installation of the ODC client](https://icms.alibaba-inc.com/content/oceanbase-developer-center/odc?l=1&m=71006&n=3113505) in FAQ.
+
+
+
+
+
diff --git a/en-US/4.quickstart/3.quickstart-log-on-to-odc.md b/en-US/4.quickstart/3.quickstart-log-on-to-odc.md
new file mode 100644
index 00000000..f3f243c6
--- /dev/null
+++ b/en-US/4.quickstart/3.quickstart-log-on-to-odc.md
@@ -0,0 +1,16 @@
+Log on to ODC with an account
+==================================================
+
+During logon to OceanBase Developer Center (ODC), a user is identified by a logon account. The account is needed for subsequent operations such as configuring database connections and saving SQL scripts in the workspace.
+
+Go to the logon page of ODC, as shown in the following figure. Enter the registered account and password on the logon page and click **Log On** to go to the ODC homepage.
+
+
+
+The Connections page automatically appears. The current account is displayed in the upper-right corner of the top navigation bar. You can click the account name and select **Log Off** from the drop-down list to return to the logon page. Then, you can log on to ODC with another account.
+
+> **Note**
+> * After ODC is deployed, you can use the IP address and port number, for example, http://IP:PORT or http://DOMAIN:PORT, of the host (where the NGINX proxy resides) to access Web ODC in a browser.
+> * The default username and password can be obtained from the administrator.
+> * For the administrator, the default username is admin, and the default password is aaAA 11__.
+> * When you upgrade ODC to V3.2.0 or later and encounter user conflicts, you need to manually modify the original username. For more information, see FAQs  Web ODC startup.
\ No newline at end of file
diff --git a/en-US/4.quickstart/4.quickstart-create-a-personal-connection.md b/en-US/4.quickstart/4.quickstart-create-a-personal-connection.md
new file mode 100644
index 00000000..ba770d17
--- /dev/null
+++ b/en-US/4.quickstart/4.quickstart-create-a-personal-connection.md
@@ -0,0 +1,71 @@
+Create a private connection
+================================================
+
+
+
+
+
+Overview
+-----------------------------
+
+After you log on to the homepage of OceanBase Developer Center (ODC), you can click **Create Connection** in the upper-right corner of the **Private Connection** tab to create a private connection.
+
+After you create the connection, you can view the saved database connection in the connection list on the ODC homepage.
+
+> **Notice**
+>
In ODC V2.3.0 and later, the root@sys user permissions are required to query views when you use the import and export features. Therefore, to use the import and export features, you need to set the root@sys user in the Advanced Configuration section during connection creation.
+>
In ODC since V2.4.1, the dependency of the import and export feature on the root@sys user is removed when you query views.
+>
However, the root@sys user permissions are still required to view the partition information. Therefore, you must set the root@sys user in the Advanced Configuration section during connection creation.
+>
The Oracle connection mode is designed to share sessions. In this mode, when you actively commit or roll back a transaction, or trigger a transaction commit or rollback by creating, modifying, or deleting a database object or by executing a DDL statement, the transaction commit or rollback takes effect in all windows. When you enter a connection in Oracle mode for the first time, a reminder is displayed.
+>
In manual-commit mode, make sure to set the `ob_trx_idle_timeout` parameter to a value greater than or equal to the timeout value of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of the `ob_trx_idle_timeout` parameter, the connection is terminated. However, if the `ob_trx_idle_timeout` parameter is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you must set this parameter to a proper value.
+
+
+
+
+
+
+Procedure
+------------------------------
+
+Perform the following steps to create a connection:
+
+
+
+1. Log on to ODC and click **Create Connection** in the upper-right corner of the **Private Connection** tab.
+
+
+
+2. In the Create Connection panel, specify the fields described in the following table. If you have an OceanBase connection string, which follows the mysql -h **host name** -P **port number** -u **database username@tenant name** # **cluster name** -D **default database** -p ' **database password** ' format, you can obtain the information from the string. You can also paste the string in the field of Intelligent Parsing on the panel to automatically populate the corresponding fields.
+
+
+
+
+ | Field | Description |
+ |-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Database Type | Select **Physical Database** or **Logical Database** . * Physical Database: regular databases. * Logical Database: ODP (Sharding). |
+ | Region | Select **Independent Deployment/Apsara Stack** if your database instance is deployed in your own environment, or select **Public Cloud** if your database instance is deployed on Alibaba Cloud. |
+ | Intelligent Parsing | You can paste a connection string to the field. ODC automatically identifies the string and fills in the corresponding fields on the page. |
+ | Connection Mode | Select **MySQL** or **Oracle** . Logical databases support only the MySQL mode. |
+ | 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 name** : the name of the cluster where the target database is located. This parameter is not required for logical databases. * **Rent name** : 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). |
+ | Database Account | * Database Username: an account under the tenant. In MySQL mode, this account must have access to the default database. * Database Password: the password of the account under the tenant. You can click **Test Connection** next to the password field to check the connection to the target database. * Save Database Password * If you disable this option, the database password for the connection is not saved. Each time you use or test the connection, you must enter the database password in the password dialog box. * If you enable this option, the database password for the connection is saved. You do not need to enter the database password each time you use the connection. **Note** * An error will be returned if the configurations such as the username, password, and network settings are invalid. * You can only connect to a database in the current tenant. Otherwise, a test failure error will be returned. |
+ | Default Database/schema | When you connect to a database in a MySQL tenant, you must specify the default database for the connection. You do not need to specify this field when you connect to a database in an Oracle tenant. **Note** If you leave this parameter unspecified, the information_schema database is connected by default. However, if the connection to the information_schema database fails, you need to specify a database that the current user has access permissions. |
+ | SQL Query Timeout Value | You can specify a timeout value for SQL queries. A query whose execution time exceeds the timeout value is automatically terminated. The default timeout value is 60 seconds. |
+ | Query sys Tenant View | When Database Type is set to Physical Database, you can specify an account that has the privilege to query the SYS tenant view, and the password. This field is automatically populated when SYS is specified as the tenant in **Endpoint** . * **Account** : an account having the privilege to check the views under the SYS tenant. * **Password** : the password of the account. After you specify the account and password, click **Test Connection** next to the password field to verify whether the account information is valid. **Note** * In ODC V2.3.0 and later versions, to use the import and export features, you need to configure the root@sys account in the Advanced Configuration section during connection creation. * In ODC V2.4.1 and later versions, the dependency of the import and export features on the root@sys user is removed when you query views. If the root@sys account is not configured, some ODC objects such as stored procedures and functions do not support the export feature. If the root@sys account is configured, you can access the views under the SYS tenant to obtain the optimal data routing strategy, which can increase the export speed. |
+
+
+
+3. Click **Save** to save the current configuration in the ODC connection list. Next time you log on to ODC, you can directly select the connection from the list. The connection configuration does not necessarily need to pass the connection test when you save the configuration.
+
+
+
+4. Click **Copy Connection String** in the lower part of the panel to copy the connection information being edited on the current panel as a connection string if necessary. This allows you to obtain the connection information with ease.
+
+
+
+5. Click **Cancel** if you do not need to save the current connection configuration. Then, a confirmation dialog box appears.
+
+
+
+
+
+
diff --git a/en-US/5.tutorials/1.tips-on-the-sql-console.md b/en-US/5.tutorials/1.tips-on-the-sql-console.md
new file mode 100644
index 00000000..d8f522b1
--- /dev/null
+++ b/en-US/5.tutorials/1.tips-on-the-sql-console.md
@@ -0,0 +1,109 @@
+Tips on the SQL Console
+============================================
+
+This topic describes some tips on the SQL console in OceanBase Developer Center (ODC) for you to carry out development work more efficiently on ODC.
+
+Background information
+-------------------------------
+
+ODC provides a web SQL-based SQL console as a work area where you can edit and diagnose SQL statements. In the SQL window, you can run and save perform operations such as running and saving SQL and PL scripts. The SQL window also provides diagnostic information such as execution details and execution results in the corresponding tabs. The editing area of the SQL window provides rich features, for example, highlighting of keywords in different colors, auto-complete, and formatting, to improve the SQL statement editing efficiency. Under the editing area, you can find the Execution Record tab and the Results tab. The Execution Record tab displays the execution details of each statement in the current connection. The Results tab displays the result of the current execution.
+
+This topic describes some additional tips that can facilitate your development and management work in the SQL console.
+
+Switch the transaction commit mode
+-------------------------------------------
+
+In ODC V2.3.2 and later versions, auto-commit is turned off by default in Oracle mode, so you need to manually commit transactions. In MySQL mode, auto-commit is turned on by default. In manual-commit mode, make sure to set `ob_trx_idle_timeout` to a value greater than the timeout duration of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of `ob_trx_idle_timeout`, the connection will be terminated.
+
+You can switch the transaction commit mode in ODC.
+
+1. Click the name of the target connection to go to the connection management page, click the **Session** button in the navigation bar, and select **Session Properties** from the drop-down list.
+
+
+
+2. On the **Session Properties** page, select the `autocommit` variable in the variable list, and click the Edit button in the toolbar to go to the variable editing page.
+
+
+
+3. On the editing page, set **Value** to **ON** to turn on auto-commit or **OFF** to turn off auto-commit.
+
+
+
+
+
+
+View the execution plan
+--------------------------------
+
+1. After you finish editing the required statements in the SQL window and before you execute the script, you can select a statement and click the **Plan** button in the toolbar. A panel appears, displaying an execution plan for the selected statement or the statement on which the pointer is located. This execution plan is estimated by the system before execution and is the result of the `EXPLAIN PLAN` operation. Therefore, the execution data displayed may differ from the actual execution data. You can use this feature to evaluate SQL statements.
+
+
+
+2. After a statement that you wrote in the editing area is executed, you can click the **Plan** button in the toolbar of the result set to view the actual resource consumption and execution plan of the statement. This allows you to evaluate the performance of the statement.
+
+
+
+
+
+
+Save an SQL script
+---------------------------
+
+1. Edit your SQL script in the editing area of the SQL window.
+
+
+
+2. Click the **Save SQL** button in the toolbar of the SQL window, specify a name for the script in the dialog box that appears, and then click **OK** to save the script.
+
+
+
+3. Click the **Workspace** button in the navigation bar in the upper part of the page, and place the pointer on **Stored Scripts** on the drop-down list that appears, to view all the scripts that you saved on the cascading menu.
+
+
+
+4. On the cascading menu, the **Edit** and **Delete** buttons are provided after each script name. Click **Edit** . A dialog box appears and displays the script name and content. You can modify the script and click **OK** to save the modification.
+
+
+
+5. After you click a script name on the cascading menu, an SQL window appears and displays the script content. You can continue to edit the script and run the script in the SQL window.
+
+
+
+
+
+
+Set the delimiter
+--------------------------
+
+ODC supports PL and allows you to edit PL statements in an SQL window starting from V2.2.0. You must set a delimiter before you edit PL statements.
+
+1. Click the **Settings** button in the toolbar of the SQL window.
+
+
+
+2. Select the sign that you want to use as the delimiter in the **Delimiter** box in the drop-down list. Five types of delimiters are supported: semi-colons ( **;** ), slashes ( **/** ), double slashes ( **//** ), dollar signs ( **$** ), and double dollar signs ( **$$** ).
+
+
+
+3. You can start to write PL statements after you set the delimiter. After you write a PL statement, end it with the selected delimiter.
+
+
+
+
+
+
+In ODC V2.4.1 and later, you can use the `DELIMITER` statement to define the delimiter. In **Settings** , the **Delimiter** field displays the delimiter that you specified.
+
+Limit the number of lines in the query result
+------------------------------------------------------
+
+1. Click the **Settings** button in the toolbar of the SQL window.
+
+
+
+2. Specify **Query Result Limit** to set the maximum number of lines returned in the query result set. The default value is 1000 rows.
+
+
+
+
+
diff --git a/en-US/5.tutorials/2.create-a-conection.md b/en-US/5.tutorials/2.create-a-conection.md
new file mode 100644
index 00000000..73db4e6f
--- /dev/null
+++ b/en-US/5.tutorials/2.create-a-conection.md
@@ -0,0 +1,127 @@
+Create a connection
+========================================
+
+This topic describes how to create a database connection in OceanBase Developer Center (ODC).
+
+Background
+-------------------
+
+As an enterprise-level database development platform tailored for OceanBase Database, ODC can connect to your OceanBase Database, and allow you to edit and manage the database objects and resources. After you install client ODC or deploy web ODC, you must create database connections. ODC can connect to OceanBase Database in MySQL and Oracle modes on Apsara Stack and Alibaba Cloud.
+
+Prerequisites
+----------------------
+
+* Client ODC has been installed or web ODC has been deployed. For the deployment of web ODC, contact your technical support personnel. For the installation of client ODC, see [Install ODC](https://www.oceanbase.com/docs/oceanbase-developer-center/odc/V3.1.1/install-odc-1).
+
+
+
+* If you are using web ODC, you have logged to ODC and entered the connection management page. For more information, see [Log on to the database](t1909443.md#task397).
+
+
+
+* The connection information or connection string of the target instance has been obtained. The connection string of the example connection in this topic is as follows:
+
+ ```unknow
+ -h100.0.0.0 -P8080 -uodc@oracle_tenant#odc_cluster -Dodc -p'Password01'
+ ```
+
+
+
+
+
+
+Procedure
+------------------
+
+1. On the **Connections** tab of the ODC homepage, click **Create Connection** go to the Create Connection panel.
+
+
+
+2. Specify **Region** for the connection. The region is where the connected instance is located. The following options are available:
+
+ * **Public Cloud** : the database instance deployed on Alibaba Cloud.
+
+ * **Independent Deployment/Apsara Stack** : the database instance in your own environment. In this example, select Apsara Stack.
+
+
+
+
+3. Specify **Connection Mode** .
+
+ OceanBase Database supports instances in MySQL and Oracle modes. In this example, Oracle is selected because the sample instance in this topic is in Oracle mode.
+
+
+4. Specify **Connection Name** .
+
+ The connection name uniquely identifies the connection. You need to specify a unique connection name. The sample connection is named Connection_Tutorial.
+
+
+5. Use intelligent DNS resolution.
+
+ If you have the connection string of the connected instance, you can paste the connection string to the Intelligent DNS Resolution field. After you click **Intelligent DNS Resolution** , ODC automatically resolves the string and specifies the parameters such as **Endpoint** , **Default Database** , **Database Username** , and **Database Password** . If you do not have the connection string, you can skip this step and start from Step 6 to manually enter the preceding information.
+
+
+6. Specify **Endpoint** .
+
+ The endpoint contains the following information:
+ * **Host Name** : the IP address of the server where the target instance is located. If your instance is located on Alibaba Cloud, you can get the host name from the tenant information page of the Alibaba Cloud Management Console. The IP address of the sample instance is 100.0.0.0.
+
+
+
+ * **Port** : the port number of the server where the target instance is located. If your instance is on Alibaba Cloud, you can get the port number from the tenant information page of the Alibaba Cloud Management Console. The port number of the sample instance is 8080.
+
+
+
+ * **Cluster** : the name of the cluster where the target instance is located. In this example, the cluster name is odc_cluster.
+
+
+
+ * **Tenant** : the name of the tenant to which the target instance belongs. The tenant name of the sample instance is oracle_tenant.
+
+
+
+
+
+
+7. Specify **Default Database** .
+
+ When you connect ODC to a database in a MySQL tenant, you can choose to specify a default database for the connection. This parameter does not need to be specified when you connect ODC to a database in an Oracle tenant. This parameter is optional. If you do not set this parameter, the default database instance information_schema is used.
+
+
+8. Specify **Database Username** .
+
+ The database username is the name of a user created in a tenant. In Oracle mode, the username is the same as the schema name. In MySQL mode, the corresponding user of the username must access to the default database. The database username of the sample instance is odc.
+
+
+9. Specify **Database Password** .
+
+ Specify the password corresponding to the database username specified in Step 8. The database password of the sample instance is Password01.
+
+
+10. Click **Test Connection** .
+
+ After you specify **Database Password** , you can click **Test Connection** to check whether ODC is connected to the target instance based on the preceding connection information. The connection status does not affect the saving of the connection information.
+
+
+11. Specify whether to disable **Save Database Password** .
+
+ If you disable this option, the database password for the connection is not saved. Each time you use or test a connection, you must enter the database password in the password dialog box to use the connection. If you enable this option, the database password for the connection is saved. You do not need to enter the database password each time you use the connection.
+
+
+12. Specify **SQL Query Timeout Value** in **Advanced Configuration** .
+
+ ODC allows you to specify a custom SQL query timeout value, which is 60s by default. When the execution time of a query reaches the specified value, the query automatically terminates. In ODC V2.3.2 and later, transactions need to be manually committed. In earlier versions, transactions are automatically committed. In manual commit mode, the value of the `ob_trx_idle_timeout` variable cannot be less than the SQL query timeout value. If two SQL queries in one transaction are executed at an interval exceeding the value of `ob_trx_idle_timeout`, the connection will be terminated. However, if `ob_trx_idle_timeout` is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you need to set this parameter to a proper value.
+
+
+13. Specify **Query SYS Tenant View** in **Advanced Configuration** .
+
+ You can specify the account that have the permission to query views of the sys tenant and the corresponding password. In ODC V2.3.0 and later versions, to use the import and export features and check the partition information, you need to configure the root@sys account, that is, the root account under the sys tenant, by using this option. By default, the password for the root@sys account of the sample instance is null, so you only need to set **Account** to root. After you specify Account, you can click **Test Connection** to test whether you can use the root@sys account to access the current database.
+
+
+14. Click **Save** to save the connection information.
+
+ After you configure all the preceding connection information, click **Save** in the lower-right corner to save the settings in the current **Create Connection** page. Then, the information appears on the **Connections** tab of the ODC homepage. You can directly find the target connection on the **Connections** tab and click the name of the connection to enter the connected instance in the future.
+
+
+
+
diff --git a/en-US/5.tutorials/3.tutorials-export.md b/en-US/5.tutorials/3.tutorials-export.md
new file mode 100644
index 00000000..011f62da
--- /dev/null
+++ b/en-US/5.tutorials/3.tutorials-export.md
@@ -0,0 +1,137 @@
+Export data
+================================
+
+This topic describes how to export data in batches in OceanBase Developer Center (ODC).
+
+Background information
+-------------------------------------------
+
+ODC provides the batch import and export features and the table import and export features, to facilitate database data maintenance for database developers. The import and export features allow you to import data or schema to or export them from database objects. ODC supports the CSV format and SQL format for data export, and supports ZIP files, SQL files, and CSV files for data import. SQL files can be imported in batches, and CSV files are supported in single table import.
+
+After you create an import or export task, you can go to the Tasks page to download the exported file and view the task details and logs.
+
+This topic takes batch export as an example to describe how to export data in ODC.
+
+Prerequisites
+----------------------------------
+
+* The character set is supported. OceanBase Database V2.2.30 and later versions support the following character sets: UTF-8, GBK, GB18030, and UTF-16. OceanBase Database of a version earlier than V2.2.30 supports only UTF-8. Exported files of ODC are encoded by using UTF-8, which cannot be changed.
+
+
+
+* The connection method is supported. In ODC V2.2.1 and earlier versions, to use the import and export features, you must connect ODC to the target instance through OBProxy. If you directly connect ODC to the target instance, the import and export features are unavailable.
+
+
+
+* The root@sys account has been configured. In ODC V2.4.1 and later versions, you can optionally configure a sys tenant account to accelerate the execution of export and import tasks. If you are exporting objects other than tables and views, the sys tenant account must be configured.
+
+
+
+
+
+
+Procedure
+------------------------------
+
+1. Go to the **Export Settings** panel.
+
+ After you enter the connection, click **Tool** in the navigation bar on the top of the page, and click **Export** in the drop-down list. Then, the **Export Settings** panel appears on the right.
+
+
+2. Specify **Task Name** .
+
+ The Export Settings panel displays the default task name automatically generated by ODC in the format of connection name_mode name_date. You can change it to a custom task name.
+
+
+3. Specify **Export Content** .
+
+ ODC supports three export modes: **Export Schema and Data** , **Export Data Only** , and **Export Schema Only** .
+
+ Export Schema Only exports the definition statements of the target object and generates an SQL file suffixed with .sql. Export Data Only exports the actual data stored in the object. The file format of exported data varies depending on the value of **Export Format** . In this example, the Export Content is **Export Schema and Data** .
+
+
+4. Specify **Data Format** .
+
+ ODC supports exporting data to the **CSV Format** or **SQL Format** . If the **Export Content** is **Export Schema Only** , you do not need to specify the data format. For more information about formats, see [Export and import formats](../7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md). In this example, the Data Format is **CSV Format** .
+
+
+5. Specify **Encoding Standard** .
+
+ ODC supports the following encoding standards: **ASCII** , **ISO-8859-1** , **GB2312** , **GBK** , **GB1803** **0** , **Unicode (UTF-8)** , **Unicode (UTF-16)** , **Unicode (UTF-32)** , and **BIG5** . You need to select an encoding standard from the **Encoding Standard** drop-down list.
+
+
+6. Specify **Export Objects** .
+
+ In the **Export Objects** table, select the objects you want to export. The table displays information on the **Object Name** and **Object Type** . You can filter objects by **Object Type** or search for target objects in the search box. You can select a batch of or all objects in the table. You can also filter objects by object type. The maximum size of data exported in one batch in ODC cannot exceed 250 MB before compression. Therefore, if the size of the data in the selected objects exceeds 250 MB, the data in the generated data file will be incomplete.
+
+
+7. Specify **Export Data Settings** .
+
+ If the **Export Content** is Export Schema Only, you do not need to configure data export settings. The following options are included:
+ * **Use Global Snapshot** : If you select this option, ODC exports the data in the latest global snapshot of the specified table to ensure global data consistency.
+
+
+
+ * **Batch Commit Quantity** : You can click **Advanced Settings** next to **Export Data Settings** to specify this option. If the **Data Format** is SQL format, you can specify this option to add a `COMMIT` command to the exported file after a certain number of rows is exported.
+
+
+
+ * **Skipped Data Types** : You can click **Advanced Settings** next to **Export Data Settings** to specify this option. This option decides the data types to be skipped when exporting data. The data types that can be skipped are different in MySQL and Oracle modes. You can select multiple data types.
+
+
+
+
+
+
+8. Specify information for the CSV format.
+
+ If you select the CSV format for **Data Format** in Step 4, you need to specify the information for the CSV format. Click **Advanced Settings** next to **Export Data Settings** to specify the following information:
+ * **Include Column Header** : This option is selected by default. It determines whether to include column headers when the export format is CSV format.
+
+
+
+ * **Convert Empty String to Null Value** : This option is selected by default. It specifies whether to convert empty strings in the table to `NULL` values when the export format is CSV format.
+
+
+
+ * **Field Delimiter** : This option specifies the delimiter between fields. The following delimiter characters are supported: commas ( **,** ), Semicolons ( **;** ), and colons ( **:** ). You can also specify another deliminter that is one character long.
+
+
+
+ * **Text Identifier** : This option specifies the identifier for text content. Single quotation marks ( **'** ) and double quotation marks ( **"** ) are supported.
+
+
+
+ * **Line Break Character** : The option specifies the line break character. The following characters are supported: **\\n** , **\\r** , and **\\r\\n** .
+
+
+
+
+
+
+9. Specify **Export Schema Settings** .
+
+ This option specifies whether to **Add DROP Statement** . If you select this option, a `DROP` statement is added before the corresponding `CREATE` statement for the object.
+
+
+10. Configure **Sys Tenant Account** .
+
+ You can specify whether to **use the sys tenant account to accelerate data export** . If you select this option, you need to enter the sys account and password in **Account** and **Password** fields that appear. After you specify this option, data export will be performed with the permissions of the sys tenant, which accelerates the execution of the export task. If you are exporting objects other than tables and views, the sys tenant account must be configured.
+ **Notice**
+
+
+
+ OceanBase Database of a version earlier than V2.2.30 supports only UTF-8.
+
+ In ODC V2.2.1 and earlier versions, to use the import and export features, you must connect ODC to the target instance through OBProxy. If you directly connect ODC to the target instance, the import and export features are unavailable.
+
+ In ODC V2.4.1 and later versions, you can optionally configure a sys tenant account to accelerate the execution of export and import tasks. If you are exporting objects other than tables and views, the sys tenant account must be configured.
+
+
+11. Generate an export task.
+
+ After you select all the objects that you want to export, you can click **Export** in the lower-right corner of the panel to generate an export task. After the task is generated, the Tasks page automatically appears, where you can view the running status of the export task. After the task is completed, you can download the exported data file and view the task details and logs.
+
+
+
+
diff --git a/en-US/5.tutorials/4.tutorials-import.md b/en-US/5.tutorials/4.tutorials-import.md
new file mode 100644
index 00000000..3719d829
--- /dev/null
+++ b/en-US/5.tutorials/4.tutorials-import.md
@@ -0,0 +1,112 @@
+Import data
+================================
+
+This topic describes how to import data in batches in OceanBase Developer Center (ODC).
+
+Background information
+-------------------------------------------
+
+ODC provides the database import and export features and the single table import and export features to facilitate database data maintenance for database developers. The database import and export features allow you to import data to or export data or schemas from selected objects in the database in batches. The single table import and export features allow you to import data to or export data from the target table. ODC supports exporting data in CSV and SQL formats and importing ZIP, SQL (batch import), and CSV (single table import) files.
+
+After you create an import or export task, you can go to the Task Center to download the exported files and view the task details and logs.
+
+This topic takes batch import as an example to describe how to import data in ODC.
+
+Prerequisites
+----------------------------------
+
+* The character set is supported. OceanBase Database V2.2.30 and later versions support the following character sets: UTF8, GBK, GB18030, and UTF16. OceanBase Database of a version earlier than V2.2.30 supports only UTF8. Exported files of ODC are encoded by using UTF-8, which cannot be changed.
+
+
+
+* The connection method is supported. In ODC V2.2.1 and earlier versions, to use the import and export features, you must connect ODC to the target instance through OBProxy. If you directly connect ODC to the target instance, the import and export features are unavailable.
+
+
+
+* The root@sys account has been configured. In ODC V2.4.1 and later, you can use the sys tenant account to accelerate the import and export tasks. To export objects other than tables and views, you must configure the sys tenant account.
+
+
+
+
+
+
+Procedure
+------------------------------
+
+1. Go to the **Batch Import** panel.
+
+ After you enter the connection, click **Tool** in the navigation bar in the upper part of the page, and then click **Import** in the drop-down list. The **Batch Import** panel appears on the right.
+
+
+2. Specify **Task Name** .
+
+ The Batch Import panel displays the default task name automatically generated by ODC in the format of connection name_mode name_date. You can change it to a custom task name.
+
+
+3. Specify **Import** **Format** .
+
+ ODC supports importing ZIP, SQL (batch import), and CSV (single table import) files. The SQL and CSV format are specific to the import and export tools of OceanBase Database. For more information about formats, see [Export and import formats](../7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md). In this topic, **ZIP Files** are used as an example.
+
+
+4. Upload the file to be imported.
+
+ Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it. The format of the uploaded file must be the same as that of the value you specified for Import Format. To upload a file in the ZIP file format, you must first package it into a .zip file. SQL files to be uploaded can be suffixed with .sql. The format of the uploaded file must be the same as that of the value you specified for **Import Format** in Step 3.
+
+
+5. Specify **Encoding Standard** .
+
+ ODC supports the following encoding formats: **ASCII** , **ISO-8859-1** , **GB2312** , **GBK** , **GB1803** **0** , **Unicode (UTF-8)** , **Unicode (UTF-16)** , **Unicode (UTF-32)** and **BIG5** . You need to select the encoding standard from the drop-down list of **Encoding Standard** .
+
+
+6. Specify **Import Content** .
+
+ ODC supports three import modes: **Import Schema and Data** , **Import Data Only** , and **Import Schema Only** **.**
+
+ You must specify this item when you select ZIP for **Import Format** . Import Schema Only runs the object definition statement in the imported file. After the file is imported, a new object will be created in the database. Import Data Only imports the data in the data file into the specified object. In this topic, the **Import Schema and Data** mode is used as an example.
+
+
+7. Specify **Data Format** .
+
+ You must specify this item when you select ZIP for **Import Format** . ODC only support importing data in **CSV format** and **SQL format** . For more information about formats, see [Export and import formats](../7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md). This topic uses the **CSV format** as an example.
+
+
+8. Specify **Import Data Settings** .
+
+ If you specify ZIP files for **Import Format** and Import Schema Only for **Import Content** , this step is not required. You need to specify the following fields:
+ * **Clear Data Before Import** : If you select this option, the original data in the destination object is cleared during data import.
+
+
+
+ * **Batch Commit Quantity** : You can click **Advanced Settings** next to **Import Data Settings** to specify this field. When you specify this field, you specify the number of rows to be committed during the data import from the source files to the database. When this number is reached, a `COMMIT` command is executed.
+
+
+
+ * **Skipped Data Types** : You can click **Advanced Settings** next to **Import Data Settings** to specify this field. Here, you can specify the data types that you want to skip when you import the data. The data types that can be skipped are different in MySQL and Oracle modes. You can select multiple data types.
+
+
+
+
+
+
+9. Specify **Import Schema Settings** .
+
+ You cannot specify this field if you select Import Data Only for **Import Content** . This field involves operations on schemas that already exist. If you select **Skip** , the system skips the schema definition statement in the file to be imported and directly imports the data. The original data in the object is retained. If you select **Replace** , the system executes the schema definition statement in the file to be imported to recreate an object and replace the original one. Data in the original object is cleared.
+
+
+10. Specify **Task Error Handling Method** .
+
+ ODC supports two error handling methods: **Abort Task** and **Ignore Error and Continue** . You need to specify the handling method in **Task Error Handling Method** .
+
+
+11. Specify **Sys Tenant Account** .
+
+ Select whether to **use the sys tenant account to accelerate data import** . If you select this option, you need to enter the sys account and the password in the **Account** and **Password** fields. Then, you can use privileges of this account to import data, which accelerates the import task.
+
+
+12. Create the import task.
+
+ Click **Import** in the lower-right corner of the panel to generate the import task. After the task is generated, the Task Center page appears, where you can view the task status. After the task is completed, you can view the task details and logs.
+
+
+
+
diff --git a/en-US/5.tutorials/5.tutorials-debug.md b/en-US/5.tutorials/5.tutorials-debug.md
new file mode 100644
index 00000000..1669f973
--- /dev/null
+++ b/en-US/5.tutorials/5.tutorials-debug.md
@@ -0,0 +1,151 @@
+Debug a stored procedure
+=============================================
+
+This topic describes how to debug a stored procedure in OceanBase Developer Center (ODC).
+
+Background
+-------------------
+
+PL program development is important daily work for database service developers. Like the support module for SQL statements, the PL debugging module is also of great significance. Therefore, developers require a PL development area and a debugging feature during programming.
+
+ODC V2.2.0 and later support the creation, compilation, running, and debugging of PL objects and anonymous blocks. In the editing area of the anonymous block window, you can compile PL/SQL statements, and edit and debug the created PL objects. ODC provides features such as Batch Execute, Step Over, Step Into, Step Out, Abort Debugging, Debug Again, and Exit Debugging for debugging PL objects. ODC also displays debugging information in tabs such as **Parameters** , **Stacks and Variables** , **DBMS Output** , **Breakpoints** , and **Debugging Logs** .
+
+Prerequisites
+----------------------
+
+* The database is OceanBase Database V2.2.73 or later in Oracle mode.
+
+
+
+* ODC V3.2.2 or earlier does not support the debugging feature when you connect ODC to the target instance by using OBProxy. To use the debugging feature, directly connect ODC to the target instance.
+
+
+
+* ODC V3.2.2 and later support PL/SQL debugging when you connect to OBServer by using OBProxy.
+
+
+
+* You have installed the debugging packages such as DBMS_DEBUG and DBMS_OUTPUT in the connected database.
+
+
+
+* You have created a sample stored procedure named procedure_test by using the following sample script:
+
+ ```javascript
+ CREATE OR REPLACE PROCEDURE procedure_test
+ (
+ A IN NUMBER,
+ B IN NUMBER,
+ C OUT NUMBER
+ ) IS
+ BEGIN
+ C:= A + B;
+ dbms_output.put_line ( C / 2 ) ;
+ END procedure_test;
+ ```
+
+
+
+
+
+
+Procedure
+------------------
+
+The result of procedure_test is the value obtained by dividing the value of output parameter C by 2. The value of parameter C is equal to the sum of values of parameter A and parameter B. Therefore, you cannot directly learn the value of parameter C from the output result of the program. You can view and verify the actual value of parameter C during program running by debugging procedure_test.
+
+1. Enter the debugging mode.
+
+ After you enter the connection, find the target stored procedure procedure_test in the stored procedure list in the left-side navigation pane. Then, right-click procedure_test and click **Debug** in the shortcut menu to start debugging. You can also click **Edit** in the shortcut menu to go to the object editing page, and then click the debug icon  in the toolbar to start debugging.
+
+
+2. Set parameters.
+
+ procedure_test has three parameters: input parameters A and B, and output parameter C.
+ 1. If the input parameters already exist, you need to set the values of the input parameters first before debugging. When you start the debugging, ODC will first display the **Set Parameters** page for you to set values of the input parameters. In this example, the value of parameter A is set to 2 and the value of parameter B is set to 4.
+
+
+
+ 2. After you set the values, click **OK** .
+
+ 
+
+
+
+
+
+3. Go to the debugging page.
+
+ The debugging page appears after you set the parameters.
+
+ The **Parameters** tab below the editing area of the debugging page displays the definition information of all the parameters configured for the program. The definition information includes the parameter name, mode, and type. The values of the parameters may change accordingly in the debugging process.
+
+ ODC provides the following buttons in the toolbar of the debugging page:
+ * **Batch Execute** : Click this button to execute the statements till the next breakpoint or the end if no breakpoint exists.
+
+
+
+ * **Step Over** : Click this button to step over a given line without stepping into any subprogram.
+
+
+
+ * **Step Into** : Click this button to step into the called subprogram if the current line calls a defined stored procedure or function.
+
+
+
+ * **Step Out** : For a subprogram, you can click this button to return to the next line of the upper-layer call position. For the main program, this button achieves the same effect as **Auto Debugging** .
+
+
+
+ * **Abort Debugging** : Click this button to execute the stored procedure till the end and skip breakpoints.
+
+
+
+
+
+
+4. Set breakpoints.
+
+ A breakpoint allows the program to stop at the specified position during execution, to facilitate program analysis. You can set a breakpoint in ODC by clicking a line number in the editing area:
+ 1. In the sample program, click the line number of the `dbms_output.put_line ( C / 2 );` statement in the ninth line to set a breakpoint.
+
+
+
+ 2. The **Breakpoints** tab below the editing area displays information such as the PL/SQL **Object Name** and **Line Number** of all breakpoints set in the program. You are also allowed to **Cancel** and **View** breakpoints.
+
+ > **Note**
+ > The kernel does not support setting breakpoints in comment lines or keywords such as BEGIN and END.
+
+
+
+
+
+5. Start the debugging.
+
+ After you set the breakpoints, click the batch execute iconin the toolbar to start the debugging. The debugging will stop at the breakpoints. You can also click the step over iconto execute the program statements step by step. One step is executed when you click this icon once.
+
+
+6. View the debugging information.
+
+ The program now stops at the ninth line. You can view the variables on the current stack and their values on the **Stacks and Variables** tab below the editing area. The program stops at the ninth line because of the breakpoint. So, on the **Stacks and Variables** tab, you can find that the value of variable C is 6. You can also view the records and error logs of actions such as starting debugging, aborting debugging, adding breakpoints, and canceling breakpoints on the **Debugging Logs** tab.
+
+
+7. Abort the debugging.
+
+ Click the abort debugging iconin the toolbar. The program will continue to run till the end and skip subsequent breakpoints.
+
+ The program contains the PL/SQL output statement `dbms_output.put_line`. Therefore, when the program ends, the **DBMS Output** tab below the editing area displays the value obtained by dividing the value of parameter C by 2. The value now displayed on the tab is 3, indicating that no error has occurred during the running of the program.
+
+
+8. Debug again.
+
+ After the program running ends, you can click **Debug Again** in the toolbar to debug the current object again. The information and breakpoints of the previous debugging will be cleared. You can reset parameters and start a new round of debugging.
+
+
+9. Exit the debugging.
+
+ After you finish the program analysis based on the debugging, you can click **Exit Debugging** in the toolbar to exit the debugging page.
+
+
+
+
diff --git a/en-US/5.tutorials/6.tutorials-view-sql-performance.md b/en-US/5.tutorials/6.tutorials-view-sql-performance.md
new file mode 100644
index 00000000..c6c314d2
--- /dev/null
+++ b/en-US/5.tutorials/6.tutorials-view-sql-performance.md
@@ -0,0 +1,118 @@
+View the performance of an SQL statement
+=============================================================
+
+This topic describes how to view the performance of an SQL statement in OceanBase Developer Center (ODC).
+
+Background information
+-------------------------------
+
+SQL is a database language that provides multiple features such as data manipulation and data definition. Most database developers manage and develop database content by using SQL statements. Therefore, the performance of SQL statements affects the performance of the database. SQL provides the `EXPLAIN` command, which allows you to view the specific steps for executing an SQL statement in the database. You can judge and improve the performance of the SQL statement based on the execution steps.
+
+As a powerful enterprise-level database development platform, ODC provides a graphical user interface (GUI) for you to view the execution plans of SQL statements. ODC allows you to directly and conveniently view the execution status and analyze the performance of SQL statements.
+
+Prerequisites
+----------------------
+
+A sample table named "employees" has been created by running the following statement:
+
+```javascript
+CREATE TABLE employees(
+ emp_id INTEGER,
+ emp_name VARCHAR(20),
+ manager_id INTEGER
+);
+
+INSERT INTO employees VALUES ( 1, 'Anna', 6 ) ;
+INSERT INTO employees VALUES ( 2, 'Brain', 4 ) ;
+INSERT INTO employees VALUES ( 3, 'Candy', 4 ) ;
+INSERT INTO employees VALUES ( 4, 'David', 5 ) ;
+INSERT INTO employees VALUES ( 5, 'Eva', NULL) ;
+INSERT INTO employees VALUES ( 6, 'Frank', 5 ) ;
+INSERT INTO employees VALUES ( 7, 'Gary', 6 ) ;
+```
+
+
+
+Procedure
+------------------
+
+1. After you enter the connection, enter the following `SELECT` statement in the editing area of the SQL window to view the data in the table named "employees":
+
+ ```javascript
+ SELECT * FROM employees;
+ ```
+
+
+
+
+
+
+
+
+2. Click **Plan** in the toolbar in the editing area.
+
+ Before you run the statements, you can click **Plan** to view the estimated execution plan of the SQL statement selected or where the cursor is located in the current editing area. The estimated execution plan is actually the result of the `EXPLAIN PLAN` operation. The estimated plan may be slightly different from the actual plan, but you can assess the SQL statement in advance.
+
+
+3. In the **Plan Details** panel, view the estimated execution plan before you execute the SQL statement.
+
+ The **Planned Statistics Collection** tab in the **Plan Details** panel displays following information:
+
+
+
+
+
+
+
+4. Run the statement.
+
+ Click **Run** in the toolbar to execute the `SELECT` statement.
+
+
+5. Click **Plan** in the toolbar of the result set, to view the execution plan after the statement is executed.
+
+ The **Execution Details** page displays the actual execution plan.
+
+
+6. View the basic information of the statement in the **Basic Info** section of the **Execution Details** panel.
+
+ The **Basic Info** section displays the following information:
+
+
+
+
+
+
+
+7. View the time statistics of the statement in the **Time Spent** section of the **Execution Details** panel.
+
+ The **Time Spent** section displays the following information and corresponding proportions in a bar graph.
+
+
+
+
+
+
+
+8. View the I/O statistics of the statement in the **I/O Statistics** section of the **Execution Details** panel.
+
+ The **I/O Statistics** section displays the following information:
+
+
+
+
+
+
+
+9. View the plan statistics of the statement on the **Planned Statistics Collection** tab of the **Execution Details** panel.
+
+ The **Planned Statistics Collection** tab displays the actual execution plan in a structured manner. This tab is the same as the **Plan Details** tab in structure. For more information about this tab, see the information about the **Planned Statistics Collection** tab in Step 3.
+
+
+10. View the outline of the statement in the **Outline** section of the **Execution Details** panel.
+
+ The **Outline** section displays the corresponding content of `OUTLINE DATA` in results returned by the execution plan. The content in this section is a set of hints generated by the optimizer for the purpose of fully reproduce a plan.
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/1.log-on-to-odc/1.log-on-to-odc-account.md b/en-US/6.web-odc-user-guide/1.log-on-to-odc/1.log-on-to-odc-account.md
new file mode 100644
index 00000000..4f6f178e
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/1.log-on-to-odc/1.log-on-to-odc-account.md
@@ -0,0 +1,15 @@
+Log on to ODC with an account
+==================================================
+
+During logon to OceanBase Developer Center (ODC), a user is identified by a logon account. The account is needed for subsequent operations such as configuring database connections and saving SQL scripts in the workspace.
+
+Go to the logon page of ODC, as shown in the following figure. Enter the registered account, password and verification code on the logon page and click **Log On** to go to the ODC homepage.
+
+
+
+The Connections page automatically appears. The current account is displayed in the upper-right corner of the top navigation bar. You can click the account name and select **Log Off** from the drop-down list to return to the logon page. Then, you can log on to ODC with another account.
+
+> **Note**
+> * After ODC is deployed, you can use the IP address and port number, for example, http://IP:PORT or http://DOMAIN:PORT, of the host (where the NGINX proxy resides) to access Web ODC in a browser.
+> * The default username and password can be obtained from the administrator.
+> * When you upgrade ODC to V3.2.0 or later and encounter user conflicts, you need to manually modify the original username. For more information, see FAQs > Web ODC startup.
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/1.log-on-to-odc/2.change-password.md b/en-US/6.web-odc-user-guide/1.log-on-to-odc/2.change-password.md
new file mode 100644
index 00000000..9404c4bc
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/1.log-on-to-odc/2.change-password.md
@@ -0,0 +1,38 @@
+Change the password
+========================================
+
+
+
+1. After you log on to Web OceanBase Developer Center (ODC), you can click the username in the upper-right corner of the top navigation bar, and select **Change Password** from the drop-down list.
+
+ 
+
+
+2. In the **Change Password** dialog box, specify the following fields to change the password:
+
+ 
+
+ * **Original Password** : enter the original password of the account.
+
+
+
+ * **New Password** : set a new password.
+
+
+
+ * **Confirm Password** : enter the new password again for verification.
+
+
+
+
+
+
+3. After you specify the preceding fields, click **OK** .
+
+
+
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/10.web-odc-session-management.md b/en-US/6.web-odc-user-guide/10.web-odc-session-management.md
new file mode 100644
index 00000000..f0fc9858
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/10.web-odc-session-management.md
@@ -0,0 +1,80 @@
+Session management
+=======================================
+
+A session is a connection between an application and a database. On the Session Management page of OceanBase Developer Center (ODC), you can view the details of all the sessions connected to the current database. The Session Properties page of ODC provides a graphical interface where you can view and modify the session variables and global variables that the current database supports.
+
+After you enter a database connection in ODC, click **Session** in the top navigation bar and then choose **Session properties** or **Session management** to go to the corresponding page.
+
+
+
+Session properties
+---------------------------------------
+
+
+
+The session properties are database variables. OceanBase Database provides two types of variables: session variables and global variables.
+
+* **Session variables** : When a client connects to a database, the database copies the global variables to automatically generate session variables. The modification of session variables takes effect on the current session only.
+
+* **Global variables** : Global variables are shared by all the instances of a database. These variables are shared among different users. When you modify a global variable, the database saves the modification, which remains valid after you disconnect from and reconnects to the database.
+
+
+
+> **Note**
+>
The current ODC version does not allow you to edit global variables. You can modify session variables.
+>
In ODC, multiple identical connections share one single session. In ODC V2.3.2 and later versions, auto-commit is turned off by default in Oracle mode, so you need to manually commit transactions. You can modify the value of the autocommit parameter to change this setting.
+>
In manual-commit mode, make sure to set ob_trx_idle_timeout to a value greater than the timeout duration of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of ob_trx_idle_timeout, the connection will be terminated. However, if ob_trx_idle_timeout is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you need to set this parameter to a proper value.
+
+
+
+
+
+
+ODC provides a graphical interface where you can view and modify the variables that the current database supports. Take note of the following items related to the modification of variables:
+
+* In the current ODC version, session variables have two modes: display mode and edit mode. To modify a variable, select the variable and click Edit in the toolbar to go to the editing page. After you edit a variable, click **OK** . On the SQL Confirmation page, click **Execute** to apply the modification.
+
+
+
+* To modify a variable of a character or numeric type, you can directly enter the new value on the Edit page.
+
+
+
+* To modify a variable of an enumeration type, ODC lists the values that the variable supports in the edit box. This allows you to modify the variable in a graphical interface without having to memorize its name or value, which saves your memorization efforts and increases the efficiency of variable modification.
+
+
+
+
+
+
+Session management
+---------------------------------------
+
+A session is a connection between an application and a database. On the Session Management page, you can view all the sessions connected to the current database and the following session information:
+
+
+| Information | Description |
+|--------------------|---------------------------------------------------------------------|
+| Session ID | The ID that uniquely identifies the current session. |
+| User | The username used to log on to the database in the current session. |
+| Source | The address from which the session is initiated. |
+| Database name | The name of the database accessed in the session. |
+| Status | The state of the session. Valid values: **SLEEP** and **ACTIVE** . |
+| Command | The type of the command being executed in the session. |
+| Execution Time (s) | The time in seconds spent on executing the current SQL query. |
+| SQL | The actual SQL query being executed in the session. |
+| OBProxy | The address of the proxy used for the session. |
+
+
+
+
+The Session Management page provides the following buttons in the navigation bar for you to manage sessions.
+
+* **Refresh** : Click this button to refresh the session list.
+
+* **Close Session** : Click this button to terminate the current session.
+
+* **Close current query processes of the session** : Click this button to terminate the ongoing SQL execution processes in the session.
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/1.web-odc-table-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/1.web-odc-table-objects-overview.md
new file mode 100644
index 00000000..c1a26429
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/1.web-odc-table-objects-overview.md
@@ -0,0 +1,262 @@
+# Create a table
+
+
+
+## Overview
+
+A table is a data structure in a database and stores data in rows and columns.
+
+
+
+As shown in the preceding figure, you can create a table in the following seven steps:
+
+1. Specify the basic information.
+
+
+
+2. Set columns.
+
+
+
+3. Set partitioning rules.
+
+
+
+4. Set the index.
+
+
+
+5. Set constraints.
+
+
+
+6. Verify the SQL statement.
+
+
+
+7. Complete the table creation.
+
+
+
+
+
+
+## Procedure
+
+In the following example, a table named employee is created in the OceanBase Developer Center (ODC) console. The table contains the emp_no, birthdate, name, and gender columns. Procedure:
+
+### Step 1: Specify the basic information.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables. To create a table, click **+** in the upper-right corner of the table list or click **Create** in the top navigation bar.
+
+In the **Basic Info** section, specify **Table Name** and **Description**.
+
+> **Note**
+> In MySQL mode, you also need to specify **Default Character Set** and **Default Sorting Rule**.
+
+
+
+### Step 2: Set columns.
+
+The following figure and table show the information that you need to specify when you add a column.
+
+
+
+
+| Field | Description |
+|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Field Name | The name of the column. |
+| Data Type | The data type of the column. For more information about data types, see [OceanBase Database Developer Guide](https://www.oceanbase.com/docs/enterprise/oceanbase-database/oceanbase-database/V3.2.3/data-type-overview). |
+| Non-empty | Specifies whether the value of the column must be specified. |
+| Auto-increment | Specifies whether to set the column to an auto-increment column. This parameter is valid in MySQL mode. |
+| Default Value | The default value of the column. |
+| Comment | The additional information about the column. |
+
+
+
+The column setting section also provides three buttons.
+
+
+| Button | Description |
+|-----|-------------------------|
+| Create | Click this button to add a field. |
+| Edit | Click this button to edit the selected field. You can also directly double-click a cell to edit it. |
+| Delete | Click this button to delete the selected field. |
+
+
+
+### Step 3: Set partitioning rules.
+
+
+
+You can partition a table that contains a large amount of data. After a table is partitioned, data in the table is stored in multiple tablespaces. The database does not scan the entire table for a query.
+
+* In MySQL mode, OceanBase Database supports the following six partitioning methods: **Key**, **Hash**, **Range**, **Range Columns**, **List**, and **List Columns**.
+
+* In Oracle mode, OceanBase Database supports the following three partitioning methods: **List**, **Range**, and **Hash**.
+
+ The definition of a partition in MySQL mode is different from that in Oracle mode. So, the values of the following fields vary in different modes. You need to specify the following fields based on the selected partitioning method.
+
+
+| Field | Description |
+|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Partitioning Method | Specifies the partitioning method. The partitioning methods supported in MySQL mode are different from those in Oracle mode. - Range partitioning: Multiple rows with column values in an ordered, continuous and non-overlapping range are assigned to a partition. - List partitioning: A table is partitioned based on the enumeration values. - Hash partitioning: A table is partitioned based on a given number of partitions. For a table that stores data without a clear pattern or range, you can use hash partitioning to randomly distribute values of the partition column to different partitions based on the HASH algorithm. - Key partitioning: This partitioning method is similar to HASH partitioning. The difference is that key partitioning only supports computation of one or more columns, and the MySQL server provides its own hash function. At least one INT type column is required for Key partitioning. For more information about partitioning, see [Overview](https://www.oceanbase.com/docs/enterprise/oceanbase-database-cn/V3.2.3/10000000000357153). |
+| Field | The column that is used as the partition key. |
+| Expression | Partitions are divided based on the return value of the expression. The partition expression is not supported in Oracle mode. |
+| Partition | Based on the value specified for **Partitioning Method**, you may need to specify information such as **Partition Name**, **Partition Quantity**, **Upper limit of the range**, and **Enumeration Value**. **Note** - When selecting the **Range** partitioning method, if the table contains a large amount of data, you can fill in MAXVALUE in **Upper limit of the range**, which means that the upper limit of the range is not set. - You can add multiple partitions and drag the partitions to adjust their order. |
+
+
+
+
+
+### Step 4: Set the index.
+
+If a table contains a large amount of data, you can use indexes to accelerate data queries. An index is a data structure that pre-sorts the values of one or more columns in a table. By using indexes, you can directly locate records that meet the conditions.
+
+The following figure and table show the information that you need to specify when you set the index.
+
+
+
+
+| Field | Description |
+|------|-------------------------------------------------------------|
+| Index Name | The name of the index. |
+| Index Range | The default value is **GLOBAL**, which indicates a global index. You can set this parameter to **LOCAL** only for tables with partitions. The value LOCAL indicates a local index. |
+| Index Type | Only BTree is supported. |
+| Optional Field | The columns to be indexed. Pay attention to the order of the indexed columns. |
+| Unique | Specifies whether the index is unique. In other words, the index is used to ensure that the constraint is unique. |
+
+
+
+The index setting section also provides three buttons.
+
+
+| Button | Description |
+|-----|-------------------------|
+| Create | Click this button to add an index. |
+| Edit | Click this button to edit the selected index. You can also directly double-click a cell to edit it. |
+| Delete | Click this button to delete the selected index. |
+
+
+
+### Step 5: Set constraints.
+
+Constraints are used to specify data rules for a table. A data operation that violates the constraints will be terminated.
+
+
+
+ODC supports the following four table constraints:
+
+* **Primary Key Constraint**: defines a primary key to uniquely identify each row of data in the table. A primary key constraint can be a field or a group of fields. You can set only one primary key constraint for a table, and you cannot edit the constraint after it is configured.
+
+* **Unique Constraint**: ensures that the data in a field or a group of fields is unique in the table. You can set multiple unique constraints in one table.
+
+* **Foreign Key Constraint**: associates one or more columns in two tables. A foreign key constraint is used to maintain the data consistency and integrity between associated tables. After you complete the setting of foreign key constraints, you cannot create new constraints or edit existing constraints.
+
+* **Check Constraint**: checks the data in the database based on the configured check rules when you edit the data. Data modification is allowed only after the check is passed. OceanBase Database supports **Check Constraint** only in Oracle mode.
+
+
+OceanBase Database supports different constraints in MySQL and Oracle modes, and different constraints require different information. Therefore, you need to specify the required information based on the constraint you selected and the requirements on the page.
+
+| Field | Description |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Constraint Name | The name of the constraint. |
+| Column Information | The field or a group of fields specified as the constraint. |
+| Trigger State |Specifies whether to enable the created constraint. In some cases, you may need to temporarily disable the constraints. For example, when you import a large amount of data, you can disable constraints to improve the import efficiency. This field is valid only in Oracle mode.|
+| Deferrable|Supports three types of delay status. Valid values: Verify Now , Non-deferrable , and Delayed Verification. This field is valid only in Oracle mode.|
+| Associated Schema | The schema where the associated table is located when **Foreign Key Constraint** is used. The associated table is the parent table. This field is valid only in Oracle mode. |
+| Associated Database | The database where the associated table is located when **Foreign Key Constraint** is used. The associated table is the parent table. This field is valid only in MySQL mode. |
+| Associated Table | The associated table when **Foreign Key Constraint** is used. The associated table is the parent table. |
+| Associated Field | The associated field when **Foreign Key Constraint** is used. The associated field is in the parent table. |
+| Delete | Specifies the action to be performed on the current table when the data in the associated table is deleted. The current table is the child table, and the associated table is the parent table. The following four types of action are supported: **CASCADE**, **NO ACTION**, **RESTRICT**, and **SET NULL**. OceanBase Database supports different foreign key actions in MySQL and Oracle modes. - In MySQL mode, OceanBase Database allows you to specify CASCADE, NO ACTION, RESTRICT, and SET NULL. - In Oracle mode, OceanBase Database allows you to specify CASCADE, NO ACTION, and SET NULL. **Notice** At present, OceanBase Database does not support **SET NULL**. For more information about the syntax, see [CREATE TABLE](https://www.oceanbase.com/docs/oceanbase-database/oceanbase-database/V3.2.1/create-table), or the official documentation of MySQL or Oracle. |
+| Update | Specifies the action to be performed on the current table when the data in the associated table is updated. The current table is the child table, and the associated table is the parent table. The following four types of action are supported: **CASCADE**, **NO ACTION**, **RESTRICT**, and **SET NULL**. OceanBase Database supports different foreign key actions in MySQL and Oracle modes. - In MySQL mode, OceanBase Database allows you to specify CASCADE, NO ACTION, RESTRICT, and SET NULL. - In Oracle mode, OceanBase Database allows you to specify NO ACTION. **Notice** At present, OceanBase Database does not support **SET NULL**. For more information about the syntax, see [CREATE TABLE](https://www.oceanbase.com/docs/oceanbase-database/oceanbase-database/V3.2.1/create-table), or the official documentation of MySQL or Oracle. |
+| Check Condition | Specifies the check rules for data verification when **Check Constraint** is enabled. This field is valid only in Oracle mode. |
+
+
+
+The constraint setting section also provides three buttons.
+
+
+| Button | Description |
+|-----|-------------------------|
+| Create | Click this button to add a constraint. |
+| Edit | Click this button to edit the selected constraint. You can also directly double-click a cell to edit it. |
+| Delete | Click this button to delete the selected constraint. |
+
+
+
+### Step 6: Verify the SQL statement.
+
+
+
+Click **Submit** to go to the SQL Confirmation page.
+
+You can edit the SQL statement on the SQL Confirmation page. Syntax:
+
+```sql
+CREATE TABLE table_name (column_name column_type, column_name column_type,.......);
+```
+
+| Parameter | Description |
+|--------------|----------------------------------------|
+| CREATE TABLE | The key word that indicates the creation ofa table with a specified name. You must have the privileges to create tables. |
+| table_name | The name of the table. The table name must conform to the identifier naming rules. |
+| column_name column_type | The name and data type of the column or field in the table. To create multiple columns, separate the tuple with commas (,). |
+
+
+
+### Step 7: Complete the table creation.
+
+Click **Run**. After the table is created, the employee table appears in the table list in the left-side navigation pane.
+
+
+
+> **Note**
+> To manage a table, right-click the table name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Single Table Import **, **Single Table Export**, **Download**, **Mock Data**, **Open SQL Window**, **Copy**, **Rename**, **Delete**, and **Refresh**.
+
+For more information, see [Manage table data](../1.web-odc-table-objects/5.web-odc-manage-table-data.md).
+
+You can use the `SELECT` statement to query data in the new table.
+
+Syntax:
+
+```sql
+SELECT
+ column_name,
+ column_name
+FROM
+ table_name [WHERE Clause] [LIMIT N] [ OFFSET M]
+```
+
+
+| Parameter | Description |
+|-------------|------------------------------------------------------|
+| SELECT | The key word that indicates the name of the statement. You can use the SELECT statement to read one or more records. |
+| column_name | The name of the column to be queried. You can use an asterisk (*) to query all columns |
+| WHERE | The key word of the condition clause. |
+| LIMIT | The number of records to be returned. |
+| OFFSET | The data offset from which the SELECT statement starts to query. The default offset is 0. |
+
+
+
+Example:
+
+```sql
+SELECT `emp_no`, `birthdate`, `name`, `gender` FROM `employee`;
+```
+
+
+
+
+
+
+
+## Related topics
+* [Create a view](../2.web-odc-view-objects/2.web-odc-create-a-view.md)
+* [Create a function](../3.web-odc-function-objects/2.web-odc-create-a-function.md)
+* [Create a stored procedure](../4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+* [Create a program package](../6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+* [Create a trigger](../7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+* [Create a type](../8.web-odc-type-objects/2.web-odc-create-a-type.md)
+* [Create a synonym](../9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md)
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/2.web-odc-create-a-table.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/2.web-odc-create-a-table.md
new file mode 100644
index 00000000..24c1bab3
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/2.web-odc-create-a-table.md
@@ -0,0 +1,263 @@
+Create a table
+========================
+
+
+
+Overview
+-----------------------
+
+OceanBase Developer Center (ODC) allows you to create a table on a GUI. This topic describes how to create a table in the ODC console.
+
+
+
+As shown in the preceding figure, you can create a table in the following seven steps:
+
+1. Specify the basic information.
+
+2. Set columns.
+
+3. Set the index.
+
+4. Set constraints.
+
+5. Set partitioning rules.
+
+6. Confirm the SQL statement.
+
+7. Complete the table creation.
+
+
+
+
+
+
+Procedure
+-------------------------
+
+In the following example, a table named `employee` is created in the ODC console. The table contains the **emp_no**, **birthdate**, **name**, and **gender** columns. Perform the following operations:
+
+### Step 1: Specify the basic information
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables. To create a table, click **+** in the upper-right corner of the table list or click **Create** in the top navigation bar.
+
+In the **Basic Info** section, specify **Table Name** and **Description**.
+
+
+
+> **Note**
+>
In MySQL mode, you also need to specify Default Character Set and Default Sorting Rule.
+>
After you specify the basic information and switch to the Column step, the basic information is submitted.
+
+### Step 2: Set columns
+
+The following figure and table show the information that you need to specify when you add a column.
+
+
+
+
+
+| Field | Description |
+|---------------|--------------------------------------------------------------------|
+| Name | The name of the column. |
+| Type | The data type of the column. For more information about data types, see [OceanBase Database Developer Guide](https://www.oceanbase.com/docs/enterprise/oceanbase-database/oceanbase-database/V3.2.3/data-type-overview). |
+| Length | The length of the data type. |
+| Scale | The number of decimal places of the data type. |
+| Non-empty | Specifies whether the value of the column must be specified. |
+| Auto-increment | Specifies whether to set the column to an auto-increment column. This parameter is valid in MySQL mode. **Notice** Only one auto-increment column is allowed for each table. After a column is set to an auto-increment column, the auto-increment checkbox of other columns cannot be selected. |
+| Virtual Column | Specifies whether to set the column to a virtual column. **Notice** When you set a virtual column, you must specify its expression. When you create a virtual column, you must define an expression that the virtual column depends on. A virtual column is a generated column. A generated column can be a virtual generated column or a stored generated column. The value of a virtual column is calculated based on the expression only when the column is used. Therefore, when you insert data into the table, you cannot specify values for the virtual column. |
+| Default Value/Expression | The default value or expression of the column. |
+| Comment | The additional information about the column. |
+
+
+
+The following table describes operations that you can perform on the column setting page.
+
+| Operation | Description |
+|--------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| Toolbar operations | You can add or delete columns by using the top toolbar of the page. |
+| Click a row ID | - You can click a row ID to select the row and display the quick access toolbar that allows you to add or delete a row. - You can click a row ID to select the row, and then drag the row to adjust its order. |
+| Right-click a row | You can right-click a row to select it, and then select **Copy** or **Move Down** from the context menu that appears. |
+
+
+> **Note**
+>
After you copy a row, you can paste the row by using the Command + V or Ctrl + V shortcut keys.
+>
The auxiliary editing section at the bottom of the page displays additional information about the selected column.
+>
Settings in the Basic Information and Column steps are required. Settings in other configuration steps are optional. After you specify settings in the Basic Information and Column steps, you can click Commit and Confirm SQL Statement to create a table.
+
+
+### Step 3: Set indexes
+
+If a table contains a large amount of data, you can use indexes to accelerate data queries. An index is a data structure that pre-sorts the values of one or more columns in a table. By using indexes, you can directly locate records that meet the conditions.
+
+The following figure and table show the information that you need to specify when you set the index.
+
+
+
+| Field | Description |
+|------|--------------------------------------------------------------------------------|
+| Index Name | The name of the index. |
+| Scope | The default value is **GLOBAL**. Valid values: **GLOBAL** and **LOCAL**. |
+| Method | The default value is **BTREE**, which is applicable to a global index. Valid values: **Empty, BTREE, and HASH**. - A BTREE index stores data in a B+ tree structure, and is suitable for searching for SQL statements in the specified index scope. - A HASH index is implemented based on a HASH table, and is used only when the query conditions exactly match all columns in the HASH index. A HASH index can be used only for query conditions that use the equal operator (=), IN operator, or NULL-safe equal operator (<=>). A HASH index cannot be used for sorting and is not suitable for columns with less distinctive values, such as the gender column. |
+| Index Type | The default value is **NORMAL**. Valid values: **NORMAL, UNIQUE**, and **FULLTEXT**. - **NORMAL** indicates a normal index. - **UNIQUE** indicates a unique index that does not allow duplicate values, such as the **emp_no** column. - **FULLTEXT** indicates a full-text index, which is used to search a table that contains a large amount of data. |
+| Columns | The columns to be indexed. Pay attention to the order of the indexed columns. |
+| Invisible | Specify whether the index is invisible. |
+
+
+
+The index setting page provides the following icons.
+
+| Icon | Description |
+|-----|------------|
+| Create | Click this icon to add an index. |
+| Delete | Click this icon to delete the selected index. |
+
+
+
+### Step 4: Set constraints
+
+Constraints are used to specify data rules for a table. A data operation that violates the constraints will be terminated.
+
+
+
+ODC supports the following four table constraints:
+
+* **Primary Key Constraint**: defines a primary key to uniquely identify each row of data in the table. A primary key constraint can be a field or a group of fields. You can set only one primary key constraint for a table, and you cannot edit the constraint after it is configured.
+
+* **Unique Constraint**: ensures that the data in a field or a group of fields is unique in the table. You can set multiple unique constraints in one table.
+
+* **Foreign Key Constraint**: associates one or more columns in two tables. A foreign key constraint is used to maintain the data consistency and integrity between associated tables. After you complete the setting of foreign key constraints, you cannot create new constraints or edit existing constraints.
+
+* **Check Constraints**: checks the data in the database based on the configured check rules when you edit the data. Data modification is allowed only after the check is passed.
+
+
+OceanBase Database supports different constraints in MySQL and Oracle modes, and different constraints require different information. Therefore, you need to specify the required information based on the constraint you selected and the requirements on the page.
+
+
+| Field | Description |
+|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Constraint Name | The name of the constraint. |
+| Column Information | The field or a group of fields specified as the constraint. |
+| Associated Schema | The schema where the associated table is located when **Foreign Key Constraint** is used. The associated table is the parent table. This field is valid only in Oracle mode. |
+| Associated Database | The database where the associated table is located when **Foreign Key Constraint** is used. The associated table is the parent table. This field is valid only in MySQL mode. |
+| Associated Table | The associated table when **Foreign Key Constraint** is used. The associated table is the parent table. |
+| Associated Field | The associated field when **Foreign Key Constraint** is used. The associated field is in the parent table. |
+| Delete | Specifies the action to be performed on the current table when the data in the associated table is deleted. The current table is the child table, and the associated table is the parent table. The following four types of action are supported: **CASCADE**, **NO ACTION**, **RESTRICT**, and **SET NULL**. OceanBase Database supports different foreign key actions in MySQL and Oracle modes. - In MySQL mode, OceanBase Database allows you to specify **CASCADE**, **NO ACTION, RESTRICT**, and **SET NULL**. - In Oracle mode, OceanBase Database allows you to specify **CASCADE**, **NO ACTION**, and **SET NULL**.
**Notice** At present, OceanBase Database does not support **SET NULL**. For more information about the syntax, see [Create a table](https://www.oceanbase.com/docs/enterprise-oceanbase-database-cn-10000000000357139), or the official documentation of MySQL or Oracle. |
+| Update | Specifies the action to be performed on the current table when the data in the associated table is updated. The current table is the child table, and the associated table is the parent table. The following four types of action are supported: **CASCADE**, **NO ACTION**, **RESTRICT**, and **SET NULL**. OceanBase Database supports different foreign key actions in MySQL and Oracle modes. - In MySQL mode, OceanBase Database allows you to specify **CASCADE**, **NO ACTION, RESTRICT**, and **SET NULL**. - In Oracle mode, OceanBase Database allows you to specify **NO ACTION**. **Notice** At present, OceanBase Database does not support **SET NULL**. For more information about the syntax, see [Create a table](https://www.oceanbase.com/docs/enterprise-oceanbase-database-cn-10000000000357139), or the official documentation of MySQL or Oracle. |
+| Check Condition | Specifies the check rules for data verification when **Check Constraint** is enabled. |
+
+The constraint setting page provides the following icons.
+
+
+| Icon | Description |
+|-----|------------|
+| Create | Click this icon to add a constraint. |
+| Delete | Click this icon to delete the selected constraint. |
+
+### Step 5: Set partitioning rules
+
+
+
+You can partition a table that contains a large amount of data. After a table is partitioned, data in the table is stored in multiple tablespaces. The database does not scan the entire table for a query.
+
+* In MySQL mode, OceanBase Database supports the following six partitioning methods: **Key**, **Hash**, **Range**, **Range Columns**, **List**, and **List Columns**.
+
+
+
+* In Oracle mode, OceanBase Database supports the following three partitioning methods: **List**, **Range**, and **Hash**.
+
+ The definition of a partition in MySQL mode is different from that in Oracle mode. So, the values of the following fields vary in different modes. You need to specify the following fields based on the selected partitioning method.
+
+ | Field | Description |
+ |------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Partitioning Method | Specifies the partitioning method. The partitioning methods supported in MySQL mode are different from those in Oracle mode. - Range partitioning: Multiple rows with column values in an ordered, continuous, and non-overlapping range are assigned to a partition. - List partitioning: A table is partitioned based on the enumeration values. - Hash partitioning: A table is partitioned based on a given number of partitions. For a table that stores data without a clear pattern or range, you can use hash partitioning to randomly distribute values of the partition column to different partitions based on the HASH algorithm. - Key partitioning: This partitioning method is similar to HASH partitioning. The difference is that key partitioning only supports computation of one or more columns, and the MySQL server provides its own hash function. At least one INT type column is required for Key partitioning. For more information about partitioning, see [Overview](https://www.oceanbase.com/docs/enterprise/oceanbase-database-cn/V3.2.3/10000000000357153). |
+ | Field | The column that is used as the partition key. |
+ | Expression | Partitions are divided based on the return value of the expression. The partition expression is not supported in Oracle mode. |
+ | Partition | Based on the value specified for **Partitioning Method**, you may need to specify information such as **Partition Name**, **Partition Quantity**, **Upper Limit**, and **Value Enumeration**. You can add multiple partitions and drag selected fields to adjust their order. |
+
+
+
+
+
+
+### Step 6: Confirm the SQL statement
+
+
+
+After you click **Submit**, you can view the statement on the SQL Confirmation page. To view lengthy clauses, click **SQL Check** and **Format** in the lower-right corner of the page.
+
+Syntax:
+
+```sql
+CREATE TABLE table_name (column_name column_type, column_name column_type,.......);
+```
+
+
+
+Parameters
+
+| Parameter | Description |
+|-------------------------|----------------------------------------|
+| CREATE TABLE | The key word that indicates the creation ofa table with a specified name. You must have the privileges to create tables. |
+| table_name | The name of the table. The table name must conform to the identifier naming rules. |
+| column_name column_type | The name and data type of the column in the table. To create multiple columns, separate the tuple with commas (,). |
+
+
+
+### Step 7: Complete the table creation
+
+Click **Execute**. After the table is created, the **employee** table appears in the table list in the left-side navigation pane.
+
+
+
+> **Note**
+> To manage a table, right-click the table name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View Table Structure**, **View DDL**, **View Table Data**, **CreateTable**, **Import**, **Export**, **Download**, **Mock Data**, **Open SQL Window**, **Copy**, **Rename**, **Delete**, and **Refresh**.
+
+For more information, see [Manage table data](../1.web-odc-table-objects/5.web-odc-manage-table-data.md).
+
+You can use the `SELECT` statement to query data in the new table.
+
+Syntax:
+
+```sql
+SELECT
+ column_name,
+ column_name
+FROM
+ table_name [WHERE Clause] [LIMIT N] [ OFFSET M]
+```
+
+
+
+Parameters
+
+| Parameter | Description |
+|-------------|------------------------------------------------------|
+| SELECT | The key word that indicates the name of the statement. You can use the SELECT statement to read one or more records. |
+| column_name | The name of the column to be queried. You can use an asterisk (\*) to query all columns |
+| WHERE | The key word of the condition clause. |
+| LIMIT | The number of records to be returned. |
+| OFFSET | The data offset from which the SELECT statement starts to query. The default offset is 0. |
+
+
+
+Example:
+
+```sql
+SELECT `emp_no`, `birthdate`, `name`, `gender` FROM `employee`;
+```
+
+
+
+
+
+Related topics
+-------------------------
+
+* [Create a view](../2.web-odc-view-objects/2.web-odc-create-a-view.md)
+* [Create a function](../3.web-odc-function-objects/2.web-odc-create-a-function.md)
+* [Create a stored procedure](../4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+* [Create a program package](../6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+* [Create a trigger](../7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+* [Create a type](../8.web-odc-type-objects/2.web-odc-create-a-type.md)
+* [Create a synonym](../9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md)
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/3.web-odc-table-list.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/3.web-odc-table-list.md
new file mode 100644
index 00000000..72344787
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/3.web-odc-table-list.md
@@ -0,0 +1,39 @@
+Table list
+===============================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables. The table list displays the table objects in the connected database. In the table list, you can view the structure tree of an object. You can also right-click the target object to perform some management actions on the object.
+
+Structure tree
+-----------------------------------
+
+You can click the expand icon before the name of the target table in the table list, and the structure tree of the table is displayed in a drop-down list, as shown in the following figure. The structure tree of a table can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section. In this section, you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------------------
+
+The names of table objects support ascending example by head character by default in the table list.
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+
+| Option | Description |
+|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Table Structure | Click this option to go to the Attribute tab. On this tab, you can view comprehensive information of the table such as the basic information, columns, indexes, constraints, and DDL statements. |
+| View DDL | Click this option to go to the Attribute tab to view the SQL statements that define the table. |
+| View Table Data | Click this option to go to the Data tab to view the data in the table. |
+| Create Table | Click this option to go to the table creation page, where you can create a table as prompted. |
+| Single Table Import | Click this option to import data to the table. For more information, see [Single table export and import](../../6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md). |
+| Single Table Export | Click this option to export data from the table. For more information, see [Single table export and import](../../6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md). |
+| Download | Download the SQL file for the table object. |
+| Mock Data | Click this option to go to the **Mock Data** panel. |
+| Open SQL Window | Click this option to open a new SQL window. |
+| Copy | Click this option to copy the table name, SELECT statement, INSERT statement, UPDATE statement, or DELETE statement. |
+| Rename | Click this option to rename the table. |
+| Delete | Click this option to delete the table. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the table, so that the structure tree displays the latest information. |
+| View Column/View Index/View Constraint | Click these options to go to the Attribute tab to view specific information about the columns, indexes, or constraints in the table. |
+| Create Column/Create Index/Create Constraint | Click these options to create a column, an index, or a constraint. |
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/4.web-odc-manage-table-attributes.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/4.web-odc-manage-table-attributes.md
new file mode 100644
index 00000000..22b07e20
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/4.web-odc-manage-table-attributes.md
@@ -0,0 +1,184 @@
+Manage table attributes
+============================================
+
+
+
+Overview
+-----------------------------
+
+
+
+1. After you log on to OceanBase Developer Center (ODC), click the name of the target connection on the ODC homepage to go to the corresponding connection management page.
+
+
+
+2. In the left-side navigation pane, click **Table** to get a list of tables.
+
+
+
+3. Double-click the name of a table in the table list to go to the table management page.
+
+
+
+4. Click **Attribute** in the top navigation bar to go to the Attribute tab.
+
+ The Attribute tab displays the following table attributes:
+
+ * **Basic information**
+
+
+
+ * **Column**
+
+
+
+ * **Index**
+
+
+
+ * **Constraints**
+
+
+
+ * **Partition**
+
+
+
+ * **DDL**
+
+
+
+
+
+
+
+
+
+Basic information
+--------------------------------------
+
+
+
+In the left-side navigation pane of the **Attribute** tab, click **Basic Info** to view the basic information about the table.
+
+
+| Field | Description |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------|
+| Table Name | Displays the name of the table. You can modify the table name here. |
+| Default Character Set | Displays the character set that the table uses. |
+| Default Sorting Rule | Displays the sorting rule that the table uses. |
+| Description | Displays the description that you specified when you created the table. You can also modify the table description here. |
+|Row data volume|Displays the number of rows.|
+|Size|Displays the data size.|
+
+
+
+The basic information page provides the following buttons.
+
+
+| Button | Description |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Edit | Click  to modify the basic information. |
+| Refresh | Click  to refresh the basic information. |
+
+
+
+Column information
+---------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Column** to view the columns in the table. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to add a field (or column) to the table. |
+| Delete | Click  to delete the selected field. |
+| Refresh | Click  to refresh the field information. |
+| Filter | Click  (to the right of **Field Name** ) to filter or search for fields. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.|
+
+
+
+Index information
+--------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Index** to view the indexes on the table. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to add an index to the table. |
+| Delete | Click  to delete the selected index. |
+| Refresh | Click  to refresh the index information. |
+| Filter | Click  (to the right of **Index Name** ) to filter or search for indexes. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.An index cannot be modified after it is created. |
+
+> **Note**
+> An index cannot be modified after it is created.
+
+Constraint information
+-------------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Constraint** to view the constraints on the table. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to add a constraint to the table. |
+| Delete | Click  to delete the selected constraint. |
+| Refresh | Click  to refresh the constraint list. |
+|Filter|  (to the right of **Name** ) to filter or search for constraints. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.|
+
+
+> **Note**
+>
The buttons provided vary with the constraint method. If a button is dimmed out or not present in the navigation bar, it means that the constraint method does not support the corresponding action.
+>
To view foreign key constraints on a table, you can query the `all_constraints` view in Oracle mode, or the information_schema.key_column_usage table in MySQL mode since OBServer V2.2.6.
+>
OceanBase Database supports constraint checking only in Oracle mode.
+
+
+
+
+
+
+Partition information
+------------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Partition** to view the information about the partitions in the table. The information includes **Partition Name** , **Order** , **Partitioning Method** , **Expression** , **Upper limit of the range** , and **Enumeration Value** . In Oracle mode, **Expression** indicates the partitioning key. **Partitioning Method** indicates the partitioning method specified when the table was created. The information displayed varies with the partitioning method. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to create a partition from an undefined range. |
+| Delete | Click  to delete the selected partition and destroy the data in the partition. |
+| Refresh | Click  to refresh the partition list. |
+| Filter | Click  to filter partitions by partition name, order, partitioning method, expression, or upper limit of the range. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.|
+
+
+> **Note**
+> In ODC V3.3.0 and later versions, you can view the partitions of table objects not necessarily under the SYS tenant.
+
+
+
+DDL information
+------------------------------------
+
+
+
+In the left-side navigation pane of the **Attribute** tab, click **DDL** to view the DDL statements that define the table. You cannot edit these statements. Click  in the toolbar to view the statements.
+
+| Button | Description |
+|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Format | Click [Format](https://help-static-aliyun-doc.aliyuncs.com/assets/img/en-US/4411843561/p412851.jpg) to format the statements. |
+| Download | Click Download to download the statements. |
+| Refresh | Click  to refresh the statement. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.|
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/5.web-odc-manage-table-data.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/5.web-odc-manage-table-data.md
new file mode 100644
index 00000000..5434e441
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/1.web-odc-table-objects/5.web-odc-manage-table-data.md
@@ -0,0 +1,135 @@
+Manage table data
+======================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables. Double-click the name of a table in the table list to go to the table management page. Click the **Data** button in the navigation bar on the top of the page to go to the Data tab, where you can view, add, modify, and delete table data.
+**Notice**
+
+
+
+In ODC, connections to the same database share the same session. In ODC V2.3.2 and later versions, auto-commit is turned off by default in Oracle mode, so you need to manually commit transactions. You can modify the value of the autocommit parameter on the **Session Properties** page to change this setting. For more information, see [Session management](6.web-odc-user-guide/10.web-odc-session-management.md).
+
+
+
+View data
+------------------------------
+
+On the Data tab, ODC displays data in the form of a table. The navigation bar provides the following buttons for you to view and manage the data:
+
+* **Enable Editing** : Click this button to enable the editing mode so that you can edit the data in the table.
+
+
+
+* **Commit** : Auto-commit is turned off by default in Oracle mode, so you need to click this button to commit the current transaction. After you click this button, a dialog box appears, indicating that the current connection uses a shared session and the commit will apply to all windows. Click **Yes** to apply the commit. In MySQL mode, auto-commit is turned on by default, so this button is not displayed.
+
+
+
+* **Rollback** : Auto-commit is turned off by default in Oracle mode. You can click this button to roll back the current transaction. After you click this button, a dialog box appears, indicating that the current connection uses a shared session and the rollback will apply to all windows. Click **Yes** to apply the rollback. In MySQL mode, auto-commit is turned on by default, so this button is not displayed.
+
+
+
+* **Refresh** : Click this button to refresh the data in the table.
+
+
+
+* **Column Mode** : Click this button to display the data in the selected rows in the form of a table. On the **Column Mode** page, you can switch to the previous or next row. The column mode makes it easier to view data in a row that has many columns.
+
+
+
+* **Columns** : Click this button to select the columns to be displayed on the page.
+
+
+
+* **Back to Start** : Click this button to jump to the first page.
+
+
+
+* **Previous** : Click this button to go to the previous page.
+
+
+
+* **Next** : Click this button to go to the next page.
+
+
+
+* **Jump to Bottom** : Click this button to jump to the last page.
+
+
+
+* **Display Data Volume** : Click this button to set the maximum number of rows to be displayed on a page.
+
+
+
+* **Export** : Click this button to export the data in the table. You can specify the type of the exported file, the character set, and the number of rows to be exported. The file type can be CSV or SQL, and the character set can be GBK or UTF8. You can export up to 10,000 rows from a result set.
+
+
+
+* **Mock Data** : Click this button to mock data in the table. For more information, see [Data mocking](6.web-odc-user-guide/6.web-odc-use-tools/2.web-odc-data-mocking.md).
+
+
+
+
+
+
+Edit data
+------------------------------
+
+Click **Enable Editing** in the navigation bar on the Data tab to enter the editing mode, as shown in the following figure. ODC use different colors to mark data in different states. New data is marked in green, deleted data in red, and modified data in orange.
+
+
+
+In editing mode, the navigation bar provides the following buttons for you to edit data in the table:
+
+* **Add Row** : Click this button to insert an empty row to the table. Double-click a cell to insert data to it. ODC provides the verification feature and related tools to help you insert data in a more convenient way. For example, if the current cell is of the date type, ODC displays a calendar for you to select the to-be-inserted date from.
+
+
+
+* **Delete Row** : Click this button to delete the selected rows from the table.
+
+
+
+* **Copy Current Row** : Click this button to copy the selected rows in the table.
+
+
+
+* **Column Mode** : Click this button to display the data in the selected rows in the form of a table. On the **Column Mode** page, you can switch to the previous or next row. The column mode makes it easier to view data in a row that has many columns.
+
+
+
+* **Columns** : Click this button to select the columns to be displayed on the page.
+
+
+
+* **Back to Start** : Click this button to jump to the first page.
+
+
+
+* **Previous** : Click this button to go to the previous page.
+
+
+
+* **Next** : Click this button to go to the next page.
+
+
+
+* **Jump to Bottom** : Click this button to jump to the last page.
+
+
+
+* **Display Data Volume** : Click this button to set the maximum number of rows to be displayed on a page.
+
+
+
+* **Cancel** : Click this button to exit the editing mode.
+
+
+
+* **Confirm Modification** : Click this button to generate the SQL statement for the action. After you verify the statement, click **Execute** to apply the data modification. If auto-commit is turned on, the transaction is automatically committed after you click this button.
+
+
+
+* **Modify and Submit** : Auto-commit is turned off by default in Oracle mode, so you need to click this button to commit the current transaction. After you click this button, a dialog box appears, indicating that the current connection uses a shared session and the commit will apply to all windows. Click **Yes** to apply the commit. In MySQL mode, auto-commit is turned on by default, so this button is not displayed.
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/1.web-odc-view-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/1.web-odc-view-objects-overview.md
new file mode 100644
index 00000000..2c047daf
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/1.web-odc-view-objects-overview.md
@@ -0,0 +1,29 @@
+Overview
+=============================
+
+A view is a virtual table created based on one or more tables or views. The tables on which the view is based are called base tables. Views do not store data. You can use views to query and modify data in base tables. Therefore, the definition of a view is stored in the data dictionary, and no data copy related to the view definition is stored in the database. Views are similar to physical tables in the database, so you can perform operations on views like on tables. When you modify data in a view, you are actually modifying data in base tables. Conversely, the modification of data in base tables is also reflected in views generated based on these base tables.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click View in the left-side navigation pane to get a list of views. In the view list, you can double-click a view name to go to the view management page. On this page, you can check the data of the view on the Data tab or the attributes such as the basic information, columns, and DDL statements of the view on the Attribute tab.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.0.0 or a later version |
+| OceanBase Database in MySQL mode | V1.4.1 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on view objects in ODC.
+
+* [Create a view](6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/2.web-odc-create-a-view.md)
+
+
+
+* [Manage views](6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/3.web-odc-manage-views.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/2.web-odc-create-a-view.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/2.web-odc-create-a-view.md
new file mode 100644
index 00000000..a8dcf0c7
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/2.web-odc-create-a-view.md
@@ -0,0 +1,200 @@
+# Create a view
+
+ODC supports visualized view creation. This topic describes how to create a view with ODC.
+
+## Overview
+
+A view is a virtual table that consists of data in one or more tables. You can use the `SELECT` statement to query a view. A view itself does not contain data.
+
+### Purposes of views
+
+* Simplifies data queries: You can use views to combine data from different tables in a database into a single virtual table, and thereby convert multi-table queries into a single-table query.
+
+
+
+* Controls data access: You can use views to present certain data to specific users. These users can view only the data in a specific view.
+
+
+
+
+
+As shown in the preceding figure, you can create a view in the following five steps:
+
+1. Specify the basic information.
+
+
+
+2. Select base tables.
+
+
+
+3. Select fields.
+
+
+
+4. Verify the SQL statement.
+
+
+
+5. Complete the view creation.
+
+
+
+
+
+
+## Procedure
+
+In the following example, an employee salary view is created in the OceanBase Developer Center (ODC) console. The salary view consists of the name field in the employee table and the budget and dept_name fields in the consumer table. Procedure:
+
+### Step 1: Specify the basic information.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **View** in the left-side navigation pane to get a list of views. To create a view, click **+** in the upper-right corner of the view list or click **Create** in the top navigation bar.
+
+In the **Basic Info** section, specify **View Name** and **Check Item**.
+
+* **View Name**: specifies the name of the view.
+
+
+
+* **Check Item**: specifies the constraints on the input data. OceanBase Database in Oracle mode supports only the read-only mode. Default value: **None**.
+
+
+
+
+
+
+
+
+After you specify all the basic information, click **OK**.
+
+After the basic information is specified, you can either click **Next: Verify SQL Statement** to go to Step 4 and verify the SQL statement, or proceed to Step 2 and select base tables.
+
+### Step 2: Select base tables.
+
+After you specify the basic information, you can proceed to Step 2 and select base tables, or skip this step.
+
+In the **Select Base Tables** section, the list on the left displays available base tables in the hierarchy of schema > database > table/view. You can search for base tables in this list. Select tables or views in this base table list, and click the add icon (>) next to the list to add the selected tables or views to the table operation area on the right.
+
+
+
+In the table operation area, you can perform the following operations on a selected base table.
+
+
+| Operation | Description |
+|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Set an alias | You can set an alias for a selected base table. Click **\** next to the table name in the table operation area and enter the alias. This operation is optional. |
+| Set association relationships | When two or more tables exist in the table operation area, you can define an association relationship between the tables. The default association is **JOIN**. You do not need to set an association relationship for the last table. Click the  icon next to Alias and select an association relationship. Supported options: **JOIN**, **INNER JOIN**, **LEFT JOIN**, **RIGHT JOIN**, **CROSS JOIN**, **FULL JOIN**, **UNION**, **UNION ALL**, **INTERSECT**, **MINUS**, **LEFT OUTER JOIN**, **RIGHT OUTER JOIN**, and **FULL OUTER JOIN**. |
+| Adjust the association order | You can drag the base tables in the table operation area to reorder them. If you drag a table to the bottom of the list, the association relationships of this table are removed. |
+| Delete a base table | You can click the delete icon next to a table in the table operation area to delete it from the table operation area. After you delete a table, its associations with the next table are removed. |
+
+
+
+After you select and configure the base tables, click **OK**.
+
+### Step 3: Select fields.
+
+After you select the base tables, you can proceed to Step 3 and select fields. If you skip Step 2, this step is unavailable.
+
+In the **Select Fields** section, the list on the left displays the fields of the base tables that you selected in Step 2 in the hierarchy of schema > database > table/view. You can search for fields in this list. Select fields in the field list, and click the add icon (>) next to the list to add the selected fields to the field operation area on the right.
+
+
+
+In the field operation area, you can perform the following operations on a selected field.
+
+
+| Operation | Description |
+|--------|-----------------------------------------------------------|
+| Set an alias | You can set an alias for a selected field. Click **\** next to the field name in the field operation area and enter the alias. This operation is optional. |
+| Adjust the association order | You can drag the fields in the field operation area to reorder them. |
+| Delete a field | You can click the delete icon next to a field in the field operation area to delete it from the operation area. |
+| Customize fields | Click **+Custom** in the upper-right corner of the field operation area to add a field to the operation area. You must specify a name and an alias for the field. |
+
+
+
+After you select and configure the fields, click **OK**.
+
+### Step 4: Verify the SQL statement.
+
+After you complete all the previous steps, click **Next: Verify SQL Statement** to go to the statement editing page.
+
+
+
+On the statement editing page, the view definition statements are generated based on the information specified in the **Basic Info**, **Select Base Tables**, and **Select Fields** sections. When two or more tables are included, you must complete the statement according to the relationship between the tables and logical conditions. After you complete the statements, click **Create** in the upper-right corner of the page to create the view.
+
+You can edit the SQL statements of the created view on the Create View page. Syntax:
+
+```sql
+CREATE VIEW view_name AS
+SELECT
+ column1,
+ column2.....
+FROM
+ table_name
+WHERE
+ [condition];
+```
+
+
+
+In addition, the toolbar on the editing page provides the following buttons.
+
+
+| Button | Description |
+|-------|--------------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | Click this button and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+|IN Value Conversion|A format such as A B can be converted to ('A','B') format.|
+| Previous | Click this button to go back to the **Create View** page, where you can continue to edit or modify the parameters in the **Basic Info**, **Select Base Tables**, and **Select Fields** sections. |
+
+
+
+### Step 5: Complete the view creation.
+
+Click **Create** in the upper-right corner to create the view. After a view is created, you can use the `SELECT` statement to query it, just like how you query a table.
+
+
+
+> **Note**
+> To manage a view, right-click the view name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Delete**, **Download**, and **Copy**.
+
+For more information, see [Manage views](../2.web-odc-view-objects/3.web-odc-manage-views.md).
+
+Syntax:
+
+```sql
+SELECT
+column1,
+column2.....
+FROM
+table_name;
+```
+
+
+
+Example:
+
+```sql
+SELECT `name`, `budget`, `department_name` FROM `salary`;
+```
+
+
+
+
+
+## Related topics
+
+* [Create a table](../1.web-odc-table-objects/2.web-odc-create-a-table.md)
+* [Create a function](../3.web-odc-function-objects/2.web-odc-create-a-function.md)
+* [Create a stored procedure](../4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+* [Create a program package](../6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+* [Create a trigger](../7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+* [Create a type](../8.web-odc-type-objects/2.web-odc-create-a-type.md)
+* [Create a synonym](../9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md)
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/3.web-odc-manage-views.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/3.web-odc-manage-views.md
new file mode 100644
index 00000000..f6040bf7
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/2.web-odc-view-objects/3.web-odc-manage-views.md
@@ -0,0 +1,57 @@
+Manage views
+=================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **View** in the left-side navigation pane to get a list of views in the current database.
+
+In the view list, you can view the **structure tree** of an object. You can also right-click the target object to perform some **management actions** on the object. You can also double-click the name of the target view to go to the view management page, which includes the **Attribute and Data tabs** .
+
+Structure tree
+-----------------------
+
+You can click the expand icon before the name of the target view in the view list, and the structure tree of the view is displayed in a drop-down list, as shown in the following figure. The structure tree of a view can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section, where you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------
+
+The names of view objects support ascending example by head character by default in the view list.
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Option | Description |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Check View Properties | Click this option to go to the **Attribute** tab, where you can view comprehensive information such as the basic information, columns, and code of the view. |
+| Check View Data | Click this option to go to the **Data** tab, to check data in the view. |
+| Create View | Click this option to go to the Create View page, where you can create a view as prompted. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the view object. |
+| Copy | Click this option to copy the object name, SELECT statement, INSERT statement, UPDATE statement, or DELETE statement. |
+| Delete | Click this option to delete the current view object. |
+
+
+
+Attribute and Data tabs
+--------------------------------
+
+
+
+* Attribute tab:
+ * **Basic Info** : displays information such as **View Name** , **Check Item** , and **Created By** .
+
+
+
+ * **Column** : displays information of the base table corresponding to the view, such as **Field Name** , **Data Type** , and **Comment** .
+
+
+
+ * **Code** : displays the definition script of the view.
+
+
+* Data tab: displays the columns that the view contains.
+
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/1.web-odc-function-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/1.web-odc-function-objects-overview.md
new file mode 100644
index 00000000..bc3a73f9
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/1.web-odc-function-objects-overview.md
@@ -0,0 +1,29 @@
+Overview
+=============================
+
+A function defines a collection of SQL statements. You can call a function in an SQL statement to get a return value from the execution.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click Function in the left-side navigation pane to get a list of functions. In the function list, double-click the name of a function to go to the function management page, where you can view the basic information, parameters, and data definition language (DDL) statements of the function.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.0.0 or a later version |
+| OceanBase Database in MySQL mode | V2.0.0 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on function objects in ODC.
+
+* [Create a function](6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/2.web-odc-create-a-function.md)
+
+
+
+* [Manage functions](6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/3.web-odc-manage-functions.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/2.web-odc-create-a-function.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/2.web-odc-create-a-function.md
new file mode 100644
index 00000000..075648f7
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/2.web-odc-create-a-function.md
@@ -0,0 +1,197 @@
+# Create a function
+
+ODC supports visualized function creation. This topic describes how to create a function with ODC.
+
+## Overview
+
+A function is a subprogram defined in a database. You can call functions by using built-in SQL statements. If the built-in functions cannot meet your business requirements, OceanBase Developer Center (ODC) allows you to create functions. User-defined functions not only help you perform some calculations and special operations, but also reduce coding redundancy to improve the program readability.
+
+A function is a procedural object that is similar to a stored procedure in a database. Like a stored procedure, a function is a code snippet of SQL statements and procedural statements, and can be called by applications and other SQL statements.
+
+Differences between a user-defined function and a stored procedure:
+
+* A function returns only one result and is suitable for data processing that generates one result. A stored procedure may return zero or multiple results and is suitable for batch insertion and batch update.
+
+* You can call a function by using a `SELECT` statement. You can call a stored procedure by using a `CALL` statement.
+
+
+
+As shown in the preceding figure, you can create a function in the following six steps:
+
+1. Specify the function name.
+
+2. Specify the data type of the return value.
+
+3. Specify parameters.
+
+4. Verify the parameters of the new function.
+
+5. Edit the function.
+
+6. Complete the function creation.
+
+## Procedure
+
+In the following example, a function named function_emp is created in the ODC console to obtain the employee name from an employee table based on the employee ID. The function_emp function contains an INT type id parameter. Procedure:
+
+### Step 1: Specify the function name.
+
+Log on to the ODC console and click the name of a connection to go to the corresponding connection management page. You can click **Function** in the left-side navigation pane to get a list of functions. To create a function, click + in the upper-right corner of the function list or click **Create** in the top navigation bar.
+
+
+
+### Step 2: Specify the data type of the return value.
+
+For more information about data types, see [OceanBase Database Developer Guide](https://www.oceanbase.com/docs/enterprise/oceanbase-database/oceanbase-database/V3.2.3/data-type-overview).
+
+### Step 3: Specify parameters.
+
+1. Parameters specify the information passed to a function when the function is called.
+
+ * In Oracle mode, specify the following fields: **Name**, **Mode**, **Type**, and **Default Value**.
+
+
+
+ * In MySQL mode, specify the following fields: **Name**, **Type**, and **Length**.
+
+
+
+
+
+
+2. You can specify parameters by using one of the following three methods.
+
+ | Method | Description |
+ |----------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Use the quick access toolbar | In the quick access toolbar, you can add, delete, and move up and down parameters. |
+ | Click the row number | - You can click a row number to select a row and display the quick access toolbar that allows you to delete the row or move the row up or down. - You can click a row number to select the row, and then drag the row to adjust its order. |
+ | Right-click | Right-click the mouse to select the entire row, copy row or move down the row. |
+
+3. You need to specify the mode for the parameters.
+
+ The parameter mode setting is unavailable in MySQL mode. The Oracle mode supports the following parameter modes: **IN**, **OUT**, and **INOUT**.
+
+
+ | **Parameter** | **Type** |
+ |--------|-------------------------------------------------------------------|
+ | IN | Indicates an input parameter. When a function is called, the input parameter is passed to the function and used in the execution of the function. |
+ | OUT | Indicates an output parameter. When a function is called, the value of the output parameter is ignored and an empty value is passed to the function. The output parameter in the function body can be modified. The modified result is returned and passed to the argument that the output parameter represents. |
+ | INOUT | Indicates an inout parameter. An inout parameter is both an input parameter and an output parameter. |
+
+
+ > **Note**
+ > In Oracle mode, both functions and stored procedures support IN, OUT, and INOUT modes. In MySQL mode, functions support only IN mode, and stored procedures support IN, OUT, and INOUT modes.
+
+
+
+
+
+### Step 4: Verify the parameters of the new function.
+Click **OK** to go to the Create Function page.
+
+### Step 5: Edit the function.
+
+
+
+Edit the function statement on the Create Function page.
+You can edit the SQL statements of the created function on the Create Function page. Syntax:
+
+```sql
+CREATE FUNCTION < function name > ([ [ , ] ] …)
+RETURNS < type >
+< function body >
+```
+
+
+
+Parameters:
+
+
+| Parameter | Description |
+|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| \< function name \> | The name of the user-defined function.
**Notice** The name of a user-defined function cannot be the same as that of a stored procedure.
|
+| \< parameter \>\< type \> | Parameters of the function. This field contains only the name and type. You cannot specify the IN, OUT, or INOUT keyword. |
+| RETURNS\< type \> | The data type of the return value. `` specifies the data type of the return value.
**Notice** The SELECT statement in a RETURN VALUE statement returns only a single-row and single-column value.
|
+| \< function body \> | The body of the user-defined function. The function body must contain a `RETURN ` statement, where `` specifies the return value of the user-defined function. |
+
+
+
+Example:
+
+```sql
+CREATE FUNCTION `function_emp` ( `id` int(45)) RETURNS VARCHAR(300)
+
+-- The start of the function body.
+BEGIN
+
+-- Declare a variable.
+DECLARE
+ a VARCHAR(300);
+
+-- Assign a value to the variable.
+SELECT
+ name INTO a
+FROM
+ employee
+WHERE
+ emp_no = id;
+
+-- The return value.
+RETURN a;
+
+-- The end of the function body.
+END
+```
+
+
+
+### Step 6: Complete the function creation.
+
+Click **Create** in the upper-right corner to create the function. After a user-defined function is created, you can use the `SELECT` statement to call it, just like how you call a built-in function.
+
+> **Note**
+> To manage a function, right-click the function name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Edit**, **Compile**, **Debug**, **Run**, **Download**, **Delete**, and **Refresh**. **Edit** , **Compile** , and **Debug** are not supported in MySQL mode.
+> For more information, see [Manage functions](../3.web-odc-function-objects/3.web-odc-manage-functions.md).
+
+Syntax:
+
+```sql
+SELECT ([ [,...]])
+```
+
+
+
+Example:
+
+```sql
+SELECT function_emp(2);
+```
+
+
+
+* MySQL mode
+
+ 
+
+
+* Oracle mode
+
+ 
+
+
+ > **Notice**
+ > - In Oracle mode, if a user-defined function contains an OUT parameter, you must call the function by using the `CALL` statement.
+ > - A yellow icon in the function list indicates an error or alert.
+
+
+
+## Related topics
+
+[Create a table](../1.web-odc-table-objects/2.web-odc-create-a-table.md)
+[Create a view](../2.web-odc-view-objects/2.web-odc-create-a-view.md)
+[Create a stored procedure](../4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md)
+[Create a sequence](../5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+[Create a program package](../6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+[Create a trigger](../7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+[Create a type](../8.web-odc-type-objects/2.web-odc-create-a-type.md)
+[Create a synonym](../9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md)
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/3.web-odc-manage-functions.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/3.web-odc-manage-functions.md
new file mode 100644
index 00000000..aed70f26
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/3.web-odc-function-objects/3.web-odc-manage-functions.md
@@ -0,0 +1,91 @@
+Manage functions
+=====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Function** in the left-side navigation pane to get a list of functions.
+
+In the function list, you can view the **structure tree** of an object, or right-click the target object to perform some **management actions** on the object. You can also double-click the name of the target function to go to the **function management page**.
+
+Structure tree
+-----------------------
+
+You can click the expand icon before the name of the target function in the function list, and the structure tree of the function is displayed in a drop-down list, as shown in the following figure. The structure tree of a function can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section. In this section, you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------
+
+The names of function objects support ascending order by the head character by default in the function list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create function. |
+| Filter | Click this option to display valid/invalid functions. |
+| Batch Compile | Click this option to batch compile the function object. Including: compile all objects and compile invalid objects.  |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the function, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+After you right-click an item in the structure tree, a shortcut menu appears and displays some actions that you can take to manage the item. The following table describes the management actions in details:
+
+
+| Action |Description|
+|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View | Click this option to go to the function management page. On this page, you can view comprehensive information such as the basic information, parameters, and code of the function. |
+| Create | Click this option to go to the Create Function page, where you can create a function as prompted.|
+| Edit | Click this option to go to the function management page, which displays the statements that define the function and where you can edit the function. |
+| Compile | Click this option to compile the function. |
+| Debug | Click this option to go to the debugging page. On this page, you can debug the function.
**Note**
We recommend that you upgrade to OBServer V2.2.77 or later. This is because some versions of OBServer have been found with PL/SQL debugging issues, which may compromise the OBServer stability.
ODC V3.2.2 or earlier does not support the debugging feature when you connect ODC to the target instance by using OBProxy. To use the debugging feature, directly connect ODC to the target instance.
ODC V3.2.2 and later support PL/SQL debugging when you connect to OBServer by using OBProxy.
ODC V4.0.0 and later support setting the parameter value as DEFAULT, NULL or empty string.
|
+| Run | Click this option to execute the function. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the function object.|
+| Delete | Click this option to delete the function. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the function, so that the structure tree displays the latest information. |
+
+
+Function management page
+---------------------------------------------
+
+
+
+You can double-click the name of the target function in the function list to go to the function management page. The function management page displays the following information:
+
+
+|Section| Description |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This section displays the basic information about the function in fields such as **Function Name** , **Return Type** , and **Created By**. |
+| Parameter | This section displays the information about the parameters in fields such as **Name** , **Order** , **Mode** , **Data Type** , and **Default Value** . Click the  icon to refresh the parameters. |
+| DDL | This section displays the script that defines the function and provides the **Edit**, **Download**, **Find**, and **Refresh** icons.
**Note** Click the **Edit** icon to go to the PL object editing page.
|
+
+
+
+Function editing page
+------------------------------
+
+Right-click the target item in the function list. In the menu that appears, click **Edit** to go to the function editing page. In the code area of the editing page, the statements that define the function are displayed. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+|Button|Description|
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Confirm Modification | Click this button to apply the current modification. |
+| Compile | Click this button to compile the statements on the current page. |
+| Run | Click this button to execute the statements in the code area. |
+|Abort|Click this button to terminate the running statement.|
+| Debug | Click this button to go to the debugging page, where you can debug the PL object in the code area. |
+| Format | Click this button to apply the formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found.|
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All C** **aps** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+| IN Value Conversion | Click this button to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format.
Column values are separated with line breaks.
Row values are separated with spaces or tabs.
|
+|Snippets| Built-in syntax snippets and custom syntax snippets are provided to view and reference. See Snippet for details.|
+|Download|Download the SQL file for the function object.|
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/1.web-odc-stored-procedure-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/1.web-odc-stored-procedure-objects-overview.md
new file mode 100644
index 00000000..fa698575
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/1.web-odc-stored-procedure-objects-overview.md
@@ -0,0 +1,46 @@
+Overview
+=============================
+
+In a database system, a stored procedure is a collection of SQL statements for implementing a specific action. A stored procedure is stored in the database, and can be reused after it is compiled.
+
+Functions and stored procedures are similar in definition. Both are a collection of SQL statements. They have the following differences:
+
+* A function normally returns a value, whereas a stored procedure does not return values.
+
+
+
+* You can embed a function in an SQL statement. For example, you can call a function in a `SELECT` statement. However, usually a stored procedure is independently executed.
+
+
+
+* Functions have more limits than stored procedures. In general, stored procedures implement more complex features, whereas a function implements a more specific feature.
+
+
+
+
+
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Stored Procedure** in the left-side navigation pane to get a list of stored procedures. In the stored procedure list, you can double-click the name of a stored procedure to go to the stored procedure management page, where you can view the basic information, parameters, and data definition language (DDL) statements of the stored procedure.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.0.0 or a later version |
+| OceanBase Database in MySQL mode | V2.0.0 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on stored procedure objects in ODC.
+
+* [Create a stored procedure](../../../6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md)
+
+
+
+* [Manage stored procedures](../../../6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/3.web-odc-manage-stored-procedures.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md
new file mode 100644
index 00000000..f18bc7a3
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md
@@ -0,0 +1,222 @@
+# Create a stored procedure
+
+ODC supports visualized stored procedure creation. This topic describes how to create a stored procedure with ODC.
+
+## Overview
+
+A stored procedure is a collection of one or more statements. To perform a series of complex operations on a database, you can use a stored procedure to encapsulate these complex operations into a reusable code block in the database. It helps developers reduce their workload.
+
+In OceanBase Database, a stored procedure is a collection of SQL statements for implementing a specific feature. After you compile and store a stored procedure in the database, you can specify the stored procedure name and the required parameters to call this stored procedure for accelerated execution of the SQL statements.
+
+A stored procedure can contain parameters and return values.
+
+### Differences between a stored procedure and a function
+
+* The return value of a function is a specific result value, while the return value of a stored procedure only indicates whether the execution is successful.
+
+
+
+* You can call a function by using a `SELECT` statement. You can call a stored procedure by using a `CALL` statement.
+
+
+
+
+
+
+### Benefits of stored procedures
+
+* Improve the versatility and portability of the application: After you create a stored procedure, it can be repeatedly called by a program without rewriting the SQL statements of the procedure. In addition, stored procedures can be modified with no impact on the program source code, thereby improving the portability of the program.
+
+
+
+* Accelerate SQL execution: If an operation involves a large amount of SQL statements or repeated execution of the same SQL statements, you can compile the code into a stored procedure and execute the stored procedure, which is faster than separately executing the statements.
+
+
+
+* Alleviate the workload of the server: If one SQL statement is called at a time to perform operations on the database objects, a large number of SQL statements are transmitted. If an equivalent stored procedure, only the command for calling the procedure is sent, thereby reducing the network load.
+
+
+
+
+
+
+
+As shown in the preceding figure, you can create a stored procedure in the following five steps:
+
+1. Specify the name of the stored procedure.
+
+2. Specify parameters.
+
+3. Verify the parameters of the stored procedure.
+
+4. Edit the parameters of the stored procedure.
+
+5. Complete the stored procedure creation.
+
+## Procedure
+
+In the following example, a stored procedure named proc_total is created in the ODC console for the calculation of department budgets. The stored procedure contains two INT type input parameters budget_r and budget_s and calculates the sum of the two parameters. Procedure:
+
+### Step 1: Specify the name of the stored procedure.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Stored Procedure** in the left-side navigation pane to get a list of stored procedures. To create a stored procedure, click **+** in the upper-right corner of the Stored Procedure list or choose **Create** > **Stored Procedure** in the top navigation bar.
+
+In the **Create Stored Procedure** dialog box, enter a name for the stored procedure.
+
+
+
+### Step 2: Specify parameters.
+
+1. Parameters specify the information passed to a function when the function is called.
+
+ * In Oracle mode, specify the following fields: **Name**, **Mode**, **Type**, and **Default Value**.
+
+
+
+ * In MySQL mode, specify **Name**, **Mode**, **Type**, and **Length**.
+
+
+
+
+
+
+2. You can specify parameters by using one of the following three methods.
+
+
+
+| Method | Description |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| Use the quick access toolbar | In the quick access toolbar, you can add, delete, and move up and down parameters. |
+| Click the row number | - You can click a row number to select a row and display the quick access toolbar that allows you to delete the row or move the row up or down. - You can click a row number to select the row, and then drag the row to adjust its order. |
+| Right-click | - Copy a row or move one row down: Drag the pointer to select a row, right-click it, and then select Copy or Move Down from the context menu that appears. - Copy a cell: Select a cell, right-click it, and then select Copy from the context menu that appears. |
+
+ > **Note**
+ >
+ > After copying a row, you can select a row and paste the copied row data with the shortcut keys Command + V / Ctrl + V.
+
+3. You need to specify the mode for the parameters.
+
+ OceanBase Database in both MySQL mode and Oracle mode supports the following parameter modes: **IN**, **OUT**, and **INOUT**.
+
+ ```sql
+ CREATE PROCEDURE proc_name ([[IN |OUT |INOUT ] parameter_name parameter_type...])
+ ```
+
+
+ * Parameters
+
+
+
+| **Parameter** | Type |
+| ------------- | ------------------------------------------------------------ |
+| IN | Indicates an input parameter. When a stored procedure is called, the input parameter is passed to the stored procedure and used in the execution of the stored procedure. Usually, input parameters are only used to pass values in, and are not modified or returned in the call of a stored procedure. |
+| OUT | Indicates an output parameter. When a stored procedure is called, the value of an output parameter is ignored and an empty value is passed to the stored procedure. The value of the output parameter is modified during the execution of the stored procedure. After the execution is complete, the modified value is assigned to the output parameter. Usually, output parameters are used to obtain the execution results of a stored procedure. Output parameters can be used to modify and return values in the call of a stored procedure. |
+| INOUT | Indicates an inout parameter. An inout parameter is both an input parameter and an output parameter. |
+
+ * Parameter settings
+
+
+
+| Property | Required | Default | Mode |
+| ------------- | -------- | ------- | ------------ |
+| Name | Yes | Empty | Oracle/MySQL |
+| Mode | Yes | IN | Oracle/MySQL |
+| Type | Yes | VARCHAR | Oracle/MySQL |
+| Length | Yes | 45 | MySQL |
+| Default value | No | Empty | Oracle |
+
+
+
+
+
+
+
+### Step 3: Verify the parameters of the stored procedure.
+
+Click **OK** to go to the Create Stored Procedure page.
+
+### Step 4: Edit the stored procedure.
+
+
+
+Edit the statements on the Create Stored Procedure page.
+
+In addition, the toolbar on the editing page provides the following buttons.
+
+
+| Button | Description |
+|-------|----------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | Click this button and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+
+
+
+You can edit the SQL statements of the created stored procedure on the Create Stored Procedure page. Syntax:
+
+```sql
+CREATE PROCEDURE proc_name (
+ [proc_parameter[,...]])
+IS
+BEGIN
+proc_body:
+ Valid SQL routine statement
+END [end_label]
+```
+
+
+
+Parameters
+
+
+| Parameter | Description |
+|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| proc_name | The name of the stored procedure. By default, a stored procedure is created in the current database. To create a stored procedure in a specific database, add the database name as the prefix to the name of the stored procedure in the format of db_name.sp_name. **Notice** The name of a stored procedure must differ from that of any built-in MySQL function. Otherwise, an error may occur. |
+| [proc_parameter[,…] ] | The list of stored procedure parameters. A parameter is specified in the format of `[IN|OUT|INOUT] parameter_name parameter_type`. `parameter_name` specifies the parameter name and `parameter_type` specifies the parameter type, which can be any valid MySQL data type. If you need to specify multiple parameters, separate them with commas (,). A stored procedure can be created without a parameter. In this case, add a pair of parentheses after the name of the stored procedure. **Notice** The parameter names must differ from the column names in the data table. Otherwise, the SQL statements of the stored procedure may take a parameter name as a column name, which results in errors. |
+| proc_body | The body of the stored procedure, which contains the SQL statements to be executed when the stored procedure is called. The body begins with **BEGIN** and ends with **END**. If the body contains only one SQL statement, you can omit the BEGIN and END flags. |
+
+
+
+### Step 5: Complete the stored procedure creation.
+
+Click **Create** in the upper-right corner to create the stored procedure. After a stored procedure is created, you can use the `CALL` statement to call it, just like how you call a built-in function.
+
+
+
+> **Note**
+> To manage a stored procedure, right-click the stored procedure name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Edit**, **Run**, **Download**, **Delete**, and **Refresh**.
+
+For more information, see [Manage stored procedures](../4.web-odc-stored-procedure-objects/3.web-odc-manage-stored-procedures.md).
+
+Syntax:
+
+```sql
+CALL proc_name ([proc_parameter [,...]]);
+```
+
+
+
+Example:
+
+```sql
+CALL proc_total (30000, 20000);
+```
+
+
+
+
+
+## Related topics
+
+* [Create a table](../1.web-odc-table-objects/2.web-odc-create-a-table.md)
+* [Create a view](../2.web-odc-view-objects/2.web-odc-create-a-view.md)
+* [Create a function](../3.web-odc-function-objects/2.web-odc-create-a-function.md)
+* [Create a sequence](../5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+* [Create a program package](../6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+* [Create a trigger](../7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+* [Create a type](../8.web-odc-type-objects/2.web-odc-create-a-type.md)
+* [Create a synonym](../9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md)
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/3.web-odc-manage-stored-procedures.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/3.web-odc-manage-stored-procedures.md
new file mode 100644
index 00000000..f326a723
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/4.web-odc-stored-procedure-objects/3.web-odc-manage-stored-procedures.md
@@ -0,0 +1,113 @@
+Manage stored procedures
+=============================================
+
+
+
+Overview
+-----------------------------
+
+After you log on to OceanBase Developer Center (ODC), you can click the name of a connection on the homepage to go to the corresponding connection management page. In the left-side navigation pane, you can click **Stored Procedure** to get a list of stored procedures in the current database.
+
+In the stored procedure list, you can view the **Structure tree** of an object, or right-click the object to perform some **Management actions** on the object. You can also double-click the name of the stored procedure in the list to go to the **Stored procedure management page** .
+
+Structure tree
+-----------------------------------
+
+You can click the expand icon  before the name of the target stored procedure in the stored procedure list, and the structure tree of the stored procedure is displayed in a drop-down list, as shown in the following figure.
+
+The structure tree of a stored procedure can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section. In this section, you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------------------
+
+The names of stored procedure objects support ascending order by the head character by default in the stored procedure list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create stored procedure. |
+| Filter | Click this option to display valid/invalid stored procedures. |
+| Batch Compile | Click this option to batch compile the stored procedure object. Including: compile all objects and compile invalid objects.  |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the stored procedure, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Action | Description |
+|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View | Click this option to go to the Stored procedure management page, where you can view comprehensive information such as the basic information, parameters, and code of the stored procedure. |
+| Create | Click this option to go to the Create Stored Procedure page, where you can create a stored procedure as prompted. |
+| Edit | Click this option to go to the Stored procedure editing page, which displays the statements that define the stored procedure and where you can edit the stored procedure. |
+| Compile | Click this option to compile the stored procedure. |
+| Debug | Click this option to go to the **debugging page** , where you can debug the stored procedure.
**Note** ODC V4.0.0 and later support setting the parameter value as DEFAULT, NULL or empty string.
|
+| Run | Click this option to execute the stored procedure. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the stored procedure object. |
+| Delete | Click this option to delete the stored procedure. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the stored procedure so that the structure tree displays the latest information. **Note**
We recommend that you upgrade to OBServer V2.2.77 or later. This is because some versions of OBServer have been found with PL/SQL debugging issues, which may compromise the OBServer stability.
ODC V3.2.2 or earlier does not support the debugging feature when you connect ODC to the target instance by using OBProxy. To use the debugging feature, directly connect ODC to the target instance.
ODC V3.2.2 and later support PL/SQL debugging when you connect to OBServer by using OBProxy.
|
+
+
+
+Stored procedure management page
+-----------------------------------------------------
+
+
+
+You can double-click the name of a stored procedure in the function list to go to the stored procedure management page. The stored procedure management page displays the following information:
+
+
+| Section | Description |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This section displays the basic information about the stored procedure in fields such as **Stored Procedure Name** , **Created By** , **Creation At** , and **Last Modified At** . |
+| Parameter | This section displays the information about the parameters in fields such as **Name** , **Mode** , **Data Type** , **Length** , and **Default Value** .Click the  icon to refresh the parameters. |
+| DDL | This section displays the script that defines the stored procedure and provides the **Edit** , **Find** **,** **Format** , and **Refresh** buttons. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
+Stored procedure editing page
+--------------------------------------------------
+
+Right-click the target item in the stored procedure list. In the menu that appears, click **Edit** to go to the stored procedure editing page. In the code area of the editing page, the statements that define the stored procedure are displayed. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+| Button | Description |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Confirm modification | Click this button to apply the current modification. |
+| Compile | Click this button to compile the statements on the current page. **Note** * During the compilation, a code line is highlighted if it contains the name of an external object that cannot be referenced. * After the compilation, the **Compilation Result** tab displays the compilation status. If alerts exist, the alert details are displayed. |
+| Run | Click this button  to execute the statements in the code area. |
+| Debug | Click this button  to enter the debug mode, which allows you to edit the PL or SQL object in the code area. After the debugging, you can close the debugging window. |
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can add indents to or delete indents from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+| IN Value Conversion | Click this button to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format. * Column values are separated with line breaks. * Row values are separated with spaces or tabs. |
+
+
+
+Stored procedure output page
+-------------------------------------------------
+
+
+
+After the stored procedure is executed, you can view the information of execution results in the **Output** and **DBMS Output** tabs.
+
+
+| Tab | Description |
+|-------------|----------------------------------------------------------------------------------------------------------------------------|
+| Output | Displays the status, parameters, parameter types, parameter values, return type, and return value of the stored procedure. |
+| DBMS Output | Displays DBMS outputs of the stored procedure. |
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/1.web-odc-sequence-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/1.web-odc-sequence-objects-overview.md
new file mode 100644
index 00000000..2f1e12eb
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/1.web-odc-sequence-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+A sequence is a serial arrangement of numbers that automatically increase based on specific rules in the database. A sequence is generally used as the primary key or unique key of a table because it does not contain duplicate values.
+**Notice**
+
+
+
+After you connect OceanBase Developer Center (ODC) to OceanBase Database V2.1.0 or a later version in Oracle mode, you can create sequence objects in ODC. The MySQL mode does not support this feature.
+
+Log on to ODC and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click Sequence in the left-side navigation pane to get a list of sequences. You can double-click a sequence name in the sequence list to go to the sequence management page. On this page, you can view the basic information, parameters, and DDL statements of the sequence.
+
+This chapter describes in different topics the operations you can perform on sequence objects in ODC.
+
+* [Create a sequence](../../../6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+
+
+
+* [Manage sequences](../../../6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/3.web-odc-manage-sequence.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md
new file mode 100644
index 00000000..58a9eb7d
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md
@@ -0,0 +1,43 @@
+Create a sequence
+======================================
+
+
+
Note
+
ODC V3.2.2 and later versions support connection to OceanBase Community Edition. Due to the function differences of different OceanBase Database versions, the sequence function of ODC does not support the OceanBase Community Edition (The menu entry will be disabled).
+
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click **Sequence** in the left-side navigation pane to get a list of sequences. To create a sequence, click **+** in the upper-right corner of the sequence list or choose **Create \> Sequence** in the top navigation bar. Perform the following two steps to create a sequence:
+
+
+
+1. Set **Basic Info** : You need to specify **Sequence Name** and **User** . The User parameter is automatically specified based on the current account.
+
+
+
+2. Set columns. This step is optional. You need to specify the following parameters to set columns:
+
+
+
+ | Parameter | Description |
+ |-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | From | Specifies the initial value of the sequence, which must not be less than the value of **Minimum Value** . |
+ | Increment | Specifies the step size for the auto-increment of sequence values. The value can be a negative number. |
+ | Minimum Value | Specifies the minimum value that can be obtained by the sequence. The minimum value supported by the database is -1026. |
+ | Maximum Value | Specifies the maximum value that can be obtained by the sequence. The maximum value supported by the database is 1027. |
+ | Cache Settings | Specifies the cache size for the sequence. A proper cache size can improve the performance in obtaining sequence values. You can also set the value to **No Cache** . |
+ | Whether to Sort | Specifies whether the sequence obtains values in an ordered manner. The performance of the sequence in obtaining values in an ordered manner is inferior to that in an unordered manner. |
+ | Cyclic or Not | Specifies whether to start from the minimum value again when the sequence value reaches the maximum value. |
+
+
+
+3. Click **Next: Verify SQL Statement** to go to the Create Sequence page.
+
+ 
+
+
+4. An SQL script is pre-generated based on the information you specified. After the SQL script is verified, click **Create** in the upper-right corner to run the script and generate a sequence.
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/3.web-odc-manage-sequence.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/3.web-odc-manage-sequence.md
new file mode 100644
index 00000000..48e630c3
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/5.web-odc-sequence-objects/3.web-odc-manage-sequence.md
@@ -0,0 +1,42 @@
+Manage sequences
+=====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click **Sequence** in the left-side navigation pane to get a list of sequences.
+
+You can right-click the target object in the sequence list to perform some **Management actions** on the object. You can also double-click the target sequence in the sequence list to go to the **sequence Management** page.
+
+
+
+Management actions
+---------------------------
+
+The names of sequence objects support ascending example by head character by default in the sequence list.
+Right-click the target object in the sequence list. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Action | Description |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create Sequence | Click this option to go to the Create Sequence page, where you can create a sequence as prompted. |
+| View Sequence | Click this option to go to the **sequence management page** , where you can view comprehensive information such as the basic information, attributes, and DDL statements of the sequence. |
+| Modify | Click this option to go to the Attribute tab of the **sequence management page** to modify the information of the sequence. |
+| Delete | Click this option to delete the sequence. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the sequence object. |
+| Refresh | Click this option to refresh the list after you perform management actions on the sequence, so that the list displays the latest information. |
+
+
+
+Sequence management page
+---------------------------------
+
+[sequence2](https://obbusiness-private.oss-cn-shanghai.aliyuncs.com/doc/img/odc/340/%E7%AE%A1%E7%90%86%E5%BA%8F%E5%88%97-2-EN.png)
+You can view the following information on the Sequence Management page.
+
+
+| Section | Description |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This tab displays the basic information of a sequence in fields such as the **Sequence Name** and **Owner** . It also provides the **Edit** and **Refresh** icons.You can click **Edit** to modify the value of the following fields: **Increment** , **Minimum Value** , **Maximum Value** , **Cache Settings** , **Whether to Sort** , and **Cyclic or Not** . **Next Buffer Value** is the value of `last_number` in the sequence view. This value cannot be modified. |
+| DDL | This section displays the script that defines the sequence. Click the  icon to refresh the parameters. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/1.web-odc-package-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/1.web-odc-package-objects-overview.md
new file mode 100644
index 00000000..739b37c5
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/1.web-odc-package-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+A package is a combination of related PL programming elements, such as functions, procedures, variables, and cursors. Packages are similar to classes in Java. Variables in a package are similar to member variables in a class, and functions and procedures are similar to methods in a Java class. A package is used to group identical or similar objects, to facilitate maintenance and management and improve development efficiency and performance.
+**Notice**
+
+
+
+After you connect OceanBase Developer Center (ODC) to OceanBase Database V2.2.20 or a later version in Oracle mode, you can create package objects in ODC. The MySQL mode does not support this feature.
+
+Log on to ODC and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click package in the left-side navigation pane to get a list of packages. Double-click a package name in the package list to go to the package management page. On this page, you can view information such as the basic information and codes of the package header and package body.
+
+This chapter describes in different topics the operations you can perform on package objects in ODC.
+
+* [Create a package](../../../6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+
+
+
+* [Manage packages](../../../6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/3.web-odc-manage-program-packages.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/2.web-odc-create-a-program-package.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/2.web-odc-create-a-program-package.md
new file mode 100644
index 00000000..f6853d5f
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/2.web-odc-create-a-program-package.md
@@ -0,0 +1,27 @@
+Create a program package
+=============================================
+
+
+
Note
+
ODC V3.2.2 and later versions support connection to OceanBase Community Edition. Due to the function differences of different OceanBase Database versions, the program package function of ODC does not support the OceanBase Community Edition (The menu entry will be disabled).
+
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Program Package** in the left-side navigation pane to get a list of program packages. To create a program package, click **+** in the upper-right corner of the program package list or click **Create** in the navigation bar on the top of the page. To create a program package, you need to create the package header and the package body.
+
+Create the package header
+----------------------------------
+
+Click the **+** icon in the upper-right corner of the package list, or click **Create** in the navigation bar to go to the Create Program Package page, where you can create the package header.
+
+
+
+On the package creation page, specify the package name and click **Next: Verify SQL Statement** to go to the header definition page.
+
+ODC automatically generates the template statement, as shown in the following figure. In the navigation bar of the header definition page, ODC provides the **Format** button for you to standardize the statement format. After you complete the header definition statements, click **Create** in the upper-right corner to generate the header.
+
+
+
+Create the package body
+--------------------------------
+
+After you create the package header, the new program package appears in the program package list. Right-click the created program package and click **Create Package Body** to go to the package body definition page. This page is similar to the header definition page, as shown in the following figure. ODC automatically generates the template statement and provides the **Format** button for you to standardize the statement format. After you complete the package body definition statements, click **Create** in the upper-right corner to generate the package body.
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/3.web-odc-manage-program-packages.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/3.web-odc-manage-program-packages.md
new file mode 100644
index 00000000..8d61c4c1
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/6.web-odc-package-objects/3.web-odc-manage-program-packages.md
@@ -0,0 +1,106 @@
+Manage program packages
+============================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Program Package** in the left-side navigation pane to get a list of program package objects in the current database.
+
+In the program package list, you can view the **structure tree** of an object. You can also right-click the target object to perform some **management actions** on the object. You can also double-click the name of a program package to go to the program package page, which provides a **Package Header** tab and a **Package Body** tab.
+
+Structure tree
+-----------------------------------
+
+You can click the Expand icon before the name of the target program package in the program package list. Then, the structure tree of the program package displayed in a drop-down list, as shown in the following figure. The structure tree of a program package can have up to six levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section, where you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------------------
+
+The names of program package objects support ascending order by the head character by default in the program package list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create program package. |
+| Filter | Click this option to display valid/invalid program packages. |
+| Batch Compile | Click this option to batch compile the program package object. Including: compile all objects and compile invalid objects.  |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the program package, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Action | Description |
+|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create Program Package | Click this option to go to the Create Program Package page, where you can create a program package header as prompted. |
+| Create Package Body | Click this option to go to the package body definition page and create a program package body. |
+| Edit the package header and package body | Click this option to open both the package header editing and package body editing pages, where you can edit the package header and the package body. |
+| Delete | Click this option to delete the program package. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the program package, so that the structure tree displays the latest information. |
+| View | Click this option to go to the Package Header tab or the Package Body tab, where you can view comprehensive information such as the basic information and code of the program package. |
+| Edit | Click this option to go to the package header editing and package body editing pages, which display the package header and package body definition statements and where you can continue to edit the package header and the package body. |
+| Compile | Click this option to compile the program package. |
+| Debug | Click this option to go to the debugging page, where you can debug the program package. PL object debugging is supported only when OBServer V2.2.73 or a later version, or V3.0.00 or a later version is connected.
**Note** ODC V4.0.0 and later support setting the parameter value as DEFAULT, NULL or empty string.
|
+| Run | Click this option to run the stored procedure or function in a subprogram in the program package body. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the program package object. |
+| Delete | Click this option to delete the body of the program package. |
+
+
+
+Package Header tab
+---------------------------------------
+
+On the program package management page, click the **Package Header** tab. The following information is displayed:
+
+
+| Section | Description |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This section displays the basic information about the program package in fields such as **Package Name** , **Created By** , **Created At** , and **Last Modified At** . |
+| DDL | This section displays the code that defines the package header and provides the **Edit**, **Download**, **Find** , and **Refresh** buttons. You can click Edit to go to the package header editing page. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
+Package Body tab
+-------------------------------------
+
+On the program package management page, click the **Package Body** tab. The following information is displayed:
+
+
+| Section | Description |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This section displays the basic information about the package header in fields such as **Package Name** , **Created By** , **Created At** , and **Last Modified At** . |
+| DDL | This section displays the script that defines the function and provides the **Edit** , **Find** , and **Refresh** icons. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
+Package header/body editing page
+-----------------------------------------------------
+
+
+
+Right-click the target object in the program package list. In the shortcut menu that appears, click **Edit** to go to the program package editing page. The code area of the editing page displays statements that define the program package. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+| Button | Description |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Confirm Modification | Click this button to apply the current modification. |
+| Compile | Click this button to compile the statements on the current page. This button is available only on the package body editing page. |
+| Abort | Click this button to abort the statement that is being executed. |
+| Debug | Click this option to go to the debugging page, where you can debug the program package. PL object debugging is supported only when OBServer V2.2.70, V3.0.00, or a later version is connected. |
+| Format | Click this button to apply the formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three configurations: **All Uppercase** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding button to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | You can add indents to or delete indents from the statements that you selected. |
+| Comment | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+| IN Value Conversion | Click this button to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format. * Column values are separated with line breaks. * Row values are separated with spaces or tabs. |
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/1.web-odc-trigger-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/1.web-odc-trigger-objects-overview.md
new file mode 100644
index 00000000..bd26d28e
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/1.web-odc-trigger-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+Triggers are special stored procedures that are triggered by events but cannot be explicitly called. Therefore, triggers are used to monitor specific situations and trigger corresponding actions.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click Trigger in the left-side navigation pane to get a list of triggers. Click **+** in the upper-right corner of the list to go to the Create Trigger page. You can also double-click the name of a trigger in the list to go to the trigger management page. On this page, you can view the basic information and codes of the trigger.
+**Notice**
+
+
+
+After you connect ODC to OceanBase Database V2.2.20 or a later version in Oracle mode, you can create trigger objects in ODC. The MySQL mode does not support this feature.
+
+This chapter describes in different topics the operations you can perform on trigger objects in ODC.
+
+* [Create a trigger](../../../6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+
+
+
+* [Manage triggers](../../../6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/3.web-odc-manage-triggers.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md
new file mode 100644
index 00000000..f75a4d3d
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md
@@ -0,0 +1,119 @@
+Create a trigger
+=====================================
+
+
+
Note
+
ODC V3.2.2 and later versions support connection to OceanBase Community Edition. Due to the function differences of different OceanBase Database versions, the trigger function of ODC does not support the OceanBase Community Edition (The menu entry will be disabled).
+
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Trigger** in the left-side navigation pane to get a list of triggers. To create a trigger, click **+** in the upper-right corner of the trigger list or click **Create** in the navigation bar on the top of the page
+
+To create a trigger, perform the following three steps:
+
+1. Specify the basic information.
+
+
+
+2. Configure the advanced settings.
+
+
+
+3. Verify the SQL statement.
+
+
+
+
+
+
+
+
+Specify the basic information
+--------------------------------------------------
+
+This is Step 1. The **Basic Inf** **ormation** section contains the following parameters:
+
+* **Trigger Name** : specifies the name of the trigger.
+
+
+
+* **Base Object Mode** : specifies the schema where the object that the trigger works on is located.
+
+
+
+* **Base Object Type** : specifies the type of the object that the trigger works on. The current version supports only **TABLE** objects.
+
+
+
+* **Base Object Name** : specifies the name of the object that the trigger works on.
+
+
+
+* **Trigger Status** : specifies the state of the trigger. Valid value: **On** or **Disable** .
+
+
+
+
+
+
+Configure the advanced settings
+----------------------------------------------------
+
+This is Step 2. The **Advanced Settings** section contains the following parameters:
+
+* **Trigger Type** : specifies the type of the trigger. The current version supports only **SIMPLE** triggers.
+
+
+
+* **Trigger** : specifies whether the trigger is activated before or after the triggering event. Valid value: **BEFORE** or **AFTER** .
+
+
+
+* **Level** : specifies the level of the trigger. The current version supports only row-level triggers.
+
+
+
+* **Event** : specifies the type of operation that activates the trigger. Valid value: **INSERT** , **UPDATE** , or **DELETE** .
+
+
+
+* **Column (Optional)** : specifies the range that the event specified in **Event** applies to. This parameter is displayed when you set **Event** to **UPDATE** . The current version allows you to create only row-level triggers in a table. Therefore, the range here is the columns that the event applies to.
+
+
+
+* **Referencing Old** **(Optional)** : specifies an alias for the referenced object that corresponds to the value specified for `REFERENCEING OLD` in the trigger creation statement.
+
+
+
+* **Referencing New** **(Optional)** : specifies an alias for the referenced object that corresponds to the value specified for `REFERENCEING NEW` in the trigger creation statement.
+
+
+
+* **Clause Condition** **(Optional)** : specifies a logical expression for the trigger. After you specify a clause condition, the action specified by the trigger is executed only if the value of the expression is True.
+
+
+
+
+
+
+Verify the SQL statement
+---------------------------------------------
+
+After you specify all the information in the **Basic Info** and **Advanced Settings** sections, click **Next: Verify SQL Statement** to go to the statement editing page.
+
+The trigger definition statement is generated on the statement editing page based on the information that you specified in the **Basic Info** and **Advanced Settings** sections. You only need to complete the trigger body, which specifies the action to be executed. After you complete the trigger body, click the **Create** button in the upper-right corner of the page to complete the creation of the trigger.
+
+In addition, the toolbar on the editing page provides the following buttons:
+
+
+| Button | Description |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can specify search criteria in the search box to find specific content in the script and enter other content in the replacement box to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three configurations: **All Caps** , **All Lowercase** , and **Capitalize the first letter** . Click this button to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | The **Add Indents** and **Delete Indent** options are provided, to allow you to add indents to or delete indents from the selected statements in the script. |
+| Comment | The **Add Comments** and **Delete Comment** options are provided, which respectively allow you to convert the selected statements in the script to comments and convert comments to SQL statements. |
+| Previous | Click this button to go back to the **Create Trigger** page, where you can continue to edit or modify the parameters in the **Basic Information** and **Advanced Settings** sections. |
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/3.web-odc-manage-triggers.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/3.web-odc-manage-triggers.md
new file mode 100644
index 00000000..02629706
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/7.web-odc-trigger-objects/3.web-odc-manage-triggers.md
@@ -0,0 +1,81 @@
+Manage triggers
+====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Trigger** in the left-side navigation pane to get a list of triggers. The trigger list displays the trigger objects in the current database. You can right-click the target object to perform some management actions on the object. You can also double-click the name of the target trigger in the trigger list to go to the trigger management page.
+
+
+
+Management actions
+---------------------------------------
+
+The names of trigger objects support ascending order by the head character by default in the trigger list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create trigger. |
+| Filter | Click this option to display valid/invalid triggers. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the trigger, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the list. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Option | Description |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Trigger | Click this option to go to the trigger management page, where you can view the basic information, parameters, and code of the trigger. |
+| Create Trigger | Click this option to go to the Create Trigger page, where you can create a trigger as prompted. |
+| Edit | Click this option to go to the trigger editing page, which displays the statements that define the trigger and where you can continue to edit the trigger. |
+| Compile | Click this option to compile the trigger. |
+| Enable | Click this option to enable the trigger. |
+| Disable | Click this option to disable the trigger. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the trigger object. |
+| Delete | Click this option to delete the trigger. |
+| Refresh | Click this option to refresh the list after you perform management actions on the trigger, so that the list displays the latest information. |
+
+
+
+Trigger management page
+--------------------------------------------
+
+[trigger2](https://obbusiness-private.oss-cn-shanghai.aliyuncs.com/doc/img/odc/340/%E7%AE%A1%E7%90%86%E8%A7%A6%E5%8F%91%E5%99%A8-2-EN.png)
+
+You can double-click the name of the target trigger in the trigger list to go to the trigger management page, which provides the following three tabs:
+
+* **Basic Info** : displays information such as **Name** , **Owner** , and the **Trigger State** of the trigger.
+
+* **Base Object** : displays information such as **Name** , **Owner** , and **Type** of the base object of the trigger.
+
+* **DDL** : displays the script that defines the trigger and provides the **Edit** , **Find** , and **Refresh** buttons. You can click Edit to go to the trigger editing page.
+
+
+
+
+
+
+Trigger editing page
+-----------------------------------------
+
+To go to the trigger editing page, right-click the target trigger in the trigger list and choose **Edit** from the shortcut menu that appears. You can also click the **Edit** button on the DDL tab of the trigger management page to go to this page. The code area on the editing page displays the statements that define the trigger. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+| Button | Description |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can specify search criteria in the search box to find specific content in the script and enter other content in the replacement box to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three configurations: **All Caps** , **All Lowercase** , and **Capitalize the first letter** . Click this button to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | The **Add Indents** and **Delete Indent** options are provided, to allow you to add indents to or delete indents from the selected statements in the script. |
+| Comment | The **Add Comments** and **Delete Comment** options are provided, which respectively allow you to convert the selected statements in the script to comments and convert comments to SQL statements. |
+| Confirm Modification | Click this button to apply the current modification. |
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/1.web-odc-type-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/1.web-odc-type-objects-overview.md
new file mode 100644
index 00000000..a8c5d77c
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/1.web-odc-type-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+You can create custom object types in OceanBase Database. A type in OceanBase Database is similar to a class in Java. A class has attributes and methods, and methods in Java are equivalent to functions and stored procedures in OceanBase Database.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. Click Type in the left-side navigation pane to get a list of types. Click the **+** button in the upper-right corner of the list to go to the type creation page. You can double-click the name of a type in the list to go to the type management page, where you can view the basic information and code of the type.
+**Notice**
+
+
+
+After you connect ODC to OceanBase Database V2.2.20 or a later version in Oracle mode, you can create type objects in ODC. The MySQL mode does not support this feature.
+
+This chapter describes in different topics the operations you can perform on type objects in ODC.
+
+* [Create a type](../8.web-odc-type-objects/2.web-odc-create-a-type.md)
+
+
+
+* [Manage types](../8.web-odc-type-objects/3.web-odc-manage-types.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/2.web-odc-create-a-type.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/2.web-odc-create-a-type.md
new file mode 100644
index 00000000..6b6a75a2
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/2.web-odc-create-a-type.md
@@ -0,0 +1,164 @@
+# Create a type
+
+
+
Note
+
ODC V3.2.2 and later versions support connection to OceanBase Community Edition. Due to the function differences of different OceanBase Database versions, the type function of ODC does not support the OceanBase Community Edition (The menu entry will be disabled).
+
+
+ODC supports visualized type creation. This topic describes how to create a type with ODC.
+
+## Overview
+
+A database type object specifies the name, method, and other attributes of a type.
+
+OceanBase Developer Center (ODC) supports three types: object type, array type, and table type.
+
+* Object type: an abstract data type (ADT), which is an expression that encapsulates database objects, relationships between database objects, and basic operations on database objects.
+
+
+
+* Array type: a variable array, which is a collection similar to a nested table. A variable array is a collection of objects, where each object is of the same data type. The size of a variable array is determined when the array is created. The data type of a column in a table can be a variable-length multidimensional array. The type of the array can be any of the primitive types, the enumerated type, the composite type, or a user-defined type.
+
+
+
+* Table type: an independent nested table type. The created arrays are directly defined in the columns of the table.
+
+
+
+
+
+As shown in the preceding figure, you can create a type in the following four steps:.
+
+1. Specify the type name.
+2. Select a type object.
+3. Edit SQL statements.
+4. Complete the type creation.
+
+## Procedure
+
+In the following example, the ob_var object type is created in the ODC console. The type contains two VARCHAR type parameters: var and var1. Procedure:
+
+### Step 1: Specify the name of the type.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Type** in the left-side navigation pane to get a list of types. To create a type, click **+** in the upper-right corner of the type list or click **Create** in the top navigation bar.
+
+
+
+### Step 2: Select a type object.
+
+
+
+| Type | Description | Example |
+|------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| Object Type | The ADT. **Note** Only the object type can contain a subprogram. | ``` CREATE OR REPLACE TYPE ob_var AS OBJECT( var varchar2(10), var1 varchar(10) ); ``` |
+| Array Type | The independent variable array (VARRAY) type. | ``` CREATE OR REPLACE TYPE test AS VARRAY(20) of varchar2(20); ``` |
+| Table Type | The independent nested table type. | ```CREATE OR REPLACE TYPE test AS TABLE OF varchar2(100 BYTE);``` The `AS TABLE OF` clause allows you to create an array list\. |
+
+
+
+### Step 3: Edit SQL statements.
+
+
+
+After you specify the information in Step 2, click **Next: Verify SQL Statement** to go to the statement editing page. This page displays the corresponding type definition statements generated based on the information you specified in the **Create Type** dialog box. You must complete the statements based on your needs. After you complete the statements, click **Create** in the upper-right corner to complete the type creation.
+
+In addition, the toolbar on the editing page provides the following buttons.
+
+
+| Button | Description |
+|-------|----------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | Click this button and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+|IN Value Conversion|A format such as A B can be converted to ('A','B') format.|
+
+
+
+### Step 4: Complete the type creation.
+
+Click **Create** in the upper-right corner to create the type. After a user-defined type is created, you can use the `INSERT` key word to call it in a PL statement.
+
+
+
+> **Note**
+> To manage a type, right-click the type name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Delete**, **Download**, and **Refresh**.
+> For more information, see [Manage types](../8.web-odc-type-objects/3.web-odc-manage-type.md).
+
+Example:
+
+```sql
+-- Create a table.
+create table data_type (id number(10),name varchar2(50),age int,address varchar2(50),salary float);
+
+-- Insert table data.
+insert into data_type values(1,'baba',20,'hangzhou',3000.00);
+
+-- Create a type.
+create or replace type ob_var as object(
+ var varchar2(10),
+ var1 varchar(10)
+);
+
+delimiter /
+-- Create a stored procedure.
+create or replace procedure p_datatype is
+begin
+ declare
+ rec data_type%rowtype;
+ v_age rec.age%type;
+ var varchar2(50);
+ v_name var%type;
+ v_salary data_type.salary%type;
+
+-- Define a type.
+ type salary is table of number index by varchar2(20);
+ arr salary;
+ v_arr arr%type;
+
+ CURSOR c2 IS SELECT name, age FROM data_type;
+ c_row c2%rowtype;
+ v_rec c_row%type;
+
+ ob ob_var;
+ v_obj ob%type;
+
+ begin
+ v_name := 'ali ';
+ v_age := 30;
+ v_salary := 2000;
+ dbms_output.put_line('Referenced item: variable, record, and table column name: ' || v_name || ' * ' || v_age || ' * ' || v_salary);
+
+ v_arr('James') := 78000;
+ dbms_output.put_line('Referenced item: name of collection variable ' || v_arr.FIRST);
+
+ open c2;
+ fetch c2 into v_rec;
+ dbms_output.put_line('Referenced item: name of cursor variable: ' || v_rec.name || ' * ' || v_rec.age);
+ close c2;
+
+ v_obj:=ob_var('test','object');
+ dbms_output.put_line('Referenced item: name of object instance: ' || v_obj.var || ' * ' || v_obj.var1);
+ end;
+end;
+/
+
+begin
+ p_datatype;
+end;
+/
+```
+
+## Related topics
+
+* [Create a table](../1.web-odc-table-objects/2.web-odc-create-a-table.md)
+* [Create a view](../2.web-odc-view-objects/2.web-odc-create-a-view.md)
+* [Create a function](../3.web-odc-function-objects/2.web-odc-create-a-function.md)
+* [Create a stored procedure](../4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+* [Create a program package](../6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+* [Create a trigger](../7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+* [Create a synonym](../9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md)
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/3.web-odc-manage-type.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/3.web-odc-manage-type.md
new file mode 100644
index 00000000..cf98e8ac
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/8.web-odc-type-objects/3.web-odc-manage-type.md
@@ -0,0 +1,55 @@
+Manage types
+=================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Type** in the left-side navigation pane to get a list of types The type list displays the type objects in the current database. You can right-click the target object in the type list to perform some management actions on the object. You can also double-click the target type in the type list to go to the type management page.
+
+Structure tree
+-----------------------------------
+
+You can click the expand icon before the name of the target type in the type list, and the structure tree of the type is displayed in a drop-down list, as shown in the following figure. The structure tree of a type can have up to five levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section, where you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------------------
+
+The names of type objects support ascending order by the head character by default in the type list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create type. |
+| Filter | Click this option to display valid/invalid types. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the type, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object.
+
+The following table describes the management options.
+
+
+| Option | Description |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Type | Click this option to go to the type management page, where you can view the basic information and codes of the type. |
+| Create Type | Click this option to go to the **Create Type** page, where you can create a type as prompted. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the type object. |
+| Delete | Click this option to delete the type. |
+| Refresh | Click this option to refresh the list after you perform management actions on the type, so that the list displays the latest information. |
+
+
+Type management page
+-----------------------------------------
+
+You can double-click the name of the target type in the type list to go to the type management page. This page provides two tabs:
+
+* **Basic Info** : displays information such as **Name** , **Owner** , **Type** , **Creation Time** , and **Modified At** of the type object.
+
+* **DDL** : displays the script that defines the type and provides the **Download** , **Find**, **Refresh** and **Format** buttons. You can click Edit to go to the type editing page.
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/1.web-odc-synonym-objects-overview.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/1.web-odc-synonym-objects-overview.md
new file mode 100644
index 00000000..998f2073
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/1.web-odc-synonym-objects-overview.md
@@ -0,0 +1,29 @@
+Overview
+=============================
+
+A synonym is an alias of a database object. It is often used to simplify object access and improve the security of object access. Similar to views, synonyms do not consume storage space, and only the synonym definitions are stored in the data dictionary. Synonyms are divided into public synonyms and common synonyms.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click Synonym in the left-side navigation pane to get a list of synonyms. You can click **+** in the upper-right corner of the list to go to the synonym creation page. You can also double-click a synonym name in the list to go to the synonym management page. On this page, you can view the basic information and codes of the synonym.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.2.0 or a later version |
+| OceanBase Database in MySQL mode | V2.2.0 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on synonym objects in ODC.
+
+* [Create a synonym](../../../6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md)
+
+
+
+* [Manage synonyms](../../../6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/3.web-odc-manage-synonyms.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md
new file mode 100644
index 00000000..f809de21
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/2.web-odc-create-a-synonym.md
@@ -0,0 +1,144 @@
+# Create a synonym
+
+
+
Note
+
ODC V3.2.2 and later versions support connection to OceanBase Community Edition. Due to the function differences of different OceanBase Database versions, the synonym function of ODC does not support the OceanBase Community Edition (The menu entry will be disabled).
+
+
+ODC supports visualized synonym creation. This topic describes how to create a synonym with ODC.
+
+## Overview
+
+A synonym is an alias that you create for a database object of another user. You can perform operations on the object by querying and operating the synonym.
+
+Synonyms are similar to views. You can use synonyms to add, delete, modify, and query table data. You can define synonyms for most database objects in OceanBase Database, such as tables, views, materialized views, sequences, functions, stored procedures, packages, and synonyms.
+
+Synonyms extend the availability of database objects and allow them to be accessed by different database users with the required privileges. This design simplifies and secures access to database objects.
+
+### Synonym types
+
+OceanBase Database supports synonyms and public synonyms.
+
+* Synonyms: In general, a synonym created by a regular user is a private synonym. A private synonym can be accessed by the user who created it or other users who are granted the required privileges. To create a private synonym under the current user, you must have the CREATE SYNONYM privilege.
+
+
+
+* Public synonyms: A public synonym is created by a user who is granted the administrator role, such as the system user account, and can be accessed by all users.
+
+
+
+For more information, see [Synonyms](https://www.oceanbase.com/docs/enterprise/oceanbase-database/oceanbase-database/V3.2.2/synonyms).
+
+
+
+As shown in the preceding figure, you can create a synonym in the following eight steps:
+
+1. Specify the synonym name.
+2. Specify the object owner.
+3. Specify the object type.
+4. Specify the object name.
+5. Specify the synonym type.
+6. Verify the information about the synonym.
+7. Edit the synonym.
+8. Complete the synonym creation.
+
+## Procedure
+
+In this example, a synonym named syn_employee is created in the OceanBase Developer Center (ODC) console for an employee table in the SYS database. Procedure:
+
+### Step 1: Specify the name of the synonym.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Synonym** in the left-side navigation pane to get a list of synonyms and a list of public synonyms. To create a synonym, click **+** in the upper-right corner of the synonym list or choose **Create** > **Synonym** in the top navigation bar.
+
+In the **Create Synonym** dialog box, specify the name of the synonym.
+
+
+
+### Step 2: Specify the object owner.
+
+Specify the schema where the object is located.
+
+### Step 3: Specify the object type.
+
+Specify the object type. Valid values: Table and View.
+
+### Step 4: Specify the object name.
+
+Specify the name of the object for which the synonym is created.
+
+### Step 5: Specify the synonym type.
+
+Specify the synonym type. Valid values: Synonym and Public Synonym.
+
+### Step 6: Verify the information about the synonym.
+
+Click **Next: Verify SQL Statement** to go to the Create Synonym page.
+
+### Step 7: Edit the synonym.
+
+
+
+Edit the statement on the Create Synonym page.
+
+On the statement editing page, a synonym definition statement is generated based on the information specified in the **Create Synonym** dialog box. You can modify this statement. After you confirm the statement, click the **Create** button in the upper-right corner of the page to complete the synonym creation. A synonym cannot be modified after it is created.
+
+Before a synonym is created, you can edit the SQL statements of the synonym on the Create Synonym page. Syntax:
+
+```sql
+CREATE OR REPLACE SYNONYM syn_name FOR schema_name.object_name;
+```
+
+
+
+Parameters
+
+
+| Parameter | Description |
+|-------------|----------------------------------------------------|
+| OR REPLACE | Updates a synonym if the synonym already exists. |
+| syn_name | The name of the synonym. The name of a synonym must be unique in the specified schema. |
+| schema_name | The database schema to which the object belongs. |
+| object_name | The name of the object. |
+
+
+
+### Step 8: Complete the synonym creation.
+
+Click **Create**. After you create a synonym, you can use it in the same way as a built-in synonym.
+
+
+
+
+> **Note**
+> To manage a synonym, right-click the synonym name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Delete**, **Download**, and **Refresh**.
+
+For more information, see [Manage synonyms](../9.web-odc-synonym-objects/3.web-odc-manage-synonyms.md).
+
+Syntax:
+
+```sql
+SELECT * FROM syn_name ([syn_parameter[,...])
+```
+
+
+
+Example:
+
+```sql
+SELECT * FROM syn_employee;
+```
+
+
+
+
+
+## Related topics
+
+* [Create a table](../1.web-odc-table-objects/2.web-odc-create-a-table.md)
+* [Create a view](../2.web-odc-view-objects/2.web-odc-create-a-view.md)
+* [Create a function](../3.web-odc-function-objects/2.web-odc-create-a-function.md)
+* [Create a stored procedure](../4.web-odc-stored-procedure-objects/2.web-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.web-odc-sequence-objects/2.web-odc-create-a-sequence.md)
+* [Create a program package](../6.web-odc-package-objects/2.web-odc-create-a-program-package.md)
+* [Create a trigger](../7.web-odc-trigger-objects/2.web-odc-create-a-trigger.md)
+* [Create a type](../8.web-odc-type-objects/2.web-odc-create-a-type.md)
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/3.web-odc-manage-synonyms.md b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/3.web-odc-manage-synonyms.md
new file mode 100644
index 00000000..e0172eb7
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/11.web-odc-database-objects/9.web-odc-synonym-objects/3.web-odc-manage-synonyms.md
@@ -0,0 +1,57 @@
+Manage synonyms
+====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Synonym** in the left-side navigation pane to get a list of synonyms or a list of public synonyms. The synonym list displays the synonym objects in the current database. You can right-click the target object in the synonym list to perform some management actions on the object. You can also double-click the target synonym to go to the synonym management page.
+
+
+
+Management actions
+---------------------------------------
+
+The names of type objects support ascending order by the head character by default in the type list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create type. |
+| Filter | Click this option to display valid/invalid types. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the type, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object.
+
+The following table describes the management options.
+
+
+| Option | Description |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Type | Click this option to go to the type management page, where you can view the basic information and codes of the type. |
+| Create Type | Click this option to go to the **Create Type** page, where you can create a type as prompted. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the type object. |
+| Delete | Click this option to delete the type. |
+| Refresh | Click this option to refresh the list after you perform management actions on the type, so that the list displays the latest information. |
+
+
+
+
+Synonym management page
+--------------------------------------------
+
+Double-click the target synonym in the synonym list to go to the synonym management page, which provides the following two tabs:
+
+* **Basic Info** : displays synonym information such as **Name** , **Object** **Owner** , **Object Name** , **Creation Time** , and **Modified At** .
+
+* **DDL** : displays the script that defines the synonym. A synonym cannot be modified after it is created. You can **Download** and **Format** the synonym.
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/12.web-odc-help-center.md b/en-US/6.web-odc-user-guide/12.web-odc-help-center.md
new file mode 100644
index 00000000..fa108834
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/12.web-odc-help-center.md
@@ -0,0 +1,65 @@
+Help center
+================================
+
+
+
+Overview
+-----------------------------
+
+In the upper-right corner of the OceanBase Developer Center (ODC) homepage, you can click **Help** in the top navigation bar to view **New Features** and **View Help Documentation** . You can also obtain product information and email address on **About Developer Center** and **Feedback** tabs.
+
+
+
+Features
+-----------------------------
+
+When you access ODC for the first time, the **Features** dialog box automatically appears. It displays the features and core functions of the current version to help you quickly learn about ODC.
+
+After you close the dialog box, you can select **Features** in the **Help** menu to open it again.
+**Note**
+
+
+
+The Features dialog box may display different information based on user permissions.
+
+View help documentation
+--------------------------------------------
+
+To view the help documentation, click **Help** in the top navigation bar, and select **View Help Documentation** in the drop-down list.
+
+* If you are using Web ODC, the help documentation is displayed in HTML format on a new tab of the browser.
+
+
+
+* If you are using Client ODC, the help documentation is displayed in a browse window.
+
+
+
+
+
+
+To view the product documentation of the latest or history versions, you can go to **[OceanBase documentation center](https://www.oceanbase.com/en/docs/enterprise/oceanbase-developer-center/odc/V3.3.1/product-updates)**.
+
+About developer center
+-------------------------------------------
+
+Select **About Developer Center** in the drop-down list of **Help** to display a window. This window displays information such as the product name, version number, release date, official website URL, and copyright.
+
+
+
+Feedback
+-----------------------------
+
+To send your feedback, select **Feedback** in the drop-down list of **Help** .
+
+* If you are using Web ODC, you can see the email address of ODC Technical Support odcsupport@service.alipay.com in the dialog box that appears. You can send your suggestions to that email address.
+
+
+
+* If you are using Client ODC, the dialog box of Feedback also provides you the feature of downloading the feedback package. You can click **Generate information package** in the dialog box to pack frontend and backend logs, system environment, and other information into a feedback package.
+
+ 
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/2.web-odc-homepage.md b/en-US/6.web-odc-user-guide/2.web-odc-homepage.md
new file mode 100644
index 00000000..9f1d6912
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/2.web-odc-homepage.md
@@ -0,0 +1,114 @@
+# ODC homepage
+
+## Overview
+
+After you log on to OceanBase Developer Center (ODC), the ODC homepage automatically appears.
+
+On the ODC homepage, you can view the session history, [tasks](../6.web-odc-user-guide/9.web-odc-task-management/1.web-odc-task-management-overview.md), [operating records](../6.web-odc-user-guide/8.web-odc-view-operation-records.md), and [help documentation](../6.web-odc-user-guide/12.web-odc-help-center.md). You can also perform the following operations on the page: managing database connections, switching the language, setting personal information, changing the password, and logging off ODC.
+
+
+
+## Manage database connections
+
+The ODC homepage provides the **Private Connections** tab that shows the connections you have created, the **Public Connections** tab that shows the public connections that you have the permission to access, and the **All Connections** tab that shows all connections.
+
+* **All Connections**: On the **All Connections** tab, you can [create a private connection](../6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md), [apply for the permission on a public connection](9.web-odc-task-management/7.web-odc-apply-for-permissions-task.md), and search for, filter, sort, and refresh connections.
+
+* **Private Connections**: On the **Private Connections** tab, you can [create a private connection](3.web-odc-connect-database/1.web-odc-create-private-connection.md), [apply for the permission on a public connection](9.web-odc-task-management/7.web-odc-apply-for-permissions-task.md), and search for, filter, sort, and refresh connections. For more information, see [Manage private connections](3.web-odc-connect-database/2.web-odc-manage-connections.md).
+
+
+
+* **Public Connections**: On the **Public Connections** tab, you can [create a private connection](3.web-odc-connect-database/1.web-odc-create-private-connection.md), [apply for the permission on a public connection](9.web-odc-task-management/7.web-odc-apply-for-permissions-task.md), and search for, filter, sort, and refresh connections. For more information, see [Manage public connections](4.web-odc-public-resource-management/3.web-odc-public-resource-permission/1.web-odc-manage-public-connection.md).
+
+
+## View session history
+
+On the ODC homepage, you can click **History** in the left-side navigation pane to go to the session history page.
+
+
+
+The page shows a list that has the following columns.
+
+
+| Column | Description |
+|-----------|----------------------------------------------------|
+| Connection Name | The name of the connection you accessed. |
+| Database/Schema Name | The name of the database or schema that you accessed by using the connection. |
+| Recently Opened At | The time when you last accessed the connection. |
+| SQL/PL Window | The workspace window that you created when you accessed the connection. Move the pointer to a window name, and the script that you edited in the window is displayed. |
+| Actions | You can click **Open** to resume the connection in a new window. The corresponding workspace window and its content are also resumed. |
+
+
+> **Note**
+> By default, the historical records in the panel are stored for 48 hours. You can restore the content in an unsaved SQL window based on records in the panel.
+
+## Manage tasks
+
+On the ODC homepage, you can click **Task** in the left-side navigation pane to create and view tasks. For more information, see [Manage tasks](9.web-odc-task-management/1.web-odc-task-management-overview.md).
+
+Public resource console
+----------------------------
+
+As a database development platform for enterprises, ODC provides the public resource console for the ODC administrator to manage users, grant permissions, and allocate resources.
+> **Notice**
+> The **Public Resource Console** tab is displayed on the ODC homepage only when you log on as an administrator.
+
+On the ODC homepage, click **Console** in the left-side navigation pane to go to the public resource management page.
+
+The console allows you to manage users, roles, public connections, resource groups, automatic authorization rules, task processes, desensitization rules, and system settings.
+
+You can grant users the permissions to use public and private resources by roles. You can also use a resource group to batch grant or revoke the permissions for multiple public connections. For more information, see [Manage public resources](4.web-odc-public-resource-management/1.web-odc-public-resource-overview.md).
+
+Switch the theme
+-------------------------
+
+
+
+In the lower-left corner of the ODC homepage, choose **Me** > **Theme** to switch the theme to **Default Theme** or **Dark Theme**.
+
+Switch the language
+-------------------------
+
+In the lower-left corner of the ODC logon page or ODC homepage, choose **Me** > **Language** to view the display language of ODC. The default language is **Simplified Chinese**. You can click the language option to switch the display language. ODC supports **English**, **Simplified Chinese**, and **Traditional Chinese**.
+
+Personal settings
+-------------------------
+
+
+
+
+In the lower-left corner of the ODC homepage, choose **Me** > **Preferences**. The **Edit Personal Settings** panel appears.
+
+In the panel, you can globally modify the settings of the customizable features. You can also select a connection and configure these features in the connection. The configurations take effect on the current connection. The priority of personal settings is lower than that of settings you configured for each connection. In addition, the personal settings are persisted.
+
+Your modifications to fields in the **Edit Personal Settings** panel take global effect.
+
+
+| Parameter | Description |
+|-------------------|----------------------------------------------------------------------------------------------------|
+| Session Mode for SQL Window | The session mode of the SQL window. |
+| Delimiter Settings | The default delimiter for executing PL/SQL statements in the SQL window. Five types of delimiters are supported: semi-colons (**;**), slashes (**/**), double slashes (**//**), dollar signs (**$**), and double dollar signs (**$$**). |
+| Transaction Commit Mode in Oracle Mode | The default transaction commit mode in Oracle mode. Valid values: **Manual** and **Automatic** |
+| Transaction Commit Mode in MySQL Mode | The default transaction commit mode in MySQL mode. Valid values: **Manual** and **Automatic** |
+| Maximum Number of Rows in Result Set | The default number of rows returned for an SQL statement executed in the SQL window. |
+| Type of Statements Generated by Dragging and Dropping Object | The default type of statements generated when you drag and drop table or view objects. |
+
+
+
+Change the password
+-------------------------
+
+In the lower-left corner of the ODC homepage, choose **Me** > **Change Password**. The **Change Password** dialog box appears. For more information, see [Change the password](1.log-on-to-odc/2.change-password.md).
+
+Log off
+-------------------------
+
+In the lower-left corner of the ODC homepage, choose **Me** > **Log Off** to return to the ODC logon page.
+
+Help
+-------------------------
+
+In the lower-left corner of the ODC homepage, you can click **Help** to view tutorial documents of some common operations in ODC, new features in the current version, and FAQ.
+
+Click the document you want to view on this tab. The introduction and link to the document are displayed in a dialog box. You can click the link to view the document.
+
diff --git a/en-US/6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md b/en-US/6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md
new file mode 100644
index 00000000..da8f95d4
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/3.web-odc-connect-database/1.web-odc-create-private-connection.md
@@ -0,0 +1,71 @@
+Create a private connection
+================================================
+
+
+
+Overview
+-----------------------------
+
+After you log on to the homepage of OceanBase Developer Center (ODC), you can click **Create Connection** in the upper-right corner of the **Private Connection** tab to create a private connection.
+
+After you create the connection, you can view the saved database connection in the connection list on the ODC homepage.
+
+
+
+> **Notice**
+>
In ODC V2.3.0 and later versions, the root@sys user permissions are required to query views when you use the import and export features. Therefore, to use the import and export features, you need to set the root@sys user in the Advanced Configuration section during connection creation.
+>
The root@sys user permissions are also required to view the partition information. Therefore, to display the table partition information, you must also set the root@sys user in the Advanced Configuration section during connection creation.
+>
ODC V3.3.0 and later versions support independent sessions and shared sessions. In independent session mode, each SQL window corresponds to one database session, and all modifications affect only the current window. In shared session mode, all SQL windows share one database session, and modifications in any SQL window affect other SQL windows.
+>
In manual-commit mode, make sure to set the `ob_trx_idle_timeout` parameter to a value greater than or equal to the timeout value of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of the `ob_trx_idle_timeout` parameter, the connection is terminated. However, if the `ob_trx_idle_timeout` parameter is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you must set this parameter to a proper value.
+
+
+
+
+
+
+Procedure
+------------------------------
+
+Perform the following steps to create a connection:
+
+
+1. Log on to ODC and click **Create Connection** in the upper-right corner of the **Private Connection** tab.
+
+
+
+2. In the Create Connection panel, specify the fields described in the following table. If you have an OceanBase connection string, which follows the mysql -h **host name** -P **port number** -u **database username@tenant name** # **cluster name** -D **default database** -p ' **database password** ' format, you can obtain the information from the string. You can also paste the string in the field of Intelligent Parsing on the panel to automatically populate the corresponding fields.
+
+
+
+ | Field | Description |
+ |-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Intelligent Parsing | You can paste a connection string to the field. ODC automatically identifies the string and fills in the corresponding fields on the page. |
+ | Connection Type | Select **MySQL** or **Oracle** . Logical databases support only the MySQL mode. |
+ | 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 name** : the name of the cluster where the target database is located. This parameter is not required for logical databases. * **Rent name** : 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). |
+ | Database Account | * Database Username: an account under the tenant. In MySQL mode, this account must have access to the default database. * Database Password: the password of the account under the tenant. You can click **Test Connection** next to the password field to check the connection to the target database. * Save Database Password * If you disable this option, the database password for the connection is not saved. Each time you use or test the connection, you must enter the database password in the password dialog box. * If you enable this option, the database password for the connection is saved. You do not need to enter the database password each time you use the connection. **Note** * An error will be returned if the configurations such as the username, password, and network settings are invalid. * You can only connect to a database in the current tenant. Otherwise, a test failure error will be returned. |
+ | Default Database/schema | When you connect to a database in a MySQL tenant, you must specify the default database for the connection. You do not need to specify this field when you connect to a database in an Oracle tenant. **Note** If you leave this parameter unspecified, the information_schema database is connected by default. However, if the connection to the information_schema database fails, you need to specify a database that the current user has access permissions. |
+ | Query Tenant Views with sys Tenant Account | When Database Type is set to Physical Database, you can specify an account that has the privilege to query the SYS tenant view, and the password. This field is automatically populated when SYS is specified as the tenant in **Endpoint** . * **Account** : an account having the privilege to check the views under the SYS tenant. * **Password** : the password of the account. After you specify the account and password, click **Test Connection** next to the password field to verify whether the account information is valid. **Note** * In ODC V2.3.0 and later versions, to use the import and export features, you need to configure the root@sys account in the Advanced Configuration section during connection creation. * In ODC V2.4.1 and later versions, the dependency of the import and export features on the root@sys user is removed when you query views. If the root@sys account is not configured, some ODC objects such as stored procedures and functions do not support the export feature. If the root@sys account is configured, you can access the views under the SYS tenant to obtain the optimal data routing strategy, which can increase the export speed. |
+ |Enable SSL|Select whether to enable the SSL encrypted SSL link to ensure the safe transmission of data between the client and the server.
**Note**
Users created in non-encrypted mode (require none) (require none by default) can choose whether to enable SSL according to their needs. If **Enable SSL** is checked, an SSL connection will be created; if not checked, a normal connection will be created.
For users created through the SSL connection method (require ssl), you can create an SSL connection after checking **Enable SSL**; if you don’t check it, the connection will fail. Users created through require ssl do not need to upload a certificate but must check **Enable SSL**, otherwise the connection will fail. It is recommended to upload a certificate to verify the identity of both communication parties (not required):
Upload the CA certificate, and the client will verify the identity of the server;
Upload the client key and client certificate, and the server will verify the identity of the client.
Users created by x509 encryption (require x509) must **enable SSL** and upload the CA certificate, client key and client certificate, and the client and server will verify each other's identity; uncheck **Enable SSL ** Neither uploading the certificate nor uploading the certificate will successfully create the connection.
Before enabling SSL through ODC, you must confirm that SSL is enabled on the OBServer side; if you connect through OBProxy, you also need to ensure that OBProxy has enabled SSL. How to enable SSL on the server side, please refer to [OBServer Transmission Encryption](https://www.oceanbase.com/docs/enterprise-oceanbase-database-cn-10000000000944716) and [ApsaraDB for OceanBase SSL Link Encryption](https://help.aliyun.com/document_detail/254643.html).
|
+
+
+
+
+3. Click **Save** to save the current configuration in the ODC connection list, and enter the connection name. Next time you log on to ODC, you can directly select the connection from the list. The connection configuration does not necessarily need to pass the connection test when you save the configuration.
+
+
+ > **Notice**
+ >
+ > Before saving, you can click **Test Connection** to test the database connection. If the database user name and password are correct, it will prompt **Connected**.
+
+
+4. Click **Copy Connection String** in the lower part of the panel to copy the connection information being edited on the current panel as a connection string if necessary. This allows you to obtain the connection information with ease.
+
+
+
+5. Click **Cancel** if you do not need to save the current connection configuration. Then, a confirmation dialog box appears.
+
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/3.web-odc-connect-database/2.web-odc-manage-connections.md b/en-US/6.web-odc-user-guide/3.web-odc-connect-database/2.web-odc-manage-connections.md
new file mode 100644
index 00000000..f66250f6
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/3.web-odc-connect-database/2.web-odc-manage-connections.md
@@ -0,0 +1,155 @@
+Manage private connections
+===============================================
+
+
+
+Overview
+-----------------------------
+
+On the homepage of OceanBase Developer Center (ODC), you can view the connections you have created on the **Private Connection** tab and the public connections that you have the permission to access on the **Public Connection** tab. Connections are listed for easy viewing and management.
+
+
+View private connections
+---------------------------------------------
+
+The information of private connections is displayed in a list:
+
+* Use the search icon  above the list to find the target connection.
+
+
+
+* Use  to filter connections by type, authority, and label. Button The refresh button can refresh the list information.
+
+
+* Refresh the list information through .
+
+
+
+* Adjust the column width of the connection list.
+
+
+
+
+
+
+The following table describes columns of the list of private connections.
+
+
+| Column | Description |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Connection Name | The name of the connection and the host and port information. You can click the name of a connection to go to the corresponding connection management page. The icon before the connection name indicates the status of the connection. Green indicates valid, red indicates invalid, and gray indicates that the database password is not saved. |
+| Cluster | The cluster information. You can click the filter icon  to filter the cluster information. If you select **Empty** , you can filter connections that do not belong to any clusters. |
+| Tenant | The tenant information. You can click the filter icon  to filter the tenant information. If you select **Empty** , you can filter connections that do not belong to any tenants. |
+| Tag | The tag of the connection. You can create a tag and assign it to a connection. You can assign only one tag to each connection. |
+| Operation Time | The time when the connection was edited, or the time when the connection was created if the connection has not been edited. |
+| Actions | You can click the More icon to display actions you can take, namely **Open** , **Edit** , **Copy** , and **Delete** . |
+
+
+
+Set a tag
+------------------------------
+
+ODC allows you to create a tag and assign it to a connection. You can assign only one tag to each connection. Alternatively, you can move the pointer in the tag column of the row where the target connection is located in the connection list and click **Set Tag** . The drop-down list provides options for you to create, set, and manage tags.
+
+* Tag creation: You can create a tag by using the following two methods:
+
+ * Click **Set Tag** next to the **Connection Name** field in the **Create Connection** panel.
+
+
+
+ * Move the pointer in the tag column of the row where the target connection is located in the connection list, click **Set Tag** and click **Create Tag** in the drop-down list. On the **Tags** page, specify the name and color of the tag, and click the tick icon to complete the creation.
+
+
+
+
+
+
+* Tag setting: Select the target tag from the drop-down list that displays all the tags that you created, and modify related parameters to finish the setting.
+
+
+
+* Tag management: Click the settings icon in the upper-right corner of the drop-down list to go to the **Tags** page, In the Tags window, you can edit or delete created tags.
+
+
+
+
+
+
+Pin a private connection to the top
+--------------------------------------------------------
+
+By default, the connections in the connection list are sorted by their creation time, with the most recently created connection on top. The list does not support custom sorting, but you can pin frequently used connections to the top.
+
+You can click the flag  next to the name of a connection to pin the connection to the top. This turns the flag to yellow. You can click the flag again to unpin the connection from the top.
+
+Edit a private connection
+----------------------------------------------
+
+Click **Edit** in the **Actions** column of the target connection. The **Edit Connection** panel appears, which has the same structure as the **Create Connection** panel and displays the configuration information of the current connection. You can edit the information displayed in the **Edit Connection** panel.
+
+Before you change **Database Password** , you must first click **Change Password** next to the password box. To abort the current change, click **Cancel** next to the password box, and the input in the password box is restored to its original value.
+
+Copy a private connection
+----------------------------------------------
+
+Click **Copy** in the **Actions** column of the target connection. The **Create Connection** panel appears. The copied information is automatically filled in the panel. This allows you to quickly create a connection by modifying existing information.
+
+The copy feature allows you to easily create database connections having similar information.
+
+Delete a private connection
+------------------------------------------------
+
+To delete a connection, click **Delete** in the **Actions** column of the target connection.
+
+For example, when the connected database no longer exists or you do not need to access the connected database, you can directly delete the corresponding connection.
+
+Other operations
+-------------------------------------
+
+* In addition to the management actions that the **Private Connection** tab provides, after you go to the management page of a database connection, the homepage menu icon  in the top navigation bar further provides the following buttons:
+
+ * **Open Connection in New Window**: After you click a connection in the connection list that appears, ODC opens the connection in a new window.
+
+
+
+ * **Connections** : Click this button to open the ODC homepage in a new window. On the ODC homepage, you can view and manage the configuration information of all connections.
+
+
+
+ * **Reload** : Click this button to reload the current page.
+
+
+
+ * **Exit Connection** : Click this button to exit the current connection and go to the ODC homepage.
+
+
+
+
+
+
+ 
+
+* On the database connection page, the `@{database name}` information is included in the browser tab of Web ODC.
+ 
+
+* Information such as the connection name, schema (in Oracle mode), and database name (in MySQL mode) appears in the top navigation bar of the workspace.
+
+ * Move your pointer over the connection name in the top navigation bar. In the tooltip that appears, you can see information in the following fields: **Connection Mode** , **Host/Port** , **Cluster/Tenant** , and **Database Username**.
+ 
+
+
+
+ * Click the drop-down arrow next to the displayed schema name or database name. All the schemas and databases accessible to the current database user are included in the drop-down list that appears. You can switch to a target schema or database by clicking its name in the list.
+ 
+
+
+
+
+
+
+Related information
+----------------------------------------
+
+On the ODC homepage, you can click the Public Connection tab to view accessible public connections.
+
+For more information about how to create and manage a public connection, see [Manage public connections](../4.web-odc-public-resource-management/3.web-odc-public-resource-permission/1.web-odc-manage-public-connection.md).
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/1.web-odc-public-resource-overview.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/1.web-odc-public-resource-overview.md
new file mode 100644
index 00000000..3a513de4
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/1.web-odc-public-resource-overview.md
@@ -0,0 +1,51 @@
+Overview
+=============================
+
+As a database development platform for enterprises, OceanBase Developer Center (ODC) provides a public resource console to enable the ODC administrator to manage users, grant permissions, and allocate resources.
+
+The ODC administrator can see the **Public Resource Console** tab on the right side of the ODC homepage. The console enables the ODC administrator to manage users, roles, public connections, resource groups, and system settings.
+
+In addition to the built-in **system_admin** role, the ODC administrator must create other roles as needed and grant appropriate permissions to the roles on the Role Management page. After the roles are created, the administrator can batch create new ODC accounts on the User Management page for users in the organization and assign roles to the users for permission authorization and control.
+
+After ODC users obtain the database access information, they can create private connections in ODC. A private connection is accessible only to the user who creates it. For the security of the enterprise, database access information is not shared with all users. The administrator can create public connections in ODC, combine multiple public connections to create resource groups, and grant the access permission on public connections or resource groups to specific roles. As the public connections of a role are shared to all users with the role, the administrator does not need to share the access information with all users.
+
+The administrator can configure global settings on the System Settings page.
+
+This chapter describes the following features of the public resource console:
+
+* [Quick start](../4.web-odc-public-resource-management/2.web-odc-public-resource-quickstart.md)
+
+
+
+* [Manage users](3.web-odc-public-resource-permission/4.web-odc-manage-users.md)
+
+
+
+* [Manage roles](3.web-odc-public-resource-permission/3.web-odc-manage-roles.md)
+
+
+
+* [Manage public connections](3.web-odc-public-resource-permission/1.web-odc-manage-public-connection.md)
+
+
+
+* [Manage resource groups](3.web-odc-public-resource-permission/2.web-odc-manage-resource-groups.md)
+
+
+
+* [Task processes](../4.web-odc-public-resource-management/4.web-odc-task-process.md)
+
+
+
+* [Operation records](../4.web-odc-public-resource-management/5.web-odc-operating-records.md)
+
+
+* [Desensitization Rules](../4.web-odc-public-resource-management/6.web-odc-desensitization-rules.md)
+
+* [System settings](../4.web-odc-public-resource-management/6.web-odc-system-settings.md)
+
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/2.web-odc-public-resource-quickstart.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/2.web-odc-public-resource-quickstart.md
new file mode 100644
index 00000000..da195cd3
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/2.web-odc-public-resource-quickstart.md
@@ -0,0 +1,55 @@
+Quick start
+================================
+
+This document helps you quickly understand and use the public resource console.
+
+Overview
+-----------------------------
+
+On the ODC homepage, click the **Public Resource Console** tab to go to the **Public** **Resource Console** page. The **Quick Start** page is displayed by default. 
+
+Features of the public resource console
+------------------------------------------------------------
+
+The public resource console of ODC manages resource permissions of users and standardizes the process of configuring risk tasks to ensure the security of data resources.
+
+* Resource permission management: grants the read/write permissions on public connections and resource groups to users with different roles, to allocate and control database resource permissions.
+
+
+
+* Task process management: restricts the content of changes that you can initiate and provides different approval processes based on the task type, to ensure the security of database changes.
+
+
+
+* Security audit management: supports 14 types of audit events such as personal settings, password management, connection management, and database operations, to ensure security compliance and allow you to trace critical events and download audit reports.
+
+
+
+
+
+
+Resource Permission Management
+---------------------------------------------------
+
+1. Add public connection resources.
+
+ As the administrator, you can create or edit a public connection resource shared by multiple users.
+
+
+2. Configure a resource group.
+
+ A resource group consists of multiple public connections. It allows you to grant the permissions on multiple public connection resources to a role at a time.
+
+
+3. Manage the permissions of a role.
+
+ You can grant the permissions on multiple public connection resources and individual resources to the role.
+
+
+4. Create a user.
+
+ Specify the username and password of the user, and assign a role to the user to grant it the permissions on required connection resources.
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/1.web-odc-manage-public-connection.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/1.web-odc-manage-public-connection.md
new file mode 100644
index 00000000..e30b3071
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/1.web-odc-manage-public-connection.md
@@ -0,0 +1,119 @@
+# Manage public connections
+
+
+
+## Overview
+
+OceanBase Developer Center (ODC) allows you to create private and public connections. A private connection is created in ODC by a user who obtains the database access information that is not shared with all users for the sake of security. The administrator can create public connections in ODC, and combine multiple public connections to create resource groups. In this way, users in a resource group can use the public connections in this group.
+
+Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, choose **Resource Permissions** \> **Public Connection** to display the **Public Connections** page.
+
+
+
+## Create a public connection
+
+
+Click **Create Public Connection** in the upper-right corner of the **Public Connections** page. The **Create Public Connection** panel appears.
+
+Specify the following parameters in the **Create Public Connection** panel.
+
+
+| Field | Description |
+|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Connection Name | Specify the name of the connection. |
+| Resource Group | Click the field and select the resource group from the drop-down list. For more information about resource groups, see [Manage resource groups](../3.web-odc-public-resource-permission/2.web-odc-manage-resource-groups.md). |
+| Connection Status | By default, the connection status is **Enabled** . You can set it to **Disabled** . A disabled connection cannot be accessed. |
+| Intelligent Parsing | You can paste a connection string to the field. ODC automatically identifies the string and fills in the corresponding fields on the page. |
+| Connection Type | Select **MySQL** or **Oracle** . Logical databases support only the MySQL mode. |
+| 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 name** : the name of the cluster where the target database is located. This parameter is not required for logical databases. * **Rent name** : 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). |
+| Read/Write Account | Specify the **Database Username** and **Database Password** for accounts that have permissions to read and write the database. An ODC user with the read/write permissions can use this account to access OceanBase Database. You can click **Test Connection** next to the password field to test the connection to the target database. |
+| Read-only Account | Specify the **Database Username** and **Database Password** for accounts that have only permissions to read the database. An ODC user with the read-only permissions can use this account to access OceanBase Database. You can click **Test Connection** next to the password field to test the connection to the target database. |
+| Default Database | When you connect to a database in a MySQL tenant, you must specify the default database for the connection. You do not need to specify this field when you connect to a database in an Oracle tenant. |
+| Query Tenant Views with sys Tenant Account | When Database Type is set to Physical Database, you can specify an account that has the privilege to query the SYS tenant view, and the password. This field is automatically populated when SYS is specified as the tenant in **Endpoint**. * **Account**: an account having the permission to check the views under the SYS tenant. * **Password** : the password of the account. After you specify the account and password, click **Test Connection** next to the password field to verify whether the account information is valid. In ODC V2.3.0 and later versions, to use the import and export features and check the partition information, you need to configure the root@sys account by using this option. |
+|Enable SSL|Select whether to enable the SSL encrypted SSL link to ensure the safe transmission of data between the client and the server.
**Note**
Users created in non-encrypted mode (require none) (require none by default) can choose whether to enable SSL according to their needs. If **Enable SSL** is checked, an SSL connection will be created; if not checked, a normal connection will be created.
For users created through the SSL connection method (require ssl), you can create an SSL connection after checking **Enable SSL**; if you don’t check it, the connection will fail. Users created through require ssl do not need to upload a certificate but must check **Enable SSL**, otherwise the connection will fail. It is recommended to upload a certificate to verify the identity of both communication parties (not required):
Upload the CA certificate, and the client will verify the identity of the server;
Upload the client key and client certificate, and the server will verify the identity of the client.
Users created by x509 encryption (require x509) must **enable SSL** and upload the CA certificate, client key and client certificate, and the client and server will verify each other's identity; uncheck **Enable SSL ** Neither uploading the certificate nor uploading the certificate will successfully create the connection.
Before enabling SSL through ODC, you must confirm that SSL is enabled on the OBServer side; if you connect through OBProxy, you also need to ensure that OBProxy has enabled SSL. How to enable SSL on the server side, please refer to [OBServer Transmission Encryption](https://www.oceanbase.com/docs/enterprise-oceanbase-database-cn-10000000000944716) and [ApsaraDB for OceanBase SSL Link Encryption](https://help.aliyun.com/document_detail/254643.html).
|
+
+
+
+After you specify the preceding information, click **Create** in the lower-right corner of the panel. The connection is created.
+
+> **Notice**
+> After you click **Create** , a warning message will appear in the following cases:
+>
The read/write account is disconnected.
+>
The read/write account has insufficient permissions.
+>
The read-only account is disconnected.
+>
The read-only account has insufficient permissions.
+
+
+
+
+
+
+Manage public connections
+----------------------------------------------
+
+The information of public connections is displayed in a list on the **Public Connections** page. On this page, you can perform the following operations:
+
+* Use the search icon  above the list to find the target connection.
+
+
+* Use  to filter connections by type, authority, and label. Button The refresh button can refresh the list information.
+
+* Use  to filter connections by type, authority, and label. Button The refresh button can refresh the list information.
+
+* Refresh the list information through .
+
+
+* Adjust the column width of the connection list.
+
+
+
+
+
+
+### Public connection list
+
+The information of public connections is provided by columns, which are described in the following table. A filter is provided on top of some columns for you to filter connections.
+
+
+| Field | Description |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Connection ID | The sequence number of the connection. You can click **Connection ID** to sort the connection IDs in ascending or descending order. |
+| Connection Name | The name of the connection and the host and port information. You can click the name of a connection to go to the corresponding connection management page. The icon before the connection name indicates the status of the connection. Blue indicates valid, red indicates invalid, and gray indicates that the database password is not saved. You can click **Connection Name** to sort the connection names in ascending or descending order. |
+| Cluster | The cluster information. You can click the filter icon  to filter the cluster information. If you select **Empty** , you can filter connections that do not belong to any clusters. |
+| Tenants | The tenant information. You can click the filter icon  to filter the tenant information. If you select **Empty** , you can filter connections that do not belong to any tenants. |
+| Resource Group | The name of the resource group to which the connection belongs. You can click the filter icon  to filter the connections by the resource group. If you select **Empty** , you can filter connections that do not belong to any resource groups. |
+| Status | The current connection status. Valid values: **Enable/Disable** . You can click the filter icon  to filter the connections by status. |
+| Operation Time | The last time when the connection was edited, or the time when the connection was created if the connection has not been edited. |
+| Actions | The actions you can take. Valid values: **View** , **Edit** , **Copy** , and **Disable** / **Enable** . * View: View the configuration of the connection. * Edit: Modify the configuration of the connection. * Copy: Quickly modify and create another connection based on the configuration of the connection. * Disable/Enable: Directly change the connection status. |
+
+
+
+### View a public connection
+
+Click **View** in the **Actions** column. The **Public Connection Information** panel appears. You can see the **Connection Details** and **Related Users** tabs.
+
+
+| Field | Description |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Connection Details | * Connection information: displays the information you specified when you created the connection in fields such as **Region** , **Connection Mode** , **Connection Name** , **Resource Group** , **Endpoint** , database username for **Read/Write Account/Read-only Account**, and **Query sys Tenant Account** . * Operation information: displays information in fields such as **Created By** , **Created At** , and **Updated At** . * User deletion: You can click **Delete Public Connection** on the tab to delete the current connection. After the connection is deleted, it is inaccessible to users who are granted the permissions to access it. |
+| Related Users | Displays the information about the users who can access the current public connection in fields such as **Name** , **Role** , and **Permissions** . |
+| Edit | In the lower-right corner of the **Public Connection Information** panel, you can click **Edit** to go to the **Edit Public Connection** panel. |
+
+
+
+### Edit a public connection
+
+1. Click **Edit** in the **Actions** column of the public connection information list. The **Edit Public Connection** panel appears.
+
+
+
+2. The **Edit Public Connection** panel displays all the parameters you specified when you created the connection. **Database Type** , **Region** , and **Connection Mode** cannot be modified after the connection is created.
+
+
+
+3. After the editing is complete, click **Save** .
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/2.web-odc-manage-resource-groups.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/2.web-odc-manage-resource-groups.md
new file mode 100644
index 00000000..7c7d6758
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/2.web-odc-manage-resource-groups.md
@@ -0,0 +1,109 @@
+Manage resource groups
+===========================================
+
+
+
+Overview
+-----------------------------
+
+
+
+A resource group is an object that aggregates multiple public connections. It allows you to grant a role the permissions to access multiple public connections at a time.
+
+1. Log on to OceanBase Developer Center (ODC) and go to the **Public Resource Console** page. In the left-side navigation pane, choose **Resource Permissions**
+
+
+
+2. Click **Resource Group** to display the **Resource Group Management** page on the right.
+
+
+
+
+
+
+Create a resource group
+--------------------------------------------
+
+
+
+1. In the upper-right corner of the **Resource Group Management** page, click **Create Resource Group** .
+
+
+
+2. In the **Create Resource Group** panel that appears, specify the following parameters to create a resource group.
+
+
+
+ | Field | Description |
+ |------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Resource Group Name | The name of the resource group. |
+ | Resource Group Status | By default, the status of the resource group is **Enabled** . You can set it to **Disabled** as needed. The disabled resource group cannot be accessed. |
+ | Public Connection (optional) | Click **Add Connection** . In the drop-down list that appears, select an existing public resource group to grant the resource group the permission to access the public resource group. |
+ | Remarks (optional) | The description of the resource group. |
+
+
+
+3. After you specify the preceding information, click **Create** in the lower-right corner of the panel.
+
+
+
+
+
+
+Manage resource groups
+-------------------------------------------
+
+The information of resource groups is displayed in a list on the **Resource Group Management** page. On this page, you can perform the following operations:
+
+* Click the refresh icon to manually refresh the list.
+
+
+
+* Search for resource groups by using the search box in the upper-right corner of the list.
+
+
+
+
+
+
+### Resource group List
+
+The information of resource groups is provided by columns, which are described in the following table. A filter is provided on top of some columns for you to filter resource groups.
+
+
+| Field | Description |
+|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Resource Group ID | The sequence number of the resource group. You can click **Resource Group ID** to sort the resource group IDs in ascending or descending order. |
+| Resource Group Name | The name of the resource group. |
+| Connections | The number of public connections accessible to the current resource group. |
+| Status | The current status of the resource group. Valid values: **Enabled** and **Disabled** . You can click the filter icon  to filter the resource groups by status. |
+| Updated At | The last time when the resource group was edited, or the time when the resource group was created if the connection has not been edited. You can click **Updated At** to sort the resource groups by update time in ascending or descending order. |
+| Actions | The actions you can take. Valid values: **View** , **Edit** , and **Disable/Enable** . You can click **Disable/Enable** in the **Actions** column to change the status of the resource group. |
+
+
+
+### View a resource group
+
+1. Click **View** in the **Actions** column. In the **Resource Group Information** panel, you can see the **Resource Group Details** and **Related Users** tabs. The following table describes the information displayed on the tabs.
+
+
+
+ | Field | Description |
+ |------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Resource Group Details | * Resource group information: displays the information you specified when you created the resource group in fields such as **Resource Group Name** , **Remarks** , and **Public Connection** ( **Connection Name** and **Status** ). * Operation information: displays information in fields such as **Created By** , **Created At** , and **Updated At** . * User deletion: You can click **Delete Resource Group** on the tab to delete the current resource group. After the resource group is deleted, it is inaccessible to users who are granted the permissions to access it. |
+ | Related Users | Displays the information about the users who can access the current resource group in fields such as **Name** , **Role** , and **Permissions** . You can click the filter icon  to filter users by role and permission. |
+
+
+
+2. After you specify the preceding information, click **Edit** to go to the **Edit Resource Group** panel.
+
+
+
+
+
+
+### Edit a resource group
+
+Click **Edit** in the **Actions** column to go to the **Edit Resource Group** panel.
+
+The **Edit Resource Group** panel displays all the parameters you specified when you created the resource group. You can modify the parameters as needed.
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/3.web-odc-manage-roles.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/3.web-odc-manage-roles.md
new file mode 100644
index 00000000..b0e02f76
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/3.web-odc-manage-roles.md
@@ -0,0 +1,180 @@
+Manage roles
+=================================
+
+A role is an object that holds user permissions, and users of the same role have the same permissions. OceanBase Developer Center (ODC) allows you to grant permissions to customized roles and assign the roles to users.
+
+Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, choose **Resource Permissions** \> **Role** to display the **Role Management** page on the right.
+
+
+
+Built-in roles
+-----------------------------------
+
+ODC has a built-in administrator role **system_admin** that is automatically assigned to the administrator, whose username is **admin** . The administrator role has all system permissions and has access to all public and individual resources. You cannot edit, delete, or disable the administrator role.
+
+Create a role
+----------------------------------
+
+Click **Create Role** in the upper-right corner of the **Role Management** page. The **Create Role** panel appears.
+
+
+
+You can take the following steps to create a role:
+
+1. Specify **Role Name** .
+
+ The role name must be specified and cannot exceed 48 characters in length.
+
+
+2. Specify **Role Status** .
+
+ By default, the new role is created in the **Enabled** status. You can specify the **Disabled** status. The permissions for a disabled role do not take effect.
+
+
+3. Specify **Permission Type** .
+
+ Select at least one permission type for the role.
+
+ ODC allows you to select the **Public Resource Permissions** and **Individual Resource Permissions** types. After you select a permission type, the corresponding **Permission Settings** section appears below. When you create a role, you must specify and set at least one permission type for the role.
+
+
+4. Configure **Permission Settings** .
+
+ The following table shows options in each **Permission Type** tab in the **Permission Settings** section.
+
+
+ | Permission type | Description |
+ |--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Connection Access Permissions | - Resource Type: includes **Connection Access Permissions**, **Resource Management Permissions** and **System Permissions**.
Click the first field and select the resources as needed from the drop-down list.
Resource Name: Click the second field and select the resources as needed from the drop-down list. Depending on the selected resource type, the list displays the names of the resources that have been created in the current system.
Resource Permissions: Click the third field and select the public resource permission as needed from the drop-down list. Permissions for public resources include Read-only and Read/Write. For more information, see the Permission description section below. Click **Add Resource** to grant the role the permission for multiple public resources.
|
+ | Resource Management Permissions | Supports configuration of permissions for public connections, resource groups, roles, and users.|
+ |System Permissions|Supports the configuration of permissions for personal connections, task processes, desensitization rules, operation records, and system configuration.|
+
+
+
+5. Specify **Remarks (optional)** .
+
+ Enter the description in the field. The remarks are optional and cannot exceed 140 characters in length.
+
+
+6. Complete the creation.
+
+ Click **Create** in the lower-right corner of the panel to create the role.
+
+
+
+
+
+Permission description
+-------------------------------------------
+
+ODC supports **Public Resource Permissions** and **Individual Resource Permissions** . The types of the public resources are **Public Connection** and **Resource Group** . The following table shows the scope and description of supported permissions.
+
+
+| Permission scope | Read-only | Read/Write |
+|-------------------------------------------------|-----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SQL window | Support query statements in the SQL window | Support control statements in the SQL window Support query statements in the SQL window Support data change statements in the SQL window Support structure change statements in the SQL window |
+| Result set | View the result set Export the result set | View the result set Export the result set Modify the result set |
+| Anonymous block window | Support operations other than writing | Support all operations in the anonymous block window |
+| Command-line window | Support operations other than writing | Support all operations in the command-line window |
+| Data mocking | Not supported | Support all permissions for data mocking |
+| Asynchronous execution | Support operations other than writing | Support all permissions for asynchronous execution |
+| Import and export | Export | Support data import Export |
+| Session | View session properties View all sessions | View session properties Modify session properties View all sessions Modify the list of sessions |
+| Recycle bin | View objects in the recycle bin | View objects in the recycle bin Modify the recycle bin |
+| Table (non-SQL statement operations) | View the table definition View table data | View the table definition View table data Modify the table definition Modify table data Create a table Delete a table |
+| View (non-SQL statement operations) | View the view definition Check view data | View the view definition Check view data Create a view Delete a view |
+| Function (non-SQL statement operations) | View the function definition | View the function definition Modify the function definition Run a function Compile a function Debug a function Create a function Delete a function |
+| Stored procedure (non-SQL statement operations) | View the stored procedure definition | View the stored procedure definition Modify the stored procedure definition Run a stored procedure Compile a stored procedure Debug a stored procedure Create a stored procedure Delete a stored procedure |
+| Program package (non-SQL statement operations) | View the program package definition | View the program package definition Modify the program package definition Run a program package Compile a program package Debug a program package Create a program package Delete a program package |
+| Trigger (non-SQL statement operations) | View the trigger definition | View the trigger definition Modify the trigger definition Create a trigger Delete a trigger Compile a trigger |
+| Type (non-SQL statement operations) | View the type definition | View the type definition Modify the type definition Create a type Delete a type Compile a type |
+| Synonym (non-SQL statement operations) | View the synonym definition | View the synonym definition Create a synonym Delete a synonym |
+| Sequence (non-SQL statement operations) | View the sequence definition | View the sequence definition Modify the sequence definition Create a sequence Delete a sequence |
+
+
+
+Manage roles
+---------------------------------
+
+
+
+The information of roles is displayed in a list on the **Role Management** page, where you can perform the following operations:
+
+* Click the refresh icon to manually refresh the list.
+
+
+
+* Search for roles by using the search box in the upper-right corner of the list.
+
+
+
+* You can also view and manage the created roles by using the buttons provided in the Actions column.
+
+
+
+
+
+
+### Information of roles
+
+The information of roles is provided by columns, which are described in the following table. A filter is provided on top of some columns for you to filter roles.
+
+
+| Field | Description |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Role Name | The name of the role. |
+| Permission Type | The type of permissions granted to the role. |
+| Status | The role status. Valid values: **Enabled** and **Disabled** . |
+| Updated At | The time of the last update of the role information. |
+| Actions | The actions you can take. Valid values: **View** , **Edit** , and **Disable** / **Enable** . You can click **Disable** / **Enable** to change the role status. |
+
+
+
+### View a role
+
+
+
+1. Click **View** in the **Actions** column. In the **Role Information** panel, you can see the tabs **Role Details** and **Related Users.** The following table describes the information displayed on the tabs.
+
+
+
+ | Field | Description |
+ |---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Role Details |
Role creation information: displays the information that you specified when you created the role in fields such as **Role Name** , **Permission Type**, and **Remarks**.
Operation information: displays information in fields such as **Created By** , **Created At** , and **Updated At**.
Role deletion: You can click **Delete Role** in the lower part of the tab to delete the role. After the role is deleted, all data related to the role cannot be recovered, and the user permissions granted to the role are revoked. The user logon is not affected. |
+ | Related Users | The **Related Users** tab displays users that are granted the role. The user information is provided in the following columns: **Username** , **Roles** , and **Status** . |
+
+
+
+2. In the lower part of the **Role Information** panel, you can click **Edit** to go to the **Edit Role** panel, and
+
+
+
+3. click **Copy Role** to go to the **Create Role** panel. In the panel that appears, the information of the current role is automatically filled.
+
+
+
+
+
+
+
+
+### Edit a role
+
+
+1. Click **Edit** in the **Actions** column to go to the **Edit Role** panel.
+
+
+
+ | Field | Description |
+ |---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Role Details | Operation information: displays information in fields such as **Role Name** , **Role Status** , **Permission Type** , **Permission Settings** , and **Remarks** . |
+ | Related Users | The **Related Users** tab displays users that are granted the role. The user information is provided in the following columns: **Username** , **Roles** , and **Status** . * You can click **Remove** to remove the users granted the current role. * You can select new users in the **Add User** field and grant the role to the selected users. |
+
+
+
+2. In the **Edit Role** panel, you can click **Save** in the lower-right corner to save the editing results.
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/4.web-odc-manage-users.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/4.web-odc-manage-users.md
new file mode 100644
index 00000000..9d9fddd5
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/4.web-odc-manage-users.md
@@ -0,0 +1,143 @@
+Manage users
+=================================
+
+
+
+Overview
+-----------------------------
+
+
+
+You can create users and manage user permissions on the User Management page of OceanBase Developer Center (ODC).
+
+Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, choose **Resource Permissions** \> **User** to display the **User Management** page on the right.
+
+Built-in user
+----------------------------------
+
+ODC has a built-in account **admin** that is automatically assigned the administrator role **system_admin** . The administrator account has all system permissions and has access to all public resources. You cannot edit, delete, or disable the account.
+
+Create a user
+----------------------------------
+
+Click **Create User** in the upper-right corner of the **User Management** page. The **Create User** panel appears.
+
+
+
+You can take the following steps to create a user:
+
+1. Specify the **User Information** .
+
+ a. User information consists of the following three parts:
+
+ * **Account** : the account used to log on to ODC. You must specify a unique account of 4 to 48 characters in length using letters, digits, and special characters. Special characters are . _ + @ # $ %
+
+
+
+ * **Name** : the screen name to be displayed after the user logs on to ODC. The name must be specified and cannot exceed 110 characters in length.
+
+
+
+ * **Password** : the password used to log on to ODC. The password must be specified. It must be 8 to 32 characters in length and contain at least two digits, two uppercase letters, two lowercase letters, and two special characters. Special characters are . _ + @ # $ % You can also click **Random Password** next to the field to generate a random password.
+
+ > **Note**
+ > You will be prompted to change the user password when you log on to ODC as a new user or after the administrator changes the user password. This hardens password security and prevents password leakage.
+
+
+
+
+
+ b. ODC allows you to create multiple users at a time. Click **Add User** to specify the information for multiple users.
+
+
+
+
+
+
+1. Specify the **Account Status** .
+
+ By default, the new user is created in the **Enabled** status. You can manually disable it. A disabled account is unable to log on.
+
+
+2. Assign roles to the new user.
+
+ The roles are optional and you can assign multiple roles to a user. Click the field. In the drop-down list, select the roles that you want to assign to all users you just added. If no role is available, go to the Create Role page to create one.
+
+
+3. Specify the **Remarks** (optional).
+
+ Enter the description in the field. The remarks are optional and cannot exceed 140 characters in length.
+
+
+4. Submit user information.
+
+ In the lower-right corner of the panel, click **Create** to submit user information.
+
+
+5. Save user information.
+
+ In the **User Created** dialog box appears after you click Create, you can view the information of all users you just created. In the dialog box, you can click **Copy User Information** and **Download User Information** to save the information of multiple users in local storage.
+
+ This operation helps you quickly save user information when you create multiple users at a time.
+
+
+
+
+
+Manage users
+---------------------------------
+
+On the **User Management** page, you can view the information of all users, and search for specific users by using the search box in the upper-right corner of the page. You can also view and manage the created users by using the buttons provided in the Actions column of the User Management page.
+
+### Information of users
+
+The information of users is provided by columns, which are described in the following table. A filter is provided on top of columns for you to filter users.
+
+
+| Column | Description |
+|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Name | The name of the user. |
+| Account | The account of the user. |
+| Role | The role of the user. |
+| Status | The user status. Valid values: **Enabled** and **Disabled** . You can click the filter icon  to filter the users by status. |
+| Updated At | The time of the last update of the user information. You can click **Updated At** to sort the users by update time in ascending or descending order. |
+| Logon Time | The time of the last logon to ODC. You can click **Logon Time** to sort the users by logon time in ascending or descending order. |
+| Actions | The actions you can take. Valid values: **View** , **Edit** , and **Disable/Enable** . You can click **Disable/Enable** to change the user status. **Note** After you log on to ODC, you cannot edit or disable your account. |
+
+
+
+### View a user
+
+
+
+Click **View** in the **Actions** column. In the **User Information** panel, you can see the **User Details** and **Related Resources** tabs.
+
+
+| Field | Description |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Details |
User creation information: **Account** , **Name** , **Password** , **Role** , and **Remarks** that you specified when you created the user. The password is masked, and a **Reset Password** button is provided for you to change the logon password.
User deletion: You can click **Delete User** in the lower part of the tab to delete the user. After the user is deleted, the corresponding account cannot log on to ODC and its related data cannot be restored.
|
+| Related Resources | This tab displays the names of the public connections that are accessible to the current user, the resource groups to which the public connections belong, and the access permissions for the resource groups. |
+| Edit | In the **User Information** panel, click **Edit** to go to the **Edit User** panel. |
+
+
+
+### Edit a user
+
+
+
+Click **Edit** in the **Actions** column to go to the **Edit User** panel.
+
+In the **Edit User** panel, you can view all information specified when you create a user. After the user is created, the **Account** cannot be modified. However, you can modify the **Name** , **Account Status** , **Roles** , and **Remarks** , and can change the **Password** when viewing the user details page.
+
+### Disable a user
+
+Click **Disable** in the **Actions** column of the user information list. In the message that appears, click **Yes** .
+
+> **Note**
+>
Disabled users cannot log on.
+>
The account information of disabled users is retained. You can enable them again as needed.
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/5.web-odc-manage-automatic-authorization-rules.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/5.web-odc-manage-automatic-authorization-rules.md
new file mode 100644
index 00000000..7a16e4be
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/3.web-odc-public-resource-permission/5.web-odc-manage-automatic-authorization-rules.md
@@ -0,0 +1,115 @@
+# Automatic authorization rules
+
+
+
+## Background
+
+OceanBase Developer Center (ODC) allows system administrators to define automatic authorization rules. System administrators can create, modify, view, and disable automatic authorization rules in the public resource console.
+
+The automatic authorization feature automatically grants roles or permissions to users whose names, departments, or logon methods meet specific conditions when they are being created or log on for the first time, to avoid redundant authorization operations.
+
+This topic describes how to create and manage automatic authorization rules in the public resource console.
+
+
+
+## Create an automatic authorization rule
+
+### Procedure
+
+
+
+1. In the upper-right corner of the **Automatic Authorization Rules** page, click **Create** **Rule**. The **Create** **Rule** panel appears.
+
+
+2. Specify the following parameters in the **Create** **Rule** panel.
+
+ | Parameter | Description |
+ |--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Rule Name | The name of the rule, which must be unique. |
+ | Status | Select **Enabled** or **Disabled**. By default, the status of the rule is **Enabled**. You can set it to **Disabled** as needed. A disabled rule cannot be accessed. |
+ | Trigger Event | Select a trigger event. Only built-in events are available. Different events correspond to different trigger occasions. |
+ | Matching Condition (Optional) | Click **Add Condition** and specify the following four fields:
**Object**: stores the trigger condition and the information required for executing the action. It can be a complex nested object such as an array, a list, or a map, or a simple object such as a string or a number.
**Expression**: the index of the target in the object. Different types of objects use different indexing methods.
**Operation**: the supported operation, for example, "Contain", "Match", or "Equal".
**Value**: the target value.
**Note**If you do not specify the matching condition, the action is unconditionally executed when the selected event is triggered.
|
+ | Actions (Optional) | Select **Grant Role** and/or **Grant Connection Access** and specify the role name and/or public connection name.
**Note**If you do not specify the action, no action is executed regardless of whether the matching condition is met.
|
+ | Remarks (Optional) | The description of the rule. |
+
+3. After you specify the preceding parameters, click **Create** in the lower-right corner of the panel.
+
+### Example
+
+After you [integrate ODC in OAuth 2.0 and log on to ODC](https://www.oceanbase.com/docs/enterprise-odc-doc-cn-10000000001031888), assume that the OAuth 2.0 system returns the following data structure:
+
+```json
+{
+ "id": 1,
+ "name": "username",
+ "mail": "example@email.com",
+ "memberOf": {
+ "department": [
+ {
+ "name": "deptA",
+ "description": "this is a department"
+ },
+ {
+ "name": "deptB",
+ "description": "this is a department"
+ }
+ ],
+ "extra": "some other info"
+ }
+}
+```
+
+
+You can use different expressions to obtain corresponding values from the data structure. Example:
+
+| **Expression** | **Result** |
+|--------------------------------|----------------------|
+| id | 1 |
+| memberOf.department\[0\].name | deptA |
+| memberOf.department\[\*\].name | \["deptA", "deptB"\] |
+
+
+The administrator can configure an automatic authorization rule for a user when the user logs on to ODC from OAuth 2.0 for the first time. The example in the following figure shows how to create an authorization rule named `Grant system_admin` for `deptB`. If `memberOf.department` contains any element named `deptB`, the user is granted the `system_admin` role.
+
+
+
+## Manage automatic authorization rules
+
+
+
+On the **Automatic Authorization Rules** page, information is displayed in a list, and you can perform the following operations:
+
+* Click the refresh icon to manually refresh the list.
+
+* Search for rules by using the search box in the upper-right corner of the list.
+
+* Adjust the column width of the rule list.
+
+
+### Rule list
+
+The information of rules is provided by columns, which are described in the following table. A filter is provided in the **Status** column for you to filter rules by status.
+
+| Parameter | Description |
+|------|----------------------------------------------------------------------------------------|
+| Rule Name | The name of the rule. |
+| Created By | The name of the user who created the rule. You can click the search icon  to search for rules created by a specific user. |
+| Status | The current status of the rule. Valid values: **Enabled** and **Disabled**. You can click the filter icon  to filter rules by status. |
+| Created At | The last time when the rule was edited. You can sort rules in ascending or descending order of creation time. |
+| Actions | The actions you can take. Valid values: **View**, **Edit**, **Disable/Enable**, and **Delete**. |
+
+
+### View a rule
+
+Click **View** in the **Actions** column of a rule to go to the **Rule Information** panel. The following information is displayed in the panel.
+
+| Information | Description |
+|------|------------------------------------------------|
+| Rule information | Displays the information you specified when you created the rule, such as **Rule Name**, **Trigger Event**, **Matching Condition**, **Actions**, **Role**, and **Remarks**. |
+| Operation information | Displays fields such as **Created By** and **Created At**. |
+
+### Edit a rule
+
+Click **Edit** in the **Actions** column of a rule to go to the **Edit Rule** panel.
+
+The **Edit Rule** panel displays all the fields you specified when you created the rule. You can modify the fields as needed.
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md
new file mode 100644
index 00000000..d504f4c0
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md
@@ -0,0 +1,146 @@
+Task process management
+===========================
+
+
+Background
+-------------------------
+
+OceanBase Developer Center (ODC) allows users with special permissions, such as administrators with permissions on the public resource console, to define change task processes. Users with read-only permissions can initiate [change tasks](../../6.web-odc-user-guide/9.web-odc-task-management/1.web-odc-task-management-overview.md) based on the defined task processes.
+
+Users with this special permission can modify, view, and disable change task processes in the public resource console. Supported task processes include data import, export, and mocking, database changes, partition plan, shadow table and connection permission application.
+
+
+
+### **Create a task process**
+
+The following example shows how to create a connection permission application process in ODC. Procedure:
+
+1. Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, click **Task Process** to go to the task process management page.
+
+2. In the upper-right corner of the **Task Process Management** page, select the desired task process type and click **Create Process**. The **Create Task Process** panel is displayed.
+
+ 
+
+3. In the **Create Task Process** panel, specify the following parameters.
+ 
+
+ | **Item** | **Description** |
+ |---------|---------------------------------|
+ | Task Process Name | The name of the task process. |
+ | Task Type | The task type, which can be Import, Export, Mock Data, Database Change, and Apply for Permission. |
+ | Risk Levels | The risk levels. |
+ | Task Approval Process | The approval nodes for the task process. |
+ | Process Validity Period | The validity period for approval and execution. If the execution times out, the task will expire. |
+ | Task Process Status | You can enable or disable the task process. |
+ | Remarks (Optional) | You can enter the description of the task process. |
+
+4. Click **Next: Associate Connection** to select the associated public connections.
+
+5. Specify **Associate Connection**.
+
+ 
+
+ | **Item** | **Description** |
+ |---------|-------------------------------|
+ | Some Public Connections | When you select **Some Public Connections**, you need to add public connections or public connections in resource groups. |
+ | All Public Connections | Associates all public connections. |
+
+6. After you specify the preceding information, click **Create** in the lower-right corner of the panel.
+
+Manage task process
+---------------------------
+
+
+
+Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, click **Task Process** to go to the **Task Process Management** page.
+
+The information about task processes is displayed in a list on the **Task Process Management** page. On this page, you can perform the following operations:
+
+* Click the refresh icon to manually refresh the list.
+* In the upper-right corner of the list, click **Set Priority** to specify the execution sequence for the task process. The task process with the highest priority is associated when you create a task.
+* You can select the check box in front of one or more task process names and click the delete icon to delete the selected processes.
+
+### List of task processes
+
+The following table describes the columns in the list of task processes. Each column provides a filter for you to filter task processes.
+
+
+| Column | Description |
+|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Task Process Name | The name of the task process. |
+| Task Type | The type of the task. You can click the filter icon  to filter task processes by task type. The following task types are supported: **Import**, **Export**, **Mock Data**, and **Database Change**. |
+| Risk Levels | The specified risk levels. The default value is 1. You can modify the value as needed. The maximum value is 10. You can set the risk levels only for database changes. Other types of tasks can have only one risk level. |
+| Created By | The user who initiated the task. You can click the search icon  to search for the creator. |
+| Status | The status of the task process. You can click the filter icon  to filter task processes by status. |
+| Created At | The time of the last action on the task process. |
+| Actions | The actions you can take. Valid values: **View**, **Edit**, and **Disable**/**Enable**. - **View**: View the details of the current task process. - **Edit**: Modify the details of the current task process. - **Disable/Enable**: Change the status of the current task process. |
+
+
+
+### View a task process
+
+
+
+On the **Task Process Management** page, click **View** in the **Actions** column of the target task process. The **Task Process Details** panel appears.
+
+
+#### **View** process information
+
+
+| Item | Description |
+|----------|-------------------------------------------------------------------------------------------|
+| Basic information | Displays the basic information of the task process in the following fields: **Task Process Name**, **Task Type**, **Risk Levels**, **Approval Validity Period**, **Valid Waiting Period**, **Operation Validity Period**, and **Remarks**. |
+| Level | Displays the task level information, which contains the approval node, approval role, and authorized approvers. |
+| Created By | The user who initiated the task. |
+| Created At | The time when the task process was created. |
+
+
+
+#### **View associated connections**
+
+| Item | Description |
+|--------|--------------|
+| Associated Connection | The associated public connections. |
+| Task Process Status | The status of the task process. |
+
+
+
+### Edit a task process
+
+
+
+On the **Task Process Management** page, click **Edit** in the **Actions** column of the target task process. The **Edit Task Process** panel appears.
+
+
+| Item | Description |
+|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Task Process Name | The name of a task process can contain up to 110 characters in length, and can contain digits, letters, and Chinese characters. The names of task processes in the same organizational structure must be unique. |
+| Task Type | The task subtypes of database changes include **Update**, **Delete**, **Insert**, **Select**, **Create, Drop**, **Alter**, and **Other**. |
+| Risk Levels | The default value is 1. You can modify the value as needed. The maximum value is 10. We recommend that you set this parameter to 3. You can set the risk levels only for database changes. Other types of tasks can have only one risk level. |
+| Task Approval Process | - This section is displayed only for database change processes. By default, only one risk level is set. The risk level contains all task subtypes you selected, does not limit the volume of data to be changed, and requires approval by the system administrator by default. You can set custom approval nodes for the risk level by setting the number of nodes and the approval roles. - If multiple risk levels are set, you can set **Task Subcategory**, **Number of SQL Statements Supported**, and **Set Approval Node** for each risk level. |
+| Process Validity Period | You can specify the validity period of approval. If the specified period expires, the approval is automatically terminated. The default value is 24 hours (1 day). You can modify the value as needed. The maximum value is 240 hours (10 days). - **Approval Validity Period**: the validity period of approval. If this period times out, the task expires. - **Valid Waiting Period**: the waiting period before manual execution. If this period times out, the task expires. - **Operation Validity Period**: the validity period of execution. If this period times out, the task expires. |
+| Task Process Status | You can enable or disable the task process. You cannot initiate tasks of a disabled process. |
+| Remarks | The description of the task process. It can contain up to 200 characters in length. |
+
+### Set priorities of task processes
+
+1. On the **Task Process Management** page, click **Set Priority**.
+
+ 
+
+2. In the **Set Priority** panel, select the task type. In the list in the **Process Priority** section, drag and drop the icon in the **Sort** column of a task process to adjust the priority order of the task process.
+
+ > **Note**
+ > Tasks will be executed based on the priority order set by the administrator in the **Set Priority** panel in the public resource console.
+ > If a connection is associated with multiple processes, the tasks within the connection are matched against the processes by the priority order.
+
+ 
+
+3. After the adjustment, click **Save** in the lower-right corner of the panel. The priority is set.
+
+### Disable a task process
+
+Click **Disable** in the **Actions** column of the target task process. In the dialog box that appears, click **OK**.
+
+> **Note**
+> After a task process is disabled, it is no longer displayed on the task initiation page, which means that you cannot initiate tasks of it.
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/5.web-odc-operating-records.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/5.web-odc-operating-records.md
new file mode 100644
index 00000000..cf594a6e
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/5.web-odc-operating-records.md
@@ -0,0 +1,76 @@
+Manage operation records
+=============================================
+
+This topic describes how to manage the records of operation events in the public resource console of OceanBase Developer Center (ODC).
+
+Operation record list
+------------------------------------------
+
+**Note**
+
+
+
+Any user who owns the system_admin role can manage operation records.
+
+Operation records are retained permanently.
+
+Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, click **Operating Records** to display the **Operating Records** page on the right.
+
+
+
+* You can the refresh icon  to manually refresh the list.
+
+
+
+* You can select an option from **Performed At** to filter the operation records by time. Operation records in the last 7 days, 15 days, 30 days, 6 months, or a custom time range can be queried.
+
+
+
+
+
+
+The following table describes the basic information displayed in the operation record list.
+
+
+| Field | Description |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| No. | The sequence number of the operation record. |
+| Event Type | The type of the operation event. The following types of operation events are supported: personal settings, password management, connection management, script management, database operations, organization configuration, member management, resource group management, data mocking, database changes, import, export, and task processes. You can click the filter icon  to filter the operation records by event type. |
+| Event Operation | The operation performed in the event. You can click the filter icon  to filter the operation records by event operation. |
+| IP Address | The IP address. You can click the search icon to search for the IP address. |
+| Operator | The user who performed the operation. You can click the search icon to search for the operator. |
+| Performed At | The time when the operation was performed. By default, the operation records are sorted by execution time. The latest record is displayed at the top. You can click the icon  to sort the operation records in ascending or descending order. |
+| Execution Result | The execution result. Valid values: **Succeeded** and **Failed** . You can click the filter icon  to filter the operation records by execution result. |
+| Actions | Indicates the actions you can take. Currently, only **View** is available. |
+
+
+
+View operation records
+-------------------------------------------
+
+In the operation record list, click **View** in the **Actions** column. The **Record Details** panel appears.
+
+
+
+You can view the details of the record in the following columns: **Operation Type** , **Event Operation** , **Connection** , **IP Address** , **Operation Rules** , **Operator** , **Performed At** , and **Result** .
+
+Export operation records
+---------------------------------------------
+
+In the operation record list, click the export iconin the upper-right corner to display the **Export Operating Records** panel.
+
+The following table describes the basic information displayed in the Export Operating Records panel.
+
+
+
+
+| Field | Description |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Operation Time Range | Select the start date and the end date. |
+| Event Operation | Select an event operation. |
+| Connection | The name of the connection to which the operation belongs. Select the connection to which the operation belongs. All connections are selected by default. |
+| Operator | Select the user who performed the operation. |
+| Execution Result | Select the execution result. |
+| Export File Format | Select the file format for exported data. Valid values: Excel and CSV. |
+
+
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/6.web-odc-desensitization-rules.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/6.web-odc-desensitization-rules.md
new file mode 100644
index 00000000..7e5edc5a
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/6.web-odc-desensitization-rules.md
@@ -0,0 +1,126 @@
+Data desensitization management
+=======================
+
+**Prerequisites**
+-------------------------
+
+You are granted the administrator role of the public resource console.
+
+**Overview**
+-----------------------
+
+Data desensitization deforms sensitive privacy information, such as names, ID card numbers, mobile phone numbers, landline numbers, bank accounts, and email addresses. You can set data desensitization rules to protect sensitive privacy data.
+
+To better identify sensitive columns in databases, ODC supports configuring AI-powered sensitive column identification (optional feature that requires users to deploy AI models themselves). This feature can intelligently identify columns that may contain sensitive information in tables, providing reference for creating data desensitization rules. We recommend using the fylfy111/SensitiveColumn model from ModelScope community (based on qwen2.5 7B Instruct). When deploying, it is recommended to configure --max-model-len=4096 and requires at least a single RTX 3090 GPU server.
+
+This topic describes how to create and manage data desensitization rules in the public resource console in OceanBase Developer Center (ODC), and how to enable data desensitization strategies in ODC scenarios such as data export and result set export.
+
+
+
+**Create a desensitization rule**
+---------------------------
+
+
+
+1. Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, click **Data Desensitization** to go to the data desensitization management page.
+
+2. Click **Create Desensitization Rule** in the upper-right corner of the **Desensitization Rules** page. The **Create Desensitization Rule** panel appears.
+
+3. Specify the following parameters in the **Create Desensitization Rule** panel.
+
+ | **Parameter** | **Description** |
+ |---------|--------------------------------------------------|
+ | Rule Name | The name of the desensitization rule. The rule name can contain up to 48 characters in length and must be unique. |
+ | Rule Status | Select **Enable** or **Disable**. |
+ | Rule Details | Select a desensitization method so that sensitive characters are treated in the selected desensitization way. |
+ | Desensitization Effect | In the **Test Data** section, enter the data that you want to desensitize and click **Verify Desensitization** to view the desensitization result. |
+
+4. After you specify the preceding information, click **Create** in the lower-right corner of the panel.
+
+
+**Manage desensitization rules**
+---------------------------
+
+Created desensitization rules are displayed in a list on the **Desensitization Rules** page. On this page, you can perform the following operations:
+
+* Click the refresh icon to manually refresh the list.
+* Search for rules by using the search box in the upper-right corner of the list.
+
+
+### **Desensitization Rules**
+
+The following table describes the columns contained in the list of desensitization rules.
+
+| **Column** | **Description** |
+|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Rule Name | The name of the desensitization rule. |
+| Desensitization Method | The desensitization method selected when the rule was created. You can click the filter icon  to filter rules by desensitization method. |
+| Rule Status | The status of the desensitization rule. You can click the filter icon  to filter rules by status. |
+| Updated At | The latest time when the current desensitization rule was edited. |
+| Actions | The actions you can take. Valid values: **View**, **Edit**, **Disable**/**Enable**, and **Delete**. - **View**: View the details of the current desensitization rule. - **Edit**: Modify the details of the current desensitization rule. - **Disable**: Disable the current desensitization rule. - **Delete**: Delete the current desensitization rule. |
+
+### **View details of a desensitization rule**
+
+On the **Desensitization Rules** page, click **View** in the **Actions** column of the target rule. The **Details of Desensitization Rule** panel appears.
+
+
+
+| **Parameter** | **Description** |
+|---------|----------------------------------------------|
+| Rule Name | The name of the desensitization rule. |
+| Desensitization Details | The desensitization mode and segment selection. |
+| Desensitization Effect | In the **Test Data** section, enter the data that you want to desensitize and click **Verify Desensitization** to view the desensitization result. |
+| Created By | The user who created the current desensitization rule. |
+| Created At | The time when the current desensitization rule was created. |
+| Updated At | The latest time when the current desensitization rule was edited. |
+
+
+
+### **Edit a desensitization rule**
+
+
+
+1. On the **Desensitization Rules** page, click **Edit** in the **Actions** column of the target rule. The **Edit Desensitization Rule** panel appears.
+
+2. In the **Edit Desensitization Rule** panel, edit the rule parameters specified when the rule was created.
+
+3. After you edit the rule, click **Save**.
+
+**Scenarios**
+-------------------------
+
+ODC allows you to enable data desensitization strategies in operations such as data export and result set export.
+
+### **Scenario 1: Enable data desensitization when you export data**
+
+To enable a data desensitization strategy when you export the department table in ODC, perform the following steps:
+
+1. In the table list, right-click the department table and select **Export** from the context menu.
+
+ 
+
+2. In the **Single Table Export** panel, click **Data Desensitization** and select a data desensitization strategy.
+
+ 
+
+3. In the **Single Table Export** panel, select **Manage Desensitization Strategies** in the **Data Desensitization** drop-down list to add, sort, edit, or remove data desensitization strategies.
+
+ 
+
+### **Scenario 2: Enable data desensitization when you export a result set**
+
+For more information about data exporting scenarios, see [Batch export and import](../6.web-odc-use-tools/1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md). To enable a data desensitization strategy when you download the result set returned by querying the department table in ODC, perform the following steps:
+
+1. In the result set, click the **Download Data** icon. In the **Download Data** panel, click **Data Desensitization** and select a data desensitization strategy.
+
+ 
+
+2. In the **Download Data** panel, click **Manage Desensitization Strategies** in the **Data Desensitization** drop-down list to add, sort, edit, or remove data desensitization strategies.
+
+ 
+
+**Related topics**
+-------------------------
+
+* [Result tab](../5.web-odc-use-workspace/2.web-odc-sql-window.md)
+* [Batch export and import](../6.web-odc-use-tools/1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md)
diff --git a/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/7.web-odc-system-settings.md b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/7.web-odc-system-settings.md
new file mode 100644
index 00000000..6213b675
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/4.web-odc-public-resource-management/7.web-odc-system-settings.md
@@ -0,0 +1,22 @@
+System settings
+====================================
+
+The administrator can configure global settings on the System Settings page. Other users can configure the same features on the Personal Settings page. The personal settings have a higher priority than the system settings configured by the administrator.
+
+Log on to ODC as the administrator, and go to the **Public Resource Console** page. In the left-side navigation pane, click the **System Settings** to display the **System Settings** page on the right.
+
+
+
+In the upper-right corner of the page, click **Edit** to edit the settings. The following table shows settings that you can configure.
+
+
+| Field | Description |
+|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Session Mode for SQL Window | Set the session mode of the SQL window. |
+| Delimiter Settings | Set the default delimiter for executing PL statements in the SQL window. Five types of delimiters are supported: semi-colons ( **;** ), slashes ( **/** ), double slashes ( **//** ), dollar signs ( **$** ), and double dollar signs ( **$$** ). |
+| Transaction Commit Mode in Oracle Mode | Set the default transaction commit mode in Oracle mode. Valid values: Manual and Automatic. |
+| Transaction Commit Mode in MySQL Mode | Set the default transaction commit mode in MySQL mode. Valid values: Manual and Automatic. |
+| Maximum Number of Rows in Result Set | Set the default number of rows returned for an SQL statement executed in the SQL window. |
+| Type of Statements Generated by Dragging and Dropping Object | Set the default type of statements generated when you drag and drop table or view objects. |
+
+
diff --git a/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/1.web-odc-use-workspace-overview.md b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/1.web-odc-use-workspace-overview.md
new file mode 100644
index 00000000..d20d2607
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/1.web-odc-use-workspace-overview.md
@@ -0,0 +1,55 @@
+Overview
+=============================
+
+The workspace is the main feature module for you to develop databases in OceanBase Developer Center (ODC).
+
+After you enter the corresponding database connection, you can click **Workspace** in the navigation bar on the top of the page. The drop-down list provides the following features:
+
+* **SQL Window** : An SQL window is a working area for database developers to edit SQL and PL statements. ODC also provides the **Snippets** button in the SQL window.
+
+
+
+* **Anonymous Block Window** : An anonymous block window is a working area for database developers to edit anonymous block scripts. (The anonymous block window is available only in Oracle mode. )
+
+
+
+* **Command-line Window** : OceanBase command-line web OBweb is integrated in the form of a command-line window. It allows you to execute SQL or PL statements and view the execution results in real time.
+
+
+
+* **Stored Scripts** : Database developers can open scripts previously stored in ODC.
+
+
+
+* **Snippets** : View and reference built-in and custom code snippets
+
+
+
+> **Note**
+> Creating anonymous block windows is only supported in Oracle mode.
+
+
+This chapter describes these features in different topics.
+
+* [SQL window](../../6.web-odc-user-guide/5.web-odc-use-workspace/2.web-odc-sql-window.md)
+
+
+
+* [Anonymous block window](../../6.web-odc-user-guide/5.web-odc-use-workspace/3.web-odc-anonymous-block-window.md)
+
+
+
+* [Command-line window](../../6.web-odc-user-guide/5.web-odc-use-workspace/5.web-odc-command-line-window.md)
+
+
+
+* [Stored scripts](../../6.web-odc-user-guide/5.web-odc-use-workspace/5.web-odc-stored-scripts.md)
+
+
+
+* [Code snippets](../../6.web-odc-user-guide/5.web-odc-use-workspace/6.web-odc-snippet.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/2.web-odc-sql-window.md b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/2.web-odc-sql-window.md
new file mode 100644
index 00000000..1ffd98c5
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/2.web-odc-sql-window.md
@@ -0,0 +1,148 @@
+SQL window
+===========================
+
+
+
+Overview
+-----------------------
+
+On the Database Management page of OceanBase Developer Center (ODC), click **Workspace** in the top navigation bar and click **SQL Window** in the drop-down list that appears.
+
+The SQL window provides an SQL editing area for editing scripts, an execution record tab, and a result tab for displaying the execution results. The SQL window also supports executing PL/SQL statements.
+
+
+
+SQL editing area
+-----------------------------
+
+The SQL editing area provides many features for you.
+
+| Operation | Description |
+|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Auto-complete | The SQL editing area provides the auto-complete feature to improve your SQL statement editing efficiency. For example, when you edit SQL statements, the table name is auto-completed for cross-database queries. |
+| Intelligent identification of keywords and code | Database keywords are highlighted in different colors, and PL/SQL statements are identified. |
+| Right-click of object names in the `SELECT` statement | When you right-click the name of a table, view, or function in a `SELECT` statement, some common operations are displayed. When you place the pointer over the name of a table, the field information is displayed. |
+| Object drag-and-drop | You can directly drag objects from the object list into an SQL statement in the SQL editing area to fill in an object name in the statement. - After you drag a table or view and drop it into the SQL editing area, you can select the type of the SQL statement to be generated in the **Fast Generation** dialog box. You can click the username and select **Personal Settings** from the drop-down list, and set the default statement type in the **Type of Statements Generated by Dragging and Dropping Object** field of the **Edit Personal Settings** panel. - If you drag an object other than a table or view, the object name is directly dropped into the SQL editing area.  |
+| Shared and independent sessions | The SQL window of ODC supports **Shared Session** and **Independent Session** modes. - If you select **Shared Session**, you can open multiple SQL windows in the same connection, but cannot execute SQL statements in multiple windows in parallel. - If you select **Independent Session**, you can open multiple SQL windows in the same connection, and execute SQL statements in multiple windows in parallel. To open a new SQL window, click **+** next to the existing SQL window tab. By default, SQL windows are in Shared Session mode. You can click the username in the upper-right corner of the top navigation bar, select **Personal Settings** from the drop-down list, and set the session mode to **Independent Session** on the **Edit Personal Settings** panel.  |
+| Identification of special symbols | Special symbol abnormality can be identified in the editing area of the SQL window, where abnormal symbols are marked with yellow wavy underlines. |
+| Viewing the execution status | When you hover the pointer over an SQL window tab, the window name and execution status are displayed.  |
+
+
+> **Note**
+> In Oracle mode, the autocommit feature of ODC is set to OFF by default. You can change the transaction commit mode by modifying the value of the `autocommit` variable in the following two ways: click the **Settings** icon in the upper-right corner of the SQL window and modify the variable in the **Session Variables** dialog box, or click **Session** in the top navigation bar and modify the variable on the **Session Properties** page. Note that the settings in the **Set session variable** dialog box are valid only for the current SQL window. For more information, see [Manage sessions](../10.web-odc-session-management.md).
+> In manual-commit mode, make sure to set `ob_trx_idle_timeout` to a value greater than the timeout value of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of `ob_trx_idle_timeout`, the connection will be terminated. However, if the `ob_trx_idle_timeout` parameter is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you must set this parameter to a proper value.
+
+
+
+In addition to the preceding features, the toolbar of the editing area provides the following icons.
+
+| Icon | Description |
+|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Run | Click this icon to execute all the SQL statements in the current window. This icon is disabled if an SQL statement is being executed in another window of the same session. |
+| Run Current Statement | Click this icon to execute all the selected SQL statements or the SQL statement in the line where the pointer is located. This icon is disabled if an SQL statement is being executed in another window of the same session. |
+| Abort | Click this icon to abort the statement that is being executed. |
+| Execution Plan | Click this icon to view the execution plan for the SQL statement that you select or on which the pointer is located. This execution plan is estimated by the system before execution and is the result of the `EXPLAINPLAN` operation. Therefore, the execution data displayed may differ from the actual execution data. You can use this feature to evaluate SQL statements. Click **Execution Plan**. On the **Plan Details** tab, click **View Formatting Info** to switch to the formatted view. |
+| Find and Replace | Click this icon and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this icon to undo the last operation. |
+| Redo | Click this icon to reverse an **Undo** operation. |
+| Format | Click this icon to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| IN Value Conversion | Click this icon to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format. - Column values are separated with line breaks. - Row values are separated with spaces or tabs. |
+| Case Sensitivity | The system supports three configurations: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click this icon to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | You can add indents to or delete indents from the statements that you selected. |
+| Comment | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+| Save script | Click this icon to save the script in the current window. You can open a saved script when you enter the workspace again. You can view only the SQL scripts saved by yourself. The script names must be unique. After you open a stored script, you can continue to edit it. |
+| Settings | - **Delimiter**: Select the character that you want to use as the delimiter from the drop-down list. Five types of delimiters are supported: semi-colons (;), slashes (/), double slashes (//), dollar signs ($), and double dollar signs ($$). - **Query Result Limit**: Set the maximum number of lines that a query can return. Default value: 1000. - **Session Variables**: You can edit, refresh, and search for variables. |
+| Snippet | Click this icon to view and reference built-in and custom code snippets. For more information, see [Snippet](../../6.web-odc-user-guide/5.web-odc-use-workspace/6.web-odc-snippet.md). |
+| Commit | - By default, `autocommit` is set to `OFF` in Oracle mode. You need to click this icon to commit the current transaction. After you click this icon, a dialog box appears, indicating that the current connection uses a shared session and the commit will apply to all windows. Click **Yes** to commit the transaction. - In MySQL mode, `autocommit` is set to `ON` by default, and this icon is not displayed. This icon is disabled if an SQL statement is being executed in another window of the same session. **Note** You can change the value of the `autocommit` variable in the following two ways: click the **Settings** icon in the upper-right corner of the SQL window and set the variable in the **Session Variables** dialog box, or click **Sessions** in the top navigation bar and set the variable on the **Session Properties** page. |
+| Rollback | - In Oracle mode, if the `autocommit` variable in the **Session Variables** dialog box is set to `OFF`, click this icon to roll back the current transaction. After you click this icon, a dialog box appears, indicating that the current connection uses a shared session and the rollback will apply to all windows. Click **Yes** to apply the rollback. - In MySQL mode, the `autocommit` variable in the **Session Variables** dialog box is set to `ON`, and this icon is not displayed. This icon is disabled if an SQL statement is being executed in another window of the same session. |
+
+
+
+Execute PL/SQL statements
+-----------------------------
+
+You can edit a PL/SQL statement in the SQL window. Note that you must end the PL/SQL statement with the specified delimiter.
+
+At present, you can use the following methods to specify a delimiter in ODC:
+
+* Click **Settings** in the toolbar of the SQL editing area. In the window that appears, select the delimiter as needed in the **Delimiter** field.
+
+
+
+* On the **Personal Settings** page, select a required delimiter in **Delimiter Settings**.
+
+
+
+* The compilation error information displayed includes the PL/SQL row ID and the position at which the error occurred.
+
+* Right-click the PL object in the left navigation bar and select **Run**, which supports setting the parameter value as DEFAULT, NULL or empty string.
+
+ > **Notice**
+ >
In ODC V2.4.1 and later, you can use the `DELIMITER` statement in the editing area to define a delimiter. In **Settings**, the **Delimiter** field displays the delimiter that you specified.
+ >
You can use slashes (/) to separate PL/SQL statements.
+
+After you execute a PL/SQL statement in the SQL window, the result tab displays the database management system (DBMS) output.
+
+
+
+Execution Records tab
+---------------------------
+
+
+
+On the **Execution Records** tab, you can view the history of SQL statements executed in the current connection. You can view the information in several columns, such as **Status**, **Time**, **SQL Statement**, **Results**, **Trace ID**, **Time Spent**, and **Execution Details**. The execution details constitute the execution plan.
+
+| Column | Description |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Check box | You can select the check box in front of one or more records and then click **Delete** in the upper-right corner of the list to delete the selected records. |
+| TRACE ID | The ID of the execution record. **Notice** If **TRACE ID** is empty, make sure that the `enable_sql_audit` and `ob_enable_trace_log` parameters are set to `ON` when the statement is executed. Procedure: 1. Choose **Sessions** > **Session Properties** > **Session Variables** and search for the `enable_sql_audit` and `ob_enable_trace_log` parameters. 2. Click the **Edit** icon on the **Session Variables** tab. In the **Edit Variable** dialog box, change **OFF** to **ON** and click **OK**. 3. Execute the following statement to enable the system parameter: ```sql obclient> alter system set enable_sql_audit='True'; Query OK, 0 rows affected (0.06 sec)``` |
+| DB Time | You can hover the pointer over the icon next to a value in the **DB Time** column. In the prompt box that appears, you can view the total execution duration of the SQL statement and verify whether the duration of each phase adds up to the total execution duration. |
+| Execution Details | By default, the execution plan is displayed in text. In the **Execution Details** column, click **View**. The **Execution Details** page displays the basic information, time spent, I/O statistics, executed SQL statements, plan statistics, and outlines. |
+
+
+
+Logs tab
+-------------------------
+
+You can view the execution records of the current SQL window in the Logs tab.
+
+
+
+Result tab
+-------------------------
+
+
+
+You can view the execution result of the current SQL statement on the **Result** tab. The result set in the Result tab can be used in the following interactive operations to facilitate daily development work.
+
+| Operation | Description |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Select required data | You can select the required data of a result set and copy the data to an external file by using hotkeys. You can also click a field name or row ID to select an entire row or column. You can also click **Export** in the toolbar to export data of a result set to a local file. |
+| Select rows and columns |
You can select consecutive rows or columns while holding the **Shift** key.
You can select inconsecutive rows or columns while holding the **Ctrl** or **Command** key.
|
+| Right-click a cell | You can right-click a cell and select **Copy** or **Export to Clipboard** to directly export the data into an external file. |
+| Right-click a row ID | You can right-click a row ID and select **Copy Row**, **Freeze this row**, or **Unlock all frozen rows**.
**Copy Row**: Click this option to copy the selected row.
**Freeze this row**: Click this option to freeze the selected row and pin it to the top. You can freeze multiple rows. The rows under the table header and frozen rows can be vertically scrolled.
**Unlock all frozen rows**: Click this option to unfreeze all frozen rows.
|
+| Zoom in | If the data in a cell is too long and cannot be fully displayed, you can hover the pointer over the cell and click the zoom-in icon  at the right end of the cell. In the window that appears, view the data in full.
**Note** LOBs are displayed in text by default. You can convert an LOB into the hexadecimal format and download the LOB to a local device. |
+| View BLOBs |
In Oracle mode, you can directly edit text data of the CLOB, BLOB, or RAW type, edit hexadecimal data, and upload files that are not greater than 200 KB in size.
In MySQL mode, you can directly edit text data of the XLOB type such as BLOB, MEDIUMBLOB, or TINYBLOB, edit hexadecimal data, and upload files.
|
+| Right-click the tab name of a result tab | For example, you can right-click the tab name of the **Result 1** tab and click **Pin** in the context menu to pin the tab, so that it remains displayed. In this way, when you execute a new query, a new result tab appears but does not overwrite the pinned result tab. This allows you to compare the query results. Click **Unpin** to unpin a result tab. |
+| Filter, sort, and search for data | Each field name in the result set is provided with a filter icon, a sort icon, and a search icon. You can use them to filter, sort, and search for data in a single column. |
+| Drag the column name | You can adjust the order of fields by dragging column names in a result set. |
+| Adjust the column width | You can adjust the column width by dragging the column edge. |
+
+
+
+The navigation bar of the **Result** tab also provides the following tools.
+
+| Tool | Description |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Column Mode | Click this icon to display the selected data row in the form of a table. On the **Column Mode** tab, you can switch to the previous or next row. ****The column mode makes it easier to view data in a row that has many columns. Procedure: 1. Select the data that you want to view and click **Column Mode** . 2. On the **Column Mode** tab, click the left or right arrow to switch between the column values of adjacent rows. 3. Hover the pointer over a value field and click the zoom-in icon  to view the details. 4. In the table on the **Column Mode** tab, you can view the comments for a column in the **Remarks** column. Perform the following steps to modify the comments: a. In the left-side navigation pane, right-click the target table and select **View Table Structure** to go to the **Attribute** tab. b. In the left-side navigation pane of the **Attribute** tab, click the **Column** tab. c. Select a field and click the **Edit** icon. The field editing dialog box appears. d. In the **Comment** field , edit the comments, and click **OK**. e. In the **SQL Confirmation** dialog box, click **Execute**. f. View the modified comments on the **Column Mode** tab. |
+| Columns | Click this icon to select the columns to be displayed on the page. |
+| Back to Start | Click this icon to go back to the first page. |
+| Previous | Click this icon to go to the previous page. |
+| Next | Click this icon to go to the next page. |
+| Jump to Bottom | Click this icon to go to the last page. |
+| Search | Enter a keyword in the search box to search for the desired results. |
+| Edit | Click **Edit** to enable editing mode for the current result set. The editing mode supports the following operations: **Add**, **Copy Current Row**, **Delete**, **Cancel**, **Confirm Modification**, which submits a transaction when autocommit is enabled, and **Modify and Submit**, which is displayed when autocommit is disabled. In the editing mode, you can either double-click target data to directly modify it or click the preceding icons for convenient operations. When you edit a cell, you can right-click the cell and select **Copy** or **Set to Null** from the context menu to operate on the cell. **Note** The ResultMetaData information is obtained during the execution of an SQL statement to indicate whether the result set can be edited. - If the result set cannot be edited, the Edit icon is not displayed and you are prompted that the result set cannot be edited. - If the result set can be edited, the Edit icon is available and you can click it to go to the result set editing page. You can edit result sets in single-table and single-view queries. - However, result sets that involve the SET and ENUM fields cannot be edited. |
+| Download Data | You can export the query results to a CSV, SQL, or Excel file. - To export the query results to an SQL file: Edit the SQL statements in the **SQL Query** field, specify **Maximum Number of Lines in Result Set**, **File Name**, **File Format** (SQL)**,** **File Encoding**, **Data Desensitization**, and **SQL File Settings** (**Table Name** ). - To export the query results to a CSV file: Edit the SQL statements in the **SQL Query** field, specify **Maximum Number of Lines in Result Set**, **File Name**, **File Format**, **File Encoding**, and **Data Desensitization**. In the **CSV File Settings** section, specify **Include the Column Header**, **Convert the Empty Character String into a Null Value**, **Field Separator**, **Text Identifier**, and **Line Break Symbol**. - To export the query results to an EXCEL file: Edit the SQL statements in the **SQL Query** field, specify **Maximum Number of Lines in Result Set**, **File Name**, **File Format**,**File Encoding**, and **Data Desensitization**. In the **Excel File Settings** section, specify **Include the Column Header** and **Export SQL statements to another sheet**. **Note** - You can desensitize the exported data. You can specify a custom number of rows to export as needed. - If you export data in CSV format, the exported CSV file can be opened by Microsoft Excel. - If you export data in XLS format, you can specify whether to include the column header and whether to export the SQL statements of the query.  |
+| Plan | Click this icon to view the actual resource consumption and execution plan of an executed SQL statement. This allows you to evaluate the performance of the statement. |
+
+
diff --git a/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/3.web-odc-anonymous-block-window.md b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/3.web-odc-anonymous-block-window.md
new file mode 100644
index 00000000..e803d6cf
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/3.web-odc-anonymous-block-window.md
@@ -0,0 +1,123 @@
+Anonymous block window
+===========================================
+
+
+
+Overview
+-----------------------------
+
+To open an anonymous block window, perform the following steps: enter the Database Management page of OceanBase Developer Center (ODC), click **Workspace** in the top navigation bar, and click **Anonymous Block Window** .
+
+An anonymous block window provides a **PL/SQL editing** area, the **PL/SQL Execution Result and DBMS Output** tabs, and the **Debugging** page.
+
+
+
+PL editing area
+------------------------------------
+
+The editing area of the anonymous block window provides many features for you. For example, when you open a new anonymous block window,
+
+* the guidance code is provided to make your script-writing easier.
+
+
+
+* Database keywords are highlighted in different colors.
+
+
+
+* It also provides features such as formatting to help you improve your PL/SQL statement writing efficiency.
+
+ In addition to the preceding features, the toolbar of the editing area provides the following buttons.
+
+
+ | Button | Description |
+ |------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Run | Click this button to execute the statements in the code area. |
+ | Abort | Click this button to abort the statement that is being executed. |
+ | Debug | Click this button to open the debugging page to debug the anonymous objects in the code area. |
+ | Format | Click this button to apply the formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+ | Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+ | Undo | Click this button to undo the last operation. |
+ | Redo | Click this button to reverse an **Undo** operation. |
+ | Case Sensitivity | The system supports three capitalization options: **All C** **aps** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+ | Indent | You can add indents to or delete indents from the statements that you selected. |
+ | Comments | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+ | Save | Click this button to save the script in the current window. You can open a saved script when you enter the workspace again. **Note** - You can view only the SQL scripts saved by yourself. The script names must be unique. - After you open a saved script, you can continue to edit it. |
+
+
+
+
+
+
+PL/SQL Execution Result and DBMS Output tabs
+-----------------------------------------------------------------
+
+After you click the run iconin the toolbar of the editing area to execute the anonymous block, you can view the information in the **Execution Result** and **DBMS Output** tabs under the editing area.
+
+* The **Execution Result** tab displays the execution result of the script. If the execution was successful, **Executed** is displayed. Otherwise, an error message is displayed.
+
+* The **DBMS Output** tab displays the output of a subprogram that contains PL/SQL output statements, such as `dbms_output.put_line`.
+
+
+
+
+Debugging page
+-----------------------------------
+
+You can debug an anonymous block on the debugging page. To enter this page, click **Debug** in the toolbar of the editing area.
+
+On the debugging page, you can debug the anonymous block.
+**Notice**
+
+
+
+* We recommend that you upgrade to OBServer V2.2.77 or later. This is because some versions of OBServer have been found with PL/SQL debugging issues, which may compromise the OBServer stability.
+
+
+
+* ODC V3.2.2 or earlier does not support the debugging feature when you connect ODC to the target instance by using OBProxy. To use the debugging feature, directly connect ODC to the target instance.
+
+
+
+* ODC V3.2.2 and later support PL/SQL debugging when you connect to OBServer by using OBProxy.
+
+
+
+* You have installed the debugging packages such as DBMS_DEBUG and DBMS_OUTPUT in the connected database.
+
+
+
+
+
+
+
+
+In debugging mode, the toolbar in the editing area provides the following buttons.
+
+
+| Button | Description |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Batch Execute | Runs till the next breakpoint. If no breakpoint exists, runs till the end. |
+| Step Over | Click this button to step over a given line without stepping into any subprogram. |
+| Step Into | Click this button to execute code line by line. If the line includes a call to a stored procedure or function, it steps into the called subprogram. |
+| Step Out | For a subprogram, you can click this button to return to the next line of the upper-layer call position. For the main program, this button achieves the same effect as **Auto Debugging** . |
+| Abort Debugging | Click this button to execute the stored procedure till the end and skip breakpoints. |
+| Debug Again | Click this button to initiate a new round of debugging on the current object. Unlike **Debug** , it does not establish a new debugging connection. |
+| Exit Debugging | Click this button to close the debugging connection and exit the debugging window. |
+
+
+
+In addition to the editing area, the debugging mode also provides the following tabs:
+
+* **Parameters** : displays the definition information and values of all the parameters of the object to be debugged. The definition information includes the parameter name, mode, and type. The values may change as a result of the debugging process.
+
+* **Stacks and Variables** : displays the variables in the current stack and the values of the variables.
+
+* **DBMS Output** : If a subprogram contains PL/SQL output statements, such as `dbms_output.put_line`, the output is displayed on this tab.
+
+* **Breakpoint** : You can click the line number in the editing area to set a breakpoint, and click the line number again to remove the breakpoint. The Breakpoint tab displays all the breakpoints that you set in their execution order. You can select multiple breakpoints to cancel them at a time. The Actions column of each breakpoint information row provides the **Cancel** and **View** actions. You can click Cancel to cancel a breakpoint. After you click View, the cursor moves to the location of the breakpoint in the editing area.
+
+* **Debugging Logs** : displays the debugging logs and error logs. Debugging logs include information about the start and end of debugging and the addition and cancellation of breakpoints.
+
+
+
diff --git a/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/4.web-odc-command-line-window.md b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/4.web-odc-command-line-window.md
new file mode 100644
index 00000000..aaf9df75
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/4.web-odc-command-line-window.md
@@ -0,0 +1,48 @@
+Command-line window
+========================================
+
+OceanBase Developer Center (ODC) integrates the OceanBase command-line client OBClient in the form of a command-line window. OBClient is the recommended command-line client for OceanBase. The command-line window allows you to use OBClient without a need to download or install it. It allows you to execute SQL or PL statements and view the execution results in real time. It also allows you to run the `SOURCE` command to execute files uploaded to the server.
+
+Create a command-line window
+-------------------------------------------------
+
+Log on to ODC and click the name of the target connection to go to the corresponding connection management page. Click **Workspace** in the navigation bar on the top of the page and select **Command-line Window** from the drop-down list, to create a command-line window. The window that opens automatically connects to the current instance, and displays a default code segment that contains the connection ID, version information, and help information.
+**Notice**
+
+
+
+You can create up to three command-line windows at a time.
+
+If a command-line window is disconnected, the **Reconnect** button appears in the upper-right corner of the command-line window. Click the button to reconnect the window.
+
+Script management
+--------------------------------------
+
+If you need to reference a script in your development work, you can the **Script Management** feature of the **Command-line Window** to import the script and then reference it.
+
+To reference a script, perform the following steps:
+
+1. Enter Script Management panel.
+
+ Click the **Script Management** button in the upper-right corner of the command-line window to open the **Script Management** panel.
+
+
+2. Import the script that you want to reference.
+
+ Click the file pool under **Import Script** to start the file explorer, and select the script that you want to reference. Alternatively, you can directly drag the script file into the file pool to upload it. The maximum file size supported is 250 MB.
+
+
+3. Obtain the file path.
+
+ After the script is uploaded, you can view information about the script in the **Scripts** table in the panel. The table contains the following columns: **Script Path** , **Script Name** , **File Size** , and **Uploaded At** . To reference a script, click the **Copy Path** button in the Actions column and paste the path in the command-line window.
+
+
+4. Delete a script file.
+
+ You can view only script files uploaded by yourself. A file will be automatically deleted 30 minutes later after it is uploaded, to avoid unnecessary space consumption. You can also click the **Delete** button in the Actions column to delete a file.
+
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/5.web-odc-stored-scripts.md b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/5.web-odc-stored-scripts.md
new file mode 100644
index 00000000..0f590dc6
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/5.web-odc-stored-scripts.md
@@ -0,0 +1,113 @@
+Stored scripts
+===================================
+
+Log on to OceanBase Developer Center (ODC), and click the name of the target connection to go to the corresponding connection management page. Click **Workspace** in the top navigation bar, choose **Stored Scripts** from the drop-down list, and then choose a script that you previously stored in an SQL window or anonymous block window.
+
+Overview
+-----------------------------
+
+
+
+After you choose the script, you can proceed to edit or run the script. If the script is an SQL script, ODC opens the script in an SQL window. If the script is an anonymous block script, ODC opens the script in an anonymous block window. In the script list, buttons with the following features are provided after each script name.
+
+
+| Feature | Description |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Edit | Click  to modify the name and content of the script. |
+| Delete | Click  to delete the script. |
+| Script management | Click  to edit, import, download, or delete scripts. |
+
+
+
+Script management
+--------------------------------------
+
+### Edit a script
+
+
+
+1. Log on to the ODC homepage, and click the name of the target connection to go to the corresponding database object management page. Choose **Workspace** \> **Stored Scripts** .
+
+
+
+2. Select a script from the drop-down list of **Stored Scripts** , and click  to go to the Edit Script panel. You can also click  to go to the Script Management panel, select a script, and click Edit.
+
+
+
+3. In the **Edit Script** panel, modify **Script Name** and **Script Content** and click **Save** .
+
+
+
+
+
+
+### Delete a script
+
+1. Log on to the ODC homepage, and click the name of the target connection to go to the corresponding database object management page. Choose **Workspace** \> **Stored Scripts** .
+
+
+
+2. Select a script from the drop-down list of **Stored Scripts** and click  to delete it.
+
+
+
+
+
+
+### Manage scripts
+
+
+
+1. Log on to the ODC homepage, and click the name of the target connection to go to the corresponding database object management page. Choose **Workspace** \> **Stored Scripts** .
+
+
+
+2. Click **Stored Scripts** , and then click  in the drop-down list to go to the Script Management panel.
+
+3. In the Import Script section, click or drag files to import one or more scripts.
+
+ > **Note**
+ > - The size of a single file cannot exceed 250 MB.
+ > - Files suffixed with .sql, .pl, and .txt are supported.
+
+
+
+
+
+
+
+4. Take the following actions in the script list:
+
+ * Click  to refresh the script list.
+
+
+
+ * Enter a script name in the search box to search for the script.
+
+
+
+ * Click  the check box to select multiple scripts for batch download or deletion.
+
+
+
+ * Click **Copy Path** to copy the script path.
+
+
+
+ * Click **Edit** to edit the script.
+
+
+
+ * Click **Download** to download the script.
+
+
+
+ * Click **Delete** to delete the script.
+
+
+
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/6.web-odc-snippet.md b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/6.web-odc-snippet.md
new file mode 100644
index 00000000..7e8672f4
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/5.web-odc-use-workspace/6.web-odc-snippet.md
@@ -0,0 +1,80 @@
+Snippet
+============================
+
+As an enterprise-grade database development platform, OceanBase Developer Center (ODC) provides the code snippet module to facilitate database development. If you forget about the usage of some statements, you can query in the code snippet module. The code snippet module provides suitable code snippets based on whether you are in Oracle or MySQL mode. In addition to the built-in code snippets, you can also create custom code snippets to store frequently used code segments. A custom code snippet can be viewed only by its creator.
+
+To open the Snippets panel, click **Snippets** in the toolbar of an SQL window, an anonymous block window, or a PL object editing page.
+
+View code snippets
+---------------------------------------
+
+In the Snippets panel, the code snippets are displayed in a list of cards. Each card displays information about a code snippet, such as its name, description, and type. When you place the pointer over the tips icon next to a code snippet name, a tip window appears, displaying the entire code in the snippet.
+
+You can directly search for specific code snippets in the search box above the card list. A filter is provided below the search box for you to filter code snippets by type. The filter provides the following options: **Others** , **DML** , **DDL** , **Process Control Statement** , and **All Types** . By default, All Types is selected.
+
+Create a code snippet
+------------------------------------------
+
+Click the **+Create** button in the upper-right corner of the code snippet list. The **Create Snippets** panel appears. Specify the following information in the panel:
+
+* **Snippet Name** : specifies the name of the code snippet. It can contain letters, digits, and underscores (_), and can contain a maximum of 60 characters. This parameter must be specified.
+
+
+
+* **Snippet Type** : specifies the type of the code snippet. The types include **Others** , **DML** , **DDL** , and **Process Control Statement** . By default, **Others** is selected.
+
+
+
+* **Snippets** : specifies the actual code of the snippet. The length cannot exceed 2000 characters. This parameter must be specified. Similar to the SQL window, the toolbar of the editing area also provides buttons such as Format, Find and Replace, Undo, Redo, Case Sensitivity, Indent, and Comment. It also provides code highlighting and association features.
+
+
+
+* **Snippet Description** : provides additional notes on the code snippet. The length cannot exceed 200 characters. This parameter is optional.
+
+ **Note**
+
+
+
+ If you specified an additional notes in the description field, the snippet card in the Snippets panel displays the notes. Otherwise, the first 30 characters of the code are displayed.
+
+
+
+
+
+
+
+Reference a code snippet
+---------------------------------------------
+
+You not only can view the content of a created code snippet when you edit scripts, but also can reference it in your script. You can reference a code snippet by using one of the following three methods:
+
+* Method 1: Drag the target card from the code snippet list to the editing area, and the code in the code snippet is copied to the editing area.
+
+
+
+* Method 2: Click the copy icon in the lower-right corner of the target code snippet card to copy the code, and then press Ctrl+V or Cmd+V to paste the code to the editing area.
+
+
+
+* Method 3: The editing area of the SQL window supports code association. When you edit a script in the editing area, existing code snippets appear in the code association window for you to view and reference.
+
+
+
+
+
+
+Manage code snippets
+-----------------------------------------
+
+ODC provides the **Edit** and **Delete** options for you to manage custom code snippets. You cannot edit or delete built-in code snippets.
+
+* **Edit** : Click the management icon (···) in the upper-right corner of the target code snippet card. In the menu that appears, click the **Edit** button to go to the **Edit Snippet** panel. The panel displays parameters such as **Snippet Name** , **Snippet Type** , **Snippets** , and **Snippet Description** that were specified at creation of the code snippet. You can modify the information as needed.
+
+
+
+* **Delete** : Click the management icon (···) in the upper-right corner of the target code snippet card. In the menu that appears, click the **Delete** button to delete the code snippet.
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/1.web-odc-data-export-and-import-overview.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/1.web-odc-data-export-and-import-overview.md
new file mode 100644
index 00000000..9d985dba
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/1.web-odc-data-export-and-import-overview.md
@@ -0,0 +1,33 @@
+Overview
+=============================
+
+OceanBase Developer Center (ODC) provides the database import and export features and the table import and export features, to facilitate database data maintenance for database developers. The database import and export features allow you to import data to or export data from selected tables in the database in batches. The table import and export features allow you to import data to or export data from the target table.
+
+ODC provides a **Task Center** page. After you create an import or export task, this page displays the current import or export task. You can also view task details and logs on this page.
+
+> **Notice**
+>
OceanBase Database of a version earlier than V2.2.30 supports only UTF8.
+>
In ODC V2.2.1 and earlier versions, to use the import and export features, you must connect ODC to the target instance through OBProxy. If you directly connect ODC to the target instance, the import and export features are unavailable.
+>
In ODC V2.4.1 and later, you can use the sys tenant account to accelerate the import and export tasks. To export objects other than tables and views, you must configure the sys tenant account.
+
+
+
+
+
+
+This chapter describes the import/export features in different topics.
+
+* [Export and import formats](../../../7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md)
+
+
+
+* [Batch export and import](../1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md)
+
+
+
+* [Single table export and import](../1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md)
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md
new file mode 100644
index 00000000..5705959e
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md
@@ -0,0 +1,30 @@
+Export and import formats
+==============================================
+
+OceanBase Developer Center (ODC) supports three data export modes: Export Schema and Data, Export Data Only, and Export Schema Only. A schema is the DDL file of an exported object, while data is the data file stored in the object. The types of schemas and data files vary with the export and import formats.
+
+ODC supports exporting data in CSV and SQL formats and importing ZIP, SQL (batch import), and CSV (single table import) files.
+
+Export file formats
+----------------------------------------
+
+ODC exports data in a zip file, which contains the metadata file MANIFEST.bin, the schema definition files of the exported objects, and the data files.
+
+When you create an export task, if you set **Data Format** to **SQL Format** , the zip file contains the schema definition files named in the pattern of `object_name-schema.sql` and data files named in the pattern of `object_name.sql`. The object names are the same as those of the objects in the database.
+
+
+
+If you set **Data Format** to **CSV Format** , the zip file contains the schema definition files named in the pattern of `object name-schema.sql` and data files named in the pattern of `object name.csv`. The object names are the same as those of the objects in the database.
+
+
+
+Import file formats
+----------------------------------------
+
+ODC supports importing ZIP (batch import and single table import), SQL (batch import), and CSV (single table import) files.
+
+The ZIP file here is a compressed package that is suffixed with .zip. When you create an import task, if you select **ZIP Files** as the **Import Content** , you must specify whether **Data Format** in the zip file is **CSV Format** or **SQL Format** . For more information about the content of different formats of files to be exported, see **Export file formats**.
+
+SQL files supported for batch data import are suffixed with .sql and contain statements that can be directly executed in the database. These statements include `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `CREATE`, and `DROP`.
+
+CSV files supported for single table import are data files that are suffixed with .csv or .txt. These files support custom delimiters.
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md
new file mode 100644
index 00000000..05dfdb98
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md
@@ -0,0 +1,255 @@
+# Batch export and import
+
+
+
+## Overview
+
+OceanBase Developer Center (ODC) allows you to export and import the schemas and data of database objects in batches.
+
+After you open a database connection, click **Tools** in the top navigation bar, and then select **Export**or **Import** from the drop-down list to go to the corresponding settings panel.
+
+The following table describes the requirements for the size of imported and exported data and the retention period of files in ODC.
+
+| Requirement | Description |
+|------------------------|------------|
+| Limits on the size of imported and exported data in web ODC |
The maximum size of files imported in one batch cannot exceed 2 GB after compression. To import data of a larger size, use the data import tool [OBLOADER](https://www.oceanbase.com/docs/enterprise/oceanbase-dumper-loader-cn/V3.2.0/10000000000610772).
The maximum size of files exported in one batch cannot exceed 2 GB before compression. To export data of a larger size, use the data export tool [OBDUMPER](https://www.oceanbase.com/docs/enterprise/oceanbase-dumper-loader-cn/V3.2.0/10000000000610778).
|
+| File retention period on the server |
The status of a task, such as Succeeded, Failed, and Canceled, does not affect the lifecycle of the task files.
Tasks are permanently retained. Task-related files are retained for 14 days by default.
|
+
+
+
+## Batch export
+
+In the **Create Export Task** panel, you can export multiple database objects to files in the specified format at the same time.
+
+
+
+
+The following example shows how to batch export the employee table and the salary view in the ODC. Procedure:
+
+### Step 1: Specify the export content
+
+As shown in the preceding figure, ODC supports three export modes: **Export Schema and Data**, **Export Data Only**, and **Export Schema Only**. **Export Schema Only** exports the definition statements of the target object. You can select the export content from the **Export Content** drop-down list.
+
+### Step 2: Select a database
+
+Select the database where the object to export resides. The name of the database connection to which the task belongs is also displayed.
+
+### Step 3: Specify the export range
+
+You can select **Partial Export** or **Full Export**.
+
+* If you select **Partial Export**, you can select the objects you want to export in the **Select Objects** pane in the **Export Objects** section. You can use the search box to search for desired objects.
+
+
+
+* If you select **Full Export**, all objects in the database are exported.
+
+
+
+
+
+
+### Step 4: Go to the Export Settings panel
+
+Click **Next: Export Settings** to specify the file export settings and the sys tenant account.
+
+### Step 5: Go to the Data File Settings panel
+
+
+
+1. Specify **Data Format**.
+
+ ODC supports exporting data to files in the CSV format and SQL format. If you specify **Export Schema Only** for **Export Content**, you can only export data to files in the SQL format. For more information about formats, see [Export and import formats](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md).
+
+
+2. Specify **File Encoding**.
+
+ ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+
+3. Specify **Data Desensitization**.
+
+ By default, desensitization is disabled. You can select and manage the names of the desensitization strategies. In the **Manage Desensitization Strategies** section, you can add, edit, or delete strategies. For more information, see [Manage data desensitization](../../4.web-odc-public-resource-management/6.web-odc-desensitization-rules.md).
+
+
+4. Specify **Data File Settings**.
+
+ If you select **Export Schema Only** for **Export Content**, you do not need to configure the export data settings. You need to specify the following fields:
+
+ * **Use Global Snapshot**: If you select this option, ODC exports the data in the latest global snapshot of the specified table to ensure global data consistency.
+
+
+
+ * **Batch Commit Quantity (SQL Format)**: You can click **Advanced** next to **Export Data Settings** to specify this field. If you select **SQL Format** for **Data Format**, you can specify the number of rows to be committed during the export. When this number is reached, a `COMMIT` command is executed.
+
+
+
+ * Specify information for the CSV format. If you select **CSV Format** for **Data Format** and **Export Schema and Data** for **Export Content**, you can specify following information:
+
+ * **Include the Column Header**: specifies whether to include column headers when data is exported in CSV format. This option is selected by default.
+
+
+
+ * **Convert the Empty String into a Null Value**: This option is selected by default to determine whether to convert empty strings in the table to NULL values when data is exported in CSV format.
+
+
+
+ * **Field Separator**: specifies the separator between fields. The following signs are supported: commas, semicolons, and colons. You can also use a character as the separator.
+
+
+
+ * **Text Identifier**: specifies the identifier for the text content. Single quotation marks (') and double quotation marks (") are supported.
+
+
+
+ * **Line Break Symbol**: specifies the line break symbol. The following characters are supported: \\n, \\r, and \\r\\n.
+
+
+
+
+
+
+
+
+
+
+
+
+### Step 6: Specify schema file settings
+
+Choose whether to select **Add DROP TABLE Statement before CREATE TABLE Statement**. If you select this option, a `DROP` statement is added before the corresponding `CREATE` statement of an object when the schema files of the object are exported.
+
+### Step 7: Select an execution method
+
+Select **Execute immediately** or **Timed execution**.
+
+### Step 8: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+**Notice**
+- The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+
+
+- If the account of the sys tenant is not configured, indexes are not imported or exported.
+
+
+### Step 9: Retain Current Configuration
+
+Check **Retain Current Configuration** to keep the current part of the data file and structure file configuration.
+
+
+#### Step 10: Generate an export task
+
+After you specify all preceding information, you can click **Export** in the lower-right corner of the panel to create an export task.
+
+#### Step 11: View the export task
+
+
+
+After the export task is generated, the **Task Center** page automatically appears, where you can view the task information and download exported data and schema files. For more information, see [Export tasks](../../../6.web-odc-user-guide/9.web-odc-task-management/3.web-odc-export-tasks.md).
+
+Batch import
+-------------------------
+
+In the **Create Import Task** panel, you can choose to import schemas and data to multiple database objects at the same time.
+
+
+
+Take the import of ZIP files (6000219_import_file) in the ODC as an example. The file contains an employee table and a salary view. Procedure:
+
+### Step 1: Specify **Import Format**
+
+As shown in the preceding figure, ODC supports batch import of **CSV Files**, **SQL Files**, and **ZIP Files**. You can select the desired file format from the **Import Format** drop-down list. For more information about formats, see [Export and import formats](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md).
+
+### Step 2: Upload the file to be imported
+
+Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it. The format of the uploaded file must be the same as that of the value you specified for Import Format. Upload files suffixed with .zip if you have selected ZIP Files for Import Format, upload files suffixed with .sql if you have selected SQL Files for Import Format, and upload files suffixed with .csv if you have selected CSV Files for Import Format.
+
+### Step 3: Specify **File Encoding**
+
+ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+### Step 4: Go to the Import Settings panel
+
+Click **Next: Import Settings** to specify file import settings and the sys tenant account.
+
+### Step 5: Specify **Import Content**
+
+
+
+You must specify this parameter when you select **ZIP Files** for **Import Format**. ODC supports **Import Data Only**, **Import Schema Only**, and **Import Schema and Data**. **Import Schema Only** imports the definition statements of the target object. You can select the import content from the **Import Content** drop-down list.
+
+### Step 6: Select a database
+
+Select the database to which the data object is to be imported. The name of the database connection to which the task belongs is also displayed.
+
+### Step 7: Specify **Import Data Settings**
+
+If you select **ZIP Files** for **Import Format** and **Import Data Only** or **Import Schema and Data** for **Import Content**, this option must be specified. You need to specify the following fields:
+
+* **Clear Data Before Import**: If you select this option, the original data in the destination object is cleared during data import.
+
+
+
+* **Batch Commit Quantity**: You can click **Advanced** next to **Export Data Settings** to specify this field. After you specify this field, a `COMMIT` statement is executed when the number of exported data rows reaches the specified quantity.
+
+
+
+* **Skipped Data Type (Optional)**: You can specify the data types to be skipped during data import. The data types that can be skipped are different in MySQL and Oracle modes. You can select multiple data types.
+
+
+
+
+
+
+### Step 8: Specify **Import Schema Settings**
+
+You cannot specify this field if you select Import Data Only for **Import Content**. This field involves operations on schemas that already exist. If you select **Skip**, the system skips the schema definition statement in the file to be imported and directly imports the data. The original data in the object is retained. If you select **Replace**, the system executes the schema definition statement in the file to be imported to re-create an object and replace the original one. Data in the original object is cleared.
+
+### Step 9: Specify **Task Error Handling Method** and the execution method
+
+* ODC supports two error handling methods: **Abort Task** and **Ignore Error and Continue**. You need to select the handling method as required.
+
+
+
+* Select **Execute immediately** or **Timed execution**.
+
+
+
+
+
+
+### Step 10: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+ **Notice**
+ - The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+ 
+
+ - If the account of the sys tenant is not configured, comments and indexes are not imported or exported.
+
+
+### Step 11: Retain Current Configuration
+
+Check **Retain Current Configuration** to keep the current part of the data file and structure file configuration.
+
+### Step 12: Generate an import task
+
+After you specify all preceding information, you can click **Submit** in the lower-right corner of the panel to create an import task.
+
+#### Step 13: View the import task
+
+
+
+After the task is generated, the **Task Center** page automatically appears, where you can view the task information. For more information, see [Import tasks](../../../6.web-odc-user-guide/9.web-odc-task-management/2.web-odc-import-tasks.md).
+
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md
new file mode 100644
index 00000000..f1c44822
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md
@@ -0,0 +1,217 @@
+Single table export and import
+============================
+
+
+
+Overview
+-----------------------
+
+OceanBase Developer Center (ODC) allows you to import and export data and schemas from a specified table.
+
+After you open a database connection, you can click Objects in the left-side navigation pane to view the objects. Right-click the name of the target object in the object list, or click **Tools** in the top navigation bar and then select **Export** or **Import** from the drop-down list to export or import the data and schema in the current table.
+
+The following table describes the requirements for the size of imported and exported data and the retention period of files in ODC.
+
+
+| Requirement | Description |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Limits on the size of imported and exported data in web ODC |
The maximum size of files imported in one batch cannot exceed 2 GB after compression. To import data of a larger size, use the data import tool [OBLOADER](https://www.oceanbase.com/docs/enterprise/oceanbase-dumper-loader-cn/V3.2.0/10000000000610772).
The maximum size of files exported in one batch cannot exceed 2 GB before compression. To export data of a larger size, use the data export tool [OBDUMPER](https://www.oceanbase.com/docs/enterprise/oceanbase-dumper-loader-cn/V3.2.0/10000000000610778).
|
+| File retention period on the server |
The status of a task, such as Succeeded, Failed, and Canceled, does not affect the lifecycle of the task files.
Tasks are permanently retained. Task-related files are retained for 14 days by default.
|
+
+
+
+Single table export
+-------------------------
+
+
+
+The procedure for exporting a single table is basically the same as the that of [batch export](../1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md). The following example shows how to export an employee table in ODC. Procedure:
+
+### Step 1: Specify the export content
+
+As shown in the preceding figure, ODC supports three export modes: **Export Schema and Data**, **Export Data Only**, and **Export Schema Only**. **Export Schema Only** exports the definition statements of the target object. You can select the export content from the **Export Content** drop-down list.
+
+### Step 2: Select a database
+
+Select the database where the object to export resides. The name of the database connection to which the task belongs is also displayed.
+
+### Step 3: Specify the export range
+
+By default, the current table is exported. You can select **Partial Export** or **Full Export**.
+
+* If you select **Partial Export**, you can select the objects you want to export in the **Select Objects** pane in the **Export Objects** section. You can use the search box to search for desired objects.
+* If you select **Full Export**, all objects in the database are exported.
+
+### Step 4: Go to the Export Settings panel
+
+Click **Next: Export Settings** to specify the file export settings and the sys tenant account.
+
+### Step 5: Go to the Data File Settings panel
+
+
+
+1. Specify **Data Format**.
+
+ ODC supports exporting data to files in the CSV format and SQL format. If you specify **Export Schema Only** for **Export Content**, you can only export data to files in the SQL format. For more information about formats, see [Export and import formats](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md).
+
+
+2. Specify **File Encoding**.
+
+ ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+
+3. Specify **Data Desensitization**.
+
+ By default, desensitization is disabled. You can select and manage the names of the desensitization strategies. In the **Manage Desensitization Strategies** section, you can add, edit, or delete strategies. For more information, see [Manage data desensitization](../../4.web-odc-public-resource-management/6.web-odc-desensitization-rules.md).
+
+
+4. Specify **Data File Settings**.
+
+ If you select **Export Schema Only** for **Export Content**, you do not need to configure the export data settings. You need to specify the following fields:
+ * **Use Global Snapshot**: If you select this option, ODC exports the data in the latest global snapshot of the specified table to ensure global data consistency.
+ * **Batch Commit Quantity (SQL Format)**: You can click **Advanced** next to **Export Data Settings** to specify this field. If you select **SQL Format** for **Data Format**, you can specify the number of rows to be committed during the export. When this number is reached, a `COMMIT` command is executed.
+ * Specify information for the CSV format. If you select **CSV Format** for **Data Format** and **Export Schema and Data** for **Export Content**, you can specify following information:
+
+ * **Include the Column Header**: specifies whether to include column headers when data is exported in CSV format. This option is selected by default.
+ * **Convert the Empty String into a Null Value**: This option is selected by default to determine whether to convert empty strings in the table to NULL values when data is exported in CSV format.
+ * **Field Separator**: specifies the separator between fields. The following signs are supported: commas, semicolons, and colons. You can also use a character as the separator.
+ * **Text Identifier**: specifies the identifier for the text content. Single quotation marks (') and double quotation marks (") are supported.
+ * **Line Break Symbol**: specifies the line break symbol. The following characters are supported: \\n, \\r, and \\r\\n.
+
+### Step 6: Specify schema file settings
+
+Choose whether to select **Add DROP TABLE Statement before CREATE TABLE Statement**. If you select this option, a `DROP` statement is added before the corresponding `CREATE` statement of an object when the schema files of the object are exported.
+
+### Step 7: Select an execution method
+
+Select **Execute immediately** or **Timed execution**.
+
+### Step 8: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+ **Notice**
+ - The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+ 
+
+ - If the account of the sys tenant is not configured, indexes are not imported or exported.
+
+### Step 9: Retain Current Configuration
+
+Check **Retain Current Configuration** to keep the current part of the data file and structure file configuration.
+
+### Step 10: Generate an export task
+
+After you specify all preceding information, you can click **Export** in the lower-right corner of the panel to create an export task.
+
+### Step 11: View the export task
+
+
+
+After the export task is generated, the **Task Center** page automatically appears, where you can view the task information and download exported data and schema files. For more information, see [Export tasks](../../../6.web-odc-user-guide/9.web-odc-task-management/3.web-odc-export-tasks.md).
+
+Single table import
+-------------------------
+
+
+
+Take the import of a ZIP file (6000219_import_file) in ODC as an example. The file contains an employee table. Procedure:
+
+### Step 1: Specify Import Format
+
+As shown in the preceding figure, ODC supports **CSV Files** and **ZIP Files** for single table import. You can select the desired file format from the **Import Format** drop-down list. For more information about formats, see [Export and import formats](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md).
+
+### Step 2: Upload the file to be imported
+
+Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it. The format of the uploaded file must be the same as that of the value you specified for **Import Format**. Upload files suffixed with .zip if you have selected **ZIP Files** for **Import Format**, and upload files suffixed with .csv if you have selected **CSV Files** for **Import Format**.
+
+> **Note**
+> You can upload a single table or multiple tables.
+
+### Step 3: Specify File Encoding
+
+ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+### Step 4: Go to the Import Settings panel
+
+Click **Next: Import Settings** to specify file import settings and the sys tenant account.
+
+### Step 5: Specify Import Content
+
+
+
+You must specify this parameter when you select **ZIP Files** for **Import Format**. ODC supports **Import Data Only**, **Import Schema Only**, and **Import Schema and Data**. **Import Schema Only** imports the definition statements of the target object. You can select the import content from the **Import Content** drop-down list.
+
+### Step 6: Select a database
+
+Select the database to which the data object is to be imported. The name of the database connection to which the task belongs is also displayed.
+
+### Step 7: Import the target table
+
+By default, the current table is imported. To import multiple tables, select the tables to be imported.
+
+### Step 8: Specify Import Data Settings
+
+If you select **ZIP Files** for **Import Format** and **Import Data Only** or **Import Schema and Data** for **Import Content**, this option must be specified. You need to specify the following fields:
+
+* **Clear Data Before Import**: If you select this option, the original data in the destination object is cleared during data import.
+
+
+
+* **Batch Commit Quantity**: You can click **Advanced** next to **Import Data Settings** to specify this field. After you specify this field, a `COMMIT` statement is executed when the number of exported data rows reaches the specified quantity.
+
+
+
+* **Skipped Data Type (Optional)**: You can specify the data types to be skipped during data import. The data types that can be skipped are different in MySQL and Oracle modes. You can select multiple data types.
+
+
+
+
+
+
+### Step 9: Specify Import Schema Settings
+
+You cannot specify this field if you select **Import Data Only** for **Import Content**. This field involves operations on schemas that already exist. If you select **Skip**, the system skips the schema definition statement in the file to be imported and directly imports the data. The original data in the object is retained. If you select **Replace**, the system executes the schema definition statement in the file to be imported to re-create an object and replace the original one. Data in the original object is cleared.
+
+### Step 10: Specify Task Error Handling Method and the execution method
+
+* ODC supports two error handling methods: **Abort Task** and **Ignore Error and Continue**. You need to select the handling method as required.
+* Select **Execute immediately** or **Timed execution**.
+
+
+
+
+
+
+### Step 11: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+ **Notice**
+ - The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+ 
+
+ - If the account of the sys tenant is not configured, comments and indexes are not imported or exported.
+
+### Step 12: Retain Current Configuration
+
+Check **Retain Current Configuration** to keep the current part of the data file and structure file configuration.
+
+### Step 13: Generate an import task
+
+After you specify all preceding information, you can click **Submit** in the lower-right corner of the panel to create an import task.
+
+### Step 14: View the import task
+
+
+After the task is generated, the **Task Center** page automatically appears, where you can view the task information. For more information, see [Import tasks](../../../6.web-odc-user-guide/9.web-odc-task-management/2.web-odc-import-tasks.md).
+
+
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/2.web-odc-data-mocking.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/2.web-odc-data-mocking.md
new file mode 100644
index 00000000..83d09bbc
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/2.web-odc-data-mocking.md
@@ -0,0 +1,75 @@
+Data mocking
+=================================
+
+OceanBase Developer Center (ODC) provides the data mocking feature. This feature can generate data based on field types in a table, to meet your requirement for a large amount of data during database performance tests or feature verification.
+
+
+
+Perform the following steps to generate data by using the data mocking feature:
+
+1. Go to the **Mock Data** panel.
+
+ Log on to ODC, and click the name of the target connection to go to the corresponding database object management page. Click **Tool** in the navigation bar in the upper part of the page and select **Mock Data** from the drop-down list. The **Mock Data** panel appears.
+
+
+2. View **Connection** .
+
+ The name of the database connection to which the task belongs is displayed under Connection.
+
+
+3. Specify **Database** .
+
+ Select the database to be changed.
+
+
+4. Specify the table for generating data.
+
+ In the Mock Data panel, select the table from the drop-down list under **Table** . The drop-down list displays all the tables in the current instance.
+
+
+5. Specify the amount of data to be generated.
+
+ In the Mock Data panel, set **Mock Data Volume** to specify the desired number of data rows to be generated. The default value is 1000. The system can generate up to 1,000,000 rows of data. You can set the value to an integer between 1 and 1000000.
+
+
+6. Specify the batch size.
+
+ In the Mock Data panel, set **Batch Processing Size** to specify the number of rows generated that trigger a `COMMIT` operation. The default value is 200. That is, a commit operation is performed once every 200 rows are generated. The maximum value supported is 500. You can set the value to an integer between 1 and 500.
+
+
+7. Specify whether to empty the table before inserting mock data into it.
+
+ In the Mock Data panel, select Yes or No under **Empty Table Before Inserting Mock Data** to specify whether or not to empty the table before inserting mock data.
+
+
+8. Specify the data conflict handling mode.
+
+ In the Mock Data panel, specify **Data Conflict Handling Mode** by selecting a mode from the drop-down list. ODC supports the following methods:
+ * **Ignore** : This option is selected by default. The data conflicting with existing data is not inserted.
+
+
+
+ * **Overwrite** : If a data conflict occurs, the original data is deleted, and the new data is inserted.
+
+
+
+ * **Terminate** : If a data conflict occurs, the data mocking task is terminated.
+
+
+
+
+
+
+9. Set data generation rules.
+
+ In the Mock Data panel, the **Rule Settings** table displays the fields in the table you selected in step 2 in the **Field Name** and **Field Type** columns. You can specify the data generation rules for the target fields in the **Rule** and **Rule Details** columns. The **Rule** column provides built-in rules based on the field type for you to choose from. The **Rule Details** column displays the detailed information for the rule that you selected. You can click the edit icon to edit the information.
+
+
+10. Submit the information to generate a data mocking task.
+
+ Click the **Submit** button in the lower-right corner of the Mock Data panel to generate a data mocking task. You can view the task details in the **Task Center** panel. For more information, see **Data mocking tasks** .
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/3.web-odc-partition-scheme.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/3.web-odc-partition-scheme.md
new file mode 100644
index 00000000..aef6240d
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/3.web-odc-partition-scheme.md
@@ -0,0 +1,42 @@
+# Partitioning plan
+
+## Background
+
+- **RANGE partitioning**: Multiple rows with column values in an ordered, continuous, and non-overlapping range are assigned to a partition. For details, see [Set partitioning rules](../11.web-odc-database-objects/1.web-odc-table-objects/2.web-odc-create-a-table.md).
+
+- **Partitioning Plan**: When inserting data in a range-partitioned table, if the inserted data exceeds the upper limit value of the current partition table, the data will not be inserted and an error will be returned. Partitioning plan is an extension function specially for range partitioning. ODC supports automatic management of range-partitioned table according to the partitioning strategy set by the user. Users do not need to manually create new partitions to facilitate the maintenance of range-partitioned table.
+
+This topic describes how to use a partitioning plan in the OceanBase Development Center (ODC) console, including performing automatic management on created and dropped table partitions.
+
+## Create a partitioning plan
+
+1. Log on to the ODC console, and click the name of the target connection to go to the corresponding database object management page.
+
+2. In the top navigation pane, choose **Tool** > **Partition Plan** to display the **Create a partition plan** panel.
+
+
+ 
+
+3. In the **Create a partition plan** panel, specify the following information.
+
+ 
+
+ | **Parameter** | **Description** |
+ |---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Connection | The connection to which the partitioning plan belongs. The default value is the current connection. |
+ | Partition policy | The information about the partitioning strategy. Search for and select a RANGE-partitioned table in the database and edit its partitioning strategy.
You can select **Only tables that are not set are displayed** on the right side of **Partition policy** to display only tables with no partitioning strategies.
You can also select multiple RANGE-partitioned tables and configure a partitioning strategy for them at a time.
In the **Partitioning Strategy** column, click the edit icon and then you can edit the number of partitions to create, partitioning interval, retention period, and naming rules.
**Number of Partitions**: set the number of partitions to pre-create.
**Partition Interval**: pre-create the corresponding number of partitions based on the time interval, unit: day/month/year.
**Retention Period**：the created partition is automatically cleared after the retention period expires, unit: day/month/year. Example: The number of partitions is 1, the partition interval is 1 month, and the retention period is 1 month, which means that 1 partition is pre-created for the current table, and 1 partition will be created every 1 month, and the created partition will be cleaned up automatically after 1 month. 
|
+ | Remarks | The business background of the project, such as the change purposes and expected goals. |
+
+4. After you specify the preceding information, click **Submit** in the lower-right corner of the panel.
+
+5. After the task is generated, the **Task Center** panel automatically appears, where you can view the task status and task information. For more information, see [Partitioning plan task](../9.web-odc-task-management/6.web-odc-partition-scheme-task.md).
+
+ 
+
+
+## Related topics
+
+* [Task process management](./4.web-odc-public-resource-management/4.web-odc-task-process.md)
+
+
+* [Partitioning plan task](../9.web-odc-task-management/6.web-odc-partition-scheme-task.md)
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/4.web-odc-database-change.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/4.web-odc-database-change.md
new file mode 100644
index 00000000..47b10e3d
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/4.web-odc-database-change.md
@@ -0,0 +1,128 @@
+Database changes
+=====================================
+
+
+
+Overview
+-----------------------------
+
+Statements in the SQL window of OceanBase Developer Center (ODC) are executed synchronously. Therefore, the execution may time out when the statement runs for a long time. You can use the database change tool to run time-consuming SQL statements to avoid execution timeout.
+
+
+
+Procedure
+------------------------------
+
+To create a database change task, perform the following steps:
+
+1. Go to the **Database Change** panel.
+
+ 1. Log on to the ODC homepage, and click the name of the target connection to go to the corresponding database object management page.
+
+
+
+ 2. Click **Tool** in the top navigation bar.
+
+
+
+ 3. Select **Database Change** in the drop-down list. The **Create Database Change Task** panel appears.
+
+
+
+
+
+
+2. View **Connection** . The current connection is selected by default and you cannot switch to another connection.
+
+
+
+3. Specify **Database** . The current database is selected by default.
+
+
+
+4. Specify **SQL Content** .
+
+ The database change supports two ways to specify SQL content:
+ * **SQL Entry** : This is the default way to specify SQL content. You can directly write the SQL script in the editing area.
+
+ **Note**
+
+
+ * You can click **IN Value Conversion** to convert the batch copied data into the in('A','B') format.
+
+
+
+
+
+ * **Upload File** : Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it.
+
+ **Note**
+
+
+ * You can upload up to 500 files. The total file size cannot exceed 256 MB.
+
+
+
+ * By default, files are sorted by the order in which they were uploaded. You can drag and drop them to change the order. Tasks are executed in the file order.
+
+
+
+ * Only SQL files suffixed with .sql are supported.
+
+
+
+
+
+
+
+
+
+
+5. Specify **Rollback Plan** .
+
+ You can write an SQL script or upload a file to specify the rollback plan. For more information, see the step of specifying SQL Content.
+
+
+6. **Delimiter** : The delimiters are supported.
+
+
+
+7. **Query Result Limit** : You can set the number of data rows in the query result. Value range: 1 to 1000000.
+
+
+
+8. Specify **Task Error Handling Method** .
+
+ The database change tool supports two methods to handle task errors:
+ * **Abort Task** : This is the default option. When you select this option, the task is aborted if an error occurs when you run the script.
+
+
+
+ * **Ignore Error and Continue** : When you select this option, the system skips the statement where an error occurs and continues to execute other statements in the script.
+
+
+
+
+
+
+9. Specify **Execution Timeout Value** .
+
+ Specify the value in the **Execution Timeout Value** field in hours. Default value: 48. Maximum value: 480.
+
+
+10. Optional. Specify the task description.
+
+ You can enter a description of no more than 200 characters in **Description** .
+
+
+11. Generate a database change task.
+
+ After you specify the above information in the panel, click **Create** to submit the information to generate the database change task.
+
+
+12. After the task is created, the **Task Center** \> **Database Change** page automatically appears. You can click **View** to go to the task details page, which displays **Task Information** , **Result** , and **Task Logs** .
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/5.web-odc-shadow-table-synchronization.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/5.web-odc-shadow-table-synchronization.md
new file mode 100644
index 00000000..98990bbc
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/5.web-odc-shadow-table-synchronization.md
@@ -0,0 +1,63 @@
+# Shadow table synchronization
+
+## Background
+
+The shadow table synchronization feature of OceanBase Developer Center (ODC) allows you to automatically create a shadow table in the current database based on the schema of the source table. The shadow table name is the combination of the source table name and a prefix or suffix. This feature applies to scenarios like full-link stress testing.
+
+This topic describes how to create a shadow table synchronization task in ODC.
+> **Note**
+>
The shadow table synchronization feature of ODC V4.0.0 supports only the MySQL mode. If the source table contains subpartitions, only template-based HASH or KEY subpartitions are supported.
+>
After a shadow table is created, you can view it on the Table page.
+>
When a shadow table is created, if a table with the same name but a different schema already exists, a synchronization SQL statement is generated to update the schema of the existing shadow table.
+
+## Create a shadow table synchronization task
+
+1. Log on to the ODC console, and click the name of the target connection to go to the corresponding database object management page.
+
+
+2. In the top navigation bar, choose **Tool** > **Synchronize Shadow Table** to display the **Create Shadow Table Synchronization Project** panel.
+
+ 
+
+3. On the **Create Shadow Table Synchronization Project** panel, specify the following information.
+
+ 1. Select a synchronization object.
+
+ 
+
+
+ | **Field** | **Description** |
+ |---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Database | The database to which the shadow table to be created belongs. You can view the name of the current connection. |
+ | Synchronization Range | The table to be synchronized.
**Partial Tables**: Shadow tables will be created in the current database for the selected tables.
**All Tables**: Shadow tables will be created in the current database for all tables in the source database.
|
+ | Name of Shadow Table | The name of the shadow table, in the format of **prefix** + source table name or source table name + **suffix**. You can use custom prefix or suffix. |
+ | Synchronization Objects | The source tables to be synchronized as shadow tables. You must specify this field when **Synchronization Range** is set to Partial Tables. |
+
+
+ 2. Analyze the schema of the shadow table.
+
+ 
+
+
+ | **Field** | **Description** |
+ |---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Synchronized Tables | The **Synchronized Tables** tab displays the source table name, shadow table name, and analysis result. You can click **View** to view the source table schema, shadow table schema, and schema change SQL statement, or click **Skip**, indicating that this shadow table is not synchronized. |
+ | Unsynchronized Tables | The **Unsynchronized Tables** tab displays the source table name, shadow table name, and analysis result. You can click **Undo Skip** to synchronize this shadow table.
**Note:** A skipped table will be displayed on the **Unsynchronized Tables** tab. If a shadow table with the same name and the same schema as the source table already exists, schema synchronization will be skipped.
|
+ | SQL Preview | The SQL statement for schema synchronization. |
+ | Task Settings | Options of **Execution Mode** include:
**Execute Immediately**: The synchronization task is executed immediately.
**Execute On Schedule**: The synchronization task is executed on schedule.
**Abort Task**: If an error occurs during the execution of the synchronization task, the subsequent SQL scripts are interrupted and no longer executed.
**Ignore Error and Continue**: If an error occurs during the execution of the synchronization task, the SQL script with the error is skipped, but subsequent SQL scripts will be executed.
|
+ | Remarks | The business background of the project, such as the change purpose and expected goal. |
+
+4. After you specify the preceding information, click **Submit** in the lower-right corner of the panel.
+
+
+5. After the task is generated, the **Task Center** panel automatically appears, where you can view the task status and task information. For more information, see [Shadow table synchronization tasks](../../6.web-odc-user-guide/9.web-odc-task-management/8.web-odc-shadow-table-synchronization.md).
+
+ 
+
+
+## Related topics
+
+* [Task process management](../../6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md)
+
+* [Shadow table synchronization tasks](../../6.web-odc-user-guide/9.web-odc-task-management/8.web-odc-shadow-table-synchronization-task.md)
diff --git a/en-US/6.web-odc-user-guide/6.web-odc-use-tools/6.web-odc-sql-plan.md b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/6.web-odc-sql-plan.md
new file mode 100644
index 00000000..758a24af
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/6.web-odc-use-tools/6.web-odc-sql-plan.md
@@ -0,0 +1,38 @@
+# SQL plan
+
+## Background information
+
+OceanBase Developer Center (ODC) can periodically execute SQL scripts created by users to complete database development and O&M tasks as required by the users. For example, ODC can periodically execute stored procedures, backup, and database and table schema synchronization.
+
+This topic describes how to create and manage SQL plan in ODC.
+
+## Create an SQL plan
+
+1. After logging in to ODC, click the target connection to enter the corresponding database object management page.
+
+2. In the top navigation bar, click **Tools** > **SQL Plan** .
+
+
+3. In the **Create SQL Plan** panel, specify the following information.
+
+ 
+
+ | **Item** | **Description** |
+ |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | SQL Content | You can specify SQL content in either of the following ways:
**SQL Entry**: This is the default way to specify SQL content. You can directly write the SQL script in the editing area.
The maximum size of the SQL statements that can be entered in the SQL window is limited to 10 MB. If the content to be entered is more than 10 MB in size, you can directly upload an attachment.
You can click **IN Value Conversion** to convert the batch copied data into the in('A','B') format.
Column values are separated with line breaks.
Row values are separated with spaces or tabs.
**Upload File**: Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it.
You can upload up to 500 files. The total file size cannot exceed 256 MB.
By default, files are sorted by the order in which they were uploaded. You can drag and drop them to change the order. Tasks are executed in the file order.
Only SQL files suffixed with .sql are supported.
|
+ | Delimiter | The delimiters are supported. |
+ | Query Result Limit | You can set the maximum number of rows allowed in the query result. Value range: 1 to 1000000. |
+ | Execution Timeout Value | Specify the value in the **Execution Timeout Value** field in hours. Default value: 48. Maximum value: 480. |
+ | Scheduled Period |
You can directly select a predefined option of Every Hour, Every Night, or Every Friday.
You can also set the scheduled execution period in either of the following modes:
Default: You can set the scheduled execution period on a daily, weekly, or monthly basis as needed. 
Custom: You can set the scheduled execution period by specifying the second, minute, hour, day, month, or week as needed. 
|
+ | Task Settings | You can handle task errors in either of the following ways:
Abort Task: This is the default option. When you select this option, the task is aborted if an error occurs when you run the script.
Ignore Error and Continue: When you select this option, the system skips the statement where an error occurs and continues to execute other statements in the script.
|
+ | Remarks (Optional) | You can enter a description of up to 200 characters. |
+
+4. Click **Create** to complete the task application.
+
+
+## References
+
+* [Manage task processes](../4.web-odc-public-resource-management/4.web-odc-task-process.md)
+
+
+* [SQL plans task](../9.web-odc-task-management/9.web-odc-sql-plan-task.md)
diff --git a/en-US/6.web-odc-user-guide/7.web-odc-recycle-bin.md b/en-US/6.web-odc-user-guide/7.web-odc-recycle-bin.md
new file mode 100644
index 00000000..57436945
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/7.web-odc-recycle-bin.md
@@ -0,0 +1,40 @@
+Recycle bin
+================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding database object management page. Click **Recycle Bin** in the upper-right corner to go to the recycle bin page.
+
+
+
+The recycle bin temporarily stores deleted database objects and allows you to search for and restore the deleted objects.
+
+Technically, the recycle bin is a data dictionary table that stores the information about deleted database objects. Deletion here refers to the `DROP` operation. Data that is deleted by the `DELETE` operation will not be moved to the recycle bin. Therefore, an object deleted by the `DROP` operation is not permanently deleted and still occupies storage space. You can use the `PURGE` operation or empty the recycle bin in ODC to release the space.
+
+The following figure shows the recycle bin page.
+
+
+| Column | Description |
+|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Original Name | The name of the deleted object specified by its creator. You can click Original Name to sort the objects by original name in ascending or descending order. |
+| Object Name | The name that ODC gives to the object. Unlike the original name, the object name is never repeated and can uniquely identify an object. |
+| Object Type | The type of the deleted object. |
+| Recycled At | The timestamp when the object was deleted. The timestamps help you track deleted objects with ease. |
+
+
+
+In addition, the navigation bar on the recycle bin page provides buttons with the following features.
+
+
+| Feature | Description |
+|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Clear | Click  to clear the recycle bin so that all the deleted objects in the recycle bin are purged and the storage space is released. |
+| Refresh | Click  to refresh the list of deleted objects in the recycle bin. |
+| Purge | Click  to purge the selected objects from the recycle bin and release the storage space. |
+| Restore | Click  to restore the selected objects from the recycle bin to its original location. |
+| Search | Enter the name of a deleted object in the search box to search for it. |
+| Settings | Click  to specify whether to enable the recycle bin and the Truncate Table feature. * If the recycle bin is enabled, the schema of deleted objects will be moved to the recycle bin. * If the Truncate Table feature is enabled, the data of deleted objects will be retained. |
+| Select All | Click the check box icon  to select or deselect all objects.  |
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/8.web-odc-view-operation-records.md b/en-US/6.web-odc-user-guide/8.web-odc-view-operation-records.md
new file mode 100644
index 00000000..37ef40e0
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/8.web-odc-view-operation-records.md
@@ -0,0 +1,84 @@
+View operation records
+===========================================
+
+This topic describes how to view the history of operation events in OceanBase Developer Center (ODC).
+
+Background
+-------------------------------
+
+You can view operation records in ODC for the following purposes:
+
+* Security compliance: A variety of features provided by operation records help you make sure that operations in your system meet security and compliance requirements.
+
+
+
+* Real-time monitoring: You can monitor business operations related to public connections in real time through operation records.
+
+
+
+* Event tracing: Database behaviors can be periodically compared based on operation records, which helps you locate anomaly points and abnormal behaviors in the database and allows you to trace risks. Besides, with operation records, correlated queries and analysis can be performed based on the database access source, to help you find the exact operator who accesses the database.
+
+
+
+
+
+
+Operation record list
+------------------------------------------
+
+**Note**
+
+
+
+You can view your own operation records in this list.
+
+Operation records are retained permanently.
+
+1. On the Database Management page of ODC, click **Operating Records** in the top navigation bar.
+
+ 
+
+
+2. The **Operating Records** tab is displayed.
+
+ 
+ * You can click the refresh icon  to manually refresh the list.
+
+
+
+ * You can select an option from **Performed At** to filter the operation records by time. Operation records in the last 7 days, 15 days, 30 days, 6 months, or a custom time range can be queried.
+
+ The following table describes the basic information displayed in the operation record list.
+
+
+ | Field | Description |
+ |------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Event Type | The type of the operation event. The following types of operation events are supported: personal settings, password management, connection management, script management, database operations, organization configuration, member management, resource group management, data mocking, database changes, import, export, and task processes. You can click the filter icon  to filter the operation records by event type. |
+ | Event Operation | The operation performed in the event. You can click the filter icon  to filter the operation records by event operation. |
+ | Connection | The name of the connection to which the operation belongs. You can click the search icon  to search for the connection to which the operation belongs. |
+ | IP Address | The IP address. You can click the search icon  to search for the IP address. |
+ | Performed At | The time when the operation was performed. By default, the operation records are sorted by execution time. The latest record is displayed at the top. You can click the icon  to sort the operation records in ascending or descending order. |
+ | Execution Result | The execution result. Valid values: **Succeeded** and **Failed** . You can click the filter icon  to filter the operation records by execution result. |
+ | Actions | Indicates the actions you can take. Currently, only **View** is available. |
+
+
+
+
+
+
+
+
+
+View operation records
+-------------------------------------------
+
+In the operation record list, click **View** in the **Actions** column. The **Record Details** panel appears.
+
+
+
+You can view the details of the record in the following columns: **Operation Type** , **Event Operation** , **IP Address** , **Operation Rules** , **Performed At** , and **Result** .
+
+Related information
+----------------------------------------
+
+For more information about how to manage the operation records, see **Manage operation records** in the chapter for the public resource console.
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/1.web-odc-task-management-overview.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/1.web-odc-task-management-overview.md
new file mode 100644
index 00000000..274f77a9
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/1.web-odc-task-management-overview.md
@@ -0,0 +1,29 @@
+Overview
+=============================
+
+OceanBase Developer Center (ODC) provides various **tools** for you to generate tasks. You can view the status and information of tasks in Task Center.
+
+After you log on to ODC and enter the management page of a database connection, click **Task** in the navigation bar in the upper part of the page to open the **Task Center** page, where you can view the information about the tasks.
+
+This chapter describes task management features in different topics.
+
+* [Import tasks](../9.web-odc-task-management/2.web-odc-import-tasks.md)
+
+
+
+* [Export tasks](../9.web-odc-task-management/3.web-odc-export-tasks.md)
+
+
+
+* [Data mocking tasks](../9.web-odc-task-management/4.web-odc-data-mocking-tasks.md)
+
+
+
+* [Database Change](../9.web-odc-task-management/5.web-odc-database-change-task.md)
+
+
+* [Apply for Permission](../9.web-odc-task-management/6.web-odc-apply-for-permissions-task.md)
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/2.web-odc-import-tasks.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/2.web-odc-import-tasks.md
new file mode 100644
index 00000000..ae0251cd
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/2.web-odc-import-tasks.md
@@ -0,0 +1,100 @@
+Import tasks
+=================================
+
+After you create a batch or single table import task in OceanBase Developer Center (ODC), you can view the task in the task list on the **Import** tab of the **Task Center** panel.
+
+Task list
+------------------------------
+
+> **Note**
+> The task list displays the tasks in the last 48 hours. ODC allows you to run up to three import tasks in parallel, while subsequent tasks wait in the queue.
+
+On the management page of the database connection, click **Task Center** in the top navigation bar to open the Task Center panel. Click **Import** to display the list of import tasks.
+
+
+
+The following table describes the columns in the task list. You can filter and sort tasks by some of the columns.
+
+
+| Column | Description |
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Task ID | The ID of the import task. |
+| Task Type | The task type specified when the task was created. The following task types are supported: import, export, data mocking, and database change. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter the tasks by connection. |
+| Database | The database to be changed. You can click the search icon  to search for the database to which the task belongs. |
+| Creator | The user who created the import task. You can click the search icon  to search for the creator. |
+| Creation Time | The date and time when the task was generated. |
+| Task Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | The actions you can take. Valid values: **View** , **Approve/Reject** , **Abort** , and **Download** . - View: Click this button to go to the task details page to view the **task information** and **task logs**. - Approve/Reject: Click this button to approve or reject a running task. - Abort: Click this button to abort a running task. - Download: Click this button to download the exported file to your local device when the task is complete. |
+
+
+
+Create an import task
+------------------------------------------
+
+
+
+1. Log on to ODC and go to the management page of the target connection. In the top navigation bar, click **Task Center** . In the Task Center panel, choose **All Tasks** \> **Import** \> **Create Import Task** and create an import task.
+
+
+
+2. In the **Create Import Task** panel, specify the fields described in the following table.
+
+
+
+ | Field | Description |
+ |-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Connection | The name of the database connection to which the task belongs. |
+ | Database | The database to be changed. |
+ | Operation Mode | Select **Automatically Perform after Approval** or **Manually Perform after Approval** . |
+ | Import Format | Select **SQL Files** or **ZIP Files** . |
+ | Import File | Upload the file to be imported. Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool toupload it. |
+ | Encoding Standard | Select the character set from the drop-down list of **Encoding Standard** . |
+ | Import Content | You must specify this item when you select ZIP Files for **Import Format** . ODC currently supports **Import Data Only** , **Import Schema Only** , and **Import Schema and Data** **.** |
+ | Data Format | You must specify this item when you select ZIP Files for **Import Format** . ODC only supports importing data in CSV format and SQL format. For more information about formats, see [Export and import formats](../6.web-odc-use-tools/1.web-odc-data-export-and-import/2.web-odc-export-and-import-formats.md). |
+ | Import Data Settings | If you specify ZIP Files for **Import Format** and Import Schema Only for **Import Content** , this step is not required. |
+ | Task Error Handling Method | Specify **Task Error Handling Method** . ODC supports two error handling methods: **Abort Task** and **Ignore Error and Continue** . You need to select the handling method under the **Task Error Handling Method** label. |
+ | Sys Tenant Account Settings | Configure **Sys Tenant Account Settings** . Select **Use sys Account to Accelerate Import Task** or not. If you select this option, you need to enter the account and password of the SYS tenant in the **Account** and **Password** fields. Then, you can use permissions of this account to import data, which accelerates the import task.
**Notice** - The account and password of a user in the SYS tenant are required. Do not enter @sys#cluster in the Account field. The following figure shows an example.  - To export objects other than tables and views, you must specify the SYS tenant account. - Otherwise, annotations and indexes are not imported or exported.
|
+
+
+
+3. Click **Import** . The import task is created.
+
+
+
+
+
+
+View an import task
+----------------------------------------
+
+### Task information
+
+Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Information** in the upper-right corner of the panel to view the basic task information, information about the imported files, and information about the imported objects.
+
+
+| Item | Description |
+|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic information | Displays the basic information of the task, such as **Task ID** , **Connection** , **Database** , and **Task Type** . |
+| Information about imported files | Displays information that you specified when you created the import task, such as **Import Format** , **Import File** , **Encoding Standard** , **Import Content** , **Data Format** , **Import Data Settings** , **Task Error Handling Method** , **Sys Tenant Account Settings** , and **CSV Settings** , |
+| Information about imported objects | Displays the information of imported objects and the progress of the import task, such as **Object Name** , **Object Type** , **Planned Processing Quantity** , **Actual Processing Quantity** , and **Data Processing Status** . |
+
+
+
+### Task logs
+
+Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Logs** in the upper-right corner of the panel to view the alert logs and all logs of the task.
+
+
+| Field | Description |
+|------------|----------------------------------------------------------------------------------------------------------------------------|
+| All Logs | Displays the **INFO** , **ERROR** , and **WARN** logs of the task. |
+| Alert Logs | Displays the **ERROR** and **WARN** logs of the task. When a task fails, you can view the error message in the alert logs. |
+
+
+In addition, the toolbar provides the following buttons:
+| Action | Description |
+|------|-----------------------------------------------------------|
+| Find | Click this option to find log information. |
+| Download | Click this option to download log information. |
+| Copy | Click this option to copy log information. |
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/3.web-odc-export-tasks.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/3.web-odc-export-tasks.md
new file mode 100644
index 00000000..b635f370
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/3.web-odc-export-tasks.md
@@ -0,0 +1,104 @@
+Export tasks
+=================================
+
+After you create a batch or single table export task in OceanBase Developer Center (ODC), you can view the task in the task list on the **Export** tab of the **Task Center** panel.
+
+
+
+Task list
+------------------------------
+
+> **Note**
+> The task list displays the tasks in the last 48 hours. ODC allows you to run up to three export tasks in parallel, while subsequent tasks wait in the queue.
+
+On the management page of the database connection, click **Task Center** in the top navigation bar to open the **Task Center** panel. Click **Export** to display the task list.
+
+
+
+The following table describes the columns in the task list. You can filter and sort tasks by some of the columns.
+
+
+| Column | Description |
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Task ID | The ID of the export task. |
+| Task Type | The task type specified when the task was created. The following task types are supported: import, export, data mocking, and database change. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter the tasks by connection. |
+| Database | The database to be changed. You can click the search icon  to search for the database. |
+| Creator | The user who created the export task. You can click the search icon  to search for the creator. |
+| Creation Time | The date and time when the task was generated. |
+| Task Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | The actions you can take. Valid values: **View** , **Approve/Reject** , **Abort** , and **Download** . * View: Click this button to go to the Task Details page to view the **task information** and **task logs**. * Approve/Reject: Click this button to approve or reject a running task. * Abort: Click this button to abort a running task. * Download: Click this button to download the exported file to your local device when the task is complete. |
+
+
+
+Create an export task
+------------------------------------------
+
+
+
+1. Log on to ODC and go to the management page of the target connection. In the top navigation bar, click **Task Center** . On the Task Center panel that appears, choose **All Tasks** \> **Export** \> **Create Export Task** and create an export task.
+
+
+
+2. In the **Create Export Task** panel, specify information as described in the following table.
+
+
+
+ | Field | Description |
+ |-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Connection | The name of the database connection to which the task belongs. |
+ | Database | The database to be changed. |
+ | Export Content | When you select ZIP for Export File Format, you must specify this parameter. ODC supports three export modes: **Export Data Only** , **Export Schema Only** , and **Export Schema and Data** **.** |
+ | Data Format | Specify **Data Format** . ODC currently supports exporting data to files in CSV format and SQL format. If you specify **Export Schema Only** for **Export Content** , you can only export data to files in SQL format. For more information about formats, see [Export and import formats](../../7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md). |
+ | Encoding Standard | Specify **Encoding Standard** . ODC supports the following character sets: **ASCII** , **ISO-8859-1** , **GB2312** , **GBK** , **GB18030** , **Unicode (UTF-8)** , **Unicode (UTF-16)** , **Unicode (UTF-32)** , and **BIG5** . You can select one from the **Encoding Standard** drop-down list. |
+ | Export Objects | Specify **Export Objects** . The **Export Objects** tab displays the **Object Name** and **Object Type** of the current table. |
+ | Export Data Settings | If you specify Export Schema Only for **Export Content** , you do not need to complete the export data settings. You need to specify the following fields: * **Use Global Snapshot** : If you select this option, ODC exports the data in the latest global snapshot of the specified table to ensure global data consistency. * **Skipped Data Types** : You can click **Advanced Settings** next to **Export Data Settings** to specify this field. Here, you can specify the data types that you want to skip when you export the data. The data types that can be skipped are different in MySQL and Oracle modes. You can select multiple data types. * Specify information for the CSV format. If you specify the CSV format for **Data Format** and Export Data Only or Export Schema and Data for **Export Content** , you can click **Advanced Settings** next to **Export Data Settings** to specify the following fields: * **Include Column Header** : This option is selected by default to determine whether to include column headers when data is exported in CSV format. * **Convert Empty String to Null Value** : This option is selected by default to determine whether to convert empty strings in the table to NULL values (\\N) when data is exported in CSV format. * **Field Delimiter** : This option specifies the delimiter between fields. The following signs are supported: commas ( **,** ), semicolons ( **;** ), and colons ( **:** ). You can also use a character as the delimiter. * **Text Identifier** : This option specifies the identifier for the text content. Single quotation marks ( **'** ) and double quotation marks ( **"** ) are supported. * **Line Break Sign** : This option specifies the sign for the line break. The following characters are supported: **\\n** , **\\r** , and **\\r\\n** . |
+ | Sys Tenant Account Settings | Configure **Sys Tenant Account Settings** . Select **Use sys Account to Accelerate Export Task** or not. If you select this option, you need to enter the account and password of the SYS tenant in the **Account** and **Password** fields. Then, you can use permissions of this account to export data, which accelerates the export task. You can access the views under the SYS tenant to obtain the optimal data routing strategy.
**Notice** - The account and password of a user in the SYS tenant are required. Do not enter @sys#cluster in the Account field. The following figure shows an example.  - To export objects other than tables and views, you must specify the SYS tenant account. - Otherwise, annotations and indexes are not imported or exported.
|
+
+
+
+3. Click **Export** . The export task is created.
+
+
+
+
+
+
+View an export task
+----------------------------------------
+
+### Task details
+
+Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Information** in the upper-right corner of the panel to view the basic task information, information about the exported files, and information about the exported objects.
+
+
+| Item | Description |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic information | Displays the basic information of the task, such as **Task ID** , **Connection Name** , **Mode Name** , **Task Type** , **Creation Time** , **Retry Limit** , and **Retry Time** . |
+| Export file information | Displays the information that you specified when you created the export task, such as **Export Content** , **Data Format** , **Encoding Standard** , **Export Data Settings** , **Export Schema Settings** , **Task Error Handling Method** , and **Sys Tenant Account Settings** . |
+| Export object information | Displays the information of exported objects and the progress of the export task, such as **Object Name** , **Object Type** , **Schema Processing Status** , **Total Record Number** , **Processed Data Entries** , and **Data Processing Status** . |
+
+
+
+### Task process
+
+Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Process** in the upper-right corner of the panel to view information related to task initiation, approval, and execution status.
+
+### Task logs
+
+Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Logs** in the upper-right corner of the panel to view the alert logs and all logs of the task.
+
+
+| Field | Description |
+|------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| All Logs | Displays the **INFO** , **ERROR** , and **WARN** logs of the task. |
+| Alert Logs | Displays only the **ERROR** and **WARN** logs of the task. When a task fails, you can view the error message in the alert logs. |
+
+In addition, the toolbar provides the following buttons:
+
+| Action | Description |
+|------|-----------------------------------------------------------|
+| Find | Click this option to find log information. |
+| Download | Click this option to download log information. |
+| Copy | Click this option to copy log information. |
+
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/4.web-odc-data-mocking-tasks.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/4.web-odc-data-mocking-tasks.md
new file mode 100644
index 00000000..7942189c
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/4.web-odc-data-mocking-tasks.md
@@ -0,0 +1,94 @@
+Data mocking tasks
+=======================================
+
+After you create a data mocking task in OceanBase Developer Center (ODC), you can view the task in the task list on the **Mock Data** tab of the **Task Center** panel.
+
+Task list
+------------------------------
+
+On the management page of the target database connection, click **Task Center** in the top navigation bar to open the Task Center panel. Then, click **Mock Data** to display the task list.
+
+
+
+The following table describes the columns in the task list. You can filter and sort tasks by some of the columns.
+
+
+| Column | Description |
+|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Task ID | The ID of the data mocking task. |
+| Task Type | The task type specified when the task was created. The following task types are supported: import, export, data mocking, and database change. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter the tasks by connection. |
+| Database | The database to be changed. You can click the search icon  to search for the database to which the task belongs. |
+| Creator | The user who created the data mocking task. You can click the search icon  to search for the creator. |
+| Creation Time | The date and time when the task was generated. |
+| Task Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | The actions you can take. Valid values: **View** , **Approve/Reject** , **Abort** , and **Download** . * View: Click this button to go to the task details page to view the **task information**, task result, and **task logs**. * Approve/Reject: Click this button to approve or reject a running task. * Abort: Click this button to abort a running task. * Download: Click this button to download the SQL file that corresponds to the mock data to your local device. |
+
+
+
+Create a data mocking task
+-----------------------------------------------
+
+
+
+1. Log on to ODC and enter the management page of the target connection. In the top navigation bar, click **Task Center** . In the Task Center panel that appears, choose **All Tasks** \> **Mock Data** \> **Create Mock Data Task** and create adata mockingtask.
+
+
+
+2. In the **Create Mock Data Task** panel, specify the fields described in the following table.
+
+
+
+ | Field | Description |
+ |----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Connection | The name of the database connection to which the task belongs. |
+ | Database | The database to be changed. |
+ | Table | The table for generating data. In the Mock Data panel, select the table from the drop-down list under **Table** . The drop-down list displays all the tables in the current instance. |
+ | Mock Data Volume | The volume of data to be generated. In the Mock Data panel, set **Mock Data Volume** to specify the desired number of data rows to be generated. The default value is 1000. The system can generate up to 1,000,000 rows of data. You can set the value to an integer between 1 and 1000000. |
+ | Batch Size | The size of data processed in a batch. In the Mock Data panel, set **Batch Size** to specify the number of rows generated that trigger a `COMMIT` operation. The default value is 200. That is, a commit operation is performed once every 200 rows are generated. The maximum value supported is 500. You can set the value to an integer between 1 and 500. |
+ | Empty Table Before Inserting Mock Data | Specifies whether to empty the table before inserting mock data into it. In the Mock Data panel, select Yes or No under **Empty Table Before Inserting Mock Data** to specify whether or not to empty the table before inserting mock data. |
+ | Data Conflict Handling Mode | The data conflict handling mode. In the Mock Data panel, specify **Data Conflict Handling Mode** by selecting a mode from the drop-down list. ODC supports the following modes: * **Ignore** : This option is selected by default. The data conflicting with existing data is not inserted. * **Overwrite** : If a data conflict occurs, the original data is deleted, and the new data is inserted. * **Terminate** : If a data conflict occurs, the data mocking task is terminated. |
+ | Rule Settings | The data generation rules. In the Mock Data panel, the **Rule Settings** table displays **Field Name** and **Field Type** based on the table you selected in step 2. You can specify the data generation rules for the target fields in the **Rule** and **Rule Details** columns. The **Rule** column provides built-in rules based on the field type for you to choose from. The **Rule Details** column displays the detailed information for the rule that you selected. You can click the edit icon to edit the information. |
+
+
+
+3. Click **Submit** . The data mocking task is created.
+
+
+
+
+
+
+View a data mocking task
+---------------------------------------------
+
+### Task information
+
+Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Information** in the upper-right corner of the panel to view the basic task information and the data mocking settings.
+
+
+| Item | Description |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic information | Displays the basic information of the task in the following fields: **Task ID** , **Database** , and **Task Type** . |
+| Data mocking settings | Displays the settings specified when the data mocking task was created in the following fields: **Target Table** , **Mock Data Volume** , **Batch Size** , **Clear Table Before Mock Data Insertion** , **Data Conflict Handling Mode** , **Actual Insertion Records** , **Conflict Records** , **Ignore Insertion** , **Clear Records** , and **Rule Settings** . |
+
+
+
+### Task logs
+
+Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Logs** in the upper-right corner of the panel to view the alert logs and all logs of the task.
+
+
+| Field | Description |
+|------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| All Logs | Displays the **INFO** , **ERROR** , and **WARN** logs of the task. |
+| Alert Logs | Displays the **ERROR** and **WARN** logs of the task. When a task fails, you can view the error message in the alert logs. |
+
+In addition, the toolbar provides the following buttons:
+
+| Action | Description |
+|------|-----------------------------------------------------------|
+| Find | Click this option to find log information. |
+| Download | Click this option to download log information. |
+| Copy | Click this option to copy log information. |
+
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/5.web-odc-database-change-task.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/5.web-odc-database-change-task.md
new file mode 100644
index 00000000..639e0301
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/5.web-odc-database-change-task.md
@@ -0,0 +1,125 @@
+Database change tasks
+==========================================
+
+After you create a database change task in OceanBase Developer Center (ODC), you can view the task in the task list on the **Database Change** tab of the **Task Center** panel.
+
+Task list
+------------------------------
+
+On the management page of the database connection, click **Task Center** in the top navigation bar to open the Task Center panel. Click **Database Change** in the panel to display the task list.
+
+
+
+The following table describes the columns in the task list. You can filter and sort tasks by some of the columns.
+
+
+| Column | Description |
+|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Task ID | The ID of the database change task. |
+| Task Type | The task type specified when the task was created. The following task types are supported: import, export, data mocking, and database change. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter the tasks by connection. |
+| Database | The database to be changed. You can click the search icon  to search for the database to which the task belongs. |
+| Creator | The user who created the database change task. You can click the search icon  to search for the creator. |
+| Creation Time | The date and time when the task was generated. |
+| Task Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | The actions you can take. Valid values: **View** , **Approve/Reject** , **Abort** , **Rollback** , and **Download** . * View: Click this button to go to the task details page to view the **task information**, task result, and **task logs**. * Approve/Reject: Click this button to approve or reject a running task. * Abort: Click this button to abort a running task. * Rollback: Click this button to roll back a completed task. * Download: Click this button to download the exported file to your local device when the task is complete. |
+
+
+
+Create a database change task
+--------------------------------------------------
+
+
+
+1. Log on to ODC and go to the management page of the target connection. In the top navigation bar, click **Task Center** .In the Task Center panel that appears, choose **All Tasks** \> **Database Change** \> **Create Database Change Task** and create a database change task.
+
+
+
+2. In the **Create Database Change Task** panel, specify the fields described in the following table.
+
+
+
+ | Field | Description |
+ |----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Connection | The name of the database connection to which the task belongs. |
+ | Database | The database to be changed. |
+ | SQL Content | Select **SQL Entry** or **Upload File** . * **SQL Entry** : This is the default way to specify SQL content. You can directly write the SQL script in the editing area. **Note** * The maximum size of the SQL statements that can be entered in the SQL window is limited to 500,000 characters. If the SQL script to be executed has more than 500,000 characters, you can upload it in the form of a \*.sql file. * You can click **IN Value Conversion** to convert the batch copied data into the in('A','B') format. * Column values are separated with line breaks. * Row values are separated with spaces or tabs. * **Upload File** : Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it. **Note** * You can upload up to 500 files. The total file size cannot exceed 256 MB. * By default, files are sorted by the order in which they were uploaded. You can drag and drop them to change the order. Tasks are executed in the file order. * Only SQL files suffixed with .sql are supported. |
+ | Rollback Plan | Specify **Rollback Plan** . You can write an SQL script or upload a file to specify the rollback plan. For more information, see the description of SQL Content. |
+ | Delimiter | The delimiters are supported. |
+ | Query Result Limit | You can set the maximum number of rows allowed in the query result. Value range: 1 to 1000000. |
+ | Task Error Handling Method | The database change tool supports two methods to handle task errors: * **Abort Task** : This is the default option. When you select this option, the task is aborted if an error occurs when you run the script. * **Ignore Error and Continue** : When you select this option, the system skips the statement where an error occurs and continues to execute other statements in the script. |
+ | Execution Timeout Value | Specify the value in the **Execution Timeout Value** field in hours. Default value: 48. Maximum value: 480. |
+ | Description | You can enter a description of no more than 200 characters in **Description** . |
+
+
+
+3. Click **Create** . The database change task is created.
+
+
+
+
+
+
+View a database change task
+------------------------------------------------
+
+### Task information
+
+
+
+1. Click **View** in the Actions column of the row where the target task is located. The Task Details panel appears. Click the **Task Information** tab to view **Connection** , **Database** , **SQL Content** , and **Rollback Content** .
+
+
+
+2. You can click **Initiate Again** to initiate the database change task again.
+
+
+
+
+
+
+### Task process
+
+1. Click **View** in the Actions column of the row where the target task is located. The Task Details panel appears. Click the **Task Process** tab to view information at the following nodes: **Initiate Task** , **Approval Node** , **Perform** , and **Complete** .
+
+
+
+2. You can click **Initiate Again** to initiate the database change task again.
+
+
+
+
+
+
+### Execution result
+
+1. Click **View** in the Actions column of the row where the target task is located. The Task Details panel appears. Click the **Result** tab to view the execution success and failure records.
+
+
+
+2. You can click **Initiate Again** to initiate the database change task again.
+
+
+
+
+
+
+### Task logs
+
+1. Click **View** in the Actions column of the row where the target task is located. The task details panel appears. Click **Task Logs** in the upper-right corner of the panel to view the alert logs and all logs of the task.
+
+
+
+ | Field | Description |
+ |------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | All Logs | Displays the **INFO** , **ERROR** , and **WARN** logs of the task. You can click **Find** , **Download** , or **Copy** to search for, download, or copy all logs. |
+ | Alert Logs | Displays the **ERROR** and **WARN** logs of the task. When a task fails, you can view the error message in the alert logs. You can click **Find** , **Download** , or **Copy** to search for, download, or copy alert logs. |
+
+
+
+2. You can click **Initiate Again** to initiate the database change task again.
+
+
+
+
+
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/6.web-odc-partition-scheme-task.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/6.web-odc-partition-scheme-task.md
new file mode 100644
index 00000000..e09922c9
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/6.web-odc-partition-scheme-task.md
@@ -0,0 +1,107 @@
+# Partitioning plan task
+
+
+
+## Background
+
+OceanBase Developer Center (ODC) allows users to apply for permissions on partitioning plans from the administrator of the public resource console.
+
+After a user creates a partitioning plan task in **Task Center**, the administrator can approve the task on the Tasks page in Task Center. The user can view the task information and approval status on the Tasks page in Task Center.
+
+## Task list
+
+> **Note**
+> The task list displays the tasks in the last 48 hours.
+
+After you enter the target database connection, click **Task Center** in the top navigation bar to open the Task Center panel. Click the **Partition Plan** tab to view the partitioning plan tasks.
+
+
+
+The following table describes the columns contained in the task list on this tab. You can filter and sort the tasks in the list.
+
+| **Column** | **Description** |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Task ID | The ID of the task. |
+| Task Type | The type of the task specified when you created the task. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter tasks by connection. |
+| Database | The name of the target database where the task operates. You can click the search icon  to search for tasks of a specific database. |
+| Created By | The user who created the task. You can click the search icon  to search for the creator. |
+| Created At | The date and time when the task was generated. |
+| Task Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | Provides task management operations such as **View**, **Approve/Reject**, and **Abort**.
View: Click this button to go to the task details page to view information about the target task.
Approve/Reject: Click this button to approve or reject the application.
Abort: Click this button to abort a running task.
|
+
+## Create a partitioning plan task
+
+
+
+1. In the Task Center panel that appears, click the **Partition Plan** tab and then the **Create Partition Plan** button to create a partitioning plan task.
+
+
+2. In the **Create a partition plan** panel, specify the following information.
+
+ | **Parameter** | **Description** |
+ |---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Connection | The connection to which the partitioning plan belongs. The default value is the current connection. |
+ | Partition policy | The information about the partitioning strategy. Search for and select a RANGE-partitioned table in the database and edit its partitioning strategy.
You can select **Only tables that are not set are displayed** on the right side of Partition policy to display only tables with no partitioning strategies.
You can also select multiple RANGE-partitioned tables and configure a partitioning strategy for them at a time.
In the **Partition policy** column, click the edit icon and then you can edit the number of partitions to create, partitioning interval, retention period, and naming rules.
|
+ | Remarks (Optional) | Enter the reason for application. |
+
+3. Click **Submit**.
+
+ > **Note**
+ > After you submit the application, the task will automatically match the default partitioning plan task application process in the public resource console.
+ > For more information about task processes, see [Task process management](../../6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md).
+
+
+
+## View a partitioning plan task*
+
+### **Task information**
+
+
+
+1. Click **Task Center** in the top navigation bar, and click the **Partition Plan** tab. In the task list on the tab, click **View** in the Actions column of the target task to view its details.
+
+
+2. In the **Task Details** panel, click the **Task Information** tab and view the basic task information and task settings.
+
+ | Item | Description |
+ |---------|--------------------------------------------------------------------------------|
+ | Basic task information | You can view the task status, task ID, task type, connection, inspection cycle, remarks, creator, and creation time. |
+ | Task settings | You can view the partitioning strategy of the RANGE-partitioned table selected when you created the partitioning plan task. |
+
+3. In the task information panel, click **Initiate Again** in the lower-right corner to initiate the task again.
+
+### **Task Process**
+
+
+
+1. In the **Task Details** panel, click the **Task Process** tab to view information about the task process, including the task initiation information, approval status, execution status, and completion status.
+
+
+2. You can click **Initiate Again** in the lower-right corner of the panel to re-initiate the task.
+
+### Associated records
+
+1. In the **Task Details** panel, click the **Associated Records** tab to view information including the task ID, database, creation time, task status, and supported actions such as view.
+
+2. You can click **Initiate Again** in the lower-right corner of the panel to initiate the task again.
+
+### Task logs
+
+
+
+1. In the **Task Details** panel, click the **Task Logs** tab and view all logs and alert logs of the task.
+
+ | Item | Description |
+ |------|-----------------------------------------------------------------------------------------------------------------------------|
+ | All Logs | Displays the **INFO**, **ERROR**, and **WARN** logs of the task. You can click **Find**, **Download**, or **Copy** to search for, download, or copy all logs. |
+ | Alert Logs | Displays the **ERROR** and **WARN** logs of the task. When a task fails, you can view the error message in the alert logs. You can click **Find**, **Download**, or **Copy** to search for, download, or copy alert logs. |
+
+2. Click **Initiate Again** to initiate the task again.
+
+
+## Related topics
+
+* [Task process management](../../6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md)
+
+* [Create a partitioning plan](../../6.web-odc-user-guide/6.web-odc-use-tools/3.web-odc-partition-scheme.md)
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/7.web-odc-apply-for-permissions-task.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/7.web-odc-apply-for-permissions-task.md
new file mode 100644
index 00000000..9c7b80df
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/7.web-odc-apply-for-permissions-task.md
@@ -0,0 +1,76 @@
+# Permission application tasks
+
+
+## **Background**
+
+OceanBase Developer Center (ODC) allows users to apply for permissions on public connections and allows administrators to manage these applications on the public resource console.
+
+After a user creates a public connection permission application task in **Task Center**, the administrator can approve the task on the **Tasks** page in **Task Center**. The user can view the task information and approval status on the **Tasks** page in **Task Center**.
+
+## **Lists of tasks**
+
+After you enter the target database connection, click **Task Center** in the top navigation bar to open the **Task Center** panel. Click the **Apply for Permission** tab to view the permission application tasks.
+
+
+The following table describes the columns contained in the task list on this tab contain. You can filter and sort the tasks in the list.
+
+| **Column** | **Description** |
+|---------|------------------------------------------|
+| Task ID | The ID of the permission application task. |
+| Task Type | The type of the task specified when you created the task. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter tasks by connection. **Note** A permission application task may involve multiple database connections. Therefore, the connection details are not displayed, and **-** is displayed instead. |
+| Database | The name of the target database where the task operates. You can click the search icon  to search for tasks of a specific database. **Note** A permission application task may involve multiple database connections. Therefore, the connection details are not displayed, and **-** is displayed instead. |
+| Created By | The user whose created the database connection task. You can click the search icon  to search for tasks created by a specific creator. |
+| Created At | The date and time when the task was generated. |
+| Task Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | ODC provides task management options such as **View** and **Approve/Reject**. - View: Click this button to go to the task details page to view the task information and task process. - Approve/Reject: Click this button to approve or reject the application. |
+
+
+## **Create a permission application task**
+
+
+
+1. Log on to ODC. Click **Task Center** in the top navigation bar. In the task panel that appears, choose **All Tasks** > **Apply for Permission** \> **Create Permission Application** to create a permission application task.
+
+2. In the **Apply for Connection Permissions** panel, specify the following information:
+
+ | **Item** | **Description** |
+ |----------|------------------------------|
+ | Select a public connection | Select public connections for the application. - **Select Connections** pane: You can select multiple public connections at a time to apply for permissions on them. - **Selected**: You can clear or delete the selected public connections. - You can search for public connections by connection name, host name, cluster name, or tenant name. |
+ | Permission Type | Select the type of the permission on the target public connections. Valid values: **Read-only** and **Read/Write**. |
+ | Reason for Application (Optional) | Enter the reason for application. |
+
+
+3. Click **Submit** to apply for permissions on the connections.
+
+ > **Note**
+ > After a connection permission application task is created, ODC automatically matches the task with the connection permission application process created by the administrator in the public resource console.
+ > Tasks will be executed based on the priority order set by the administrator in **Set Priority** in the public resource console.
+ > For more information about task processes, see [Task process management](../4.web-odc-public-resource-management/4.web-odc-task-process.md).
+
+## **View a permission application task**
+
+### **Task information**
+
+
+
+1. Click **Task Center** in the top navigation bar, and click the **Apply for Permission** tab. In the task list on the tab, click **View** in the **Actions** column of the target task to view its details.
+
+
+2. In the **Task Details** panel, click the **Task Information** tab to view the basic information and settings of the task, including **Task Status**, **Task ID**, **Task Type**, **Risk Levels**, and **Apply for Public Connection**.
+
+| **Item** | **Description** |
+|----------|--------------------------------------------------------------------------|
+| Basic task information | Displays task information, including **Task Status**, **Task ID**, **Task Type**, **Risk Levels**, **Created By**, and **Created At**. |
+| Information about public connections applied for | Displays the **Connection Name**, **Permission Type**, and **Status** values specified when you created the permission application task. |
+
+
+
+### **Task Process**
+
+
+
+1. In the **Task Details** panel, click the **Task Process** tab to view information about the task process, including the task initiation information, approval status, execution status, and completion status.
+
+
+2. You can click **Initiate Again** in the lower-right corner of the panel to re-initiate the permission application task.
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/8.web-odc-shadow-table-synchronization-task.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/8.web-odc-shadow-table-synchronization-task.md
new file mode 100644
index 00000000..58314664
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/8.web-odc-shadow-table-synchronization-task.md
@@ -0,0 +1,117 @@
+# Shadow table synchronization tasks
+
+## Background
+
+OceanBase Developer Center (ODC) allows you to apply for permissions to create shadow table synchronization tasks from the administrator of the public resource console.
+
+After you create a shadow table synchronization task in **Task Center**, the administrator can approve the task in the task list in **Task Center**, where you can view the task information and approval status.
+
+## Task list
+
+> **Note**
+> The task list displays the tasks created in the last 48 hours.
+
+After you enter the target database connection, click **Task Center** in the top navigation bar to open the **Task Center** panel. Click the **Synchronize Shadow Table** tab to view the shadow table synchronization tasks.
+
+
+
+The following table describes the columns contained in the task list on this tab. You can filter and sort the tasks in the list.
+
+| **Column** | **Description** |
+|---------|----------------------------------------------------------------------------------------------------|
+| Task ID | The ID of the task. |
+| Task Type | The type of the task specified when you created the task. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter tasks by connection. |
+| Database | The name of the target database where the task operates. You can click the search icon  to search for tasks of a specific database. |
+| Created By | The user who created the task. You can click the search icon  to search for tasks created by a specific creator. |
+| Created At | The date and time when the task was generated. |
+| Task Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | The task management actions, including: **View**, **Approve/Reject**, and **Abort**.
View: You can click this button to go to the task details page to view the task information and task process.
Approve/Reject: You can click this button to approve or reject the task.
Abort: You can click this button to abort a running task.
|
+
+
+## Create a shadow table synchronization task
+
+1. On the **Task Center** panel that appears, choose **Synchronize Shadow Table** > **Create Shadow Table Synchronization Project**.
+
+
+2. On the **Create Shadow Table Synchronization Project** panel, specify the following information.
+
+ 1. Select a synchronization object.
+
+ 
+
+
+ | **Field** | **Description** |
+ |---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Database | The database to which the shadow table to be created belongs. You can view the name of the current connection. |
+ | Synchronization Range | The table to be synchronized.
**Partial Tables**: Shadow tables will be created in the current database for the selected tables.
**All Tables**: Shadow tables will be created in the current database for all tables in the source database.
|
+ | Name of Shadow Table | The name of the shadow table, in the format of **prefix** + source table name or source table name + **suffix**. You can use custom prefix or suffix. |
+ | Synchronization Objects | The source tables to be synchronized as shadow tables. You must specify this field when **Synchronization Range** is set to Partial Tables. |
+
+ 2. Analyze the schema of the shadow table.
+
+ 
+
+ | **Field** | **Description** |
+ |---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Synchronized Tables | The **Synchronized Tables** tab displays the source table name, shadow table name, and analysis result. You can click **View** to view the source table schema, shadow table schema, and schema change SQL statement, or click **Skip**, indicating that this shadow table is not synchronized. |
+ | Unsynchronized Tables | The **Unsynchronized Tables** tab displays the source table name, shadow table name, and analysis result. You can click **Undo Skip** to synchronize this shadow table.
**Note**: A skipped table will be displayed on the **Unsynchronized Tables** tab. If a shadow table with the same name and the same schema as the source table already exists, schema synchronization will be skipped.
|
+ | SQL Preview | The SQL statement for schema synchronization. |
+ | Task Settings | Options of **Execution Mode** include:
**Execute Immediately**: The synchronization task is executed immediately.
**Execute On Schedule**: The synchronization task is executed on schedule.
**Abort Task**: If an error occurs during the execution of the synchronization task, the subsequent SQL scripts are interrupted and no longer executed.
**Ignore Error and Continue**: If an error occurs during the execution of the synchronization task, the SQL script with the error is skipped, but subsequent SQL scripts will be executed.
|
+ | Remarks | The business background of the project, such as the change purpose and expected goal. |
+
+3. Click **Submit**.
+
+ > **Note**
+ > After a task is created, the task will automatically match the application process of shadow table synchronization task created by the administrator on the public resource console.
+ > Tasks will be executed based on the priority order set by the administrator in **Set Priority** on the public resource console.
+ > For more information about task processes, see [Task process management](../../6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md).
+
+## View the shadow table synchronization task
+
+### Task information
+
+
+
+1. Click **Task Center** in the top navigation bar, and click the **Synchronize Shadow Table** tab. In the task list on the tab, click **View** in the **Actions** column of the target task to view its details.
+
+2. On the **Task Details** panel, click the **Task Information** tab to view the basic task information and task settings.
+
+ | **Information** | **Description** |
+ |---------|---------------------------------------------------------------------------------------------------------|
+ | Basic information | You can view the status, ID, type, connection, database, execution mode, error handling method, remarks, creator, and creation time of the task. |
+ | Task settings | You can view the tables to be synchronized, tables not to be synchronized, and SQL scripts to be executed. |
+
+
+3. On the **Task Details** panel, click **Initiate Again** in the lower-right corner to initiate the task again.
+
+### **Task Process**
+
+
+
+1. In the **Task Details** panel, click the **Task Process** tab to view information about the task process, including the task initiation information, approval status, execution status, and completion status.
+
+
+2. You can click **Initiate Again** in the lower-right corner of the panel to re-initiate the task.
+
+### Task logs
+
+
+
+1. On the **Task Details** panel, click the **Task Logs** tab to view all logs and alert logs of the task.
+
+ | Item | Description |
+ |------|-----------------------------------------------------------------------------------------------------------------------------|
+ | All Logs | Displays the complete information of all task logs, including **INFO**, **ERROR **, and **WARN** logs. You can click **Search**, **Download**, or **Copy** to search for, download, or copy all logs. |
+ | Alert Logs | Displays the **ERROR** and **WARN** logs of the task. When a task fails, you can view the error message in the alert logs. You can click **Search**, **Download**, or **Copy** to search for, download, or copy alert logs. |
+
+
+2. You can click **Initiate Again** to initiate the task again.
+
+
+
+## Related topics
+
+* [Task process management](../../6.web-odc-user-guide/4.web-odc-public-resource-management/4.web-odc-task-process.md)
+* [Create a shadow table synchronization task](../../6.web-odc-user-guide/6.web-odc-use-tools/6.web-odc-shadow-table-synchronization.md)
\ No newline at end of file
diff --git a/en-US/6.web-odc-user-guide/9.web-odc-task-management/9.web-odc-sql-plan-task.md b/en-US/6.web-odc-user-guide/9.web-odc-task-management/9.web-odc-sql-plan-task.md
new file mode 100644
index 00000000..3e5a0a14
--- /dev/null
+++ b/en-US/6.web-odc-user-guide/9.web-odc-task-management/9.web-odc-sql-plan-task.md
@@ -0,0 +1,90 @@
+# SQL plan task
+
+## Background information
+
+OceanBase Developer Center (ODC) can periodically execute SQL scripts created by users to complete database development and O&M tasks as required by the users. For example, ODC can periodically execute stored procedures, backup, and database and table schema synchronization.
+
+After a user creates an SQL plan task in **Task Center**, the administrator can approve the task on the Tasks page in Task Center. The user can view the task information and approval status on the Tasks page in Task Center.
+
+This topic describes how to create and manage SQL plan tasks in ODC.
+
+## Task list
+
+> **Note**
+> The task list displays the tasks created in the last 336 hours.
+
+After you enter the target database connection, click **Task Center** in the top navigation bar to open the Task Center panel. Click the **SQL Plan** tab to view the SQL plan tasks.
+
+
+
+The following table describes the columns contained in the task list on this tab. You can filter and sort the tasks in the list.
+
+| **Column** | **Description** |
+|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| No. | The ID of the task. You can click the search icon  to search for and filter tasks by ID. |
+| Connection | The name of the database connection to which the task belongs. You can click the filter icon  to filter tasks by connection. |
+| Execution Period | - |
+| Next Execution Time | The time when the SQL plan task is to be executed the next time. |
+| Created By | The user who created the task. You can click the search icon  to search for and filter tasks by creator. |
+| Updated At | The date and time when the task was generated. |
+| Status | The current status of the task. ODC provides different management actions for tasks in different states. |
+| Actions | The task management actions, including **View**, **Approve/Reject, Edit**, and **Enable/Disable**.
View: You can click this button to view task information on the task details page.
Approve/Reject: You can click this button to approve or reject the task.
Enable/Disable: You can click this button to enable or disable an ongoing task.
|
+
+
+## Create an SQL plan task
+
+1. In the Task Center panel that appears, click the plus sign (**+**) on the right of **SQL Plan** to create an SQL plan task.
+
+ 
+
+2. In the **Create SQL Plan** panel, specify the following information.
+
+ 
+
+ | **Item** | **Description** |
+ |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | SQL Content | You can specify SQL content in either of the following ways:
**SQL Entry**: This is the default way to specify SQL content. You can directly write the SQL script in the editing area.
The maximum size of the SQL statements that can be entered in the SQL window is limited to 10 MB. If the content to be entered is more than 10 MB in size, you can directly upload an attachment.
You can click **IN Value Conversion** to convert the batch copied data into the in('A','B') format.
Column values are separated with line breaks.
Row values are separated with spaces or tabs.
**Upload File**: Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it.
You can upload up to 500 files. The total file size cannot exceed 256 MB.
By default, files are sorted by the order in which they were uploaded. You can drag and drop them to change the order. Tasks are executed in the file order.
Only SQL files suffixed with .sql are supported.
|
+ | Delimiter | The delimiters are supported. |
+ | Query Result Limit | You can set the maximum number of rows allowed in the query result. Value range: 1 to 1000000. |
+ | Execution Timeout Value | Specify the value in the **Execution Timeout Value** field in hours. Default value: 48. Maximum value: 480. |
+ | Scheduled Period |
You can directly select a predefined option of Every Hour, Every Night, or Every Friday.
You can also set the scheduled execution period in either of the following modes:
Default: You can set the scheduled execution period on a daily, weekly, or monthly basis as needed. 
Custom: You can set the scheduled execution period by specifying the second, minute, hour, day, month, or week as needed. 
|
+ | Task Settings | You can handle task errors in either of the following ways:
Abort Task: This is the default option. When you select this option, the task is aborted if an error occurs when you run the script.
Ignore Error and Continue: When you select this option, the system skips the statement where an error occurs and continues to execute other statements in the script.
|
+ | Remarks (Optional) | You can enter a description of up to 200 characters. |
+
+3. Click **Create** to complete the task application.
+
+ > **Note**
+ > After you submit the application, the task will automatically match the default SQL plan task application process in the public resource console.
+ > For more information about task processes, see [Manage task processes](../4.web-odc-public-resource-management/4.web-odc-task-process.md).
+
+## View SQL plan tasks
+
+### Task information
+
+
+
+1. Click **Task Center** in the top navigation bar, and click the **SQL Plan** tab. In the task list on the tab, click **View** in the Actions column of the target task to view its details.
+
+
+2. In the **Task Details** panel, click the **Task Information** tab to view the basic task information and task settings.
+
+ | **Item** | **Description** |
+ |---------|-------------------------------------------------------------------------------------------------------|
+ | Basic task information | You can view the task status****, task ID****, task type****, connection, ****remarks, creator, and creation time.**** |
+ | Task settings | You can view the SQL content, scheduled execution period, next execution time, delimiter, query result limit, error handling method, and execution timeout period.**************************** |
+
+
+### Execution records
+
+In the **Task Details** panel, click the **Execution Records** tab to view information including the task ID, database, creation time, task status, and supported actions.********************
+
+### Operating records
+
+In the **Task Details** panel, click the **Operating Records** tab and view information including the event operation, operation time, approval status, and supported actions.****************
+
+## References
+
+* [Manage task processes](../4.web-odc-public-resource-management/4.web-odc-task-process.md)
+
+
+* [SQL plans](../6.web-odc-use-tools/6.web-odc-sql-plan.md)
diff --git a/en-US/7.client-odc-user-guide/1.client-odc-install-odc.md b/en-US/7.client-odc-user-guide/1.client-odc-install-odc.md
new file mode 100644
index 00000000..1cda20ca
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/1.client-odc-install-odc.md
@@ -0,0 +1,44 @@
+Install ODC
+================================
+
+To manage your database, you can either access the web-based OceanBase Developer Center (ODC) console from OceanBase, or download the ODC client. Unlike the web-based ODC console that provides a logon portal, the ODC client uses a default user account for user identification. You just need to install the client and [create a connection](7.client-odc-user-guide/../3.client-odc-connect-database/1.client-odc-create-connection.md) to connect to your database.
+
+Recommended installation environment
+---------------------------------------------
+
+
+
+| Item | Requirement |
+|-----------------------|-----------------------------------------------------------------------------------------------------------------|
+| Operating system (OS) | Windows: Windows 7 or Windows 10 Mac: 10.13.6 (17G65) |
+| Java environment | JDK 1.8.0_242 and later. |
+| Port number | Thanks to the dynamic port detection technology, you do not need to reserve port 8989 for ODC V2.3.0 and later. |
+| CPU | X86-64 processor with 2 or more cores. |
+| Memory | 4 GB or above. |
+
+
+
+Procedure
+------------------
+
+1. Download [ODC Client](https://help.aliyun.com/document_detail/212816.html).
+
+
+
+2. Double-click the installation file you downloaded to start the installation.
+
+
+
+3. The setup wizard prompts you to select an installation directory.
+
+
+
+4. When you run the client after installation, it checks the environment. If the environment does not meet the requirements, the client displays an error message, indicating that you can either continue using the application, or end the process to fix the problem of the environment. If ODC passes the environment check and operates normally, you can create a connection.
+ > **Notice**
+ >
JRE installation packages for Mac and 64-bit Windows are included in the installation package of ODC V3.2.0. You can install it as needed.
+ >
For more information about installation or startup failures, see Installation of the ODC client in FAQ.
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/1.client-odc-database-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/1.client-odc-database-objects-overview.md
new file mode 100644
index 00000000..390128c4
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/1.client-odc-database-objects-overview.md
@@ -0,0 +1,42 @@
+Overview
+=============================
+
+A table consists of rows and columns. Each column is called a field, and the title of each column is called the field name. A row contains several columns of information, and a row of data is called a record. A database table consists of one or more records. A table without records is called an empty table. A table usually has one primary key that uniquely identifies each record.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables. You can double-click a table name in the table list to go to the table management page. On this page, you can view and modify the table data on the **Data** tab, and view the basic information, columns, partitions, indexes, constraints, and DDL statements of the table on the **Attribute** tab.
+**Notice**
+
+
+
+The root@sys user privileges are required to view partition information. This requires that you set the root@sys user in Advanced Configuration during connection creation.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.0.0 or a later version |
+| OceanBase Database in MySQL mode | V1.4.1 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on table objects in ODC.
+
+* [Create a table](../1.client-odc-table-objects/2.client-odc-create-a-table.md)
+
+
+
+* [Table list](../1.client-odc-table-objects/3.client-odc-table-list.md)
+
+
+
+* [Manage table attributes](../1.client-odc-table-objects/4.client-odc-manage-table-attributes.md)
+
+
+
+* [Manage table data](../1.client-odc-table-objects/5.client-odc-manage-table-data.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/2.client-odc-create-a-table.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/2.client-odc-create-a-table.md
new file mode 100644
index 00000000..6c0af892
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/2.client-odc-create-a-table.md
@@ -0,0 +1,258 @@
+# Create a table
+
+ODC supports visualized table creation. This topic describes how to create a table with ODC.
+
+## Overview
+
+OceanBase Developer Center (ODC) allows you to create a table on a GUI. This topic describes how to create a table in the ODC console.
+
+
+
+As shown in the preceding figure, you can create a table in the following seven steps:
+
+1. Specify the basic information.
+
+2. Set columns.
+
+3. Set the index.
+
+4. Set constraints.
+
+5. Set partitioning rules.
+
+6. Confirm the SQL statement.
+
+7. Complete the table creation.
+
+
+
+
+
+
+## Procedure
+
+In the following example, a table named `employee` is created in the ODC console. The table contains the **emp_no**, **birthdate**, **name**, and **gender** columns. Perform the following operations:
+
+### Step 1: Specify the basic information
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables. To create a table, click **+** in the upper-right corner of the table list or click **Create** in the top navigation bar.
+
+In the **Basic Info** section, specify **Table Name** and **Description**.
+
+
+
+> **Note**
+>
In MySQL mode, you also need to specify **Default Character Set** and **Default Sorting Rule**.
+>
After you specify the basic information and switch to the **Column** step, the basic information is submitted.
+
+### Step 2: Set columns
+
+The following figure and table show the information that you need to specify when you add a column.
+
+
+
+
+
+| Field | Description |
+|---------------|--------------------------------------------------------------------|
+| Name | The name of the column. |
+| Type | The data type of the column. For more information about data types, see [OceanBase Database Developer Guide](https://www.oceanbase.com/docs/enterprise/oceanbase-database/oceanbase-database/V3.2.3/data-type-overview). |
+| Length | The length of the data type. |
+| Scale | The number of decimal places of the data type. |
+| Non-empty | Specifies whether the value of the column must be specified. |
+| Auto-increment | Specifies whether to set the column to an auto-increment column. This parameter is valid in MySQL mode. **Notice** Only one auto-increment column is allowed for each table. After a column is set to an auto-increment column, the auto-increment checkbox of other columns cannot be selected. |
+| Virtual Column | Specifies whether to set the column to a virtual column. **Notice** When you set a virtual column, you must specify its expression. When you create a virtual column, you must define an expression that the virtual column depends on. A virtual column is a generated column. A generated column can be a virtual generated column or a stored generated column. The value of a virtual column is calculated based on the expression only when the column is used. Therefore, when you insert data into the table, you cannot specify values for the virtual column. |
+| Default Value/Expression | The default value or expression of the column. |
+| Comment | The additional information about the column. |
+
+
+
+The following table describes operations that you can perform on the column setting page.
+
+| Operation | Description |
+|--------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| Toolbar operations | You can add or delete columns by using the top toolbar of the page. |
+| Click a row ID | - You can click a row ID to select the row and display the quick access toolbar that allows you to add or delete a row. - You can click a row ID to select the row, and then drag the row to adjust its order. |
+| Right-click a row | You can right-click a row to select it, and then select **Copy** or **Move Down** from the context menu that appears. |
+
+
+> **Note**
+>
After you copy a row, you can paste the row by using the Command + V or Ctrl + V shortcut keys.
+>
The auxiliary editing section at the bottom of the page displays additional information about the selected column.
+>
Settings in the Basic Information and Column steps are required. Settings in other configuration steps are optional. After you specify settings in the Basic Information and Column steps, you can click Commit and Confirm SQL Statement to create a table.
+
+
+### Step 3: Set indexes
+
+If a table contains a large amount of data, you can use indexes to accelerate data queries. An index is a data structure that pre-sorts the values of one or more columns in a table. By using indexes, you can directly locate records that meet the conditions.
+
+The following figure and table show the information that you need to specify when you set the index.
+
+
+
+| Field | Description |
+|------|--------------------------------------------------------------------------------|
+| Index Name | The name of the index. |
+| Scope | The default value is **GLOBAL**. Valid values: **GLOBAL** and **LOCAL**. |
+| Method | The default value is **BTREE**, which is applicable to a global index. Valid values: **Empty, BTREE, and HASH**. - A BTREE index stores data in a B+ tree structure, and is suitable for searching for SQL statements in the specified index scope. - A HASH index is implemented based on a HASH table, and is used only when the query conditions exactly match all columns in the HASH index. A HASH index can be used only for query conditions that use the equal operator (=), IN operator, or NULL-safe equal operator (<=>). A HASH index cannot be used for sorting and is not suitable for columns with less distinctive values, such as the gender column. |
+| Index Type | The default value is **NORMAL**. Valid values: **NORMAL, UNIQUE**, and **FULLTEXT**. - **NORMAL** indicates a normal index. - **UNIQUE** indicates a unique index that does not allow duplicate values, such as the **emp_no** column. - **FULLTEXT** indicates a full-text index, which is used to search a table that contains a large amount of data. |
+| Columns | The columns to be indexed. Pay attention to the order of the indexed columns. |
+| Invisible | Specify whether the index is invisible. |
+
+
+
+The index setting page provides the following icons.
+
+| Icon | Description |
+|-----|------------|
+| Create | Click this icon to add an index. |
+| Delete | Click this icon to delete the selected index. |
+
+
+
+### Step 4: Set constraints
+
+Constraints are used to specify data rules for a table. A data operation that violates the constraints will be terminated.
+
+
+
+ODC supports the following four table constraints:
+
+* **Primary Key Constraint**: defines a primary key to uniquely identify each row of data in the table. A primary key constraint can be a field or a group of fields. You can set only one primary key constraint for a table, and you cannot edit the constraint after it is configured.
+
+* **Unique Constraint**: ensures that the data in a field or a group of fields is unique in the table. You can set multiple unique constraints in one table.
+
+* **Foreign Key Constraint**: associates one or more columns in two tables. A foreign key constraint is used to maintain the data consistency and integrity between associated tables. After you complete the setting of foreign key constraints, you cannot create new constraints or edit existing constraints.
+
+* **Check Constraints**: checks the data in the database based on the configured check rules when you edit the data. Data modification is allowed only after the check is passed.
+
+
+OceanBase Database supports different constraints in MySQL and Oracle modes, and different constraints require different information. Therefore, you need to specify the required information based on the constraint you selected and the requirements on the page.
+
+
+| Field | Description |
+|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Constraint Name | The name of the constraint. |
+| Column Information | The field or a group of fields specified as the constraint. |
+| Associated Schema | The schema where the associated table is located when **Foreign Key Constraint** is used. The associated table is the parent table. This field is valid only in Oracle mode. |
+| Associated Database | The database where the associated table is located when **Foreign Key Constraint** is used. The associated table is the parent table. This field is valid only in MySQL mode. |
+| Associated Table | The associated table when **Foreign Key Constraint** is used. The associated table is the parent table. |
+| Associated Field | The associated field when **Foreign Key Constraint** is used. The associated field is in the parent table. |
+| Delete | Specifies the action to be performed on the current table when the data in the associated table is deleted. The current table is the child table, and the associated table is the parent table. The following four types of action are supported: **CASCADE**, **NO ACTION**, **RESTRICT**, and **SET NULL**. OceanBase Database supports different foreign key actions in MySQL and Oracle modes. - In MySQL mode, OceanBase Database allows you to specify **CASCADE**, **NO ACTION, RESTRICT**, and **SET NULL**. - In Oracle mode, OceanBase Database allows you to specify **CASCADE**, **NO ACTION**, and **SET NULL**.
**Notice** At present, OceanBase Database does not support **SET NULL**. For more information about the syntax, see [Create a table](https://www.oceanbase.com/docs/enterprise-oceanbase-database-cn-10000000000357139), or the official documentation of MySQL or Oracle. |
+| Update | Specifies the action to be performed on the current table when the data in the associated table is updated. The current table is the child table, and the associated table is the parent table. The following four types of action are supported: **CASCADE**, **NO ACTION**, **RESTRICT**, and **SET NULL**. OceanBase Database supports different foreign key actions in MySQL and Oracle modes. - In MySQL mode, OceanBase Database allows you to specify **CASCADE**, **NO ACTION, RESTRICT**, and **SET NULL**. - In Oracle mode, OceanBase Database allows you to specify **NO ACTION**. **Notice** At present, OceanBase Database does not support **SET NULL**. For more information about the syntax, see [Create a table](https://www.oceanbase.com/docs/enterprise-oceanbase-database-cn-10000000000357139), or the official documentation of MySQL or Oracle. |
+| Check Condition | Specifies the check rules for data verification when **Check Constraint** is enabled. |
+
+The constraint setting page provides the following icons.
+
+
+| Icon | Description |
+|-----|------------|
+| Create | Click this icon to add a constraint. |
+| Delete | Click this icon to delete the selected constraint. |
+
+### Step 5: Set partitioning rules
+
+
+
+You can partition a table that contains a large amount of data. After a table is partitioned, data in the table is stored in multiple tablespaces. The database does not scan the entire table for a query.
+
+* In MySQL mode, OceanBase Database supports the following six partitioning methods: **Key**, **Hash**, **Range**, **Range Columns**, **List**, and **List Columns**.
+
+
+
+* In Oracle mode, OceanBase Database supports the following three partitioning methods: **List**, **Range**, and **Hash**.
+
+ The definition of a partition in MySQL mode is different from that in Oracle mode. So, the values of the following fields vary in different modes. You need to specify the following fields based on the selected partitioning method.
+
+ | Field | Description |
+ |------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Partitioning Method | Specifies the partitioning method. The partitioning methods supported in MySQL mode are different from those in Oracle mode. - Range partitioning: Multiple rows with column values in an ordered, continuous, and non-overlapping range are assigned to a partition. - List partitioning: A table is partitioned based on the enumeration values. - Hash partitioning: A table is partitioned based on a given number of partitions. For a table that stores data without a clear pattern or range, you can use hash partitioning to randomly distribute values of the partition column to different partitions based on the HASH algorithm. - Key partitioning: This partitioning method is similar to HASH partitioning. The difference is that key partitioning only supports computation of one or more columns, and the MySQL server provides its own hash function. At least one INT type column is required for Key partitioning. For more information about partitioning, see [Overview](https://www.oceanbase.com/docs/enterprise/oceanbase-database-cn/V3.2.3/10000000000357153). |
+ | Field | The column that is used as the partition key. |
+ | Expression | Partitions are divided based on the return value of the expression. The partition expression is not supported in Oracle mode. |
+ | Partition | Based on the value specified for **Partitioning Method**, you may need to specify information such as **Partition Name**, **Partition Quantity**, **Upper Limit**, and **Value Enumeration**. You can add multiple partitions and drag selected fields to adjust their order. |
+
+
+
+
+
+
+### Step 6: Confirm the SQL statement
+
+
+
+After you click **Submit**, you can view the statement on the SQL Confirmation page. To view lengthy clauses, click **SQL Check** and **Format** in the lower-right corner of the page.
+
+Syntax:
+
+```sql
+CREATE TABLE table_name (column_name column_type, column_name column_type,.......);
+```
+
+
+
+Parameters
+
+| Parameter | Description |
+|-------------------------|----------------------------------------|
+| CREATE TABLE | The key word that indicates the creation ofa table with a specified name. You must have the privileges to create tables. |
+| table_name | The name of the table. The table name must conform to the identifier naming rules. |
+| column_name column_type | The name and data type of the column in the table. To create multiple columns, separate the tuple with commas (,). |
+
+
+
+### Step 7: Complete the table creation
+
+Click **Execute**. After the table is created, the **employee** table appears in the table list in the left-side navigation pane.
+
+
+
+> **Note**
+> To manage a table, right-click the table name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View Table Structure**, **View DDL**, **View Table Data**, **CreateTable**, **Import**, **Export**, **Download**, **Mock Data**, **Open SQL Window**, **Copy**, **Rename**, **Delete**, and **Refresh**.
+
+For more information, see [Manage table data](../1.client-odc-table-objects/5.client-odc-manage-table-data.md).
+
+You can use the `SELECT` statement to query data in the new table.
+
+Syntax:
+
+```sql
+SELECT
+ column_name,
+ column_name
+FROM
+ table_name [WHERE Clause] [LIMIT N] [ OFFSET M]
+```
+
+
+
+Parameters
+
+| Parameter | Description |
+|-------------|------------------------------------------------------|
+| SELECT | The key word that indicates the name of the statement. You can use the SELECT statement to read one or more records. |
+| column_name | The name of the column to be queried. You can use an asterisk (\*) to query all columns |
+| WHERE | The key word of the condition clause. |
+| LIMIT | The number of records to be returned. |
+| OFFSET | The data offset from which the SELECT statement starts to query. The default offset is 0. |
+
+
+
+Example:
+
+```sql
+SELECT `emp_no`, `birthdate`, `name`, `gender` FROM `employee`;
+```
+
+
+
+
+
+## Related topics
+* [Create a view](../2.client-odc-view-objects/2.client-odc-create-a-view.md)
+* [Create a function](../3.client-odc-function-objects/2.client-odc-create-a-function.md)
+* [Create a stored procedure](../4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md)
+* [Create a program package](../6.client-odc-package-objects/2.client-odc-create-a-program-package.md)
+* [Create a trigger](../7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md)
+* [Create a type](../8.client-odc-type-objects/2.client-odc-create-a-type.md)
+* [Create a synonym](../9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md)
\ No newline at end of file
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/3.client-odc-table-list.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/3.client-odc-table-list.md
new file mode 100644
index 00000000..6c60ade2
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/3.client-odc-table-list.md
@@ -0,0 +1,45 @@
+Table list
+===============================
+
+
+
+Overview
+-----------------------------
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables.
+
+The table list displays the table objects in the current database. In the table list, you can view the **structure tree** of an object. You can also right-click the target object to perform some **management actions** on the object.
+
+Structure tree
+-----------------------
+
+You can click the expand icon before the name of the target table in the table list, and the structure tree of the table is displayed in a drop-down list, as shown in the following figure. The structure tree of a table can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section. In this section, you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------
+
+The names of table objects support ascending example by head character by default in the table list.
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+
+| Action | Description |
+|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Table Structure | Click this option to go to the Attribute tab. On this tab, you can view comprehensive information of the table such as the basic information, columns, indexes, constraints, and DDL statements. |
+| View DDL | Click this option to go to the Attribute tab to view the SQL statements that define the table.|
+| View Table Data | Click this option to go to the Data tab to view the data in the table. |
+| Create Table | Click this option to go to the table creation page, where you can create a table as prompted. |
+| Single Table Import | Click this option to import data to the table. For more information, see [Single table export and import](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md). |
+| Single Table Export | Click this option to export data from the table. For more information, see [Single table export and import](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md). |
+| Download | Download the SQL file for the table object. |
+| Mock Data | Click this option to go to the Mock Data panel. |
+| Open SQL Window | Click this option to open a new SQL window. |
+|Copy|Click this option to copy the table name, SELECT statement, INSERT statement, UPDATE statement, or DELETE statement. |
+| Rename | Click this option to rename the table. |
+|Delete | Click this option to delete the table. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the table, so that the structure tree displays the latest information. |
+| View Column/View Index/View Constraint | Click these options to go to the Attribute tab to view specific information about the columns, indexes, or constraints in the table. |
+| Create Column/Create Index/Create Constraint | Click these options to create a column, an index, or a constraint. |
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/4.client-odc-manage-table-attributes.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/4.client-odc-manage-table-attributes.md
new file mode 100644
index 00000000..ac8ebb01
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/4.client-odc-manage-table-attributes.md
@@ -0,0 +1,184 @@
+Manage table attributes
+============================================
+
+
+
+Overview
+-----------------------------
+
+
+
+1. After you log on to OceanBase Developer Center (ODC), click the name of the target connection on the ODC homepage to go to the corresponding connection management page.
+
+
+
+2. In the left-side navigation pane, click **Table** to get a list of tables.
+
+
+
+3. Double-click the name of a table in the table list to go to the table management page.
+
+
+
+4. Click **Attribute** in the top navigation bar to go to the Attribute tab.
+
+ The Attribute tab displays the following table attributes:
+
+ * **Basic information**
+
+
+
+ * **Column**
+
+
+
+ * **Index**
+
+
+
+ * **Constraints**
+
+
+
+ * **Partition**
+
+
+
+ * **DDL**
+
+
+
+
+
+
+
+
+
+Basic information
+--------------------------------------
+
+
+
+In the left-side navigation pane of the **Attribute** tab, click **Basic Info** to view the basic information about the table.
+
+
+| Field | Description |
+|-----------------------|-------------------------------------------------------------------------------------------------------------------------|
+| Table Name | Displays the name of the table. You can modify the table name here. |
+| Default Character Set | Displays the character set that the table uses. |
+| Default Sorting Rule | Displays the sorting rule that the table uses. |
+| Description | Displays the description that you specified when you created the table. You can also modify the table description here. |
+|Row data volume|Displays the number of rows.|
+|Size|Displays the data size.|
+
+
+
+The basic information page provides the following buttons.
+
+
+| Button | Description |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Edit | Click  to modify the basic information. |
+| Refresh | Click  to refresh the basic information. |
+
+
+
+Column information
+---------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Column** to view the columns in the table. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to add a field (or column) to the table. |
+| Delete | Click  to delete the selected field. |
+| Refresh | Click  to refresh the field information. |
+| Filter | Click  (to the right of **Field Name** ) to filter or search for fields. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.|
+
+
+
+Index information
+--------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Index** to view the indexes on the table. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to add an index to the table. |
+| Delete | Click  to delete the selected index. |
+| Refresh | Click  to refresh the index information. |
+| Filter | Click  (to the right of **Index Name** ) to filter or search for indexes. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.An index cannot be modified after it is created. |
+
+> **Note**
+> An index cannot be modified after it is created.
+
+Constraint information
+-------------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Constraint** to view the constraints on the table. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to add a constraint to the table. |
+| Delete | Click  to delete the selected constraint. |
+| Refresh | Click  to refresh the constraint list. |
+|Filter|  (to the right of **Name** ) to filter or search for constraints. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.|
+
+
+> **Note**
+>
The buttons provided vary with the constraint method. If a button is dimmed out or not present in the navigation bar, it means that the constraint method does not support the corresponding action.
+>
To view foreign key constraints on a table, you can query the `all_constraints` view in Oracle mode, or the information_schema.key_column_usage table in MySQL mode since OBServer V2.2.6.
+>
OceanBase Database supports constraint checking only in Oracle mode.
+
+
+
+
+
+
+Partition information
+------------------------------------------
+
+
+
+In the left-side navigation pane of the Attribute tab, click **Partition** to view the information about the partitions in the table. The information includes **Partition Name** , **Order** , **Partitioning Method** , **Expression** , **Upper limit of the range** , and **Enumeration Value** . In Oracle mode, **Expression** indicates the partitioning key. **Partitioning Method** indicates the partitioning method specified when the table was created. The information displayed varies with the partitioning method. The navigation bar also provides the following buttons.
+
+
+| Button | Description |
+|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click + to create a partition from an undefined range. |
+| Delete | Click  to delete the selected partition and destroy the data in the partition. |
+| Refresh | Click  to refresh the partition list. |
+| Filter | Click  to filter partitions by partition name, order, partitioning method, expression, or upper limit of the range. |
+|Export|Click the export icon in the upper right corner to export single table data.For details, please refer to the Single table export and import.|
+
+
+> **Note**
+> In ODC V3.3.0 and later versions, you can view the partitions of table objects not necessarily under the SYS tenant.
+
+
+
+DDL information
+------------------------------------
+
+
+
+In the left-side navigation pane of the **Attribute** tab, click **DDL** to view the DDL statements that define the table. You cannot edit these statements. Click  in the toolbar to view the statements.
+
+| Button | Description |
+|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Format | Click [Format](https://help-static-aliyun-doc.aliyuncs.com/assets/img/en-US/4411843561/p412851.jpg) to format the statements. |
+| Download | Click Download to download the statements. |
+| Refresh | Click  to refresh the statement. |
+|Export|Click the export icon in the upper right corner to export single table data. For details, please refer to the Single table export and import.|
\ No newline at end of file
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/5.client-odc-manage-table-data.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/5.client-odc-manage-table-data.md
new file mode 100644
index 00000000..0ce0b0e4
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/1.client-odc-table-objects/5.client-odc-manage-table-data.md
@@ -0,0 +1,135 @@
+Manage table data
+======================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Table** in the left-side navigation pane to get a list of tables. Double-click the name of a table in the table list to go to the table management page. Click the **Data** button in the navigation bar on the top of the page to go to the Data tab, where you can view, add, modify, and delete table data.
+**Notice**
+
+
+
+In ODC, connections to the same database share the same session. In ODC V2.3.2 and later versions, auto-commit is turned off by default in Oracle mode, so you need to manually commit transactions. You can modify the value of the autocommit parameter on the **Session Properties** page to change this setting. For more information, see [Session management](../../9.client-odc-session-management.md).
+
+
+
+View data
+------------------------------
+
+On the Data tab, ODC displays data in the form of a table. The navigation bar provides the following buttons for you to view and manage the data:
+
+* **Enable Editing** : Click this button to enable the editing mode so that you can edit the data in the table.
+
+
+
+* **Commit** : Auto-commit is turned off by default in Oracle mode, so you need to click this button to commit the current transaction. After you click this button, a dialog box appears, indicating that the current connection uses a shared session and the commit will apply to all windows. Click **Yes** to apply the commit. In MySQL mode, auto-commit is turned on by default, so this button is not displayed.
+
+
+
+* **Rollback** : Auto-commit is turned off by default in Oracle mode. You can click this button to roll back the current transaction. After you click this button, a dialog box appears, indicating that the current connection uses a shared session and the rollback will apply to all windows. Click **Yes** to apply the rollback. In MySQL mode, auto-commit is turned on by default, so this button is not displayed.
+
+
+
+* **Refresh** : Click this button to refresh the data in the table.
+
+
+
+* **Column Mode** : Click this button to display the data in the selected rows in the form of a table. On the **Column Mode** page, you can switch to the previous or next row. The column mode makes it easier to view data in a row that has many columns.
+
+
+
+* **Columns** : Click this button to select the columns to be displayed on the page.
+
+
+
+* **Back to Start** : Click this button to jump to the first page.
+
+
+
+* **Previous** : Click this button to go to the previous page.
+
+
+
+* **Next** : Click this button to go to the next page.
+
+
+
+* **Jump to Bottom** : Click this button to jump to the last page.
+
+
+
+* **Display Data Volume** : Click this button to set the maximum number of rows to be displayed on a page.
+
+
+
+* **Export** : Click this button to export the data in the table. You can specify the type of the exported file, the character set, and the number of rows to be exported. The file type can be CSV or SQL, and the character set can be GBK or UTF8. You can export up to 10,000 rows from a result set.
+
+
+
+* **Mock Data** : Click this button to mock data in the table. For more information, see [Data mocking](../../5.client-odc-use-tools/2.client-odc-data-mocking.md).
+
+
+
+
+
+
+Edit data
+------------------------------
+
+Click **Enable Editing** in the navigation bar on the Data tab to enter the editing mode, as shown in the following figure. ODC use different colors to mark data in different states. New data is marked in green, deleted data in red, and modified data in orange.
+
+
+
+In editing mode, the navigation bar provides the following buttons for you to edit data in the table:
+
+* **Add Row** : Click this button to insert an empty row to the table. Double-click a cell to insert data to it. ODC provides the verification feature and related tools to help you insert data in a more convenient way. For example, if the current cell is of the date type, ODC displays a calendar for you to select the to-be-inserted date from.
+
+
+
+* **Delete Row** : Click this button to delete the selected rows from the table.
+
+
+
+* **Copy Current Row** : Click this button to copy the selected rows in the table.
+
+
+
+* **Column Mode** : Click this button to display the data in the selected rows in the form of a table. On the **Column Mode** page, you can switch to the previous or next row. The column mode makes it easier to view data in a row that has many columns.
+
+
+
+* **Columns** : Click this button to select the columns to be displayed on the page.
+
+
+
+* **Back to Start** : Click this button to jump to the first page.
+
+
+
+* **Previous** : Click this button to go to the previous page.
+
+
+
+* **Next** : Click this button to go to the next page.
+
+
+
+* **Jump to Bottom** : Click this button to jump to the last page.
+
+
+
+* **Display Data Volume** : Click this button to set the maximum number of rows to be displayed on a page.
+
+
+
+* **Cancel** : Click this button to exit the editing mode.
+
+
+
+* **Confirm Modification** : Click this button to generate the SQL statement for the action. After you verify the statement, click **Execute** to apply the data modification. If auto-commit is turned on, the transaction is automatically committed after you click this button.
+
+
+
+* **Modify and Submit** : Auto-commit is turned off by default in Oracle mode, so you need to click this button to commit the current transaction. After you click this button, a dialog box appears, indicating that the current connection uses a shared session and the commit will apply to all windows. Click **Yes** to apply the commit. In MySQL mode, auto-commit is turned on by default, so this button is not displayed.
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/1.client-odc-view-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/1.client-odc-view-objects-overview.md
new file mode 100644
index 00000000..1eb15622
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/1.client-odc-view-objects-overview.md
@@ -0,0 +1,29 @@
+Overview
+=============================
+
+A view is a virtual table created based on one or more tables or views. The tables on which the view is based are called base tables. Views do not store data. You can use views to query and modify data in base tables. Therefore, the definition of a view is stored in the data dictionary, and no data copy related to the view definition is stored in the database. Views are similar to physical tables in the database, so you can perform operations on views like on tables. When you modify data in a view, you are actually modifying data in base tables. Conversely, the modification of data in base tables is also reflected in views generated based on these base tables.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click View in the left-side navigation pane to get a list of views. In the view list, you can double-click a view name to go to the view management page. On this page, you can check the data of the view on the Data tab or the attributes such as the basic information, columns, and DDL statements of the view on the Attribute tab.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.0.0 or a later version |
+| OceanBase Database in MySQL mode | V1.4.1 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on view objects in ODC.
+
+* [Create a view](../2.client-odc-view-objects/2.client-odc-create-a-view.md)
+
+
+
+* [Manage views](../2.client-odc-view-objects/3.client-odc-manage-views.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/2.client-odc-create-a-view.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/2.client-odc-create-a-view.md
new file mode 100644
index 00000000..1e604a10
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/2.client-odc-create-a-view.md
@@ -0,0 +1,199 @@
+# Create a view
+
+ODC supports visualized view creation. This topic describes how to create a view with ODC.
+
+## Overview
+
+A view is a virtual table that consists of data in one or more tables. You can use the `SELECT` statement to query a view. A view itself does not contain data.
+
+### Purposes of views
+
+* Simplifies data queries: You can use views to combine data from different tables in a database into a single virtual table, and thereby convert multi-table queries into a single-table query.
+
+
+
+* Controls data access: You can use views to present certain data to specific users. These users can view only the data in a specific view.
+
+
+
+
+
+As shown in the preceding figure, you can create a view in the following five steps:
+
+1. Specify the basic information.
+
+
+
+2. Select base tables.
+
+
+
+3. Select fields.
+
+
+
+4. Verify the SQL statement.
+
+
+
+5. Complete the view creation.
+
+
+
+
+
+
+## Procedure
+
+In the following example, an employee salary view is created in the OceanBase Developer Center (ODC) console. The salary view consists of the name field in the employee table and the budget and dept_name fields in the consumer table. Procedure:
+
+### Step 1: Specify the basic information.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **View** in the left-side navigation pane to get a list of views. To create a view, click **+** in the upper-right corner of the view list or click **Create** in the top navigation bar.
+
+In the **Basic Info** section, specify **View Name** and **Check Item**.
+
+* **View Name**: specifies the name of the view.
+
+
+
+* **Check Item**: specifies the constraints on the input data. OceanBase Database in Oracle mode supports only the read-only mode. Default value: **None**.
+
+
+
+
+
+
+
+
+After you specify all the basic information, click **OK**.
+
+After the basic information is specified, you can either click **Next: Verify SQL Statement** to go to Step 4 and verify the SQL statement, or proceed to Step 2 and select base tables.
+
+### Step 2: Select base tables.
+
+After you specify the basic information, you can proceed to Step 2 and select base tables, or skip this step.
+
+In the **Select Base Tables** section, the list on the left displays available base tables in the hierarchy of schema > database > table/view. You can search for base tables in this list. Select tables or views in this base table list, and click the add icon (>) next to the list to add the selected tables or views to the table operation area on the right.
+
+
+
+In the table operation area, you can perform the following operations on a selected base table.
+
+
+| Operation | Description |
+|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Set an alias | You can set an alias for a selected base table. Click **\** next to the table name in the table operation area and enter the alias. This operation is optional. |
+| Set association relationships | When two or more tables exist in the table operation area, you can define an association relationship between the tables. The default association is **JOIN**. You do not need to set an association relationship for the last table. Click the  icon next to Alias and select an association relationship. Supported options: **JOIN**, **INNER JOIN**, **LEFT JOIN**, **RIGHT JOIN**, **CROSS JOIN**, **FULL JOIN**, **UNION**, **UNION ALL**, **INTERSECT**, **MINUS**, **LEFT OUTER JOIN**, **RIGHT OUTER JOIN**, and **FULL OUTER JOIN**. |
+| Adjust the association order | You can drag the base tables in the table operation area to reorder them. If you drag a table to the bottom of the list, the association relationships of this table are removed. |
+| Delete a base table | You can click the delete icon next to a table in the table operation area to delete it from the table operation area. After you delete a table, its associations with the next table are removed. |
+
+
+
+After you select and configure the base tables, click **OK**.
+
+### Step 3: Select fields.
+
+After you select the base tables, you can proceed to Step 3 and select fields. If you skip Step 2, this step is unavailable.
+
+In the **Select Fields** section, the list on the left displays the fields of the base tables that you selected in Step 2 in the hierarchy of schema > database > table/view. You can search for fields in this list. Select fields in the field list, and click the add icon (>) next to the list to add the selected fields to the field operation area on the right.
+
+
+
+In the field operation area, you can perform the following operations on a selected field.
+
+
+| Operation | Description |
+|--------|-----------------------------------------------------------|
+| Set an alias | You can set an alias for a selected field. Click **\** next to the field name in the field operation area and enter the alias. This operation is optional. |
+| Adjust the association order | You can drag the fields in the field operation area to reorder them. |
+| Delete a field | You can click the delete icon next to a field in the field operation area to delete it from the operation area. |
+| Customize fields | Click **+Custom** in the upper-right corner of the field operation area to add a field to the operation area. You must specify a name and an alias for the field. |
+
+
+
+After you select and configure the fields, click **OK**.
+
+### Step 4: Verify the SQL statement.
+
+After you complete all the previous steps, click **Next: Verify SQL Statement** to go to the statement editing page.
+
+
+
+On the statement editing page, the view definition statements are generated based on the information specified in the **Basic Info**, **Select Base Tables**, and **Select Fields** sections. When two or more tables are included, you must complete the statement according to the relationship between the tables and logical conditions. After you complete the statements, click **Create** in the upper-right corner of the page to create the view.
+
+You can edit the SQL statements of the created view on the Create View page. Syntax:
+
+```sql
+CREATE VIEW view_name AS
+SELECT
+ column1,
+ column2.....
+FROM
+ table_name
+WHERE
+ [condition];
+```
+
+
+
+In addition, the toolbar on the editing page provides the following buttons.
+
+
+| Button | Description |
+|-------|--------------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | Click this button and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+|IN Value Conversion|A format such as A B can be converted to ('A','B') format.|
+| Previous | Click this button to go back to the **Create View** page, where you can continue to edit or modify the parameters in the **Basic Info**, **Select Base Tables**, and **Select Fields** sections. |
+
+
+
+### Step 5: Complete the view creation.
+
+Click **Create** in the upper-right corner to create the view. After a view is created, you can use the `SELECT` statement to query it, just like how you query a table.
+
+
+
+> **Note**
+> To manage a view, right-click the view name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Delete**, **Download**, and **Copy**.
+
+For more information, see [Manage views](../2.client-odc-view-objects/3.client-odc-manage-views.md).
+
+Syntax:
+
+```sql
+SELECT
+column1,
+column2.....
+FROM
+table_name;
+```
+
+
+
+Example:
+
+```sql
+SELECT `name`, `budget`, `department_name` FROM `salary`;
+```
+
+
+
+
+
+## Related topics
+
+* [Create a table](../1.client-odc-table-objects/2.client-odc-create-a-table.md)
+* [Create a function](../3.client-odc-function-objects/2.client-odc-create-a-function.md)
+* [Create a stored procedure](../4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md)
+* [Create a program package](../6.client-odc-package-objects/2.client-odc-create-a-program-package.md)
+* [Create a trigger](../7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md)
+* [Create a type](../8.client-odc-type-objects/2.client-odc-create-a-type.md)
+* [Create a synonym](../9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md)
\ No newline at end of file
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/3.client-odc-manage-views.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/3.client-odc-manage-views.md
new file mode 100644
index 00000000..7e66185c
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/2.client-odc-view-objects/3.client-odc-manage-views.md
@@ -0,0 +1,53 @@
+Manage views
+=================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **View** in the left-side navigation pane to get a list of views in the current database.
+
+In the view list, you can view the **structure tree** of an object. You can also right-click the target object to perform some **management actions** on the object. You can also double-click the name of the target view to go to the view management page, which includes the **Attribute and Data tabs** .
+
+Structure tree
+-----------------------
+
+You can click the expand icon before the name of the target view in the view list, and the structure tree of the view is displayed in a drop-down list, as shown in the following figure. The structure tree of a view can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section, where you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------
+
+The names of view objects support ascending example by head character by default in the view list.
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Option | Description |
+|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Check View Properties | Click this option to go to the **Attribute** tab, where you can view comprehensive information such as the basic information, columns, and code of the view. |
+| Check View Data | Click this option to go to the **Data** tab, to check data in the view. |
+| Create View | Click this option to go to the Create View page, where you can create a view as prompted. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the view object. |
+| Copy | Click this option to copy the object name, SELECT statement, INSERT statement, UPDATE statement, or DELETE statement. |
+| Delete | Click this option to delete the current view object. |
+
+
+
+Attribute and Data tabs
+--------------------------------
+
+
+
+* Attribute tab:
+
+ * **Basic Info** : displays information such as **View Name** , **Check Item** , and **Created By** .
+
+
+
+ * **Column** : displays information of the base table corresponding to the view, such as **Field Name** , **Data Type** , and **Comment** .
+
+
+
+ * **Code** : displays the definition script of the view.
+
+
+
+* Data tab: displays the columns that the view contains.
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/1.client-odc-functin-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/1.client-odc-functin-objects-overview.md
new file mode 100644
index 00000000..2507bfad
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/1.client-odc-functin-objects-overview.md
@@ -0,0 +1,29 @@
+Overview
+=============================
+
+A function defines a collection of SQL statements. You can call a function in an SQL statement to get a return value from the execution.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click Function in the left-side navigation pane to get a list of functions. In the function list, double-click the name of a function to go to the function management page, where you can view the basic information, parameters, and data definition language (DDL) statements of the function.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.0.0 or a later version |
+| OceanBase Database in MySQL mode | V2.0.0 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on function objects in ODC.
+
+* [Create a function](../3.client-odc-function-objects/2.client-odc-create-a-function.md)
+
+
+
+* [Manage functions](../3.client-odc-function-objects/3.client-odc-manage-functions.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/2.client-odc-create-a-function.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/2.client-odc-create-a-function.md
new file mode 100644
index 00000000..b6f2d21b
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/2.client-odc-create-a-function.md
@@ -0,0 +1,200 @@
+# Create a function
+
+ODC supports visualized function creation. This topic describes how to create a function with ODC.
+
+## Overview
+
+A function is a subprogram defined in a database. You can call functions by using built-in SQL statements. If the built-in functions cannot meet your business requirements, OceanBase Developer Center (ODC) allows you to create functions. User-defined functions not only help you perform some calculations and special operations, but also reduce coding redundancy to improve the program readability.
+
+A function is a procedural object that is similar to a stored procedure in a database. Like a stored procedure, a function is a code snippet of SQL statements and procedural statements, and can be called by applications and other SQL statements.
+
+Differences between a user-defined function and a stored procedure:
+
+* A function returns only one result and is suitable for data processing that generates one result. A stored procedure may return zero or multiple results and is suitable for batch insertion and batch update.
+
+* You can call a function by using a `SELECT` statement. You can call a stored procedure by using a `CALL` statement.
+
+
+
+As shown in the preceding figure, you can create a function in the following six steps:
+
+1. Specify the function name.
+
+2. Specify the data type of the return value.
+
+3. Specify parameters.
+
+4. Verify the parameters of the new function.
+
+5. Edit the function.
+
+6. Complete the function creation.
+
+## Procedure
+
+In the following example, a function named function_emp is created in the ODC console to obtain the employee name from an employee table based on the employee ID. The function_emp function contains an INT type id parameter. Procedure:
+
+### Step 1: Specify the function name.
+
+Log on to the ODC console and click the name of a connection to go to the corresponding connection management page. You can click **Function** in the left-side navigation pane to get a list of functions. To create a function, click + in the upper-right corner of the function list or click **Create** in the top navigation bar.
+
+
+
+### Step 2: Specify the data type of the return value.
+
+For more information about data types, see [OceanBase Database Developer Guide](https://www.oceanbase.com/docs/enterprise/oceanbase-database/oceanbase-database/V3.2.3/data-type-overview).
+
+### Step 3: Specify parameters.
+
+1. Parameters specify the information passed to a function when the function is called.
+
+ * In Oracle mode, specify the following fields: **Name**, **Mode**, **Type**, and **Default Value**.
+
+
+
+ * In MySQL mode, specify the following fields: **Name**, **Type**, and **Length**.
+
+
+
+
+
+
+2. You can specify parameters by using one of the following three methods.
+
+
+
+| Method | Description |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| Use the quick access toolbar | In the quick access toolbar, you can add, delete, and move up and down parameters. |
+| Click the row number | - You can click a row number to select a row and display the quick access toolbar that allows you to delete the row or move the row up or down. - You can click a row number to select the row, and then drag the row to adjust its order. |
+| Right-click | Right-click the mouse to select the entire row, copy row or move down the row. |
+
+
+3. You need to specify the mode for the parameters.
+
+ The parameter mode setting is unavailable in MySQL mode. The Oracle mode supports the following parameter modes: **IN**, **OUT**, and **INOUT**.
+
+
+| **Parameter** | **Type** |
+|--------|-------------------------------------------------------------------|
+| IN | Indicates an input parameter. When a function is called, the input parameter is passed to the function and used in the execution of the function. |
+| OUT | Indicates an output parameter. When a function is called, the value of the output parameter is ignored and an empty value is passed to the function. The output parameter in the function body can be modified. The modified result is returned and passed to the argument that the output parameter represents. |
+| INOUT | Indicates an inout parameter. An inout parameter is both an input parameter and an output parameter. |
+
+
+ > **Note**
+ > In Oracle mode, both functions and stored procedures support IN, OUT, and INOUT modes. In MySQL mode, functions support only IN mode, and stored procedures support IN, OUT, and INOUT modes.
+
+
+
+
+
+### Step 4: Verify the parameters of the new function.
+Click **OK** to go to the Create Function page.
+
+### Step 5: Edit the function.
+
+
+
+Edit the function statement on the Create Function page.
+You can edit the SQL statements of the created function on the Create Function page. Syntax:
+
+```sql
+CREATE FUNCTION < function name > ([ [ , ] ] …)
+RETURNS < type >
+< function body >
+```
+
+
+
+Parameters
+
+
+| Parameter | Description |
+|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| \< function name \> | The name of the user-defined function. **Notice** The name of a user-defined function cannot be the same as that of a stored procedure. |
+| \< parameter \>\< type \> | Parameters of the function. This field contains only the name and type. You cannot specify the IN, OUT, or INOUT keyword. |
+| RETURNS\< type \> | The data type of the return value. `` specifies the data type of the return value. **Notice** The SELECT statement in a RETURN VALUE statement returns only a single-row and single-column value. |
+| \< function body \> | The body of the user-defined function. The function body must contain a `RETURN ` statement, where `` specifies the return value of the user-defined function. |
+
+
+
+Example:
+
+```sql
+CREATE FUNCTION `function_emp` ( `id` int(45)) RETURNS VARCHAR(300)
+
+-- The start of the function body.
+BEGIN
+
+-- Declare a variable.
+DECLARE
+ a VARCHAR(300);
+
+-- Assign a value to the variable.
+SELECT
+ name INTO a
+FROM
+ employee
+WHERE
+ emp_no = id;
+
+-- The return value.
+RETURN a;
+
+-- The end of the function body.
+END
+```
+
+
+
+### Step 6: Complete the function creation.
+
+Click **Create** in the upper-right corner to create the function. After a user-defined function is created, you can use the `SELECT` statement to call it, just like how you call a built-in function.
+
+> **Note**
+> To manage a function, right-click the function name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Edit**, **Compile**, **Debug**, **Run**, **Download**, **Delete**, and **Refresh**. **Edit** , **Compile** , and **Debug** are not supported in MySQL mode.
+> For more information, see [Manage functions](../3.client-odc-function-objects/3.client-odc-manage-functions.md).
+
+Syntax:
+
+```sql
+SELECT ([ [,...]])
+```
+
+
+
+Example:
+
+```sql
+SELECT function_emp(2);
+```
+
+
+
+* MySQL mode
+
+ 
+
+
+* Oracle mode
+
+ 
+
+
+ > **Notice**
+ > - In Oracle mode, if a user-defined function contains an OUT parameter, you must call the function by using the `CALL` statement.
+ > - A yellow icon in the function list indicates an error or alert.
+
+
+
+## Related topics
+
+[Create a table](../1.client-odc-table-objects/2.client-odc-create-a-table.md)
+[Create a view](../2.client-odc-view-objects/2.client-odc-create-a-view.md)
+[Create a stored procedure](../4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md)
+[Create a sequence](../5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md)
+[Create a program package](../6.client-odc-package-objects/2.client-odc-create-a-program-package.md)
+[Create a trigger](../7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md)
+[Create a type](../8.client-odc-type-objects/2.client-odc-create-a-type.md)
+[Create a synonym](../9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md)
\ No newline at end of file
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/3.client-odc-manage-functions.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/3.client-odc-manage-functions.md
new file mode 100644
index 00000000..8e4be135
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/3.client-odc-function-objects/3.client-odc-manage-functions.md
@@ -0,0 +1,90 @@
+Manage functions
+=====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Function** in the left-side navigation pane to get a list of functions.
+
+In the function list, you can view the **structure tree** of an object, or right-click the target object to perform some **management actions** on the object. You can also double-click the name of the target function to go to the **function management page**.
+
+Structure tree
+-----------------------
+
+You can click the expand icon before the name of the target function in the function list, and the structure tree of the function is displayed in a drop-down list, as shown in the following figure. The structure tree of a function can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section. In this section, you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------
+
+The names of function objects support ascending order by the head character by default in the function list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create function. |
+| Filter | Click this option to display valid/invalid functions. |
+| Batch Compile | Click this option to batch compile the function object. Including: compile all objects and compile invalid objects.  |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the function, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+After you right-click an item in the structure tree, a shortcut menu appears and displays some actions that you can take to manage the item. The following table describes the management actions in details:
+
+
+| Action | Description |
+|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View | Click this option to go to the function management page. On this page, you can view comprehensive information such as the basic information, parameters, and code of the function. |
+| Create | Click this option to go to the Create Function page, where you can create a function as prompted. |
+| Edit | Click this option to go to the function management page, which displays the statements that define the function and where you can edit the function. |
+| Compile | Click this option to compile the function. |
+| Debug | Click this option to go to the debugging page. On this page, you can debug the function.
**Note**
We recommend that you upgrade to OBServer V2.2.77 or later. This is because some versions of OBServer have been found with PL/SQL debugging issues, which may compromise the OBServer stability.
ODC V3.2.2 or earlier does not support the debugging feature when you connect ODC to the target instance by using OBProxy. To use the debugging feature, directly connect ODC to the target instance.
ODC V3.2.2 and later support PL/SQL debugging when you connect to OBServer by using OBProxy.
ODC V4.0.0 and later support setting the parameter value as DEFAULT, NULL or empty string.
|
+| Run | Click this option to execute the function. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the function object. |
+| Delete | Click this option to delete the function. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the function, so that the structure tree displays the latest information. |
+
+
+Function management page
+---------------------------------------------
+
+
+
+You can double-click the name of the target function in the function list to go to the function management page. The function management page displays the following information:
+
+
+| Section | Description |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This section displays the basic information about the function in fields such as **Function Name** , **Return Type** , and **Created By** . |
+| Parameter | This section displays the information about the parameters in fields such as **Name** , **Order** , **Mode** , **Data Type** , and **Default Value** . Click the  icon to refresh the parameters. |
+| DDL | This section displays the script that defines the function and provides the **Edit**, **Download**, **Find**, and **Refresh** icons. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
+Function editing page
+------------------------------
+
+Right-click the target item in the function list. In the menu that appears, click **Edit** to go to the function editing page. In the code area of the editing page, the statements that define the function are displayed. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+| Button | Description |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Confirm Modification | Click this button to apply the current modification. |
+| Compile | Click this button to compile the statements on the current page. |
+| Run | Click this button to execute the statements in the code area. |
+| Debug | Click this button to go to the debugging page, where you can debug the PL object in the code area. |
+| Format | Click this button to apply the formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All C** **aps** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+| IN Value Conversion | Click this button to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format. * Column values are separated with line breaks. * Row values are separated with spaces or tabs. |
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/1.client-odc-stored-procedure-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/1.client-odc-stored-procedure-objects-overview.md
new file mode 100644
index 00000000..b82493da
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/1.client-odc-stored-procedure-objects-overview.md
@@ -0,0 +1,46 @@
+Overview
+=============================
+
+In a database system, a stored procedure is a collection of SQL statements for implementing a specific action. A stored procedure is stored in the database, and can be reused after it is compiled.
+
+Functions and stored procedures are similar in definition. Both are a collection of SQL statements. They have the following differences:
+
+* A function normally returns a value, whereas a stored procedure does not return values.
+
+
+
+* You can embed a function in an SQL statement. For example, you can call a function in a `SELECT` statement. However, usually a stored procedure is independently executed.
+
+
+
+* Functions have more limits than stored procedures. In general, stored procedures implement more complex features, whereas a function implements a more specific feature.
+
+
+
+
+
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Stored Procedure** in the left-side navigation pane to get a list of stored procedures. In the stored procedure list, you can double-click the name of a stored procedure to go to the stored procedure management page, where you can view the basic information, parameters, and data definition language (DDL) statements of the stored procedure.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.0.0 or a later version |
+| OceanBase Database in MySQL mode | V2.0.0 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on stored procedure objects in ODC.
+
+* [Create a stored procedure](../4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md)
+
+
+
+* [Manage stored procedures](../4.client-odc-stored-procedure-objects/3.client-odc-manage-stored-procedures.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md
new file mode 100644
index 00000000..879a9009
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md
@@ -0,0 +1,223 @@
+# Create a stored procedure
+
+ODC supports visualized stored procedure creation. This topic describes how to create a stored procedure with ODC.
+
+## Overview
+
+A stored procedure is a collection of one or more statements. To perform a series of complex operations on a database, you can use a stored procedure to encapsulate these complex operations into a reusable code block in the database. It helps developers reduce their workload.
+
+In OceanBase Database, a stored procedure is a collection of SQL statements for implementing a specific feature. After you compile and store a stored procedure in the database, you can specify the stored procedure name and the required parameters to call this stored procedure for accelerated execution of the SQL statements.
+
+A stored procedure can contain parameters and return values.
+
+### Differences between a stored procedure and a function
+
+* The return value of a function is a specific result value, while the return value of a stored procedure only indicates whether the execution is successful.
+
+
+
+* You can call a function by using a `SELECT` statement. You can call a stored procedure by using a `CALL` statement.
+
+
+
+
+
+
+### Benefits of stored procedures
+
+* Improve the versatility and portability of the application: After you create a stored procedure, it can be repeatedly called by a program without rewriting the SQL statements of the procedure. In addition, stored procedures can be modified with no impact on the program source code, thereby improving the portability of the program.
+
+
+
+* Accelerate SQL execution: If an operation involves a large amount of SQL statements or repeated execution of the same SQL statements, you can compile the code into a stored procedure and execute the stored procedure, which is faster than separately executing the statements.
+
+
+
+* Alleviate the workload of the server: If one SQL statement is called at a time to perform operations on the database objects, a large number of SQL statements are transmitted. If an equivalent stored procedure, only the command for calling the procedure is sent, thereby reducing the network load.
+
+
+
+
+
+
+
+As shown in the preceding figure, you can create a stored procedure in the following five steps:
+
+1. Specify the name of the stored procedure.
+
+2. Specify parameters.
+
+3. Verify the parameters of the stored procedure.
+
+4. Edit the parameters of the stored procedure.
+
+5. Complete the stored procedure creation.
+
+## Procedure
+
+In the following example, a stored procedure named proc_total is created in the ODC console for the calculation of department budgets. The stored procedure contains two INT type input parameters budget_r and budget_s and calculates the sum of the two parameters. Procedure:
+
+### Step 1: Specify the name of the stored procedure.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Stored Procedure** in the left-side navigation pane to get a list of stored procedures. To create a stored procedure, click **+** in the upper-right corner of the Stored Procedure list or choose **Create** > **Stored Procedure** in the top navigation bar.
+
+In the **Create Stored Procedure** dialog box, enter a name for the stored procedure.
+
+
+
+### Step 2: Specify parameters.
+
+1. Parameters specify the information passed to a function when the function is called.
+
+ * In Oracle mode, specify the following fields: **Name**, **Mode**, **Type**, and **Default Value**.
+
+
+
+ * In MySQL mode, specify **Name**, **Mode**, **Type**, and **Length**.
+
+
+
+
+
+
+2. You can specify parameters by using one of the following three methods.
+
+
+
+| Method | Description |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| Use the quick access toolbar | In the quick access toolbar, you can add, delete, and move up and down parameters. |
+| Click the row number | - You can click a row number to select a row and display the quick access toolbar that allows you to delete the row or move the row up or down. - You can click a row number to select the row, and then drag the row to adjust its order. |
+| Right-click | - Copy a row or move one row down: Drag the pointer to select a row, right-click it, and then select Copy or Move Down from the context menu that appears. - Copy a cell: Select a cell, right-click it, and then select Copy from the context menu that appears. |
+
+> **Note**
+>
+> After copying a row, you can select a row and paste the copied row data with the shortcut keys Command + V / Ctrl + V.
+
+
+3. You need to specify the mode for the parameters.
+
+ OceanBase Database in both MySQL mode and Oracle mode supports the following parameter modes: **IN**, **OUT**, and **INOUT**.
+
+ ```sql
+ CREATE PROCEDURE proc_name ([[IN |OUT |INOUT ] parameter_name parameter_type...])
+ ```
+
+
+ * Parameters
+
+
+
+| **Parameter** | Type |
+| ------------- | ------------------------------------------------------------ |
+| IN | Indicates an input parameter. When a stored procedure is called, the input parameter is passed to the stored procedure and used in the execution of the stored procedure. Usually, input parameters are only used to pass values in, and are not modified or returned in the call of a stored procedure. |
+| OUT | Indicates an output parameter. When a stored procedure is called, the value of an output parameter is ignored and an empty value is passed to the stored procedure. The value of the output parameter is modified during the execution of the stored procedure. After the execution is complete, the modified value is assigned to the output parameter. Usually, output parameters are used to obtain the execution results of a stored procedure. Output parameters can be used to modify and return values in the call of a stored procedure. |
+| INOUT | Indicates an inout parameter. An inout parameter is both an input parameter and an output parameter. |
+
+ * Parameter settings
+
+
+
+| Property | Required | Default | Mode |
+| ------------- | -------- | ------- | ------------ |
+| Name | Yes | Empty | Oracle/MySQL |
+| Mode | Yes | IN | Oracle/MySQL |
+| Type | Yes | VARCHAR | Oracle/MySQL |
+| Length | Yes | 45 | MySQL |
+| Default value | No | Empty | Oracle |
+
+
+
+
+
+
+
+### Step 3: Verify the parameters of the stored procedure.
+
+Click **OK** to go to the Create Stored Procedure page.
+
+### Step 4: Edit the stored procedure.
+
+
+
+Edit the statements on the Create Stored Procedure page.
+
+In addition, the toolbar on the editing page provides the following buttons.
+
+
+| Button | Description |
+|-------|----------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | Click this button and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+
+
+
+You can edit the SQL statements of the created stored procedure on the Create Stored Procedure page. Syntax:
+
+```sql
+CREATE PROCEDURE proc_name (
+ [proc_parameter[,...]])
+IS
+BEGIN
+proc_body:
+ Valid SQL routine statement
+END [end_label]
+```
+
+
+
+Parameters
+
+
+| Parameter | Description |
+|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| proc_name | The name of the stored procedure. By default, a stored procedure is created in the current database. To create a stored procedure in a specific database, add the database name as the prefix to the name of the stored procedure in the format of db_name.sp_name. **Notice** The name of a stored procedure must differ from that of any built-in MySQL function. Otherwise, an error may occur. |
+| [proc_parameter[,…] ] | The list of stored procedure parameters. A parameter is specified in the format of `[IN|OUT|INOUT] parameter_name parameter_type`. `parameter_name` specifies the parameter name and `parameter_type` specifies the parameter type, which can be any valid MySQL data type. If you need to specify multiple parameters, separate them with commas (,). A stored procedure can be created without a parameter. In this case, add a pair of parentheses after the name of the stored procedure. **Notice** The parameter names must differ from the column names in the data table. Otherwise, the SQL statements of the stored procedure may take a parameter name as a column name, which results in errors. |
+| proc_body | The body of the stored procedure, which contains the SQL statements to be executed when the stored procedure is called. The body begins with **BEGIN** and ends with **END**. If the body contains only one SQL statement, you can omit the BEGIN and END flags. |
+
+
+
+### Step 5: Complete the stored procedure creation.
+
+Click **Create** in the upper-right corner to create the stored procedure. After a stored procedure is created, you can use the `CALL` statement to call it, just like how you call a built-in function.
+
+
+
+> **Note**
+> To manage a stored procedure, right-click the stored procedure name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Edit**, **Run**, **Download**, **Delete**, and **Refresh**.
+
+For more information, see [Manage stored procedures](../4.client-odc-stored-procedure-objects/3.client-odc-manage-stored-procedures.md).
+
+Syntax:
+
+```sql
+CALL proc_name ([proc_parameter [,...]]);
+```
+
+
+
+Example:
+
+```sql
+CALL proc_total (30000, 20000);
+```
+
+
+
+
+
+## Related topics
+
+* [Create a table](../1.client-odc-table-objects/2.client-odc-create-a-table.md)
+* [Create a view](../2.client-odc-view-objects/2.client-odc-create-a-view.md)
+* [Create a function](../3.client-odc-function-objects/2.client-odc-create-a-function.md)
+* [Create a sequence](../5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md)
+* [Create a program package](../6.client-odc-package-objects/2.client-odc-create-a-program-package.md)
+* [Create a trigger](../7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md)
+* [Create a type](../8.client-odc-type-objects/2.client-odc-create-a-type.md)
+* [Create a synonym](../9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md)
\ No newline at end of file
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/3.client-odc-manage-stored-procedures.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/3.client-odc-manage-stored-procedures.md
new file mode 100644
index 00000000..def254a5
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/4.client-odc-stored-procedure-objects/3.client-odc-manage-stored-procedures.md
@@ -0,0 +1,112 @@
+Manage stored procedures
+=============================================
+
+
+
+Overview
+-----------------------------
+
+After you log on to OceanBase Developer Center (ODC), you can click the name of a connection on the homepage to go to the corresponding connection management page. In the left-side navigation pane, you can click **Stored Procedure** to get a list of stored procedures in the current database.
+
+In the stored procedure list, you can view the **Structure tree** of an object, or right-click the object to perform some **Management actions** on the object. You can also double-click the name of the stored procedure in the list to go to the **Stored procedure management page** .
+
+Structure tree
+-----------------------------------
+
+You can click the expand icon  before the name of the target stored procedure in the stored procedure list, and the structure tree of the stored procedure is displayed in a drop-down list, as shown in the following figure.
+
+The structure tree of a stored procedure can have up to three levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the Management actions section. In this section, you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------------------
+
+The names of stored procedure objects support ascending order by the head character by default in the stored procedure list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create stored procedure. |
+| Filter | Click this option to display valid/invalid stored procedures. |
+| Batch Compile | Click this option to batch compile the stored procedure object. Including: compile all objects and compile invalid objects.  |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the stored procedure, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Action | Description |
+|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View | Click this option to go to the Stored procedure management page, where you can view comprehensive information such as the basic information, parameters, and code of the stored procedure. |
+| Create | Click this option to go to the Create Stored Procedure page, where you can create a stored procedure as prompted. |
+| Edit | Click this option to go to the Stored procedure editing page, which displays the statements that define the stored procedure and where you can edit the stored procedure. |
+| Compile | Click this option to compile the stored procedure. |
+| Debug | Click this option to go to the **debugging page** , where you can debug the stored procedure.
**Note** ODC V4.0.0 and later support setting the parameter value as DEFAULT, NULL or empty string.
|
+| Run | Click this option to execute the stored procedure. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the stored procedure object. |
+| Delete | Click this option to delete the stored procedure. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the stored procedure so that the structure tree displays the latest information. **Note**
We recommend that you upgrade to OBServer V2.2.77 or later. This is because some versions of OBServer have been found with PL/SQL debugging issues, which may compromise the OBServer stability.
ODC V3.2.2 or earlier does not support the debugging feature when you connect ODC to the target instance by using OBProxy. To use the debugging feature, directly connect ODC to the target instance.
ODC V3.2.2 and later support PL/SQL debugging when you connect to OBServer by using OBProxy.
|
+
+
+Stored procedure management page
+-----------------------------------------------------
+
+
+
+You can double-click the name of a stored procedure in the function list to go to the stored procedure management page. The stored procedure management page displays the following information:
+
+
+| Section | Description |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This section displays the basic information about the stored procedure in fields such as **Stored Procedure Name** , **Created By** , **Creation At** , and **Last Modified At** . |
+| Parameter | This section displays the information about the parameters in fields such as **Name** , **Mode** , **Data Type** , **Length** , and **Default Value** .Click the  icon to refresh the parameters. |
+| DDL | This section displays the script that defines the stored procedure and provides the **Edit**, **Download**, **Find** **,** **Format**, and **Refresh** buttons. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
+Stored procedure editing page
+--------------------------------------------------
+
+Right-click the target item in the stored procedure list. In the menu that appears, click **Edit** to go to the stored procedure editing page. In the code area of the editing page, the statements that define the stored procedure are displayed. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+| Button | Description |
+|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Confirm modification | Click this button to apply the current modification. |
+| Compile | Click this button to compile the statements on the current page. **Note** * During the compilation, a code line is highlighted if it contains the name of an external object that cannot be referenced. * After the compilation, the **Compilation Result** tab displays the compilation status. If alerts exist, the alert details are displayed. |
+| Run | Click this button  to execute the statements in the code area. |
+| Debug | Click this button  to enter the debug mode, which allows you to edit the PL or SQL object in the code area. After the debugging, you can close the debugging window. |
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can add indents to or delete indents from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+| IN Value Conversion | Click this button to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format. * Column values are separated with line breaks. * Row values are separated with spaces or tabs. |
+
+
+
+Stored procedure output page
+-------------------------------------------------
+
+
+
+After the stored procedure is executed, you can view the information of execution results in the **Output** and **DBMS Output** tabs.
+
+
+| Tab | Description |
+|-------------|----------------------------------------------------------------------------------------------------------------------------|
+| Output | Displays the status, parameters, parameter types, parameter values, return type, and return value of the stored procedure. |
+| DBMS Output | Displays DBMS outputs of the stored procedure. |
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/1.client-odc-squence-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/1.client-odc-squence-objects-overview.md
new file mode 100644
index 00000000..3b6ba18a
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/1.client-odc-squence-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+A sequence is a serial arrangement of numbers that automatically increase based on specific rules in the database. A sequence is generally used as the primary key or unique key of a table because it does not contain duplicate values.
+**Notice**
+
+
+
+After you connect OceanBase Developer Center (ODC) to OceanBase Database V2.1.0 or a later version in Oracle mode, you can create sequence objects in ODC. The MySQL mode does not support this feature.
+
+Log on to ODC and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click Sequence in the left-side navigation pane to get a list of sequences. You can double-click a sequence name in the sequence list to go to the sequence management page. On this page, you can view the basic information, parameters, and DDL statements of the sequence.
+
+This chapter describes in different topics the operations you can perform on sequence objects in ODC.
+
+* [Create a sequence](../5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md)
+
+
+
+* [Manage sequences](../5.client-odc-sequence-objects/3.client-odc-manage-sequence.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md
new file mode 100644
index 00000000..61ebbbf8
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md
@@ -0,0 +1,38 @@
+Create a sequence
+======================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click **Sequence** in the left-side navigation pane to get a list of sequences. To create a sequence, click **+** in the upper-right corner of the sequence list or choose **Create \> Sequence** in the top navigation bar. Perform the following two steps to create a sequence:
+
+
+
+1. Set **Basic Info** : You need to specify **Sequence Name** and **User** . The User parameter is automatically specified based on the current account.
+
+
+
+2. Set columns. This step is optional. You need to specify the following parameters to set columns:
+
+
+
+ | Parameter | Description |
+ |-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | From | Specifies the initial value of the sequence, which must not be less than the value of **Minimum Value** . |
+ | Increment | Specifies the step size for the auto-increment of sequence values. The value can be a negative number. |
+ | Minimum Value | Specifies the minimum value that can be obtained by the sequence. The minimum value supported by the database is -1026. |
+ | Maximum Value | Specifies the maximum value that can be obtained by the sequence. The maximum value supported by the database is 1027. |
+ | Cache Settings | Specifies the cache size for the sequence. A proper cache size can improve the performance in obtaining sequence values. You can also set the value to **No Cache** . |
+ | Whether to Sort | Specifies whether the sequence obtains values in an ordered manner. The performance of the sequence in obtaining values in an ordered manner is inferior to that in an unordered manner. |
+ | Cyclic or Not | Specifies whether to start from the minimum value again when the sequence value reaches the maximum value. |
+
+
+
+3. Click **Next: Verify SQL Statement** to go to the Create Sequence page.
+
+ 
+
+
+4. An SQL script is pre-generated based on the information you specified. After the SQL script is verified, click **Create** in the upper-right corner to run the script and generate a sequence.
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/3.client-odc-manage-sequence.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/3.client-odc-manage-sequence.md
new file mode 100644
index 00000000..427cde11
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/5.client-odc-sequence-objects/3.client-odc-manage-sequence.md
@@ -0,0 +1,44 @@
+Manage sequences
+=====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click **Sequence** in the left-side navigation pane to get a list of sequences.
+
+You can right-click the target object in the sequence list to perform some **Management actions** on the object. You can also double-click the target sequence in the sequence list to go to the **sequence Management** page.
+
+
+
+Management actions
+---------------------------
+
+The names of sequence objects support ascending example by head character by default in the sequence list.
+Right-click the target object in the sequence list. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object.
+
+The following table describes the management options.
+
+
+| Action | Description |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create Sequence | Click this option to go to the Create Sequence page, where you can create a sequence as prompted. |
+| View Sequence | Click this option to go to the **sequence management page** , where you can view comprehensive information such as the basic information, attributes, and DDL statements of the sequence. |
+| Modify | Click this option to go to the Attribute tab of the **sequence management page** to modify the information of the sequence. |
+| Delete | Click this option to delete the sequence. |
+|Export|Export single table, see **Single table export and import**.|
+|Download|Download the SQL file for the sequence object.|
+| Refresh | Click this option to refresh the list after you perform management actions on the sequence, so that the list displays the latest information. |
+
+
+
+Sequence management page
+---------------------------------
+
+[sequence2](https://obbusiness-private.oss-cn-shanghai.aliyuncs.com/doc/img/odc/340/%E7%AE%A1%E7%90%86%E5%BA%8F%E5%88%97-2-EN.png)
+You can view the following information on the Sequence Management page.
+
+
+| Section | Description |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This tab displays the basic information of a sequence in fields such as the **Sequence Name** and **Owner** . It also provides the **Edit** and **Refresh** icons.You can click **Edit** to modify the value of the following fields: **Increment** , **Minimum Value** , **Maximum Value** , **Cache Settings** , **Whether to Sort** , and **Cyclic or Not** . **Next Buffer Value** is the value of `last_number` in the sequence view. This value cannot be modified. |
+| DDL | This section displays the script that defines the sequence. Click the  icon to refresh the parameters. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/1.client-odc-package-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/1.client-odc-package-objects-overview.md
new file mode 100644
index 00000000..4c7f6e5c
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/1.client-odc-package-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+A package is a combination of related PL programming elements, such as functions, procedures, variables, and cursors. Packages are similar to classes in Java. Variables in a package are similar to member variables in a class, and functions and procedures are similar to methods in a Java class. A package is used to group identical or similar objects, to facilitate maintenance and management and improve development efficiency and performance.
+**Notice**
+
+
+
+After you connect OceanBase Developer Center (ODC) to OceanBase Database V2.2.20 or a later version in Oracle mode, you can create package objects in ODC. The MySQL mode does not support this feature.
+
+Log on to ODC and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click package in the left-side navigation pane to get a list of packages. Double-click a package name in the package list to go to the package management page. On this page, you can view information such as the basic information and codes of the package header and package body.
+
+This chapter describes in different topics the operations you can perform on package objects in ODC.
+
+* [Create a package](../6.client-odc-package-objects/2.client-odc-create-a-program-package.md)
+
+
+
+* [Manage packages](../6.client-odc-package-objects/3.client-odc-manage-program-packages.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/2.client-odc-create-a-program-package.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/2.client-odc-create-a-program-package.md
new file mode 100644
index 00000000..f1f35732
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/2.client-odc-create-a-program-package.md
@@ -0,0 +1,22 @@
+Create a program package
+=============================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Program Package** in the left-side navigation pane to get a list of program packages. To create a program package, click **+** in the upper-right corner of the program package list or click **Create** in the navigation bar on the top of the page. To create a program package, you need to create the package header and the package body.
+
+Create the package header
+----------------------------------
+
+Click the **+** icon in the upper-right corner of the package list, or click **Create** in the navigation bar to go to the Create Program Package page, where you can create the package header.
+
+
+
+On the package creation page, specify the package name and click **Next: Verify SQL Statement** to go to the header definition page.
+
+ODC automatically generates the template statement, as shown in the following figure. In the navigation bar of the header definition page, ODC provides the **Format** button for you to standardize the statement format. After you complete the header definition statements, click **Create** in the upper-right corner to generate the header.
+
+
+
+Create the package body
+--------------------------------
+
+After you create the package header, the new program package appears in the program package list. Right-click the created program package and click **Create Package Body** to go to the package body definition page. This page is similar to the header definition page, as shown in the following figure. ODC automatically generates the template statement and provides the **Format** button for you to standardize the statement format. After you complete the package body definition statements, click **Create** in the upper-right corner to generate the package body.
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/3.client-odc-manage-program-packages.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/3.client-odc-manage-program-packages.md
new file mode 100644
index 00000000..6d91d057
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/6.client-odc-package-objects/3.client-odc-manage-program-packages.md
@@ -0,0 +1,92 @@
+Manage program packages
+============================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Program Package** in the left-side navigation pane to get a list of program package objects in the current database.
+
+In the program package list, you can view the **structure tree** of an object. You can also right-click the target object to perform some **management actions** on the object. You can also double-click the name of a program package to go to the program package page, which provides a **Package Header** tab and a **Package Body** tab.
+
+Structure tree
+-----------------------------------
+
+You can click the Expand icon before the name of the target program package in the program package list. Then, the structure tree of the program package displayed in a drop-down list, as shown in the following figure. The structure tree of a program package can have up to six levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section, where you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------------------
+
+The names of program package objects support ascending order by the head character by default in the program package list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create program package. |
+| Filter | Click this option to display valid/invalid program packages. |
+| Batch Compile | Click this option to batch compile the program package object. Including: compile all objects and compile invalid objects.  |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the program package, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Action | Description |
+|------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create Program Package | Click this option to go to the Create Program Package page, where you can create a program package header as prompted. |
+| Create Package Body | Click this option to go to the package body definition page and create a program package body. |
+| Edit the package header and package body | Click this option to open both the package header editing and package body editing pages, where you can edit the package header and the package body. |
+| Delete | Click this option to delete the program package. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the program package, so that the structure tree displays the latest information. |
+| View | Click this option to go to the Package Header tab or the Package Body tab, where you can view comprehensive information such as the basic information and code of the program package. |
+| Edit | Click this option to go to the package header editing and package body editing pages, which display the package header and package body definition statements and where you can continue to edit the package header and the package body. |
+| Compile | Click this option to compile the program package. |
+| Debug | Click this option to go to the debugging page, where you can debug the program package. PL object debugging is supported only when OBServer V2.2.73 or a later version, or V3.0.00 or a later version is connected.
**Note** ODC V4.0.0 and later support setting the parameter value as DEFAULT, NULL or empty string.
|
+| Run | Click this option to run the stored procedure or function in a subprogram in the program package body. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the program package object. |
+| Delete | Click this option to delete the body of the program package. |
+
+
+Package Body tab
+-------------------------------------
+
+On the program package management page, click the **Package Body** tab. The following information is displayed:
+
+
+| Section | Description |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic Information | This section displays the basic information about the package header in fields such as **Package Name** , **Created By** , **Created At** , and **Last Modified At** . |
+| DDL | This section displays the script that defines the function and provides the **Edit** , **Find** , and **Refresh** icons. **Note** Click the **Edit** icon to go to the PL object editing page. |
+
+
+
+Package header/body editing page
+-----------------------------------------------------
+
+
+
+Right-click the target object in the program package list. In the shortcut menu that appears, click **Edit** to go to the program package editing page. The code area of the editing page displays statements that define the program package. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+| Button | Description |
+|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Confirm Modification | Click this button to apply the current modification. |
+| Compile | Click this button to compile the statements on the current page. This button is available only on the package body editing page. |
+| Abort | Click this button to abort the statement that is being executed. |
+| Debug | Click this option to go to the debugging page, where you can debug the program package. PL object debugging is supported only when OBServer V2.2.70, V3.0.00, or a later version is connected. |
+| Format | Click this button to apply the formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three configurations: **All Uppercase** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding button to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | You can add indents to or delete indents from the statements that you selected. |
+| Comment | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+| IN Value Conversion | Click this button to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format. * Column values are separated with line breaks. * Row values are separated with spaces or tabs. |
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/1.client-odc-trigger-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/1.client-odc-trigger-objects-overview.md
new file mode 100644
index 00000000..581719d0
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/1.client-odc-trigger-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+Triggers are special stored procedures that are triggered by events but cannot be explicitly called. Therefore, triggers are used to monitor specific situations and trigger corresponding actions.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection in Oracle mode to go to the corresponding connection management page. You can click Trigger in the left-side navigation pane to get a list of triggers. Click **+** in the upper-right corner of the list to go to the Create Trigger page. You can also double-click the name of a trigger in the list to go to the trigger management page. On this page, you can view the basic information and codes of the trigger.
+**Notice**
+
+
+
+After you connect ODC to OceanBase Database V2.2.20 or a later version in Oracle mode, you can create trigger objects in ODC. The MySQL mode does not support this feature.
+
+This chapter describes in different topics the operations you can perform on trigger objects in ODC.
+
+* [Create a trigger](../7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md)
+
+
+
+* [Manage triggers](../7.client-odc-trigger-objects/3.client-odc-manage-triggers.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md
new file mode 100644
index 00000000..5002b529
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md
@@ -0,0 +1,114 @@
+Create a trigger
+=====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Trigger** in the left-side navigation pane to get a list of triggers. To create a trigger, click **+** in the upper-right corner of the trigger list or click **Create** in the navigation bar on the top of the page
+
+To create a trigger, perform the following three steps:
+
+1. Specify the basic information.
+
+
+
+2. Configure the advanced settings.
+
+
+
+3. Verify the SQL statement.
+
+
+
+
+
+
+
+
+Specify the basic information
+--------------------------------------------------
+
+This is Step 1. The **Basic Inf** **ormation** section contains the following parameters:
+
+* **Trigger Name** : specifies the name of the trigger.
+
+
+
+* **Base Object Mode** : specifies the schema where the object that the trigger works on is located.
+
+
+
+* **Base Object Type** : specifies the type of the object that the trigger works on. The current version supports only **TABLE** objects.
+
+
+
+* **Base Object Name** : specifies the name of the object that the trigger works on.
+
+
+
+* **Trigger Status** : specifies the state of the trigger. Valid value: **On** or **Disable** .
+
+
+
+
+
+
+Configure the advanced settings
+----------------------------------------------------
+
+This is Step 2. The **Advanced Settings** section contains the following parameters:
+
+* **Trigger Type** : specifies the type of the trigger. The current version supports only **SIMPLE** triggers.
+
+
+
+* **Trigger** : specifies whether the trigger is activated before or after the triggering event. Valid value: **BEFORE** or **AFTER** .
+
+
+
+* **Level** : specifies the level of the trigger. The current version supports only row-level triggers.
+
+
+
+* **Event** : specifies the type of operation that activates the trigger. Valid value: **INSERT** , **UPDATE** , or **DELETE** .
+
+
+
+* **Column (Optional)** : specifies the range that the event specified in **Event** applies to. This parameter is displayed when you set **Event** to **UPDATE** . The current version allows you to create only row-level triggers in a table. Therefore, the range here is the columns that the event applies to.
+
+
+
+* **Referencing Old** **(Optional)** : specifies an alias for the referenced object that corresponds to the value specified for `REFERENCEING OLD` in the trigger creation statement.
+
+
+
+* **Referencing New** **(Optional)** : specifies an alias for the referenced object that corresponds to the value specified for `REFERENCEING NEW` in the trigger creation statement.
+
+
+
+* **Clause Condition** **(Optional)** : specifies a logical expression for the trigger. After you specify a clause condition, the action specified by the trigger is executed only if the value of the expression is True.
+
+
+
+
+
+
+Verify the SQL statement
+---------------------------------------------
+
+After you specify all the information in the **Basic Info** and **Advanced Settings** sections, click **Next: Verify SQL Statement** to go to the statement editing page.
+
+The trigger definition statement is generated on the statement editing page based on the information that you specified in the **Basic Info** and **Advanced Settings** sections. You only need to complete the trigger body, which specifies the action to be executed. After you complete the trigger body, click the **Create** button in the upper-right corner of the page to complete the creation of the trigger.
+
+In addition, the toolbar on the editing page provides the following buttons:
+
+
+| Button | Description |
+|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can specify search criteria in the search box to find specific content in the script and enter other content in the replacement box to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three configurations: **All Caps** , **All Lowercase** , and **Capitalize the first letter** . Click this button to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | The **Add Indents** and **Delete Indent** options are provided, to allow you to add indents to or delete indents from the selected statements in the script. |
+| Comment | The **Add Comments** and **Delete Comment** options are provided, which respectively allow you to convert the selected statements in the script to comments and convert comments to SQL statements. |
+| Previous | Click this button to go back to the **Create Trigger** page, where you can continue to edit or modify the parameters in the **Basic Information** and **Advanced Settings** sections. |
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/3.client-odc-manage-triggers.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/3.client-odc-manage-triggers.md
new file mode 100644
index 00000000..02629706
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/7.client-odc-trigger-objects/3.client-odc-manage-triggers.md
@@ -0,0 +1,81 @@
+Manage triggers
+====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Trigger** in the left-side navigation pane to get a list of triggers. The trigger list displays the trigger objects in the current database. You can right-click the target object to perform some management actions on the object. You can also double-click the name of the target trigger in the trigger list to go to the trigger management page.
+
+
+
+Management actions
+---------------------------------------
+
+The names of trigger objects support ascending order by the head character by default in the trigger list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create trigger. |
+| Filter | Click this option to display valid/invalid triggers. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the trigger, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the list. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object. The following table describes the management options.
+
+
+| Option | Description |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Trigger | Click this option to go to the trigger management page, where you can view the basic information, parameters, and code of the trigger. |
+| Create Trigger | Click this option to go to the Create Trigger page, where you can create a trigger as prompted. |
+| Edit | Click this option to go to the trigger editing page, which displays the statements that define the trigger and where you can continue to edit the trigger. |
+| Compile | Click this option to compile the trigger. |
+| Enable | Click this option to enable the trigger. |
+| Disable | Click this option to disable the trigger. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the trigger object. |
+| Delete | Click this option to delete the trigger. |
+| Refresh | Click this option to refresh the list after you perform management actions on the trigger, so that the list displays the latest information. |
+
+
+
+Trigger management page
+--------------------------------------------
+
+[trigger2](https://obbusiness-private.oss-cn-shanghai.aliyuncs.com/doc/img/odc/340/%E7%AE%A1%E7%90%86%E8%A7%A6%E5%8F%91%E5%99%A8-2-EN.png)
+
+You can double-click the name of the target trigger in the trigger list to go to the trigger management page, which provides the following three tabs:
+
+* **Basic Info** : displays information such as **Name** , **Owner** , and the **Trigger State** of the trigger.
+
+* **Base Object** : displays information such as **Name** , **Owner** , and **Type** of the base object of the trigger.
+
+* **DDL** : displays the script that defines the trigger and provides the **Edit** , **Find** , and **Refresh** buttons. You can click Edit to go to the trigger editing page.
+
+
+
+
+
+
+Trigger editing page
+-----------------------------------------
+
+To go to the trigger editing page, right-click the target trigger in the trigger list and choose **Edit** from the shortcut menu that appears. You can also click the **Edit** button on the DDL tab of the trigger management page to go to this page. The code area on the editing page displays the statements that define the trigger. You can edit the statements. In addition, the toolbar provides the following buttons:
+
+
+| Button | Description |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | You can specify search criteria in the search box to find specific content in the script and enter other content in the replacement box to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three configurations: **All Caps** , **All Lowercase** , and **Capitalize the first letter** . Click this button to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | The **Add Indents** and **Delete Indent** options are provided, to allow you to add indents to or delete indents from the selected statements in the script. |
+| Comment | The **Add Comments** and **Delete Comment** options are provided, which respectively allow you to convert the selected statements in the script to comments and convert comments to SQL statements. |
+| Confirm Modification | Click this button to apply the current modification. |
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/1.client-odc-type-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/1.client-odc-type-objects-overview.md
new file mode 100644
index 00000000..78dcebed
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/1.client-odc-type-objects-overview.md
@@ -0,0 +1,24 @@
+Overview
+=============================
+
+You can create custom object types in OceanBase Database. A type in OceanBase Database is similar to a class in Java. A class has attributes and methods, and methods in Java are equivalent to functions and stored procedures in OceanBase Database.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. Click Type in the left-side navigation pane to get a list of types. Click the **+** button in the upper-right corner of the list to go to the type creation page. You can double-click the name of a type in the list to go to the type management page, where you can view the basic information and code of the type.
+**Notice**
+
+
+
+After you connect ODC to OceanBase Database V2.2.20 or a later version in Oracle mode, you can create type objects in ODC. The MySQL mode does not support this feature.
+
+This chapter describes in different topics the operations you can perform on type objects in ODC.
+
+* [Create a type](../8.client-odc-type-objects/2.client-odc-create-a-type.md)
+
+
+
+* [Manage types](../8.client-odc-type-objects/3.client-odc-manage-types.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/2.client-odc-create-a-type.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/2.client-odc-create-a-type.md
new file mode 100644
index 00000000..82dc0684
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/2.client-odc-create-a-type.md
@@ -0,0 +1,159 @@
+# Create a type
+
+ODC supports visualized type creation. This topic describes how to create a type with ODC.
+
+## Overview
+
+A database type object specifies the name, method, and other attributes of a type.
+
+OceanBase Developer Center (ODC) supports three types: object type, array type, and table type.
+
+* Object type: an abstract data type (ADT), which is an expression that encapsulates database objects, relationships between database objects, and basic operations on database objects.
+
+
+
+* Array type: a variable array, which is a collection similar to a nested table. A variable array is a collection of objects, where each object is of the same data type. The size of a variable array is determined when the array is created. The data type of a column in a table can be a variable-length multidimensional array. The type of the array can be any of the primitive types, the enumerated type, the composite type, or a user-defined type.
+
+
+
+* Table type: an independent nested table type. The created arrays are directly defined in the columns of the table.
+
+
+
+
+
+As shown in the preceding figure, you can create a type in the following four steps:.
+
+1. Specify the type name.
+2. Select a type object.
+3. Edit SQL statements.
+4. Complete the type creation.
+
+## Procedure
+
+In the following example, the ob_var object type is created in the ODC console. The type contains two VARCHAR type parameters: var and var1. Procedure:
+
+### Step 1: Specify the name of the type.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Type** in the left-side navigation pane to get a list of types. To create a type, click **+** in the upper-right corner of the type list or click **Create** in the top navigation bar.
+
+
+
+### Step 2: Select a type object.
+
+
+
+| Type | Description | Example |
+|------|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| Object Type | The ADT. **Note** Only the object type can contain a subprogram. | ``` CREATE OR REPLACE TYPE ob_var AS OBJECT( var varchar2(10), var1 varchar(10) ); ``` |
+| Array Type | The independent variable array (VARRAY) type. | ``` CREATE OR REPLACE TYPE test AS VARRAY(20) of varchar2(20); ``` |
+| Table Type | The independent nested table type. | ```CREATE OR REPLACE TYPE test AS TABLE OF varchar2(100 BYTE);``` The `AS TABLE OF` clause allows you to create an array list\. |
+
+
+
+### Step 3: Edit SQL statements.
+
+
+
+After you specify the information in Step 2, click **Next: Verify SQL Statement** to go to the statement editing page. This page displays the corresponding type definition statements generated based on the information you specified in the **Create Type** dialog box. You must complete the statements based on your needs. After you complete the statements, click **Create** in the upper-right corner to complete the type creation.
+
+In addition, the toolbar on the editing page provides the following buttons.
+
+
+| Button | Description |
+|-------|----------------------------------------------------------------|
+| Format | Click this button to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| Find and Replace | Click this button and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this button to undo the last operation. |
+| Redo | Click this button to reverse an **Undo** operation. |
+| Case Sensitivity | The system supports three capitalization options: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+| Indent | You can **add indents** to or **delete indents** from the statements that you selected. |
+| Comments | You can click **Add Comments** to convert the statements that you selected into comments or click **Delete Comment** to convert comments to SQL statements. |
+|IN Value Conversion|A format such as A B can be converted to ('A','B') format.|
+
+
+
+### Step 4: Complete the type creation.
+
+Click **Create** in the upper-right corner to create the type. After a user-defined type is created, you can use the `INSERT` key word to call it in a PL statement.
+
+
+
+> **Note**
+> To manage a type, right-click the type name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Delete**, **Download**, and **Refresh**.
+> For more information, see [Manage types](../8.client-odc-type-objects/3.client-odc-manage-types.md).
+
+Example:
+
+```sql
+-- Create a table.
+create table data_type (id number(10),name varchar2(50),age int,address varchar2(50),salary float);
+
+-- Insert table data.
+insert into data_type values(1,'baba',20,'hangzhou',3000.00);
+
+-- Create a type.
+create or replace type ob_var as object(
+ var varchar2(10),
+ var1 varchar(10)
+);
+
+delimiter /
+-- Create a stored procedure.
+create or replace procedure p_datatype is
+begin
+ declare
+ rec data_type%rowtype;
+ v_age rec.age%type;
+ var varchar2(50);
+ v_name var%type;
+ v_salary data_type.salary%type;
+
+-- Define a type.
+ type salary is table of number index by varchar2(20);
+ arr salary;
+ v_arr arr%type;
+
+ CURSOR c2 IS SELECT name, age FROM data_type;
+ c_row c2%rowtype;
+ v_rec c_row%type;
+
+ ob ob_var;
+ v_obj ob%type;
+
+ begin
+ v_name := 'ali ';
+ v_age := 30;
+ v_salary := 2000;
+ dbms_output.put_line('Referenced item: variable, record, and table column name: ' || v_name || ' * ' || v_age || ' * ' || v_salary);
+
+ v_arr('James') := 78000;
+ dbms_output.put_line('Referenced item: name of collection variable ' || v_arr.FIRST);
+
+ open c2;
+ fetch c2 into v_rec;
+ dbms_output.put_line('Referenced item: name of cursor variable: ' || v_rec.name || ' * ' || v_rec.age);
+ close c2;
+
+ v_obj:=ob_var('test','object');
+ dbms_output.put_line('Referenced item: name of object instance: ' || v_obj.var || ' * ' || v_obj.var1);
+ end;
+end;
+/
+
+begin
+ p_datatype;
+end;
+/
+```
+
+## Related topics
+
+* [Create a table](../1.client-odc-table-objects/2.client-odc-create-a-table.md)
+* [Create a view](../2.client-odc-view-objects/2.client-odc-create-a-view.md)
+* [Create a function](../3.client-odc-function-objects/2.client-odc-create-a-function.md)
+* [Create a stored procedure](../4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md)
+* [Create a program package](../6.client-odc-package-objects/2.client-odc-create-a-program-package.md)
+* [Create a trigger](../7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md)
+* [Create a synonym](../9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md)
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/3.client-odc-manage-types.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/3.client-odc-manage-types.md
new file mode 100644
index 00000000..7d9b5722
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/8.client-odc-type-objects/3.client-odc-manage-types.md
@@ -0,0 +1,56 @@
+Manage types
+=================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Type** in the left-side navigation pane to get a list of types The type list displays the type objects in the current database. You can right-click the target object in the type list to perform some management actions on the object. You can also double-click the target type in the type list to go to the type management page.
+
+Structure tree
+-----------------------------------
+
+You can click the expand icon before the name of the target type in the type list, and the structure tree of the type is displayed in a drop-down list, as shown in the following figure. The structure tree of a type can have up to five levels. When you right-click an item in the tree, the shortcut menu displays some actions that you can perform on the item. For more information about these actions, see the **Management actions** section, where you can find the table describing the management options.
+
+
+
+Management actions
+---------------------------------------
+
+The names of type objects support ascending order by the head character by default in the type list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create type. |
+| Filter | Click this option to display valid/invalid types. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the type, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object.
+
+The following table describes the management options.
+
+
+| Option | Description |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Type | Click this option to go to the type management page, where you can view the basic information and codes of the type. |
+| Create Type | Click this option to go to the **Create Type** page, where you can create a type as prompted. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the type object. |
+| Delete | Click this option to delete the type. |
+| Refresh | Click this option to refresh the list after you perform management actions on the type, so that the list displays the latest information. |
+
+
+
+Type management page
+-----------------------------------------
+
+You can double-click the name of the target type in the type list to go to the type management page. This page provides two tabs:
+
+* **Basic Info** : displays information such as **Name** , **Owner** , **Type** , **Creation Time** , and **Modified At** of the type object.
+
+* **DDL** : displays the script that defines the type and provides the **Download**, **Find**, **Refresh** and **Format** buttons. You can click Edit to go to the type editing page.
\ No newline at end of file
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/1.client-odc-synonym-objects-overview.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/1.client-odc-synonym-objects-overview.md
new file mode 100644
index 00000000..0d1b12e2
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/1.client-odc-synonym-objects-overview.md
@@ -0,0 +1,29 @@
+Overview
+=============================
+
+A synonym is an alias of a database object. It is often used to simplify object access and improve the security of object access. Similar to views, synonyms do not consume storage space, and only the synonym definitions are stored in the data dictionary. Synonyms are divided into public synonyms and common synonyms.
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click Synonym in the left-side navigation pane to get a list of synonyms. You can click **+** in the upper-right corner of the list to go to the synonym creation page. You can also double-click a synonym name in the list to go to the synonym management page. On this page, you can view the basic information and codes of the synonym.
+
+The database version must meet the following requirements:
+
+
+| Database | Version |
+|-----------------------------------|---------------------------|
+| OceanBase Database in Oracle mode | V2.2.0 or a later version |
+| OceanBase Database in MySQL mode | V2.2.0 or a later version |
+
+
+
+This chapter describes in different topics the operations you can perform on synonym objects in ODC.
+
+* [Create a synonym](../9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md)
+
+
+
+* [Manage synonyms](../9.client-odc-synonym-objects/3.client-odc-manage-synonyms.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md
new file mode 100644
index 00000000..7579739b
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/2.client-odc-create-a-synonym.md
@@ -0,0 +1,139 @@
+# Create a synonym
+
+ODC supports visualized synonym creation. This topic describes how to create a synonym with ODC.
+
+## Overview
+
+A synonym is an alias that you create for a database object of another user. You can perform operations on the object by querying and operating the synonym.
+
+Synonyms are similar to views. You can use synonyms to add, delete, modify, and query table data. You can define synonyms for most database objects in OceanBase Database, such as tables, views, materialized views, sequences, functions, stored procedures, packages, and synonyms.
+
+Synonyms extend the availability of database objects and allow them to be accessed by different database users with the required privileges. This design simplifies and secures access to database objects.
+
+### Synonym types
+
+OceanBase Database supports synonyms and public synonyms.
+
+* Synonyms: In general, a synonym created by a regular user is a private synonym. A private synonym can be accessed by the user who created it or other users who are granted the required privileges. To create a private synonym under the current user, you must have the CREATE SYNONYM privilege.
+
+
+
+* Public synonyms: A public synonym is created by a user who is granted the administrator role, such as the system user account, and can be accessed by all users.
+
+
+
+For more information, see [Synonyms](https://www.oceanbase.com/docs/enterprise/oceanbase-database/oceanbase-database/V3.2.2/synonyms).
+
+
+
+As shown in the preceding figure, you can create a synonym in the following eight steps:
+
+1. Specify the synonym name.
+2. Specify the object owner.
+3. Specify the object type.
+4. Specify the object name.
+5. Specify the synonym type.
+6. Verify the information about the synonym.
+7. Edit the synonym.
+8. Complete the synonym creation.
+
+## Procedure
+
+In this example, a synonym named syn_employee is created in the OceanBase Developer Center (ODC) console for an employee table in the SYS database. Procedure:
+
+### Step 1: Specify the name of the synonym.
+
+Log on to the ODC console and click the name of the desired connection to go to the corresponding connection management page. You can click **Synonym** in the left-side navigation pane to get a list of synonyms and a list of public synonyms. To create a synonym, click **+** in the upper-right corner of the synonym list or choose **Create** > **Synonym** in the top navigation bar.
+
+In the **Create Synonym** dialog box, specify the name of the synonym.
+
+
+
+### Step 2: Specify the object owner.
+
+Specify the schema where the object is located.
+
+### Step 3: Specify the object type.
+
+Specify the object type. Valid values: Table and View.
+
+### Step 4: Specify the object name.
+
+Specify the name of the object for which the synonym is created.
+
+### Step 5: Specify the synonym type.
+
+Specify the synonym type. Valid values: Synonym and Public Synonym.
+
+### Step 6: Verify the information about the synonym.
+
+Click **Next: Verify SQL Statement** to go to the Create Synonym page.
+
+### Step 7: Edit the synonym.
+
+
+
+Edit the statement on the Create Synonym page.
+
+On the statement editing page, a synonym definition statement is generated based on the information specified in the **Create Synonym** dialog box. You can modify this statement. After you confirm the statement, click the **Create** button in the upper-right corner of the page to complete the synonym creation. A synonym cannot be modified after it is created.
+
+Before a synonym is created, you can edit the SQL statements of the synonym on the Create Synonym page. Syntax:
+
+```sql
+CREATE OR REPLACE SYNONYM syn_name FOR schema_name.object_name;
+```
+
+
+
+Parameters
+
+
+| Parameter | Description |
+|-------------|----------------------------------------------------|
+| OR REPLACE | Updates a synonym if the synonym already exists. |
+| syn_name | The name of the synonym. The name of a synonym must be unique in the specified schema. |
+| schema_name | The database schema to which the object belongs. |
+| object_name | The name of the object. |
+
+
+
+### Step 8: Complete the synonym creation.
+
+Click **Create**. After you create a synonym, you can use it in the same way as a built-in synonym.
+
+
+
+
+> **Note**
+> To manage a synonym, right-click the synonym name in the left-side navigation pane, and select the required operation from the context menu, which provides the following options: **View**, **Create**, **Delete**, **Download**, and **Refresh**.
+
+For more information, see [Manage synonyms](../9.client-odc-synonym-objects/3.client-odc-manage-synonyms.md).
+
+Syntax:
+
+```sql
+SELECT * FROM syn_name ([syn_parameter[,...])
+```
+
+
+
+Example:
+
+```sql
+SELECT * FROM syn_employee;
+```
+
+
+
+
+
+## Related topics
+
+* [Create a table](../1.client-odc-table-objects/2.client-odc-create-a-table.md)
+* [Create a view](../2.client-odc-view-objects/2.client-odc-create-a-view.md)
+* [Create a function](../3.client-odc-function-objects/2.client-odc-create-a-function.md)
+* [Create a stored procedure](../4.client-odc-stored-procedure-objects/2.client-odc-create-a-stored-procedure.md)
+* [Create a sequence](../5.client-odc-sequence-objects/2.client-odc-create-a-sequence.md)
+* [Create a program package](../6.client-odc-package-objects/2.client-odc-create-a-program-package.md)
+* [Create a trigger](../7.client-odc-trigger-objects/2.client-odc-create-a-trigger.md)
+* [Create a type](../8.client-odc-type-objects/2.client-odc-create-a-type.md)
diff --git a/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/3.client-odc-manage-synonyms.md b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/3.client-odc-manage-synonyms.md
new file mode 100644
index 00000000..ec6d003e
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/10.client-odc-database-objects/9.client-odc-synonym-objects/3.client-odc-manage-synonyms.md
@@ -0,0 +1,56 @@
+Manage synonyms
+====================================
+
+Log on to OceanBase Developer Center (ODC) and click the name of the target connection to go to the corresponding connection management page. You can click **Synonym** in the left-side navigation pane to get a list of synonyms or a list of public synonyms. The synonym list displays the synonym objects in the current database. You can right-click the target object in the synonym list to perform some management actions on the object. You can also double-click the target synonym to go to the synonym management page.
+
+
+Management actions
+---------------------------------------
+
+The names of type objects support ascending order by the head character by default in the type list.
+
+### Shortcut function
+
+The following functions are provided in the upper right corner of the tree:
+
+
+| Action | Description |
+|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Create | Click this option to create type. |
+| Filter | Click this option to display valid/invalid types. |
+| Refresh | Click this option to refresh the structure tree after you perform management actions on the type, so that the structure tree displays the latest information. |
+
+
+
+### Right-click function
+
+Right-click the target object in the structure tree. A shortcut menu appears, displaying some management options provided by ODC for you to conveniently manage the target object.
+
+The following table describes the management options.
+
+
+| Option | Description |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| View Type | Click this option to go to the type management page, where you can view the basic information and codes of the type. |
+| Create Type | Click this option to go to the **Create Type** page, where you can create a type as prompted. |
+|Export|Export single table, see **Single table export and import**.|
+| Download | Download the SQL file for the type object. |
+| Delete | Click this option to delete the type. |
+| Refresh | Click this option to refresh the list after you perform management actions on the type, so that the list displays the latest information. |
+
+
+
+
+Synonym management page
+--------------------------------------------
+
+Double-click the target synonym in the synonym list to go to the synonym management page, which provides the following two tabs:
+
+* **Basic Info** : displays synonym information such as **Name** , **Object** **Owner** , **Object Name** , **Creation Time** , and **Modified At** .
+
+* **DDL** : displays the script that defines the synonym. A synonym cannot be modified after it is created. You can **Download** and **Format** the synonym.
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/11.client-odc-help-center.md b/en-US/7.client-odc-user-guide/11.client-odc-help-center.md
new file mode 100644
index 00000000..9b06a1fa
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/11.client-odc-help-center.md
@@ -0,0 +1,64 @@
+Help center
+================================
+
+
+
+Overview
+-----------------------------
+
+In the upper-right corner of the OceanBase Developer Center (ODC) homepage, you can click **Help** in the top navigation bar to view **New Features** and **View Help Documentation** . You can also obtain service information and email address on **About Developer Center** and **Feedback** tabs.
+
+
+
+Features
+-----------------------------
+
+When you access ODC for the first time, the **Features** dialog box automatically appears. It displays the features and core functions of the current version to help you quickly learn about ODC.
+
+After you close the dialog box, you can select **Features** in the **Help** menu to open it again.
+**Note**
+
+
+
+The Features dialog box may display different information based on user permissions.
+
+View help documentation
+--------------------------------------------
+
+To view the help documentation, click **Help** in the top navigation bar, and select **View Help Documentation** in the drop-down list.
+
+* If you are using Web ODC, the help documentation is displayed on a new tab of the browser.
+
+
+
+* If you are using the ODC client, the help documentation is displayed in a browse window.
+
+ To view the service documentation of the latest or history versions, you can go to **[OceanBase documentation center](https://www.oceanbase.com/en/docs/enterprise/oceanbase-developer-center/odc/V3.3.1/product-updates)**.
+
+
+
+
+
+About developer center
+-------------------------------------------
+
+Select **About Developer Center** in the drop-down list of **Help** to display a window. This window displays information such as the service name, version number, release date, official website URL, and copyright.
+
+
+
+Feedback
+-----------------------------
+
+To send your feedback, select **Feedback** in the drop-down list of **Help** .
+
+* If you are using Web ODC, you can see the email address of ODC technical support odcsupport@service.alipay.com in the dialog box that appears. You can send your suggestions to that email address.
+
+
+
+* If you are using the ODC client, the dialog box of Feedback also provides you the feature of downloading the feedback package. You can click **Generate information package** in the dialog box to pack frontend and backend logs, system environment, and other information into a feedback package.
+
+ 
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/2.client-odc-homepage.md b/en-US/7.client-odc-user-guide/2.client-odc-homepage.md
new file mode 100644
index 00000000..17a7279b
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/2.client-odc-homepage.md
@@ -0,0 +1,90 @@
+ODC homepage
+=================================
+
+
+
+Overview
+-----------------------------
+
+After you log on to OceanBase Developer Center (ODC), the ODC homepage automatically appears.
+
+On the ODC homepage, you can click [Task](8.client-odc-task-management/1.client-odc-task-management-overview.md), [Operating Records](../7.client-odc-user-guide/7.view-operation-records.md), or [Help](../7.client-odc-user-guide/11.client-odc-help-center.md) in the top navigation bar to go to the corresponding page. You can also perform the following operations on the page: managing database connections, switching the language, setting personal information, changing the password, and logging off from ODC. On the right side of the homepage, you can also find the Help, Related Tools, and Related Resources tabs.
+
+
+
+Manage database connections
+------------------------------------------------
+
+The ODC homepage provides the **Private Connection** tab that shows the connections you have created in a list.
+
+On the **All Connections** tab, you can [create a private connection](../7.client-odc-user-guide/3.client-odc-connect-database/1.client-odc-create-connection.md), and search for, filter, sort, and refresh connections.
+
+
+# View session history
+
+On the ODC homepage, you can click **History** in the left-side navigation pane to go to the session history page.
+
+The page shows a list that has the following columns.
+
+
+| Column | Description |
+|-----------|----------------------------------------------------|
+| Connection Name | The name of the connection you accessed. |
+| Database/Schema Name | The name of the database or schema that you accessed by using the connection. |
+| Recently Opened At | The time when you last accessed the connection. |
+| SQL/PL Window | The workspace window that you created when you accessed the connection. Move the pointer to a window name, and the script that you edited in the window is displayed. |
+| Actions | You can click **Open** to resume the connection in a new window. The corresponding workspace window and its content are also resumed. |
+
+
+> **Note**
+> By default, the historical records in the panel are stored for 48 hours. You can restore the content in an unsaved SQL window based on records in the panel.
+
+
+
+## Manage tasks
+
+On the ODC homepage, you can click **Task** in the left-side navigation pane to create and view tasks. For more information, see [Manage tasks](../6.web-odc-user-guide/9.web-odc-task-management/1.web-odc-task-management-overview.md).
+
+
+Switch the theme
+-------------------------
+
+
+
+In the lower-left corner of the ODC homepage, choose **Me** > **Theme** to switch the theme to **Default Theme** or **Dark Theme**.
+
+Switch the language
+-------------------------
+
+In the lower-left corner of the ODC logon page or ODC homepage, choose **Me** > **Language** to view the display language of ODC. The default language is **Simplified Chinese**. You can click the language option to switch the display language. ODC supports **English**, **Simplified Chinese**, and **Traditional Chinese**.
+
+Personal Settings
+-------------------------
+
+
+
+In the lower-left corner of the ODC homepage, choose **Me** > **Preferences**. The **Edit Personal Settings** panel appears.
+
+In the panel, you can globally modify the settings of the customizable features. You can also select a connection and configure these features in the connection. The configurations take effect on the current connection. The priority of personal settings is lower than that of settings you configured for each connection. In addition, the personal settings are persisted.
+
+Your modifications to fields in the Edit Personal Settings panel take global effect.
+
+
+| Field | Description |
+|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Session Mode for SQL Window | Set the session mode of the SQL window. |
+| Delimiter Settings | Set the default delimiter for executing PL statements in the SQL window. Five types of delimiters are supported: semi-colons ( **;** ), slashes ( **/** ), double slashes ( **//** ), dollar signs ( **$** ), and double dollar signs ( **$$** ). |
+| Transaction Commit Mode in Oracle Mode | Set the default transaction commit mode in Oracle mode. Valid values: Manual and Automatic. |
+| Transaction Commit Mode in MySQL Mode | Set the default transaction commit mode in MySQL mode. Valid values: Manual and Automatic. |
+| Maximum Number of Rows in Result Set | Set the default number of rows returned for an SQL statement executed in the SQL window. |
+| Type of Statements Generated by Dragging and Dropping Object | Set the default type of statements generated when you drag and drop table or view objects. |
+
+
+
+Set an application password
+------------------------------------------------
+
+You do not need to log on when you start Client ODC, because a default user is used. For security purposes, Client ODC allows you to set an application password. After you set an application password, you must enter the password when you start Client ODC. If you enter the wrong password three times, the system will prompt you to reset the data. If you reset the data, connection information saved in ODC will be cleared.
+
+
+In the lower-left corner of the ODC homepage, choose **Me** > **Application Password**. The **Set Application Password** dialog box appears.
\ No newline at end of file
diff --git a/en-US/7.client-odc-user-guide/3.client-odc-connect-database/1.client-odc-create-connection.md b/en-US/7.client-odc-user-guide/3.client-odc-connect-database/1.client-odc-create-connection.md
new file mode 100644
index 00000000..2c3351d5
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/3.client-odc-connect-database/1.client-odc-create-connection.md
@@ -0,0 +1,74 @@
+Create a private connection
+================================================
+
+
+
+Overview
+-----------------------------
+
+After you log on to the homepage of OceanBase Developer Center (ODC), you can click **Create Connection** in the upper-right corner of the **Private Connection** tab to create a private connection.
+
+After you create the connection, you can view the saved database connection in the connection list on the ODC homepage.
+
+
+
+> **Notice**
+>
In ODC V2.3.0 and later versions, the root@sys user permissions are required to query views when you use the import and export features. Therefore, to use the import and export features, you need to set the root@sys user in the Advanced Configuration section during connection creation.
+>
The root@sys user permissions are also required to view the partition information. Therefore, to display the table partition information, you must also set the root@sys user in the Advanced Configuration section during connection creation.
+>
ODC V3.3.0 and later versions support independent sessions and shared sessions. In independent session mode, each SQL window corresponds to one database session, and all modifications affect only the current window. In shared session mode, all SQL windows share one database session, and modifications in any SQL window affect other SQL windows.
+>
In manual-commit mode, make sure to set the `ob_trx_idle_timeout` parameter to a value greater than or equal to the timeout value of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of the `ob_trx_idle_timeout` parameter, the connection is terminated. However, if the `ob_trx_idle_timeout` parameter is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you must set this parameter to a proper value.
+
+
+
+
+
+
+Procedure
+------------------------------
+
+Perform the following steps to create a connection:
+
+
+
+1. Log on to ODC and click **Create Connection** in the upper-right corner of the **Private Connection** tab.
+
+
+
+2. In the Create Connection panel, specify the fields described in the following table. If you have an OceanBase connection string, which follows the mysql -h **host name** -P **port number** -u **database username@tenant name** # **cluster name** -D **default database** -p ' **database password** ' format, you can obtain the information from the string. You can also paste the string in the field of Intelligent Parsing on the panel to automatically populate the corresponding fields.
+
+
+
+ | Field | Description |
+ |-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Database Type | Select **Physical Database** or **Logical Database** . * Physical Database: regular databases. * Logical Database: ODP (Sharding). |
+ | Region | Select **Independent Deployment/Apsara Stack** if your database instance is deployed in your own environment, or select **Public Cloud** if your database instance is deployed on Alibaba Cloud. |
+ | Intelligent Parsing | You can paste a connection string to the field. ODC automatically identifies the string and fills in the corresponding fields on the page. |
+ | Connection Mode | Select **MySQL** or **Oracle** . Logical databases support only the MySQL mode. |
+ | 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 name** : the name of the cluster where the target database is located. This parameter is not required for logical databases. * **Rent name** : 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). |
+ | Database Account | * Database Username: an account under the tenant. In MySQL mode, this account must have access to the default database. * Database Password: the password of the account under the tenant. You can click **Test Connection** next to the password field to check the connection to the target database. * Save Database Password * If you disable this option, the database password for the connection is not saved. Each time you use or test the connection, you must enter the database password in the password dialog box. * If you enable this option, the database password for the connection is saved. You do not need to enter the database password each time you use the connection. **Note** * An error will be returned if the configurations such as the username, password, and network settings are invalid. * You can only connect to a database in the current tenant. Otherwise, a test failure error will be returned. |
+ | Default Database/schema | When you connect to a database in a MySQL tenant, you must specify the default database for the connection. You do not need to specify this field when you connect to a database in an Oracle tenant. **Note** If you leave this parameter unspecified, the information_schema database is connected by default. However, if the connection to the information_schema database fails, you need to specify a database that the current user has access permissions. |
+ | SQL Query Timeout Value | You can specify a timeout value for SQL queries. A query whose execution time exceeds the timeout value is automatically terminated. The default timeout value is 60 seconds. |
+ | Query sys Tenant View | When Database Type is set to Physical Database, you can specify an account that has the privilege to query the SYS tenant view, and the password. This field is automatically populated when SYS is specified as the tenant in **Endpoint** . * **Account** : an account having the privilege to check the views under the SYS tenant. * **Password** : the password of the account. After you specify the account and password, click **Test Connection** next to the password field to verify whether the account information is valid. **Note** * In ODC V2.3.0 and later versions, to use the import and export features, you need to configure the root@sys account in the Advanced Configuration section during connection creation. * In ODC V2.4.1 and later versions, the dependency of the import and export features on the root@sys user is removed when you query views. If the root@sys account is not configured, some ODC objects such as stored procedures and functions do not support the export feature. If the root@sys account is configured, you can access the views under the SYS tenant to obtain the optimal data routing strategy, which can increase the export speed. |
+
+
+
+3. Click **Save** to save the current configuration in the ODC connection list, and enter the connection name. Next time you log on to ODC, you can directly select the connection from the list. The connection configuration does not necessarily need to pass the connection test when you save the configuration.
+
+ 
+
+ > **Notice**
+ >
+ > Before saving, you can click **Test Connection** to test the database connection. If the database user name and password are correct, it will prompt **Connected**.
+
+
+4. Click **Copy Connection String** in the lower part of the panel to copy the connection information being edited on the current panel as a connection string if necessary. This allows you to obtain the connection information with ease.
+
+
+
+5. Click **Cancel** if you do not need to save the current connection configuration. Then, a confirmation dialog box appears.
+
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/3.client-odc-connect-database/2.client-odc-manage-connections.md b/en-US/7.client-odc-user-guide/3.client-odc-connect-database/2.client-odc-manage-connections.md
new file mode 100644
index 00000000..4027addf
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/3.client-odc-connect-database/2.client-odc-manage-connections.md
@@ -0,0 +1,169 @@
+Manage connections
+=======================================
+
+
+
+Overview
+-----------------------------
+
+On the homepage of OceanBase Developer Center (ODC), the **Private Connection** tab displays the information of connections that you created and saved.
+
+All the connections you created are displayed in a list on the **Private Connection** tab for you to view and manage them.
+
+
+
+View connections
+-------------------------------------
+
+On the **Private Connection** tab, you can perform the following operations:
+
+* Click the refresh icon to manually refresh the list.
+
+
+
+* Click **All Modes** to select the MySQL or Oracle mode.
+
+
+
+* Search for connections by using the search box.
+
+
+
+* Adjust the column width of the connection list.
+
+
+
+
+
+
+The following table describes columns in the list of private connections.
+
+
+| Column | Description |
+|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Connection Name | The name of the connection and the host, port, cluster, and tenant information. You can click the name of a connection to go to the corresponding connection management page. The icon before the connection name indicates the status of the connection. Blue indicates valid, red indicates invalid, and gray indicates that the database password is not saved. |
+| Cluster | The cluster information. You can click the filter icon  to filter the cluster information. If you select **Empty** , you can filter connections that do not belong to any clusters. |
+| Tenant | The tenant information. You can click the filter icon  to filter the tenant information. If you select **Empty** , you can filter connections that do not belong to any tenants. |
+| Tag | The tag of the connection. You can create a tag and assign it to a connection. You can assign only one tag to each connection. |
+| Operation Time | The time when the connection was edited, or the time when the connection was created if the connection has not been edited. |
+| Actions | The actions you can take. Valid values: **Open** , **Edit** , **Copy** , and **Delete** . |
+
+
+
+View connection history
+--------------------------------------------
+
+In the upper-right corner of the list, click **History** . The **Historical Opened Windows** panel appears.
+
+
+
+The panel shows a list that has the following columns.
+
+
+| Column | Description |
+|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Connection Name | The name of the connection you accessed. |
+| Database/Schema Name | The name of the database or schema that you accessed by using the connection. |
+| Recently Opened At | The time when you last accessed the connection. |
+| SQL/PL Window | The workspace window that you created when you accessed the connection. Move the pointer to a window name, and the script that you edited in the window is displayed. |
+| Actions | You can click **Open** to resume the connection in a new window. The corresponding workspace window and its content are also resumed. |
+
+
+**Note**
+
+
+
+By default, the historical records in the panel are saved for 48 hours. You can quickly restore the content in an unsaved SQL window based on records in the panel.
+
+Set a tag
+------------------------------
+
+ODC allows you to create a tag and assign it to a connection. You can assign only one tag to each connection.
+
+* Tag creation: You can create a tag by using the following two methods:
+
+ * Click **Set Tag** next to the **Connection Name** field in the **Create Connection** panel.
+
+
+
+ * Move the pointer in the tag column of the row where the target connection is located in the connection list, click **Set Tag** and click **Create Tag** in the drop-down list. On the **Tags** page, specify the name and color of the tag, and click the tick icon to complete the creation.
+
+
+
+
+
+
+* Tag setting: Select the target tag from the drop-down list that displays all the tags that you created, and modify related parameters to finish the setting.
+
+
+
+* Tag management: Click the settings icon in the upper-right corner of the drop-down list to go to the **Tags** page, where you can edit or delete created tags.
+
+
+
+
+
+
+Pin a connection to the top
+------------------------------------------------
+
+By default, the connections in the connection list are sorted by creation time, with the most recently created connection on top. The list does not support custom sorting, but you can pin frequently used connections to the top.
+
+You can click the flag  next to the name of a connection to pin the connection to the top. This turns the flag yellow. You can click the flag again to unpin the connection from the top.
+
+Edit a connection
+--------------------------------------
+
+Click **Edit** in the **Actions** column of the target connection. The **Edit Connection** panel appears, which has the same structure as the **Create Connection** panel and displays the configuration information of the current connection. You can edit the information displayed in the **Edit Connection** panel.
+
+Before you change **Database Password** , you must first click **Change Password** next to the password box. To abort the current change, click **Cancel** next to the password box, and the input in the password box is restored to its original value.
+
+Copy a connection
+--------------------------------------
+
+Click **Copy** in the **Actions** column of the target connection. The **Create Connection** panel appears. The copied information is automatically filled in the panel. This allows you to quickly create a connection by modifying existing information.
+
+The copy feature allows you to easily create database connections having similar information.
+
+Delete a connection
+----------------------------------------
+
+To delete a connection, click **Delete** in the **Actions** column of the target connection.
+
+For example, when the connected database no longer exists or you do not need to access the connected database, you can directly delete the corresponding connection.
+
+Other operations
+-------------------------------------
+
+* In addition to the management actions that the **Private Connection** tab provides, after you go to the management page of a database connection, the homepage menu icon  in the top navigation bar further provides the following buttons:
+
+ * **Open Connection in New Window** : After you click a connection in the connection list that appears, ODC opens the connection in a new window.
+
+
+
+ * **Connections** : Click this button to open the ODC homepage in a new window. On the ODC homepage, you can view and manage the configuration information of all connections.
+
+
+
+ * **Reload** : Click this button to reload the current page.
+
+
+
+ * **Exit Connection** : Click this button to exit the current connection and go to the ODC homepage.
+
+ 
+
+* On the database connection page, the `@{database name}` information is included in the window name of Client ODC.
+ 
+
+* Information such as the connection name, schema (in Oracle mode), and database name (in MySQL mode) appears in the top navigation bar of the workspace.
+
+ * Move your pointer over the connection name in the top navigation bar. In the tooltip that appears, you can see information in the following fields: **Connection Mode** , **Host/Port**, **Cluster/Tenant** , and **Database Username** .
+
+ * Click the drop-down arrow next to the displayed schema name or database name. In the drop-down list that appears, click a schema or database name to go to the target schema or database.
+
+ 
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/1.client-odc-use-workspace-overview.md b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/1.client-odc-use-workspace-overview.md
new file mode 100644
index 00000000..4d4a961f
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/1.client-odc-use-workspace-overview.md
@@ -0,0 +1,55 @@
+Overview
+=============================
+
+The workspace is the main feature module for you to develop databases in OceanBase Developer Center (ODC).
+
+After you enter the corresponding database connection, you can click **Workspace** in the navigation bar on the top of the page. The drop-down list provides the following features:
+
+* **SQL Window** : An SQL window is a working area for database developers to edit SQL and PL statements. ODC also provides the **Snippets** button in the SQL window.
+
+
+
+* **Anonymous Block Window** : An anonymous block window is a working area for database developers to edit anonymous block scripts. (The anonymous block window is available only in Oracle mode. )
+
+
+
+* **Command-line Window** : OceanBase command-line client OBClient is integrated in the form of a command-line window. It allows you to execute SQL or PL statements and view the execution results in real time.
+
+
+
+* **Stored Scripts** : Database developers can open scripts previously stored in ODC.
+
+
+
+* **Snippets** : View and reference built-in and custom code snippets
+
+
+
+> **Note**
+> Creating anonymous block windows is only supported in Oracle mode.
+
+
+This chapter describes these features in different topics.
+
+* [SQL window](../4.client-odc-use-workspace/2.client-odc-sql-window.md)
+
+
+
+* [Anonymous block window](../4.client-odc-use-workspace/3.client-odc-anonymous-block-window.md)
+
+
+
+* [Command-line window](../4.client-odc-use-workspace/4.client-odc-command-line-window.md)
+
+
+
+* [Stored scripts](../4.client-odc-use-workspace/5.client-odc-stored-scripts.md)
+
+
+
+* [Code snippets](../4.client-odc-use-workspace/6.client-odc-snippet.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/2.client-odc-sql-window.md b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/2.client-odc-sql-window.md
new file mode 100644
index 00000000..85c19a29
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/2.client-odc-sql-window.md
@@ -0,0 +1,149 @@
+SQL window
+===========================
+
+
+
+Overview
+-----------------------
+
+On the Database Management page of OceanBase Developer Center (ODC), click **Workspace** in the top navigation bar and click **SQL Window** in the drop-down list that appears.
+
+The SQL window provides an SQL editing area for editing scripts, an execution record tab, and a result tab for displaying the execution results. The SQL window also supports executing PL/SQL statements.
+
+
+
+SQL editing area
+-----------------------------
+
+The SQL editing area provides many features for you.
+
+| Operation | Description |
+|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Auto-complete | The SQL editing area provides the auto-complete feature to improve your SQL statement editing efficiency. For example, when you edit SQL statements, the table name is auto-completed for cross-database queries. |
+| Intelligent identification of keywords and code | Database keywords are highlighted in different colors, and PL/SQL statements are identified. |
+| Right-click of object names in the `SELECT` statement | When you right-click the name of a table, view, or function in a `SELECT` statement, some common operations are displayed. When you place the pointer over the name of a table, the field information is displayed. |
+| Object drag-and-drop | You can directly drag objects from the object list into an SQL statement in the SQL editing area to fill in an object name in the statement. - After you drag a table or view and drop it into the SQL editing area, you can select the type of the SQL statement to be generated in the **Fast Generation** dialog box. You can click the username and select **Personal Settings** from the drop-down list, and set the default statement type in the **Type of Statements Generated by Dragging and Dropping Object** field of the **Edit Personal Settings** panel. - If you drag an object other than a table or view, the object name is directly dropped into the SQL editing area.  |
+| Shared and independent sessions | The SQL window of ODC supports **Shared Session** and **Independent Session** modes. - If you select **Shared Session**, you can open multiple SQL windows in the same connection, but cannot execute SQL statements in multiple windows in parallel. - If you select **Independent Session**, you can open multiple SQL windows in the same connection, and execute SQL statements in multiple windows in parallel. To open a new SQL window, click **+** next to the existing SQL window tab. By default, SQL windows are in Shared Session mode. You can click the username in the upper-right corner of the top navigation bar, select **Personal Settings** from the drop-down list, and set the session mode to **Independent Session** on the **Edit Personal Settings** panel.  |
+| Identification of special symbols | Special symbol abnormality can be identified in the editing area of the SQL window, where abnormal symbols are marked with yellow wavy underlines. |
+| Viewing the execution status | When you hover the pointer over an SQL window tab, the window name and execution status are displayed.  |
+
+
+> **Note**
+> In Oracle mode, the autocommit feature of ODC is set to OFF by default. You can change the transaction commit mode by modifying the value of the `autocommit` variable in the following two ways: click the Settings icon in the upper-right corner of the SQL window and modify the variable in the Session Variables dialog box, or click Session in the top navigation bar and modify the variable on the Session Properties page. Note that the settings in the Set session variable dialog box are valid only for the current SQL window. For more information, see [Manage sessions](../../6.web-odc-user-guide/10.web-odc-session-management.md).
+> In manual-commit mode, make sure to set `ob_trx_idle_timeout` to a value greater than the timeout value of SQL queries. Otherwise, if two SQL statements in one transaction are executed at an interval longer than the value of `ob_trx_idle_timeout`, the connection will be terminated. However, if the `ob_trx_idle_timeout` parameter is set to an excessively large value, the session cannot be released in time, resulting in unnecessary memory consumption. Therefore, you must set this parameter to a proper value.
+
+
+
+In addition to the preceding features, the toolbar of the editing area provides the following icons.
+
+| Icon | Description |
+|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Run | Click this icon to execute all the SQL statements in the current window. This icon is disabled if an SQL statement is being executed in another window of the same session. |
+| Run Current Statement | Click this icon to execute all the selected SQL statements or the SQL statement in the line where the pointer is located. This icon is disabled if an SQL statement is being executed in another window of the same session. |
+| Abort | Click this icon to abort the statement that is being executed. |
+| Execution Plan | Click this icon to view the execution plan for the SQL statement that you select or on which the pointer is located. This execution plan is estimated by the system before execution and is the result of the `EXPLAINPLAN` operation. Therefore, the execution data displayed may differ from the actual execution data. You can use this feature to evaluate SQL statements. Click **Execution Plan**. On the **Plan Details** tab, click **View Formatting Info** to switch to the formatted view. |
+| Find and Replace | Click this icon and enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+| Undo | Click this icon to undo the last operation. |
+| Redo | Click this icon to reverse an **Undo** operation. |
+| Format | Click this icon to apply formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+| IN Value Conversion | Click this icon to convert the copied rows or columns into the specified format during queries. After you paste the copied data to the SQL editing area, select the copied data and click **IN Value Conversion** to convert it into the in('A','B') format. - Column values are separated with line breaks. - Row values are separated with spaces or tabs. |
+| Case Sensitivity | The system supports three configurations: **All Caps**, **All Lowercase**, and **Capitalize First Letter**. Click this icon to convert the selected statements in the script to the corresponding capitalization format. |
+| Indent | You can add indents to or delete indents from the statements that you selected. |
+| Comment | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+| Save script | Click this icon to save the script in the current window. You can open a saved script when you enter the workspace again. You can view only the SQL scripts saved by yourself. The script names must be unique. After you open a stored script, you can continue to edit it. |
+| Settings | - **Delimiter**: Select the character that you want to use as the delimiter from the drop-down list. Five types of delimiters are supported: semi-colons (;), slashes (/), double slashes (//), dollar signs ($), and double dollar signs ($$). - **Query Result Limit**: Set the maximum number of lines that a query can return. Default value: 1000. - **Session Variables**: You can edit, refresh, and search for variables. |
+| Snippet | Click this icon to view and reference built-in and custom code snippets. For more information, see [Snippet](../4.client-odc-use-workspace/6.client-odc-snippet.md). |
+| Commit | - By default, `autocommit` is set to `OFF` in Oracle mode. You need to click this icon to commit the current transaction. After you click this icon, a dialog box appears, indicating that the current connection uses a shared session and the commit will apply to all windows. Click **Yes** to commit the transaction. - In MySQL mode, `autocommit` is set to `ON` by default, and this icon is not displayed. This icon is disabled if an SQL statement is being executed in another window of the same session. **Note** You can change the value of the `autocommit` variable in the following two ways: click the **Settings** icon in the upper-right corner of the SQL window and set the variable in the **Session Variables** dialog box, or click **Sessions** in the top navigation bar and set the variable on the **Session Properties** page. |
+| Rollback | - In Oracle mode, if the `autocommit` variable in the **Session Variables** dialog box is set to `OFF`, click this icon to roll back the current transaction. After you click this icon, a dialog box appears, indicating that the current connection uses a shared session and the rollback will apply to all windows. Click **Yes** to apply the rollback. - In MySQL mode, the `autocommit` variable in the **Session Variables** dialog box is set to `ON`, and this icon is not displayed. This icon is disabled if an SQL statement is being executed in another window of the same session. |
+
+
+
+Execute PL/SQL statements
+-----------------------------
+
+You can edit a PL/SQL statement in the SQL window. Note that you must end the PL/SQL statement with the specified delimiter.
+
+At present, you can use the following methods to specify a delimiter in ODC:
+
+* Click **Settings** in the toolbar of the SQL editing area. In the window that appears, select the delimiter as needed in the **Delimiter** field.
+
+
+
+* On the **Personal Settings** page, select a required delimiter in **Delimiter Settings**.
+
+
+
+* The compilation error information displayed includes the PL/SQL row ID and the position at which the error occurred.
+
+* Right-click the PL object in the left navigation bar and select **Run**, which supports setting the parameter value as DEFAULT, NULL or empty string.
+
+ > **Notice**
+ > * In ODC V2.4.1 and later, you can use the `DELIMITER` statement in the editing area to define a delimiter. In **Settings**, the **Delimiter** field displays the delimiter that you specified.
+ >
+ > * You can use slashes (/) to separate PL/SQL statements.
+
+After you execute a PL/SQL statement in the SQL window, the result tab displays the database management system (DBMS) output.
+
+
+
+Execution Records tab
+---------------------------
+
+
+
+On the **Execution Records** tab, you can view the history of SQL statements executed in the current connection. You can view the information in several columns, such as **Status**, **Time**, **SQL Statement**, **Results**, **Trace ID**, **Time Spent**, and **Execution Details**. The execution details constitute the execution plan.
+
+| Column | Description |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Check box | You can select the check box in front of one or more records and then click **Delete** in the upper-right corner of the list to delete the selected records. |
+| TRACE ID | The ID of the execution record. **Notice** If **TRACE ID** is empty, make sure that the `enable_sql_audit` and `ob_enable_trace_log` parameters are set to `ON` when the statement is executed. Procedure: 1. Choose **Sessions** > **Session Properties** > **Session Variables** and search for the `enable_sql_audit` and `ob_enable_trace_log` parameters. 2. Click the **Edit** icon on the **Session Variables** tab. In the **Edit Variable** dialog box, change **OFF** to **ON** and click **OK**. 3. Execute the following statement to enable the system parameter: ```sql obclient> alter system set enable_sql_audit='True'; Query OK, 0 rows affected (0.06 sec)``` |
+| DB Time | You can hover the pointer over the icon next to a value in the **DB Time** column. In the prompt box that appears, you can view the total execution duration of the SQL statement and verify whether the duration of each phase adds up to the total execution duration. |
+| Execution Details | By default, the execution plan is displayed in text. In the **Execution Details** column, click **View**. The **Execution Details** page displays the basic information, time spent, I/O statistics, executed SQL statements, plan statistics, and outlines. |
+
+
+
+Logs tab
+-------------------------
+
+You can view the execution records of the current SQL window in the Logs tab.
+
+
+
+Result tab
+-------------------------
+
+
+
+You can view the execution result of the current SQL statement on the **Result** tab. The result set in the Result tab can be used in the following interactive operations to facilitate daily development work.
+
+| Operation | Description |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Select required data | You can select the required data of a result set and copy the data to an external file by using hotkeys. You can also click a field name or row ID to select an entire row or column. You can also click **Export** in the toolbar to export data of a result set to a local file. |
+| Select rows and columns |
You can select consecutive rows or columns while holding the **Shift** key.
You can select inconsecutive rows or columns while holding the **Ctrl** or **Command** key.
|
+| Right-click a cell | You can right-click a cell and select **Copy** or **Export to Clipboard** to directly export the data into an external file. |
+| Right-click a row ID | You can right-click a row ID and select **Copy Row**, **Freeze this row**, or **Unlock all frozen rows**.
**Copy Row**: Click this option to copy the selected row.
**Freeze this row**: Click this option to freeze the selected row and pin it to the top. You can freeze multiple rows. The rows under the table header and frozen rows can be vertically scrolled.
**Unlock all frozen rows**: Click this option to unfreeze all frozen rows.
|
+| Zoom in | If the data in a cell is too long and cannot be fully displayed, you can hover the pointer over the cell and click the zoom-in icon  at the right end of the cell. In the window that appears, view the data in full.
**Note** LOBs are displayed in text by default. You can convert an LOB into the hexadecimal format and download the LOB to a local device. |
+| View BLOBs |
In Oracle mode, you can directly edit text data of the CLOB, BLOB, or RAW type, edit hexadecimal data, and upload files that are not greater than 200 KB in size.
In MySQL mode, you can directly edit text data of the XLOB type such as BLOB, MEDIUMBLOB, or TINYBLOB, edit hexadecimal data, and upload files.
|
+| Right-click the tab name of a result tab | For example, you can right-click the tab name of the **Result 1** tab and click **Pin** in the context menu to pin the tab, so that it remains displayed. In this way, when you execute a new query, a new result tab appears but does not overwrite the pinned result tab. This allows you to compare the query results. Click **Unpin** to unpin a result tab. |
+| Filter, sort, and search for data | Each field name in the result set is provided with a filter icon, a sort icon, and a search icon. You can use them to filter, sort, and search for data in a single column. |
+| Drag the column name | You can adjust the order of fields by dragging column names in a result set. |
+| Adjust the column width | You can adjust the column width by dragging the column edge. |
+
+
+
+The navigation bar of the **Result** tab also provides the following tools.
+
+| Tool | Description |
+|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Column Mode | Click this icon to display the selected data row in the form of a table. On the **Column Mode** tab, you can switch to the previous or next row. ****The column mode makes it easier to view data in a row that has many columns. Procedure: 1. Select the data that you want to view and click **Column Mode** . 2. On the **Column Mode** tab, click the left or right arrow to switch between the column values of adjacent rows. 3. Hover the pointer over a value field and click the zoom-in icon  to view the details. 4. In the table on the **Column Mode** tab, you can view the comments for a column in the **Remarks** column. Perform the following steps to modify the comments: a. In the left-side navigation pane, right-click the target table and select **View Table Structure** to go to the **Attribute** tab. b. In the left-side navigation pane of the **Attribute** tab, click the **Column** tab. c. Select a field and click the **Edit** icon. The field editing dialog box appears. d. In the **Comment** field , edit the comments, and click **OK**. e. In the **SQL Confirmation** dialog box, click **Execute**. f. View the modified comments on the **Column Mode** tab. |
+| Columns | Click this icon to select the columns to be displayed on the page. |
+| Back to Start | Click this icon to go back to the first page. |
+| Previous | Click this icon to go to the previous page. |
+| Next | Click this icon to go to the next page. |
+| Jump to Bottom | Click this icon to go to the last page. |
+| Search | Enter a keyword in the search box to search for the desired results. |
+| Edit | Click **Edit** to enable editing mode for the current result set. The editing mode supports the following operations: **Add**, **Copy Current Row**, **Delete**, **Cancel**, **Confirm Modification**, which submits a transaction when autocommit is enabled, and **Modify and Submit**, which is displayed when autocommit is disabled. In the editing mode, you can either double-click target data to directly modify it or click the preceding icons for convenient operations. When you edit a cell, you can right-click the cell and select **Copy** or **Set to Null** from the context menu to operate on the cell. **Note** The ResultMetaData information is obtained during the execution of an SQL statement to indicate whether the result set can be edited. - If the result set cannot be edited, the Edit icon is not displayed and you are prompted that the result set cannot be edited. - If the result set can be edited, the Edit icon is available and you can click it to go to the result set editing page. You can edit result sets in single-table and single-view queries. - However, result sets that involve the SET and ENUM fields cannot be edited. |
+| Download Data | You can export the query results to a CSV, SQL, or Excel file. - To export the query results to an SQL file: Edit the SQL statements in the **SQL Query** field, specify **Maximum Number of Lines in Result Set**, **File Name**, **File Format** (SQL)**,** **File Encoding**, **Data Desensitization**, and **SQL File Settings** (**Table Name** ). - To export the query results to a CSV file: Edit the SQL statements in the **SQL Query** field, specify **Maximum Number of Lines in Result Set**, **File Name**, **File Format**, **File Encoding**, and **Data Desensitization**. In the **CSV File Settings** section, specify **Include the Column Header**, **Convert the Empty Character String into a Null Value**, **Field Separator**, **Text Identifier**, and **Line Break Symbol**. - To export the query results to an EXCEL file: Edit the SQL statements in the **SQL Query** field, specify **Maximum Number of Lines in Result Set**, **File Name**, **File Format**,**File Encoding**, and **Data Desensitization**. In the **Excel File Settings** section, specify **Include the Column Header** and **Export SQL statements to another sheet**. **Note** - You can desensitize the exported data. You can specify a custom number of rows to export as needed. - If you export data in CSV format, the exported CSV file can be opened by Microsoft Excel. - If you export data in XLS format, you can specify whether to include the column header and whether to export the SQL statements of the query.  |
+| Plan | Click this icon to view the actual resource consumption and execution plan of an executed SQL statement. This allows you to evaluate the performance of the statement. |
+
+
diff --git a/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/3.client-odc-anonymous-block-window.md b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/3.client-odc-anonymous-block-window.md
new file mode 100644
index 00000000..127d1f47
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/3.client-odc-anonymous-block-window.md
@@ -0,0 +1,113 @@
+Anonymous block window
+===========================================
+
+
+
+Overview
+-----------------------------
+
+To open an anonymous block window, perform the following steps: enter the Database Management page of OceanBase Developer Center (ODC), click **Workspace** in the top navigation bar, and click **Anonymous Block Window** .
+
+An anonymous block window provides a **PL/SQL editing** area, the **PL/SQL Execution Result and DBMS Output** tabs, and the **Debugging** page.
+
+
+
+PL editing area
+------------------------------------
+
+The editing area of the anonymous block window provides many features for you. For example, when you open a new anonymous block window,
+
+* the guidance code is provided to make your script-writing easier.
+
+
+
+* Database keywords are highlighted in different colors.
+
+
+
+* It also provides features such as formatting to help you improve your PL/SQL statement writing efficiency.
+
+ In addition to the preceding features, the toolbar of the editing area provides the following buttons.
+
+
+ | Button | Description |
+ |------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+ | Run | Click this button to execute the statements in the code area. |
+ | Abort | Click this button to abort the statement that is being executed. |
+ | Debug | Click this button to open the debugging page to debug the anonymous objects in the code area. |
+ | Format | Click this button to apply the formatting, such as indentation, line break, and keyword highlighting, to the selected SQL statements or all the SQL statements in the current SQL window. |
+ | Find and Replace | You can enter text in the search field to find the specific content and enter text in the replacement field to replace the content found. |
+ | Undo | Click this button to undo the last operation. |
+ | Redo | Click this button to reverse an **Undo** operation. |
+ | Case Sensitivity | The system supports three capitalization options: **All C** **aps** , **All Lowercase** , and **Capitalize First Letter** . Click the corresponding option to convert the selected statements in the script to the desired capitalization format. |
+ | Indent | You can add indents to or delete indents from the statements that you selected. |
+ | Comments | You can click **Add Comments** to convert the statements that you select into comments or click **Delete Comment** to convert comments to SQL statements. |
+ | Save | Click this button to save the script in the current window. You can open a saved script when you enter the workspace again. **Note** * You can view only the SQL scripts saved by yourself. The script names must be unique. * After you open a saved script, you can continue to edit it. |
+
+
+
+
+
+
+PL/SQL Execution Result and DBMS Output tabs
+-----------------------------------------------------------------
+
+After you click the run iconin the toolbar of the editing area to execute the anonymous block, you can view the information in the **Execution Result** and **DBMS Output** tabs under the editing area.
+
+* The **Execution Result** tab displays the execution result of the script. If the execution was successful, **Executed** is displayed. Otherwise, an error message is displayed.
+
+* The **DBMS Output** tab displays the output of a subprogram that contains PL/SQL output statements, such as `dbms_output.put_line`.
+
+
+
+
+Debugging page
+-----------------------------------
+
+You can debug an anonymous block on the debugging page. To enter this page, click **Debug** in the toolbar of the editing area.
+
+On the debugging page, you can debug the anonymous block.
+
+
+> **Notice**
+>
We recommend that you upgrade to OBServer V2.2.77 or later. This is because some versions of OBServer have been found with PL/SQL debugging issues, which may compromise the OBServer stability.
+>
ODC V3.2.2 or earlier does not support the debugging feature when you connect ODC to the target instance by using OBProxy. To use the debugging feature, directly connect ODC to the target instance.
+>
ODC V3.2.2 and later support PL/SQL debugging when you connect to OBServer by using OBProxy.
+>
You have installed the debugging packages such as DBMS_DEBUG and DBMS_OUTPUT in the connected database.
+
+
+
+
+
+
+
+
+In debugging mode, the toolbar in the editing area provides the following buttons.
+
+
+| Button | Description |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Batch Execute | Runs till the next breakpoint. If no breakpoint exists, runs till the end. |
+| Step Over | Click this button to step over a given line without stepping into any subprogram. |
+| Step Into | Click this button to execute code line by line. If the line includes a call to a stored procedure or function, it steps into the called subprogram. |
+| Step Out | For a subprogram, you can click this button to return to the next line of the upper-layer call position. For the main program, this button achieves the same effect as **Auto Debugging** . |
+| Abort Debugging | Click this button to execute the stored procedure till the end and skip breakpoints. |
+| Debug Again | Click this button to initiate a new round of debugging on the current object. Unlike **Debug** , it does not establish a new debugging connection. |
+| Exit Debugging | Click this button to close the debugging connection and exit the debugging window. |
+
+
+
+In addition to the editing area, the debugging mode also provides the following tabs:
+
+* **Parameters** : displays the definition information and values of all the parameters of the object to be debugged. The definition information includes the parameter name, mode, and type. The values may change as a result of the debugging process.
+
+* **Stacks and Variables** : displays the variables in the current stack and the values of the variables.
+
+* **DBMS Output** : If a subprogram contains PL/SQL output statements, such as `dbms_output.put_line`, the output is displayed on this tab.
+
+* **Breakpoint** : You can click the line number in the editing area to set a breakpoint, and click the line number again to remove the breakpoint. The Breakpoint tab displays all the breakpoints that you set in their execution order. You can select multiple breakpoints to cancel them at a time. The Actions column of each breakpoint information row provides the **Cancel** and **View** actions. You can click Cancel to cancel a breakpoint. After you click View, the cursor moves to the location of the breakpoint in the editing area.
+
+* **Debugging Logs** : displays the debugging logs and error logs. Debugging logs include information about the start and end of debugging and the addition and cancellation of breakpoints.
+
+
+
diff --git a/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/4.client-odc-command-line-window.md b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/4.client-odc-command-line-window.md
new file mode 100644
index 00000000..aaf9df75
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/4.client-odc-command-line-window.md
@@ -0,0 +1,48 @@
+Command-line window
+========================================
+
+OceanBase Developer Center (ODC) integrates the OceanBase command-line client OBClient in the form of a command-line window. OBClient is the recommended command-line client for OceanBase. The command-line window allows you to use OBClient without a need to download or install it. It allows you to execute SQL or PL statements and view the execution results in real time. It also allows you to run the `SOURCE` command to execute files uploaded to the server.
+
+Create a command-line window
+-------------------------------------------------
+
+Log on to ODC and click the name of the target connection to go to the corresponding connection management page. Click **Workspace** in the navigation bar on the top of the page and select **Command-line Window** from the drop-down list, to create a command-line window. The window that opens automatically connects to the current instance, and displays a default code segment that contains the connection ID, version information, and help information.
+**Notice**
+
+
+
+You can create up to three command-line windows at a time.
+
+If a command-line window is disconnected, the **Reconnect** button appears in the upper-right corner of the command-line window. Click the button to reconnect the window.
+
+Script management
+--------------------------------------
+
+If you need to reference a script in your development work, you can the **Script Management** feature of the **Command-line Window** to import the script and then reference it.
+
+To reference a script, perform the following steps:
+
+1. Enter Script Management panel.
+
+ Click the **Script Management** button in the upper-right corner of the command-line window to open the **Script Management** panel.
+
+
+2. Import the script that you want to reference.
+
+ Click the file pool under **Import Script** to start the file explorer, and select the script that you want to reference. Alternatively, you can directly drag the script file into the file pool to upload it. The maximum file size supported is 250 MB.
+
+
+3. Obtain the file path.
+
+ After the script is uploaded, you can view information about the script in the **Scripts** table in the panel. The table contains the following columns: **Script Path** , **Script Name** , **File Size** , and **Uploaded At** . To reference a script, click the **Copy Path** button in the Actions column and paste the path in the command-line window.
+
+
+4. Delete a script file.
+
+ You can view only script files uploaded by yourself. A file will be automatically deleted 30 minutes later after it is uploaded, to avoid unnecessary space consumption. You can also click the **Delete** button in the Actions column to delete a file.
+
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/5.client-odc-stored-scripts.md b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/5.client-odc-stored-scripts.md
new file mode 100644
index 00000000..0f590dc6
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/5.client-odc-stored-scripts.md
@@ -0,0 +1,113 @@
+Stored scripts
+===================================
+
+Log on to OceanBase Developer Center (ODC), and click the name of the target connection to go to the corresponding connection management page. Click **Workspace** in the top navigation bar, choose **Stored Scripts** from the drop-down list, and then choose a script that you previously stored in an SQL window or anonymous block window.
+
+Overview
+-----------------------------
+
+
+
+After you choose the script, you can proceed to edit or run the script. If the script is an SQL script, ODC opens the script in an SQL window. If the script is an anonymous block script, ODC opens the script in an anonymous block window. In the script list, buttons with the following features are provided after each script name.
+
+
+| Feature | Description |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Edit | Click  to modify the name and content of the script. |
+| Delete | Click  to delete the script. |
+| Script management | Click  to edit, import, download, or delete scripts. |
+
+
+
+Script management
+--------------------------------------
+
+### Edit a script
+
+
+
+1. Log on to the ODC homepage, and click the name of the target connection to go to the corresponding database object management page. Choose **Workspace** \> **Stored Scripts** .
+
+
+
+2. Select a script from the drop-down list of **Stored Scripts** , and click  to go to the Edit Script panel. You can also click  to go to the Script Management panel, select a script, and click Edit.
+
+
+
+3. In the **Edit Script** panel, modify **Script Name** and **Script Content** and click **Save** .
+
+
+
+
+
+
+### Delete a script
+
+1. Log on to the ODC homepage, and click the name of the target connection to go to the corresponding database object management page. Choose **Workspace** \> **Stored Scripts** .
+
+
+
+2. Select a script from the drop-down list of **Stored Scripts** and click  to delete it.
+
+
+
+
+
+
+### Manage scripts
+
+
+
+1. Log on to the ODC homepage, and click the name of the target connection to go to the corresponding database object management page. Choose **Workspace** \> **Stored Scripts** .
+
+
+
+2. Click **Stored Scripts** , and then click  in the drop-down list to go to the Script Management panel.
+
+3. In the Import Script section, click or drag files to import one or more scripts.
+
+ > **Note**
+ > - The size of a single file cannot exceed 250 MB.
+ > - Files suffixed with .sql, .pl, and .txt are supported.
+
+
+
+
+
+
+
+4. Take the following actions in the script list:
+
+ * Click  to refresh the script list.
+
+
+
+ * Enter a script name in the search box to search for the script.
+
+
+
+ * Click  the check box to select multiple scripts for batch download or deletion.
+
+
+
+ * Click **Copy Path** to copy the script path.
+
+
+
+ * Click **Edit** to edit the script.
+
+
+
+ * Click **Download** to download the script.
+
+
+
+ * Click **Delete** to delete the script.
+
+
+
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/6.client-odc-snippet.md b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/6.client-odc-snippet.md
new file mode 100644
index 00000000..7e8672f4
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/4.client-odc-use-workspace/6.client-odc-snippet.md
@@ -0,0 +1,80 @@
+Snippet
+============================
+
+As an enterprise-grade database development platform, OceanBase Developer Center (ODC) provides the code snippet module to facilitate database development. If you forget about the usage of some statements, you can query in the code snippet module. The code snippet module provides suitable code snippets based on whether you are in Oracle or MySQL mode. In addition to the built-in code snippets, you can also create custom code snippets to store frequently used code segments. A custom code snippet can be viewed only by its creator.
+
+To open the Snippets panel, click **Snippets** in the toolbar of an SQL window, an anonymous block window, or a PL object editing page.
+
+View code snippets
+---------------------------------------
+
+In the Snippets panel, the code snippets are displayed in a list of cards. Each card displays information about a code snippet, such as its name, description, and type. When you place the pointer over the tips icon next to a code snippet name, a tip window appears, displaying the entire code in the snippet.
+
+You can directly search for specific code snippets in the search box above the card list. A filter is provided below the search box for you to filter code snippets by type. The filter provides the following options: **Others** , **DML** , **DDL** , **Process Control Statement** , and **All Types** . By default, All Types is selected.
+
+Create a code snippet
+------------------------------------------
+
+Click the **+Create** button in the upper-right corner of the code snippet list. The **Create Snippets** panel appears. Specify the following information in the panel:
+
+* **Snippet Name** : specifies the name of the code snippet. It can contain letters, digits, and underscores (_), and can contain a maximum of 60 characters. This parameter must be specified.
+
+
+
+* **Snippet Type** : specifies the type of the code snippet. The types include **Others** , **DML** , **DDL** , and **Process Control Statement** . By default, **Others** is selected.
+
+
+
+* **Snippets** : specifies the actual code of the snippet. The length cannot exceed 2000 characters. This parameter must be specified. Similar to the SQL window, the toolbar of the editing area also provides buttons such as Format, Find and Replace, Undo, Redo, Case Sensitivity, Indent, and Comment. It also provides code highlighting and association features.
+
+
+
+* **Snippet Description** : provides additional notes on the code snippet. The length cannot exceed 200 characters. This parameter is optional.
+
+ **Note**
+
+
+
+ If you specified an additional notes in the description field, the snippet card in the Snippets panel displays the notes. Otherwise, the first 30 characters of the code are displayed.
+
+
+
+
+
+
+
+Reference a code snippet
+---------------------------------------------
+
+You not only can view the content of a created code snippet when you edit scripts, but also can reference it in your script. You can reference a code snippet by using one of the following three methods:
+
+* Method 1: Drag the target card from the code snippet list to the editing area, and the code in the code snippet is copied to the editing area.
+
+
+
+* Method 2: Click the copy icon in the lower-right corner of the target code snippet card to copy the code, and then press Ctrl+V or Cmd+V to paste the code to the editing area.
+
+
+
+* Method 3: The editing area of the SQL window supports code association. When you edit a script in the editing area, existing code snippets appear in the code association window for you to view and reference.
+
+
+
+
+
+
+Manage code snippets
+-----------------------------------------
+
+ODC provides the **Edit** and **Delete** options for you to manage custom code snippets. You cannot edit or delete built-in code snippets.
+
+* **Edit** : Click the management icon (···) in the upper-right corner of the target code snippet card. In the menu that appears, click the **Edit** button to go to the **Edit Snippet** panel. The panel displays parameters such as **Snippet Name** , **Snippet Type** , **Snippets** , and **Snippet Description** that were specified at creation of the code snippet. You can modify the information as needed.
+
+
+
+* **Delete** : Click the management icon (···) in the upper-right corner of the target code snippet card. In the menu that appears, click the **Delete** button to delete the code snippet.
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/1.client-odc-data-export-and-import-overview.md b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/1.client-odc-data-export-and-import-overview.md
new file mode 100644
index 00000000..419244e7
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/1.client-odc-data-export-and-import-overview.md
@@ -0,0 +1,33 @@
+Overview
+=============================
+
+OceanBase Developer Center (ODC) provides the database import and export features and the table import and export features, to facilitate database data maintenance for database developers. The database import and export features allow you to import data to or export data from selected tables in the database in batches. The table import and export features allow you to import data to or export data from the target table.
+
+ODC provides a **Task Center** page. After you create an import or export task, this page displays the current import or export task. You can also view task details and logs on this page.
+
+> **Notice**
+>
OceanBase Database of a version earlier than V2.2.30 supports only UTF8.
+>
In ODC V2.2.1 and earlier versions, to use the import and export features, you must connect ODC to the target instance through OBProxy. If you directly connect ODC to the target instance, the import and export features are unavailable.
+>
In ODC V2.4.1 and later, you can use the sys tenant account to accelerate the import and export tasks. To export objects other than tables and views, you must configure the sys tenant account.
+
+
+
+
+
+
+This chapter describes the import/export features in different topics.
+
+* [Export and import formats](../1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md)
+
+
+
+* [Batch export and import](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/3.web-odc-batch-export-and-import.md)
+
+
+
+* [Single table export and import](../../../6.web-odc-user-guide/6.web-odc-use-tools/1.web-odc-data-export-and-import/4.web-odc-single-table-export-and-import.md)
+
+
+
+
+
diff --git a/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md
new file mode 100644
index 00000000..5705959e
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md
@@ -0,0 +1,30 @@
+Export and import formats
+==============================================
+
+OceanBase Developer Center (ODC) supports three data export modes: Export Schema and Data, Export Data Only, and Export Schema Only. A schema is the DDL file of an exported object, while data is the data file stored in the object. The types of schemas and data files vary with the export and import formats.
+
+ODC supports exporting data in CSV and SQL formats and importing ZIP, SQL (batch import), and CSV (single table import) files.
+
+Export file formats
+----------------------------------------
+
+ODC exports data in a zip file, which contains the metadata file MANIFEST.bin, the schema definition files of the exported objects, and the data files.
+
+When you create an export task, if you set **Data Format** to **SQL Format** , the zip file contains the schema definition files named in the pattern of `object_name-schema.sql` and data files named in the pattern of `object_name.sql`. The object names are the same as those of the objects in the database.
+
+
+
+If you set **Data Format** to **CSV Format** , the zip file contains the schema definition files named in the pattern of `object name-schema.sql` and data files named in the pattern of `object name.csv`. The object names are the same as those of the objects in the database.
+
+
+
+Import file formats
+----------------------------------------
+
+ODC supports importing ZIP (batch import and single table import), SQL (batch import), and CSV (single table import) files.
+
+The ZIP file here is a compressed package that is suffixed with .zip. When you create an import task, if you select **ZIP Files** as the **Import Content** , you must specify whether **Data Format** in the zip file is **CSV Format** or **SQL Format** . For more information about the content of different formats of files to be exported, see **Export file formats**.
+
+SQL files supported for batch data import are suffixed with .sql and contain statements that can be directly executed in the database. These statements include `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `CREATE`, and `DROP`.
+
+CSV files supported for single table import are data files that are suffixed with .csv or .txt. These files support custom delimiters.
diff --git a/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/3.client-odc-batch-export-and-import.md b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/3.client-odc-batch-export-and-import.md
new file mode 100644
index 00000000..c0fac5b7
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/3.client-odc-batch-export-and-import.md
@@ -0,0 +1,241 @@
+Batch export and import
+============================
+
+
+
+Overview
+-----------------------
+
+OceanBase Developer Center (ODC) allows you to export and import the schemas and data of database objects in batches.
+
+After you open a database connection, click **Tools** in the top navigation bar, and then select **Export**or **Import** from the drop-down list to go to the corresponding settings panel.
+
+The following table describes the requirements for the size of imported and exported data and the retention period of files in ODC.
+
+| Requirement | Description |
+|------------------------|------------|
+| File retention period on the server |
The status of a task, such as Succeeded, Failed, and Canceled, does not affect the lifecycle of the task files.
Tasks are permanently retained. Task-related files are retained for 14 days by default.
|
+
+
+
+Batch export
+-------------------------
+
+In the **Create Export Task** panel, you can export multiple database objects to files in the specified format at the same time.
+
+
+
+
+The following example shows how to batch export the employee table and the salary view in the ODC. Procedure:
+
+### Step 1: Specify the export content
+
+As shown in the preceding figure, ODC supports three export modes: **Export Schema and Data**, **Export Data Only**, and **Export Schema Only**. **Export Schema Only** exports the definition statements of the target object. You can select the export content from the **Export Content** drop-down list.
+
+### Step 2: Select a database
+
+Select the database where the object to export resides. The name of the database connection to which the task belongs is also displayed.
+
+### Step 3: Specify the export range
+
+You can select **Partial Export** or **Full Export**.
+
+* If you select **Partial Export**, you can select the objects you want to export in the **Select Objects** pane in the **Export Objects** section. You can use the search box to search for desired objects.
+
+
+
+* If you select **Full Export**, all objects in the database are exported.
+
+
+
+
+
+
+### Step 4: Go to the Export Settings panel
+
+Click **Next: Export Settings** to specify the file export settings and the sys tenant account.
+
+### Step 5: Go to the Data File Settings panel
+
+
+
+1. Specify Data Format.
+
+ ODC supports exporting data to files in the CSV format and SQL format. If you specify **Export Schema Only** for **Export Content**, you can only export data to files in the SQL format. For more information about formats, see [Export and import formats](../1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md).
+
+
+2. Specify File Encoding.
+
+ ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+
+3. Specify Data File Settings.
+
+ If you select **Export Schema Only** for **Export Content**, you do not need to configure the export data settings. You need to specify the following fields:
+
+ * **Use Global Snapshot**: If you select this option, ODC exports the data in the latest global snapshot of the specified table to ensure global data consistency.
+
+
+
+ * **Batch Commit Quantity (SQL Format)**: You can click **Advanced** next to **Export Data Settings** to specify this field. If you select **SQL Format** for **Data Format**, you can specify the number of rows to be committed during the export. When this number is reached, a `COMMIT` command is executed.
+
+
+
+ * Specify information for the CSV format. If you select **CSV Format** for **Data Format** and **Export Schema and Data** for **Export Content**, you can specify following information:
+
+ * **Include the Column Header**: specifies whether to include column headers when data is exported in CSV format. This option is selected by default.
+
+
+
+ * **Convert the Empty String into a Null Value**: This option is selected by default to determine whether to convert empty strings in the table to NULL values when data is exported in CSV format.
+
+
+
+ * **Field Separator**: specifies the separator between fields. The following signs are supported: commas, semicolons, and colons. You can also use a character as the separator.
+
+
+
+ * **Text Identifier**: specifies the identifier for the text content. Single quotation marks (') and double quotation marks (") are supported.
+
+
+
+ * **Line Break Symbol**: specifies the line break symbol. The following characters are supported: \\n, \\r, and \\r\\n.
+
+
+
+### Step 6: Specify schema file settings
+
+Choose whether to select **Add DROP TABLE Statement before CREATE TABLE Statement**. If you select this option, a `DROP` statement is added before the corresponding `CREATE` statement of an object when the schema files of the object are exported.
+
+### Step 7: Select an execution method
+
+Select **Execute immediately** or **Timed execution**.
+
+### Step 8: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+**Notice**
+- The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+
+
+- If the account of the sys tenant is not configured, comments and indexes are not imported or exported.
+
+
+### Step 9: Retain Current Configuration
+
+Check **Retain Current Configuration** to keep the current part of the data file and structure file configuration.
+
+
+### Step 10: Generate an export task
+
+After you specify all preceding information, you can click **Export** in the lower-right corner of the panel to create an export task and export the backup file directly to a local directory.
+
+#### Step 11: View the export task
+
+After the export task is generated, the **Task Center** page automatically appears, where you can view the task information and download exported data and schema files. For more information, see [Export tasks](../../8.client-odc-task-management/3.client-odc-export-tasks.md).
+
+Batch import
+-------------------------
+
+In the **Create Import Task** panel, you can choose to import schemas and data to multiple database objects at the same time.
+
+
+
+Take the import of ZIP files (6000219_import_file) in the ODC as an example. The file contains an employee table and a salary view. Procedure:
+
+### Step 1: Specify **Import Format**
+
+As shown in the preceding figure, ODC supports batch import of **CSV Files**, **SQL Files**, and **ZIP Files**. You can select the desired file format from the **Import Format** drop-down list. For more information about formats, see [Export and import formats](../1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md).
+
+### Step 2: Upload the file to be imported
+
+Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it. The format of the uploaded file must be the same as that of the value you specified for Import Format. Upload files suffixed with .zip if you have selected ZIP Files for Import Format, upload files suffixed with .sql if you have selected SQL Files for Import Format, and upload files suffixed with .csv if you have selected CSV Files for Import Format.
+
+### Step 3: Specify **File Encoding**
+
+ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+### Step 4: Go to the Import Settings panel
+
+Click **Next: Import Settings** to specify file import settings and the sys tenant account.
+
+### Step 5: Specify **Import Content**
+
+
+
+You must specify this parameter when you select **ZIP Files** for **Import Format**. ODC supports **Import Data Only**, **Import Schema Only**, and **Import Schema and Data**. **Import Schema Only** imports the definition statements of the target object. You can select the import content from the **Import Content** drop-down list.
+
+### Step 6: Select a database
+
+Select the database to which the data object is to be imported. The name of the database connection to which the task belongs is also displayed.
+
+### Step 7: Specify **Import Data Settings**
+
+If you select **ZIP Files** for **Import Format** and **Import Data Only** or **Import Schema and Data** for **Import Content**, this option must be specified. You need to specify the following fields:
+
+* **Clear Data Before Import**: If you select this option, the original data in the destination object is cleared during data import.
+
+
+
+* **Batch Commit Quantity**: You can click **Advanced** next to **Export Data Settings** to specify this field. After you specify this field, a `COMMIT` statement is executed when the number of exported data rows reaches the specified quantity.
+
+
+
+* **Skipped Data Type (Optional)**: You can specify the data types to be skipped during data import. The data types that can be skipped are different in MySQL and Oracle modes. You can select multiple data types.
+
+
+
+
+
+
+### Step 8: Specify **Import Schema Settings**
+
+You cannot specify this field if you select Import Data Only for **Import Content**. This field involves operations on schemas that already exist. If you select **Skip**, the system skips the schema definition statement in the file to be imported and directly imports the data. The original data in the object is retained. If you select **Replace**, the system executes the schema definition statement in the file to be imported to re-create an object and replace the original one. Data in the original object is cleared.
+
+### Step 9: Specify **Task Error Handling Method** and the execution method
+
+* ODC supports two error handling methods: **Abort Task** and **Ignore Error and Continue**. You need to select the handling method as required.
+
+
+
+* Select **Execute immediately** or **Timed execution**.
+
+
+
+
+
+
+### Step 10: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+ **Notice**
+ - The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+ 
+
+ - If the account of the sys tenant is not configured, comments and indexes are not imported or exported.
+
+### Step 11: Retain Current Configuration
+
+Check **Retain Current Configuration** to keep the current part of the data file and structure file configuration.
+
+
+### Step 12: Generate an import task
+
+After you specify all preceding information, you can click **Submit** in the lower-right corner of the panel to create an import task.
+
+### Step 13: View the import task
+
+
+
+After the task is generated, the **Task Center** page automatically appears, where you can view the task information. For more information, see [Import tasks](../../8.client-odc-task-management/2.client-odc-import-tasks.md).
+
diff --git a/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/4.client-odc-single-table-export-and-import.md b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/4.client-odc-single-table-export-and-import.md
new file mode 100644
index 00000000..7cdc5ef9
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/1.client-odc-data-export-and-import/4.client-odc-single-table-export-and-import.md
@@ -0,0 +1,205 @@
+Single table export and import
+============================
+
+
+
+Overview
+-----------------------
+
+OceanBase Developer Center (ODC) allows you to import and export data and schemas from a specified table.
+
+After you open a database connection, you can click Objects in the left-side navigation pane to view the objects. Right-click the name of the target object in the object list, or click **Tools** in the top navigation bar and then select **Export** or **Import** from the drop-down list to export or import the data and schema in the current table.
+
+The following table describes the requirements for the size of imported and exported data and the retention period of files in ODC.
+
+
+| Requirement | Description |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| File retention period on the server |
The status of a task, such as Succeeded, Failed, and Canceled, does not affect the lifecycle of the task files.
Tasks are permanently retained. Task-related files are retained for 14 days by default.
|
+
+
+
+Single table export
+-------------------------
+
+
+
+### Procedure
+
+The procedure for exporting a single table is basically the same as the that of [batch export](../1.client-odc-data-export-and-import/3.client-odc-batch-export-and-import.md). The following example shows how to export an employee table in ODC. Procedure:
+
+#### Step 1: Specify the export content
+
+As shown in the preceding figure, ODC supports three export modes: **Export Schema and Data**, **Export Data Only**, and **Export Schema Only**. **Export Schema Only** exports the definition statements of the target object. You can select the export content from the **Export Content** drop-down list.
+
+#### Step 2: Select a database
+
+Select the database where the object to export resides. The name of the database connection to which the task belongs is also displayed.
+
+#### Step 3: Specify the export range
+
+By default, the current table is exported. You can select **Partial Export** or **Full Export**.
+
+* If you select **Partial Export**, you can select the objects you want to export in the **Select Objects** pane in the **Export Objects** section. You can use the search box to search for desired objects.
+* If you select **Full Export**, all objects in the database are exported.
+
+#### Step 4: Go to the Export Settings panel
+
+Click **Next: Export Settings** to specify the file export settings and the sys tenant account.
+
+#### Step 5: Go to the Data File Settings panel
+
+
+
+1. Specify **Data Format**.
+
+ ODC supports exporting data to files in the CSV format and SQL format. If you specify **Export Schema Only** for **Export Content**, you can only export data to files in the SQL format. For more information about formats, see [Export and import formats](../1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md).
+
+
+2. Specify **File Encoding**.
+
+ ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+
+3. Specify **Data File Settings**.
+
+ If you select **Export Schema Only** for **Export Content**, you do not need to configure the export data settings. You need to specify the following fields:
+ * **Use Global Snapshot**: If you select this option, ODC exports the data in the latest global snapshot of the specified table to ensure global data consistency.
+ * **Batch Commit Quantity (SQL Format)**: You can click **Advanced** next to **Export Data Settings** to specify this field. If you select **SQL Format** for **Data Format**, you can specify the number of rows to be committed during the export. When this number is reached, a `COMMIT` command is executed.
+ * Specify information for the CSV format. If you select **CSV Format** for **Data Format** and **Export Schema and Data** for **Export Content**, you can specify following information:
+
+ * **Include the Column Header**: specifies whether to include column headers when data is exported in CSV format. This option is selected by default.
+ * **Convert the Empty String into a Null Value**: This option is selected by default to determine whether to convert empty strings in the table to NULL values when data is exported in CSV format.
+ * **Field Separator**: specifies the separator between fields. The following signs are supported: commas, semicolons, and colons. You can also use a character as the separator.
+ * **Text Identifier**: specifies the identifier for the text content. Single quotation marks (') and double quotation marks (") are supported.
+ * **Line Break Symbol**: specifies the line break symbol. The following characters are supported: \\n, \\r, and \\r\\n.
+
+#### Step 6: Specify schema file settings
+
+Choose whether to select **Add DROP TABLE Statement before CREATE TABLE Statement**. If you select this option, a `DROP` statement is added before the corresponding `CREATE` statement of an object when the schema files of the object are exported.
+
+#### Step 7: Select an execution method
+
+Select **Execute immediately** or **Timed execution**.
+
+#### Step 8: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+ **Notice**
+ - The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+ 
+
+ - If the account of the sys tenant is not configured, comments and indexes are not imported or exported.
+
+#### Step 9: Generate an export task
+
+After you specify all preceding information, you can click **Export** in the lower-right corner of the panel to create an export task.
+
+#### Step 10: View the export task
+
+
+
+After the export task is generated, the **Task Center** page automatically appears, where you can view the task information and download exported data and schema files. For more information, see [Export tasks](../../8.client-odc-task-management/3.client-odc-export-tasks.md).
+
+Single table import
+-------------------------
+
+
+
+### Procedure
+
+Take the import of a ZIP file (6000219_import_file) in ODC as an example. The file contains an employee table. Procedure:
+
+#### Step 1: Specify Import Format
+
+As shown in the preceding figure, ODC supports **CSV Files** and **ZIP Files** for single table import. You can select the desired file format from the **Import Format** drop-down list. For more information about formats, see [Export and import formats](../1.client-odc-data-export-and-import/2.client-odc-export-and-import-formats.md).
+
+#### Step 2: Upload the file to be imported
+
+Click the file pool to go to the file explorer and select the file to be imported. You can also directly drag the file to the file pool to upload it. The format of the uploaded file must be the same as that of the value you specified for **Import Format**. Upload files suffixed with .zip if you have selected **ZIP Files** for **Import Format**, and upload files suffixed with .csv if you have selected **CSV Files** for **Import Format**.
+
+> **Note**
+> You can upload a single table or multiple tables.
+
+#### Step 3: Specify File Encoding
+
+ODC supports the following encoding standards: **ASCII**, **ISO-8859-1**, **GB2312**, **GBK**, **GB18030**, **Unicode (UTF-8)**, **Unicode (UTF-16)**, **Unicode (UTF-32)**, and **BIG5**. You can select the encoding standard from the **File Encoding** drop-down list.
+
+#### Step 4: Go to the Import Settings panel
+
+Click **Next: Import Settings** to specify file import settings and the sys tenant account.
+
+#### Step 5: Specify Import Content
+
+
+
+You must specify this parameter when you select **ZIP Files** for **Import Format**. ODC supports **Import Data Only**, **Import Schema Only**, and **Import Schema and Data**. **Import Schema Only** imports the definition statements of the target object. You can select the import content from the **Import Content** drop-down list.
+
+#### Step 6: Select a database
+
+Select the database to which the data object is to be imported. The name of the database connection to which the task belongs is also displayed.
+
+#### Step 7: Import the target table
+
+By default, the current table is imported. To import multiple tables, select the tables to be imported.
+
+#### Step 8: Specify Import Data Settings
+
+If you select **ZIP Files** for **Import Format** and **Import Data Only** or **Import Schema and Data** for **Import Content**, this option must be specified. You need to specify the following fields:
+
+* **Clear Data Before Import**: If you select this option, the original data in the destination object is cleared during data import.
+
+
+
+* **Batch Commit Quantity**: You can click **Advanced** next to **Import Data Settings** to specify this field. After you specify this field, a `COMMIT` statement is executed when the number of exported data rows reaches the specified quantity.
+
+
+
+* **Skipped Data Type (Optional)**: You can specify the data types to be skipped during data import. The data types that can be skipped are different in MySQL and Oracle modes. You can select multiple data types.
+
+
+
+
+
+
+#### Step 9: Specify Import Schema Settings
+
+You cannot specify this field if you select **Import Data Only** for **Import Content**. This field involves operations on schemas that already exist. If you select **Skip**, the system skips the schema definition statement in the file to be imported and directly imports the data. The original data in the object is retained. If you select **Replace**, the system executes the schema definition statement in the file to be imported to re-create an object and replace the original one. Data in the original object is cleared.
+
+#### Step 10: Specify Task Error Handling Method and the execution method
+
+* ODC supports two error handling methods: **Abort Task** and **Ignore Error and Continue**. You need to select the handling method as required.
+* Select **Execute immediately** or **Timed execution**.
+
+
+
+
+
+
+#### Step 11: Set up the sys tenant account
+
+1. Choose whether to select **Use sys Tenant Account to Accelerate Export Task**. If you select this option, specify **Account** and **Password**.
+
+
+
+2. After you specify the account and password, you can click the **Test Connection** button next to the password box to verify whether the account information is valid. By default, the account for the connection settings is automatically filled in. If the connection fails, we recommend that you change the password for this export.
+
+ **Notice**
+ - The account and password of the sys tenant are the account and password of a user in a cluster tenant. Do not enter `@sys#cluster` in the **Account** field. The following figure shows an example.
+ 
+
+ - If the account of the sys tenant is not configured, comments and indexes are not imported or exported.
+
+#### Step 12: Generate an import task
+
+After you specify all preceding information, you can click **Submit** in the lower-right corner of the panel to create an import task.
+
+#### Step 13: View the import task
+
+
+After the task is generated, the **Task Center** page automatically appears, where you can view the task information. For more information, see [Import tasks](../../8.client-odc-task-management/2.client-odc-import-tasks.md).
diff --git a/en-US/7.client-odc-user-guide/5.client-odc-use-tools/2.client-odc-data-mocking.md b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/2.client-odc-data-mocking.md
new file mode 100644
index 00000000..8f1824a4
--- /dev/null
+++ b/en-US/7.client-odc-user-guide/5.client-odc-use-tools/2.client-odc-data-mocking.md
@@ -0,0 +1,65 @@
+Data mocking
+=================================
+
+OceanBase Developer Center (ODC) provides the data mocking feature. This feature can generate data based on field types in a table, to meet your requirement for a large amount of data during database performance tests or feature verification.
+
+
+
+Perform the following steps to generate data by using the data mocking feature:
+
+1. Go to the **Mock Data** panel.
+
+ Log on to ODC, and click the name of the target connection to go to the corresponding database object management page. Click **Tool** in the navigation bar in the upper part of the page and select **Mock Data** from the drop-down list. The **Mock Data** panel appears.
+
+
+2. Specify the table for generating data.
+
+ In the Mock Data panel, select the table from the drop-down list under **Table** . The drop-down list displays all the tables in the current instance.
+
+
+3. Specify the task name.
+
+ By default, the data mocking task is named in the format of \< **Connection name\>_\_\