diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 33b2cffbacbf4c8e57a8abe0c04afc1d88f2e498..cd8811a50247bb209ffb801c7ef0964070d9ef5b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,6 +8,8 @@ git remote add upstream git@gitee.com:enmotech/mogdb-docs.git 2. 同步代码 ```bash + git clone <个人仓库地址> + git remote add upstream git@gitee.com:enmotech/mogdb-docs.git git fetch upstream git checkout -b upstream/master # 从最新的master分支创建新分支 ``` diff --git a/product/en/docs-mtk/v2.0/faqs.md b/product/en/docs-mtk/v2.0/faqs.md index 98c3322d2215c701729a471f20c2fc83a807f342..4873aa903c76de4f3b966929d2a127f1c45c608b 100644 --- a/product/en/docs-mtk/v2.0/faqs.md +++ b/product/en/docs-mtk/v2.0/faqs.md @@ -24,7 +24,7 @@ The following scenarios exist. - The source database column type is character migration to byte type. The length of the field will be twice as long as the original. - - MySQL database Migration to openGauss/MogDB non-PG compatible mode will become 3x the original. e.g. varchar(10) becomes varchar(30) + - MySQL database Migration to openGauss/MogDB non-PG/B compatible mode will become 3x the original. e.g. varchar(10) becomes varchar(30) - Character encoding conversion is present. Database length migration from GBK to UTF-8 increases by 50% and rounds up. @@ -32,44 +32,44 @@ The following scenarios exist. |---------|--------------|-----------|-----------|---------|---------------|-----------------------| |Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(150)|openGauss|UTF8|A| |Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(300)|openGauss|UTF8|A| -|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG| -|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG| +|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG/B| +|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG/B| |Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|GBK |A| |Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(200)|openGauss|GBK |A| -|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|GBK |PG| -|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|GBK |PG| +|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|GBK |PG/B| +|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|GBK |PG/B| |Oracle |AL32UTF8 |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|A| |Oracle |AL32UTF8 |VARCHAR2(100 CHAR)|VARCHAR(300)|openGauss|UTF8|A| -|Oracle |AL32UTF8 |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG| -|Oracle |AL32UTF8 |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG| +|Oracle |AL32UTF8 |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG/B| +|Oracle |AL32UTF8 |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG/B| |oracle |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |oracle |ZHS16GBK |CHAR(2 ) |CHAR(3)|openGauss|UTF8|A| -|oracle |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|oracle |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|oracle |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|oracle |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| |oracle |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |oracle |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|A| -|oracle |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|oracle |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|oracle |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|oracle |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| |MySQL |GBK |VARCHAR(100 ) |VARCHAR(300)|openGauss|UTF8|A| |MySQL |GBK |VARCHAR(100 ) |VARCHAR(300)|openGauss|GBK|A| |MySQL |UTF8 |VARCHAR(100 ) |VARCHAR(300)|openGauss|UTF8|A| -|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| -|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG| -|MySQL |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| +|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| +|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG/B| +|MySQL |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| |DB2 |GBK |VARCHAR(100 ) |VARCHAR(150)|openGauss|UTF8|A| |DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|A| |DB2 |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|A| -|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| -|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG| -|DB2 |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| +|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| +|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG/B| +|DB2 |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| |DB2 |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |DB2 |ZHS16GBK |CHAR(2 ) |CHAR(3)|openGauss|UTF8|A| -|DB2 |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|DB2 |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|DB2 |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|DB2 |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| |DB2 |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |DB2 |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|A| -|DB2 |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|DB2 |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|DB2 |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|DB2 |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| ## Empty String and NULL conversions ? diff --git a/product/en/docs-mtk/v2.0/mtk-env.md b/product/en/docs-mtk/v2.0/mtk-env.md index 03f3c786966a3ffb354546171c0d4c6910e19d0b..b6865516e63c0d154fc481a5db48c2734916ed9c 100644 --- a/product/en/docs-mtk/v2.0/mtk-env.md +++ b/product/en/docs-mtk/v2.0/mtk-env.md @@ -87,3 +87,7 @@ No client needs to be installed. ## openGauss No client needs to be installed. + +## Informix + +See [DB2](#db2) diff --git a/product/en/docs-mtk/v2.0/overview.md b/product/en/docs-mtk/v2.0/overview.md index 80919b029d75aae1de0edba70de596080389fd98..91687bbd148022aa7bc1aa2685caf93d672d5147 100644 --- a/product/en/docs-mtk/v2.0/overview.md +++ b/product/en/docs-mtk/v2.0/overview.md @@ -7,11 +7,11 @@ date: 2021-09-03 # Overview of MTK -MTK (Database Migration Toolkit) is a tool used for quickly importing the data structure and full data of Oracle/DB2/MySQL/openGauss into MogDB. MTK of the latest version also supports compatibility with MogDB by rewriting and importing stored procedures, functions, triggers and other program segments in Oracle databases. +MTK (Database Migration Toolkit) is a tool used for quickly importing the data structure and full data of Oracle/DB2/MySQL/openGauss/SqlServer/Informix into MogDB. MTK of the latest version also supports compatibility with MogDB by rewriting and importing stored procedures, functions, triggers and other program segments in Oracle databases. ## Support for Multiple Database Types -- Data migration between Oracle, DB2, openGauss, SQL Server, and MySQL is supported. These databases act as the source or target database of each other. +- Data migration between Oracle, DB2, openGauss, SQL Server, MySQL and Informix is supported. These databases act as the source or target database of each other. - Database content can be exported as an executable SQL script. ## Migration Performance Adjustment @@ -25,11 +25,11 @@ MTK (Database Migration Toolkit) is a tool used for quickly importing the data s - The migration range can be specified, such as table-level or schema-level migration. You can specify whether to migrate all objects or some objects under a schema. - Schema remapping is supported during the migration. In other word, objects under the source schema can be migrated to a different schema in the target database. -## Procedure Migration from Oracle/MySQL to openGauss +## Procedure Migration from Oracle/MySQL/DB2 to openGauss -Storage procedures, functions, triggers, and packages can be migrated from Oracle/MySQL to openGauss. +Storage procedures, functions, triggers, and packages can be migrated from Oracle/MySQL/DB2 to openGauss. -According to the openGauss syntax rules, Oracle/MySQL procedures are automatically rewritten and then created in the target openGauss database. +According to the openGauss syntax rules, Oracle/MySQL/DB2 procedures are automatically rewritten and then created in the target openGauss database. ## Migration Scenario @@ -51,6 +51,7 @@ According to the openGauss syntax rules, Oracle/MySQL procedures are automatical | openGauss | openGauss | | openGauss | PostgreSQL | | PostgreSQL | openGauss | +| Informix | openGauss |
diff --git a/product/en/docs-mtk/v2.0/toc.md b/product/en/docs-mtk/v2.0/toc.md index 368772dfeebd006552556a6717b507c537371fcb..00f73a6f79bf09d62ba73ff9e034315e49093dfc 100644 --- a/product/en/docs-mtk/v2.0/toc.md +++ b/product/en/docs-mtk/v2.0/toc.md @@ -61,6 +61,7 @@ + [DB2 to openGauss/MogDB](/mtk-db2-to-openGauss.md) + [MySQL to openGauss/MogDB](/mtk-mysql-to-openGauss.md) + [Oracle to openGauss/MogDB](/mtk-oracle-to-openGauss.md) ++ [Informix到openGauss/MogDB](/mtk-informix-to-openGauss.md) + [DB2 to MySQL](/mtk-db2-to-mysql.md) + [常见问题](/faqs.md) + [Release Notes](/release-notes.md) diff --git a/product/zh/docs-mtk/v2.0/faqs.md b/product/zh/docs-mtk/v2.0/faqs.md index 8e229a77652e01d1ee77937deca29251d3cc975e..4ba42122423850e75a5c5a551b8e7c7fd7d677e6 100644 --- a/product/zh/docs-mtk/v2.0/faqs.md +++ b/product/zh/docs-mtk/v2.0/faqs.md @@ -22,7 +22,7 @@ Char类型数据需要注意. 如在Oracle里Char(1)迁移到openGauss/MogDB就 - 源库列类型是字符迁移到字节型. 字段长度会变成原来的2倍. - - MySQL 数据库 迁移到 openGauss/MogDB 非PG兼容模式 会变成原来的3倍. 如varchar(10)变为varchar(30) + - MySQL 数据库 迁移到 openGauss/MogDB 非PG/B兼容模式 会变成原来的3倍. 如varchar(10)变为varchar(30) - 存在字符编码转换. 从GBK的数据库迁移到UTF-8的数据库长度会增加50%,向上取整. @@ -30,44 +30,44 @@ Char类型数据需要注意. 如在Oracle里Char(1)迁移到openGauss/MogDB就 |---------|--------------|-----------|-----------|---------|---------------|-----------------------| |Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(150)|openGauss|UTF8|A| |Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(300)|openGauss|UTF8|A| -|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG| -|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG| +|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG/B| +|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG/B| |Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|GBK |A| |Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(200)|openGauss|GBK |A| -|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|GBK |PG| -|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|GBK |PG| +|Oracle |ZHS16GBK |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|GBK |PG/B| +|Oracle |ZHS16GBK |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|GBK |PG/B| |Oracle |AL32UTF8 |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|A| |Oracle |AL32UTF8 |VARCHAR2(100 CHAR)|VARCHAR(300)|openGauss|UTF8|A| -|Oracle |AL32UTF8 |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG| -|Oracle |AL32UTF8 |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG| +|Oracle |AL32UTF8 |VARCHAR2(100 BYTE)|VARCHAR(100)|openGauss|UTF8|PG/B| +|Oracle |AL32UTF8 |VARCHAR2(100 CHAR)|VARCHAR(100)|openGauss|UTF8|PG/B| |oracle |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |oracle |ZHS16GBK |CHAR(2 ) |CHAR(3)|openGauss|UTF8|A| -|oracle |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|oracle |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|oracle |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|oracle |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| |oracle |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |oracle |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|A| -|oracle |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|oracle |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|oracle |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|oracle |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| |MySQL |GBK |VARCHAR(100 ) |VARCHAR(300)|openGauss|UTF8|A| |MySQL |GBK |VARCHAR(100 ) |VARCHAR(300)|openGauss|GBK|A| |MySQL |UTF8 |VARCHAR(100 ) |VARCHAR(300)|openGauss|UTF8|A| -|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| -|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG| -|MySQL |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| +|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| +|MySQL |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG/B| +|MySQL |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| |DB2 |GBK |VARCHAR(100 ) |VARCHAR(150)|openGauss|UTF8|A| |DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|A| |DB2 |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|A| -|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| -|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG| -|DB2 |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG| +|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| +|DB2 |GBK |VARCHAR(100 ) |VARCHAR(100)|openGauss|GBK|PG/B| +|DB2 |UTF8 |VARCHAR(100 ) |VARCHAR(100)|openGauss|UTF8|PG/B| |DB2 |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |DB2 |ZHS16GBK |CHAR(2 ) |CHAR(3)|openGauss|UTF8|A| -|DB2 |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|DB2 |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|DB2 |ZHS16GBK |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|DB2 |ZHS16GBK |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| |DB2 |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|A| |DB2 |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|A| -|DB2 |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG| -|DB2 |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG| +|DB2 |AL32UTF8 |CHAR(1 ) |CHAR(1)|openGauss|UTF8|PG/B| +|DB2 |AL32UTF8 |CHAR(2 ) |CHAR(2)|openGauss|UTF8|PG/B| ## 存在空字符串和NULL转换？ diff --git a/product/zh/docs-mtk/v2.0/mtk-env.md b/product/zh/docs-mtk/v2.0/mtk-env.md index 2d773273a85a27efc802e1e4b1d694751b93261e..2f82d6fc9c03441c144a82b64cb37b16e23272b4 100644 --- a/product/zh/docs-mtk/v2.0/mtk-env.md +++ b/product/zh/docs-mtk/v2.0/mtk-env.md @@ -86,3 +86,7 @@ mtk: error while loading shared libraries: libdb2.so.1: cannot open shared objec ## openGauss 无需安装额外客户端 + +## Informix + +参考[DB2](#db2) diff --git a/product/zh/docs-mtk/v2.0/mtk-informix-to-openGauss.md b/product/zh/docs-mtk/v2.0/mtk-informix-to-openGauss.md index e6144f61273de7fe44e01db1b1a832cc8a26efe3..3f471e706fb7ffaa143b8208a2fc40991ae6d8e0 100644 --- a/product/zh/docs-mtk/v2.0/mtk-informix-to-openGauss.md +++ b/product/zh/docs-mtk/v2.0/mtk-informix-to-openGauss.md @@ -7,19 +7,21 @@ date: 2022-05-28 # 使用MTK迁移Informix到openGauss/MogDB +> 下载带DB2 字样的程序包进行迁移 + ## 支持版本 - 12.10 ## 驱动 -### Informix ODBC +### Informix ODBC(CSDK) -不支持. 未研发成功 +不支持. 未适配成功 ### DB2 ODBC -支持. +支持. 参考[DB2](mtk-env#db2) > Port allow remote connections from DRDA clients @@ -29,21 +31,11 @@ date: 2022-05-28 空字符串和NULL问题, Informix null 不等于 '' -openGauss A 模式下和 Informix 不一样,需要处理数据 当列的属性为not null时转为`" "`,允许为null时转为null - -openGauss PG 模式下和 Informix 一样, null != '' 无需处理 - -openGauss B 模式下和 Informix 一样, null != '' 无需处理 - -DBCOMPATIBILITY [ = ] compatibility_type +- openGauss A 模式下和 Informix 不一样,需要处理数据 当列的属性为not null时转为`" "`,允许为null时转为null -指定兼容的数据库的类型。取值范围: A、B、C、PG。分别表示兼容Oracle、MySQL、Teradata和PostgreSQL。但是C目前已经放弃支持。因此常用的取值是A、B、PG。 +- openGauss PG 模式下和 Informix 一样, null != '' 无需处理 - > 说明: - > - > - A兼容性下，数据库将空字符串作为NULL处理，数据类型DATE会被替换为TIMESTAMP(0) WITHOUT TIME ZONE。 - > - 将字符串转换成整数类型时，如果输入不合法，B兼容性会将输入转换为0，而其它兼容性则会报错。 - > - PG兼容性下，CHAR和VARCHAR以字符为计数单位，其它兼容性以字节为计数单位。例如，对于UTF-8字符集，CHAR(3)在PG兼容性下能存放3个中文字符，而在其它兼容性下只能存放1个中文字符。 +- openGauss B 模式下和 Informix 一样, null != '' 无需处理 ### 序列 @@ -248,8 +240,6 @@ openGauss统一处理为bigint类型加默认序列 - 不支持函数索引 - 没有找到列信息. 只支持用户自己定义的函数 - ### 约束 - 检查约束存在语法转换问题. @@ -266,10 +256,18 @@ openGauss统一处理为bigint类型加默认序列 ### 函数 +- 只查询不支持语法转换 + ### 存储过程 +- 只查询不支持语法转换 + ### 触发器 +- 只查询不支持语法转换 + +### 同义词 + ## 部分SQL语句 ### 系统视图 @@ -287,6 +285,11 @@ openGauss统一处理为bigint类型加默认序列 - sysreferences 外健约束 - syschecks 检查约束 - sysviews 视图 +- SYSSYNTABLE 同义词关系表 +- systriggers 触发器 +- systrigbody 触发器定义表 +- sysprocedures 存储过程/函数 +- sysprocbody 存储过程/函数定义 ### 序列信息 @@ -490,3 +493,63 @@ join informix.systables t on v.tabid = t.tabid order by v.tabid,v.seqno ``` + +## 函数信息 + +```sql +select + sp.procid, + sp.owner, + sp.procname, + sb.datakey, + sb.seqno, + sb.data +from + informix.sysprocedures sp + left join sysprocbody sb on sp.procid = sb.procid +where sb.datakey IN ('D','T') + and sp.isproc='f' +order by sb.procid, sb.seqno +``` + +## 存储过程信息 + +```sql +select + sp.procid, + sp.owner, + sp.procname, + sb.datakey, + sb.seqno, + sb.data +from + informix.sysprocedures sp + left join sysprocbody sb on sp.procid = sb.procid +where sb.datakey IN ('D','T') + and sp.isproc='t' +order by sb.procid, sb.seqno +``` + +## 触发器信息 + +```sql +select tr.owner,tr.trigname,tr.trigid,tr.tabid,tr.event,tr.old,tr.new, + ta.owner,ta.tabname, + tb.seqno, tb.data +from + systables ta + join systriggers tr on tr.tabid = ta.tabid + join systrigbody tb on tb.trigid = tr.trigid +where ta.tabtype = 'T' + and tb.datakey IN ('A', 'D') +order by tr.trigname, datakey desc, seqno +``` + +## 同义词 + +```sql +select t.owner,t.tabname,t1.owner,t1.tabname,t.tabtype from informix.systables t +left join informix.SYSSYNTABLE s on t.tabid=s.tabid +left join informix.systables t1 on s.btabid=t1.tabid +where t.tabtype in ('S','P') +``` diff --git a/product/zh/docs-mtk/v2.0/overview.md b/product/zh/docs-mtk/v2.0/overview.md index 469e6e8687f2f1cf0b5d24a208626851e81b69e7..7ffe9b5ce799745316398148e5890a0fe483b358 100644 --- a/product/zh/docs-mtk/v2.0/overview.md +++ b/product/zh/docs-mtk/v2.0/overview.md @@ -7,11 +7,12 @@ date: 2021-03-04 # MTK 简介 -MTK全称为 Database Migration Toolkit，是一个可以将Oracle/DB2/MySQL/openGauss数据库的数据结构，全量数据高速导入到MogDB的工具。最新版本同时支持对于Oracle数据库中存储过程，函数，触发器等程序段的MogDB兼容性改写和导入。 +MTK全称为 Database Migration Toolkit，是一个可以将Oracle/DB2/MySQL/openGauss/SqlServer/Informix数据库的数据结构，全量数据高速导入到MogDB的工具。 +最新版本同时支持对于Oracle/MySQL/DB2数据库中存储过程，函数，触发器等程序段的MogDB兼容性改写和导入。 ## 多数据库类型支持 -- 支持 Oracle,DB2, openGauss,sqlServer, MySQL 等数据库之间的互相迁移 (互为源和目标)。 +- 支持 Oracle,DB2,openGauss,SqlServer,MySQL,Informix 等数据库之间的互相迁移 (互为源和目标)。 - 支持将数据库内容导出成可执行的 SQL 脚本 （源数据库内容迁移到文本）。 ## 迁移性能调整 @@ -25,11 +26,11 @@ MTK全称为 Database Migration Toolkit，是一个可以将Oracle/DB2/MySQL/ope - 支持表级和 Schema 级的迁移范围限定，允许指定schema下全部对象或者某些对象进行迁移 。 - 支持迁移过程中的 Schema 重映射，也就是支持将对象从源Schema迁移到目标端的不同名Schema下 。 -## 程序迁移（支持Oracle/MySQL为源,openGauss为目标） +## 程序迁移（支持Oracle/MySQL/DB2为源,openGauss为目标） -支持Oracle/MySQL->openGauss的存储过程，函数，触发器，包迁移。 +- 支持Oracle/MySQL/DB2->openGauss的存储过程，函数，触发器，包迁移。 -自动根据openGauss的语法规则，对Oracle/MySQL的程序进行改写，之后再在目标端openGauss数据库中创建。 +自动根据openGauss的语法规则，对Oracle/MySQL/DB2的程序进行改写，之后再在目标端openGauss数据库中创建。 ## 迁移场景 @@ -51,6 +52,7 @@ MTK全称为 Database Migration Toolkit，是一个可以将Oracle/DB2/MySQL/ope | openGauss | openGauss | | openGauss | PostgreSQL | | PostgreSQL | openGauss | +| Informix | openGauss |
diff --git a/product/zh/docs-mtk/v2.0/toc.md b/product/zh/docs-mtk/v2.0/toc.md index 2c3520959c4c99e0216af2840d8fa2a676be82ca..5990be1b541fd60d2fcff99e63e0b1e91b4710cb 100644 --- a/product/zh/docs-mtk/v2.0/toc.md +++ b/product/zh/docs-mtk/v2.0/toc.md @@ -61,6 +61,7 @@ + [DB2到openGauss/MogDB](/mtk-db2-to-openGauss.md) + [MySQL到openGauss/MogDB](/mtk-mysql-to-openGauss.md) + [Oracle到openGauss/MogDB](/mtk-oracle-to-openGauss.md) ++ [Informix到openGauss/MogDB](/mtk-informix-to-openGauss.md) + [DB2到MySQL](/mtk-db2-to-mysql.md) + [常见问题](/faqs.md) + [发布记录](/release-notes.md)