updates

Author: Cary Huang

docs/en/getting-started/quick_start.md

@@ -388,7 +388,7 @@ postgres=# SELECT * from inventory.orders;
 
 **Sqlserver:**
 ```bash
-docker exec -i mysql mysql -D inventory -umysqluser -pmysqlpwd -e "INSERT INTO orders(order_date, purchaser, quantity, product_id) VALUES ('2025-12-12', 1002, 10000, 102)"
+docker exec -i sqlserver /opt/mssql-tools18/bin/sqlcmd -U sa -P 'Password!' -d testDB -C -Q "INSERT INTO orders(order_date, purchaser, quantity, product_id) VALUES ('2025-12-12', 1002, 10000, 102)"
 
 ```
 

docs/en/user-guide/configure_olr.md

@@ -2,9 +2,16 @@
 
 ## **Overview**
 
-In addition to LogMiner-based replication, **SynchDB** supports **Openlog Replicator (OLR)** as a data source for Oracle connectors. This integration enables low-latency, redo log–based change data capture from Oracle databases via a standalone replication server.
+In addition to LogMiner-based Oracle replication, **SynchDB** supports **Openlog Replicator (OLR)** as a data source for Debezium-based Oracle connectors (type = `oracle`). This integration enables low-latency, redo log–based change data capture from Oracle databases via a standalone replication server. 
 
-This guide details the configuration steps necessary to associate an Oracle connector with an OLR endpoint using `synchdb_add_olr_conninfo()` and `synchdb_del_olr_conninfo()`.
+Furthermore, Synchdb also supports `native` Openlog Replicator connector, which does not rely on Debezium. This is a OLR client written purely in C that eliminates the JNI overheads.
+
+This guide details the configuration steps necessary to:
+
+* associate an Oracle connector with an OLR endpoint 
+* or create a native Openlog Replicator Connector
+
+Both can be done using `synchdb_add_olr_conninfo()` and `synchdb_del_olr_conninfo()`.
 
 ## **Requirements**
 
@@ -15,10 +22,29 @@ This guide details the configuration steps necessary to associate an Oracle conn
 
 Refer to this [external guide](https://highgo.atlassian.net/wiki/external/OTUzY2Q2OWFkNzUzNGVkM2EyZGIyMDE1YzVhMDdkNWE) for details on deploying Openlog Replicator via Docker.
 
+## **`synchdb_add_conninfo()`**
+
+To create a **Debezium-based** or **Native** Openlog Replicator, users first have to create the connector with `synchdb_add_conninfo()` but with different `connector type`. For example:
+
+```sql
+SELECT synchdb_add_conninfo('olrconn',
+                            'ora19c',
+                            1521,
+                            'DBZUSER',
+                            'dbz',
+                            'FREE',
+                            'postgres',
+                            'null',
+                            'null',
+                            'olr');    -- 'olr' for native openlog replicator or 'oracle' for debezium based openlog replicator connector
+
+```
+
+More on creating a connector can be found [here](https://docs.synchdb.com/user-guide/create_a_connector/)
 
 ## **`synchdb_add_olr_conninfo()`**
 
-Registers an Openlog Replicator endpoint for an existing Oracle connector.
+With a connector created, the user then registers an Openlog Replicator endpoint for an existing Oracle connector.
 
 **Signature:**
 
@@ -64,4 +90,6 @@ SELECT synchdb_del_olr_conninfo('oracleconn');
 
 * When both LogMiner and OLR configurations exist, SynchDB defaults to using Openlog Replicator for change capture.
 * Restarting the connector is required after modifying its OLR configuration.
-* The Oracle instance and OLR must remain synchronized in SCN progression and resetlogs identity for consistency.
+* The Oracle instance and OLR must remain synchronized in SCN progression and resetlogs identity for consistency.
+* If OLR connection info exists, and connector type is `oracle` then it will use Debezium based Openlog Replicator client to stream changes.
+* If OLR connection info exists, and connector type is `olr` then it will use native Openlog Replicator client to stream changes.

docs/zh/getting-started/quick_start.md

@@ -391,7 +391,7 @@ postgres=# SELECT * from inventory.orders;
 
 **Sqlserver:**
 ```bash
-docker exec -i mysql mysql -D inventory -umysqluser -pmysqlpwd -e "INSERT INTO orders(order_date, purchaser, quantity, product_id) VALUES ('2025-12-12', 1002, 10000, 102)"
+docker exec -i sqlserver /opt/mssql-tools18/bin/sqlcmd -U sa -P 'Password!' -d testDB -C -Q "INSERT INTO orders(order_date, purchaser, quantity, product_id) VALUES ('2025-12-12', 1002, 10000, 102)"
 
 ```
 

docs/zh/user-guide/configure_olr.md

@@ -2,9 +2,16 @@
 
 ## **概述**
 
-除了基于 LogMiner 的复制功能外，**SynchDB** 还支持将 **Openlog Replicator (OLR)** 作为 Oracle 连接器的数据源。此集成功能支持通过独立的复制服务器从 Oracle 数据库捕获低延迟、基于重做日志的变更数据。
+除了基于 LogMiner 的 Oracle 复制功能外，**SynchDB** 还支持将 **Openlog Replicator (OLR)** 作为基于 Debezium 的 Oracle 连接器（类型为 `oracle`）的数据源。此集成支持通过独立的复制服务器从 Oracle 数据库捕获基于重做日志的低延迟变更数据。
 
-本指南详细介绍了使用 `synchdb_add_olr_conninfo()` 和 `synchdb_del_olr_conninfo()` 将 Oracle 连接器与 OLR 端点关联的配置步骤。
+此外，Synchdb 还支持原生 Openlog Replicator 连接器，该连接器不依赖于 Debezium。这是一个纯 C 语言编写的 OLR 客户端，可消除 JNI 开销。
+
+本指南详细介绍了以下配置步骤：
+
+* 将 Oracle 连接器与 OLR 端点关联
+* 或创建原生 Openlog Replicator 连接器
+
+这两个操作都可以使用 `synchdb_add_olr_conninfo()` 和 `synchdb_del_olr_conninfo()` 完成。
 
 ## **要求**
 
@@ -15,9 +22,29 @@
 
 有关通过 Docker 部署 Openlog Replicator 的详细信息，请参阅此[外部指南](https://highgo.atlassian.net/wiki/external/OTUzY2Q2OWFkNzUzNGVkM2EyZGIyMDE1YzVhMDdkNWE)。
 
+## **`synchdb_add_conninfo()`**
+
+要创建**基于 Debezium 的**或**原生** Openlog Replicator，用户首先必须使用 `synchdb_add_conninfo()` 创建连接器，但要选择不同的“连接器类型”。例如：
+
+```sql
+SELECT synchdb_add_conninfo('olrconn',
+							'ora19c',
+							1521,
+							'DBZUSER',
+							'dbz',
+							'FREE',
+							'postgres',
+							'null',
+							'null',
+							'olr'); -- 原生 Openlog Replicator 连接器为“olr”，基于 Debezium 的 Openlog Replicator 连接器为“oracle”。
+
+```
+
+更多关于创建连接器的信息，请访问[此处](https://docs.synchdb.com/user-guide/create_a_connector/)
+
 ## **`synchdb_add_olr_conninfo()`**
 
-为现有的 Oracle 连接器注册 Openlog Replicator 端点。
+创建连接器后，用户可以为现有的 Oracle 连接器注册一个 Openlog Replicator 端点。 
 
 **签名：**
 
@@ -63,4 +90,7 @@ SELECT synchdb_del_olr_conninfo('oracleconn');
 
 * 当 LogMiner 和 OLR 配置同时存在时，SynchDB 默认使用 Openlog Replicator 进行更改捕获。
 * 修改连接器的 OLR 配置后，需要重新启动连接器。
-* Oracle 实例和 OLR 必须在 SCN 进程和 resetlogs 标识方面保持同步，以保持一致性。
+* Oracle 实例和 OLR 必须在 SCN 进程和 resetlogs 标识方面保持同步，以保持一致性。
+* 如果 OLR 连接信息存在，且连接器类型为“oracle”，则它将使用基于 Debezium 的 Openlog Replicator 客户端来传输更改。
+* 如果 OLR 连接信息存在，且连接器类型为“olr”，则它将使用原生 Openlog Replicator 客户端来传输更改。
+* 有关 Openlog Replicator 的更多信息，请访问[此处](https://github.com/bersler/OpenLogReplicator)

mkdocs.yml

@@ -126,7 +126,7 @@ plugins:
             Oracle CDC to PostgreSQL: Oracle CDC 到 PostgreSQL
             Table Snapshot and Re-snapshot: 表快照和重新快照
             JMX Monitor Settings: JMX 监视器设置
-            JVM Memory Usage: JVM内存使用情况
+            JVM Memory Usage: JVM 内存使用情况
             Attribute View: 属性视图
             JMX Exporter Settings: JMX exporter 设置
             Configure Openlog Replicator for Oracle Connector: 为 Oracle Connector 配置 Openlog Replicator