From 27019c29917ea7849bfdc573fcf97f44acfb323f Mon Sep 17 00:00:00 2001 From: "Lu, Huayi" Date: Thu, 16 May 2024 07:35:25 +0000 Subject: [PATCH] DWS TOOL 830.201 version Reviewed-by: Hasko, Vladimir Reviewed-by: Pruthi, Vineet Co-authored-by: Lu, Huayi Co-committed-by: Lu, Huayi --- docs/dws/tool/ALL_META.TXT.json | 5943 +++++++++++++++-- docs/dws/tool/CLASS.TXT.json | 2512 +++++-- docs/dws/tool/DWS_DS_145.html | 4 +- docs/dws/tool/DWS_DS_154.html | 2 +- docs/dws/tool/DWS_DS_16.html | 2 +- docs/dws/tool/dws_07_0002.html | 4 +- docs/dws/tool/dws_07_0101.html | 14 +- docs/dws/tool/dws_07_0128.html | 2 + docs/dws/tool/dws_07_0173.html | 12 +- docs/dws/tool/dws_07_0666.html | 155 - docs/dws/tool/dws_07_0675.html | 46 - docs/dws/tool/dws_07_0676.html | 73 - docs/dws/tool/dws_07_0682.html | 10 +- docs/dws/tool/dws_07_0684.html | 25 - docs/dws/tool/dws_07_0759.html | 12 +- docs/dws/tool/dws_07_6814.html | 103 +- docs/dws/tool/dws_07_6815.html | 18 +- docs/dws/tool/dws_07_6816.html | 10 +- docs/dws/tool/dws_07_6817.html | 93 +- docs/dws/tool/dws_07_6818.html | 12 +- docs/dws/tool/dws_07_6819.html | 126 +- docs/dws/tool/dws_07_6821.html | 236 +- docs/dws/tool/dws_07_6822.html | 674 +- docs/dws/tool/dws_07_6823.html | 1999 ++++-- docs/dws/tool/dws_07_6824.html | 369 +- docs/dws/tool/dws_07_6825.html | 34 +- docs/dws/tool/dws_07_6826.html | 144 +- docs/dws/tool/dws_07_6827.html | 341 +- docs/dws/tool/dws_07_6831.html | 757 --- docs/dws/tool/dws_07_6832.html | 644 -- docs/dws/tool/dws_07_6833.html | 367 - docs/dws/tool/dws_07_6834.html | 113 - docs/dws/tool/dws_07_6835.html | 73 - docs/dws/tool/dws_07_6836.html | 84 - docs/dws/tool/dws_07_6837.html | 105 - docs/dws/tool/dws_07_6838.html | 115 - docs/dws/tool/dws_07_6841.html | 376 -- docs/dws/tool/dws_07_6842.html | 122 - docs/dws/tool/dws_07_6843.html | 50 - docs/dws/tool/dws_07_6844.html | 27 - docs/dws/tool/dws_07_6845.html | 57 - docs/dws/tool/dws_07_6846.html | 158 - docs/dws/tool/dws_07_8111.html | 15 - docs/dws/tool/dws_07_8120.html | 595 -- docs/dws/tool/dws_07_8121.html | 303 - docs/dws/tool/dws_07_8310.html | 82 - docs/dws/tool/dws_07_8311.html | 31 - docs/dws/tool/dws_07_8312.html | 32 - docs/dws/tool/dws_07_8313.html | 287 - docs/dws/tool/dws_07_8314.html | 276 - docs/dws/tool/dws_16_0001.html | 22 + docs/dws/tool/dws_16_0002.html | 14 + docs/dws/tool/dws_16_0003.html | 109 + docs/dws/tool/dws_16_0005.html | 12 + docs/dws/tool/dws_16_0006.html | 18 + docs/dws/tool/dws_16_0008.html | 260 + docs/dws/tool/dws_16_0009.html | 26 + docs/dws/tool/dws_16_0010.html | 19 + docs/dws/tool/dws_16_0012.html | 26 + docs/dws/tool/dws_16_0013.html | 347 + docs/dws/tool/dws_16_0014.html | 338 + docs/dws/tool/dws_16_0015.html | 222 + docs/dws/tool/dws_16_0016.html | 199 + docs/dws/tool/dws_16_0017.html | 24 + docs/dws/tool/dws_16_0018.html | 266 + docs/dws/tool/dws_16_0019.html | 21 + docs/dws/tool/dws_16_0020.html | 109 + docs/dws/tool/dws_16_0021.html | 24 + docs/dws/tool/dws_16_0022.html | 12 + docs/dws/tool/dws_16_0023.html | 20 + docs/dws/tool/dws_16_0024.html | 29 + docs/dws/tool/dws_16_0025.html | 206 + docs/dws/tool/dws_16_0026.html | 51 + docs/dws/tool/dws_16_0027.html | 96 + docs/dws/tool/dws_16_0028.html | 57 + docs/dws/tool/dws_16_0029.html | 54 + docs/dws/tool/dws_16_0030.html | 24 + docs/dws/tool/dws_16_0031.html | 137 + docs/dws/tool/dws_16_0032.html | 20 + docs/dws/tool/dws_16_0033.html | 75 + docs/dws/tool/dws_16_0034.html | 42 + docs/dws/tool/dws_16_0035.html | 22 + docs/dws/tool/dws_16_0036.html | 33 + docs/dws/tool/dws_16_0038.html | 429 ++ docs/dws/tool/dws_16_0039.html | 82 + docs/dws/tool/dws_16_0040.html | 172 + docs/dws/tool/dws_16_0041.html | 29 + docs/dws/tool/dws_16_0043.html | 343 + docs/dws/tool/dws_16_0044.html | 94 + docs/dws/tool/dws_16_0045.html | 105 + docs/dws/tool/dws_16_0046.html | 317 + docs/dws/tool/dws_16_0047.html | 186 + docs/dws/tool/dws_16_0048.html | 25 + docs/dws/tool/dws_16_0049.html | 24 + docs/dws/tool/dws_16_0051.html | 242 + docs/dws/tool/dws_16_0052.html | 103 + docs/dws/tool/dws_16_0053.html | 220 + docs/dws/tool/dws_16_0054.html | 138 + docs/dws/tool/dws_16_0055.html | 305 + .../{dws_mt_0091.html => dws_16_0056.html} | 48 +- docs/dws/tool/dws_16_0059.html | 34 + docs/dws/tool/dws_16_0061.html | 38 + docs/dws/tool/dws_16_0063.html | 96 + docs/dws/tool/dws_16_0064.html | 155 + docs/dws/tool/dws_16_0065.html | 92 + docs/dws/tool/dws_16_0066.html | 41 + docs/dws/tool/dws_16_0067.html | 34 + docs/dws/tool/dws_16_0068.html | 198 + docs/dws/tool/dws_16_0069.html | 159 + docs/dws/tool/dws_16_0070.html | 83 + docs/dws/tool/dws_16_0071.html | 45 + docs/dws/tool/dws_16_0072.html | 423 ++ docs/dws/tool/dws_16_0073.html | 28 + docs/dws/tool/dws_16_0074.html | 293 + .../{dws_mt_0064.html => dws_16_0075.html} | 40 +- .../{dws_mt_0065.html => dws_16_0076.html} | 99 +- docs/dws/tool/dws_16_0077.html | 134 + docs/dws/tool/dws_16_0078.html | 38 + .../{dws_mt_0068.html => dws_16_0079.html} | 82 +- .../{dws_mt_0069.html => dws_16_0080.html} | 16 +- docs/dws/tool/dws_16_0081.html | 102 + docs/dws/tool/dws_16_0082.html | 15 + docs/dws/tool/dws_16_0083.html | 40 + docs/dws/tool/dws_16_0084.html | 30 + docs/dws/tool/dws_16_0086.html | 22 + docs/dws/tool/dws_16_0087.html | 24 + docs/dws/tool/dws_16_0088.html | 60 + docs/dws/tool/dws_16_0089.html | 190 + docs/dws/tool/dws_16_0090.html | 188 + docs/dws/tool/dws_16_0091.html | 79 + docs/dws/tool/dws_16_0092.html | 306 + docs/dws/tool/dws_16_0093.html | 81 + docs/dws/tool/dws_16_0094.html | 115 + docs/dws/tool/dws_16_0095.html | 113 + docs/dws/tool/dws_16_0096.html | 117 + docs/dws/tool/dws_16_0097.html | 150 + docs/dws/tool/dws_16_0098.html | 30 + .../{dws_mt_0103.html => dws_16_0099.html} | 317 +- docs/dws/tool/dws_16_0100.html | 190 + docs/dws/tool/dws_16_0101.html | 145 + docs/dws/tool/dws_16_0102.html | 83 + docs/dws/tool/dws_16_0103.html | 25 + docs/dws/tool/dws_16_0105.html | 255 + docs/dws/tool/dws_16_0106.html | 31 + docs/dws/tool/dws_16_0108.html | 163 + docs/dws/tool/dws_16_0109.html | 145 + docs/dws/tool/dws_16_0110.html | 157 + docs/dws/tool/dws_16_0111.html | 116 + docs/dws/tool/dws_16_0112.html | 75 + docs/dws/tool/dws_16_0113.html | 67 + docs/dws/tool/dws_16_0114.html | 29 + docs/dws/tool/dws_16_0115.html | 91 + docs/dws/tool/dws_16_0116.html | 37 + docs/dws/tool/dws_16_0117.html | 210 + docs/dws/tool/dws_16_0118.html | 22 + docs/dws/tool/dws_16_0119.html | 104 + docs/dws/tool/dws_16_0120.html | 38 + docs/dws/tool/dws_16_0121.html | 21 + docs/dws/tool/dws_16_0122.html | 98 + docs/dws/tool/dws_16_0123.html | 29 + docs/dws/tool/dws_16_0124.html | 26 + docs/dws/tool/dws_16_0125.html | 29 + docs/dws/tool/dws_16_0126.html | 35 + docs/dws/tool/dws_16_0127.html | 24 + docs/dws/tool/dws_16_0128.html | 31 + docs/dws/tool/dws_16_0129.html | 33 + docs/dws/tool/dws_16_0130.html | 36 + docs/dws/tool/dws_16_0131.html | 475 ++ docs/dws/tool/dws_16_0132.html | 31 + docs/dws/tool/dws_16_0133.html | 32 + docs/dws/tool/dws_16_0134.html | 43 + docs/dws/tool/dws_16_0135.html | 45 + docs/dws/tool/dws_16_0136.html | 24 + docs/dws/tool/dws_16_0137.html | 31 + docs/dws/tool/dws_16_0138.html | 26 + docs/dws/tool/dws_16_0139.html | 36 + docs/dws/tool/dws_16_0140.html | 32 + docs/dws/tool/dws_16_0141.html | 62 + docs/dws/tool/dws_16_0142.html | 32 + docs/dws/tool/dws_16_0143.html | 31 + docs/dws/tool/dws_16_0145.html | 48 + docs/dws/tool/dws_16_0146.html | 100 + docs/dws/tool/dws_16_0147.html | 30 + docs/dws/tool/dws_16_0148.html | 65 + docs/dws/tool/dws_16_0149.html | 48 + docs/dws/tool/dws_16_0150.html | 47 + docs/dws/tool/dws_16_0151.html | 32 + docs/dws/tool/dws_16_0152.html | 47 + docs/dws/tool/dws_16_0153.html | 47 + docs/dws/tool/dws_16_0154.html | 55 + docs/dws/tool/dws_16_0155.html | 94 + docs/dws/tool/dws_16_0156.html | 31 + docs/dws/tool/dws_16_0157.html | 34 + docs/dws/tool/dws_16_0158.html | 53 + docs/dws/tool/dws_16_0159.html | 17 + docs/dws/tool/dws_16_0160.html | 23 + docs/dws/tool/dws_16_0161.html | 39 + docs/dws/tool/dws_16_0162.html | 53 + docs/dws/tool/dws_16_0163.html | 57 + docs/dws/tool/dws_16_0164.html | 52 + docs/dws/tool/dws_16_0165.html | 86 + docs/dws/tool/dws_16_0166.html | 30 + docs/dws/tool/dws_16_0167.html | 176 + docs/dws/tool/dws_16_0168.html | 73 + docs/dws/tool/dws_16_0169.html | 84 + docs/dws/tool/dws_16_0170.html | 91 + docs/dws/tool/dws_16_0171.html | 115 + docs/dws/tool/dws_16_0172.html | 116 + docs/dws/tool/dws_16_0173.html | 82 + docs/dws/tool/dws_16_0174.html | 29 + docs/dws/tool/dws_16_0175.html | 31 + docs/dws/tool/dws_16_0176.html | 32 + docs/dws/tool/dws_16_0177.html | 22 + docs/dws/tool/dws_16_0178.html | 26 + docs/dws/tool/dws_16_0179.html | 39 + docs/dws/tool/dws_16_0180.html | 25 + docs/dws/tool/dws_16_0181.html | 17 + docs/dws/tool/dws_16_0182.html | 27 + docs/dws/tool/dws_16_0183.html | 26 + docs/dws/tool/dws_16_0184.html | 30 + docs/dws/tool/dws_16_0185.html | 32 + docs/dws/tool/dws_16_0186.html | 25 + docs/dws/tool/dws_16_0187.html | 23 + docs/dws/tool/dws_16_0188.html | 33 + docs/dws/tool/dws_16_0189.html | 33 + docs/dws/tool/dws_16_0190.html | 17 + docs/dws/tool/dws_16_0191.html | 23 + docs/dws/tool/dws_16_0192.html | 21 + docs/dws/tool/dws_16_0193.html | 22 + docs/dws/tool/dws_16_0194.html | 17 + docs/dws/tool/dws_16_0195.html | 17 + docs/dws/tool/dws_16_0196.html | 43 + docs/dws/tool/dws_16_0197.html | 17 + docs/dws/tool/dws_16_0198.html | 26 + docs/dws/tool/dws_16_0199.html | 25 + docs/dws/tool/dws_16_0200.html | 23 + docs/dws/tool/dws_16_0201.html | 33 + docs/dws/tool/dws_16_0202.html | 31 + docs/dws/tool/dws_16_0203.html | 23 + docs/dws/tool/dws_16_0204.html | 18 + docs/dws/tool/dws_16_0205.html | 18 + docs/dws/tool/dws_16_0206.html | 47 + docs/dws/tool/dws_16_0207.html | 44 + docs/dws/tool/dws_16_0208.html | 16 + docs/dws/tool/dws_16_0209.html | 200 + docs/dws/tool/dws_16_0210.html | 623 ++ docs/dws/tool/dws_16_0211.html | 124 + docs/dws/tool/dws_16_0212.html | 118 + docs/dws/tool/dws_16_0213.html | 547 ++ docs/dws/tool/dws_16_0214.html | 74 + docs/dws/tool/dws_16_0215.html | 106 + docs/dws/tool/dws_16_0216.html | 46 + docs/dws/tool/dws_16_0217.html | 16 + docs/dws/tool/dws_gsql_007.html | 30 +- docs/dws/tool/dws_mt_0012.html | 131 - docs/dws/tool/dws_mt_0014.html | 225 - docs/dws/tool/dws_mt_0015.html | 15 - docs/dws/tool/dws_mt_0021.html | 116 - docs/dws/tool/dws_mt_0023.html | 27 - docs/dws/tool/dws_mt_0024.html | 12 - docs/dws/tool/dws_mt_0025.html | 276 - docs/dws/tool/dws_mt_0026.html | 334 - docs/dws/tool/dws_mt_0027.html | 547 -- docs/dws/tool/dws_mt_0029.html | 222 - docs/dws/tool/dws_mt_0030.html | 74 - docs/dws/tool/dws_mt_0031.html | 27 - docs/dws/tool/dws_mt_0032.html | 25 - docs/dws/tool/dws_mt_0033.html | 372 -- docs/dws/tool/dws_mt_0034.html | 21 - docs/dws/tool/dws_mt_0035.html | 170 - docs/dws/tool/dws_mt_0036.html | 24 - docs/dws/tool/dws_mt_0037.html | 12 - docs/dws/tool/dws_mt_0038.html | 53 - docs/dws/tool/dws_mt_0039.html | 106 - docs/dws/tool/dws_mt_0041.html | 96 - docs/dws/tool/dws_mt_0042.html | 165 - docs/dws/tool/dws_mt_0044.html | 39 - docs/dws/tool/dws_mt_0045.html | 12 - docs/dws/tool/dws_mt_0046.html | 33 - docs/dws/tool/dws_mt_0048.html | 1463 ---- docs/dws/tool/dws_mt_0066.html | 134 - docs/dws/tool/dws_mt_0067.html | 38 - docs/dws/tool/dws_mt_0070.html | 102 - docs/dws/tool/dws_mt_0071.html | 1269 ---- docs/dws/tool/dws_mt_0084.html | 982 --- docs/dws/tool/dws_mt_0094.html | 541 -- docs/dws/tool/dws_mt_0100.html | 94 - docs/dws/tool/dws_mt_0101.html | 89 - docs/dws/tool/dws_mt_0102.html | 413 -- docs/dws/tool/dws_mt_0104.html | 4 +- docs/dws/tool/dws_mt_0105.html | 6 +- docs/dws/tool/dws_mt_0106.html | 10 +- docs/dws/tool/dws_mt_0108.html | 3642 ++++++---- docs/dws/tool/dws_mt_0109.html | 10 +- docs/dws/tool/dws_mt_0110.html | 249 +- docs/dws/tool/dws_mt_0111.html | 10 +- docs/dws/tool/dws_mt_0112.html | 94 +- docs/dws/tool/dws_mt_0113.html | 8 +- docs/dws/tool/dws_mt_0114.html | 86 +- docs/dws/tool/dws_mt_0115.html | 787 ++- docs/dws/tool/dws_mt_0128.html | 181 +- docs/dws/tool/dws_mt_0132.html | 14 +- docs/dws/tool/dws_mt_0133.html | 8 +- docs/dws/tool/dws_mt_0135.html | 306 +- docs/dws/tool/dws_mt_0136.html | 486 +- docs/dws/tool/dws_mt_0137.html | 314 +- docs/dws/tool/dws_mt_0138.html | 450 +- docs/dws/tool/dws_mt_0139.html | 815 ++- docs/dws/tool/dws_mt_0141.html | 1361 ++-- docs/dws/tool/dws_mt_0155.html | 437 +- docs/dws/tool/dws_mt_0156.html | 8 +- docs/dws/tool/dws_mt_0158.html | 1729 +++-- docs/dws/tool/dws_mt_0159.html | 3127 ++++++--- docs/dws/tool/dws_mt_0183.html | 19 - docs/dws/tool/dws_mt_0184.html | 275 - docs/dws/tool/dws_mt_0185.html | 26 - docs/dws/tool/dws_mt_0186.html | 137 - docs/dws/tool/dws_mt_0187.html | 19 - docs/dws/tool/dws_mt_0188.html | 17 - docs/dws/tool/dws_mt_0189.html | 75 - docs/dws/tool/dws_mt_0190.html | 42 - docs/dws/tool/dws_mt_0191.html | 138 - docs/dws/tool/dws_mt_0192.html | 20 +- docs/dws/tool/dws_mt_0193.html | 18 - docs/dws/tool/dws_mt_0207.html | 39 - docs/dws/tool/dws_mt_0212.html | 12 +- docs/dws/tool/dws_mt_0215.html | 101 +- docs/dws/tool/dws_mt_0216.html | 354 +- docs/dws/tool/dws_mt_0221.html | 51 +- docs/dws/tool/dws_mt_0222.html | 34 +- docs/dws/tool/dws_mt_0301.html | 430 +- docs/dws/tool/dws_mt_0302.html | 153 +- docs/dws/tool/dws_mt_0303.html | 140 +- docs/dws/tool/dws_mt_0304.html | 276 +- docs/dws/tool/dws_mt_0305.html | 40 +- docs/dws/tool/dws_mt_0306.html | 279 +- docs/dws/tool/dws_mt_index.html | 38 +- docs/dws/tool/dws_sct_0013.html | 41 - .../figure/en-us_image_0000001188681130.png | Bin 6232 -> 0 bytes .../figure/en-us_image_0000001188681162.png | Bin 209150 -> 0 bytes .../figure/en-us_image_0000001234042247.png | Bin 36552 -> 0 bytes .../figure/en-us_image_0000001234042287.png | Bin 635423 -> 0 bytes .../figure/en-us_image_0000001234200759.png | Bin 640252 -> 0 bytes .../figure/en-us_image_0000001382373772.png | Bin 0 -> 1919 bytes ...4.png => en-us_image_0000001384569256.png} | Bin ...6.png => en-us_image_0000001387842380.png} | Bin .../figure/en-us_image_0000001432333769.png | Bin 0 -> 1334 bytes .../figure/en-us_image_0000001432453549.png | Bin 0 -> 1334 bytes .../figure/en-us_image_0000001432533957.png | Bin 0 -> 1940 bytes .../figure/en-us_image_0000001432613505.png | Bin 0 -> 862 bytes ...4.png => en-us_image_0000001434809241.png} | Bin ...5.png => en-us_image_0000001657865806.png} | Bin ...5.png => en-us_image_0000001657865822.png} | Bin ...4.jpg => en-us_image_0000001657865874.jpg} | Bin ...2.png => en-us_image_0000001657865890.png} | Bin ...8.png => en-us_image_0000001657865902.png} | Bin ...7.png => en-us_image_0000001657865926.png} | Bin ...9.png => en-us_image_0000001657865930.png} | Bin ...6.png => en-us_image_0000001657865946.png} | Bin ...7.png => en-us_image_0000001657865950.png} | Bin .../figure/en-us_image_0000001657865966.png | Bin 0 -> 93842 bytes ...8.png => en-us_image_0000001657865986.png} | Bin ...0.png => en-us_image_0000001657865990.png} | Bin ...8.png => en-us_image_0000001657865994.png} | Bin ...3.png => en-us_image_0000001657865998.png} | Bin ...3.png => en-us_image_0000001658025090.png} | Bin ...7.png => en-us_image_0000001658025146.png} | Bin ...5.png => en-us_image_0000001658025202.png} | Bin ...6.png => en-us_image_0000001658025214.png} | Bin ...2.png => en-us_image_0000001658025218.png} | Bin ...5.jpg => en-us_image_0000001658025226.jpg} | Bin ...9.png => en-us_image_0000001658025254.png} | Bin ...1.png => en-us_image_0000001658025258.png} | Bin ...5.png => en-us_image_0000001658025270.png} | Bin ...4.png => en-us_image_0000001658025274.png} | Bin ...9.png => en-us_image_0000001658025302.png} | Bin ...8.png => en-us_image_0000001658025306.png} | Bin ...2.png => en-us_image_0000001658025310.png} | Bin ...9.png => en-us_image_0000001658025314.png} | Bin ...4.png => en-us_image_0000001706105257.png} | Bin ...7.jpg => en-us_image_0000001706105309.jpg} | Bin ...1.png => en-us_image_0000001706105325.png} | Bin ...5.png => en-us_image_0000001706105329.png} | Bin ...0.png => en-us_image_0000001706105333.png} | Bin ...8.png => en-us_image_0000001706105337.png} | Bin ...2.png => en-us_image_0000001706105385.png} | Bin ...6.png => en-us_image_0000001706105389.png} | Bin .../figure/en-us_image_0000001706105425.png | Bin 0 -> 19585 bytes ...6.png => en-us_image_0000001706105429.png} | Bin ...3.png => en-us_image_0000001706105433.png} | Bin ...3.png => en-us_image_0000001706105437.png} | Bin ...3.png => en-us_image_0000001706224445.png} | Bin ...9.png => en-us_image_0000001706224505.png} | Bin ...5.png => en-us_image_0000001706224557.png} | Bin ...1.png => en-us_image_0000001706224565.png} | Bin ...2.jpg => en-us_image_0000001706224569.jpg} | Bin ...8.png => en-us_image_0000001706224573.png} | Bin ...6.png => en-us_image_0000001706224577.png} | Bin ...3.png => en-us_image_0000001706224581.png} | Bin ...9.png => en-us_image_0000001706224629.png} | Bin ...4.png => en-us_image_0000001706224653.png} | Bin ...1.png => en-us_image_0000001706224669.png} | Bin ...5.png => en-us_image_0000001706224673.png} | Bin .../figure/en-us_image_0000001809221997.png | Bin 0 -> 10309 bytes .../figure/en-us_image_0000001809304349.png | Bin 0 -> 218259 bytes docs/dws/tool/mt_tool_index.html | 20 +- 406 files changed, 38000 insertions(+), 22627 deletions(-) delete mode 100644 docs/dws/tool/dws_07_0666.html delete mode 100644 docs/dws/tool/dws_07_0675.html delete mode 100644 docs/dws/tool/dws_07_0676.html delete mode 100644 docs/dws/tool/dws_07_0684.html delete mode 100644 docs/dws/tool/dws_07_6831.html delete mode 100644 docs/dws/tool/dws_07_6832.html delete mode 100644 docs/dws/tool/dws_07_6833.html delete mode 100644 docs/dws/tool/dws_07_6834.html delete mode 100644 docs/dws/tool/dws_07_6835.html delete mode 100644 docs/dws/tool/dws_07_6836.html delete mode 100644 docs/dws/tool/dws_07_6837.html delete mode 100644 docs/dws/tool/dws_07_6838.html delete mode 100644 docs/dws/tool/dws_07_6841.html delete mode 100644 docs/dws/tool/dws_07_6842.html delete mode 100644 docs/dws/tool/dws_07_6843.html delete mode 100644 docs/dws/tool/dws_07_6844.html delete mode 100644 docs/dws/tool/dws_07_6845.html delete mode 100644 docs/dws/tool/dws_07_6846.html delete mode 100644 docs/dws/tool/dws_07_8111.html delete mode 100644 docs/dws/tool/dws_07_8120.html delete mode 100644 docs/dws/tool/dws_07_8121.html delete mode 100644 docs/dws/tool/dws_07_8310.html delete mode 100644 docs/dws/tool/dws_07_8311.html delete mode 100644 docs/dws/tool/dws_07_8312.html delete mode 100644 docs/dws/tool/dws_07_8313.html delete mode 100644 docs/dws/tool/dws_07_8314.html create mode 100644 docs/dws/tool/dws_16_0001.html create mode 100644 docs/dws/tool/dws_16_0002.html create mode 100644 docs/dws/tool/dws_16_0003.html create mode 100644 docs/dws/tool/dws_16_0005.html create mode 100644 docs/dws/tool/dws_16_0006.html create mode 100644 docs/dws/tool/dws_16_0008.html create mode 100644 docs/dws/tool/dws_16_0009.html create mode 100644 docs/dws/tool/dws_16_0010.html create mode 100644 docs/dws/tool/dws_16_0012.html create mode 100644 docs/dws/tool/dws_16_0013.html create mode 100644 docs/dws/tool/dws_16_0014.html create mode 100644 docs/dws/tool/dws_16_0015.html create mode 100644 docs/dws/tool/dws_16_0016.html create mode 100644 docs/dws/tool/dws_16_0017.html create mode 100644 docs/dws/tool/dws_16_0018.html create mode 100644 docs/dws/tool/dws_16_0019.html create mode 100644 docs/dws/tool/dws_16_0020.html create mode 100644 docs/dws/tool/dws_16_0021.html create mode 100644 docs/dws/tool/dws_16_0022.html create mode 100644 docs/dws/tool/dws_16_0023.html create mode 100644 docs/dws/tool/dws_16_0024.html create mode 100644 docs/dws/tool/dws_16_0025.html create mode 100644 docs/dws/tool/dws_16_0026.html create mode 100644 docs/dws/tool/dws_16_0027.html create mode 100644 docs/dws/tool/dws_16_0028.html create mode 100644 docs/dws/tool/dws_16_0029.html create mode 100644 docs/dws/tool/dws_16_0030.html create mode 100644 docs/dws/tool/dws_16_0031.html create mode 100644 docs/dws/tool/dws_16_0032.html create mode 100644 docs/dws/tool/dws_16_0033.html create mode 100644 docs/dws/tool/dws_16_0034.html create mode 100644 docs/dws/tool/dws_16_0035.html create mode 100644 docs/dws/tool/dws_16_0036.html create mode 100644 docs/dws/tool/dws_16_0038.html create mode 100644 docs/dws/tool/dws_16_0039.html create mode 100644 docs/dws/tool/dws_16_0040.html create mode 100644 docs/dws/tool/dws_16_0041.html create mode 100644 docs/dws/tool/dws_16_0043.html create mode 100644 docs/dws/tool/dws_16_0044.html create mode 100644 docs/dws/tool/dws_16_0045.html create mode 100644 docs/dws/tool/dws_16_0046.html create mode 100644 docs/dws/tool/dws_16_0047.html create mode 100644 docs/dws/tool/dws_16_0048.html create mode 100644 docs/dws/tool/dws_16_0049.html create mode 100644 docs/dws/tool/dws_16_0051.html create mode 100644 docs/dws/tool/dws_16_0052.html create mode 100644 docs/dws/tool/dws_16_0053.html create mode 100644 docs/dws/tool/dws_16_0054.html create mode 100644 docs/dws/tool/dws_16_0055.html rename docs/dws/tool/{dws_mt_0091.html => dws_16_0056.html} (59%) create mode 100644 docs/dws/tool/dws_16_0059.html create mode 100644 docs/dws/tool/dws_16_0061.html create mode 100644 docs/dws/tool/dws_16_0063.html create mode 100644 docs/dws/tool/dws_16_0064.html create mode 100644 docs/dws/tool/dws_16_0065.html create mode 100644 docs/dws/tool/dws_16_0066.html create mode 100644 docs/dws/tool/dws_16_0067.html create mode 100644 docs/dws/tool/dws_16_0068.html create mode 100644 docs/dws/tool/dws_16_0069.html create mode 100644 docs/dws/tool/dws_16_0070.html create mode 100644 docs/dws/tool/dws_16_0071.html create mode 100644 docs/dws/tool/dws_16_0072.html create mode 100644 docs/dws/tool/dws_16_0073.html create mode 100644 docs/dws/tool/dws_16_0074.html rename docs/dws/tool/{dws_mt_0064.html => dws_16_0075.html} (81%) rename docs/dws/tool/{dws_mt_0065.html => dws_16_0076.html} (53%) create mode 100644 docs/dws/tool/dws_16_0077.html create mode 100644 docs/dws/tool/dws_16_0078.html rename docs/dws/tool/{dws_mt_0068.html => dws_16_0079.html} (60%) rename docs/dws/tool/{dws_mt_0069.html => dws_16_0080.html} (75%) create mode 100644 docs/dws/tool/dws_16_0081.html create mode 100644 docs/dws/tool/dws_16_0082.html create mode 100644 docs/dws/tool/dws_16_0083.html create mode 100644 docs/dws/tool/dws_16_0084.html create mode 100644 docs/dws/tool/dws_16_0086.html create mode 100644 docs/dws/tool/dws_16_0087.html create mode 100644 docs/dws/tool/dws_16_0088.html create mode 100644 docs/dws/tool/dws_16_0089.html create mode 100644 docs/dws/tool/dws_16_0090.html create mode 100644 docs/dws/tool/dws_16_0091.html create mode 100644 docs/dws/tool/dws_16_0092.html create mode 100644 docs/dws/tool/dws_16_0093.html create mode 100644 docs/dws/tool/dws_16_0094.html create mode 100644 docs/dws/tool/dws_16_0095.html create mode 100644 docs/dws/tool/dws_16_0096.html create mode 100644 docs/dws/tool/dws_16_0097.html create mode 100644 docs/dws/tool/dws_16_0098.html rename docs/dws/tool/{dws_mt_0103.html => dws_16_0099.html} (55%) create mode 100644 docs/dws/tool/dws_16_0100.html create mode 100644 docs/dws/tool/dws_16_0101.html create mode 100644 docs/dws/tool/dws_16_0102.html create mode 100644 docs/dws/tool/dws_16_0103.html create mode 100644 docs/dws/tool/dws_16_0105.html create mode 100644 docs/dws/tool/dws_16_0106.html create mode 100644 docs/dws/tool/dws_16_0108.html create mode 100644 docs/dws/tool/dws_16_0109.html create mode 100644 docs/dws/tool/dws_16_0110.html create mode 100644 docs/dws/tool/dws_16_0111.html create mode 100644 docs/dws/tool/dws_16_0112.html create mode 100644 docs/dws/tool/dws_16_0113.html create mode 100644 docs/dws/tool/dws_16_0114.html create mode 100644 docs/dws/tool/dws_16_0115.html create mode 100644 docs/dws/tool/dws_16_0116.html create mode 100644 docs/dws/tool/dws_16_0117.html create mode 100644 docs/dws/tool/dws_16_0118.html create mode 100644 docs/dws/tool/dws_16_0119.html create mode 100644 docs/dws/tool/dws_16_0120.html create mode 100644 docs/dws/tool/dws_16_0121.html create mode 100644 docs/dws/tool/dws_16_0122.html create mode 100644 docs/dws/tool/dws_16_0123.html create mode 100644 docs/dws/tool/dws_16_0124.html create mode 100644 docs/dws/tool/dws_16_0125.html create mode 100644 docs/dws/tool/dws_16_0126.html create mode 100644 docs/dws/tool/dws_16_0127.html create mode 100644 docs/dws/tool/dws_16_0128.html create mode 100644 docs/dws/tool/dws_16_0129.html create mode 100644 docs/dws/tool/dws_16_0130.html create mode 100644 docs/dws/tool/dws_16_0131.html create mode 100644 docs/dws/tool/dws_16_0132.html create mode 100644 docs/dws/tool/dws_16_0133.html create mode 100644 docs/dws/tool/dws_16_0134.html create mode 100644 docs/dws/tool/dws_16_0135.html create mode 100644 docs/dws/tool/dws_16_0136.html create mode 100644 docs/dws/tool/dws_16_0137.html create mode 100644 docs/dws/tool/dws_16_0138.html create mode 100644 docs/dws/tool/dws_16_0139.html create mode 100644 docs/dws/tool/dws_16_0140.html create mode 100644 docs/dws/tool/dws_16_0141.html create mode 100644 docs/dws/tool/dws_16_0142.html create mode 100644 docs/dws/tool/dws_16_0143.html create mode 100644 docs/dws/tool/dws_16_0145.html create mode 100644 docs/dws/tool/dws_16_0146.html create mode 100644 docs/dws/tool/dws_16_0147.html create mode 100644 docs/dws/tool/dws_16_0148.html create mode 100644 docs/dws/tool/dws_16_0149.html create mode 100644 docs/dws/tool/dws_16_0150.html create mode 100644 docs/dws/tool/dws_16_0151.html create mode 100644 docs/dws/tool/dws_16_0152.html create mode 100644 docs/dws/tool/dws_16_0153.html create mode 100644 docs/dws/tool/dws_16_0154.html create mode 100644 docs/dws/tool/dws_16_0155.html create mode 100644 docs/dws/tool/dws_16_0156.html create mode 100644 docs/dws/tool/dws_16_0157.html create mode 100644 docs/dws/tool/dws_16_0158.html create mode 100644 docs/dws/tool/dws_16_0159.html create mode 100644 docs/dws/tool/dws_16_0160.html create mode 100644 docs/dws/tool/dws_16_0161.html create mode 100644 docs/dws/tool/dws_16_0162.html create mode 100644 docs/dws/tool/dws_16_0163.html create mode 100644 docs/dws/tool/dws_16_0164.html create mode 100644 docs/dws/tool/dws_16_0165.html create mode 100644 docs/dws/tool/dws_16_0166.html create mode 100644 docs/dws/tool/dws_16_0167.html create mode 100644 docs/dws/tool/dws_16_0168.html create mode 100644 docs/dws/tool/dws_16_0169.html create mode 100644 docs/dws/tool/dws_16_0170.html create mode 100644 docs/dws/tool/dws_16_0171.html create mode 100644 docs/dws/tool/dws_16_0172.html create mode 100644 docs/dws/tool/dws_16_0173.html create mode 100644 docs/dws/tool/dws_16_0174.html create mode 100644 docs/dws/tool/dws_16_0175.html create mode 100644 docs/dws/tool/dws_16_0176.html create mode 100644 docs/dws/tool/dws_16_0177.html create mode 100644 docs/dws/tool/dws_16_0178.html create mode 100644 docs/dws/tool/dws_16_0179.html create mode 100644 docs/dws/tool/dws_16_0180.html create mode 100644 docs/dws/tool/dws_16_0181.html create mode 100644 docs/dws/tool/dws_16_0182.html create mode 100644 docs/dws/tool/dws_16_0183.html create mode 100644 docs/dws/tool/dws_16_0184.html create mode 100644 docs/dws/tool/dws_16_0185.html create mode 100644 docs/dws/tool/dws_16_0186.html create mode 100644 docs/dws/tool/dws_16_0187.html create mode 100644 docs/dws/tool/dws_16_0188.html create mode 100644 docs/dws/tool/dws_16_0189.html create mode 100644 docs/dws/tool/dws_16_0190.html create mode 100644 docs/dws/tool/dws_16_0191.html create mode 100644 docs/dws/tool/dws_16_0192.html create mode 100644 docs/dws/tool/dws_16_0193.html create mode 100644 docs/dws/tool/dws_16_0194.html create mode 100644 docs/dws/tool/dws_16_0195.html create mode 100644 docs/dws/tool/dws_16_0196.html create mode 100644 docs/dws/tool/dws_16_0197.html create mode 100644 docs/dws/tool/dws_16_0198.html create mode 100644 docs/dws/tool/dws_16_0199.html create mode 100644 docs/dws/tool/dws_16_0200.html create mode 100644 docs/dws/tool/dws_16_0201.html create mode 100644 docs/dws/tool/dws_16_0202.html create mode 100644 docs/dws/tool/dws_16_0203.html create mode 100644 docs/dws/tool/dws_16_0204.html create mode 100644 docs/dws/tool/dws_16_0205.html create mode 100644 docs/dws/tool/dws_16_0206.html create mode 100644 docs/dws/tool/dws_16_0207.html create mode 100644 docs/dws/tool/dws_16_0208.html create mode 100644 docs/dws/tool/dws_16_0209.html create mode 100644 docs/dws/tool/dws_16_0210.html create mode 100644 docs/dws/tool/dws_16_0211.html create mode 100644 docs/dws/tool/dws_16_0212.html create mode 100644 docs/dws/tool/dws_16_0213.html create mode 100644 docs/dws/tool/dws_16_0214.html create mode 100644 docs/dws/tool/dws_16_0215.html create mode 100644 docs/dws/tool/dws_16_0216.html create mode 100644 docs/dws/tool/dws_16_0217.html delete mode 100644 docs/dws/tool/dws_mt_0012.html delete mode 100644 docs/dws/tool/dws_mt_0014.html delete mode 100644 docs/dws/tool/dws_mt_0015.html delete mode 100644 docs/dws/tool/dws_mt_0021.html delete mode 100644 docs/dws/tool/dws_mt_0023.html delete mode 100644 docs/dws/tool/dws_mt_0024.html delete mode 100644 docs/dws/tool/dws_mt_0025.html delete mode 100644 docs/dws/tool/dws_mt_0026.html delete mode 100644 docs/dws/tool/dws_mt_0027.html delete mode 100644 docs/dws/tool/dws_mt_0029.html delete mode 100644 docs/dws/tool/dws_mt_0030.html delete mode 100644 docs/dws/tool/dws_mt_0031.html delete mode 100644 docs/dws/tool/dws_mt_0032.html delete mode 100644 docs/dws/tool/dws_mt_0033.html delete mode 100644 docs/dws/tool/dws_mt_0034.html delete mode 100644 docs/dws/tool/dws_mt_0035.html delete mode 100644 docs/dws/tool/dws_mt_0036.html delete mode 100644 docs/dws/tool/dws_mt_0037.html delete mode 100644 docs/dws/tool/dws_mt_0038.html delete mode 100644 docs/dws/tool/dws_mt_0039.html delete mode 100644 docs/dws/tool/dws_mt_0041.html delete mode 100644 docs/dws/tool/dws_mt_0042.html delete mode 100644 docs/dws/tool/dws_mt_0044.html delete mode 100644 docs/dws/tool/dws_mt_0045.html delete mode 100644 docs/dws/tool/dws_mt_0046.html delete mode 100644 docs/dws/tool/dws_mt_0048.html delete mode 100644 docs/dws/tool/dws_mt_0066.html delete mode 100644 docs/dws/tool/dws_mt_0067.html delete mode 100644 docs/dws/tool/dws_mt_0070.html delete mode 100644 docs/dws/tool/dws_mt_0071.html delete mode 100644 docs/dws/tool/dws_mt_0084.html delete mode 100644 docs/dws/tool/dws_mt_0094.html delete mode 100644 docs/dws/tool/dws_mt_0100.html delete mode 100644 docs/dws/tool/dws_mt_0101.html delete mode 100644 docs/dws/tool/dws_mt_0102.html delete mode 100644 docs/dws/tool/dws_mt_0183.html delete mode 100644 docs/dws/tool/dws_mt_0184.html delete mode 100644 docs/dws/tool/dws_mt_0185.html delete mode 100644 docs/dws/tool/dws_mt_0186.html delete mode 100644 docs/dws/tool/dws_mt_0187.html delete mode 100644 docs/dws/tool/dws_mt_0188.html delete mode 100644 docs/dws/tool/dws_mt_0189.html delete mode 100644 docs/dws/tool/dws_mt_0190.html delete mode 100644 docs/dws/tool/dws_mt_0191.html delete mode 100644 docs/dws/tool/dws_mt_0193.html delete mode 100644 docs/dws/tool/dws_mt_0207.html delete mode 100644 docs/dws/tool/dws_sct_0013.html delete mode 100644 docs/dws/tool/figure/en-us_image_0000001188681130.png delete mode 100644 docs/dws/tool/figure/en-us_image_0000001188681162.png delete mode 100644 docs/dws/tool/figure/en-us_image_0000001234042247.png delete mode 100644 docs/dws/tool/figure/en-us_image_0000001234042287.png delete mode 100644 docs/dws/tool/figure/en-us_image_0000001234200759.png create mode 100644 docs/dws/tool/figure/en-us_image_0000001382373772.png rename docs/dws/tool/figure/{en-us_image_0000001188362654.png => en-us_image_0000001384569256.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188362656.png => en-us_image_0000001387842380.png} (100%) create mode 100644 docs/dws/tool/figure/en-us_image_0000001432333769.png create mode 100644 docs/dws/tool/figure/en-us_image_0000001432453549.png create mode 100644 docs/dws/tool/figure/en-us_image_0000001432533957.png create mode 100644 docs/dws/tool/figure/en-us_image_0000001432613505.png rename docs/dws/tool/figure/{en-us_image_0000001188521204.png => en-us_image_0000001434809241.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233800845.png => en-us_image_0000001657865806.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233800815.png => en-us_image_0000001657865822.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188202724.jpg => en-us_image_0000001657865874.jpg} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188202702.png => en-us_image_0000001657865890.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188202698.png => en-us_image_0000001657865902.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200727.png => en-us_image_0000001657865926.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233800799.png => en-us_image_0000001657865930.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188362646.png => en-us_image_0000001657865946.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200717.png => en-us_image_0000001657865950.png} (100%) create mode 100644 docs/dws/tool/figure/en-us_image_0000001657865966.png rename docs/dws/tool/figure/{en-us_image_0000001188681128.png => en-us_image_0000001657865986.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188202690.png => en-us_image_0000001657865990.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188521208.png => en-us_image_0000001657865994.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234042243.png => en-us_image_0000001657865998.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200773.png => en-us_image_0000001658025090.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234042257.png => en-us_image_0000001658025146.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233800835.png => en-us_image_0000001658025202.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188681136.png => en-us_image_0000001658025214.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188521222.png => en-us_image_0000001658025218.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233922305.jpg => en-us_image_0000001658025226.jpg} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234042239.png => en-us_image_0000001658025254.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234042241.png => en-us_image_0000001658025258.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200695.png => en-us_image_0000001658025270.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188681114.png => en-us_image_0000001658025274.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233800839.png => en-us_image_0000001658025302.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188202688.png => en-us_image_0000001658025306.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188202692.png => en-us_image_0000001658025310.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200729.png => en-us_image_0000001658025314.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188681124.png => en-us_image_0000001706105257.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233800837.jpg => en-us_image_0000001706105309.jpg} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233800811.png => en-us_image_0000001706105325.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200745.png => en-us_image_0000001706105329.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188362670.png => en-us_image_0000001706105333.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188521218.png => en-us_image_0000001706105337.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188362642.png => en-us_image_0000001706105385.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188681116.png => en-us_image_0000001706105389.png} (100%) create mode 100644 docs/dws/tool/figure/en-us_image_0000001706105425.png rename docs/dws/tool/figure/{en-us_image_0000001188681126.png => en-us_image_0000001706105429.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233922293.png => en-us_image_0000001706105433.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200733.png => en-us_image_0000001706105437.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234042283.png => en-us_image_0000001706224445.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233922289.png => en-us_image_0000001706224505.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233922325.png => en-us_image_0000001706224557.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233922301.png => en-us_image_0000001706224565.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188362672.jpg => en-us_image_0000001706224569.jpg} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188681138.png => en-us_image_0000001706224573.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188521216.png => en-us_image_0000001706224577.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234042253.png => en-us_image_0000001706224581.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001234200719.png => en-us_image_0000001706224629.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001188362694.png => en-us_image_0000001706224653.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233922291.png => en-us_image_0000001706224669.png} (100%) rename docs/dws/tool/figure/{en-us_image_0000001233922295.png => en-us_image_0000001706224673.png} (100%) create mode 100644 docs/dws/tool/figure/en-us_image_0000001809221997.png create mode 100644 docs/dws/tool/figure/en-us_image_0000001809304349.png diff --git a/docs/dws/tool/ALL_META.TXT.json b/docs/dws/tool/ALL_META.TXT.json index 3e70b212..d6430abb 100644 --- a/docs/dws/tool/ALL_META.TXT.json +++ b/docs/dws/tool/ALL_META.TXT.json @@ -1,2951 +1,7546 @@ [ + { + "dockw":"Tool Guide" + }, { "uri":"dws_07_0001.html", + "node_id":"en-us_topic_0000001233800667.xml", "product_code":"dws", "code":"1", "des":"This document describes how to use GaussDB(DWS) tools, including client tools, as shown in Table 1, and server tools, as shown in Table 2.The client tools can be obtained", "doc_type":"tg", "kw":"Overview,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"dws_07_0002.html", + "node_id":"en-us_topic_0000001515111185.xml", "product_code":"dws", "code":"2", "des":"Log in to the GaussDB(DWS) management console at: https://console.otc.t-systems.com/dws/You can download the following tools:gsql CLI client: The gsql tool package contai", "doc_type":"tg", "kw":"Downloading Related Tools,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Downloading Related Tools", "githuburl":"" }, { "uri":"dws_gsql_index.html", + "node_id":"en-us_topic_0000001188521128.xml", "product_code":"dws", "code":"3", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"gsql", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gsql", "githuburl":"" }, { "uri":"dws_gsql_002.html", + "node_id":"en-us_topic_0000001234200693.xml", "product_code":"dws", "code":"4", "des":"Connect to the database: Use the gsql client to remotely connect to the GaussDB(DWS) database. If the gsql client is used to connect to a database, the connection timeout", "doc_type":"tg", "kw":"Overview,gsql,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"dws_gsql_003.html", + "node_id":"en-us_topic_0000001188521082.xml", "product_code":"dws", "code":"5", "des":"For details about how to download and install gsql and connect it to the cluster database, see section \"Using the gsql CLI Client to Connect to a Cluster\" in the Data War", "doc_type":"tg", "kw":"Instruction,gsql,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Instruction", "githuburl":"" }, { "uri":"dws_gsql_005.html", + "node_id":"en-us_topic_0000001234200681.xml", "product_code":"dws", "code":"6", "des":"When a database is being connected, run the following commands to obtain the help information:gsql --helpThe following information is displayed:......\nUsage:\n gsql [OPTI", "doc_type":"tg", "kw":"Online Help,gsql,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Online Help", "githuburl":"" }, { "uri":"dws_gsql_006.html", + "node_id":"en-us_topic_0000001233922173.xml", "product_code":"dws", "code":"7", "des":"For details about gsql parameters, see Table 1, Table 2, Table 3, and Table 4.", "doc_type":"tg", "kw":"Command Reference,gsql,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Command Reference", "githuburl":"" }, { "uri":"dws_gsql_007.html", + "node_id":"en-us_topic_0000001233922235.xml", "product_code":"dws", "code":"8", "des":"This section describes meta-commands provided by gsql after the GaussDB(DWS) database CLI tool is used to connect to a database. A gsql meta-command can be anything that ", "doc_type":"tg", "kw":"Meta-Command Reference,gsql,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Meta-Command Reference", "githuburl":"" }, { "uri":"dws_gsql_008.html", + "node_id":"en-us_topic_0000001188681032.xml", "product_code":"dws", "code":"9", "des":"The database kernel slowly runs the initialization statement.Problems are difficult to locate in this scenario. Try using the strace Linux trace command.strace gsql -U My", "doc_type":"tg", "kw":"Troubleshooting,gsql,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Troubleshooting", "githuburl":"" }, { "uri":"dws_ds_index.html", + "node_id":"en-us_topic_0000001188202556.xml", "product_code":"dws", "code":"10", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Data Studio", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Data Studio", "githuburl":"" }, { "uri":"DWS_DS_09.html", + "node_id":"en-us_topic_0000001233922147.xml", "product_code":"dws", "code":"11", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"About Data Studio", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"About Data Studio", "githuburl":"" }, { "uri":"dws_07_0012.html", + "node_id":"en-us_topic_0000001233800675.xml", "product_code":"dws", "code":"12", "des":"Data Studio provides a graphical interface which supports essential features of the database. This simplifies database development and application building tasks.Data Stu", "doc_type":"tg", "kw":"Overview,About Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_12.html", + "node_id":"en-us_topic_0000001233800651.xml", "product_code":"dws", "code":"13", "des":"This section describes the constraints and limitations for using Data Studio.The filter count and filtering status of the tree are not supported.If the SQL statement, DDL", "doc_type":"tg", "kw":"Constraints and Limitations,About Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Constraints and Limitations", "githuburl":"" }, { "uri":"DWS_DS_13.html", + "node_id":"en-us_topic_0000001233922187.xml", "product_code":"dws", "code":"14", "des":"The release package structure of Data Studio is as follows:", "doc_type":"tg", "kw":"Structure of a Release Package,About Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Structure of a Release Package", "githuburl":"" }, { "uri":"DWS_DS_14.html", + "node_id":"en-us_topic_0000001188362538.xml", "product_code":"dws", "code":"15", "des":"This section describes the minimum system requirements for using Data Studio.OSThe following table lists the OS requirements of Data Studio.BrowserThe following table lis", "doc_type":"tg", "kw":"System Requirements,About Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"System Requirements", "githuburl":"" }, { "uri":"DWS_DS_16.html", + "node_id":"en-us_topic_0000001188521096.xml", "product_code":"dws", "code":"16", "des":"This section describes the installation and configuration steps to use Data Studio. It also explains the steps to configure servers for debugging PL/SQL Functions.On the ", "doc_type":"tg", "kw":"Installing and Configuring Data Studio,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Installing and Configuring Data Studio", "githuburl":"" }, { "uri":"DWS_DS_19.html", + "node_id":"en-us_topic_0000001233922169.xml", "product_code":"dws", "code":"17", "des":"This section describes how to start Data Studio.The StartDataStudio.bat batch file checks the version of Operating System (OS), Java and Data Studio as a prerequisite to ", "doc_type":"tg", "kw":"Quick Start,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Quick Start", "githuburl":"" }, { "uri":"DWS_DS_20.html", + "node_id":"en-us_topic_0000001188521104.xml", "product_code":"dws", "code":"18", "des":"This section describes the Data Studio GUI.The Data Studio GUI contains the following:Main Menu provides basic operations.Toolbarcontains buttons for easy access to frequ", "doc_type":"tg", "kw":"Data Studio GUI,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Data Studio GUI", "githuburl":"" }, { "uri":"DWS_DS_21.html", + "node_id":"en-us_topic_0000001188680990.xml", "product_code":"dws", "code":"19", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Data Studio Menus", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Data Studio Menus", "githuburl":"" }, { "uri":"DWS_DS_22.html", + "node_id":"en-us_topic_0000001234042089.xml", "product_code":"dws", "code":"20", "des":"The Filemenu contains database connection options. Click File from main menu or press Alt+F to open the File menu.Follow the steps below to stop Data Studio:Alternatively", "doc_type":"tg", "kw":"File,Data Studio Menus,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"File", "githuburl":"" }, { "uri":"DWS_DS_23.html", + "node_id":"en-us_topic_0000001188362522.xml", "product_code":"dws", "code":"21", "des":"The Editmenu contains clipboard, Format, Find and Replace, andSearch Objectsoperations to use in the PL/SQL Viewer and SQL Terminal tab. Press Alt+E to open the Edit menu", "doc_type":"tg", "kw":"Edit,Data Studio Menus,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Edit", "githuburl":"" }, { "uri":"DWS_DS_24.html", + "node_id":"en-us_topic_0000001233922223.xml", "product_code":"dws", "code":"22", "des":"The Runmenu contains options to execute a database object in the PL/SQL Viewer tab and to execute SQL statements in the SQL Terminal tab. Press Alt+R to open the Run menu", "doc_type":"tg", "kw":"Run,Data Studio Menus,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Run", "githuburl":"" }, { "uri":"DWS_DS_25.html", + "node_id":"en-us_topic_0000001234042151.xml", "product_code":"dws", "code":"23", "des":"The Debugmenu contains debug operations in the PL/SQL Viewer and SQL Terminal tab. Press Alt+D to open the Debug menu.", "doc_type":"tg", "kw":"Debug,Data Studio Menus,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Debug", "githuburl":"" }, { "uri":"DWS_DS_26.html", + "node_id":"en-us_topic_0000001188202542.xml", "product_code":"dws", "code":"24", "des":"The Settingsmenu contains the option to change the language. Press Alt+G to open the Settings menu.", "doc_type":"tg", "kw":"Settings,Data Studio Menus,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Settings", "githuburl":"" }, { "uri":"DWS_DS_27.html", + "node_id":"en-us_topic_0000001188362534.xml", "product_code":"dws", "code":"25", "des":"The Helpmenu contains the user manual and version information of Data Studio. Press Alt+H to open the Help menu.Visit https://java.com/en/download/help/path.xml to set th", "doc_type":"tg", "kw":"Help,Data Studio Menus,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Help", "githuburl":"" }, { "uri":"DWS_DS_28.html", + "node_id":"en-us_topic_0000001233922201.xml", "product_code":"dws", "code":"26", "des":"The following image shows the toolbar:The toolbar contains the following operations:Adding a ConnectionRemoving a ConnectionConnecting to a DatabaseDisconnecting a Databa", "doc_type":"tg", "kw":"Data Studio Toolbar,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Data Studio Toolbar", "githuburl":"" }, { "uri":"DWS_DS_29.html", + "node_id":"en-us_topic_0000001188362536.xml", "product_code":"dws", "code":"27", "des":"This section describes the right-click menus of Data Studio.The following figure shows the Object Browser pane.Right-clicking the connection name allows you to select Ren", "doc_type":"tg", "kw":"Data Studio Right-Click Menus,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Data Studio Right-Click Menus", "githuburl":"" }, { "uri":"DWS_DS_32.html", + "node_id":"en-us_topic_0000001233800653.xml", "product_code":"dws", "code":"28", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Connection Profiles", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Connection Profiles", "githuburl":"" }, { "uri":"DWS_DS_33.html", + "node_id":"en-us_topic_0000001234042087.xml", "product_code":"dws", "code":"29", "des":"When Data Studio is started, the New Database Connection dialog box will open by default. To perform any DB operations, Data Studio must be connected to at least one data", "doc_type":"tg", "kw":"Overview,Connection Profiles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_34.html", + "node_id":"en-us_topic_0000001188521154.xml", "product_code":"dws", "code":"30", "des":"Performing the following steps to establish a new database connection.click on the toolbar, or press Ctrl+N to connect to the database. The New Database Connection dialo", "doc_type":"tg", "kw":"Adding a Connection,Connection Profiles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Adding a Connection", "githuburl":"" }, { "uri":"DWS_DS_35.html", + "node_id":"en-us_topic_0000001233800689.xml", "product_code":"dws", "code":"31", "des":"Follow the steps below to rename a database connection:A Rename Connection dialog box is displayed prompting you to provide the new name for the connection.The status bar", "doc_type":"tg", "kw":"Renaming a Connection,Connection Profiles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Renaming a Connection", "githuburl":"" }, { "uri":"DWS_DS_36.html", + "node_id":"en-us_topic_0000001233800713.xml", "product_code":"dws", "code":"32", "des":"Follow the steps below to edit the database connection properties:Editing an active connection will require closing the connection and then reopening the connection with ", "doc_type":"tg", "kw":"Editing a Connection,Connection Profiles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Editing a Connection", "githuburl":"" }, { "uri":"DWS_DS_37.html", + "node_id":"en-us_topic_0000001234042191.xml", "product_code":"dws", "code":"33", "des":"Follow the steps below to remove an existing database connection:A confirmation dialog box is displayed to remove the connection.The status bar displays the status of the", "doc_type":"tg", "kw":"Removing a Connection,Connection Profiles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Removing a Connection", "githuburl":"" }, { "uri":"DWS_DS_38.html", + "node_id":"en-us_topic_0000001233800737.xml", "product_code":"dws", "code":"34", "des":"Follow the steps below to view the properties of a connection:The status bar displays the status of the completed operation.Properties of the selected connection is displ", "doc_type":"tg", "kw":"Viewing Connection Properties,Connection Profiles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing Connection Properties", "githuburl":"" }, { "uri":"DWS_DS_39.html", + "node_id":"en-us_topic_0000001233800723.xml", "product_code":"dws", "code":"35", "des":"Follow the steps below to refresh the database connection:The status bar displays the status of the completed operation.The time taken to refresh the database depends on ", "doc_type":"tg", "kw":"Refreshing a Database Connection,Connection Profiles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Refreshing a Database Connection", "githuburl":"" }, { "uri":"DWS_DS_40.html", + "node_id":"en-us_topic_0000001188521168.xml", "product_code":"dws", "code":"36", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Databases", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Databases", "githuburl":"" }, { "uri":"DWS_DS_41.html", + "node_id":"en-us_topic_0000001233922161.xml", "product_code":"dws", "code":"37", "des":"A relational database is a database that has a set of tables which is manipulated in accordance with the relational model of data. It contains a set of data objects used ", "doc_type":"tg", "kw":"Creating a Database,Databases,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating a Database", "githuburl":"" }, { "uri":"DWS_DS_42.html", + "node_id":"en-us_topic_0000001234200579.xml", "product_code":"dws", "code":"38", "des":"You can disconnect all the databases from a connection.Follow the steps below to disconnect all the databases from a connection:This operation can be performed only when ", "doc_type":"tg", "kw":"Disconnecting All Databases,Databases,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Disconnecting All Databases", "githuburl":"" }, { "uri":"DWS_DS_43.html", + "node_id":"en-us_topic_0000001188362552.xml", "product_code":"dws", "code":"39", "des":"You can connect to the database.Follow the steps below to connect a database:This operation can be performed only on an inactive database.The database is connected.The st", "doc_type":"tg", "kw":"Connecting to a Database,Databases,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Connecting to a Database", "githuburl":"" }, { "uri":"DWS_DS_44.html", + "node_id":"en-us_topic_0000001234200657.xml", "product_code":"dws", "code":"40", "des":"You can disconnect the database.Follow the steps below to disconnect a database:This operation can be performed only on an active database.A confirmation dialog box is di", "doc_type":"tg", "kw":"Disconnecting a Database,Databases,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Disconnecting a Database", "githuburl":"" }, { "uri":"DWS_DS_45.html", + "node_id":"en-us_topic_0000001188681058.xml", "product_code":"dws", "code":"41", "des":"Follow the steps below to rename a database:This operation can be performed only on an inactive database.A Rename Database dialog box is displayed prompting you to provid", "doc_type":"tg", "kw":"Renaming a Database,Databases,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Renaming a Database", "githuburl":"" }, { "uri":"DWS_DS_46.html", + "node_id":"en-us_topic_0000001233800731.xml", "product_code":"dws", "code":"42", "des":"Individual or batch drop can be performed on databases. Refer to Dropping a Batch of Objects section for batch drop.Follow the steps below to drop a database:This operati", "doc_type":"tg", "kw":"Dropping a Database,Databases,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Dropping a Database", "githuburl":"" }, { "uri":"DWS_DS_47.html", + "node_id":"en-us_topic_0000001188202536.xml", "product_code":"dws", "code":"43", "des":"Follow the steps below to view the properties of a database:This operation can be performed only on an active database.The status bar displays the status of the completed", "doc_type":"tg", "kw":"Viewing Properties of a Database,Databases,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing Properties of a Database", "githuburl":"" }, { "uri":"DWS_DS_48.html", + "node_id":"en-us_topic_0000001234200609.xml", "product_code":"dws", "code":"44", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Schemas", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Schemas", "githuburl":"" }, { "uri":"DWS_DS_49.html", + "node_id":"en-us_topic_0000001234200683.xml", "product_code":"dws", "code":"45", "des":"This section describes working with database schemas. All system schemas are grouped under Catalogs and user schemas under Schemas.", "doc_type":"tg", "kw":"Overview,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_50.html", + "node_id":"en-us_topic_0000001188202546.xml", "product_code":"dws", "code":"46", "des":"In relational database technology, schemas provide a logical classification of objects in the database. Some of the objects that a schema may contain include functions/pr", "doc_type":"tg", "kw":"Creating a Schema,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating a Schema", "githuburl":"" }, { "uri":"DWS_DS_51.html", + "node_id":"en-us_topic_0000001233800745.xml", "product_code":"dws", "code":"47", "des":"Exporting the schema DDL exports the DDLs of functions/procedures, tables, sequences and views of the schema.Follow the steps to export the schema DDL:The Data Studio Sec", "doc_type":"tg", "kw":"Exporting Schema DDL,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Exporting Schema DDL", "githuburl":"" }, { "uri":"DWS_DS_52.html", + "node_id":"en-us_topic_0000001188681084.xml", "product_code":"dws", "code":"48", "des":"The exported schema DDL and data include the following:DDLs of functions/procedures of the schema.DDLs and data of tables of the schema.DDLs of views of the schema.DDLs o", "doc_type":"tg", "kw":"Exporting Schema DDL and Data,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Exporting Schema DDL and Data", "githuburl":"" }, { "uri":"DWS_DS_53.html", + "node_id":"en-us_topic_0000001188202598.xml", "product_code":"dws", "code":"49", "des":"Follow the steps to rename a schema:You can view the renamed schema in the Object Browser.The status bar displays the status of the completed operation.", "doc_type":"tg", "kw":"Renaming a Schema,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Renaming a Schema", "githuburl":"" }, { "uri":"DWS_DS_201.html", + "node_id":"en-us_topic_0000001234042201.xml", "product_code":"dws", "code":"50", "des":"Data Studio provides the option to show sequence DDL or allow users to export sequence DDL. It provides \"Show DDL\", \"Export DDL\", \"Export DDL and Data\"Follow the steps to", "doc_type":"tg", "kw":"Supporting Sequence DDL,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Supporting Sequence DDL", "githuburl":"" }, { "uri":"DWS_DS_54.html", + "node_id":"en-us_topic_0000001233800657.xml", "product_code":"dws", "code":"51", "des":"Follow the steps below to grant/revoke a privilege:The Grant/Revoke dialog is displayed.In SQL Preview tab, you can view the SQL query automatically generated for the inp", "doc_type":"tg", "kw":"Granting/Revoking a Privilege,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Granting/Revoking a Privilege", "githuburl":"" }, { "uri":"DWS_DS_55.html", + "node_id":"en-us_topic_0000001188362532.xml", "product_code":"dws", "code":"52", "des":"Individual or batch dropping can be performed on schemas. Refer to Dropping a Batch of Objects section for batch dropping.Follow the steps below to drop a schema:A confir", "doc_type":"tg", "kw":"Dropping a Schema,Schemas,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Dropping a Schema", "githuburl":"" }, { "uri":"DWS_DS_57.html", + "node_id":"en-us_topic_0000001233800753.xml", "product_code":"dws", "code":"53", "des":"Perform the following steps to create a function/procedure and SQL function:The selected template is displayed in the new tab of Data Studio.The Created function/procedur", "doc_type":"tg", "kw":"Creating a Function/Procedure,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating a Function/Procedure", "githuburl":"" }, { "uri":"DWS_DS_58.html", + "node_id":"en-us_topic_0000001188681048.xml", "product_code":"dws", "code":"54", "des":"Follow the steps below to open and edit the function/procedure or SQL function:The function/procedure or SQL function based on your selection is displayed.Only one functi", "doc_type":"tg", "kw":"Editing a Function/Procedure,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Editing a Function/Procedure", "githuburl":"" }, { "uri":"DWS_DS_59.html", + "node_id":"en-us_topic_0000001233922149.xml", "product_code":"dws", "code":"55", "des":"Perform the following steps to grant or revoke a permission:The Grant/Revoke dialog box is displayed.The Privilege Selection tab is displayed.The SQL Preview tab displays", "doc_type":"tg", "kw":"Granting/Revoking a Permission (Function/Procedure),Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Granting/Revoking a Permission (Function/Procedure)", "githuburl":"" }, { "uri":"DWS_DS_62.html", + "node_id":"en-us_topic_0000001233922213.xml", "product_code":"dws", "code":"56", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Debugging a PL/SQL Function", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Debugging a PL/SQL Function", "githuburl":"" }, { "uri":"DWS_DS_621.html", + "node_id":"en-us_topic_0000001188521056.xml", "product_code":"dws", "code":"57", "des":"During debugging, if the connection is lost but the database remains connected to Object Browser, the Connection Errordialog box is displayed with the following options:Y", "doc_type":"tg", "kw":"Overview,Debugging a PL/SQL Function,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_622.html", + "node_id":"en-us_topic_0000001188202610.xml", "product_code":"dws", "code":"58", "des":"This section contains the following topics:Using the Breakpoints PaneSetting or Adding Breakpoints on a RowEnabling or Disabling a Breakpoint on a RowRemoving a Breakpoin", "doc_type":"tg", "kw":"Using Breakpoints,Debugging a PL/SQL Function,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Using Breakpoints", "githuburl":"" }, { "uri":"DWS_DS_623.html", + "node_id":"en-us_topic_0000001188680998.xml", "product_code":"dws", "code":"59", "des":"This section contains the following topics:Starting DebuggingStepping Through a PL/SQL FunctionContinuing the Debug ExecutionViewing CallstackSelect the function that you", "doc_type":"tg", "kw":"Controlling Execution,Debugging a PL/SQL Function,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Controlling Execution", "githuburl":"" }, { "uri":"DWS_DS_624.html", + "node_id":"en-us_topic_0000001233800681.xml", "product_code":"dws", "code":"60", "des":"When you use Data Studio, you can examine debugging information through several debugging tabs. This section describes how to check the debugging information:Operating on", "doc_type":"tg", "kw":"Checking Debugging Information,Debugging a PL/SQL Function,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Checking Debugging Information", "githuburl":"" }, { "uri":"DWS_DS_60.html", + "node_id":"en-us_topic_0000001233800643.xml", "product_code":"dws", "code":"61", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Working with Functions/Procedures", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with Functions/Procedures", "githuburl":"" }, { "uri":"DWS_DS_61.html", + "node_id":"en-us_topic_0000001188521112.xml", "product_code":"dws", "code":"62", "des":"This section provides you with details on working with functions/procedures and SQL functions in Data Studio.Data Studio supports PL/pgSQL and SQL languages for the opera", "doc_type":"tg", "kw":"Overview,Working with Functions/Procedures,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_63.html", + "node_id":"en-us_topic_0000001234042115.xml", "product_code":"dws", "code":"63", "des":"Data Studio suggests a list of possible schema names, table names, column names, views, sequences, and functions in thePL/SQL Viewer.Follow the steps below to select a DB", "doc_type":"tg", "kw":"Selecting a DB Object in the PL/SQL Viewer,Working with Functions/Procedures,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Selecting a DB Object in the PL/SQL Viewer", "githuburl":"" }, { "uri":"DWS_DS_64.html", + "node_id":"en-us_topic_0000001188521072.xml", "product_code":"dws", "code":"64", "des":"Follow the steps below to export the function/procedure DDL:The Data Studio Security Disclaimer dialog box is displayed.The Save As dialog box is displayed.To cancel the ", "doc_type":"tg", "kw":"Exporting a Function/Procedure DDL,Working with Functions/Procedures,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Exporting a Function/Procedure DDL", "githuburl":"" }, { "uri":"DWS_DS_65.html", + "node_id":"en-us_topic_0000001188362616.xml", "product_code":"dws", "code":"65", "des":"Data Studio allows you to view table properties, procedures/functions and SQL functions.Follow the steps below to view table properties:The properties of the selected tab", "doc_type":"tg", "kw":"Viewing Object Properties in the PL/SQL Viewer,Working with Functions/Procedures,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing Object Properties in the PL/SQL Viewer", "githuburl":"" }, { "uri":"DWS_DS_66.html", + "node_id":"en-us_topic_0000001188680984.xml", "product_code":"dws", "code":"66", "des":"Individual or batch drop can be performed on functions/procedures. Refer to Dropping a Batch of Objects section for batch drop.Follow the steps below to drop a function/p", "doc_type":"tg", "kw":"Dropping a Function/Procedure,Working with Functions/Procedures,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Dropping a Function/Procedure", "githuburl":"" }, { "uri":"DWS_DS_67.html", + "node_id":"en-us_topic_0000001188362510.xml", "product_code":"dws", "code":"67", "des":"After you connect to the database, all the stored functions/procedures and tables will be automatically populated in the Object Browser pane. You can use Data Studio to e", "doc_type":"tg", "kw":"Executing a Function/Procedure,Working with Functions/Procedures,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Executing a Function/Procedure", "githuburl":"" }, { "uri":"DWS_DS_68.html", + "node_id":"en-us_topic_0000001234042107.xml", "product_code":"dws", "code":"68", "des":"Follow the steps below to grant/revoke a privilege:The Grant/Revoke dialog box is displayed.", "doc_type":"tg", "kw":"Granting/Revoking a Privilege,Working with Functions/Procedures,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Granting/Revoking a Privilege", "githuburl":"" }, { "uri":"DWS_DS_69.html", + "node_id":"en-us_topic_0000001188681080.xml", "product_code":"dws", "code":"69", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"GaussDB(DWS) Tables", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"GaussDB(DWS) Tables", "githuburl":"" }, { "uri":"DWS_DS_70.html", + "node_id":"en-us_topic_0000001188362526.xml", "product_code":"dws", "code":"70", "des":"This section describes how to manage tables efficiently.You need to configure all mandatory parameters to complete the operation. Mandatory parameters are marked with an ", "doc_type":"tg", "kw":"Table Management Overview,GaussDB(DWS) Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Table Management Overview", "githuburl":"" }, { "uri":"DWS_DS_71.html", + "node_id":"en-us_topic_0000001233800761.xml", "product_code":"dws", "code":"71", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Creating Regular Table", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating Regular Table", "githuburl":"" }, { "uri":"DWS_DS_72.html", + "node_id":"en-us_topic_0000001234200603.xml", "product_code":"dws", "code":"72", "des":"This section describes how to create a common table.A table is a logical structure maintained by a database administrator and consists of rows and columns. You can define", "doc_type":"tg", "kw":"Overview,Creating Regular Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_73.html", + "node_id":"en-us_topic_0000001188202570.xml", "product_code":"dws", "code":"73", "des":"After creating a table, you can add new columns in that table. You can also perform the following operations on the existing column only for a Regular table:Creating a Ne", "doc_type":"tg", "kw":"Working with Columns,Creating Regular Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with Columns", "githuburl":"" }, { "uri":"DWS_DS_74.html", + "node_id":"en-us_topic_0000001188521088.xml", "product_code":"dws", "code":"74", "des":"You can perform the following operations after a table is created only for a Regular table:Creating a ConstraintRenaming a ConstraintDropping a ConstraintFollow the steps", "doc_type":"tg", "kw":"Working with Constraints,Creating Regular Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with Constraints", "githuburl":"" }, { "uri":"DWS_DS_75.html", + "node_id":"en-us_topic_0000001188362546.xml", "product_code":"dws", "code":"75", "des":"You can create indexes in a table to search for data efficiently.After a table is created, you can add indexes to it. You can perform the following operations only in a c", "doc_type":"tg", "kw":"Managing Indexes,Creating Regular Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Managing Indexes", "githuburl":"" }, { "uri":"DWS_DS_76.html", + "node_id":"en-us_topic_0000001234042145.xml", "product_code":"dws", "code":"76", "des":"Foreign tables created using query execution in SQL Terminal or any other tool can be viewed in the Object browser after refresh.GDS Foreign table is denoted with icon b", "doc_type":"tg", "kw":"Creating Foreign Table,GaussDB(DWS) Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating Foreign Table", "githuburl":"" }, { "uri":"DWS_DS_77.html", + "node_id":"en-us_topic_0000001233922175.xml", "product_code":"dws", "code":"77", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Creating Partition Table", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating Partition Table", "githuburl":"" }, { "uri":"DWS_DS_78.html", + "node_id":"en-us_topic_0000001233922163.xml", "product_code":"dws", "code":"78", "des":"Partitioning refers to splitting what is logically one large table into smaller physical pieces based on specific schemes. The table based on the logic is called a partit", "doc_type":"tg", "kw":"Overview,Creating Partition Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_79.html", + "node_id":"en-us_topic_0000001188362578.xml", "product_code":"dws", "code":"79", "des":"After creating a table, you can add/modify partitions. You can also perform the following operations on an existing partition:Renaming a PartitionDropping a PartitionFoll", "doc_type":"tg", "kw":"Working with Partitions,Creating Partition Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with Partitions", "githuburl":"" }, { "uri":"DWS_DS_80.html", + "node_id":"en-us_topic_0000001234200591.xml", "product_code":"dws", "code":"80", "des":"Follow the steps below to grant/revoke a privilege:The Grant/Revoke dialog box is displayed.In the SQL Preview tab, you can view the SQL query automatically generated for", "doc_type":"tg", "kw":"Grant/Revoke Privilege - Regular/Partition Table,GaussDB(DWS) Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Grant/Revoke Privilege - Regular/Partition Table", "githuburl":"" }, { "uri":"DWS_DS_81.html", + "node_id":"en-us_topic_0000001233800751.xml", "product_code":"dws", "code":"81", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Managing Table", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Managing Table", "githuburl":"" }, { "uri":"DWS_DS_82.html", + "node_id":"en-us_topic_0000001188202566.xml", "product_code":"dws", "code":"82", "des":"This section describes how to manage tables efficiently.You need to configure all mandatory parameters to complete the operation. Mandatory parameters are marked with ast", "doc_type":"tg", "kw":"Overview,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_83.html", + "node_id":"en-us_topic_0000001188202534.xml", "product_code":"dws", "code":"83", "des":"Follow the steps below to rename a table:The Rename Table dialog box is displayed prompting you to provide the new name.Data Studio displays the status of the operation i", "doc_type":"tg", "kw":"Renaming a Table,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Renaming a Table", "githuburl":"" }, { "uri":"DWS_DS_84.html", + "node_id":"en-us_topic_0000001188521080.xml", "product_code":"dws", "code":"84", "des":"Follow the steps below to truncate a table:Data Studio prompts you to confirm this operation.A popup message and status bar display the status of the completed operation.", "doc_type":"tg", "kw":"Truncating a Table,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Truncating a Table", "githuburl":"" }, { "uri":"DWS_DS_85.html", + "node_id":"en-us_topic_0000001188521078.xml", "product_code":"dws", "code":"85", "des":"Index facilitate lookup of records. You need to reindex tables in the following scenarios:The index is corrupted and no longer contains valid data. Although in theory thi", "doc_type":"tg", "kw":"Reindexing a Table,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Reindexing a Table", "githuburl":"" }, { "uri":"DWS_DS_86.html", + "node_id":"en-us_topic_0000001188362590.xml", "product_code":"dws", "code":"86", "des":"The analyzing table operation collects statistics about tables and table indicies and stores the collected information in internal tables of the database where the query ", "doc_type":"tg", "kw":"Analyzing a Table,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Analyzing a Table", "githuburl":"" }, { "uri":"DWS_DS_87.html", + "node_id":"en-us_topic_0000001234042113.xml", "product_code":"dws", "code":"87", "des":"Vacuuming table operation reclaims space and makes it available for re-use.Follow the steps below to vacuum the table:The Vacuum Table message and status bar display the ", "doc_type":"tg", "kw":"Vacuuming a Table,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Vacuuming a Table", "githuburl":"" }, { "uri":"DWS_DS_88.html", + "node_id":"en-us_topic_0000001188202572.xml", "product_code":"dws", "code":"88", "des":"Follow the steps below to set the description of a table:The Update Table Description dialog box is displayed. It prompts you to set the table description.The status bar ", "doc_type":"tg", "kw":"Setting the Table Description,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Setting the Table Description", "githuburl":"" }, { "uri":"DWS_DS_90.html", + "node_id":"en-us_topic_0000001188362518.xml", "product_code":"dws", "code":"89", "des":"Follow the steps below to set a schema:The Set Schema dialog box is displayed, prompting you to select the new schema for the selected table.The status bar displays the s", "doc_type":"tg", "kw":"Setting the Schema,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Setting the Schema", "githuburl":"" }, { "uri":"DWS_DS_91.html", + "node_id":"en-us_topic_0000001188362504.xml", "product_code":"dws", "code":"90", "des":"Individual or batch dropping can be performed on tables. Refer to Dropping a Batch of Objects section for batch dropping.This operation removes the complete table structu", "doc_type":"tg", "kw":"Dropping a Table,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Dropping a Table", "githuburl":"" }, { "uri":"DWS_DS_92.html", + "node_id":"en-us_topic_0000001234200673.xml", "product_code":"dws", "code":"91", "des":"Perform the following operations to view the table properties:Data Studio displays the properties (General, Columns, Constraints, and Index) of the selected table in diff", "doc_type":"tg", "kw":"Viewing Table Properties,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing Table Properties", "githuburl":"" }, { "uri":"DWS_DS_93.html", + "node_id":"en-us_topic_0000001233922151.xml", "product_code":"dws", "code":"92", "des":"Follow the steps below to grant/revoke a privilege:The Grant/Revoke dialog is displayed.", "doc_type":"tg", "kw":"Grant/Revoke Privilege,Managing Table,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Grant/Revoke Privilege", "githuburl":"" }, { "uri":"DWS_DS_94.html", + "node_id":"en-us_topic_0000001188521098.xml", "product_code":"dws", "code":"93", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Managing Table Data", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Managing Table Data", "githuburl":"" }, { "uri":"DWS_DS_95.html", + "node_id":"en-us_topic_0000001188202638.xml", "product_code":"dws", "code":"94", "des":"This section describes how to manage table data.", "doc_type":"tg", "kw":"Overview,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_96.html", + "node_id":"en-us_topic_0000001188521108.xml", "product_code":"dws", "code":"95", "des":"Follow the steps below to export the table DDL:The Data Studio Security Disclaimer dialog box is displayed.The Save As dialog box is displayed.To cancel the export operat", "doc_type":"tg", "kw":"Exporting Table DDL,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Exporting Table DDL", "githuburl":"" }, { "uri":"DWS_DS_97.html", + "node_id":"en-us_topic_0000001233800663.xml", "product_code":"dws", "code":"96", "des":"The exported table DDL and data include the following:DDL of the table.Columns and rows of the table.Follow the steps below to export the table DDL:The Data Studio Securi", "doc_type":"tg", "kw":"Exporting Table DDL and Data,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Exporting Table DDL and Data", "githuburl":"" }, { "uri":"DWS_DS_98.html", + "node_id":"en-us_topic_0000001188521136.xml", "product_code":"dws", "code":"97", "des":"Perform the following steps to export table data:The Export Table Datadialog box is displayed with the following options:Format: Table data can be exported in Excel (xlsx", "doc_type":"tg", "kw":"Exporting Table Data,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Exporting Table Data", "githuburl":"" }, { "uri":"DWS_DS_99.html", + "node_id":"en-us_topic_0000001234042205.xml", "product_code":"dws", "code":"98", "des":"To display a DDL query for a table, perform the following steps:Data Studio displays the DDL of the selected table.A new terminal window is opened each time you select to", "doc_type":"tg", "kw":"Show DDL,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Show DDL", "githuburl":"" }, { "uri":"DWS_DS_100.html", + "node_id":"en-us_topic_0000001188680976.xml", "product_code":"dws", "code":"99", "des":"Prerequisites:If the definition of the source file does not match that of the destination table, modify the properties of the destination table in the Import Table Data d", "doc_type":"tg", "kw":"Importing Table Data,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Importing Table Data", "githuburl":"" }, { "uri":"DWS_DS_101.html", + "node_id":"en-us_topic_0000001234200597.xml", "product_code":"dws", "code":"100", "des":"Follow the steps to view table data:The View Table Data tab is displayed where you can view the table data information.Toolbar menu in the View Table Data window:Icons in", "doc_type":"tg", "kw":"Viewing Table Data,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing Table Data", "githuburl":"" }, { "uri":"DWS_DS_102.html", + "node_id":"en-us_topic_0000001233800701.xml", "product_code":"dws", "code":"101", "des":"Follow the steps below to edit table data:The Edit Table data tab is displayed.Refer to Viewing Table Data for description on copy and search toolbar options.Data Studio ", "doc_type":"tg", "kw":"Editing Table Data,Managing Table Data,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Editing Table Data", "githuburl":"" }, { "uri":"DWS_DS_103.html", + "node_id":"en-us_topic_0000001234042149.xml", "product_code":"dws", "code":"102", "des":"Data Studio allows you to edit temporary tables. Temporary tables are deleted automatically when you close the connection that was used to create the table.Ensure that co", "doc_type":"tg", "kw":"Editing Temporary Tables,GaussDB(DWS) Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Editing Temporary Tables", "githuburl":"" }, { "uri":"DWS_DS_104.html", + "node_id":"en-us_topic_0000001188521138.xml", "product_code":"dws", "code":"103", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Sequences", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Sequences", "githuburl":"" }, { "uri":"DWS_DS_105.html", + "node_id":"en-us_topic_0000001233922155.xml", "product_code":"dws", "code":"104", "des":"Follow the steps below to create a sequence:The Create New Sequence dialog box is displayed.Enter a name in the Sequence Name field.Select theCase check box to retain the", "doc_type":"tg", "kw":"Creating Sequence,Sequences,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating Sequence", "githuburl":"" }, { "uri":"DWS_DS_106.html", + "node_id":"en-us_topic_0000001188681038.xml", "product_code":"dws", "code":"105", "des":"Follow the steps below to grant/revoke a privilege:The Grant/Revoke dialog is displayed.In the SQL Preview tab, you can view the SQL query automatically generated for the", "doc_type":"tg", "kw":"Grant/Revoke Privilege,Sequences,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Grant/Revoke Privilege", "githuburl":"" }, { "uri":"DWS_DS_107.html", + "node_id":"en-us_topic_0000001233800647.xml", "product_code":"dws", "code":"106", "des":"You can perform the following operations on an existing sequence:Granting/Revoking a PrivilegeDropping a SequenceDropping a Sequence CascadeIndividual or batch dropping c", "doc_type":"tg", "kw":"Working with Sequences,Sequences,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with Sequences", "githuburl":"" }, { "uri":"DWS_DS_108.html", + "node_id":"en-us_topic_0000001233922181.xml", "product_code":"dws", "code":"107", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Views", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Views", "githuburl":"" }, { "uri":"DWS_DS_109.html", + "node_id":"en-us_topic_0000001234042187.xml", "product_code":"dws", "code":"108", "des":"Follow the steps below to create a new view:The DDL template for the view is displayed in the SQL Terminal tab.You can view the new view in the Object Browser.The status ", "doc_type":"tg", "kw":"Creating a View,Views,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating a View", "githuburl":"" }, { "uri":"DWS_DS_110.html", + "node_id":"en-us_topic_0000001234200689.xml", "product_code":"dws", "code":"109", "des":"Follow the steps below to grant/revoke a privilege:The Grant/Revoke dialog box is displayed.In the SQL Preview tab, you can view the SQL query automatically generated for", "doc_type":"tg", "kw":"Granting/Revoking a Privilege,Views,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Granting/Revoking a Privilege", "githuburl":"" }, { "uri":"DWS_DS_111.html", + "node_id":"en-us_topic_0000001233800703.xml", "product_code":"dws", "code":"110", "des":"Views can be created to restrict access to specific rows or columns of a table. A view can be created from one or more tables and is determined by the query used to creat", "doc_type":"tg", "kw":"Working with Views,Views,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with Views", "githuburl":"" }, { "uri":"DWS_DS_115.html", + "node_id":"en-us_topic_0000001234200687.xml", "product_code":"dws", "code":"111", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Users/Roles", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Users/Roles", "githuburl":"" }, { "uri":"DWS_DS_116.html", + "node_id":"en-us_topic_0000001188202538.xml", "product_code":"dws", "code":"112", "des":"A database is used by many users, and the users are grouped for management convenience. A database role can be one or a group of database users.Users and roles have simil", "doc_type":"tg", "kw":"Creating a User/Role,Users/Roles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating a User/Role", "githuburl":"" }, { "uri":"DWS_DS_117.html", + "node_id":"en-us_topic_0000001234200577.xml", "product_code":"dws", "code":"113", "des":"You can perform the following operations on an existing user/role:Dropping a User/RoleViewing/Editing User/Role PropertiesViewing the User/Role DDLFollow the steps below ", "doc_type":"tg", "kw":"Working with Users/Roles,Users/Roles,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with Users/Roles", "githuburl":"" }, { "uri":"DWS_DS_118.html", + "node_id":"en-us_topic_0000001233800679.xml", "product_code":"dws", "code":"114", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"SQL Terminal", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"SQL Terminal", "githuburl":"" }, { "uri":"DWS_DS_119.html", + "node_id":"en-us_topic_0000001233800741.xml", "product_code":"dws", "code":"115", "des":"You can open multiple SQL Terminal tabs in Data Studio to execute multiple SQL statements for query in the current SQL Terminal tab. Perform the following steps to open a", "doc_type":"tg", "kw":"Opening Multiple SQL Terminal Tabs,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Opening Multiple SQL Terminal Tabs", "githuburl":"" }, { "uri":"DWS_DS_120.html", + "node_id":"en-us_topic_0000001188521134.xml", "product_code":"dws", "code":"116", "des":"Data Studio allows viewing and managing frequently used SQL queries. The history of executed SQL queries is maintained only for the SQL Terminal.Follow the steps to view ", "doc_type":"tg", "kw":"Managing the SQL Query Execution History,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Managing the SQL Query Execution History", "githuburl":"" }, { "uri":"DWS_DS_121.html", + "node_id":"en-us_topic_0000001188521062.xml", "product_code":"dws", "code":"117", "des":"Follow the steps to open an SQL script:If the SQL Terminal has existing content, then there will be an option to overwrite the existing content or append content to it.Th", "doc_type":"tg", "kw":"Opening and Saving SQL Scripts,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Opening and Saving SQL Scripts", "githuburl":"" }, { "uri":"DWS_DS_122.html", + "node_id":"en-us_topic_0000001188680986.xml", "product_code":"dws", "code":"118", "des":"Data Studio allows you to view table properties and functions/procedures.Follow the steps to view table properties:The table properties are read-only.Follow the steps to ", "doc_type":"tg", "kw":"Viewing Object Properties in the SQL Terminal,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing Object Properties in the SQL Terminal", "githuburl":"" }, { "uri":"DWS_DS_123.html", + "node_id":"en-us_topic_0000001188681012.xml", "product_code":"dws", "code":"119", "des":"Data Studio allows you to cancel the execution of an SQL query being executed in the SQL Terminal.Follow the steps to cancel execution of an SQL query:Alternatively, you", "doc_type":"tg", "kw":"Canceling the Execution of SQL Queries,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Canceling the Execution of SQL Queries", "githuburl":"" }, { "uri":"DWS_DS_124.html", + "node_id":"en-us_topic_0000001188521090.xml", "product_code":"dws", "code":"120", "des":"Data Studio supports formatting and highlighting of SQL queries and PL/SQL statements.Follow the steps to format PL/SQL statements:Alternatively, use the key combination ", "doc_type":"tg", "kw":"Formatting of SQL Queries,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Formatting of SQL Queries", "githuburl":"" }, { "uri":"DWS_DS_125.html", + "node_id":"en-us_topic_0000001233922141.xml", "product_code":"dws", "code":"121", "des":"Data Studio suggests a list of possible schema names, table names and column names, and views in theSQL Terminal.Follow the steps below to select a DB object:On selection", "doc_type":"tg", "kw":"Selecting a DB Object in the SQL Terminal,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Selecting a DB Object in the SQL Terminal", "githuburl":"" }, { "uri":"DWS_DS_126.html", + "node_id":"en-us_topic_0000001188362512.xml", "product_code":"dws", "code":"122", "des":"The execution plan shows how the table(s) referenced by the SQL statement will be scanned (plain sequential scan and index scan).The SQL statement execution cost is the e", "doc_type":"tg", "kw":"Viewing the Query Execution Plan and Cost,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing the Query Execution Plan and Cost", "githuburl":"" }, { "uri":"DWS_DS_127.html", + "node_id":"en-us_topic_0000001234042185.xml", "product_code":"dws", "code":"123", "des":"Visual Explain plan displays a graphical representation of the SQL query using information from the extended JSON format. This helps to refine query to enhance query and ", "doc_type":"tg", "kw":"Viewing the Query Execution Plan and Cost Graphically,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Viewing the Query Execution Plan and Cost Graphically", "githuburl":"" }, { "uri":"DWS_DS_128.html", + "node_id":"en-us_topic_0000001234200573.xml", "product_code":"dws", "code":"124", "des":"In SQL Terminal, you canAutomatically Commit a TransactionExecute SQL QueriesMulti-Column SortBackuping Unsaved Queries/Functions/ProceduresError LocatorSearch in PL/SQL ", "doc_type":"tg", "kw":"Working with SQL Terminals,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Working with SQL Terminals", "githuburl":"" }, { "uri":"DWS_DS_129.html", + "node_id":"en-us_topic_0000001188680978.xml", "product_code":"dws", "code":"125", "des":"You can export the results of an SQL query into a CSV, Text or Binary file.This section contains the following topics:Exporting all dataExporting Data On the Current Page", "doc_type":"tg", "kw":"Exporting Query Results,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Exporting Query Results", "githuburl":"" }, { "uri":"DWS_DS_130.html", + "node_id":"en-us_topic_0000001234042141.xml", "product_code":"dws", "code":"126", "des":"Data Studio allows you to reuse an existing SQL Terminal connection or create a new SQL Terminal connection for execution plan and cost, visual explain plan, and operatio", "doc_type":"tg", "kw":"Managing SQL Terminal Connections,SQL Terminal,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Managing SQL Terminal Connections", "githuburl":"" }, { "uri":"DWS_DS_131.html", + "node_id":"en-us_topic_0000001234042129.xml", "product_code":"dws", "code":"127", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Batch Operation", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Batch Operation", "githuburl":"" }, { "uri":"DWS_DS_132.html", + "node_id":"en-us_topic_0000001188521094.xml", "product_code":"dws", "code":"128", "des":"You can view accessible database objects in the navigation tree in Object Browser. Schema are displayed under databases, and tables are displayed under schemas.Object Bro", "doc_type":"tg", "kw":"Overview,Batch Operation,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_133.html", + "node_id":"en-us_topic_0000001234200613.xml", "product_code":"dws", "code":"129", "des":"The batch drop operation allows you select multiple objects to drop. You can also perform batch drop operation on searched objects.Batch drop is allowed only within a dat", "doc_type":"tg", "kw":"Dropping a Batch of Objects,Batch Operation,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Dropping a Batch of Objects", "githuburl":"" }, { "uri":"DWS_DS_134.html", + "node_id":"en-us_topic_0000001188202544.xml", "product_code":"dws", "code":"130", "des":"The batch grant/revoke operation allows you select multiple objects to grant/revoke privileges. You can also perform batch grant/revoke operation on searched objects.This", "doc_type":"tg", "kw":"Granting/Revoking Privileges,Batch Operation,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Granting/Revoking Privileges", "githuburl":"" }, { "uri":"DWS_DS_135.html", + "node_id":"en-us_topic_0000001188202634.xml", "product_code":"dws", "code":"131", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Personalizing Data Studio", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Personalizing Data Studio", "githuburl":"" }, { "uri":"DWS_DS_137.html", + "node_id":"en-us_topic_0000001234042091.xml", "product_code":"dws", "code":"132", "des":"This section provides details on how to customize shortcut keys.You can customize the Data Studio shortcut keys as required.Follow the steps below to set or modify the sh", "doc_type":"tg", "kw":"General,Personalizing Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"General", "githuburl":"" }, { "uri":"DWS_DS_138.html", + "node_id":"en-us_topic_0000001188521052.xml", "product_code":"dws", "code":"133", "des":"This section provides details on how to personalize syntax coloring, SQL history information, templates, and formatter.Follow the steps to customize the SQL highlight col", "doc_type":"tg", "kw":"Editor,Personalizing Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Editor", "githuburl":"" }, { "uri":"DWS_DS_139.html", + "node_id":"en-us_topic_0000001234200631.xml", "product_code":"dws", "code":"134", "des":"Follow the steps to set Data Studio and file encoding:The Preferences dialog box is displayed.The Session Setting pane is displayed.Data Studio supports only UTF-8 and GB", "doc_type":"tg", "kw":"Environment,Personalizing Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Environment", "githuburl":"" }, { "uri":"DWS_DS_141.html", + "node_id":"en-us_topic_0000001188202558.xml", "product_code":"dws", "code":"135", "des":"This section provides details on how to personalize the column width, number of records to be fetched in the query results, and result copy of column header or row number", "doc_type":"tg", "kw":"Result Management,Personalizing Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Result Management", "githuburl":"" }, { "uri":"DWS_DS_142.html", + "node_id":"en-us_topic_0000001234042179.xml", "product_code":"dws", "code":"136", "des":"This section provides details on how to personalize password and security disclaimer display.You can enable/disable to display the permanent option to save password in th", "doc_type":"tg", "kw":"Security,Personalizing Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Security", "githuburl":"" }, { "uri":"DWS_DS_144.html", + "node_id":"en-us_topic_0000001234200679.xml", "product_code":"dws", "code":"137", "des":"The loading and operation performance of Data Studio depends on the number of objects to be loaded in Object Browser, including tables, views, and columns.Memory consumpt", "doc_type":"tg", "kw":"Performance Specifications,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Performance Specifications", "githuburl":"" }, { "uri":"DWS_DS_146.html", + "node_id":"en-us_topic_0000001233922177.xml", "product_code":"dws", "code":"138", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Security Management", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Security Management", "githuburl":"" }, { "uri":"DWS_DS_147.html", + "node_id":"en-us_topic_0000001233800685.xml", "product_code":"dws", "code":"139", "des":"Ensure that the operating system and the required software's (refer to System Requirements for more details) are updated with the latest patches to prevent vulnerabilitie", "doc_type":"tg", "kw":"Overview,Security Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"DWS_DS_148.html", + "node_id":"en-us_topic_0000001188680974.xml", "product_code":"dws", "code":"140", "des":"The following information is critical to the security management for Data Studio:When you log into a database, Data Studio displays a pop-up with details of the last succ", "doc_type":"tg", "kw":"Login History,Security Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Login History", "githuburl":"" }, { "uri":"DWS_DS_149.html", + "node_id":"en-us_topic_0000001233922215.xml", "product_code":"dws", "code":"141", "des":"The following information is critical to manage security for Data Studio:Your password will expire within 7 days from the date of notification. If the password expires, c", "doc_type":"tg", "kw":"Password Expiry Notification,Security Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Password Expiry Notification", "githuburl":"" }, { "uri":"DWS_DS_151.html", + "node_id":"en-us_topic_0000001233800659.xml", "product_code":"dws", "code":"142", "des":"The following information is critical to manage security for Data Studio:While running Data Studio in a trusted environment, user must ensure to prevent malicious softwar", "doc_type":"tg", "kw":"Securing the Application In-Memory Data,Security Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Securing the Application In-Memory Data", "githuburl":"" }, { "uri":"DWS_DS_152.html", + "node_id":"en-us_topic_0000001233800743.xml", "product_code":"dws", "code":"143", "des":"The following information is critical to manage security for Data Studio:You can ensure encryption of auto saved data by enabling encryption option from Preferences page.", "doc_type":"tg", "kw":"Data Encryption for Saved Data,Security Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Data Encryption for Saved Data", "githuburl":"" }, { "uri":"DWS_DS_153.html", + "node_id":"en-us_topic_0000001188521114.xml", "product_code":"dws", "code":"144", "des":"The following information is critical to manage security for Data Studio:SQL History scripts are not encrypted.The SQL History list does not display sensitive queries tha", "doc_type":"tg", "kw":"SQL History,Security Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"SQL History", "githuburl":"" }, { "uri":"DWS_DS_154.html", + "node_id":"en-us_topic_0000001233800747.xml", "product_code":"dws", "code":"145", "des":"The information on using SSL certificates is for reference only. For details on the certificates and for security guidelines for managing the certificates and related fil", "doc_type":"tg", "kw":"SSL Certificates,Security Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"SSL Certificates", "githuburl":"" }, { "uri":"DWS_DS_145.html", + "node_id":"en-us_topic_0000001188362524.xml", "product_code":"dws", "code":"146", "des":"Data Studio does not open.Solution: Check whether JRE is missing. Verify the Java path in the environment. For details about the supported Java JDK versions, see System R", "doc_type":"tg", "kw":"Troubleshooting,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Troubleshooting", "githuburl":"" }, { "uri":"DWS_DS_155.html", + "node_id":"en-us_topic_0000001188681066.xml", "product_code":"dws", "code":"147", "des":"What do I need to check if my connection fails?Answer: Check the following items:Check whether Connection Properties are properly configured.Check whether the server vers", "doc_type":"tg", "kw":"FAQs,Data Studio,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"FAQs", "githuburl":"" }, { "uri":"dws_gds_index.html", + "node_id":"en-us_topic_0000001188521102.xml", "product_code":"dws", "code":"148", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"GDS", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"GDS", "githuburl":"" }, { "uri":"dws_07_0759.html", + "node_id":"en-us_topic_0000001503363660.xml", "product_code":"dws", "code":"149", "des":"GaussDB(DWS) uses GDS to allocate the source data for parallel data import. Deploy GDS on the data server.If a large volume of data is stored on multiple data servers, in", "doc_type":"tg", "kw":"Installing, Configuring, and Starting GDS,GDS,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Installing, Configuring, and Starting GDS", "githuburl":"" }, { "uri":"dws_07_0128.html", + "node_id":"en-us_topic_0000001503523556.xml", "product_code":"dws", "code":"150", "des":"Stop GDS after data is imported successfully.If GDS is started using the gds command, perform the following operations to stop GDS:Query the GDS process ID:ps -ef|grep gd", "doc_type":"tg", "kw":"Stopping GDS,GDS,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Stopping GDS", "githuburl":"" }, { "uri":"dws_07_0692.html", + "node_id":"en-us_topic_0000001188202652.xml", "product_code":"dws", "code":"151", "des":"The data servers reside on the same intranet as the cluster. Their IP addresses are 192.168.0.90 and 192.168.0.91. Source data files are in CSV format.Create the target t", "doc_type":"tg", "kw":"Example of Importing Data Using GDS,GDS,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Example of Importing Data Using GDS", "githuburl":"" }, { "uri":"gds_cmd_reference.html", + "node_id":"en-us_topic_0000001188202560.xml", "product_code":"dws", "code":"152", "des":"gds is used to import and export data of GaussDB(DWS). For details, see \"Importing Data\" and \"Exporting Data\" in the Developer Guide.The -d and -H parameters are mandator", "doc_type":"tg", "kw":"gds,GDS,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gds", "githuburl":"" }, { "uri":"dws_07_0129.html", + "node_id":"en-us_topic_0000001233922183.xml", "product_code":"dws", "code":"153", "des":"gds_ctl.py can be used to start and stop gds if gds.conf has been configured.Run the following commands on Linux OS: You need to ensure that the directory structure is as", "doc_type":"tg", "kw":"gds_ctl.py,GDS,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gds_ctl.py", "githuburl":"" }, { "uri":"dws_07_0056.html", + "node_id":"en-us_topic_0000001188681008.xml", "product_code":"dws", "code":"154", "des":"Handle errors that occurred during data import.Errors that occur when data is imported are divided into data format errors and non-data format errors.Data format errorWhe", "doc_type":"tg", "kw":"Handling Import Errors,GDS,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Handling Import Errors", "githuburl":"" }, { "uri":"dws_mt_index.html", + "node_id":"en-us_topic_0000001772696040.xml", "product_code":"dws", "code":"155", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"DSC", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"DSC", "githuburl":"" }, { - "uri":"mt_tool_index.html", + "uri":"dws_16_0001.html", + "node_id":"en-us_topic_0000001772536368.xml", "product_code":"dws", "code":"156", - "des":"After switching to GaussDB(DWS) databases, you may need to migrate user data and application SQL scripts to new databases. In particular,the migration of application SQL ", - "doc_type":"tg", - "kw":"Overview,DSC,Tool Guide", - "title":"Overview", - "githuburl":"" - }, - { - "uri":"dws_mt_0015.html", - "product_code":"dws", - "code":"157", - "des":"This section provides the system context of DSC. DSC is a CLI tool that helps data migration engineers migrate scripts of source databases, such as Teradata, Oracle, Nete", - "doc_type":"tg", - "kw":"Supported Keywords and Features,DSC,Tool Guide", - "title":"Supported Keywords and Features", - "githuburl":"" - }, - { - "uri":"dws_mt_0012.html", - "product_code":"dws", - "code":"158", - "des":"This section describes the constraints and limitations of DSC.DSC is used only for syntax migration and not for data migration.If the SELECT clause of a subquery contains", - "doc_type":"tg", - "kw":"Constraints and Limitations,DSC,Tool Guide", - "title":"Constraints and Limitations", - "githuburl":"" - }, - { - "uri":"dws_mt_0014.html", - "product_code":"dws", - "code":"159", - "des":"Table 1 lists the source databases supported by DSC.OS requirementsTable 2 lists the operating systems compatible with DSC.Other software requirementsTable 3 lists the re", - "doc_type":"tg", - "kw":"System Requirements,DSC,Tool Guide", - "title":"System Requirements", - "githuburl":"" - }, - { - "uri":"dws_mt_0021.html", - "product_code":"dws", - "code":"160", - "des":"Before using DSC, install it on a Linux or Windows server. DSC supports 64-bit Linux OSs. For details about other OSs supported by DSC, see Compatible OSs.In Linux, do no", - "doc_type":"tg", - "kw":"Installing DSC,DSC,Tool Guide", - "title":"Installing DSC", - "githuburl":"" - }, - { - "uri":"dws_mt_0023.html", - "product_code":"dws", - "code":"161", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", - "kw":"Configuring DSC", - "title":"Configuring DSC", + "kw":"About This Document", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"About This Document", "githuburl":"" }, { - "uri":"dws_mt_0024.html", + "uri":"dws_16_0002.html", + "node_id":"en-us_topic_0000001819416073.xml", "product_code":"dws", - "code":"162", - "des":"DSC provides configuration files and parameters to configure migration logic and rules. Before migrating scripts, you need to configure the following as required:Tool con", + "code":"157", + "des":"This document is intended for the following DSC users:Database migration engineersDatabase administratorsTechnical support engineersDSC users need to have a basic knowled", "doc_type":"tg", - "kw":"Overview,Configuring DSC,Tool Guide", + "kw":"Intended Audience,About This Document,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Intended Audience", + "githuburl":"" + }, + { + "uri":"dws_16_0003.html", + "node_id":"en-us_topic_0000001819336045.xml", + "product_code":"dws", + "code":"158", + "des":"This section describes the content, symbol, and command conventions of this document.The purchased products, services, and features are subject to the signed contract. Al", + "doc_type":"tg", + "kw":"Document Conventions,About This Document,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Document Conventions", + "githuburl":"" + }, + { + "uri":"dws_16_0005.html", + "node_id":"en-us_topic_0000001772536372.xml", + "product_code":"dws", + "code":"159", + "des":"This section lists the applicable third-party licenses.ANTLR v4.9.3Apache Commons IO 2.11Apache Commons CLI 1.5Apache Log4j 2.17.2JSON.org json 20220320postgresql 42.4.1s", + "doc_type":"tg", + "kw":"Third-party Licenses,About This Document,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Third-party Licenses", + "githuburl":"" + }, + { + "uri":"dws_16_0006.html", + "node_id":"en-us_topic_0000001819416077.xml", + "product_code":"dws", + "code":"160", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Introduction to DSC", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Introduction to DSC", + "githuburl":"" + }, + { + "uri":"mt_tool_index.html", + "node_id":"en-us_topic_0000001819336049.xml", + "product_code":"dws", + "code":"161", + "des":"After switching to GaussDB(DWS) databases, you may need to migrate user data and application SQL scripts to new databases. In particular,the migration of application SQL ", + "doc_type":"tg", + "kw":"Overview,Introduction to DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Overview", "githuburl":"" }, { - "uri":"dws_mt_0025.html", + "uri":"dws_16_0008.html", + "node_id":"en-us_topic_0000001772696052.xml", + "product_code":"dws", + "code":"162", + "des":"The following table lists the source databases supported by DSC.The following table lists the destination databases supported by DSC.Table 3 lists the hardware requiremen", + "doc_type":"tg", + "kw":"Operating Environment,Introduction to DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Operating Environment", + "githuburl":"" + }, + { + "uri":"dws_16_0009.html", + "node_id":"en-us_topic_0000001772536376.xml", "product_code":"dws", "code":"163", - "des":"Configure the following items:Setting application.properties: Configure the migration behavior of DSC, for example, whether to overwrite the files in the target folder an", - "doc_type":"tg", - "kw":"DSC Configuration,Configuring DSC,Tool Guide", - "title":"DSC Configuration", - "githuburl":"" - }, - { - "uri":"dws_mt_0026.html", - "product_code":"dws", - "code":"164", - "des":"Teradata parameters are used to customize rules for Teradata script migration.Open the features-teradata.properties file in the config folder and set the parameters in Ta", - "doc_type":"tg", - "kw":"Teradata SQL Configuration,Configuring DSC,Tool Guide", - "title":"Teradata SQL Configuration", - "githuburl":"" - }, - { - "uri":"dws_mt_0027.html", - "product_code":"dws", - "code":"165", - "des":"Oracle parameters are used to customize rules for Oracle script migration.Open the features-oracle.properties file in the config folder and set parameters in Table 1 as n", - "doc_type":"tg", - "kw":"Oracle SQL Configuration,Configuring DSC,Tool Guide", - "title":"Oracle SQL Configuration", - "githuburl":"" - }, - { - "uri":"dws_mt_0029.html", - "product_code":"dws", - "code":"166", - "des":"Teradata Perl parameters are used to customize rules for Teradata Perl script migration.Open the perl-migration.properties file in the config folder and set parameters in", - "doc_type":"tg", - "kw":"Teradata Perl Configuration,Configuring DSC,Tool Guide", - "title":"Teradata Perl Configuration", - "githuburl":"" - }, - { - "uri":"dws_07_0666.html", - "product_code":"dws", - "code":"167", - "des":"MySQL parameters are used to customize rules for MySQL script migration.Open the features-mysql.properties file in the config folder and configure parameters in the featu", - "doc_type":"tg", - "kw":"MySQL SQL Configuration,Configuring DSC,Tool Guide", - "title":"MySQL SQL Configuration", - "githuburl":"" - }, - { - "uri":"dws_mt_0030.html", - "product_code":"dws", - "code":"168", - "des":"Netezza parameters are used to customize rules for Netezza script migration.Open the features-netezza.properties file in the config folder and set parameters in Table 1 a", - "doc_type":"tg", - "kw":"Netezza Configuration,Configuring DSC,Tool Guide", - "title":"Netezza Configuration", - "githuburl":"" - }, - { - "uri":"dws_mt_0031.html", - "product_code":"dws", - "code":"169", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Using DSC", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Using DSC", "githuburl":"" }, { - "uri":"dws_mt_0032.html", + "uri":"dws_16_0010.html", + "node_id":"en-us_topic_0000001819416081.xml", + "product_code":"dws", + "code":"164", + "des":"This chapter describes how to use DSC, including how to install and configure DSC and how to use DSC to migrate data.Use the latest patches to update the operating system", + "doc_type":"tg", + "kw":"Overview,Using DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Overview", + "githuburl":"" + }, + { + "uri":"dws_16_0212.html", + "node_id":"en-us_topic_0000001819336053.xml", + "product_code":"dws", + "code":"165", + "des":"Before using DSC, install it on a Linux or Windows server. DSC supports 64-bit Linux OSs. For details about other OSs supported by DSC, see Table 4.In Linux, do not insta", + "doc_type":"tg", + "kw":"Downloading and Installing DSC,Using DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], + "title":"Downloading and Installing DSC", + "githuburl":"" + }, + { + "uri":"dws_16_0012.html", + "node_id":"en-us_topic_0000001772696056.xml", + "product_code":"dws", + "code":"166", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Configuring DSC", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Configuring DSC", + "githuburl":"" + }, + { + "uri":"dws_16_0013.html", + "node_id":"en-us_topic_0000001772536384.xml", + "product_code":"dws", + "code":"167", + "des":"Configure the following items:Setting application.properties: Configure the migration behavior of DSC, for example, whether to overwrite the files in the target folder an", + "doc_type":"tg", + "kw":"DSC Configuration,Configuring DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DSC Configuration", + "githuburl":"" + }, + { + "uri":"dws_16_0014.html", + "node_id":"en-us_topic_0000001819416085.xml", + "product_code":"dws", + "code":"168", + "des":"Teradata parameters are used to customize rules for Teradata script migration.Open the features-teradata.properties file in the config folder and set the parameters in Ta", + "doc_type":"tg", + "kw":"Teradata SQL Configuration,Configuring DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Teradata SQL Configuration", + "githuburl":"" + }, + { + "uri":"dws_16_0015.html", + "node_id":"en-us_topic_0000001819336057.xml", + "product_code":"dws", + "code":"169", + "des":"Teradata Perl parameters are used to customize rules for Teradata Perl script migration.Open the perl-migration.properties file in the config folder and set parameters in", + "doc_type":"tg", + "kw":"Teradata Perl Configuration,Configuring DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Teradata Perl Configuration", + "githuburl":"" + }, + { + "uri":"dws_16_0016.html", + "node_id":"en-us_topic_0000001772696060.xml", "product_code":"dws", "code":"170", + "des":"MySQL parameters are used to customize rules for MySQL script migration.Open the features-mysql.properties file in the config folder and configure Parameters in the featu", + "doc_type":"tg", + "kw":"MySQL Configuration,Configuring DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"MySQL Configuration", + "githuburl":"" + }, + { + "uri":"dws_16_0213.html", + "node_id":"en-us_topic_0000001772536388.xml", + "product_code":"dws", + "code":"171", + "des":"Oracle parameters are used to customize rules for Oracle script migration.Open the features-oracle.properties file in the config folder and set parameters in Table 1 as n", + "doc_type":"tg", + "kw":"Oracle SQL Configuration,Configuring DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], + "title":"Oracle SQL Configuration", + "githuburl":"" + }, + { + "uri":"dws_16_0214.html", + "node_id":"en-us_topic_0000001819416089.xml", + "product_code":"dws", + "code":"172", + "des":"Netezza parameters are used to customize rules for Netezza script migration.Open the features-netezza.properties file in the config folder and set parameters in Table 1 a", + "doc_type":"tg", + "kw":"Netezza Configuration,Configuring DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], + "title":"Netezza Configuration", + "githuburl":"" + }, + { + "uri":"dws_16_0017.html", + "node_id":"en-us_topic_0000001819336065.xml", + "product_code":"dws", + "code":"173", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Migration Process", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Migration Process", "githuburl":"" }, { - "uri":"dws_mt_0207.html", + "uri":"dws_16_0018.html", + "node_id":"en-us_topic_0000001772696064.xml", "product_code":"dws", - "code":"171", - "des":"The following use cases for migration are supported by DSC:Migrate Teradata SQLMigrate Oracle SQLMigrate Teradata Perl filesMigrate NetezzaMigrate MySQL SQLMigrate DB2Fig", - "doc_type":"tg", - "kw":"Overview,Migration Process,Tool Guide", - "title":"Overview", - "githuburl":"" - }, - { - "uri":"dws_mt_0033.html", - "product_code":"dws", - "code":"172", + "code":"174", "des":"Custom scripts are executed to support input keywords that do not exist in certain versions of the target database. These scripts must be executed in each target database", "doc_type":"tg", "kw":"Prerequisites,Migration Process,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Prerequisites", "githuburl":"" }, { - "uri":"dws_mt_0034.html", + "uri":"dws_16_0019.html", + "node_id":"en-us_topic_0000001772536392.xml", "product_code":"dws", - "code":"173", + "code":"175", "des":"Before the migration, create an input folder and an output folder, and copy all the SQL scripts to be migrated to the input folder. The following procedure describes how ", "doc_type":"tg", "kw":"Preparations,Migration Process,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Preparations", "githuburl":"" }, { - "uri":"dws_mt_0035.html", + "uri":"dws_16_0020.html", + "node_id":"en-us_topic_0000001819416093.xml", "product_code":"dws", - "code":"174", + "code":"176", "des":"Before starting DSC, specify the output folder path. Separate the input folder path, output folder path, and log path with spaces. The input folder path cannot contain sp", "doc_type":"tg", - "kw":"Migrating Data Using DSC,Migration Process,Tool Guide", - "title":"Migrating Data Using DSC", + "kw":"Executing DSC,Migration Process,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Executing DSC", "githuburl":"" }, { - "uri":"dws_mt_0036.html", + "uri":"dws_16_0021.html", + "node_id":"en-us_topic_0000001819336069.xml", "product_code":"dws", - "code":"175", + "code":"177", "des":"After the migration is complete, you can use a comparison tool (for example, BeyondCompare®) to compare the output file with its input file. Input SQL files can also be f", "doc_type":"tg", "kw":"Viewing Output Files and Logs,Migration Process,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Viewing Output Files and Logs", "githuburl":"" }, { - "uri":"dws_mt_0037.html", + "uri":"dws_16_0022.html", + "node_id":"en-us_topic_0000001772696072.xml", "product_code":"dws", - "code":"176", + "code":"178", "des":"Migration related issues can be classified into:Tool execution issues: No output or incorrect output is displayed because DSC partially or fully failed to be executed. Fo", "doc_type":"tg", "kw":"Troubleshooting,Migration Process,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Troubleshooting", "githuburl":"" }, { - "uri":"dws_mt_0038.html", + "uri":"dws_16_0023.html", + "node_id":"en-us_topic_0000001772536400.xml", "product_code":"dws", - "code":"177", + "code":"179", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"CLI Reference", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CLI Reference", + "githuburl":"" + }, + { + "uri":"dws_16_0024.html", + "node_id":"en-us_topic_0000001819416101.xml", + "product_code":"dws", + "code":"180", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Database Schema Conversion", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Database Schema Conversion", + "githuburl":"" + }, + { + "uri":"dws_16_0025.html", + "node_id":"en-us_topic_0000001819336077.xml", + "product_code":"dws", + "code":"181", + "des":"It is mandatory to specify the source database, input folder path, and output folder path, and optional to specify the migration type and log path.If a user does not spec", + "doc_type":"tg", + "kw":"Migration Parameters,Database Schema Conversion,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Migration Parameters", + "githuburl":"" + }, + { + "uri":"dws_16_0026.html", + "node_id":"en-us_topic_0000001772696076.xml", + "product_code":"dws", + "code":"182", "des":"DSC supports the migration from Teradata to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and type conversion.Run the following comman", "doc_type":"tg", - "kw":"Teradata SQL Migration,Using DSC,Tool Guide", + "kw":"Teradata SQL Migration,Database Schema Conversion,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Teradata SQL Migration", "githuburl":"" }, { - "uri":"dws_mt_0039.html", + "uri":"dws_16_0027.html", + "node_id":"en-us_topic_0000001772536404.xml", "product_code":"dws", - "code":"178", - "des":"DSC supports the migration from Oracle to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set t", - "doc_type":"tg", - "kw":"Oracle SQL Migration,Using DSC,Tool Guide", - "title":"Oracle SQL Migration", - "githuburl":"" - }, - { - "uri":"dws_mt_0041.html", - "product_code":"dws", - "code":"179", + "code":"183", "des":"This section describes how to migrate Teradata Perl files.Run the runDSC.shor runDSC.bat command and set --application-lang to perl to migrate Teradata BTEQ or SQL_LANG s", "doc_type":"tg", - "kw":"Teradata Perl Migration,Using DSC,Tool Guide", + "kw":"Teradata Perl Migration,Database Schema Conversion,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Teradata Perl Migration", "githuburl":"" }, { - "uri":"dws_07_0675.html", + "uri":"dws_16_0028.html", + "node_id":"en-us_topic_0000001819416105.xml", "product_code":"dws", - "code":"180", - "des":"DSC supports the migration from Netezza to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set ", - "doc_type":"tg", - "kw":"Netezza SQL Migration,Using DSC,Tool Guide", - "title":"Netezza SQL Migration", - "githuburl":"" - }, - { - "uri":"dws_07_0676.html", - "product_code":"dws", - "code":"181", + "code":"184", "des":"DSC supports the migration from MySQL to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following command on Linux t", "doc_type":"tg", - "kw":"MySQL SQL Migration,Using DSC,Tool Guide", + "kw":"MySQL SQL Migration,Database Schema Conversion,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"MySQL SQL Migration", "githuburl":"" }, { - "uri":"dws_mt_0042.html", + "uri":"dws_16_0215.html", + "node_id":"en-us_topic_0000001819336081.xml", "product_code":"dws", - "code":"182", - "des":"SQL Formatter improves the readability of SQL statements. It formats SQL statements by adding/deleting rows and indenting context, and is used to format migrated output f", + "code":"185", + "des":"DSC supports the migration from Oracle to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set t", "doc_type":"tg", - "kw":"SQL Formatter,Using DSC,Tool Guide", - "title":"SQL Formatter", + "kw":"Oracle SQL Migration,Database Schema Conversion,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], + "title":"Oracle SQL Migration", "githuburl":"" }, { - "uri":"dws_mt_0044.html", + "uri":"dws_16_0216.html", + "node_id":"en-us_topic_0000001772696084.xml", "product_code":"dws", - "code":"183", + "code":"186", + "des":"DSC supports the migration from Netezza to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set ", + "doc_type":"tg", + "kw":"Netezza SQL Migration,Database Schema Conversion,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], + "title":"Netezza SQL Migration", + "githuburl":"" + }, + { + "uri":"dws_16_0029.html", + "node_id":"en-us_topic_0000001772536408.xml", + "product_code":"dws", + "code":"187", + "des":"After DSC converts the source sql files, execute the converted files on target GaussDB(DWS) and provide a report with details of number of statements succeeded and failed", + "doc_type":"tg", + "kw":"Verification,Database Schema Conversion,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Verification", + "githuburl":"" + }, + { + "uri":"dws_16_0030.html", + "node_id":"en-us_topic_0000001819416113.xml", + "product_code":"dws", + "code":"188", + "des":"The version command is used to display the version number of the DSC.Linux:Windows:Linux:Windows:", + "doc_type":"tg", + "kw":"VERSION,CLI Reference,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"VERSION", + "githuburl":"" + }, + { + "uri":"dws_16_0031.html", + "node_id":"en-us_topic_0000001819336085.xml", + "product_code":"dws", + "code":"189", + "des":"The help command is used to provide the help information for the commands supported by DSC.Linux:Windows:Linux:Windows:Linux:Windows:", + "doc_type":"tg", + "kw":"HELP,CLI Reference,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"HELP", + "githuburl":"" + }, + { + "uri":"dws_16_0032.html", + "node_id":"en-us_topic_0000001772696088.xml", + "product_code":"dws", + "code":"190", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", - "kw":"Teradata Syntax Migration", - "title":"Teradata Syntax Migration", + "kw":"Log Reference", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Log Reference", "githuburl":"" }, { - "uri":"dws_mt_0045.html", + "uri":"dws_16_0217.html", + "node_id":"en-us_topic_0000001772536412.xml", "product_code":"dws", - "code":"184", - "des":"This section lists the Teradata features supported by the syntax migration tool, and provides the Teradata syntax and the equivalent GaussDB syntax for each feature. The ", + "code":"191", + "des":"The log files are the repository for all operations and status of the DSC. The following log files are available:SQL Migration LogsDSC.log: SQL Migration all activities.D", "doc_type":"tg", - "kw":"Overview,Teradata Syntax Migration,Tool Guide", + "kw":"Overview,Log Reference,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { - "uri":"dws_mt_0046.html", - "product_code":"dws", - "code":"185", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"tg", - "kw":"Schema Objects", - "title":"Schema Objects", - "githuburl":"" - }, - { - "uri":"dws_mt_0048.html", - "product_code":"dws", - "code":"186", - "des":"The table-specific keyword MULTISET VOLATILE is provided in the input file, but the keyword is not supported by GaussDB(DWS). Therefore, the tool replaces it with the LOC", - "doc_type":"tg", - "kw":"Table Migration,Schema Objects,Tool Guide", - "title":"Table Migration", - "githuburl":"" - }, - { - "uri":"dws_mt_0064.html", - "product_code":"dws", - "code":"187", - "des":"The sequence of CREATE INDEX columns and table names in Teradata is different from that in GaussDB(DWS). Use the configuration parameter distributeByHash to configure how", - "doc_type":"tg", - "kw":"Index Migration,Schema Objects,Tool Guide", - "title":"Index Migration", - "githuburl":"" - }, - { - "uri":"dws_mt_0065.html", - "product_code":"dws", - "code":"188", - "des":"CREATE VIEW (short key CV) is used together with SELECT to create a view.The keyword VIEW is supported by both Teradata and GaussDB(DWS), but the SELECT statements are en", - "doc_type":"tg", - "kw":"View Migration,Schema Objects,Tool Guide", - "title":"View Migration", - "githuburl":"" - }, - { - "uri":"dws_mt_0066.html", - "product_code":"dws", - "code":"189", - "des":"COLLECT STAT is used in Teradata for collecting optimizer statistics, which will be used for query performance. GaussDB(DWS) uses the ANALYZE statement to replace the COL", - "doc_type":"tg", - "kw":"COLLECT STATISTICS,Schema Objects,Tool Guide", - "title":"COLLECT STATISTICS", - "githuburl":"" - }, - { - "uri":"dws_mt_0067.html", - "product_code":"dws", - "code":"190", - "des":"ACCESS LOCK allows you to read the data from a table that may have been locked for the READ or WRITE.Use the tdMigrateLOCKOption configuration parameter to configure migr", - "doc_type":"tg", - "kw":"ACCESS LOCK,Schema Objects,Tool Guide", - "title":"ACCESS LOCK", - "githuburl":"" - }, - { - "uri":"dws_mt_0068.html", - "product_code":"dws", - "code":"191", - "des":"DBC.COLUMNSview is a table containing information about table and view columns, stored procedures, or macro parameters. The view includes the following column names: Data", - "doc_type":"tg", - "kw":"DBC.COLUMNS,Schema Objects,Tool Guide", - "title":"DBC.COLUMNS", - "githuburl":"" - }, - { - "uri":"dws_mt_0069.html", + "uri":"dws_16_0033.html", + "node_id":"en-us_topic_0000001819416117.xml", "product_code":"dws", "code":"192", - "des":"The DSC migrates dbc.tables to their corresponding mig_td_ext.vw_td_dbc_tables.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutput", + "des":"The SQL DSC (DSC.jar) supports the following types of logging:Activity loggingError loggingsuccessReadsuccessWriteIf a user specifies a log path, then all the logs are sa", "doc_type":"tg", - "kw":"DBC.TABLES,Schema Objects,Tool Guide", - "title":"DBC.TABLES", + "kw":"SQL Migration Logs,Log Reference,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SQL Migration Logs", "githuburl":"" }, { - "uri":"dws_mt_0070.html", + "uri":"dws_16_0034.html", + "node_id":"en-us_topic_0000001819336089.xml", "product_code":"dws", "code":"193", - "des":"DSC migrates dbc.indices to the corresponding mig_td_ext.vw_td_dbc_indices.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutputIn dbc.i", + "des":"The DSC writes all log information to a single file, perlDSC.log.Since the DSC will execute the SQL to migrate the SQL scripts inside Perl files, the following SQL migrat", "doc_type":"tg", - "kw":"DBC.INDICES,Schema Objects,Tool Guide", - "title":"DBC.INDICES", + "kw":"Perl Migration Logs,Log Reference,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Perl Migration Logs", "githuburl":"" }, { - "uri":"dws_07_8111.html", + "uri":"dws_16_0035.html", + "node_id":"en-us_topic_0000001772696092.xml", "product_code":"dws", "code":"194", - "des":"This command displays the COLLECT STATISTICS statement with statistics. Gauss does not have an equivalent for this. Since it does not affect the functionality, this comma", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", - "kw":"SHOW STATS VALUES SEQUENCED,Teradata Syntax Migration,Tool Guide", - "title":"SHOW STATS VALUES SEQUENCED", + "kw":"SQL Syntax Migration Reference", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SQL Syntax Migration Reference", "githuburl":"" }, { - "uri":"dws_mt_0071.html", + "uri":"dws_16_0036.html", + "node_id":"en-us_topic_0000001772536416.xml", "product_code":"dws", "code":"195", - "des":"This section describes the syntax for migrating Teradata DML. The migration syntax determines how the keywords and features are migrated.In Teradata, SQL queries in a fil", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", - "kw":"DML,Teradata Syntax Migration,Tool Guide", - "title":"DML", + "kw":"Teradata Syntax Migration", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Teradata Syntax Migration", "githuburl":"" }, { - "uri":"dws_mt_0084.html", + "uri":"dws_16_0038.html", + "node_id":"en-us_topic_0000001819416121.xml", "product_code":"dws", "code":"196", - "des":"This section contains the migration syntax for migrating Teradata query migration operators. The migration syntax determines how the keywords and features are migrated.Fo", + "des":"Table 1 lists the Teradata keywords and features that can be migrated.The Version column contains the earliest versions that support the keywords or features.The Remarks ", "doc_type":"tg", - "kw":"Querying Migration Operators,Teradata Syntax Migration,Tool Guide", - "title":"Querying Migration Operators", + "kw":"Supported Keywords and Features,Teradata Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Supported Keywords and Features", "githuburl":"" }, { - "uri":"dws_mt_0091.html", + "uri":"dws_16_0039.html", + "node_id":"en-us_topic_0000001819336093.xml", "product_code":"dws", "code":"197", - "des":"This section describes the syntax for migrating Teradata query optimization operators. The migration syntax determines how the keywords and features are migrated.Use the ", + "des":"The restrictions on using DSC to migrate data from TD are as follows:DSC is used only for syntax migration and not for data migration.If the SELECT clause of a subquery c", "doc_type":"tg", - "kw":"Query Optimization Operators,Teradata Syntax Migration,Tool Guide", - "title":"Query Optimization Operators", + "kw":"Constraints and Limitations,Teradata Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Constraints and Limitations", "githuburl":"" }, { - "uri":"dws_mt_0094.html", + "uri":"dws_16_0040.html", + "node_id":"en-us_topic_0000001772696096.xml", "product_code":"dws", "code":"198", - "des":"This section contains the migration syntax for migrating Teradata system functions and operators. The migration syntax determines how the keywords and features are migrat", + "des":"InputOutput", "doc_type":"tg", - "kw":"System Functions and Operators,Teradata Syntax Migration,Tool Guide", - "title":"System Functions and Operators", + "kw":"Data Type,Teradata Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Data Type", "githuburl":"" }, { - "uri":"dws_mt_0100.html", + "uri":"dws_16_0041.html", + "node_id":"en-us_topic_0000001772536420.xml", "product_code":"dws", "code":"199", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Functions and Operators", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Functions and Operators", + "githuburl":"" + }, + { + "uri":"dws_16_0043.html", + "node_id":"en-us_topic_0000001819416125.xml", + "product_code":"dws", + "code":"200", + "des":"Analytical functions are collectively called ordered analytical functions in Teradata, and they provide powerful analytical abilities for data mining, analysis and busine", + "doc_type":"tg", + "kw":"Analytical Functions,Functions and Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Analytical Functions", + "githuburl":"" + }, + { + "uri":"dws_16_0044.html", + "node_id":"en-us_topic_0000001819336097.xml", + "product_code":"dws", + "code":"201", "des":"Input: **OutputInput: MODOutputUse the tdMigrateNULLIFZERO configuration parameter to configure migration of NULLIFZERO.Input: NULLIFZEROSELECT NULLIFZERO(expr1) FROM tab", "doc_type":"tg", - "kw":"Math Functions,Teradata Syntax Migration,Tool Guide", + "kw":"Math Functions,Functions and Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Math Functions", "githuburl":"" }, { - "uri":"dws_mt_0101.html", + "uri":"dws_16_0045.html", + "node_id":"en-us_topic_0000001772696100.xml", "product_code":"dws", - "code":"200", + "code":"202", "des":"Input: CHAROutputInput: CHARACTERSOutputInput: INDEXOutputInput: STRREPLACESELECT STRREPLACE(c2, '.', '')\n FROM tab1\n WHERE ...;OutputInput: OREPLACESELECT OREPLACE (c2,", "doc_type":"tg", - "kw":"String Functions,Teradata Syntax Migration,Tool Guide", + "kw":"String Functions,Functions and Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"String Functions", "githuburl":"" }, { - "uri":"dws_mt_0102.html", + "uri":"dws_16_0046.html", + "node_id":"en-us_topic_0000001772536424.xml", "product_code":"dws", - "code":"201", + "code":"203", "des":"Migration tools support the migration of Teradata DATE FORMAT in SELECT statements, using TO_CHAR to display the date in the source format. This conversion is not done if", "doc_type":"tg", - "kw":"Date and Time Functions,Teradata Syntax Migration,Tool Guide", + "kw":"Date and Time Functions,Functions and Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Date and Time Functions", "githuburl":"" }, { - "uri":"dws_mt_0103.html", + "uri":"dws_16_0047.html", + "node_id":"en-us_topic_0000001819416129.xml", "product_code":"dws", - "code":"202", + "code":"204", + "des":"The comparison operators LT, LE, GT, GE, EQ, and NE must not be used as TABLE alias or COLUMN alias.The following comparison and list operators are supported:Input: Compa", + "doc_type":"tg", + "kw":"Comparison and List Operators,Functions and Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Comparison and List Operators", + "githuburl":"" + }, + { + "uri":"dws_16_0048.html", + "node_id":"en-us_topic_0000001819336101.xml", + "product_code":"dws", + "code":"205", + "des":"The functions that can be called in the FROM clause of a query are from the table operator.Input: Table operator with RETURNSSELECT * \n FROM TABLE( sales_retrieve (9005)", + "doc_type":"tg", + "kw":"Table Operators,Functions and Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Table Operators", + "githuburl":"" + }, + { + "uri":"dws_16_0049.html", + "node_id":"en-us_topic_0000001772696104.xml", + "product_code":"dws", + "code":"206", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Query Migration Operators", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Query Migration Operators", + "githuburl":"" + }, + { + "uri":"dws_16_0051.html", + "node_id":"en-us_topic_0000001772536428.xml", + "product_code":"dws", + "code":"207", + "des":"In general, the QUALIFY clause is accompanied by analytic functions (window functions) such as CSUM(), MDIFF(), ROW_NUMBER() and RANK(). This is addressed using sub-query", + "doc_type":"tg", + "kw":"QUALIFY,Query Migration Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"QUALIFY", + "githuburl":"" + }, + { + "uri":"dws_16_0052.html", + "node_id":"en-us_topic_0000001819416133.xml", + "product_code":"dws", + "code":"208", + "des":"ALIAS is supported by all databases. In Teradata, an ALIAS can be referred in SELECT and WHERE clauses of the same statement where the alias is defined. Since ALIAS is no", + "doc_type":"tg", + "kw":"ALIAS,Query Migration Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ALIAS", + "githuburl":"" + }, + { + "uri":"dws_16_0053.html", + "node_id":"en-us_topic_0000001819336105.xml", + "product_code":"dws", + "code":"209", + "des":"In Teradata, the FORMAT keyword is used for formatting a column/expression. For example, FORMAT '9(n)' and 'z(n)' are addressed using LPAD with 0 and space (' ') respecti", + "doc_type":"tg", + "kw":"FORMAT and CAST,Query Migration Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"FORMAT and CAST", + "githuburl":"" + }, + { + "uri":"dws_16_0054.html", + "node_id":"en-us_topic_0000001772696108.xml", + "product_code":"dws", + "code":"210", + "des":"Table 1 lists the abbreviation keywords supported by Teradata and the corresponding syntax in GaussDB A and GaussDB(DWS).Input - BTOutput", + "doc_type":"tg", + "kw":"Short Keys Migration,Query Migration Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Short Keys Migration", + "githuburl":"" + }, + { + "uri":"dws_16_0055.html", + "node_id":"en-us_topic_0000001772536432.xml", + "product_code":"dws", + "code":"211", + "des":"This section describes the migration of object names starting with $.The migration behavior for object names starting with $ is explained in the following table. Use the ", + "doc_type":"tg", + "kw":"Object Names Starting with $,Query Migration Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Object Names Starting with $", + "githuburl":"" + }, + { + "uri":"dws_16_0056.html", + "node_id":"en-us_topic_0000001819416137.xml", + "product_code":"dws", + "code":"212", + "des":"This section describes the syntax for migrating Teradata query optimization operators. The migration syntax determines how the keywords and features are migrated.Use the ", + "doc_type":"tg", + "kw":"Query Optimization Operators,Functions and Operators,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Query Optimization Operators", + "githuburl":"" + }, + { + "uri":"dws_16_0059.html", + "node_id":"en-us_topic_0000001819336109.xml", + "product_code":"dws", + "code":"213", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Schema Objects and Data Definition Language (DDL)", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Schema Objects and Data Definition Language (DDL)", + "githuburl":"" + }, + { + "uri":"dws_16_0061.html", + "node_id":"en-us_topic_0000001772696112.xml", + "product_code":"dws", + "code":"214", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Migrating Tables", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Migrating Tables", + "githuburl":"" + }, + { + "uri":"dws_16_0063.html", + "node_id":"en-us_topic_0000001772536436.xml", + "product_code":"dws", + "code":"215", + "des":"The Teradata CREATE TABLE (short key CT) statements are used to create new tables.Example:Input: CREATE TABLEOutputWhen CREATE tab2 AS tab1 is executed, the structure cop", + "doc_type":"tg", + "kw":"CREATE TABLE,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CREATE TABLE", + "githuburl":"" + }, + { + "uri":"dws_16_0064.html", + "node_id":"en-us_topic_0000001819416141.xml", + "product_code":"dws", + "code":"216", + "des":"CHARACTER SET is used to specify the server character set for a character column. CASESPECIFIC specifies the case for character data comparisons and collations.Use the td", + "doc_type":"tg", + "kw":"CHARACTER SET and CASESPECIFIC,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CHARACTER SET and CASESPECIFIC", + "githuburl":"" + }, + { + "uri":"dws_16_0065.html", + "node_id":"en-us_topic_0000001819336113.xml", + "product_code":"dws", + "code":"217", + "des":"The table-specific keyword VOLATILE is provided in the input file, but the keyword is not supported by GaussDB(DWS). The tool replaces it with the LOCAL TEMPORARYkeyword ", + "doc_type":"tg", + "kw":"VOLATILE,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"VOLATILE", + "githuburl":"" + }, + { + "uri":"dws_16_0066.html", + "node_id":"en-us_topic_0000001772696116.xml", + "product_code":"dws", + "code":"218", + "des":"SET is a unique feature in Teradata. It does not allow duplicate records. It is addressed using the MINUSset operator. Migration tool supports MULTISET and SET tables. SE", + "doc_type":"tg", + "kw":"SET,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SET", + "githuburl":"" + }, + { + "uri":"dws_16_0067.html", + "node_id":"en-us_topic_0000001772536440.xml", + "product_code":"dws", + "code":"219", + "des":"MULTISETis a normal table, which is supported by all the DBs. Migration tool supports MULTISET and SET tables.MULTISET table can be used with VOLATILE.Input: CREATE MULTI", + "doc_type":"tg", + "kw":"MULTISET,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"MULTISET", + "githuburl":"" + }, + { + "uri":"dws_16_0068.html", + "node_id":"en-us_topic_0000001819416145.xml", + "product_code":"dws", + "code":"220", + "des":"The keyword TITLE is supported for Teradata Permanent, Global Temporary and Volatile tables. In the migration process, the TITLE text is migrated as a comment.If the TITL", + "doc_type":"tg", + "kw":"TITLE,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"TITLE", + "githuburl":"" + }, + { + "uri":"dws_16_0069.html", + "node_id":"en-us_topic_0000001819336117.xml", + "product_code":"dws", + "code":"221", + "des":"The CREATE TABLE statement supports creation of an index. Migration tool supports the TABLE statement with PRIMARY INDEX and UNIQUE INDEX.The tool will not add DISTRIBUTE", + "doc_type":"tg", + "kw":"Indexes,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0070.html", + "node_id":"en-us_topic_0000001772696120.xml", + "product_code":"dws", + "code":"222", + "des":"A table CONSTRAINT is applied to multiple columns. Migration tool supports the following constraints:CHECK constraint: supported by GaussDB T, GaussDB A, and GaussDB(DWS)", + "doc_type":"tg", + "kw":"CONSTRAINT,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CONSTRAINT", + "githuburl":"" + }, + { + "uri":"dws_16_0071.html", + "node_id":"en-us_topic_0000001772536444.xml", + "product_code":"dws", + "code":"223", + "des":"The table orientation can be converted from ROW-STORE to COLUMN store using the WITH (ORIENTATION=COLUMN) in the CREATE TABLE statement. This feature can be enabled/disab", + "doc_type":"tg", + "kw":"COLUMN STORE,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"COLUMN STORE", + "githuburl":"" + }, + { + "uri":"dws_16_0072.html", + "node_id":"en-us_topic_0000001819416149.xml", + "product_code":"dws", + "code":"224", + "des":"The tool does not support migration of partitions/subpartitions and the partition/subpartition keywords are commented in the migrated scripts:Range partition/subpartition", + "doc_type":"tg", + "kw":"PARTITION,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"PARTITION", + "githuburl":"" + }, + { + "uri":"dws_16_0073.html", + "node_id":"en-us_topic_0000001819336121.xml", + "product_code":"dws", + "code":"225", + "des":"Input - CREATE TABLE with INDEXOutput", + "doc_type":"tg", + "kw":"ANALYZE,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ANALYZE", + "githuburl":"" + }, + { + "uri":"dws_16_0074.html", + "node_id":"en-us_topic_0000001772696124.xml", + "product_code":"dws", + "code":"226", + "des":"Migration tool supports queries that specify number of columns (not all columns specified) during INSERT. This can happen when the input INSERT statement does not contain", + "doc_type":"tg", + "kw":"Support for Specified Columns,Migrating Tables,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Support for Specified Columns", + "githuburl":"" + }, + { + "uri":"dws_16_0075.html", + "node_id":"en-us_topic_0000001772536448.xml", + "product_code":"dws", + "code":"227", + "des":"The sequence of columns and table names in CREATE INDEX in Teradata is different from that in GaussDB T, GaussDB A, and GaussDB(DWS). Use the configuration parameter dist", + "doc_type":"tg", + "kw":"Migrating Indexes,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Migrating Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0076.html", + "node_id":"en-us_topic_0000001819416153.xml", + "product_code":"dws", + "code":"228", + "des":"CREATE VIEW (short key CV) is used together with SELECT to create a view.Teradata, GaussDB T, GaussDB A, and GaussDB(DWS) all support the keyword VIEW. It is enclosed by ", + "doc_type":"tg", + "kw":"Migrating Views,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Migrating Views", + "githuburl":"" + }, + { + "uri":"dws_16_0077.html", + "node_id":"en-us_topic_0000001819336125.xml", + "product_code":"dws", + "code":"229", + "des":"COLLECT STAT is used in Teradata for collecting optimizer statistics, which will be used for query performance. GaussDB T, GaussDB A, and GaussDB(DWS) use the ANALYZE sta", + "doc_type":"tg", + "kw":"COLLECT STATISTICS,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"COLLECT STATISTICS", + "githuburl":"" + }, + { + "uri":"dws_16_0078.html", + "node_id":"en-us_topic_0000001772696128.xml", + "product_code":"dws", + "code":"230", + "des":"ACCESS LOCK allows you to read the data from a table that may have been locked for the READ or WRITE.Use the tdMigrateLOCKoption configuration parameter to configure migr", + "doc_type":"tg", + "kw":"ACCESS LOCK,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ACCESS LOCK", + "githuburl":"" + }, + { + "uri":"dws_16_0079.html", + "node_id":"en-us_topic_0000001772536452.xml", + "product_code":"dws", + "code":"231", + "des":"DBC.COLUMNSview is a table containing information about table and view columns, stored procedures, or macro parameters. The view includes the following column names: Data", + "doc_type":"tg", + "kw":"DBC.COLUMNS,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DBC.COLUMNS", + "githuburl":"" + }, + { + "uri":"dws_16_0080.html", + "node_id":"en-us_topic_0000001819416157.xml", + "product_code":"dws", + "code":"232", + "des":"The DSC migrates dbc.tables to their corresponding mig_td_ext.vw_td_dbc_tables.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutput", + "doc_type":"tg", + "kw":"DBC.TABLES,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DBC.TABLES", + "githuburl":"" + }, + { + "uri":"dws_16_0081.html", + "node_id":"en-us_topic_0000001819336129.xml", + "product_code":"dws", + "code":"233", + "des":"DSC migrates dbc.indices to the corresponding mig_td_ext.vw_td_dbc_indices.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutputIn dbc.i", + "doc_type":"tg", + "kw":"DBC.INDICES,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DBC.INDICES", + "githuburl":"" + }, + { + "uri":"dws_16_0082.html", + "node_id":"en-us_topic_0000001772696132.xml", + "product_code":"dws", + "code":"234", + "des":"This command displays the COLLECT STATISTICS statement with statistics. Gauss does not have an equivalent for this. Since it does not affect the functionality, this comma", + "doc_type":"tg", + "kw":"SHOW STATS VALUES SEQUENCED,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SHOW STATS VALUES SEQUENCED", + "githuburl":"" + }, + { + "uri":"dws_16_0083.html", + "node_id":"en-us_topic_0000001772536456.xml", + "product_code":"dws", + "code":"235", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"COMMENT,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"COMMENT", + "githuburl":"" + }, + { + "uri":"dws_16_0084.html", + "node_id":"en-us_topic_0000001819416161.xml", + "product_code":"dws", + "code":"236", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Data Manipulation Language (DML)", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Data Manipulation Language (DML)", + "githuburl":"" + }, + { + "uri":"dws_16_0086.html", + "node_id":"en-us_topic_0000001819336133.xml", + "product_code":"dws", + "code":"237", + "des":"The Teradata INSERT (short key INS) statement is used to insert records into a table. DSC supports the INSERT statement.The INSERT INTO TABLE table_name syntax is used in", + "doc_type":"tg", + "kw":"INSERT,Data Manipulation Language (DML),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"INSERT", + "githuburl":"" + }, + { + "uri":"dws_16_0087.html", + "node_id":"en-us_topic_0000001772696136.xml", + "product_code":"dws", + "code":"238", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"SELECT", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SELECT", + "githuburl":"" + }, + { + "uri":"dws_16_0088.html", + "node_id":"en-us_topic_0000001772536460.xml", + "product_code":"dws", + "code":"239", + "des":"The Teradata SELECT command (short key SEL) is used to specify the table columns from which data is to be retrieved.ANALYZE is used in GaussDB(DWS) for collecting optimiz", + "doc_type":"tg", + "kw":"ANALYZE,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ANALYZE", + "githuburl":"" + }, + { + "uri":"dws_16_0089.html", + "node_id":"en-us_topic_0000001819416169.xml", + "product_code":"dws", + "code":"240", + "des":"For Teradata migration of SELECTstatements, all the clauses (FROM, WHERE, HAVING and GROUP BY) can be listed in any order. The tool will not migrate the statement if it c", + "doc_type":"tg", + "kw":"Order of Clauses,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Order of Clauses", + "githuburl":"" + }, + { + "uri":"dws_16_0090.html", + "node_id":"en-us_topic_0000001819336145.xml", + "product_code":"dws", + "code":"241", + "des":"The GROUP BY clause can be specified if you want the database to group the selected rows based on the value of expr(s). If this clause contains CUBE, ROLLUPor GROUPING SE", + "doc_type":"tg", + "kw":"Extended Group By Clause,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Extended Group By Clause", + "githuburl":"" + }, + { + "uri":"dws_16_0091.html", + "node_id":"en-us_topic_0000001772696140.xml", + "product_code":"dws", + "code":"242", + "des":"GaussDB(DWS) variable names are case insensitive, and TD variable names are case sensitive. To ensure that the TD script is correct before and after the migration, retain", + "doc_type":"tg", + "kw":"SELECT AS,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SELECT AS", + "githuburl":"" + }, + { + "uri":"dws_16_0092.html", + "node_id":"en-us_topic_0000001772536464.xml", + "product_code":"dws", + "code":"243", + "des":"The TOP and SAMPLE clauses of Teradata are migrated to LIMIT in GaussDB(DWS).The DSC also supports migration of TOPstatements with dynamic parameters.For TOPclauses conta", + "doc_type":"tg", + "kw":"TOP and SAMPLE,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"TOP and SAMPLE", + "githuburl":"" + }, + { + "uri":"dws_16_0093.html", + "node_id":"en-us_topic_0000001819416173.xml", + "product_code":"dws", + "code":"244", + "des":"The tool supports and migrates the UPDATE(short key UPD) statements.Input: UPDATE with TABLE ALIASOutputInput: UPDATE with TABLE ALIASusing a sub queryOutputInput: UPDATE", + "doc_type":"tg", + "kw":"UPDATE,Data Manipulation Language (DML),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"UPDATE", + "githuburl":"" + }, + { + "uri":"dws_16_0094.html", + "node_id":"en-us_topic_0000001819336149.xml", + "product_code":"dws", + "code":"245", + "des":"DELETE (short key abbreviated as DEL) is an ANSI-compliant SQL syntax operator used to delete existing records from a table. DSC supports the Teradata DELETE statement an", + "doc_type":"tg", + "kw":"DELETE,Data Manipulation Language (DML),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DELETE", + "githuburl":"" + }, + { + "uri":"dws_16_0095.html", + "node_id":"en-us_topic_0000001772696144.xml", + "product_code":"dws", + "code":"246", + "des":"Gauss database in 6.5.0 or later versions support the MERGE function.MERGEis an ANSI-standard SQL syntax operator used to select rows from one or more sources for updatin", + "doc_type":"tg", + "kw":"MERGE,Data Manipulation Language (DML),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"MERGE", + "githuburl":"" + }, + { + "uri":"dws_16_0096.html", + "node_id":"en-us_topic_0000001772536468.xml", + "product_code":"dws", + "code":"247", + "des":"NAMED is used in Teradata to assign a temporary name to an expression or column. NAMED statements used for expressions are migrated to AS in GaussDB T, GaussDB A, and Gau", + "doc_type":"tg", + "kw":"NAMED,Data Manipulation Language (DML),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"NAMED", + "githuburl":"" + }, + { + "uri":"dws_16_0097.html", + "node_id":"en-us_topic_0000001819416181.xml", + "product_code":"dws", + "code":"248", + "des":"ACTIVITYCOUNTInputIt is a status variable that returns the number of rows affected by an SQL DML statement in an embedded SQL.Output", + "doc_type":"tg", + "kw":"ACTIVITYCOUNT,Data Manipulation Language (DML),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ACTIVITYCOUNT", + "githuburl":"" + }, + { + "uri":"dws_16_0098.html", + "node_id":"en-us_topic_0000001819336153.xml", + "product_code":"dws", + "code":"249", + "des":"Input - TIMESTAMP with FORMATThe FORMAT phrase sets the format for a specific TIME or TIMESTAMP column or value. A FORMAT phrase overrides the system format.OutputInputOu", + "doc_type":"tg", + "kw":"TIMESTAMP,Data Manipulation Language (DML),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"TIMESTAMP", + "githuburl":"" + }, + { + "uri":"dws_16_0099.html", + "node_id":"en-us_topic_0000001772696148.xml", + "product_code":"dws", + "code":"250", "des":"This section contains the migration syntax for migrating Teradata type casting and formatting syntax. The migration syntax determines how the keywords and features are mi", "doc_type":"tg", "kw":"Type Casting and Formatting,Teradata Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"Type Casting and Formatting", "githuburl":"" }, { - "uri":"dws_07_8120.html", + "uri":"dws_16_0100.html", + "node_id":"en-us_topic_0000001772536472.xml", "product_code":"dws", - "code":"203", - "des":"The BTEQ utility commands are as follows:LOGOFF ends the current RDBMS sessions without exiting BTEQ.QUIT command ends the current Teradata database sessions and exits BT", + "code":"251", + "des":"GaussDB(DWS) provides gsql meta-commands that can be used to replace common BTEQ tool commands. The mostly used replacements are as follows:The meta-command \\q [value] ca", "doc_type":"tg", "kw":"BTEQ Utility Command,Teradata Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], "title":"BTEQ Utility Command", "githuburl":"" }, { - "uri":"dws_07_8121.html", + "uri":"dws_16_0101.html", + "node_id":"en-us_topic_0000001819416185.xml", "product_code":"dws", - "code":"204", - "des":"InputOutputInputOutputInputOutputInputOutputInputOutput", + "code":"252", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", - "kw":"DSQL,Teradata Syntax Migration,Tool Guide", - "title":"DSQL", + "kw":"Teradata Formats,Teradata Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Teradata Formats", + "githuburl":"" + }, + { + "uri":"dws_16_0102.html", + "node_id":"en-us_topic_0000001819336157.xml", + "product_code":"dws", + "code":"253", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"System Views,Teradata Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"System Views", + "githuburl":"" + }, + { + "uri":"dws_16_0103.html", + "node_id":"en-us_topic_0000001772696152.xml", + "product_code":"dws", + "code":"254", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"MySQL Syntax Migrating", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"MySQL Syntax Migrating", + "githuburl":"" + }, + { + "uri":"dws_16_0105.html", + "node_id":"en-us_topic_0000001772536476.xml", + "product_code":"dws", + "code":"255", + "des":"Table 1 lists the MySQL keywords and features that can be migrated.The Version column contains the earliest versions that support the keywords or features.The Remarks col", + "doc_type":"tg", + "kw":"Supported Keywords and Features,MySQL Syntax Migrating,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Supported Keywords and Features", + "githuburl":"" + }, + { + "uri":"dws_16_0106.html", + "node_id":"en-us_topic_0000001819416189.xml", + "product_code":"dws", + "code":"256", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Data Types", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Data Types", + "githuburl":"" + }, + { + "uri":"dws_16_0108.html", + "node_id":"en-us_topic_0000001819336161.xml", + "product_code":"dws", + "code":"257", + "des":"A data type is a basic data attribute. Occupied storage space and allowed operations vary according to data types. In a database, data is stored in tables, in which a dat", + "doc_type":"tg", + "kw":"Numeric Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Numeric Types", + "githuburl":"" + }, + { + "uri":"dws_16_0109.html", + "node_id":"en-us_topic_0000001772696156.xml", + "product_code":"dws", + "code":"258", + "des":"This section describes the following date and time types: DATETIME, TIME, TIMESTAMP, and YEAR. GaussDB(DWS) does not support these types, and DSC will convert them.The va", + "doc_type":"tg", + "kw":"Date/Time Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Date/Time Types", + "githuburl":"" + }, + { + "uri":"dws_16_0110.html", + "node_id":"en-us_topic_0000001772536480.xml", + "product_code":"dws", + "code":"259", + "des":"MySQL interprets length specifications in character column definitions in character units. This applies to the CHAR, VARCHAR, and TEXT types. DSC supports the following t", + "doc_type":"tg", + "kw":"String Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"String Types", + "githuburl":"" + }, + { + "uri":"dws_16_0111.html", + "node_id":"en-us_topic_0000001819416193.xml", + "product_code":"dws", + "code":"260", + "des":"MySQL has spatial data types corresponding to the OpenGIS class. DSC supports the following type conversions:GEOMETRY can store geometry values of any type. The other sin", + "doc_type":"tg", + "kw":"Spatial Data Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Spatial Data Types", + "githuburl":"" + }, + { + "uri":"dws_16_0112.html", + "node_id":"en-us_topic_0000001819336165.xml", + "product_code":"dws", + "code":"261", + "des":"A BLOB is a binary large object that can hold a variable amount of data. The four BLOB types are TINYBLOB, BLOB, MEDIUMBLOB, and LONGBLOB. The only difference between the", + "doc_type":"tg", + "kw":"LOB Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LOB Types", + "githuburl":"" + }, + { + "uri":"dws_16_0113.html", + "node_id":"en-us_topic_0000001772696160.xml", + "product_code":"dws", + "code":"262", + "des":"In MySQL, an ENUM is a string object with a value chosen from a list of permitted values that are enumerated explicitly in the column specification at table creation.A SE", + "doc_type":"tg", + "kw":"Set Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Set Types", + "githuburl":"" + }, + { + "uri":"dws_16_0114.html", + "node_id":"en-us_topic_0000001772536484.xml", + "product_code":"dws", + "code":"263", + "des":"MySQL supports both BOOL and BOOLEAN. DSC supports the following type conversions:Input: BOOL/BOOLEANOutput", + "doc_type":"tg", + "kw":"Boolean,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Boolean", + "githuburl":"" + }, + { + "uri":"dws_16_0115.html", + "node_id":"en-us_topic_0000001819416197.xml", + "product_code":"dws", + "code":"264", + "des":"In MySQL, the BIT data type is used to store bit values. A type of BIT(M) enables storage of M-bit values. M can range from 1 to 64.MySQL BINARY and VARBINARY types are s", + "doc_type":"tg", + "kw":"Binary Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Binary Types", + "githuburl":"" + }, + { + "uri":"dws_16_0116.html", + "node_id":"en-us_topic_0000001819336169.xml", + "product_code":"dws", + "code":"265", + "des":"The JSON data type can be used to store JavaScript Object Notation (JSON) data. DSC supports the following type conversions:Input Example (JSON)Output", + "doc_type":"tg", + "kw":"JSON Types,Data Types,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"JSON Types", + "githuburl":"" + }, + { + "uri":"dws_16_0117.html", + "node_id":"en-us_topic_0000001772696164.xml", + "product_code":"dws", + "code":"266", + "des":"The functions and expressions in MySQL do not exist in GaussDB(DWS) or are different from those in GaussDB(DWS). DSC migrates the functions and expressions based on the s", + "doc_type":"tg", + "kw":"Functions and Expressions,MySQL Syntax Migrating,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Functions and Expressions", + "githuburl":"" + }, + { + "uri":"dws_16_0118.html", + "node_id":"en-us_topic_0000001772536488.xml", + "product_code":"dws", + "code":"267", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Schema Objects and Data Definition Language (DDL)", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Schema Objects and Data Definition Language (DDL)", + "githuburl":"" + }, + { + "uri":"dws_16_0119.html", + "node_id":"en-us_topic_0000001819416201.xml", + "product_code":"dws", + "code":"268", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Table (Optional Parameters and Operations)", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Table (Optional Parameters and Operations)", + "githuburl":"" + }, + { + "uri":"dws_16_0120.html", + "node_id":"en-us_topic_0000001819336173.xml", + "product_code":"dws", + "code":"269", + "des":"MySQL 8.0.29 has extended the support for ALTER TABLE... ALGORITHM=INSTANT: Users can add columns instantly and delete columns instantly anywhere in a table, and evaluate", + "doc_type":"tg", + "kw":"ALGORITHM,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ALGORITHM", + "githuburl":"" + }, + { + "uri":"dws_16_0121.html", + "node_id":"en-us_topic_0000001772696168.xml", + "product_code":"dws", + "code":"270", + "des":"In GaussDB(DWS), the rename clause cannot contain the schema name. The DSC tool supports only the rename operation in the same schema. After the rename operation, the sch", + "doc_type":"tg", + "kw":"ALTER TABLE RENAME,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ALTER TABLE RENAME", + "githuburl":"" + }, + { + "uri":"dws_16_0122.html", + "node_id":"en-us_topic_0000001772536492.xml", + "product_code":"dws", + "code":"271", + "des":"In database application, unique numbers that increase automatically are needed to identify records. In MySQL, the AUTO_INCREMENT attribute of a data column can be used to", + "doc_type":"tg", + "kw":"AUTO_INCREMENT,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"AUTO_INCREMENT", + "githuburl":"" + }, + { + "uri":"dws_16_0123.html", + "node_id":"en-us_topic_0000001819416205.xml", + "product_code":"dws", + "code":"272", + "des":"In MySQL, AVG_ROW_LENGTH indicates the average length of each row. This is not supported by GaussDB(DWS) and is deleted by DSC during the migration.InputOutput", + "doc_type":"tg", + "kw":"AVG_ROW_LENGTH,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"AVG_ROW_LENGTH", + "githuburl":"" + }, + { + "uri":"dws_16_0124.html", + "node_id":"en-us_topic_0000001819336177.xml", + "product_code":"dws", + "code":"273", + "des":"In ADB, this parameter specifies the number of values stored in each block in columnar storage, which is also the minimum I/O unit. GaussDB(DWS does not support table def", + "doc_type":"tg", + "kw":"BLOCK_SIZE,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"BLOCK_SIZE", + "githuburl":"" + }, + { + "uri":"dws_16_0125.html", + "node_id":"en-us_topic_0000001772696172.xml", + "product_code":"dws", + "code":"274", + "des":"CHARSET specifies the default character set for a table. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword dur", + "doc_type":"tg", + "kw":"CHARSET,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CHARSET", + "githuburl":"" + }, + { + "uri":"dws_16_0126.html", + "node_id":"en-us_topic_0000001772536496.xml", + "product_code":"dws", + "code":"275", + "des":"In MySQL, CHECKSUM maintains a live checksum for all rows. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword d", + "doc_type":"tg", + "kw":"CHECKSUM,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CHECKSUM", + "githuburl":"" + }, + { + "uri":"dws_16_0127.html", + "node_id":"en-us_topic_0000001819416209.xml", + "product_code":"dws", + "code":"276", + "des":"It is a clustered index in ADB that defines the sorting sequence in a table. The logical sequence of key values in a clustered index determines the physical sequence of r", + "doc_type":"tg", + "kw":"CLUSTERED KEY,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CLUSTERED KEY", + "githuburl":"" + }, + { + "uri":"dws_16_0128.html", + "node_id":"en-us_topic_0000001819336181.xml", + "product_code":"dws", + "code":"277", + "des":"In MySQL, COLLATE specifies a default database sorting rule. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword", + "doc_type":"tg", + "kw":"COLLATE,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"COLLATE", + "githuburl":"" + }, + { + "uri":"dws_16_0129.html", + "node_id":"en-us_topic_0000001772696176.xml", + "product_code":"dws", + "code":"278", + "des":"In MySQL, COMMENT is a comment for a table. In GaussDB(DWS), this attribute can be used to modify table definition. During migration using DSC, additional table attribute", + "doc_type":"tg", + "kw":"COMMENT,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"COMMENT", + "githuburl":"" + }, + { + "uri":"dws_16_0130.html", + "node_id":"en-us_topic_0000001772536500.xml", + "product_code":"dws", + "code":"279", + "des":"GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the attribute during migration.In MySQL, the keyword CONNECTION is used ", + "doc_type":"tg", + "kw":"CONNECTION,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CONNECTION", + "githuburl":"" + }, + { + "uri":"dws_16_0131.html", + "node_id":"en-us_topic_0000001819416213.xml", + "product_code":"dws", + "code":"280", + "des":"In MySQL, when using ALTER TABLE to add a column with the not null constraint, if no value is specified, a default value is inserted. However, an error will be reported a", + "doc_type":"tg", + "kw":"DEFAULT,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DEFAULT", + "githuburl":"" + }, + { + "uri":"dws_16_0132.html", + "node_id":"en-us_topic_0000001819336185.xml", + "product_code":"dws", + "code":"281", + "des":"DELAY_KEY_WRITE is valid only for MyISAM tables. It is used to delay updates until the table is closed. GaussDB(DWS) does not support table definition modification using ", + "doc_type":"tg", + "kw":"DELAY_KEY_WRITE,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DELAY_KEY_WRITE", + "githuburl":"" + }, + { + "uri":"dws_16_0133.html", + "node_id":"en-us_topic_0000001772696180.xml", + "product_code":"dws", + "code":"282", + "des":"ADB supports distribution keys. During DSC migration, the corresponding distribution keys are retained.InputOutput", + "doc_type":"tg", + "kw":"DISTRIBUTE BY,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DISTRIBUTE BY", + "githuburl":"" + }, + { + "uri":"dws_16_0134.html", + "node_id":"en-us_topic_0000001772536504.xml", + "product_code":"dws", + "code":"283", + "des":"DIRECTORY enables a tablespace to be created outside the data directory and index directory. It allows DATA DIRECTORY and INDEX DIRECTORY. GaussDB(DWS) does not support t", + "doc_type":"tg", + "kw":"DIRECTORY,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DIRECTORY", + "githuburl":"" + }, + { + "uri":"dws_16_0135.html", + "node_id":"en-us_topic_0000001819416217.xml", + "product_code":"dws", + "code":"284", + "des":"In MySQL, ENGINE specifies the storage engine for a table. When the storage engine is ARCHIVE, BLACKHOLE, CSV, FEDERATED, INNODB, MYISAM, MEMORY, MRG_MYISAM, NDB, NDBCLUS", + "doc_type":"tg", + "kw":"ENGINE,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ENGINE", + "githuburl":"" + }, + { + "uri":"dws_16_0136.html", + "node_id":"en-us_topic_0000001819336189.xml", + "product_code":"dws", + "code":"285", + "des":"For foreign key constraints in MySQL, GaussDB(DWS) does not support them modifying table definition. They will be deleted during DSC migration.InputOutput", + "doc_type":"tg", + "kw":"FOREIGN_KEY_CHECKS,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"FOREIGN_KEY_CHECKS", + "githuburl":"" + }, + { + "uri":"dws_16_0137.html", + "node_id":"en-us_topic_0000001772696184.xml", + "product_code":"dws", + "code":"286", + "des":"DSC supports the conversion of IF NOT EXISTS, which is reserved during the migration.InputOutput", + "doc_type":"tg", + "kw":"IF NOT EXISTS,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"IF NOT EXISTS", + "githuburl":"" + }, + { + "uri":"dws_16_0138.html", + "node_id":"en-us_topic_0000001772536508.xml", + "product_code":"dws", + "code":"287", + "des":"In the ADB, index_all='Y' is used to create the full-column index. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the a", + "doc_type":"tg", + "kw":"INDEX_ALL,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"INDEX_ALL", + "githuburl":"" + }, + { + "uri":"dws_16_0139.html", + "node_id":"en-us_topic_0000001819416225.xml", + "product_code":"dws", + "code":"288", + "des":"INSERT_METHOD specifies the table into which the row should be inserted. Use a value of FIRST or LAST to have inserts go to the first or last table, or a value of NO to p", + "doc_type":"tg", + "kw":"INSERT_METHOD,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"INSERT_METHOD", + "githuburl":"" + }, + { + "uri":"dws_16_0140.html", + "node_id":"en-us_topic_0000001819336193.xml", + "product_code":"dws", + "code":"289", + "des":"KEY_BLOCK_SIZE choices vary depending on the storage engine used for a table. For MyISAM tables, KEY_BLOCK_SIZE optionally specifies the size in bytes to be used for inde", + "doc_type":"tg", + "kw":"KEY_BLOCK_SIZE,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"KEY_BLOCK_SIZE", + "githuburl":"" + }, + { + "uri":"dws_16_0141.html", + "node_id":"en-us_topic_0000001772696188.xml", + "product_code":"dws", + "code":"290", + "des":"GaussDB(DWS) does not support the ALTER TABLEtbNameLOCK statement of MySQL, which will be deleted by DSC during migration.InputOutput", + "doc_type":"tg", + "kw":"LOCK,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LOCK", + "githuburl":"" + }, + { + "uri":"dws_16_0142.html", + "node_id":"en-us_topic_0000001772536512.xml", + "product_code":"dws", + "code":"291", + "des":"In MySQL, MAX_ROWS indicates the maximum number of rows that can be stored in a table. This attribute will be deleted during migration using DSC.InputOutput", + "doc_type":"tg", + "kw":"MAX_ROWS,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"MAX_ROWS", + "githuburl":"" + }, + { + "uri":"dws_16_0143.html", + "node_id":"en-us_topic_0000001819416229.xml", + "product_code":"dws", + "code":"292", + "des":"MIN_ROWS indicates the minimum number of rows that can be stored in a table. This attribute will be deleted during migration using DSC.InputOutput", + "doc_type":"tg", + "kw":"MIN_ROWS,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"MIN_ROWS", + "githuburl":"" + }, + { + "uri":"dws_16_0145.html", + "node_id":"en-us_topic_0000001819336201.xml", + "product_code":"dws", + "code":"293", + "des":"In MySQL, PACK_KEYS specifies the index compression mode in the MyISAM storage engine. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during m", + "doc_type":"tg", + "kw":"PACK_KEYS,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"PACK_KEYS", + "githuburl":"" + }, + { + "uri":"dws_16_0146.html", + "node_id":"en-us_topic_0000001772696192.xml", + "product_code":"dws", + "code":"294", + "des":"In MySQL, PARTITION BY is used to create partitioned tables. Currently, GaussDB(DWS) supports only range and list partitions in MySQL.Hash partitions of PARTITION BY are ", + "doc_type":"tg", + "kw":"PARTITION BY,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"PARTITION BY", + "githuburl":"" + }, + { + "uri":"dws_16_0147.html", + "node_id":"en-us_topic_0000001772536516.xml", + "product_code":"dws", + "code":"295", + "des":"In MySQL, PASSWORD indicates the user password. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during migration.InputOutput", + "doc_type":"tg", + "kw":"PASSWORD,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"PASSWORD", + "githuburl":"" + }, + { + "uri":"dws_16_0148.html", + "node_id":"en-us_topic_0000001819416233.xml", + "product_code":"dws", + "code":"296", + "des":"ROW_FORMAT defines the physical format in which the rows are stored. Row format choices vary depending on the storage engine used for the table. If you specify a row form", + "doc_type":"tg", + "kw":"ROW_FORMAT,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ROW_FORMAT", + "githuburl":"" + }, + { + "uri":"dws_16_0149.html", + "node_id":"en-us_topic_0000001819336205.xml", + "product_code":"dws", + "code":"297", + "des":"STATS_AUTO_RECALC specifies whether to automatically recalculate persistent statistics for an InnoDB table. GaussDB(DWS) does not support this attribute, which will be de", + "doc_type":"tg", + "kw":"STATS_AUTO_RECALC,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"STATS_AUTO_RECALC", + "githuburl":"" + }, + { + "uri":"dws_16_0150.html", + "node_id":"en-us_topic_0000001772696196.xml", + "product_code":"dws", + "code":"298", + "des":"In MySQL, STATS_PERSISTENT specifies whether to enable persistence statistics for an InnoDB table. The CREATE TABLE and ALTER TABLE statements can be used to enable persi", + "doc_type":"tg", + "kw":"STATS_PERSISTENT,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"STATS_PERSISTENT", + "githuburl":"" + }, + { + "uri":"dws_16_0151.html", + "node_id":"en-us_topic_0000001772536520.xml", + "product_code":"dws", + "code":"299", + "des":"STATS_SAMPLE_PAGES specifies the number of index pages to sample when cardinality and other statistics for an indexed column are estimated. DSC will delete this attribute", + "doc_type":"tg", + "kw":"STATS_SAMPLE_PAGES,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"STATS_SAMPLE_PAGES", + "githuburl":"" + }, + { + "uri":"dws_16_0152.html", + "node_id":"en-us_topic_0000001819416237.xml", + "product_code":"dws", + "code":"300", + "des":"UNION is a table creation parameter of the MERGE storage engine. Creating a table using this keyword is similar to creating a common view. The created table logically com", + "doc_type":"tg", + "kw":"UNION,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"UNION", + "githuburl":"" + }, + { + "uri":"dws_16_0153.html", + "node_id":"en-us_topic_0000001819336209.xml", + "product_code":"dws", + "code":"301", + "des":"WITH AS is used in GaussDB(DWS) to declare one or more subqueries that can be referenced by name in the main query. It is equivalent to a temporary table. DSC supports th", + "doc_type":"tg", + "kw":"WITH AS,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"WITH AS", + "githuburl":"" + }, + { + "uri":"dws_16_0154.html", + "node_id":"en-us_topic_0000001772696200.xml", + "product_code":"dws", + "code":"302", + "des":"MySQL uses the CHANGE keyword to change column names and data types and set NOT NULL constraints. DSC will perform adaptation based on GaussDB(DWS) features during migrat", + "doc_type":"tg", + "kw":"CHANGE (Column Modification),Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CHANGE (Column Modification)", + "githuburl":"" + }, + { + "uri":"dws_16_0155.html", + "node_id":"en-us_topic_0000001772536524.xml", + "product_code":"dws", + "code":"303", + "des":"Specifies an expression producing a Boolean result which new or updated rows must satisfy for an insert or update operation to succeed. Expressions evaluating to TRUE or ", + "doc_type":"tg", + "kw":"CHECK Constraint,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"CHECK Constraint", + "githuburl":"" + }, + { + "uri":"dws_16_0156.html", + "node_id":"en-us_topic_0000001819416241.xml", + "product_code":"dws", + "code":"304", + "des":"Both GaussDB(DWS) and MySQL support using the DROP statement to delete tables. However, GaussDB(DWS) does not support the RESTRICT | CASCADE keyword in the DROP statement", + "doc_type":"tg", + "kw":"DROP (Table Deletion),Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DROP (Table Deletion)", + "githuburl":"" + }, + { + "uri":"dws_16_0157.html", + "node_id":"en-us_topic_0000001819336213.xml", + "product_code":"dws", + "code":"305", + "des":"MySQL databases support CREATE TABLE. LIKE is a method with which a table is created by cloning the old table structure, It is also supported by GaussDB(DWS). DSC will ad", + "doc_type":"tg", + "kw":"LIKE (Table Cloning),Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LIKE (Table Cloning)", + "githuburl":"" + }, + { + "uri":"dws_16_0158.html", + "node_id":"en-us_topic_0000001772696204.xml", + "product_code":"dws", + "code":"306", + "des":"MySQL uses the MODIFY keyword to change column data types and set NOT NULL constraints. DSC will perform adaptation based on GaussDB(DWS) features during migration.InputO", + "doc_type":"tg", + "kw":"MODIFY (Modifying a Cloumn),Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"MODIFY (Modifying a Cloumn)", + "githuburl":"" + }, + { + "uri":"dws_16_0159.html", + "node_id":"en-us_topic_0000001772536528.xml", + "product_code":"dws", + "code":"307", + "des":"In MySQL, the TABLE keyword can be omitted when the TRUNCATE statement is used to delete table data. GaussDB(DWS) does not support this usage. In addition, DSC will add C", + "doc_type":"tg", + "kw":"TRUNCATE (Table Deletion),Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"TRUNCATE (Table Deletion)", + "githuburl":"" + }, + { + "uri":"dws_16_0160.html", + "node_id":"en-us_topic_0000001819416245.xml", + "product_code":"dws", + "code":"308", + "des":"GaussDB(DWS) supports the creation of roundrobin tables. You can set the table.type in Table 1. Set table.type=ROUND-ROBIN.InputOutput", + "doc_type":"tg", + "kw":"ROUNDROBIN Table,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ROUNDROBIN Table", + "githuburl":"" + }, + { + "uri":"dws_16_0161.html", + "node_id":"en-us_topic_0000001819336217.xml", + "product_code":"dws", + "code":"309", + "des":"The statement for renaming a table in MySQL is slightly different from that in GaussDB(DWS). DSC will perform adaptation based on GaussDB(DWS) features during migration.C", + "doc_type":"tg", + "kw":"RENAME (Table Renaming),Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"RENAME (Table Renaming)", + "githuburl":"" + }, + { + "uri":"dws_16_0162.html", + "node_id":"en-us_topic_0000001772696208.xml", + "product_code":"dws", + "code":"310", + "des":"In MySQL, the COLUMN keyword can be omitted when the ALTER statement is used to set the default value of a column. DSC will perform adaptation based on GaussDB(DWS) featu", + "doc_type":"tg", + "kw":"SET|DROP COLUMN DEFAULT VALUE,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SET|DROP COLUMN DEFAULT VALUE", + "githuburl":"" + }, + { + "uri":"dws_16_0163.html", + "node_id":"en-us_topic_0000001772536532.xml", + "product_code":"dws", + "code":"311", + "des":"In GaussDB(DWS), reserved keywords must be enclosed in double quotation marks when they are used as column names. The following reserved keywords are supported: desc, che", + "doc_type":"tg", + "kw":"Renaming a Column,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Renaming a Column", + "githuburl":"" + }, + { + "uri":"dws_16_0164.html", + "node_id":"en-us_topic_0000001819416249.xml", + "product_code":"dws", + "code":"312", + "des":"GaussDB(DWS) supports column-store table compression, but does not support row-store table compression. DSC performs migration based on GaussDB(DWS) features.Compression ", + "doc_type":"tg", + "kw":"Row-Store/Column-Store Table Compression,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Row-Store/Column-Store Table Compression", + "githuburl":"" + }, + { + "uri":"dws_16_0165.html", + "node_id":"en-us_topic_0000001819336221.xml", + "product_code":"dws", + "code":"313", + "des":"The statements for adding and deleting columns in MySQL are different from those in GaussDB(DWS). DSC will perform adaptation based on GaussDB(DWS) features during migrat", + "doc_type":"tg", + "kw":"Adding/Deleting a Column,Table (Optional Parameters and Operations),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Adding/Deleting a Column", + "githuburl":"" + }, + { + "uri":"dws_16_0166.html", + "node_id":"en-us_topic_0000001772696212.xml", + "product_code":"dws", + "code":"314", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Indexes", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0167.html", + "node_id":"en-us_topic_0000001772536536.xml", + "product_code":"dws", + "code":"315", + "des":"GaussDB(DWS) does not support the combination of unique indexes (constraints) and primary key constraints. DSC will perform adaptation based on GaussDB(DWS) features duri", + "doc_type":"tg", + "kw":"Unique Indexes,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Unique Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0168.html", + "node_id":"en-us_topic_0000001819416253.xml", + "product_code":"dws", + "code":"316", + "des":"GaussDB(DWS) does not support prefix indexes or inline normal indexes. DSC will replace these indexes with normal indexes based on GaussDB(DWS) features.Inline normal/pre", + "doc_type":"tg", + "kw":"Normal and Prefix Indexes,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Normal and Prefix Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0169.html", + "node_id":"en-us_topic_0000001819336225.xml", + "product_code":"dws", + "code":"317", + "des":"GaussDB(DWS) does not support hash indexes. DSC will replace these indexes with normal indexes based on GaussDB(DWS) features.Inline hash indexesInputCREATE TABLE `public", + "doc_type":"tg", + "kw":"Hash Indexes,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Hash Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0170.html", + "node_id":"en-us_topic_0000001772696216.xml", + "product_code":"dws", + "code":"318", + "des":"GaussDB(DWS) supports B-tree indexes, but the position of the USING BTREE keyword in a statement is different from that in MySQL. DSC will perform adaptation based on Gau", + "doc_type":"tg", + "kw":"B-tree Indexes,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"B-tree Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0171.html", + "node_id":"en-us_topic_0000001772536540.xml", + "product_code":"dws", + "code":"319", + "des":"GaussDB(DWS) does not support spatial indexes. DSC will perform adaptation based on GaussDB(DWS) features during migration.Inline spatial indexInputCREATE TABLE `public`.", + "doc_type":"tg", + "kw":"Spatial Indexes,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Spatial Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0172.html", + "node_id":"en-us_topic_0000001819416257.xml", + "product_code":"dws", + "code":"320", + "des":"GaussDB(DWS) does not support full-text indexes. DSC will perform adaptation based on GaussDB(DWS) features during migration.Inline full-text indexInput## A.\nCREATE TABLE", + "doc_type":"tg", + "kw":"Full-Text Indexes,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Full-Text Indexes", + "githuburl":"" + }, + { + "uri":"dws_16_0173.html", + "node_id":"en-us_topic_0000001819336229.xml", + "product_code":"dws", + "code":"321", + "des":"MySQL supports both DROP INDEX and ALTER TABLE DROP INDEX for deleting indexes. DSC will perform adaptation based on GaussDB(DWS) features during migration.DROP INDEXInpu", + "doc_type":"tg", + "kw":"Deleting an Index,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Deleting an Index", + "githuburl":"" + }, + { + "uri":"dws_16_0174.html", + "node_id":"en-us_topic_0000001772696220.xml", + "product_code":"dws", + "code":"322", + "des":"DSC supports renaming indexes. Prefix a table name to an index name to prevent name conflicts. (Only DDL statements with specific index names can be created. Currently, t", + "doc_type":"tg", + "kw":"Renaming an Index,Indexes,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Renaming an Index", + "githuburl":"" + }, + { + "uri":"dws_16_0175.html", + "node_id":"en-us_topic_0000001772536544.xml", + "product_code":"dws", + "code":"323", + "des":"To comment out a single line, MySQL uses # or --, and GaussDB(DWS) uses --. DSC will replace # with -- for commenting out a single line during migration.InputOutput", + "doc_type":"tg", + "kw":"Comment,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Comment", + "githuburl":"" + }, + { + "uri":"dws_16_0176.html", + "node_id":"en-us_topic_0000001819416265.xml", + "product_code":"dws", + "code":"324", + "des":"In MySQL, DATABASE is a schema object, which is equivalent to the SCHEMA of Oracle and GaussDB(DWS). DSC supports the following two scenarios:Database creationInputcreate", + "doc_type":"tg", + "kw":"Databases,Schema Objects and Data Definition Language (DDL),Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Databases", + "githuburl":"" + }, + { + "uri":"dws_16_0177.html", + "node_id":"en-us_topic_0000001819336233.xml", + "product_code":"dws", + "code":"325", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Data Manipulation Language (DML)", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Data Manipulation Language (DML)", + "githuburl":"" + }, + { + "uri":"dws_16_0178.html", + "node_id":"en-us_topic_0000001772696224.xml", + "product_code":"dws", + "code":"326", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"SELECT", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SELECT", + "githuburl":"" + }, + { + "uri":"dws_16_0179.html", + "node_id":"en-us_topic_0000001772536548.xml", + "product_code":"dws", + "code":"327", + "des":"Aliases in MySQL contain single quotation marks, which are not supported by GaussDB(DWS). DSC changes them to double quotation marks during migration.InputOutputAliases a", + "doc_type":"tg", + "kw":"Quotation Marks,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Quotation Marks", + "githuburl":"" + }, + { + "uri":"dws_16_0180.html", + "node_id":"en-us_topic_0000001819416269.xml", + "product_code":"dws", + "code":"328", + "des":"In MySQL, the interval expression format is INTERVAL N, which is not supported by GaussDB(DWS) and needs to be converted to INTERVAL'N'.InputOutput", + "doc_type":"tg", + "kw":"INTERVAL,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"INTERVAL", + "githuburl":"" + }, + { + "uri":"dws_16_0181.html", + "node_id":"en-us_topic_0000001819336237.xml", + "product_code":"dws", + "code":"329", + "des":"In MySQL, in a division expression, if the divisor is 0, null is returned. GaussDB(DWS) reports an error. Therefore, the division expression is converted by adding an if ", + "doc_type":"tg", + "kw":"Division Expressions,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Division Expressions", + "githuburl":"" + }, + { + "uri":"dws_16_0182.html", + "node_id":"en-us_topic_0000001772696228.xml", + "product_code":"dws", + "code":"330", + "des":"During MySQL/ADB group query, non-group columns can be queried. During GaussDB(DWS) group query, only group columns and aggregate functions can be queried, and if non-gro", + "doc_type":"tg", + "kw":"GROUP BY Conversion,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"GROUP BY Conversion", + "githuburl":"" + }, + { + "uri":"dws_16_0183.html", + "node_id":"en-us_topic_0000001772536552.xml", + "product_code":"dws", + "code":"331", + "des":"group by column with rollup in MySQL needs to be converted to group by rollup (column) in GaussDB(DWS).InputOutput", + "doc_type":"tg", + "kw":"ROLLUP,SELECT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ROLLUP", + "githuburl":"" + }, + { + "uri":"dws_16_0184.html", + "node_id":"en-us_topic_0000001819416273.xml", + "product_code":"dws", + "code":"332", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"INSERT", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"INSERT", + "githuburl":"" + }, + { + "uri":"dws_16_0185.html", + "node_id":"en-us_topic_0000001819336241.xml", + "product_code":"dws", + "code":"333", + "des":"MySQL uses HIGH_PRIORITY will override the effect of the LOW_PRIORITY option.InputOutput", + "doc_type":"tg", + "kw":"HIGH_PRIORITY,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"HIGH_PRIORITY", + "githuburl":"" + }, + { + "uri":"dws_16_0186.html", + "node_id":"en-us_topic_0000001772696232.xml", + "product_code":"dws", + "code":"334", + "des":"When the LOW_PRIORITY modifier is used, execution of INSERT is delayed.InputOutput", + "doc_type":"tg", + "kw":"LOW_PRIORITY,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LOW_PRIORITY", + "githuburl":"" + }, + { + "uri":"dws_16_0187.html", + "node_id":"en-us_topic_0000001772536556.xml", + "product_code":"dws", + "code":"335", + "des":"When inserting into a partitioned table, you can control which partitions and subpartitions accept new rows.InputOutput", + "doc_type":"tg", + "kw":"PARTITION,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"PARTITION", + "githuburl":"" + }, + { + "uri":"dws_16_0188.html", + "node_id":"en-us_topic_0000001819416277.xml", + "product_code":"dws", + "code":"336", + "des":"In MySQL 5.7, the DELAYED keyword is recognized but ignored by the server.InputOutput", + "doc_type":"tg", + "kw":"DELAYED,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DELAYED", + "githuburl":"" + }, + { + "uri":"dws_16_0189.html", + "node_id":"en-us_topic_0000001819336245.xml", + "product_code":"dws", + "code":"337", + "des":"When the IGNORE modifier is used, errors that occur during INSERT execution are ignored.InputOutput", + "doc_type":"tg", + "kw":"IGNORE,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"IGNORE", + "githuburl":"" + }, + { + "uri":"dws_16_0190.html", + "node_id":"en-us_topic_0000001772696236.xml", + "product_code":"dws", + "code":"338", + "des":"INSERT statements that use the VALUES syntax can insert multiple lines, separated by commas.InputOutput", + "doc_type":"tg", + "kw":"VALUES,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"VALUES", + "githuburl":"" + }, + { + "uri":"dws_16_0191.html", + "node_id":"en-us_topic_0000001772536560.xml", + "product_code":"dws", + "code":"339", + "des":"INSERT uses the ON DUPLICATE KEY UPDATE clause to update existing rows.InputOutput", + "doc_type":"tg", + "kw":"ON DUPLICATE KEY UPDATE,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ON DUPLICATE KEY UPDATE", + "githuburl":"" + }, + { + "uri":"dws_16_0192.html", + "node_id":"en-us_topic_0000001819416281.xml", + "product_code":"dws", + "code":"340", + "des":"MySQL INSERT...SET statement inserts rows based on explicitly specified values.InputOutput", + "doc_type":"tg", + "kw":"SET,INSERT,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SET", + "githuburl":"" + }, + { + "uri":"dws_16_0193.html", + "node_id":"en-us_topic_0000001819336249.xml", + "product_code":"dws", + "code":"341", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"UPDATE", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"UPDATE", + "githuburl":"" + }, + { + "uri":"dws_16_0194.html", + "node_id":"en-us_topic_0000001772696240.xml", + "product_code":"dws", + "code":"342", + "des":"With the LOW_PRIORITY modifier, execution of UPDATE is delayed.InputOutput", + "doc_type":"tg", + "kw":"LOW_PRIORITY,UPDATE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LOW_PRIORITY", + "githuburl":"" + }, + { + "uri":"dws_16_0195.html", + "node_id":"en-us_topic_0000001772536564.xml", + "product_code":"dws", + "code":"343", + "des":"In MySQL, if an UPDATE statement includes an ORDER BY clause, the rows will be updated in the order specified by the clause.InputOutput", + "doc_type":"tg", + "kw":"ORDER BY,UPDATE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"ORDER BY", + "githuburl":"" + }, + { + "uri":"dws_16_0196.html", + "node_id":"en-us_topic_0000001819416285.xml", + "product_code":"dws", + "code":"344", + "des":"UPDATE LIMIT syntax can be used to limit the scope. A clause is a limit on row matching. As long as the rows that satisfy the clause are found, the statements will stop, ", + "doc_type":"tg", + "kw":"LIMIT,UPDATE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LIMIT", + "githuburl":"" + }, + { + "uri":"dws_16_0197.html", + "node_id":"en-us_topic_0000001819336253.xml", + "product_code":"dws", + "code":"345", + "des":"With the IGNORE modifier, the UPDATE statement does not abort even if errors occur during execution.InputOutput", + "doc_type":"tg", + "kw":"IGNORE,UPDATE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"IGNORE", + "githuburl":"" + }, + { + "uri":"dws_16_0198.html", + "node_id":"en-us_topic_0000001772696244.xml", + "product_code":"dws", + "code":"346", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"REPLACE", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"REPLACE", + "githuburl":"" + }, + { + "uri":"dws_16_0199.html", + "node_id":"en-us_topic_0000001772536568.xml", + "product_code":"dws", + "code":"347", + "des":"MySQL REPLACE supports the use of LOW_PRIORITY, which is converted by the Migration tool.InputOutput", + "doc_type":"tg", + "kw":"LOW_PRIORITY,REPLACE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LOW_PRIORITY", + "githuburl":"" + }, + { + "uri":"dws_16_0200.html", + "node_id":"en-us_topic_0000001819416289.xml", + "product_code":"dws", + "code":"348", + "des":"MySQL REPLACE supports explicit partitioning selection using the PARTITION keyword and a comma-separated name list for partitions, subpartitions, or both.InputOutput", + "doc_type":"tg", + "kw":"PARTITION,REPLACE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"PARTITION", + "githuburl":"" + }, + { + "uri":"dws_16_0201.html", + "node_id":"en-us_topic_0000001819336257.xml", + "product_code":"dws", + "code":"349", + "des":"DELAYED INSERT and REPLACE operations were deprecated in MySQL 5.6. In MySQL 5.7, DELAYED was not supported. The server recognizes but ignores the DELAYED keyword, handle", + "doc_type":"tg", + "kw":"DELAYED,REPLACE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"DELAYED", + "githuburl":"" + }, + { + "uri":"dws_16_0202.html", + "node_id":"en-us_topic_0000001772696248.xml", + "product_code":"dws", + "code":"350", + "des":"MySQL REPLACE supports a statement to insert or delete multiple values, separated by commas.InputOutput", + "doc_type":"tg", + "kw":"VALUES,REPLACE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"VALUES", + "githuburl":"" + }, + { + "uri":"dws_16_0203.html", + "node_id":"en-us_topic_0000001772536572.xml", + "product_code":"dws", + "code":"351", + "des":"MySQL REPLACE supports the use of SET settings, which the Migration tool will convert.InputOutput", + "doc_type":"tg", + "kw":"SET,REPLACE,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SET", + "githuburl":"" + }, + { + "uri":"dws_16_0204.html", + "node_id":"en-us_topic_0000001819416293.xml", + "product_code":"dws", + "code":"352", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Transaction Management and Database Management", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Transaction Management and Database Management", + "githuburl":"" + }, + { + "uri":"dws_16_0205.html", + "node_id":"en-us_topic_0000001819336261.xml", + "product_code":"dws", + "code":"353", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Transaction Management", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Transaction Management", + "githuburl":"" + }, + { + "uri":"dws_16_0206.html", + "node_id":"en-us_topic_0000001772696252.xml", + "product_code":"dws", + "code":"354", + "des":"DSC will perform adaptation based on GaussDB features during MySQL transaction statement migration.InputOutput", + "doc_type":"tg", + "kw":"TRANSACTION,Transaction Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"TRANSACTION", + "githuburl":"" + }, + { + "uri":"dws_16_0207.html", + "node_id":"en-us_topic_0000001772536576.xml", + "product_code":"dws", + "code":"355", + "des":"DSC will perform adaptation based on GaussDB features during the migration of MySQL table locking statements which are used in transaction processing.InputOutput", + "doc_type":"tg", + "kw":"LOCK,Transaction Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"LOCK", + "githuburl":"" + }, + { + "uri":"dws_16_0208.html", + "node_id":"en-us_topic_0000001819416297.xml", + "product_code":"dws", + "code":"356", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"tg", + "kw":"Database Management", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Database Management", + "githuburl":"" + }, + { + "uri":"dws_16_0209.html", + "node_id":"en-us_topic_0000001819336265.xml", + "product_code":"dws", + "code":"357", + "des":"DSC will replace MySQL SET CHARACTER SET with SET SESSION NAMES during migration. The following table lists character set mapping.InputOutput", + "doc_type":"tg", + "kw":"SET CHARACTER,Database Management,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"SET CHARACTER", "githuburl":"" }, { "uri":"dws_mt_0104.html", + "node_id":"en-us_topic_0000001772696256.xml", "product_code":"dws", - "code":"205", + "code":"358", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Oracle Syntax Migration", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Oracle Syntax Migration", "githuburl":"" }, { "uri":"dws_mt_0105.html", + "node_id":"en-us_topic_0000001772536580.xml", "product_code":"dws", - "code":"206", + "code":"359", "des":"This section lists the Oracle features supported by the syntax migration tool, and provides the Oracle syntax and the equivalent GaussDB(DWS) syntax for each feature. The", "doc_type":"tg", "kw":"Overview,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Overview", "githuburl":"" }, { "uri":"dws_mt_0106.html", + "node_id":"en-us_topic_0000001819416301.xml", "product_code":"dws", - "code":"207", + "code":"360", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Schema Objects", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Schema Objects", "githuburl":"" }, { "uri":"dws_mt_0108.html", + "node_id":"en-us_topic_0000001819336269.xml", "product_code":"dws", - "code":"208", - "des":"The Oracle CREATE TABLE statement is used to create new tables. The target database supports Oracle CREATE TABLE without any migration.The Oracle ALTER TABLE statement is", + "code":"361", + "des":"The CREATE TABLE statement in Oracle databases is used to create new tables. GaussDB(DWS) also supports this statement. So it does not need to be migrated.The ALTER TABLE", "doc_type":"tg", "kw":"Tables,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Tables", "githuburl":"" }, { "uri":"dws_mt_0109.html", + "node_id":"en-us_topic_0000001772696260.xml", "product_code":"dws", - "code":"209", + "code":"362", "des":"GaussDB(DWS) does not support GLOBAL TEMPORARY TABLE, and it will be migrated to LOCAL TEMPORARY TABLE.ON COMMIT DELETE ROWS is also not supported, and will be migrated t", "doc_type":"tg", "kw":"Temporary Tables,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Temporary Tables", "githuburl":"" }, { "uri":"dws_mt_0212.html", + "node_id":"en-us_topic_0000001772536584.xml", "product_code":"dws", - "code":"210", + "code":"363", "des":"Global temporary tables are converted to local temporary tables.Input - GLOBAL TEMPORARY TABLEOutput", "doc_type":"tg", "kw":"Global Temporary Tables,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Global Temporary Tables", "githuburl":"" }, { "uri":"dws_mt_0110.html", + "node_id":"en-us_topic_0000001819416305.xml", "product_code":"dws", - "code":"211", + "code":"364", "des":"When an index is created in GaussDB(DWS), a schema name cannot be specified along with the index name. The index will be automatically created in the schema where the ind", "doc_type":"tg", - "kw":"Index Migration,Schema Objects,Tool Guide", - "title":"Index Migration", + "kw":"Indexes,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], + "title":"Indexes", "githuburl":"" }, { "uri":"dws_mt_0111.html", + "node_id":"en-us_topic_0000001819336273.xml", "product_code":"dws", - "code":"212", + "code":"365", "des":"A view is a logical table that is based on one or more tables or views. A view itself contains no data.In the source file, if the table names are not qualified with the s", "doc_type":"tg", "kw":"Views,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Views", "githuburl":"" }, { "uri":"dws_mt_0112.html", + "node_id":"en-us_topic_0000001772696264.xml", "product_code":"dws", - "code":"213", + "code":"366", "des":"A sequence is an Oracle object used to generate a number sequence. This can be useful when you need to create an autonumber column to act as a primary key.If MigSupportSe", "doc_type":"tg", "kw":"Sequences,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Sequences", "githuburl":"" }, { "uri":"dws_mt_0113.html", + "node_id":"en-us_topic_0000001772536588.xml", "product_code":"dws", - "code":"214", + "code":"367", "des":"In Oracle, the DROP TABLE statement moves a table to the recycle bin. The PURGE statement is used to remove a table or index from the recycle bin and release all of the s", "doc_type":"tg", "kw":"PURGE,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"PURGE", "githuburl":"" }, { "uri":"dws_mt_0114.html", + "node_id":"en-us_topic_0000001819416309.xml", "product_code":"dws", - "code":"215", + "code":"368", "des":"DSC supports GaussDB(DWS) keywords, such as NAME, LIMIT, OWNER, KEY, and CAST. These keywords must be enclosed in double quotation marks.The keywords NAME, VERSION, LABEL", "doc_type":"tg", "kw":"Database Keywords,Schema Objects,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Database Keywords", "githuburl":"" }, { "uri":"dws_07_6814.html", + "node_id":"en-us_topic_0000001819336277.xml", "product_code":"dws", - "code":"216", + "code":"369", "des":"Input – COMPRESS PhraseOutput", "doc_type":"tg", "kw":"COMPRESS Phrase,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"COMPRESS Phrase", "githuburl":"" }, { "uri":"dws_07_6815.html", + "node_id":"en-us_topic_0000001772696268.xml", "product_code":"dws", - "code":"217", + "code":"370", "des":"There is a configuration parameter that is introduced for this feature named BitmapIndexSupport which default value is comment, then the sample input and output are as fo", "doc_type":"tg", "kw":"Bitmap Index,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Bitmap Index", "githuburl":"" }, { "uri":"dws_07_6816.html", + "node_id":"en-us_topic_0000001772536592.xml", "product_code":"dws", - "code":"218", + "code":"371", "des":"Input – custom tablespaceOutput", "doc_type":"tg", "kw":"Custom Tablespace,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Custom Tablespace", "githuburl":"" }, { "uri":"dws_07_6817.html", + "node_id":"en-us_topic_0000001819416317.xml", "product_code":"dws", - "code":"219", - "des":"Supplemental columns can be recorded in redo log files. The process of recording these additional columns is called supplemental logging. The Oracle database supports thi", + "code":"372", + "des":"Supplemental columns can be recorded in redo log files. The process of recording these additional columns is called supplemental logging. Oracle supports this function, b", "doc_type":"tg", "kw":"Supplemental Log Data,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Supplemental Log Data", "githuburl":"" }, { "uri":"dws_07_6818.html", + "node_id":"en-us_topic_0000001819336281.xml", "product_code":"dws", - "code":"220", + "code":"373", "des":"\"Data type LONG RAW\" is not supported in the CREATE TABLE statement. LONG RAW data type needs to be replaced with Byte.InputOutput", "doc_type":"tg", "kw":"LONG RAW,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"LONG RAW", "githuburl":"" }, { "uri":"dws_07_6819.html", + "node_id":"en-us_topic_0000001772696272.xml", "product_code":"dws", - "code":"221", + "code":"374", "des":"SYS_GUID is a built-in function which returns the Global Unique Identifier (GUID) for a row in a table. It accepts no arguments and returns a RAW value of 16 bytes.InputO", "doc_type":"tg", "kw":"SYS_GUID,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"SYS_GUID", "githuburl":"" }, { "uri":"dws_mt_0115.html", + "node_id":"en-us_topic_0000001772536600.xml", "product_code":"dws", - "code":"222", + "code":"375", "des":"This section describes the migration syntax of Oracle DML. The migration syntax decides how the keywords/features are migrated.For details, see the following topics:SELEC", "doc_type":"tg", "kw":"DML,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"DML", "githuburl":"" }, { "uri":"dws_mt_0128.html", + "node_id":"en-us_topic_0000001819416321.xml", "product_code":"dws", - "code":"223", + "code":"376", "des":"This section contains the migration syntax of Oracle Pseudo Columns. The migration syntax decides how the keywords/features are migrated.A pseudo column is similar to a t", "doc_type":"tg", "kw":"Pseudo Columns,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Pseudo Columns", "githuburl":"" }, { "uri":"dws_mt_0132.html", + "node_id":"en-us_topic_0000001819336285.xml", "product_code":"dws", - "code":"224", + "code":"377", "des":"This section describes the migration syntax of Oracle OUTER JOIN. The migration syntax determines how the keywords/features are migrated.An OUTER JOIN returns all rows th", "doc_type":"tg", "kw":"OUTER JOIN,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"OUTER JOIN", "githuburl":"" }, { "uri":"dws_mt_0215.html", + "node_id":"en-us_topic_0000001772696284.xml", "product_code":"dws", - "code":"225", - "des":"Join is supported in Gauss 18.2.0, so parameter supportJoinOperatoris added.OUTER QUERY (+)can be migrated when supportJoinOperatoris set to false.Input-OUTER QUERY(+)Out", + "code":"378", + "des":"Join is supported by GaussDB(DWS), so parameter supportJoinOperatoris added.OUTER QUERY (+)can be migrated when supportJoinOperatoris set to false.Input-OUTER QUERY(+)Out", "doc_type":"tg", "kw":"OUTER QUERY (+),Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"OUTER QUERY (+)", "githuburl":"" }, { "uri":"dws_mt_0216.html", + "node_id":"en-us_topic_0000001772536604.xml", "product_code":"dws", - "code":"226", + "code":"379", "des":"Input-CONNECT BYOutputInput - CONNECT BY multiple tablesThe syntax shows the relationship between each child row and its parent row. It uses the CONNECT BY xxx PRIOR clau", "doc_type":"tg", "kw":"CONNECT BY,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"CONNECT BY", "githuburl":"" }, { "uri":"dws_mt_0133.html", + "node_id":"en-us_topic_0000001819416325.xml", "product_code":"dws", - "code":"227", + "code":"380", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"System Functions", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"System Functions", "githuburl":"" }, { "uri":"dws_mt_0135.html", + "node_id":"en-us_topic_0000001819336293.xml", "product_code":"dws", - "code":"228", + "code":"381", "des":"This section describes the following date functions:ADD_MONTHSDATE_TRUNCLAST_DAYMONTHS_BETWEENSYSTIMESTAMPADD_MONTHS is an Oracle system function and is not implicitly su", "doc_type":"tg", "kw":"Date Functions,System Functions,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Date Functions", "githuburl":"" }, { "uri":"dws_mt_0136.html", + "node_id":"en-us_topic_0000001772696288.xml", "product_code":"dws", - "code":"229", + "code":"382", "des":"This section describes the following LOB functions:DBMS_LOB.APPENDDBMS_LOB.COMPAREDBMS_LOB.CREATETEMPORARYDBMS_LOB.INSTRDBMS_LOB.SUBSTRDBMS_LOB.APPEND function appends th", "doc_type":"tg", "kw":"LOB Functions,System Functions,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"LOB Functions", "githuburl":"" }, { "uri":"dws_mt_0137.html", + "node_id":"en-us_topic_0000001772536612.xml", "product_code":"dws", - "code":"230", + "code":"383", "des":"This section describes the following string functions:LISTAGGSTRAGGWM_CONCATNVL2 and REPLACEQUOTELISTAGG is used to order data in columns within each group specified in t", "doc_type":"tg", "kw":"String Functions,System Functions,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"String Functions", "githuburl":"" }, { "uri":"dws_mt_0138.html", + "node_id":"en-us_topic_0000001819416329.xml", "product_code":"dws", - "code":"231", + "code":"384", "des":"Analytical functions compute an aggregate value based on a group of rows. They differ from aggregate functions in that they return multiple rows for each group. Analytica", "doc_type":"tg", "kw":"Analytical Functions,System Functions,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Analytical Functions", "githuburl":"" }, { "uri":"dws_mt_0139.html", + "node_id":"en-us_topic_0000001819336297.xml", "product_code":"dws", - "code":"232", + "code":"385", "des":"Regular expressions specify patterns to match strings using standardized syntax conventions. In Oracle, regular expressions are implemented using a set of SQL functions t", "doc_type":"tg", "kw":"Regular Expression Functions,System Functions,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Regular Expression Functions", "githuburl":"" }, { "uri":"dws_mt_0141.html", + "node_id":"en-us_topic_0000001772536616.xml", "product_code":"dws", - "code":"233", + "code":"386", "des":"This section describes the migration syntax of Oracle PL/SQL. The migration syntax determines how the keywords and features are migrated.PL/SQL combines the procedural fe", "doc_type":"tg", "kw":"PL/SQL,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"PL/SQL", "githuburl":"" }, { "uri":"dws_mt_0155.html", + "node_id":"en-us_topic_0000001819416333.xml", "product_code":"dws", - "code":"234", + "code":"387", "des":"This section descripes the migration syntax of Oracle PL/SQL Collections. The migration syntax decides how the keywords/features are migrated.A user-defined type (UDT) is", "doc_type":"tg", "kw":"PL/SQL Collections (Using User-Defined Types),Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"PL/SQL Collections (Using User-Defined Types)", "githuburl":"" }, { "uri":"dws_mt_0156.html", + "node_id":"en-us_topic_0000001819336301.xml", "product_code":"dws", - "code":"235", + "code":"388", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"PL/SQL Packages", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"PL/SQL Packages", "githuburl":"" }, { "uri":"dws_mt_0158.html", + "node_id":"en-us_topic_0000001772696296.xml", "product_code":"dws", - "code":"236", + "code":"389", "des":"Packages are schema objects that group logically related PL/SQL types, variables, functions and procedures. In Oracle, each package consists of two parts: package specifi", "doc_type":"tg", "kw":"Packages,PL/SQL Packages,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Packages", "githuburl":"" }, { "uri":"dws_mt_0159.html", + "node_id":"en-us_topic_0000001772536624.xml", "product_code":"dws", - "code":"237", + "code":"390", "des":"Package variables are available in Oracle packages that allow variables to retain all the functions and procedures in the package. DSC uses customized functions to help G", "doc_type":"tg", "kw":"Package Variables,PL/SQL Packages,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Package Variables", "githuburl":"" }, { "uri":"dws_mt_0301.html", + "node_id":"en-us_topic_0000001819416341.xml", "product_code":"dws", - "code":"238", + "code":"391", "des":"The package specification is migrated as a schema named after the package and the procedures and functions in the package body is migrated as Packagename.procedurenameand", "doc_type":"tg", "kw":"Splitting Packages,PL/SQL Packages,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Splitting Packages", "githuburl":"" }, { "uri":"dws_mt_0302.html", + "node_id":"en-us_topic_0000001819336305.xml", "product_code":"dws", - "code":"239", + "code":"392", "des":"REF Cursor is a data type that can store the database cursor values and is used to return query results. DSC supports migration of REF CURSOR. The example below shows how", "doc_type":"tg", "kw":"REF CURSOR,PL/SQL Packages,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"REF CURSOR", "githuburl":"" }, { "uri":"dws_mt_0221.html", + "node_id":"en-us_topic_0000001772696304.xml", "product_code":"dws", - "code":"240", - "des":"The pacakge declaration is miagrated as a schema named after the package. The migration can be performed after pkgSchemaNaming is set to false.Input – Create schema for P", + "code":"393", + "des":"The package declaration is migrated as a schema named after the package. The migration can be performed after pkgSchemaNaming is set to false.Input – Create schema for Pa", "doc_type":"tg", "kw":"Creating a Schema for Package,PL/SQL Packages,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Creating a Schema for Package", "githuburl":"" }, { "uri":"dws_mt_0303.html", + "node_id":"en-us_topic_0000001772536628.xml", "product_code":"dws", - "code":"241", + "code":"394", "des":"REF CURSOR is defined as a return parameter.It can be migrated after plsqlCollectionis set tovarray.Input - VARRAYOutput", "doc_type":"tg", "kw":"VARRAY,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"VARRAY", "githuburl":"" }, { "uri":"dws_mt_0304.html", + "node_id":"en-us_topic_0000001819416345.xml", "product_code":"dws", - "code":"242", - "des":"This feature is used to give privileges to users for specific packages. As GaussDB does not support packages, all the procedures and functions defined in the specific pac", + "code":"395", + "des":"This feature is used to give privileges to users for specific packages. All the procedures and functions defined in the specific packages will be granted the execution pe", "doc_type":"tg", "kw":"Granting Execution Permissions,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Granting Execution Permissions", "githuburl":"" }, { "uri":"dws_mt_0305.html", + "node_id":"en-us_topic_0000001819336309.xml", "product_code":"dws", - "code":"243", + "code":"396", "des":"Enable & DisableSet package_name_list to bas_lookup_misc_pkg.Enable and disable the function based on configuration parameters.InputOutput", "doc_type":"tg", "kw":"Package Name List,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Package Name List", "githuburl":"" }, { "uri":"dws_mt_0306.html", + "node_id":"en-us_topic_0000001772696308.xml", "product_code":"dws", - "code":"244", - "des":"SubtypeThe customized type in the package cannot be converted.SUBTYPE error_msg IS sad_products_t.exception_description%TYPE;SUBTYPE AR_FLAG IS SAD_RA_LINES_TI.AR_FLAG%TY", + "code":"397", + "des":"SubtypeCustomized types in the package cannot be converted.SUBTYPE error_msg IS sad_products_t.exception_description%TYPE;SUBTYPE AR_FLAG IS SAD_RA_LINES_TI.AR_FLAG%TYPE;", "doc_type":"tg", "kw":"Data Type,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Data Type", "githuburl":"" }, { "uri":"dws_mt_0222.html", + "node_id":"en-us_topic_0000001772536632.xml", "product_code":"dws", - "code":"245", + "code":"398", "des":"Input-Chinese (OutputInput-Chinese )OutputInput-Chinese,OutputInput-Support Chinese SPACEOutput", "doc_type":"tg", "kw":"Chinese Character Support,Oracle Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Chinese Character Support", "githuburl":"" }, { "uri":"dws_07_0682.html", + "node_id":"en-us_topic_0000001819416349.xml", "product_code":"dws", - "code":"246", + "code":"399", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Netezza Syntax Migration", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Netezza Syntax Migration", "githuburl":"" }, { "uri":"dws_07_6821.html", + "node_id":"en-us_topic_0000001819336317.xml", "product_code":"dws", - "code":"247", + "code":"400", "des":"DISTRIBUTE ON (column) should be migrated to DISTRIBUTE BY HASH (column).ORGANIZE ON will be commented out.The row-store supports BLOB and CLOB. Column storage does not s", "doc_type":"tg", "kw":"Tables,Netezza Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Tables", "githuburl":"" }, { "uri":"dws_07_6822.html", + "node_id":"en-us_topic_0000001772696312.xml", "product_code":"dws", - "code":"248", + "code":"401", "des":"PROCEDURE with RETURNS will be modified to FUNCTION with RETURN.Migrate the nzplSQL language to the plpgSQL language or delete the language.The process which is started w", "doc_type":"tg", "kw":"PROCEDURE with RETURNS,Netezza Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"PROCEDURE with RETURNS", "githuburl":"" }, { "uri":"dws_07_6823.html", + "node_id":"en-us_topic_0000001772536640.xml", "product_code":"dws", - "code":"249", + "code":"402", "des":"NVARCHAR changed to NCHAR VARING.The row_count function is supported for affected row counting.ROW_COUNT identifies the number of rows associated with the previous SQL st", "doc_type":"tg", "kw":"Procedure,Netezza Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Procedure", "githuburl":"" }, { "uri":"dws_07_6824.html", + "node_id":"en-us_topic_0000001819416353.xml", "product_code":"dws", - "code":"250", + "code":"403", "des":"Second parameter is missing.Casting the data type.", "doc_type":"tg", "kw":"System Functions,Netezza Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"System Functions", "githuburl":"" }, { "uri":"dws_07_6825.html", + "node_id":"en-us_topic_0000001819336321.xml", "product_code":"dws", - "code":"251", + "code":"404", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Operator,Netezza Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Operator", "githuburl":"" }, { "uri":"dws_07_6826.html", + "node_id":"en-us_topic_0000001772696320.xml", "product_code":"dws", - "code":"252", + "code":"405", "des":"A new configuration parameter \"keywords_addressed_using_doublequote\" should be introduced with the below value:keywords_addressed_using_doublequote=freezekeywords_address", "doc_type":"tg", "kw":"DML,Netezza Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"DML", "githuburl":"" }, { "uri":"dws_07_6827.html", + "node_id":"en-us_topic_0000001772536644.xml", "product_code":"dws", - "code":"253", + "code":"406", "des":"This feature is applicable only for COLUMN store. For ROW store, Unique Index should not be commented.", "doc_type":"tg", - "kw":"Index Migration,Netezza Syntax Migration,Tool Guide", - "title":"Index Migration", - "githuburl":"" - }, - { - "uri":"dws_sct_0013.html", - "product_code":"dws", - "code":"254", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"tg", - "kw":"MySQL Syntax Migration", - "title":"MySQL Syntax Migration", - "githuburl":"" - }, - { - "uri":"dws_07_6831.html", - "product_code":"dws", - "code":"255", - "des":"MySQL supports a number of basic data types, including numeric, date/time, string (character), LOB, set, binary, and Boolean types. GaussDB(DWS) does not support some bas", - "doc_type":"tg", - "kw":"Basic Data Types,MySQL Syntax Migration,Tool Guide", - "title":"Basic Data Types", - "githuburl":"" - }, - { - "uri":"dws_07_6832.html", - "product_code":"dws", - "code":"256", - "des":"This section describes the migration syntax of MySQL tables (optional parameter). The migration syntax determines how the keywords and features are migrated. GaussDB(DWS)", - "doc_type":"tg", - "kw":"Table (Optional),MySQL Syntax Migration,Tool Guide", - "title":"Table (Optional)", - "githuburl":"" - }, - { - "uri":"dws_07_6833.html", - "product_code":"dws", - "code":"257", - "des":"This section contains the migration syntax for migrating MySQL table operation. The migration syntax decides how the supported keywords/features are migrated.For details,", - "doc_type":"tg", - "kw":"Table Operations,MySQL Syntax Migration,Tool Guide", - "title":"Table Operations", - "githuburl":"" - }, - { - "uri":"dws_07_6834.html", - "product_code":"dws", - "code":"258", - "des":"If MySQL unique indexes (constraints) and primary key constraints are used together during migration, OLAP distribution keys may become unavailable. Therefore, this scena", - "doc_type":"tg", - "kw":"Unique Indexes,MySQL Syntax Migration,Tool Guide", - "title":"Unique Indexes", - "githuburl":"" - }, - { - "uri":"dws_07_6835.html", - "product_code":"dws", - "code":"259", - "des":"GaussDB(DWS) does not support prefix indexes or inline normal indexes. DSC will replace these indexes with normal indexes based on GaussDB features.Inline normal/prefix i", - "doc_type":"tg", - "kw":"Normal and Prefix Indexes,MySQL Syntax Migration,Tool Guide", - "title":"Normal and Prefix Indexes", - "githuburl":"" - }, - { - "uri":"dws_07_6836.html", - "product_code":"dws", - "code":"260", - "des":"GaussDB(DWS) does not support hash indexes. DSC will replace these indexes with normal indexes based on GaussDB features.Inline hash indexInputCREATE TABLE `public`.`test", - "doc_type":"tg", - "kw":"Hash Indexes,MySQL Syntax Migration,Tool Guide", - "title":"Hash Indexes", - "githuburl":"" - }, - { - "uri":"dws_07_6837.html", - "product_code":"dws", - "code":"261", - "des":"GaussDB(DWS) supports B-tree indexes, but the position of the USING BTREE keyword in a statement is different from that in MySQL. DSC will perform adaptation based on Gau", - "doc_type":"tg", - "kw":"B-tree Indexes,MySQL Syntax Migration,Tool Guide", - "title":"B-tree Indexes", - "githuburl":"" - }, - { - "uri":"dws_07_6838.html", - "product_code":"dws", - "code":"262", - "des":"GaussDB(DWS) does not support spatial indexes. DSC will perform adaptation based on GaussDB features during migration.Inline spatial indexInputCREATE TABLE `public`.`test", - "doc_type":"tg", - "kw":"Spatial Indexes,MySQL Syntax Migration,Tool Guide", - "title":"Spatial Indexes", - "githuburl":"" - }, - { - "uri":"dws_07_8310.html", - "product_code":"dws", - "code":"263", - "des":"MySQL supports both DROP INDEX and ALTER TABLE DROP INDEX for deleting indexes. DSC will perform adaptation based on GaussDB features during migration.DROP INDEXInputCREA", - "doc_type":"tg", - "kw":"Delete an Index,MySQL Syntax Migration,Tool Guide", - "title":"Delete an Index", - "githuburl":"" - }, - { - "uri":"dws_07_8311.html", - "product_code":"dws", - "code":"264", - "des":"To comment out a single line, MySQL uses # or --, and GaussDB(DWS) uses --. DSC will replace # with -- for commenting out a single line during migration.InputOutput", - "doc_type":"tg", - "kw":"Comments,MySQL Syntax Migration,Tool Guide", - "title":"Comments", - "githuburl":"" - }, - { - "uri":"dws_07_8312.html", - "product_code":"dws", - "code":"265", - "des":"In MySQL, DATABASE is a schema object, which is equivalent to the SCHEMA of Oracle and GaussDB(DWS). DSC supports the following two scenarios:Database creationInputcreate", - "doc_type":"tg", - "kw":"Databases,MySQL Syntax Migration,Tool Guide", - "title":"Databases", - "githuburl":"" - }, - { - "uri":"dws_07_8313.html", - "product_code":"dws", - "code":"266", - "des":"This section describes the migration syntax of MySQL DML. The migration syntax determines how the keywords and features are migrated.For details, see the following topics", - "doc_type":"tg", - "kw":"Data Manipulation Language (DML),MySQL Syntax Migration,Tool Guide", - "title":"Data Manipulation Language (DML)", - "githuburl":"" - }, - { - "uri":"dws_07_8314.html", - "product_code":"dws", - "code":"267", - "des":"This section describes how to migrate keywords and features related to MySQL transaction and database management.TRANSACTIONDSC will perform adaptation based on GaussDB f", - "doc_type":"tg", - "kw":"Transaction Management and Database Management,MySQL Syntax Migration,Tool Guide", - "title":"Transaction Management and Database Management", - "githuburl":"" - }, - { - "uri":"dws_07_0684.html", - "product_code":"dws", - "code":"268", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"tg", - "kw":"DB2 Syntax Migration", - "title":"DB2 Syntax Migration", - "githuburl":"" - }, - { - "uri":"dws_07_6841.html", - "product_code":"dws", - "code":"269", - "des":"If a keyword is used as a column name, quotes (\") must be added, for example, \"order\".LONG VARCHAR should be changed to CLOB.LONG VARGRAPHIC.Below attributes of Foreign k", - "doc_type":"tg", - "kw":"Tables,DB2 Syntax Migration,Tool Guide", - "title":"Tables", - "githuburl":"" - }, - { - "uri":"dws_07_6842.html", - "product_code":"dws", - "code":"270", - "des":"FETCH clauseThe fetch-first-clause sets a maximum number of rows that can be retrieved.WITH AS with column listWITH AS with VALUES clauseTABLE function is specified with ", - "doc_type":"tg", - "kw":"DML,DB2 Syntax Migration,Tool Guide", - "title":"DML", - "githuburl":"" - }, - { - "uri":"dws_07_6843.html", - "product_code":"dws", - "code":"271", - "des":"Reverse Scansindex's schema is different from its table's schema.", - "doc_type":"tg", - "kw":"Index Migration (DB2),DB2 Syntax Migration,Tool Guide", - "title":"Index Migration (DB2)", - "githuburl":"" - }, - { - "uri":"dws_07_6844.html", - "product_code":"dws", - "code":"272", - "des":"Synonym is referred to Nickname in DB2.", - "doc_type":"tg", - "kw":"NICKNAME,DB2 Syntax Migration,Tool Guide", - "title":"NICKNAME", - "githuburl":"" - }, - { - "uri":"dws_07_6845.html", - "product_code":"dws", - "code":"273", - "des":"SET CURRENT SCHEMA", - "doc_type":"tg", - "kw":"Statement,DB2 Syntax Migration,Tool Guide", - "title":"Statement", - "githuburl":"" - }, - { - "uri":"dws_07_6846.html", - "product_code":"dws", - "code":"274", - "des":"DayMonthYearCurrent dateCurrent timestampPOSSTRValueThe date function returns a date using a value.", - "doc_type":"tg", - "kw":"System Functions,DB2 Syntax Migration,Tool Guide", - "title":"System Functions", - "githuburl":"" - }, - { - "uri":"dws_mt_0183.html", - "product_code":"dws", - "code":"275", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"tg", - "kw":"Command Reference", - "title":"Command Reference", - "githuburl":"" - }, - { - "uri":"dws_mt_0184.html", - "product_code":"dws", - "code":"276", - "des":"runDSC.sh or runDSC.bat is used to migrate schemas and queries of Teradata, Oracle, Netezza, MySQL, and DB2 to GaussDB(DWS).Linux:Windows:It is mandatory to specify the s", - "doc_type":"tg", - "kw":"Database Schema Conversion,Command Reference,Tool Guide", - "title":"Database Schema Conversion", - "githuburl":"" - }, - { - "uri":"dws_mt_0185.html", - "product_code":"dws", - "code":"277", - "des":"The version command is used to display the version number of the DSC.Linux:Windows:NoneLinux:Windows:", - "doc_type":"tg", - "kw":"Version,Command Reference,Tool Guide", - "title":"Version", - "githuburl":"" - }, - { - "uri":"dws_mt_0186.html", - "product_code":"dws", - "code":"278", - "des":"The help command is used to provide the help information for the commands supported by DSC.Linux:Windows:NoneNoneLinux:Windows:Linux:Windows:", - "doc_type":"tg", - "kw":"Help,Command Reference,Tool Guide", - "title":"Help", - "githuburl":"" - }, - { - "uri":"dws_mt_0187.html", - "product_code":"dws", - "code":"279", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"tg", - "kw":"Log Reference", - "title":"Log Reference", - "githuburl":"" - }, - { - "uri":"dws_mt_0188.html", - "product_code":"dws", - "code":"280", - "des":"The log files are the repository for all operations and status of the DSC. The following log files are available:SQL Migration LogsDSC.log: SQL Migration all activities.D", - "doc_type":"tg", - "kw":"Overview,Log Reference,Tool Guide", - "title":"Overview", - "githuburl":"" - }, - { - "uri":"dws_mt_0189.html", - "product_code":"dws", - "code":"281", - "des":"The SQL DSC (DSC.jar) supports the following types of logging:Activity LoggingError LoggingsuccessReadsuccessWriteIf a user specifies a log path, then all the logs are sa", - "doc_type":"tg", - "kw":"SQL Migration Logs,Log Reference,Tool Guide", - "title":"SQL Migration Logs", - "githuburl":"" - }, - { - "uri":"dws_mt_0190.html", - "product_code":"dws", - "code":"282", - "des":"The DSC writes all log information to a single file, perlDSC.log.Since the DSC will execute the SQL to migrate the SQL scripts inside Perl files, the following SQL migra", - "doc_type":"tg", - "kw":"Perl Migration Logs,Log Reference,Tool Guide", - "title":"Perl Migration Logs", - "githuburl":"" - }, - { - "uri":"dws_mt_0191.html", - "product_code":"dws", - "code":"283", - "des":"This section contains a list of troubleshooting steps and solutions for issues encountered while using DSC.The table lists the troubleshooting symptoms/issues along with ", - "doc_type":"tg", - "kw":"Troubleshooting,DSC,Tool Guide", - "title":"Troubleshooting", + "kw":"Unique Index,Netezza Syntax Migration,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], + "title":"Unique Index", "githuburl":"" }, { "uri":"dws_mt_0192.html", + "node_id":"en-us_topic_0000001819416357.xml", "product_code":"dws", - "code":"284", + "code":"407", "des":"This section covers the frequently asked questions.Q1: During installation, I get an error \"Root privileged users are not allowed to install the DSC for Linux.\" What is t", "doc_type":"tg", "kw":"FAQs,DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"FAQs", "githuburl":"" }, { - "uri":"dws_mt_0193.html", + "uri":"dws_16_0210.html", + "node_id":"en-us_topic_0000001819336325.xml", "product_code":"dws", - "code":"285", - "des":"Ensure that the operating system and the required software (refer toSystem Requirements for more details) are updated with the latest patches to prevent vulnerabilities a", + "code":"408", + "des":"This section contains a list of troubleshooting steps and solutions for issues encountered while using DSC.The table lists the troubleshooting symptoms/issues along with ", "doc_type":"tg", - "kw":"Security Management,DSC,Tool Guide", - "title":"Security Management", + "kw":"Troubleshooting,DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Troubleshooting", + "githuburl":"" + }, + { + "uri":"dws_16_0211.html", + "node_id":"en-us_topic_0000001772696324.xml", + "product_code":"dws", + "code":"409", + "des":"The following table lists the acronyms, abbreviations, terms, and their descriptions.", + "doc_type":"tg", + "kw":"Glossary,DSC,Tool Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"tg", + "prodname":"dws" + } + ], + "title":"Glossary", "githuburl":"" }, { "uri":"dws_07_0100.html", + "node_id":"en-us_topic_0000001188202642.xml", "product_code":"dws", - "code":"286", + "code":"410", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Server Tool", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Server Tool", "githuburl":"" }, { "uri":"dws_07_0101.html", + "node_id":"en-us_topic_0000001188362608.xml", "product_code":"dws", - "code":"287", + "code":"411", "des":"gs_dump is tool provided by GaussDB(DWS) to export database information. You can export a database or its objects, such as schemas, tables, and views. The database can be", "doc_type":"tg", "kw":"gs_dump,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gs_dump", "githuburl":"" }, { "uri":"dws_07_0102.html", + "node_id":"en-us_topic_0000001233922249.xml", "product_code":"dws", - "code":"288", + "code":"412", "des":"gs_dumpall is a tool provided by GaussDB(DWS) to export all database information, including the data of the default postgres database, data of user-specified databases, a", "doc_type":"tg", "kw":"gs_dumpall,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gs_dumpall", "githuburl":"" }, { "uri":"dws_07_0103.html", + "node_id":"en-us_topic_0000001188521068.xml", "product_code":"dws", - "code":"289", + "code":"413", "des":"gs_restore is a tool provided by GaussDB(DWS) to import data that was exported using gs_dump. It can also be used to import files that were exported using gs_dump.It has ", "doc_type":"tg", "kw":"gs_restore,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gs_restore", "githuburl":"" }, { "uri":"dws_07_0104.html", + "node_id":"en-us_topic_0000001234200661.xml", "product_code":"dws", - "code":"290", + "code":"414", "des":"gds_check is used to check the GDS deployment environment, including the OS parameters, network environment, and disk usage. It also supports the recovery of system param", "doc_type":"tg", "kw":"gds_check,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gds_check", "githuburl":"" }, { "uri":"dws_07_0106.html", + "node_id":"en-us_topic_0000001234200667.xml", "product_code":"dws", - "code":"291", + "code":"415", "des":"gds_install is a script tool used to install GDS in batches, improving GDS deployment efficiency.Configure environment variables before executing the script. For details,", "doc_type":"tg", "kw":"gds_install,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gds_install", "githuburl":"" }, { "uri":"dws_07_0107.html", + "node_id":"en-us_topic_0000001234042127.xml", "product_code":"dws", - "code":"292", + "code":"416", "des":"gds_uninstall is a script tool used to uninstall GDS in batches.Set environment variables before executing the script. For details, see \"Importing Data > Using a Foreign ", "doc_type":"tg", "kw":"gds_uninstall,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gds_uninstall", "githuburl":"" }, { "uri":"dws_07_0105.html", + "node_id":"en-us_topic_0000001188362580.xml", "product_code":"dws", - "code":"293", + "code":"417", "des":"gds_ctl is a script tool used for starting or stopping GDS service processes in batches. You can start or stop GDS service processes, which use the same port, on multiple", "doc_type":"tg", "kw":"gds_ctl,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gds_ctl", "githuburl":"" }, { "uri":"dws_07_0108.html", + "node_id":"en-us_topic_0000001188202530.xml", "product_code":"dws", - "code":"294", + "code":"418", "des":"During cluster installation, you need to execute commands and transfer files among hosts in the cluster. Therefore, mutual trust relationships must be established among t", "doc_type":"tg", "kw":"gs_sshexkey,Server Tool,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"gs_sshexkey", "githuburl":"" }, { "uri":"dws_07_0173.html", + "node_id":"en-us_topic_0000001376268154.xml", "product_code":"dws", - "code":"295", + "code":"419", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"tg", "kw":"Change History,Tool Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dws", + "documenttype":"tg" + } + ], "title":"Change History", "githuburl":"" } diff --git a/docs/dws/tool/CLASS.TXT.json b/docs/dws/tool/CLASS.TXT.json index 80015999..79577b62 100644 --- a/docs/dws/tool/CLASS.TXT.json +++ b/docs/dws/tool/CLASS.TXT.json @@ -1395,1009 +1395,1009 @@ "code":"155" }, { - "desc":"After switching to GaussDB(DWS) databases, you may need to migrate user data and application SQL scripts to new databases. In particular,the migration of application SQL ", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Overview", - "uri":"mt_tool_index.html", + "title":"About This Document", + "uri":"dws_16_0001.html", "doc_type":"tg", "p_code":"155", "code":"156" }, { - "desc":"This section provides the system context of DSC. DSC is a CLI tool that helps data migration engineers migrate scripts of source databases, such as Teradata, Oracle, Nete", + "desc":"This document is intended for the following DSC users:Database migration engineersDatabase administratorsTechnical support engineersDSC users need to have a basic knowled", "product_code":"dws", - "title":"Supported Keywords and Features", - "uri":"dws_mt_0015.html", + "title":"Intended Audience", + "uri":"dws_16_0002.html", "doc_type":"tg", - "p_code":"155", + "p_code":"156", "code":"157" }, { - "desc":"This section describes the constraints and limitations of DSC.DSC is used only for syntax migration and not for data migration.If the SELECT clause of a subquery contains", + "desc":"This section describes the content, symbol, and command conventions of this document.The purchased products, services, and features are subject to the signed contract. Al", "product_code":"dws", - "title":"Constraints and Limitations", - "uri":"dws_mt_0012.html", + "title":"Document Conventions", + "uri":"dws_16_0003.html", "doc_type":"tg", - "p_code":"155", + "p_code":"156", "code":"158" }, { - "desc":"Table 1 lists the source databases supported by DSC.OS requirementsTable 2 lists the operating systems compatible with DSC.Other software requirementsTable 3 lists the re", + "desc":"This section lists the applicable third-party licenses.ANTLR v4.9.3Apache Commons IO 2.11Apache Commons CLI 1.5Apache Log4j 2.17.2JSON.org json 20220320postgresql 42.4.1s", "product_code":"dws", - "title":"System Requirements", - "uri":"dws_mt_0014.html", + "title":"Third-party Licenses", + "uri":"dws_16_0005.html", "doc_type":"tg", - "p_code":"155", + "p_code":"156", "code":"159" }, { - "desc":"Before using DSC, install it on a Linux or Windows server. DSC supports 64-bit Linux OSs. For details about other OSs supported by DSC, see Compatible OSs.In Linux, do no", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Installing DSC", - "uri":"dws_mt_0021.html", + "title":"Introduction to DSC", + "uri":"dws_16_0006.html", "doc_type":"tg", "p_code":"155", "code":"160" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"After switching to GaussDB(DWS) databases, you may need to migrate user data and application SQL scripts to new databases. In particular,the migration of application SQL ", "product_code":"dws", - "title":"Configuring DSC", - "uri":"dws_mt_0023.html", + "title":"Overview", + "uri":"mt_tool_index.html", "doc_type":"tg", - "p_code":"155", + "p_code":"160", "code":"161" }, { - "desc":"DSC provides configuration files and parameters to configure migration logic and rules. Before migrating scripts, you need to configure the following as required:Tool con", + "desc":"The following table lists the source databases supported by DSC.The following table lists the destination databases supported by DSC.Table 3 lists the hardware requiremen", "product_code":"dws", - "title":"Overview", - "uri":"dws_mt_0024.html", + "title":"Operating Environment", + "uri":"dws_16_0008.html", "doc_type":"tg", - "p_code":"161", + "p_code":"160", "code":"162" }, - { - "desc":"Configure the following items:Setting application.properties: Configure the migration behavior of DSC, for example, whether to overwrite the files in the target folder an", - "product_code":"dws", - "title":"DSC Configuration", - "uri":"dws_mt_0025.html", - "doc_type":"tg", - "p_code":"161", - "code":"163" - }, - { - "desc":"Teradata parameters are used to customize rules for Teradata script migration.Open the features-teradata.properties file in the config folder and set the parameters in Ta", - "product_code":"dws", - "title":"Teradata SQL Configuration", - "uri":"dws_mt_0026.html", - "doc_type":"tg", - "p_code":"161", - "code":"164" - }, - { - "desc":"Oracle parameters are used to customize rules for Oracle script migration.Open the features-oracle.properties file in the config folder and set parameters in Table 1 as n", - "product_code":"dws", - "title":"Oracle SQL Configuration", - "uri":"dws_mt_0027.html", - "doc_type":"tg", - "p_code":"161", - "code":"165" - }, - { - "desc":"Teradata Perl parameters are used to customize rules for Teradata Perl script migration.Open the perl-migration.properties file in the config folder and set parameters in", - "product_code":"dws", - "title":"Teradata Perl Configuration", - "uri":"dws_mt_0029.html", - "doc_type":"tg", - "p_code":"161", - "code":"166" - }, - { - "desc":"MySQL parameters are used to customize rules for MySQL script migration.Open the features-mysql.properties file in the config folder and configure parameters in the featu", - "product_code":"dws", - "title":"MySQL SQL Configuration", - "uri":"dws_07_0666.html", - "doc_type":"tg", - "p_code":"161", - "code":"167" - }, - { - "desc":"Netezza parameters are used to customize rules for Netezza script migration.Open the features-netezza.properties file in the config folder and set parameters in Table 1 a", - "product_code":"dws", - "title":"Netezza Configuration", - "uri":"dws_mt_0030.html", - "doc_type":"tg", - "p_code":"161", - "code":"168" - }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", "title":"Using DSC", - "uri":"dws_mt_0031.html", + "uri":"dws_16_0009.html", "doc_type":"tg", "p_code":"155", + "code":"163" + }, + { + "desc":"This chapter describes how to use DSC, including how to install and configure DSC and how to use DSC to migrate data.Use the latest patches to update the operating system", + "product_code":"dws", + "title":"Overview", + "uri":"dws_16_0010.html", + "doc_type":"tg", + "p_code":"163", + "code":"164" + }, + { + "desc":"Before using DSC, install it on a Linux or Windows server. DSC supports 64-bit Linux OSs. For details about other OSs supported by DSC, see Table 4.In Linux, do not insta", + "product_code":"dws", + "title":"Downloading and Installing DSC", + "uri":"dws_16_0212.html", + "doc_type":"tg", + "p_code":"163", + "code":"165" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Configuring DSC", + "uri":"dws_16_0012.html", + "doc_type":"tg", + "p_code":"163", + "code":"166" + }, + { + "desc":"Configure the following items:Setting application.properties: Configure the migration behavior of DSC, for example, whether to overwrite the files in the target folder an", + "product_code":"dws", + "title":"DSC Configuration", + "uri":"dws_16_0013.html", + "doc_type":"tg", + "p_code":"166", + "code":"167" + }, + { + "desc":"Teradata parameters are used to customize rules for Teradata script migration.Open the features-teradata.properties file in the config folder and set the parameters in Ta", + "product_code":"dws", + "title":"Teradata SQL Configuration", + "uri":"dws_16_0014.html", + "doc_type":"tg", + "p_code":"166", + "code":"168" + }, + { + "desc":"Teradata Perl parameters are used to customize rules for Teradata Perl script migration.Open the perl-migration.properties file in the config folder and set parameters in", + "product_code":"dws", + "title":"Teradata Perl Configuration", + "uri":"dws_16_0015.html", + "doc_type":"tg", + "p_code":"166", "code":"169" }, + { + "desc":"MySQL parameters are used to customize rules for MySQL script migration.Open the features-mysql.properties file in the config folder and configure Parameters in the featu", + "product_code":"dws", + "title":"MySQL Configuration", + "uri":"dws_16_0016.html", + "doc_type":"tg", + "p_code":"166", + "code":"170" + }, + { + "desc":"Oracle parameters are used to customize rules for Oracle script migration.Open the features-oracle.properties file in the config folder and set parameters in Table 1 as n", + "product_code":"dws", + "title":"Oracle SQL Configuration", + "uri":"dws_16_0213.html", + "doc_type":"tg", + "p_code":"166", + "code":"171" + }, + { + "desc":"Netezza parameters are used to customize rules for Netezza script migration.Open the features-netezza.properties file in the config folder and set parameters in Table 1 a", + "product_code":"dws", + "title":"Netezza Configuration", + "uri":"dws_16_0214.html", + "doc_type":"tg", + "p_code":"166", + "code":"172" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", "title":"Migration Process", - "uri":"dws_mt_0032.html", + "uri":"dws_16_0017.html", "doc_type":"tg", - "p_code":"169", - "code":"170" - }, - { - "desc":"The following use cases for migration are supported by DSC:Migrate Teradata SQLMigrate Oracle SQLMigrate Teradata Perl filesMigrate NetezzaMigrate MySQL SQLMigrate DB2Fig", - "product_code":"dws", - "title":"Overview", - "uri":"dws_mt_0207.html", - "doc_type":"tg", - "p_code":"170", - "code":"171" + "p_code":"163", + "code":"173" }, { "desc":"Custom scripts are executed to support input keywords that do not exist in certain versions of the target database. These scripts must be executed in each target database", "product_code":"dws", "title":"Prerequisites", - "uri":"dws_mt_0033.html", + "uri":"dws_16_0018.html", "doc_type":"tg", - "p_code":"170", - "code":"172" + "p_code":"173", + "code":"174" }, { "desc":"Before the migration, create an input folder and an output folder, and copy all the SQL scripts to be migrated to the input folder. The following procedure describes how ", "product_code":"dws", "title":"Preparations", - "uri":"dws_mt_0034.html", + "uri":"dws_16_0019.html", "doc_type":"tg", - "p_code":"170", - "code":"173" + "p_code":"173", + "code":"175" }, { "desc":"Before starting DSC, specify the output folder path. Separate the input folder path, output folder path, and log path with spaces. The input folder path cannot contain sp", "product_code":"dws", - "title":"Migrating Data Using DSC", - "uri":"dws_mt_0035.html", + "title":"Executing DSC", + "uri":"dws_16_0020.html", "doc_type":"tg", - "p_code":"170", - "code":"174" + "p_code":"173", + "code":"176" }, { "desc":"After the migration is complete, you can use a comparison tool (for example, BeyondCompare®) to compare the output file with its input file. Input SQL files can also be f", "product_code":"dws", "title":"Viewing Output Files and Logs", - "uri":"dws_mt_0036.html", + "uri":"dws_16_0021.html", "doc_type":"tg", - "p_code":"170", - "code":"175" + "p_code":"173", + "code":"177" }, { "desc":"Migration related issues can be classified into:Tool execution issues: No output or incorrect output is displayed because DSC partially or fully failed to be executed. Fo", "product_code":"dws", "title":"Troubleshooting", - "uri":"dws_mt_0037.html", + "uri":"dws_16_0022.html", "doc_type":"tg", - "p_code":"170", - "code":"176" + "p_code":"173", + "code":"178" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"CLI Reference", + "uri":"dws_16_0023.html", + "doc_type":"tg", + "p_code":"163", + "code":"179" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Database Schema Conversion", + "uri":"dws_16_0024.html", + "doc_type":"tg", + "p_code":"179", + "code":"180" + }, + { + "desc":"It is mandatory to specify the source database, input folder path, and output folder path, and optional to specify the migration type and log path.If a user does not spec", + "product_code":"dws", + "title":"Migration Parameters", + "uri":"dws_16_0025.html", + "doc_type":"tg", + "p_code":"180", + "code":"181" }, { "desc":"DSC supports the migration from Teradata to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and type conversion.Run the following comman", "product_code":"dws", "title":"Teradata SQL Migration", - "uri":"dws_mt_0038.html", + "uri":"dws_16_0026.html", "doc_type":"tg", - "p_code":"169", - "code":"177" - }, - { - "desc":"DSC supports the migration from Oracle to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set t", - "product_code":"dws", - "title":"Oracle SQL Migration", - "uri":"dws_mt_0039.html", - "doc_type":"tg", - "p_code":"169", - "code":"178" + "p_code":"180", + "code":"182" }, { "desc":"This section describes how to migrate Teradata Perl files.Run the runDSC.shor runDSC.bat command and set --application-lang to perl to migrate Teradata BTEQ or SQL_LANG s", "product_code":"dws", "title":"Teradata Perl Migration", - "uri":"dws_mt_0041.html", + "uri":"dws_16_0027.html", "doc_type":"tg", - "p_code":"169", - "code":"179" - }, - { - "desc":"DSC supports the migration from Netezza to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set ", - "product_code":"dws", - "title":"Netezza SQL Migration", - "uri":"dws_07_0675.html", - "doc_type":"tg", - "p_code":"169", - "code":"180" + "p_code":"180", + "code":"183" }, { "desc":"DSC supports the migration from MySQL to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following command on Linux t", "product_code":"dws", "title":"MySQL SQL Migration", - "uri":"dws_07_0676.html", + "uri":"dws_16_0028.html", "doc_type":"tg", - "p_code":"169", - "code":"181" + "p_code":"180", + "code":"184" }, { - "desc":"SQL Formatter improves the readability of SQL statements. It formats SQL statements by adding/deleting rows and indenting context, and is used to format migrated output f", + "desc":"DSC supports the migration from Oracle to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set t", "product_code":"dws", - "title":"SQL Formatter", - "uri":"dws_mt_0042.html", + "title":"Oracle SQL Migration", + "uri":"dws_16_0215.html", "doc_type":"tg", - "p_code":"169", - "code":"182" + "p_code":"180", + "code":"185" + }, + { + "desc":"DSC supports the migration from Netezza to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.Run the following commands to set ", + "product_code":"dws", + "title":"Netezza SQL Migration", + "uri":"dws_16_0216.html", + "doc_type":"tg", + "p_code":"180", + "code":"186" + }, + { + "desc":"After DSC converts the source sql files, execute the converted files on target GaussDB(DWS) and provide a report with details of number of statements succeeded and failed", + "product_code":"dws", + "title":"Verification", + "uri":"dws_16_0029.html", + "doc_type":"tg", + "p_code":"180", + "code":"187" + }, + { + "desc":"The version command is used to display the version number of the DSC.Linux:Windows:Linux:Windows:", + "product_code":"dws", + "title":"VERSION", + "uri":"dws_16_0030.html", + "doc_type":"tg", + "p_code":"179", + "code":"188" + }, + { + "desc":"The help command is used to provide the help information for the commands supported by DSC.Linux:Windows:Linux:Windows:Linux:Windows:", + "product_code":"dws", + "title":"HELP", + "uri":"dws_16_0031.html", + "doc_type":"tg", + "p_code":"179", + "code":"189" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Log Reference", + "uri":"dws_16_0032.html", + "doc_type":"tg", + "p_code":"163", + "code":"190" + }, + { + "desc":"The log files are the repository for all operations and status of the DSC. The following log files are available:SQL Migration LogsDSC.log: SQL Migration all activities.D", + "product_code":"dws", + "title":"Overview", + "uri":"dws_16_0217.html", + "doc_type":"tg", + "p_code":"190", + "code":"191" + }, + { + "desc":"The SQL DSC (DSC.jar) supports the following types of logging:Activity loggingError loggingsuccessReadsuccessWriteIf a user specifies a log path, then all the logs are sa", + "product_code":"dws", + "title":"SQL Migration Logs", + "uri":"dws_16_0033.html", + "doc_type":"tg", + "p_code":"190", + "code":"192" + }, + { + "desc":"The DSC writes all log information to a single file, perlDSC.log.Since the DSC will execute the SQL to migrate the SQL scripts inside Perl files, the following SQL migrat", + "product_code":"dws", + "title":"Perl Migration Logs", + "uri":"dws_16_0034.html", + "doc_type":"tg", + "p_code":"190", + "code":"193" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"SQL Syntax Migration Reference", + "uri":"dws_16_0035.html", + "doc_type":"tg", + "p_code":"155", + "code":"194" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", "title":"Teradata Syntax Migration", - "uri":"dws_mt_0044.html", + "uri":"dws_16_0036.html", "doc_type":"tg", - "p_code":"155", - "code":"183" + "p_code":"194", + "code":"195" }, { - "desc":"This section lists the Teradata features supported by the syntax migration tool, and provides the Teradata syntax and the equivalent GaussDB syntax for each feature. The ", + "desc":"Table 1 lists the Teradata keywords and features that can be migrated.The Version column contains the earliest versions that support the keywords or features.The Remarks ", "product_code":"dws", - "title":"Overview", - "uri":"dws_mt_0045.html", + "title":"Supported Keywords and Features", + "uri":"dws_16_0038.html", "doc_type":"tg", - "p_code":"183", - "code":"184" + "p_code":"195", + "code":"196" + }, + { + "desc":"The restrictions on using DSC to migrate data from TD are as follows:DSC is used only for syntax migration and not for data migration.If the SELECT clause of a subquery c", + "product_code":"dws", + "title":"Constraints and Limitations", + "uri":"dws_16_0039.html", + "doc_type":"tg", + "p_code":"195", + "code":"197" + }, + { + "desc":"InputOutput", + "product_code":"dws", + "title":"Data Type", + "uri":"dws_16_0040.html", + "doc_type":"tg", + "p_code":"195", + "code":"198" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Schema Objects", - "uri":"dws_mt_0046.html", + "title":"Functions and Operators", + "uri":"dws_16_0041.html", "doc_type":"tg", - "p_code":"183", - "code":"185" + "p_code":"195", + "code":"199" }, { - "desc":"The table-specific keyword MULTISET VOLATILE is provided in the input file, but the keyword is not supported by GaussDB(DWS). Therefore, the tool replaces it with the LOC", + "desc":"Analytical functions are collectively called ordered analytical functions in Teradata, and they provide powerful analytical abilities for data mining, analysis and busine", "product_code":"dws", - "title":"Table Migration", - "uri":"dws_mt_0048.html", + "title":"Analytical Functions", + "uri":"dws_16_0043.html", "doc_type":"tg", - "p_code":"185", - "code":"186" - }, - { - "desc":"The sequence of CREATE INDEX columns and table names in Teradata is different from that in GaussDB(DWS). Use the configuration parameter distributeByHash to configure how", - "product_code":"dws", - "title":"Index Migration", - "uri":"dws_mt_0064.html", - "doc_type":"tg", - "p_code":"185", - "code":"187" - }, - { - "desc":"CREATE VIEW (short key CV) is used together with SELECT to create a view.The keyword VIEW is supported by both Teradata and GaussDB(DWS), but the SELECT statements are en", - "product_code":"dws", - "title":"View Migration", - "uri":"dws_mt_0065.html", - "doc_type":"tg", - "p_code":"185", - "code":"188" - }, - { - "desc":"COLLECT STAT is used in Teradata for collecting optimizer statistics, which will be used for query performance. GaussDB(DWS) uses the ANALYZE statement to replace the COL", - "product_code":"dws", - "title":"COLLECT STATISTICS", - "uri":"dws_mt_0066.html", - "doc_type":"tg", - "p_code":"185", - "code":"189" - }, - { - "desc":"ACCESS LOCK allows you to read the data from a table that may have been locked for the READ or WRITE.Use the tdMigrateLOCKOption configuration parameter to configure migr", - "product_code":"dws", - "title":"ACCESS LOCK", - "uri":"dws_mt_0067.html", - "doc_type":"tg", - "p_code":"185", - "code":"190" - }, - { - "desc":"DBC.COLUMNSview is a table containing information about table and view columns, stored procedures, or macro parameters. The view includes the following column names: Data", - "product_code":"dws", - "title":"DBC.COLUMNS", - "uri":"dws_mt_0068.html", - "doc_type":"tg", - "p_code":"185", - "code":"191" - }, - { - "desc":"The DSC migrates dbc.tables to their corresponding mig_td_ext.vw_td_dbc_tables.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutput", - "product_code":"dws", - "title":"DBC.TABLES", - "uri":"dws_mt_0069.html", - "doc_type":"tg", - "p_code":"185", - "code":"192" - }, - { - "desc":"DSC migrates dbc.indices to the corresponding mig_td_ext.vw_td_dbc_indices.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutputIn dbc.i", - "product_code":"dws", - "title":"DBC.INDICES", - "uri":"dws_mt_0070.html", - "doc_type":"tg", - "p_code":"185", - "code":"193" - }, - { - "desc":"This command displays the COLLECT STATISTICS statement with statistics. Gauss does not have an equivalent for this. Since it does not affect the functionality, this comma", - "product_code":"dws", - "title":"SHOW STATS VALUES SEQUENCED", - "uri":"dws_07_8111.html", - "doc_type":"tg", - "p_code":"183", - "code":"194" - }, - { - "desc":"This section describes the syntax for migrating Teradata DML. The migration syntax determines how the keywords and features are migrated.In Teradata, SQL queries in a fil", - "product_code":"dws", - "title":"DML", - "uri":"dws_mt_0071.html", - "doc_type":"tg", - "p_code":"183", - "code":"195" - }, - { - "desc":"This section contains the migration syntax for migrating Teradata query migration operators. The migration syntax determines how the keywords and features are migrated.Fo", - "product_code":"dws", - "title":"Querying Migration Operators", - "uri":"dws_mt_0084.html", - "doc_type":"tg", - "p_code":"183", - "code":"196" - }, - { - "desc":"This section describes the syntax for migrating Teradata query optimization operators. The migration syntax determines how the keywords and features are migrated.Use the ", - "product_code":"dws", - "title":"Query Optimization Operators", - "uri":"dws_mt_0091.html", - "doc_type":"tg", - "p_code":"183", - "code":"197" - }, - { - "desc":"This section contains the migration syntax for migrating Teradata system functions and operators. The migration syntax determines how the keywords and features are migrat", - "product_code":"dws", - "title":"System Functions and Operators", - "uri":"dws_mt_0094.html", - "doc_type":"tg", - "p_code":"183", - "code":"198" + "p_code":"199", + "code":"200" }, { "desc":"Input: **OutputInput: MODOutputUse the tdMigrateNULLIFZERO configuration parameter to configure migration of NULLIFZERO.Input: NULLIFZEROSELECT NULLIFZERO(expr1) FROM tab", "product_code":"dws", "title":"Math Functions", - "uri":"dws_mt_0100.html", + "uri":"dws_16_0044.html", "doc_type":"tg", - "p_code":"183", - "code":"199" + "p_code":"199", + "code":"201" }, { "desc":"Input: CHAROutputInput: CHARACTERSOutputInput: INDEXOutputInput: STRREPLACESELECT STRREPLACE(c2, '.', '')\n FROM tab1\n WHERE ...;OutputInput: OREPLACESELECT OREPLACE (c2,", "product_code":"dws", "title":"String Functions", - "uri":"dws_mt_0101.html", + "uri":"dws_16_0045.html", "doc_type":"tg", - "p_code":"183", - "code":"200" + "p_code":"199", + "code":"202" }, { "desc":"Migration tools support the migration of Teradata DATE FORMAT in SELECT statements, using TO_CHAR to display the date in the source format. This conversion is not done if", "product_code":"dws", "title":"Date and Time Functions", - "uri":"dws_mt_0102.html", + "uri":"dws_16_0046.html", "doc_type":"tg", - "p_code":"183", - "code":"201" - }, - { - "desc":"This section contains the migration syntax for migrating Teradata type casting and formatting syntax. The migration syntax determines how the keywords and features are mi", - "product_code":"dws", - "title":"Type Casting and Formatting", - "uri":"dws_mt_0103.html", - "doc_type":"tg", - "p_code":"183", - "code":"202" - }, - { - "desc":"The BTEQ utility commands are as follows:LOGOFF ends the current RDBMS sessions without exiting BTEQ.QUIT command ends the current Teradata database sessions and exits BT", - "product_code":"dws", - "title":"BTEQ Utility Command", - "uri":"dws_07_8120.html", - "doc_type":"tg", - "p_code":"183", + "p_code":"199", "code":"203" }, { - "desc":"InputOutputInputOutputInputOutputInputOutputInputOutput", + "desc":"The comparison operators LT, LE, GT, GE, EQ, and NE must not be used as TABLE alias or COLUMN alias.The following comparison and list operators are supported:Input: Compa", "product_code":"dws", - "title":"DSQL", - "uri":"dws_07_8121.html", + "title":"Comparison and List Operators", + "uri":"dws_16_0047.html", "doc_type":"tg", - "p_code":"183", + "p_code":"199", "code":"204" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"The functions that can be called in the FROM clause of a query are from the table operator.Input: Table operator with RETURNSSELECT * \n FROM TABLE( sales_retrieve (9005)", "product_code":"dws", - "title":"Oracle Syntax Migration", - "uri":"dws_mt_0104.html", + "title":"Table Operators", + "uri":"dws_16_0048.html", "doc_type":"tg", - "p_code":"155", + "p_code":"199", "code":"205" }, { - "desc":"This section lists the Oracle features supported by the syntax migration tool, and provides the Oracle syntax and the equivalent GaussDB(DWS) syntax for each feature. The", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Overview", - "uri":"dws_mt_0105.html", + "title":"Query Migration Operators", + "uri":"dws_16_0049.html", "doc_type":"tg", - "p_code":"205", + "p_code":"199", "code":"206" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"In general, the QUALIFY clause is accompanied by analytic functions (window functions) such as CSUM(), MDIFF(), ROW_NUMBER() and RANK(). This is addressed using sub-query", "product_code":"dws", - "title":"Schema Objects", - "uri":"dws_mt_0106.html", + "title":"QUALIFY", + "uri":"dws_16_0051.html", "doc_type":"tg", - "p_code":"205", + "p_code":"206", "code":"207" }, { - "desc":"The Oracle CREATE TABLE statement is used to create new tables. The target database supports Oracle CREATE TABLE without any migration.The Oracle ALTER TABLE statement is", + "desc":"ALIAS is supported by all databases. In Teradata, an ALIAS can be referred in SELECT and WHERE clauses of the same statement where the alias is defined. Since ALIAS is no", "product_code":"dws", - "title":"Tables", - "uri":"dws_mt_0108.html", + "title":"ALIAS", + "uri":"dws_16_0052.html", "doc_type":"tg", - "p_code":"207", + "p_code":"206", "code":"208" }, { - "desc":"GaussDB(DWS) does not support GLOBAL TEMPORARY TABLE, and it will be migrated to LOCAL TEMPORARY TABLE.ON COMMIT DELETE ROWS is also not supported, and will be migrated t", + "desc":"In Teradata, the FORMAT keyword is used for formatting a column/expression. For example, FORMAT '9(n)' and 'z(n)' are addressed using LPAD with 0 and space (' ') respecti", "product_code":"dws", - "title":"Temporary Tables", - "uri":"dws_mt_0109.html", + "title":"FORMAT and CAST", + "uri":"dws_16_0053.html", "doc_type":"tg", - "p_code":"207", + "p_code":"206", "code":"209" }, { - "desc":"Global temporary tables are converted to local temporary tables.Input - GLOBAL TEMPORARY TABLEOutput", + "desc":"Table 1 lists the abbreviation keywords supported by Teradata and the corresponding syntax in GaussDB A and GaussDB(DWS).Input - BTOutput", "product_code":"dws", - "title":"Global Temporary Tables", - "uri":"dws_mt_0212.html", + "title":"Short Keys Migration", + "uri":"dws_16_0054.html", "doc_type":"tg", - "p_code":"207", + "p_code":"206", "code":"210" }, { - "desc":"When an index is created in GaussDB(DWS), a schema name cannot be specified along with the index name. The index will be automatically created in the schema where the ind", + "desc":"This section describes the migration of object names starting with $.The migration behavior for object names starting with $ is explained in the following table. Use the ", "product_code":"dws", - "title":"Index Migration", - "uri":"dws_mt_0110.html", + "title":"Object Names Starting with $", + "uri":"dws_16_0055.html", "doc_type":"tg", - "p_code":"207", + "p_code":"206", "code":"211" }, { - "desc":"A view is a logical table that is based on one or more tables or views. A view itself contains no data.In the source file, if the table names are not qualified with the s", + "desc":"This section describes the syntax for migrating Teradata query optimization operators. The migration syntax determines how the keywords and features are migrated.Use the ", "product_code":"dws", - "title":"Views", - "uri":"dws_mt_0111.html", + "title":"Query Optimization Operators", + "uri":"dws_16_0056.html", "doc_type":"tg", - "p_code":"207", + "p_code":"199", "code":"212" }, - { - "desc":"A sequence is an Oracle object used to generate a number sequence. This can be useful when you need to create an autonumber column to act as a primary key.If MigSupportSe", - "product_code":"dws", - "title":"Sequences", - "uri":"dws_mt_0112.html", - "doc_type":"tg", - "p_code":"207", - "code":"213" - }, - { - "desc":"In Oracle, the DROP TABLE statement moves a table to the recycle bin. The PURGE statement is used to remove a table or index from the recycle bin and release all of the s", - "product_code":"dws", - "title":"PURGE", - "uri":"dws_mt_0113.html", - "doc_type":"tg", - "p_code":"207", - "code":"214" - }, - { - "desc":"DSC supports GaussDB(DWS) keywords, such as NAME, LIMIT, OWNER, KEY, and CAST. These keywords must be enclosed in double quotation marks.The keywords NAME, VERSION, LABEL", - "product_code":"dws", - "title":"Database Keywords", - "uri":"dws_mt_0114.html", - "doc_type":"tg", - "p_code":"207", - "code":"215" - }, - { - "desc":"Input – COMPRESS PhraseOutput", - "product_code":"dws", - "title":"COMPRESS Phrase", - "uri":"dws_07_6814.html", - "doc_type":"tg", - "p_code":"205", - "code":"216" - }, - { - "desc":"There is a configuration parameter that is introduced for this feature named BitmapIndexSupport which default value is comment, then the sample input and output are as fo", - "product_code":"dws", - "title":"Bitmap Index", - "uri":"dws_07_6815.html", - "doc_type":"tg", - "p_code":"205", - "code":"217" - }, - { - "desc":"Input – custom tablespaceOutput", - "product_code":"dws", - "title":"Custom Tablespace", - "uri":"dws_07_6816.html", - "doc_type":"tg", - "p_code":"205", - "code":"218" - }, - { - "desc":"Supplemental columns can be recorded in redo log files. The process of recording these additional columns is called supplemental logging. The Oracle database supports thi", - "product_code":"dws", - "title":"Supplemental Log Data", - "uri":"dws_07_6817.html", - "doc_type":"tg", - "p_code":"205", - "code":"219" - }, - { - "desc":"\"Data type LONG RAW\" is not supported in the CREATE TABLE statement. LONG RAW data type needs to be replaced with Byte.InputOutput", - "product_code":"dws", - "title":"LONG RAW", - "uri":"dws_07_6818.html", - "doc_type":"tg", - "p_code":"205", - "code":"220" - }, - { - "desc":"SYS_GUID is a built-in function which returns the Global Unique Identifier (GUID) for a row in a table. It accepts no arguments and returns a RAW value of 16 bytes.InputO", - "product_code":"dws", - "title":"SYS_GUID", - "uri":"dws_07_6819.html", - "doc_type":"tg", - "p_code":"205", - "code":"221" - }, - { - "desc":"This section describes the migration syntax of Oracle DML. The migration syntax decides how the keywords/features are migrated.For details, see the following topics:SELEC", - "product_code":"dws", - "title":"DML", - "uri":"dws_mt_0115.html", - "doc_type":"tg", - "p_code":"205", - "code":"222" - }, - { - "desc":"This section contains the migration syntax of Oracle Pseudo Columns. The migration syntax decides how the keywords/features are migrated.A pseudo column is similar to a t", - "product_code":"dws", - "title":"Pseudo Columns", - "uri":"dws_mt_0128.html", - "doc_type":"tg", - "p_code":"205", - "code":"223" - }, - { - "desc":"This section describes the migration syntax of Oracle OUTER JOIN. The migration syntax determines how the keywords/features are migrated.An OUTER JOIN returns all rows th", - "product_code":"dws", - "title":"OUTER JOIN", - "uri":"dws_mt_0132.html", - "doc_type":"tg", - "p_code":"205", - "code":"224" - }, - { - "desc":"Join is supported in Gauss 18.2.0, so parameter supportJoinOperatoris added.OUTER QUERY (+)can be migrated when supportJoinOperatoris set to false.Input-OUTER QUERY(+)Out", - "product_code":"dws", - "title":"OUTER QUERY (+)", - "uri":"dws_mt_0215.html", - "doc_type":"tg", - "p_code":"205", - "code":"225" - }, - { - "desc":"Input-CONNECT BYOutputInput - CONNECT BY multiple tablesThe syntax shows the relationship between each child row and its parent row. It uses the CONNECT BY xxx PRIOR clau", - "product_code":"dws", - "title":"CONNECT BY", - "uri":"dws_mt_0216.html", - "doc_type":"tg", - "p_code":"205", - "code":"226" - }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"System Functions", - "uri":"dws_mt_0133.html", + "title":"Schema Objects and Data Definition Language (DDL)", + "uri":"dws_16_0059.html", "doc_type":"tg", - "p_code":"205", + "p_code":"195", + "code":"213" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Migrating Tables", + "uri":"dws_16_0061.html", + "doc_type":"tg", + "p_code":"213", + "code":"214" + }, + { + "desc":"The Teradata CREATE TABLE (short key CT) statements are used to create new tables.Example:Input: CREATE TABLEOutputWhen CREATE tab2 AS tab1 is executed, the structure cop", + "product_code":"dws", + "title":"CREATE TABLE", + "uri":"dws_16_0063.html", + "doc_type":"tg", + "p_code":"214", + "code":"215" + }, + { + "desc":"CHARACTER SET is used to specify the server character set for a character column. CASESPECIFIC specifies the case for character data comparisons and collations.Use the td", + "product_code":"dws", + "title":"CHARACTER SET and CASESPECIFIC", + "uri":"dws_16_0064.html", + "doc_type":"tg", + "p_code":"214", + "code":"216" + }, + { + "desc":"The table-specific keyword VOLATILE is provided in the input file, but the keyword is not supported by GaussDB(DWS). The tool replaces it with the LOCAL TEMPORARYkeyword ", + "product_code":"dws", + "title":"VOLATILE", + "uri":"dws_16_0065.html", + "doc_type":"tg", + "p_code":"214", + "code":"217" + }, + { + "desc":"SET is a unique feature in Teradata. It does not allow duplicate records. It is addressed using the MINUSset operator. Migration tool supports MULTISET and SET tables. SE", + "product_code":"dws", + "title":"SET", + "uri":"dws_16_0066.html", + "doc_type":"tg", + "p_code":"214", + "code":"218" + }, + { + "desc":"MULTISETis a normal table, which is supported by all the DBs. Migration tool supports MULTISET and SET tables.MULTISET table can be used with VOLATILE.Input: CREATE MULTI", + "product_code":"dws", + "title":"MULTISET", + "uri":"dws_16_0067.html", + "doc_type":"tg", + "p_code":"214", + "code":"219" + }, + { + "desc":"The keyword TITLE is supported for Teradata Permanent, Global Temporary and Volatile tables. In the migration process, the TITLE text is migrated as a comment.If the TITL", + "product_code":"dws", + "title":"TITLE", + "uri":"dws_16_0068.html", + "doc_type":"tg", + "p_code":"214", + "code":"220" + }, + { + "desc":"The CREATE TABLE statement supports creation of an index. Migration tool supports the TABLE statement with PRIMARY INDEX and UNIQUE INDEX.The tool will not add DISTRIBUTE", + "product_code":"dws", + "title":"Indexes", + "uri":"dws_16_0069.html", + "doc_type":"tg", + "p_code":"214", + "code":"221" + }, + { + "desc":"A table CONSTRAINT is applied to multiple columns. Migration tool supports the following constraints:CHECK constraint: supported by GaussDB T, GaussDB A, and GaussDB(DWS)", + "product_code":"dws", + "title":"CONSTRAINT", + "uri":"dws_16_0070.html", + "doc_type":"tg", + "p_code":"214", + "code":"222" + }, + { + "desc":"The table orientation can be converted from ROW-STORE to COLUMN store using the WITH (ORIENTATION=COLUMN) in the CREATE TABLE statement. This feature can be enabled/disab", + "product_code":"dws", + "title":"COLUMN STORE", + "uri":"dws_16_0071.html", + "doc_type":"tg", + "p_code":"214", + "code":"223" + }, + { + "desc":"The tool does not support migration of partitions/subpartitions and the partition/subpartition keywords are commented in the migrated scripts:Range partition/subpartition", + "product_code":"dws", + "title":"PARTITION", + "uri":"dws_16_0072.html", + "doc_type":"tg", + "p_code":"214", + "code":"224" + }, + { + "desc":"Input - CREATE TABLE with INDEXOutput", + "product_code":"dws", + "title":"ANALYZE", + "uri":"dws_16_0073.html", + "doc_type":"tg", + "p_code":"214", + "code":"225" + }, + { + "desc":"Migration tool supports queries that specify number of columns (not all columns specified) during INSERT. This can happen when the input INSERT statement does not contain", + "product_code":"dws", + "title":"Support for Specified Columns", + "uri":"dws_16_0074.html", + "doc_type":"tg", + "p_code":"214", + "code":"226" + }, + { + "desc":"The sequence of columns and table names in CREATE INDEX in Teradata is different from that in GaussDB T, GaussDB A, and GaussDB(DWS). Use the configuration parameter dist", + "product_code":"dws", + "title":"Migrating Indexes", + "uri":"dws_16_0075.html", + "doc_type":"tg", + "p_code":"213", "code":"227" }, { - "desc":"This section describes the following date functions:ADD_MONTHSDATE_TRUNCLAST_DAYMONTHS_BETWEENSYSTIMESTAMPADD_MONTHS is an Oracle system function and is not implicitly su", + "desc":"CREATE VIEW (short key CV) is used together with SELECT to create a view.Teradata, GaussDB T, GaussDB A, and GaussDB(DWS) all support the keyword VIEW. It is enclosed by ", "product_code":"dws", - "title":"Date Functions", - "uri":"dws_mt_0135.html", + "title":"Migrating Views", + "uri":"dws_16_0076.html", "doc_type":"tg", - "p_code":"227", + "p_code":"213", "code":"228" }, { - "desc":"This section describes the following LOB functions:DBMS_LOB.APPENDDBMS_LOB.COMPAREDBMS_LOB.CREATETEMPORARYDBMS_LOB.INSTRDBMS_LOB.SUBSTRDBMS_LOB.APPEND function appends th", + "desc":"COLLECT STAT is used in Teradata for collecting optimizer statistics, which will be used for query performance. GaussDB T, GaussDB A, and GaussDB(DWS) use the ANALYZE sta", "product_code":"dws", - "title":"LOB Functions", - "uri":"dws_mt_0136.html", + "title":"COLLECT STATISTICS", + "uri":"dws_16_0077.html", "doc_type":"tg", - "p_code":"227", + "p_code":"213", "code":"229" }, { - "desc":"This section describes the following string functions:LISTAGGSTRAGGWM_CONCATNVL2 and REPLACEQUOTELISTAGG is used to order data in columns within each group specified in t", + "desc":"ACCESS LOCK allows you to read the data from a table that may have been locked for the READ or WRITE.Use the tdMigrateLOCKoption configuration parameter to configure migr", "product_code":"dws", - "title":"String Functions", - "uri":"dws_mt_0137.html", + "title":"ACCESS LOCK", + "uri":"dws_16_0078.html", "doc_type":"tg", - "p_code":"227", + "p_code":"213", "code":"230" }, { - "desc":"Analytical functions compute an aggregate value based on a group of rows. They differ from aggregate functions in that they return multiple rows for each group. Analytica", + "desc":"DBC.COLUMNSview is a table containing information about table and view columns, stored procedures, or macro parameters. The view includes the following column names: Data", "product_code":"dws", - "title":"Analytical Functions", - "uri":"dws_mt_0138.html", + "title":"DBC.COLUMNS", + "uri":"dws_16_0079.html", "doc_type":"tg", - "p_code":"227", + "p_code":"213", "code":"231" }, { - "desc":"Regular expressions specify patterns to match strings using standardized syntax conventions. In Oracle, regular expressions are implemented using a set of SQL functions t", + "desc":"The DSC migrates dbc.tables to their corresponding mig_td_ext.vw_td_dbc_tables.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutput", "product_code":"dws", - "title":"Regular Expression Functions", - "uri":"dws_mt_0139.html", + "title":"DBC.TABLES", + "uri":"dws_16_0080.html", "doc_type":"tg", - "p_code":"227", + "p_code":"213", "code":"232" }, { - "desc":"This section describes the migration syntax of Oracle PL/SQL. The migration syntax determines how the keywords and features are migrated.PL/SQL combines the procedural fe", + "desc":"DSC migrates dbc.indices to the corresponding mig_td_ext.vw_td_dbc_indices.Example: databasename is migrated as mig_td_ext.vw_td_dbc_tables.schemaname.InputOutputIn dbc.i", "product_code":"dws", - "title":"PL/SQL", - "uri":"dws_mt_0141.html", + "title":"DBC.INDICES", + "uri":"dws_16_0081.html", "doc_type":"tg", - "p_code":"205", + "p_code":"213", "code":"233" }, { - "desc":"This section descripes the migration syntax of Oracle PL/SQL Collections. The migration syntax decides how the keywords/features are migrated.A user-defined type (UDT) is", + "desc":"This command displays the COLLECT STATISTICS statement with statistics. Gauss does not have an equivalent for this. Since it does not affect the functionality, this comma", "product_code":"dws", - "title":"PL/SQL Collections (Using User-Defined Types)", - "uri":"dws_mt_0155.html", + "title":"SHOW STATS VALUES SEQUENCED", + "uri":"dws_16_0082.html", "doc_type":"tg", - "p_code":"205", + "p_code":"213", "code":"234" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"PL/SQL Packages", - "uri":"dws_mt_0156.html", + "title":"COMMENT", + "uri":"dws_16_0083.html", "doc_type":"tg", - "p_code":"205", + "p_code":"213", "code":"235" }, { - "desc":"Packages are schema objects that group logically related PL/SQL types, variables, functions and procedures. In Oracle, each package consists of two parts: package specifi", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Packages", - "uri":"dws_mt_0158.html", + "title":"Data Manipulation Language (DML)", + "uri":"dws_16_0084.html", "doc_type":"tg", - "p_code":"235", + "p_code":"195", "code":"236" }, { - "desc":"Package variables are available in Oracle packages that allow variables to retain all the functions and procedures in the package. DSC uses customized functions to help G", + "desc":"The Teradata INSERT (short key INS) statement is used to insert records into a table. DSC supports the INSERT statement.The INSERT INTO TABLE table_name syntax is used in", "product_code":"dws", - "title":"Package Variables", - "uri":"dws_mt_0159.html", + "title":"INSERT", + "uri":"dws_16_0086.html", "doc_type":"tg", - "p_code":"235", + "p_code":"236", "code":"237" }, { - "desc":"The package specification is migrated as a schema named after the package and the procedures and functions in the package body is migrated as Packagename.procedurenameand", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Splitting Packages", - "uri":"dws_mt_0301.html", + "title":"SELECT", + "uri":"dws_16_0087.html", "doc_type":"tg", - "p_code":"235", + "p_code":"236", "code":"238" }, { - "desc":"REF Cursor is a data type that can store the database cursor values and is used to return query results. DSC supports migration of REF CURSOR. The example below shows how", + "desc":"The Teradata SELECT command (short key SEL) is used to specify the table columns from which data is to be retrieved.ANALYZE is used in GaussDB(DWS) for collecting optimiz", "product_code":"dws", - "title":"REF CURSOR", - "uri":"dws_mt_0302.html", + "title":"ANALYZE", + "uri":"dws_16_0088.html", "doc_type":"tg", - "p_code":"235", + "p_code":"238", "code":"239" }, { - "desc":"The pacakge declaration is miagrated as a schema named after the package. The migration can be performed after pkgSchemaNaming is set to false.Input – Create schema for P", + "desc":"For Teradata migration of SELECTstatements, all the clauses (FROM, WHERE, HAVING and GROUP BY) can be listed in any order. The tool will not migrate the statement if it c", "product_code":"dws", - "title":"Creating a Schema for Package", - "uri":"dws_mt_0221.html", + "title":"Order of Clauses", + "uri":"dws_16_0089.html", "doc_type":"tg", - "p_code":"235", + "p_code":"238", "code":"240" }, { - "desc":"REF CURSOR is defined as a return parameter.It can be migrated after plsqlCollectionis set tovarray.Input - VARRAYOutput", + "desc":"The GROUP BY clause can be specified if you want the database to group the selected rows based on the value of expr(s). If this clause contains CUBE, ROLLUPor GROUPING SE", "product_code":"dws", - "title":"VARRAY", - "uri":"dws_mt_0303.html", + "title":"Extended Group By Clause", + "uri":"dws_16_0090.html", "doc_type":"tg", - "p_code":"205", + "p_code":"238", "code":"241" }, { - "desc":"This feature is used to give privileges to users for specific packages. As GaussDB does not support packages, all the procedures and functions defined in the specific pac", + "desc":"GaussDB(DWS) variable names are case insensitive, and TD variable names are case sensitive. To ensure that the TD script is correct before and after the migration, retain", "product_code":"dws", - "title":"Granting Execution Permissions", - "uri":"dws_mt_0304.html", + "title":"SELECT AS", + "uri":"dws_16_0091.html", "doc_type":"tg", - "p_code":"205", + "p_code":"238", "code":"242" }, { - "desc":"Enable & DisableSet package_name_list to bas_lookup_misc_pkg.Enable and disable the function based on configuration parameters.InputOutput", + "desc":"The TOP and SAMPLE clauses of Teradata are migrated to LIMIT in GaussDB(DWS).The DSC also supports migration of TOPstatements with dynamic parameters.For TOPclauses conta", "product_code":"dws", - "title":"Package Name List", - "uri":"dws_mt_0305.html", + "title":"TOP and SAMPLE", + "uri":"dws_16_0092.html", "doc_type":"tg", - "p_code":"205", + "p_code":"238", "code":"243" }, { - "desc":"SubtypeThe customized type in the package cannot be converted.SUBTYPE error_msg IS sad_products_t.exception_description%TYPE;SUBTYPE AR_FLAG IS SAD_RA_LINES_TI.AR_FLAG%TY", + "desc":"The tool supports and migrates the UPDATE(short key UPD) statements.Input: UPDATE with TABLE ALIASOutputInput: UPDATE with TABLE ALIASusing a sub queryOutputInput: UPDATE", "product_code":"dws", - "title":"Data Type", - "uri":"dws_mt_0306.html", + "title":"UPDATE", + "uri":"dws_16_0093.html", "doc_type":"tg", - "p_code":"205", + "p_code":"236", "code":"244" }, { - "desc":"Input-Chinese (OutputInput-Chinese )OutputInput-Chinese,OutputInput-Support Chinese SPACEOutput", + "desc":"DELETE (short key abbreviated as DEL) is an ANSI-compliant SQL syntax operator used to delete existing records from a table. DSC supports the Teradata DELETE statement an", "product_code":"dws", - "title":"Chinese Character Support", - "uri":"dws_mt_0222.html", + "title":"DELETE", + "uri":"dws_16_0094.html", "doc_type":"tg", - "p_code":"205", + "p_code":"236", "code":"245" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"Gauss database in 6.5.0 or later versions support the MERGE function.MERGEis an ANSI-standard SQL syntax operator used to select rows from one or more sources for updatin", "product_code":"dws", - "title":"Netezza Syntax Migration", - "uri":"dws_07_0682.html", + "title":"MERGE", + "uri":"dws_16_0095.html", "doc_type":"tg", - "p_code":"155", + "p_code":"236", "code":"246" }, { - "desc":"DISTRIBUTE ON (column) should be migrated to DISTRIBUTE BY HASH (column).ORGANIZE ON will be commented out.The row-store supports BLOB and CLOB. Column storage does not s", + "desc":"NAMED is used in Teradata to assign a temporary name to an expression or column. NAMED statements used for expressions are migrated to AS in GaussDB T, GaussDB A, and Gau", "product_code":"dws", - "title":"Tables", - "uri":"dws_07_6821.html", + "title":"NAMED", + "uri":"dws_16_0096.html", "doc_type":"tg", - "p_code":"246", + "p_code":"236", "code":"247" }, { - "desc":"PROCEDURE with RETURNS will be modified to FUNCTION with RETURN.Migrate the nzplSQL language to the plpgSQL language or delete the language.The process which is started w", + "desc":"ACTIVITYCOUNTInputIt is a status variable that returns the number of rows affected by an SQL DML statement in an embedded SQL.Output", "product_code":"dws", - "title":"PROCEDURE with RETURNS", - "uri":"dws_07_6822.html", + "title":"ACTIVITYCOUNT", + "uri":"dws_16_0097.html", "doc_type":"tg", - "p_code":"246", + "p_code":"236", "code":"248" }, { - "desc":"NVARCHAR changed to NCHAR VARING.The row_count function is supported for affected row counting.ROW_COUNT identifies the number of rows associated with the previous SQL st", + "desc":"Input - TIMESTAMP with FORMATThe FORMAT phrase sets the format for a specific TIME or TIMESTAMP column or value. A FORMAT phrase overrides the system format.OutputInputOu", "product_code":"dws", - "title":"Procedure", - "uri":"dws_07_6823.html", + "title":"TIMESTAMP", + "uri":"dws_16_0098.html", "doc_type":"tg", - "p_code":"246", + "p_code":"236", "code":"249" }, { - "desc":"Second parameter is missing.Casting the data type.", + "desc":"This section contains the migration syntax for migrating Teradata type casting and formatting syntax. The migration syntax determines how the keywords and features are mi", "product_code":"dws", - "title":"System Functions", - "uri":"dws_07_6824.html", + "title":"Type Casting and Formatting", + "uri":"dws_16_0099.html", "doc_type":"tg", - "p_code":"246", + "p_code":"195", "code":"250" }, + { + "desc":"GaussDB(DWS) provides gsql meta-commands that can be used to replace common BTEQ tool commands. The mostly used replacements are as follows:The meta-command \\q [value] ca", + "product_code":"dws", + "title":"BTEQ Utility Command", + "uri":"dws_16_0100.html", + "doc_type":"tg", + "p_code":"195", + "code":"251" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Operator", - "uri":"dws_07_6825.html", + "title":"Teradata Formats", + "uri":"dws_16_0101.html", "doc_type":"tg", - "p_code":"246", - "code":"251" - }, - { - "desc":"A new configuration parameter \"keywords_addressed_using_doublequote\" should be introduced with the below value:keywords_addressed_using_doublequote=freezekeywords_address", - "product_code":"dws", - "title":"DML", - "uri":"dws_07_6826.html", - "doc_type":"tg", - "p_code":"246", + "p_code":"195", "code":"252" }, { - "desc":"This feature is applicable only for COLUMN store. For ROW store, Unique Index should not be commented.", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Index Migration", - "uri":"dws_07_6827.html", + "title":"System Views", + "uri":"dws_16_0102.html", "doc_type":"tg", - "p_code":"246", + "p_code":"195", "code":"253" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"MySQL Syntax Migration", - "uri":"dws_sct_0013.html", + "title":"MySQL Syntax Migrating", + "uri":"dws_16_0103.html", "doc_type":"tg", - "p_code":"155", + "p_code":"194", "code":"254" }, { - "desc":"MySQL supports a number of basic data types, including numeric, date/time, string (character), LOB, set, binary, and Boolean types. GaussDB(DWS) does not support some bas", + "desc":"Table 1 lists the MySQL keywords and features that can be migrated.The Version column contains the earliest versions that support the keywords or features.The Remarks col", "product_code":"dws", - "title":"Basic Data Types", - "uri":"dws_07_6831.html", + "title":"Supported Keywords and Features", + "uri":"dws_16_0105.html", "doc_type":"tg", "p_code":"254", "code":"255" }, { - "desc":"This section describes the migration syntax of MySQL tables (optional parameter). The migration syntax determines how the keywords and features are migrated. GaussDB(DWS)", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Table (Optional)", - "uri":"dws_07_6832.html", + "title":"Data Types", + "uri":"dws_16_0106.html", "doc_type":"tg", "p_code":"254", "code":"256" }, { - "desc":"This section contains the migration syntax for migrating MySQL table operation. The migration syntax decides how the supported keywords/features are migrated.For details,", + "desc":"A data type is a basic data attribute. Occupied storage space and allowed operations vary according to data types. In a database, data is stored in tables, in which a dat", "product_code":"dws", - "title":"Table Operations", - "uri":"dws_07_6833.html", + "title":"Numeric Types", + "uri":"dws_16_0108.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"257" }, { - "desc":"If MySQL unique indexes (constraints) and primary key constraints are used together during migration, OLAP distribution keys may become unavailable. Therefore, this scena", + "desc":"This section describes the following date and time types: DATETIME, TIME, TIMESTAMP, and YEAR. GaussDB(DWS) does not support these types, and DSC will convert them.The va", "product_code":"dws", - "title":"Unique Indexes", - "uri":"dws_07_6834.html", + "title":"Date/Time Types", + "uri":"dws_16_0109.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"258" }, { - "desc":"GaussDB(DWS) does not support prefix indexes or inline normal indexes. DSC will replace these indexes with normal indexes based on GaussDB features.Inline normal/prefix i", + "desc":"MySQL interprets length specifications in character column definitions in character units. This applies to the CHAR, VARCHAR, and TEXT types. DSC supports the following t", "product_code":"dws", - "title":"Normal and Prefix Indexes", - "uri":"dws_07_6835.html", + "title":"String Types", + "uri":"dws_16_0110.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"259" }, { - "desc":"GaussDB(DWS) does not support hash indexes. DSC will replace these indexes with normal indexes based on GaussDB features.Inline hash indexInputCREATE TABLE `public`.`test", + "desc":"MySQL has spatial data types corresponding to the OpenGIS class. DSC supports the following type conversions:GEOMETRY can store geometry values of any type. The other sin", "product_code":"dws", - "title":"Hash Indexes", - "uri":"dws_07_6836.html", + "title":"Spatial Data Types", + "uri":"dws_16_0111.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"260" }, { - "desc":"GaussDB(DWS) supports B-tree indexes, but the position of the USING BTREE keyword in a statement is different from that in MySQL. DSC will perform adaptation based on Gau", + "desc":"A BLOB is a binary large object that can hold a variable amount of data. The four BLOB types are TINYBLOB, BLOB, MEDIUMBLOB, and LONGBLOB. The only difference between the", "product_code":"dws", - "title":"B-tree Indexes", - "uri":"dws_07_6837.html", + "title":"LOB Types", + "uri":"dws_16_0112.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"261" }, { - "desc":"GaussDB(DWS) does not support spatial indexes. DSC will perform adaptation based on GaussDB features during migration.Inline spatial indexInputCREATE TABLE `public`.`test", + "desc":"In MySQL, an ENUM is a string object with a value chosen from a list of permitted values that are enumerated explicitly in the column specification at table creation.A SE", "product_code":"dws", - "title":"Spatial Indexes", - "uri":"dws_07_6838.html", + "title":"Set Types", + "uri":"dws_16_0113.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"262" }, { - "desc":"MySQL supports both DROP INDEX and ALTER TABLE DROP INDEX for deleting indexes. DSC will perform adaptation based on GaussDB features during migration.DROP INDEXInputCREA", + "desc":"MySQL supports both BOOL and BOOLEAN. DSC supports the following type conversions:Input: BOOL/BOOLEANOutput", "product_code":"dws", - "title":"Delete an Index", - "uri":"dws_07_8310.html", + "title":"Boolean", + "uri":"dws_16_0114.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"263" }, { - "desc":"To comment out a single line, MySQL uses # or --, and GaussDB(DWS) uses --. DSC will replace # with -- for commenting out a single line during migration.InputOutput", + "desc":"In MySQL, the BIT data type is used to store bit values. A type of BIT(M) enables storage of M-bit values. M can range from 1 to 64.MySQL BINARY and VARBINARY types are s", "product_code":"dws", - "title":"Comments", - "uri":"dws_07_8311.html", + "title":"Binary Types", + "uri":"dws_16_0115.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"264" }, { - "desc":"In MySQL, DATABASE is a schema object, which is equivalent to the SCHEMA of Oracle and GaussDB(DWS). DSC supports the following two scenarios:Database creationInputcreate", + "desc":"The JSON data type can be used to store JavaScript Object Notation (JSON) data. DSC supports the following type conversions:Input Example (JSON)Output", "product_code":"dws", - "title":"Databases", - "uri":"dws_07_8312.html", + "title":"JSON Types", + "uri":"dws_16_0116.html", "doc_type":"tg", - "p_code":"254", + "p_code":"256", "code":"265" }, { - "desc":"This section describes the migration syntax of MySQL DML. The migration syntax determines how the keywords and features are migrated.For details, see the following topics", + "desc":"The functions and expressions in MySQL do not exist in GaussDB(DWS) or are different from those in GaussDB(DWS). DSC migrates the functions and expressions based on the s", "product_code":"dws", - "title":"Data Manipulation Language (DML)", - "uri":"dws_07_8313.html", + "title":"Functions and Expressions", + "uri":"dws_16_0117.html", "doc_type":"tg", "p_code":"254", "code":"266" }, { - "desc":"This section describes how to migrate keywords and features related to MySQL transaction and database management.TRANSACTIONDSC will perform adaptation based on GaussDB f", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Transaction Management and Database Management", - "uri":"dws_07_8314.html", + "title":"Schema Objects and Data Definition Language (DDL)", + "uri":"dws_16_0118.html", "doc_type":"tg", "p_code":"254", "code":"267" @@ -2405,146 +2405,1253 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"DB2 Syntax Migration", - "uri":"dws_07_0684.html", + "title":"Table (Optional Parameters and Operations)", + "uri":"dws_16_0119.html", "doc_type":"tg", - "p_code":"155", + "p_code":"267", "code":"268" }, { - "desc":"If a keyword is used as a column name, quotes (\") must be added, for example, \"order\".LONG VARCHAR should be changed to CLOB.LONG VARGRAPHIC.Below attributes of Foreign k", + "desc":"MySQL 8.0.29 has extended the support for ALTER TABLE... ALGORITHM=INSTANT: Users can add columns instantly and delete columns instantly anywhere in a table, and evaluate", "product_code":"dws", - "title":"Tables", - "uri":"dws_07_6841.html", + "title":"ALGORITHM", + "uri":"dws_16_0120.html", "doc_type":"tg", "p_code":"268", "code":"269" }, { - "desc":"FETCH clauseThe fetch-first-clause sets a maximum number of rows that can be retrieved.WITH AS with column listWITH AS with VALUES clauseTABLE function is specified with ", + "desc":"In GaussDB(DWS), the rename clause cannot contain the schema name. The DSC tool supports only the rename operation in the same schema. After the rename operation, the sch", "product_code":"dws", - "title":"DML", - "uri":"dws_07_6842.html", + "title":"ALTER TABLE RENAME", + "uri":"dws_16_0121.html", "doc_type":"tg", "p_code":"268", "code":"270" }, { - "desc":"Reverse Scansindex's schema is different from its table's schema.", + "desc":"In database application, unique numbers that increase automatically are needed to identify records. In MySQL, the AUTO_INCREMENT attribute of a data column can be used to", "product_code":"dws", - "title":"Index Migration (DB2)", - "uri":"dws_07_6843.html", + "title":"AUTO_INCREMENT", + "uri":"dws_16_0122.html", "doc_type":"tg", "p_code":"268", "code":"271" }, { - "desc":"Synonym is referred to Nickname in DB2.", + "desc":"In MySQL, AVG_ROW_LENGTH indicates the average length of each row. This is not supported by GaussDB(DWS) and is deleted by DSC during the migration.InputOutput", "product_code":"dws", - "title":"NICKNAME", - "uri":"dws_07_6844.html", + "title":"AVG_ROW_LENGTH", + "uri":"dws_16_0123.html", "doc_type":"tg", "p_code":"268", "code":"272" }, { - "desc":"SET CURRENT SCHEMA", + "desc":"In ADB, this parameter specifies the number of values stored in each block in columnar storage, which is also the minimum I/O unit. GaussDB(DWS does not support table def", "product_code":"dws", - "title":"Statement", - "uri":"dws_07_6845.html", + "title":"BLOCK_SIZE", + "uri":"dws_16_0124.html", "doc_type":"tg", "p_code":"268", "code":"273" }, { - "desc":"DayMonthYearCurrent dateCurrent timestampPOSSTRValueThe date function returns a date using a value.", + "desc":"CHARSET specifies the default character set for a table. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword dur", "product_code":"dws", - "title":"System Functions", - "uri":"dws_07_6846.html", + "title":"CHARSET", + "uri":"dws_16_0125.html", "doc_type":"tg", "p_code":"268", "code":"274" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"In MySQL, CHECKSUM maintains a live checksum for all rows. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword d", "product_code":"dws", - "title":"Command Reference", - "uri":"dws_mt_0183.html", + "title":"CHECKSUM", + "uri":"dws_16_0126.html", "doc_type":"tg", - "p_code":"155", + "p_code":"268", "code":"275" }, { - "desc":"runDSC.sh or runDSC.bat is used to migrate schemas and queries of Teradata, Oracle, Netezza, MySQL, and DB2 to GaussDB(DWS).Linux:Windows:It is mandatory to specify the s", + "desc":"It is a clustered index in ADB that defines the sorting sequence in a table. The logical sequence of key values in a clustered index determines the physical sequence of r", "product_code":"dws", - "title":"Database Schema Conversion", - "uri":"dws_mt_0184.html", + "title":"CLUSTERED KEY", + "uri":"dws_16_0127.html", "doc_type":"tg", - "p_code":"275", + "p_code":"268", "code":"276" }, { - "desc":"The version command is used to display the version number of the DSC.Linux:Windows:NoneLinux:Windows:", + "desc":"In MySQL, COLLATE specifies a default database sorting rule. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword", "product_code":"dws", - "title":"Version", - "uri":"dws_mt_0185.html", + "title":"COLLATE", + "uri":"dws_16_0128.html", "doc_type":"tg", - "p_code":"275", + "p_code":"268", "code":"277" }, { - "desc":"The help command is used to provide the help information for the commands supported by DSC.Linux:Windows:NoneNoneLinux:Windows:Linux:Windows:", + "desc":"In MySQL, COMMENT is a comment for a table. In GaussDB(DWS), this attribute can be used to modify table definition. During migration using DSC, additional table attribute", "product_code":"dws", - "title":"Help", - "uri":"dws_mt_0186.html", + "title":"COMMENT", + "uri":"dws_16_0129.html", "doc_type":"tg", - "p_code":"275", + "p_code":"268", "code":"278" }, + { + "desc":"GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the attribute during migration.In MySQL, the keyword CONNECTION is used ", + "product_code":"dws", + "title":"CONNECTION", + "uri":"dws_16_0130.html", + "doc_type":"tg", + "p_code":"268", + "code":"279" + }, + { + "desc":"In MySQL, when using ALTER TABLE to add a column with the not null constraint, if no value is specified, a default value is inserted. However, an error will be reported a", + "product_code":"dws", + "title":"DEFAULT", + "uri":"dws_16_0131.html", + "doc_type":"tg", + "p_code":"268", + "code":"280" + }, + { + "desc":"DELAY_KEY_WRITE is valid only for MyISAM tables. It is used to delay updates until the table is closed. GaussDB(DWS) does not support table definition modification using ", + "product_code":"dws", + "title":"DELAY_KEY_WRITE", + "uri":"dws_16_0132.html", + "doc_type":"tg", + "p_code":"268", + "code":"281" + }, + { + "desc":"ADB supports distribution keys. During DSC migration, the corresponding distribution keys are retained.InputOutput", + "product_code":"dws", + "title":"DISTRIBUTE BY", + "uri":"dws_16_0133.html", + "doc_type":"tg", + "p_code":"268", + "code":"282" + }, + { + "desc":"DIRECTORY enables a tablespace to be created outside the data directory and index directory. It allows DATA DIRECTORY and INDEX DIRECTORY. GaussDB(DWS) does not support t", + "product_code":"dws", + "title":"DIRECTORY", + "uri":"dws_16_0134.html", + "doc_type":"tg", + "p_code":"268", + "code":"283" + }, + { + "desc":"In MySQL, ENGINE specifies the storage engine for a table. When the storage engine is ARCHIVE, BLACKHOLE, CSV, FEDERATED, INNODB, MYISAM, MEMORY, MRG_MYISAM, NDB, NDBCLUS", + "product_code":"dws", + "title":"ENGINE", + "uri":"dws_16_0135.html", + "doc_type":"tg", + "p_code":"268", + "code":"284" + }, + { + "desc":"For foreign key constraints in MySQL, GaussDB(DWS) does not support them modifying table definition. They will be deleted during DSC migration.InputOutput", + "product_code":"dws", + "title":"FOREIGN_KEY_CHECKS", + "uri":"dws_16_0136.html", + "doc_type":"tg", + "p_code":"268", + "code":"285" + }, + { + "desc":"DSC supports the conversion of IF NOT EXISTS, which is reserved during the migration.InputOutput", + "product_code":"dws", + "title":"IF NOT EXISTS", + "uri":"dws_16_0137.html", + "doc_type":"tg", + "p_code":"268", + "code":"286" + }, + { + "desc":"In the ADB, index_all='Y' is used to create the full-column index. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the a", + "product_code":"dws", + "title":"INDEX_ALL", + "uri":"dws_16_0138.html", + "doc_type":"tg", + "p_code":"268", + "code":"287" + }, + { + "desc":"INSERT_METHOD specifies the table into which the row should be inserted. Use a value of FIRST or LAST to have inserts go to the first or last table, or a value of NO to p", + "product_code":"dws", + "title":"INSERT_METHOD", + "uri":"dws_16_0139.html", + "doc_type":"tg", + "p_code":"268", + "code":"288" + }, + { + "desc":"KEY_BLOCK_SIZE choices vary depending on the storage engine used for a table. For MyISAM tables, KEY_BLOCK_SIZE optionally specifies the size in bytes to be used for inde", + "product_code":"dws", + "title":"KEY_BLOCK_SIZE", + "uri":"dws_16_0140.html", + "doc_type":"tg", + "p_code":"268", + "code":"289" + }, + { + "desc":"GaussDB(DWS) does not support the ALTER TABLEtbNameLOCK statement of MySQL, which will be deleted by DSC during migration.InputOutput", + "product_code":"dws", + "title":"LOCK", + "uri":"dws_16_0141.html", + "doc_type":"tg", + "p_code":"268", + "code":"290" + }, + { + "desc":"In MySQL, MAX_ROWS indicates the maximum number of rows that can be stored in a table. This attribute will be deleted during migration using DSC.InputOutput", + "product_code":"dws", + "title":"MAX_ROWS", + "uri":"dws_16_0142.html", + "doc_type":"tg", + "p_code":"268", + "code":"291" + }, + { + "desc":"MIN_ROWS indicates the minimum number of rows that can be stored in a table. This attribute will be deleted during migration using DSC.InputOutput", + "product_code":"dws", + "title":"MIN_ROWS", + "uri":"dws_16_0143.html", + "doc_type":"tg", + "p_code":"268", + "code":"292" + }, + { + "desc":"In MySQL, PACK_KEYS specifies the index compression mode in the MyISAM storage engine. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during m", + "product_code":"dws", + "title":"PACK_KEYS", + "uri":"dws_16_0145.html", + "doc_type":"tg", + "p_code":"268", + "code":"293" + }, + { + "desc":"In MySQL, PARTITION BY is used to create partitioned tables. Currently, GaussDB(DWS) supports only range and list partitions in MySQL.Hash partitions of PARTITION BY are ", + "product_code":"dws", + "title":"PARTITION BY", + "uri":"dws_16_0146.html", + "doc_type":"tg", + "p_code":"268", + "code":"294" + }, + { + "desc":"In MySQL, PASSWORD indicates the user password. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during migration.InputOutput", + "product_code":"dws", + "title":"PASSWORD", + "uri":"dws_16_0147.html", + "doc_type":"tg", + "p_code":"268", + "code":"295" + }, + { + "desc":"ROW_FORMAT defines the physical format in which the rows are stored. Row format choices vary depending on the storage engine used for the table. If you specify a row form", + "product_code":"dws", + "title":"ROW_FORMAT", + "uri":"dws_16_0148.html", + "doc_type":"tg", + "p_code":"268", + "code":"296" + }, + { + "desc":"STATS_AUTO_RECALC specifies whether to automatically recalculate persistent statistics for an InnoDB table. GaussDB(DWS) does not support this attribute, which will be de", + "product_code":"dws", + "title":"STATS_AUTO_RECALC", + "uri":"dws_16_0149.html", + "doc_type":"tg", + "p_code":"268", + "code":"297" + }, + { + "desc":"In MySQL, STATS_PERSISTENT specifies whether to enable persistence statistics for an InnoDB table. The CREATE TABLE and ALTER TABLE statements can be used to enable persi", + "product_code":"dws", + "title":"STATS_PERSISTENT", + "uri":"dws_16_0150.html", + "doc_type":"tg", + "p_code":"268", + "code":"298" + }, + { + "desc":"STATS_SAMPLE_PAGES specifies the number of index pages to sample when cardinality and other statistics for an indexed column are estimated. DSC will delete this attribute", + "product_code":"dws", + "title":"STATS_SAMPLE_PAGES", + "uri":"dws_16_0151.html", + "doc_type":"tg", + "p_code":"268", + "code":"299" + }, + { + "desc":"UNION is a table creation parameter of the MERGE storage engine. Creating a table using this keyword is similar to creating a common view. The created table logically com", + "product_code":"dws", + "title":"UNION", + "uri":"dws_16_0152.html", + "doc_type":"tg", + "p_code":"268", + "code":"300" + }, + { + "desc":"WITH AS is used in GaussDB(DWS) to declare one or more subqueries that can be referenced by name in the main query. It is equivalent to a temporary table. DSC supports th", + "product_code":"dws", + "title":"WITH AS", + "uri":"dws_16_0153.html", + "doc_type":"tg", + "p_code":"268", + "code":"301" + }, + { + "desc":"MySQL uses the CHANGE keyword to change column names and data types and set NOT NULL constraints. DSC will perform adaptation based on GaussDB(DWS) features during migrat", + "product_code":"dws", + "title":"CHANGE (Column Modification)", + "uri":"dws_16_0154.html", + "doc_type":"tg", + "p_code":"268", + "code":"302" + }, + { + "desc":"Specifies an expression producing a Boolean result which new or updated rows must satisfy for an insert or update operation to succeed. Expressions evaluating to TRUE or ", + "product_code":"dws", + "title":"CHECK Constraint", + "uri":"dws_16_0155.html", + "doc_type":"tg", + "p_code":"268", + "code":"303" + }, + { + "desc":"Both GaussDB(DWS) and MySQL support using the DROP statement to delete tables. However, GaussDB(DWS) does not support the RESTRICT | CASCADE keyword in the DROP statement", + "product_code":"dws", + "title":"DROP (Table Deletion)", + "uri":"dws_16_0156.html", + "doc_type":"tg", + "p_code":"268", + "code":"304" + }, + { + "desc":"MySQL databases support CREATE TABLE. LIKE is a method with which a table is created by cloning the old table structure, It is also supported by GaussDB(DWS). DSC will ad", + "product_code":"dws", + "title":"LIKE (Table Cloning)", + "uri":"dws_16_0157.html", + "doc_type":"tg", + "p_code":"268", + "code":"305" + }, + { + "desc":"MySQL uses the MODIFY keyword to change column data types and set NOT NULL constraints. DSC will perform adaptation based on GaussDB(DWS) features during migration.InputO", + "product_code":"dws", + "title":"MODIFY (Modifying a Cloumn)", + "uri":"dws_16_0158.html", + "doc_type":"tg", + "p_code":"268", + "code":"306" + }, + { + "desc":"In MySQL, the TABLE keyword can be omitted when the TRUNCATE statement is used to delete table data. GaussDB(DWS) does not support this usage. In addition, DSC will add C", + "product_code":"dws", + "title":"TRUNCATE (Table Deletion)", + "uri":"dws_16_0159.html", + "doc_type":"tg", + "p_code":"268", + "code":"307" + }, + { + "desc":"GaussDB(DWS) supports the creation of roundrobin tables. You can set the table.type in Table 1. Set table.type=ROUND-ROBIN.InputOutput", + "product_code":"dws", + "title":"ROUNDROBIN Table", + "uri":"dws_16_0160.html", + "doc_type":"tg", + "p_code":"268", + "code":"308" + }, + { + "desc":"The statement for renaming a table in MySQL is slightly different from that in GaussDB(DWS). DSC will perform adaptation based on GaussDB(DWS) features during migration.C", + "product_code":"dws", + "title":"RENAME (Table Renaming)", + "uri":"dws_16_0161.html", + "doc_type":"tg", + "p_code":"268", + "code":"309" + }, + { + "desc":"In MySQL, the COLUMN keyword can be omitted when the ALTER statement is used to set the default value of a column. DSC will perform adaptation based on GaussDB(DWS) featu", + "product_code":"dws", + "title":"SET|DROP COLUMN DEFAULT VALUE", + "uri":"dws_16_0162.html", + "doc_type":"tg", + "p_code":"268", + "code":"310" + }, + { + "desc":"In GaussDB(DWS), reserved keywords must be enclosed in double quotation marks when they are used as column names. The following reserved keywords are supported: desc, che", + "product_code":"dws", + "title":"Renaming a Column", + "uri":"dws_16_0163.html", + "doc_type":"tg", + "p_code":"268", + "code":"311" + }, + { + "desc":"GaussDB(DWS) supports column-store table compression, but does not support row-store table compression. DSC performs migration based on GaussDB(DWS) features.Compression ", + "product_code":"dws", + "title":"Row-Store/Column-Store Table Compression", + "uri":"dws_16_0164.html", + "doc_type":"tg", + "p_code":"268", + "code":"312" + }, + { + "desc":"The statements for adding and deleting columns in MySQL are different from those in GaussDB(DWS). DSC will perform adaptation based on GaussDB(DWS) features during migrat", + "product_code":"dws", + "title":"Adding/Deleting a Column", + "uri":"dws_16_0165.html", + "doc_type":"tg", + "p_code":"268", + "code":"313" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"Log Reference", - "uri":"dws_mt_0187.html", + "title":"Indexes", + "uri":"dws_16_0166.html", "doc_type":"tg", - "p_code":"155", - "code":"279" + "p_code":"267", + "code":"314" }, { - "desc":"The log files are the repository for all operations and status of the DSC. The following log files are available:SQL Migration LogsDSC.log: SQL Migration all activities.D", + "desc":"GaussDB(DWS) does not support the combination of unique indexes (constraints) and primary key constraints. DSC will perform adaptation based on GaussDB(DWS) features duri", + "product_code":"dws", + "title":"Unique Indexes", + "uri":"dws_16_0167.html", + "doc_type":"tg", + "p_code":"314", + "code":"315" + }, + { + "desc":"GaussDB(DWS) does not support prefix indexes or inline normal indexes. DSC will replace these indexes with normal indexes based on GaussDB(DWS) features.Inline normal/pre", + "product_code":"dws", + "title":"Normal and Prefix Indexes", + "uri":"dws_16_0168.html", + "doc_type":"tg", + "p_code":"314", + "code":"316" + }, + { + "desc":"GaussDB(DWS) does not support hash indexes. DSC will replace these indexes with normal indexes based on GaussDB(DWS) features.Inline hash indexesInputCREATE TABLE `public", + "product_code":"dws", + "title":"Hash Indexes", + "uri":"dws_16_0169.html", + "doc_type":"tg", + "p_code":"314", + "code":"317" + }, + { + "desc":"GaussDB(DWS) supports B-tree indexes, but the position of the USING BTREE keyword in a statement is different from that in MySQL. DSC will perform adaptation based on Gau", + "product_code":"dws", + "title":"B-tree Indexes", + "uri":"dws_16_0170.html", + "doc_type":"tg", + "p_code":"314", + "code":"318" + }, + { + "desc":"GaussDB(DWS) does not support spatial indexes. DSC will perform adaptation based on GaussDB(DWS) features during migration.Inline spatial indexInputCREATE TABLE `public`.", + "product_code":"dws", + "title":"Spatial Indexes", + "uri":"dws_16_0171.html", + "doc_type":"tg", + "p_code":"314", + "code":"319" + }, + { + "desc":"GaussDB(DWS) does not support full-text indexes. DSC will perform adaptation based on GaussDB(DWS) features during migration.Inline full-text indexInput## A.\nCREATE TABLE", + "product_code":"dws", + "title":"Full-Text Indexes", + "uri":"dws_16_0172.html", + "doc_type":"tg", + "p_code":"314", + "code":"320" + }, + { + "desc":"MySQL supports both DROP INDEX and ALTER TABLE DROP INDEX for deleting indexes. DSC will perform adaptation based on GaussDB(DWS) features during migration.DROP INDEXInpu", + "product_code":"dws", + "title":"Deleting an Index", + "uri":"dws_16_0173.html", + "doc_type":"tg", + "p_code":"314", + "code":"321" + }, + { + "desc":"DSC supports renaming indexes. Prefix a table name to an index name to prevent name conflicts. (Only DDL statements with specific index names can be created. Currently, t", + "product_code":"dws", + "title":"Renaming an Index", + "uri":"dws_16_0174.html", + "doc_type":"tg", + "p_code":"314", + "code":"322" + }, + { + "desc":"To comment out a single line, MySQL uses # or --, and GaussDB(DWS) uses --. DSC will replace # with -- for commenting out a single line during migration.InputOutput", + "product_code":"dws", + "title":"Comment", + "uri":"dws_16_0175.html", + "doc_type":"tg", + "p_code":"267", + "code":"323" + }, + { + "desc":"In MySQL, DATABASE is a schema object, which is equivalent to the SCHEMA of Oracle and GaussDB(DWS). DSC supports the following two scenarios:Database creationInputcreate", + "product_code":"dws", + "title":"Databases", + "uri":"dws_16_0176.html", + "doc_type":"tg", + "p_code":"267", + "code":"324" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Data Manipulation Language (DML)", + "uri":"dws_16_0177.html", + "doc_type":"tg", + "p_code":"254", + "code":"325" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"SELECT", + "uri":"dws_16_0178.html", + "doc_type":"tg", + "p_code":"325", + "code":"326" + }, + { + "desc":"Aliases in MySQL contain single quotation marks, which are not supported by GaussDB(DWS). DSC changes them to double quotation marks during migration.InputOutputAliases a", + "product_code":"dws", + "title":"Quotation Marks", + "uri":"dws_16_0179.html", + "doc_type":"tg", + "p_code":"326", + "code":"327" + }, + { + "desc":"In MySQL, the interval expression format is INTERVAL N, which is not supported by GaussDB(DWS) and needs to be converted to INTERVAL'N'.InputOutput", + "product_code":"dws", + "title":"INTERVAL", + "uri":"dws_16_0180.html", + "doc_type":"tg", + "p_code":"326", + "code":"328" + }, + { + "desc":"In MySQL, in a division expression, if the divisor is 0, null is returned. GaussDB(DWS) reports an error. Therefore, the division expression is converted by adding an if ", + "product_code":"dws", + "title":"Division Expressions", + "uri":"dws_16_0181.html", + "doc_type":"tg", + "p_code":"326", + "code":"329" + }, + { + "desc":"During MySQL/ADB group query, non-group columns can be queried. During GaussDB(DWS) group query, only group columns and aggregate functions can be queried, and if non-gro", + "product_code":"dws", + "title":"GROUP BY Conversion", + "uri":"dws_16_0182.html", + "doc_type":"tg", + "p_code":"326", + "code":"330" + }, + { + "desc":"group by column with rollup in MySQL needs to be converted to group by rollup (column) in GaussDB(DWS).InputOutput", + "product_code":"dws", + "title":"ROLLUP", + "uri":"dws_16_0183.html", + "doc_type":"tg", + "p_code":"326", + "code":"331" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"INSERT", + "uri":"dws_16_0184.html", + "doc_type":"tg", + "p_code":"325", + "code":"332" + }, + { + "desc":"MySQL uses HIGH_PRIORITY will override the effect of the LOW_PRIORITY option.InputOutput", + "product_code":"dws", + "title":"HIGH_PRIORITY", + "uri":"dws_16_0185.html", + "doc_type":"tg", + "p_code":"332", + "code":"333" + }, + { + "desc":"When the LOW_PRIORITY modifier is used, execution of INSERT is delayed.InputOutput", + "product_code":"dws", + "title":"LOW_PRIORITY", + "uri":"dws_16_0186.html", + "doc_type":"tg", + "p_code":"332", + "code":"334" + }, + { + "desc":"When inserting into a partitioned table, you can control which partitions and subpartitions accept new rows.InputOutput", + "product_code":"dws", + "title":"PARTITION", + "uri":"dws_16_0187.html", + "doc_type":"tg", + "p_code":"332", + "code":"335" + }, + { + "desc":"In MySQL 5.7, the DELAYED keyword is recognized but ignored by the server.InputOutput", + "product_code":"dws", + "title":"DELAYED", + "uri":"dws_16_0188.html", + "doc_type":"tg", + "p_code":"332", + "code":"336" + }, + { + "desc":"When the IGNORE modifier is used, errors that occur during INSERT execution are ignored.InputOutput", + "product_code":"dws", + "title":"IGNORE", + "uri":"dws_16_0189.html", + "doc_type":"tg", + "p_code":"332", + "code":"337" + }, + { + "desc":"INSERT statements that use the VALUES syntax can insert multiple lines, separated by commas.InputOutput", + "product_code":"dws", + "title":"VALUES", + "uri":"dws_16_0190.html", + "doc_type":"tg", + "p_code":"332", + "code":"338" + }, + { + "desc":"INSERT uses the ON DUPLICATE KEY UPDATE clause to update existing rows.InputOutput", + "product_code":"dws", + "title":"ON DUPLICATE KEY UPDATE", + "uri":"dws_16_0191.html", + "doc_type":"tg", + "p_code":"332", + "code":"339" + }, + { + "desc":"MySQL INSERT...SET statement inserts rows based on explicitly specified values.InputOutput", + "product_code":"dws", + "title":"SET", + "uri":"dws_16_0192.html", + "doc_type":"tg", + "p_code":"332", + "code":"340" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"UPDATE", + "uri":"dws_16_0193.html", + "doc_type":"tg", + "p_code":"325", + "code":"341" + }, + { + "desc":"With the LOW_PRIORITY modifier, execution of UPDATE is delayed.InputOutput", + "product_code":"dws", + "title":"LOW_PRIORITY", + "uri":"dws_16_0194.html", + "doc_type":"tg", + "p_code":"341", + "code":"342" + }, + { + "desc":"In MySQL, if an UPDATE statement includes an ORDER BY clause, the rows will be updated in the order specified by the clause.InputOutput", + "product_code":"dws", + "title":"ORDER BY", + "uri":"dws_16_0195.html", + "doc_type":"tg", + "p_code":"341", + "code":"343" + }, + { + "desc":"UPDATE LIMIT syntax can be used to limit the scope. A clause is a limit on row matching. As long as the rows that satisfy the clause are found, the statements will stop, ", + "product_code":"dws", + "title":"LIMIT", + "uri":"dws_16_0196.html", + "doc_type":"tg", + "p_code":"341", + "code":"344" + }, + { + "desc":"With the IGNORE modifier, the UPDATE statement does not abort even if errors occur during execution.InputOutput", + "product_code":"dws", + "title":"IGNORE", + "uri":"dws_16_0197.html", + "doc_type":"tg", + "p_code":"341", + "code":"345" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"REPLACE", + "uri":"dws_16_0198.html", + "doc_type":"tg", + "p_code":"325", + "code":"346" + }, + { + "desc":"MySQL REPLACE supports the use of LOW_PRIORITY, which is converted by the Migration tool.InputOutput", + "product_code":"dws", + "title":"LOW_PRIORITY", + "uri":"dws_16_0199.html", + "doc_type":"tg", + "p_code":"346", + "code":"347" + }, + { + "desc":"MySQL REPLACE supports explicit partitioning selection using the PARTITION keyword and a comma-separated name list for partitions, subpartitions, or both.InputOutput", + "product_code":"dws", + "title":"PARTITION", + "uri":"dws_16_0200.html", + "doc_type":"tg", + "p_code":"346", + "code":"348" + }, + { + "desc":"DELAYED INSERT and REPLACE operations were deprecated in MySQL 5.6. In MySQL 5.7, DELAYED was not supported. The server recognizes but ignores the DELAYED keyword, handle", + "product_code":"dws", + "title":"DELAYED", + "uri":"dws_16_0201.html", + "doc_type":"tg", + "p_code":"346", + "code":"349" + }, + { + "desc":"MySQL REPLACE supports a statement to insert or delete multiple values, separated by commas.InputOutput", + "product_code":"dws", + "title":"VALUES", + "uri":"dws_16_0202.html", + "doc_type":"tg", + "p_code":"346", + "code":"350" + }, + { + "desc":"MySQL REPLACE supports the use of SET settings, which the Migration tool will convert.InputOutput", + "product_code":"dws", + "title":"SET", + "uri":"dws_16_0203.html", + "doc_type":"tg", + "p_code":"346", + "code":"351" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Transaction Management and Database Management", + "uri":"dws_16_0204.html", + "doc_type":"tg", + "p_code":"254", + "code":"352" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Transaction Management", + "uri":"dws_16_0205.html", + "doc_type":"tg", + "p_code":"352", + "code":"353" + }, + { + "desc":"DSC will perform adaptation based on GaussDB features during MySQL transaction statement migration.InputOutput", + "product_code":"dws", + "title":"TRANSACTION", + "uri":"dws_16_0206.html", + "doc_type":"tg", + "p_code":"353", + "code":"354" + }, + { + "desc":"DSC will perform adaptation based on GaussDB features during the migration of MySQL table locking statements which are used in transaction processing.InputOutput", + "product_code":"dws", + "title":"LOCK", + "uri":"dws_16_0207.html", + "doc_type":"tg", + "p_code":"353", + "code":"355" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Database Management", + "uri":"dws_16_0208.html", + "doc_type":"tg", + "p_code":"352", + "code":"356" + }, + { + "desc":"DSC will replace MySQL SET CHARACTER SET with SET SESSION NAMES during migration. The following table lists character set mapping.InputOutput", + "product_code":"dws", + "title":"SET CHARACTER", + "uri":"dws_16_0209.html", + "doc_type":"tg", + "p_code":"356", + "code":"357" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Oracle Syntax Migration", + "uri":"dws_mt_0104.html", + "doc_type":"tg", + "p_code":"194", + "code":"358" + }, + { + "desc":"This section lists the Oracle features supported by the syntax migration tool, and provides the Oracle syntax and the equivalent GaussDB(DWS) syntax for each feature. The", "product_code":"dws", "title":"Overview", - "uri":"dws_mt_0188.html", + "uri":"dws_mt_0105.html", "doc_type":"tg", - "p_code":"279", - "code":"280" + "p_code":"358", + "code":"359" }, { - "desc":"The SQL DSC (DSC.jar) supports the following types of logging:Activity LoggingError LoggingsuccessReadsuccessWriteIf a user specifies a log path, then all the logs are sa", + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dws", - "title":"SQL Migration Logs", - "uri":"dws_mt_0189.html", + "title":"Schema Objects", + "uri":"dws_mt_0106.html", "doc_type":"tg", - "p_code":"279", - "code":"281" + "p_code":"358", + "code":"360" }, { - "desc":"The DSC writes all log information to a single file, perlDSC.log.Since the DSC will execute the SQL to migrate the SQL scripts inside Perl files, the following SQL migra", + "desc":"The CREATE TABLE statement in Oracle databases is used to create new tables. GaussDB(DWS) also supports this statement. So it does not need to be migrated.The ALTER TABLE", "product_code":"dws", - "title":"Perl Migration Logs", - "uri":"dws_mt_0190.html", + "title":"Tables", + "uri":"dws_mt_0108.html", "doc_type":"tg", - "p_code":"279", - "code":"282" + "p_code":"360", + "code":"361" }, { - "desc":"This section contains a list of troubleshooting steps and solutions for issues encountered while using DSC.The table lists the troubleshooting symptoms/issues along with ", + "desc":"GaussDB(DWS) does not support GLOBAL TEMPORARY TABLE, and it will be migrated to LOCAL TEMPORARY TABLE.ON COMMIT DELETE ROWS is also not supported, and will be migrated t", "product_code":"dws", - "title":"Troubleshooting", - "uri":"dws_mt_0191.html", + "title":"Temporary Tables", + "uri":"dws_mt_0109.html", "doc_type":"tg", - "p_code":"155", - "code":"283" + "p_code":"360", + "code":"362" + }, + { + "desc":"Global temporary tables are converted to local temporary tables.Input - GLOBAL TEMPORARY TABLEOutput", + "product_code":"dws", + "title":"Global Temporary Tables", + "uri":"dws_mt_0212.html", + "doc_type":"tg", + "p_code":"360", + "code":"363" + }, + { + "desc":"When an index is created in GaussDB(DWS), a schema name cannot be specified along with the index name. The index will be automatically created in the schema where the ind", + "product_code":"dws", + "title":"Indexes", + "uri":"dws_mt_0110.html", + "doc_type":"tg", + "p_code":"360", + "code":"364" + }, + { + "desc":"A view is a logical table that is based on one or more tables or views. A view itself contains no data.In the source file, if the table names are not qualified with the s", + "product_code":"dws", + "title":"Views", + "uri":"dws_mt_0111.html", + "doc_type":"tg", + "p_code":"360", + "code":"365" + }, + { + "desc":"A sequence is an Oracle object used to generate a number sequence. This can be useful when you need to create an autonumber column to act as a primary key.If MigSupportSe", + "product_code":"dws", + "title":"Sequences", + "uri":"dws_mt_0112.html", + "doc_type":"tg", + "p_code":"360", + "code":"366" + }, + { + "desc":"In Oracle, the DROP TABLE statement moves a table to the recycle bin. The PURGE statement is used to remove a table or index from the recycle bin and release all of the s", + "product_code":"dws", + "title":"PURGE", + "uri":"dws_mt_0113.html", + "doc_type":"tg", + "p_code":"360", + "code":"367" + }, + { + "desc":"DSC supports GaussDB(DWS) keywords, such as NAME, LIMIT, OWNER, KEY, and CAST. These keywords must be enclosed in double quotation marks.The keywords NAME, VERSION, LABEL", + "product_code":"dws", + "title":"Database Keywords", + "uri":"dws_mt_0114.html", + "doc_type":"tg", + "p_code":"360", + "code":"368" + }, + { + "desc":"Input – COMPRESS PhraseOutput", + "product_code":"dws", + "title":"COMPRESS Phrase", + "uri":"dws_07_6814.html", + "doc_type":"tg", + "p_code":"358", + "code":"369" + }, + { + "desc":"There is a configuration parameter that is introduced for this feature named BitmapIndexSupport which default value is comment, then the sample input and output are as fo", + "product_code":"dws", + "title":"Bitmap Index", + "uri":"dws_07_6815.html", + "doc_type":"tg", + "p_code":"358", + "code":"370" + }, + { + "desc":"Input – custom tablespaceOutput", + "product_code":"dws", + "title":"Custom Tablespace", + "uri":"dws_07_6816.html", + "doc_type":"tg", + "p_code":"358", + "code":"371" + }, + { + "desc":"Supplemental columns can be recorded in redo log files. The process of recording these additional columns is called supplemental logging. Oracle supports this function, b", + "product_code":"dws", + "title":"Supplemental Log Data", + "uri":"dws_07_6817.html", + "doc_type":"tg", + "p_code":"358", + "code":"372" + }, + { + "desc":"\"Data type LONG RAW\" is not supported in the CREATE TABLE statement. LONG RAW data type needs to be replaced with Byte.InputOutput", + "product_code":"dws", + "title":"LONG RAW", + "uri":"dws_07_6818.html", + "doc_type":"tg", + "p_code":"358", + "code":"373" + }, + { + "desc":"SYS_GUID is a built-in function which returns the Global Unique Identifier (GUID) for a row in a table. It accepts no arguments and returns a RAW value of 16 bytes.InputO", + "product_code":"dws", + "title":"SYS_GUID", + "uri":"dws_07_6819.html", + "doc_type":"tg", + "p_code":"358", + "code":"374" + }, + { + "desc":"This section describes the migration syntax of Oracle DML. The migration syntax decides how the keywords/features are migrated.For details, see the following topics:SELEC", + "product_code":"dws", + "title":"DML", + "uri":"dws_mt_0115.html", + "doc_type":"tg", + "p_code":"358", + "code":"375" + }, + { + "desc":"This section contains the migration syntax of Oracle Pseudo Columns. The migration syntax decides how the keywords/features are migrated.A pseudo column is similar to a t", + "product_code":"dws", + "title":"Pseudo Columns", + "uri":"dws_mt_0128.html", + "doc_type":"tg", + "p_code":"358", + "code":"376" + }, + { + "desc":"This section describes the migration syntax of Oracle OUTER JOIN. The migration syntax determines how the keywords/features are migrated.An OUTER JOIN returns all rows th", + "product_code":"dws", + "title":"OUTER JOIN", + "uri":"dws_mt_0132.html", + "doc_type":"tg", + "p_code":"358", + "code":"377" + }, + { + "desc":"Join is supported by GaussDB(DWS), so parameter supportJoinOperatoris added.OUTER QUERY (+)can be migrated when supportJoinOperatoris set to false.Input-OUTER QUERY(+)Out", + "product_code":"dws", + "title":"OUTER QUERY (+)", + "uri":"dws_mt_0215.html", + "doc_type":"tg", + "p_code":"358", + "code":"378" + }, + { + "desc":"Input-CONNECT BYOutputInput - CONNECT BY multiple tablesThe syntax shows the relationship between each child row and its parent row. It uses the CONNECT BY xxx PRIOR clau", + "product_code":"dws", + "title":"CONNECT BY", + "uri":"dws_mt_0216.html", + "doc_type":"tg", + "p_code":"358", + "code":"379" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"System Functions", + "uri":"dws_mt_0133.html", + "doc_type":"tg", + "p_code":"358", + "code":"380" + }, + { + "desc":"This section describes the following date functions:ADD_MONTHSDATE_TRUNCLAST_DAYMONTHS_BETWEENSYSTIMESTAMPADD_MONTHS is an Oracle system function and is not implicitly su", + "product_code":"dws", + "title":"Date Functions", + "uri":"dws_mt_0135.html", + "doc_type":"tg", + "p_code":"380", + "code":"381" + }, + { + "desc":"This section describes the following LOB functions:DBMS_LOB.APPENDDBMS_LOB.COMPAREDBMS_LOB.CREATETEMPORARYDBMS_LOB.INSTRDBMS_LOB.SUBSTRDBMS_LOB.APPEND function appends th", + "product_code":"dws", + "title":"LOB Functions", + "uri":"dws_mt_0136.html", + "doc_type":"tg", + "p_code":"380", + "code":"382" + }, + { + "desc":"This section describes the following string functions:LISTAGGSTRAGGWM_CONCATNVL2 and REPLACEQUOTELISTAGG is used to order data in columns within each group specified in t", + "product_code":"dws", + "title":"String Functions", + "uri":"dws_mt_0137.html", + "doc_type":"tg", + "p_code":"380", + "code":"383" + }, + { + "desc":"Analytical functions compute an aggregate value based on a group of rows. They differ from aggregate functions in that they return multiple rows for each group. Analytica", + "product_code":"dws", + "title":"Analytical Functions", + "uri":"dws_mt_0138.html", + "doc_type":"tg", + "p_code":"380", + "code":"384" + }, + { + "desc":"Regular expressions specify patterns to match strings using standardized syntax conventions. In Oracle, regular expressions are implemented using a set of SQL functions t", + "product_code":"dws", + "title":"Regular Expression Functions", + "uri":"dws_mt_0139.html", + "doc_type":"tg", + "p_code":"380", + "code":"385" + }, + { + "desc":"This section describes the migration syntax of Oracle PL/SQL. The migration syntax determines how the keywords and features are migrated.PL/SQL combines the procedural fe", + "product_code":"dws", + "title":"PL/SQL", + "uri":"dws_mt_0141.html", + "doc_type":"tg", + "p_code":"358", + "code":"386" + }, + { + "desc":"This section descripes the migration syntax of Oracle PL/SQL Collections. The migration syntax decides how the keywords/features are migrated.A user-defined type (UDT) is", + "product_code":"dws", + "title":"PL/SQL Collections (Using User-Defined Types)", + "uri":"dws_mt_0155.html", + "doc_type":"tg", + "p_code":"358", + "code":"387" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"PL/SQL Packages", + "uri":"dws_mt_0156.html", + "doc_type":"tg", + "p_code":"358", + "code":"388" + }, + { + "desc":"Packages are schema objects that group logically related PL/SQL types, variables, functions and procedures. In Oracle, each package consists of two parts: package specifi", + "product_code":"dws", + "title":"Packages", + "uri":"dws_mt_0158.html", + "doc_type":"tg", + "p_code":"388", + "code":"389" + }, + { + "desc":"Package variables are available in Oracle packages that allow variables to retain all the functions and procedures in the package. DSC uses customized functions to help G", + "product_code":"dws", + "title":"Package Variables", + "uri":"dws_mt_0159.html", + "doc_type":"tg", + "p_code":"388", + "code":"390" + }, + { + "desc":"The package specification is migrated as a schema named after the package and the procedures and functions in the package body is migrated as Packagename.procedurenameand", + "product_code":"dws", + "title":"Splitting Packages", + "uri":"dws_mt_0301.html", + "doc_type":"tg", + "p_code":"388", + "code":"391" + }, + { + "desc":"REF Cursor is a data type that can store the database cursor values and is used to return query results. DSC supports migration of REF CURSOR. The example below shows how", + "product_code":"dws", + "title":"REF CURSOR", + "uri":"dws_mt_0302.html", + "doc_type":"tg", + "p_code":"388", + "code":"392" + }, + { + "desc":"The package declaration is migrated as a schema named after the package. The migration can be performed after pkgSchemaNaming is set to false.Input – Create schema for Pa", + "product_code":"dws", + "title":"Creating a Schema for Package", + "uri":"dws_mt_0221.html", + "doc_type":"tg", + "p_code":"388", + "code":"393" + }, + { + "desc":"REF CURSOR is defined as a return parameter.It can be migrated after plsqlCollectionis set tovarray.Input - VARRAYOutput", + "product_code":"dws", + "title":"VARRAY", + "uri":"dws_mt_0303.html", + "doc_type":"tg", + "p_code":"358", + "code":"394" + }, + { + "desc":"This feature is used to give privileges to users for specific packages. All the procedures and functions defined in the specific packages will be granted the execution pe", + "product_code":"dws", + "title":"Granting Execution Permissions", + "uri":"dws_mt_0304.html", + "doc_type":"tg", + "p_code":"358", + "code":"395" + }, + { + "desc":"Enable & DisableSet package_name_list to bas_lookup_misc_pkg.Enable and disable the function based on configuration parameters.InputOutput", + "product_code":"dws", + "title":"Package Name List", + "uri":"dws_mt_0305.html", + "doc_type":"tg", + "p_code":"358", + "code":"396" + }, + { + "desc":"SubtypeCustomized types in the package cannot be converted.SUBTYPE error_msg IS sad_products_t.exception_description%TYPE;SUBTYPE AR_FLAG IS SAD_RA_LINES_TI.AR_FLAG%TYPE;", + "product_code":"dws", + "title":"Data Type", + "uri":"dws_mt_0306.html", + "doc_type":"tg", + "p_code":"358", + "code":"397" + }, + { + "desc":"Input-Chinese (OutputInput-Chinese )OutputInput-Chinese,OutputInput-Support Chinese SPACEOutput", + "product_code":"dws", + "title":"Chinese Character Support", + "uri":"dws_mt_0222.html", + "doc_type":"tg", + "p_code":"358", + "code":"398" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Netezza Syntax Migration", + "uri":"dws_07_0682.html", + "doc_type":"tg", + "p_code":"194", + "code":"399" + }, + { + "desc":"DISTRIBUTE ON (column) should be migrated to DISTRIBUTE BY HASH (column).ORGANIZE ON will be commented out.The row-store supports BLOB and CLOB. Column storage does not s", + "product_code":"dws", + "title":"Tables", + "uri":"dws_07_6821.html", + "doc_type":"tg", + "p_code":"399", + "code":"400" + }, + { + "desc":"PROCEDURE with RETURNS will be modified to FUNCTION with RETURN.Migrate the nzplSQL language to the plpgSQL language or delete the language.The process which is started w", + "product_code":"dws", + "title":"PROCEDURE with RETURNS", + "uri":"dws_07_6822.html", + "doc_type":"tg", + "p_code":"399", + "code":"401" + }, + { + "desc":"NVARCHAR changed to NCHAR VARING.The row_count function is supported for affected row counting.ROW_COUNT identifies the number of rows associated with the previous SQL st", + "product_code":"dws", + "title":"Procedure", + "uri":"dws_07_6823.html", + "doc_type":"tg", + "p_code":"399", + "code":"402" + }, + { + "desc":"Second parameter is missing.Casting the data type.", + "product_code":"dws", + "title":"System Functions", + "uri":"dws_07_6824.html", + "doc_type":"tg", + "p_code":"399", + "code":"403" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dws", + "title":"Operator", + "uri":"dws_07_6825.html", + "doc_type":"tg", + "p_code":"399", + "code":"404" + }, + { + "desc":"A new configuration parameter \"keywords_addressed_using_doublequote\" should be introduced with the below value:keywords_addressed_using_doublequote=freezekeywords_address", + "product_code":"dws", + "title":"DML", + "uri":"dws_07_6826.html", + "doc_type":"tg", + "p_code":"399", + "code":"405" + }, + { + "desc":"This feature is applicable only for COLUMN store. For ROW store, Unique Index should not be commented.", + "product_code":"dws", + "title":"Unique Index", + "uri":"dws_07_6827.html", + "doc_type":"tg", + "p_code":"399", + "code":"406" }, { "desc":"This section covers the frequently asked questions.Q1: During installation, I get an error \"Root privileged users are not allowed to install the DSC for Linux.\" What is t", @@ -2553,16 +3660,25 @@ "uri":"dws_mt_0192.html", "doc_type":"tg", "p_code":"155", - "code":"284" + "code":"407" }, { - "desc":"Ensure that the operating system and the required software (refer toSystem Requirements for more details) are updated with the latest patches to prevent vulnerabilities a", + "desc":"This section contains a list of troubleshooting steps and solutions for issues encountered while using DSC.The table lists the troubleshooting symptoms/issues along with ", "product_code":"dws", - "title":"Security Management", - "uri":"dws_mt_0193.html", + "title":"Troubleshooting", + "uri":"dws_16_0210.html", "doc_type":"tg", "p_code":"155", - "code":"285" + "code":"408" + }, + { + "desc":"The following table lists the acronyms, abbreviations, terms, and their descriptions.", + "product_code":"dws", + "title":"Glossary", + "uri":"dws_16_0211.html", + "doc_type":"tg", + "p_code":"155", + "code":"409" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2571,7 +3687,7 @@ "uri":"dws_07_0100.html", "doc_type":"tg", "p_code":"", - "code":"286" + "code":"410" }, { "desc":"gs_dump is tool provided by GaussDB(DWS) to export database information. You can export a database or its objects, such as schemas, tables, and views. The database can be", @@ -2579,8 +3695,8 @@ "title":"gs_dump", "uri":"dws_07_0101.html", "doc_type":"tg", - "p_code":"286", - "code":"287" + "p_code":"410", + "code":"411" }, { "desc":"gs_dumpall is a tool provided by GaussDB(DWS) to export all database information, including the data of the default postgres database, data of user-specified databases, a", @@ -2588,8 +3704,8 @@ "title":"gs_dumpall", "uri":"dws_07_0102.html", "doc_type":"tg", - "p_code":"286", - "code":"288" + "p_code":"410", + "code":"412" }, { "desc":"gs_restore is a tool provided by GaussDB(DWS) to import data that was exported using gs_dump. It can also be used to import files that were exported using gs_dump.It has ", @@ -2597,8 +3713,8 @@ "title":"gs_restore", "uri":"dws_07_0103.html", "doc_type":"tg", - "p_code":"286", - "code":"289" + "p_code":"410", + "code":"413" }, { "desc":"gds_check is used to check the GDS deployment environment, including the OS parameters, network environment, and disk usage. It also supports the recovery of system param", @@ -2606,8 +3722,8 @@ "title":"gds_check", "uri":"dws_07_0104.html", "doc_type":"tg", - "p_code":"286", - "code":"290" + "p_code":"410", + "code":"414" }, { "desc":"gds_install is a script tool used to install GDS in batches, improving GDS deployment efficiency.Configure environment variables before executing the script. For details,", @@ -2615,8 +3731,8 @@ "title":"gds_install", "uri":"dws_07_0106.html", "doc_type":"tg", - "p_code":"286", - "code":"291" + "p_code":"410", + "code":"415" }, { "desc":"gds_uninstall is a script tool used to uninstall GDS in batches.Set environment variables before executing the script. For details, see \"Importing Data > Using a Foreign ", @@ -2624,8 +3740,8 @@ "title":"gds_uninstall", "uri":"dws_07_0107.html", "doc_type":"tg", - "p_code":"286", - "code":"292" + "p_code":"410", + "code":"416" }, { "desc":"gds_ctl is a script tool used for starting or stopping GDS service processes in batches. You can start or stop GDS service processes, which use the same port, on multiple", @@ -2633,8 +3749,8 @@ "title":"gds_ctl", "uri":"dws_07_0105.html", "doc_type":"tg", - "p_code":"286", - "code":"293" + "p_code":"410", + "code":"417" }, { "desc":"During cluster installation, you need to execute commands and transfer files among hosts in the cluster. Therefore, mutual trust relationships must be established among t", @@ -2642,8 +3758,8 @@ "title":"gs_sshexkey", "uri":"dws_07_0108.html", "doc_type":"tg", - "p_code":"286", - "code":"294" + "p_code":"410", + "code":"418" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2652,6 +3768,6 @@ "uri":"dws_07_0173.html", "doc_type":"tg", "p_code":"", - "code":"295" + "code":"419" } ] \ No newline at end of file diff --git a/docs/dws/tool/DWS_DS_145.html b/docs/dws/tool/DWS_DS_145.html index ddc8f4dd..41152b85 100644 --- a/docs/dws/tool/DWS_DS_145.html +++ b/docs/dws/tool/DWS_DS_145.html @@ -5,9 +5,9 @@
  • Data Studio does not open and displays a 'Java Runtime' error when I double-click the Data Studio.exe file.

    Solution:

    • Without JRE:

      Check whether the Java Runtime Environment (JRE) or Java Development Kit (JDK) version 1.8.0_141 or above with appropriate bit number is installed on the system and Java Home path is set. If there are more than one version of Java installed, set the -vm parameter in the configuration file by referring to Installing and Configuring Data Studio. This is a prerequisite for running Data Studio.

      -
    • Old JRE version:

      +
    • Old JRE version:

      Check the version of Java Runtime Environment (JRE) or Java Development Kit (JDK) that is installed on the system. An older version installed on the system causes this error. Update the JRE to version 1.8.0_141 or above with appropriate bit number.

      -
    • Java Incompatibility:

      +
    • Java Incompatibility:

      Check the version of the JRE or JDK installed in the system. If the installed Java version is incompatible with the system, this error occurs. Update the JRE to version 1.8.0_141 or above with appropriate bit number.

      You are advised to run the batch file to check compatibility and launch Data Studio. For details, see Quick Start.

      diff --git a/docs/dws/tool/DWS_DS_154.html b/docs/dws/tool/DWS_DS_154.html index 0c9955c5..adb2b1a7 100644 --- a/docs/dws/tool/DWS_DS_154.html +++ b/docs/dws/tool/DWS_DS_154.html @@ -40,7 +40,7 @@

      Server Configuration

      After a GaussDB(DWS) cluster is deployed, the SSL authentication mode is enabled by default. The server certificate, private key, and root certificate have been configured by default.

      SSL Certificate and Client Configuration

      You need to configure the client.

      -
      1. You can download an SSL certificate from GaussDB(DWS).

        Log in to the GaussDB(DWS) management console. In the navigation pane, choose Connections. In the Driver area, click download an SSL certificate.

        +
        1. You can download an SSL certificate from GaussDB(DWS).

          Log in to the GaussDB(DWS) management console. In the navigation pane, choose Connections. In the Driver area, click download an SSL certificate.

        2. Decompress the downloaded dws_ssl_cert.zip package to obtain the certificate file. Click the SSL tab on the Data Studio client and set the following parameters:

          diff --git a/docs/dws/tool/DWS_DS_16.html b/docs/dws/tool/DWS_DS_16.html index 7a9f95ca..99e0e469 100644 --- a/docs/dws/tool/DWS_DS_16.html +++ b/docs/dws/tool/DWS_DS_16.html @@ -2,7 +2,7 @@

          Installing and Configuring Data Studio

          This section describes the installation and configuration steps to use Data Studio. It also explains the steps to configure servers for debugging PL/SQL Functions.

          -

          Installation Preparations

          On the Connections page of the GaussDB(DWS) console, download the Data Studio GUI client.

          +

          Installation Preparations

          On the Connections page of the GaussDB(DWS) console, download the Data Studio GUI client.

          Installing Data Studio

          Data Studio can be run after decompression of the package.

          diff --git a/docs/dws/tool/dws_07_0002.html b/docs/dws/tool/dws_07_0002.html index fbfc11ad..76bb5e1e 100644 --- a/docs/dws/tool/dws_07_0002.html +++ b/docs/dws/tool/dws_07_0002.html @@ -1,8 +1,8 @@

          Downloading Related Tools

          -
          1. Log in to the GaussDB(DWS) management console.

            Log in to the GaussDB(DWS) management console at: https://console.otc.t-systems.com/dws/

            -

          2. In the navigation tree on the left, click Connections.
          3. In the Download Client and Driver area, select the tools corresponding to the cluster version based on the computer OS and download them.

            You can download the following tools:

            +
            1. Log in to the management console and search for GaussDB(DWS). The GaussDB(DWS) console page is displayed.

              Log in to the GaussDB(DWS) management console at: https://console.otc.t-systems.com/dws/

              +

            2. In the navigation tree on the left, choose Connections.
            3. In the Download Client and Driver area, select the tools corresponding to the cluster version based on the computer OS and download them.

              You can download the following tools:

              • gsql CLI client: The gsql tool package contains the gsql client tool, GDS (parallel data loading tool), gs_dump, gs_dumpall, and gs_restore tools.
              • Data Studio GUI client
              • DSC migration tool

              The gsql and Data Studio client tools have multiple historical versions. You can click Historical Version to download the tools based on the cluster version. GaussDB(DWS) clusters are compatible with earlier versions of gsql and Data Studio tools. You are advised to download the matching tool version based on the cluster version.

              Figure 1 Downloading the DSC client
              diff --git a/docs/dws/tool/dws_07_0101.html b/docs/dws/tool/dws_07_0101.html index 479403e2..fa6acc86 100644 --- a/docs/dws/tool/dws_07_0101.html +++ b/docs/dws/tool/dws_07_0101.html @@ -102,7 +102,7 @@
            4. -c, --clean

              Before writing the command of creating database objects into the backup file, write the command of clearing (deleting) database objects to the backup files. (If no objects exist in the target database, gs_restore probably displays some error information.)

              This parameter is used only for the plain-text format. For the archive format, you can specify the option when using gs_restore.

            5. -C, --create

              The backup file content starts with the commands of creating the database and connecting to the created database. (If the script is in this format, any database to be connected is allowed before running the script.)

              -

              This parameter is used only for the plain-text format. For the archive format, you can specify the option when using gs_restore.

              +

              This parameter is used only for the plain-text format. For the archive format, you can specify the option when using gs_restore.

            6. -E, --encoding=ENCODING

              Creates a dump file in the specified character set encoding. By default, the dump file is created in the database encoding. (Alternatively, you can set the environment variable PGCLIENTENCODING to the required dump encoding.)

            7. -n, --schema=SCHEMA

              Dumps only schemas matching the schema names. This option contains the schema and all its contained objects. If this option is not specified, all non-system schemas in the target database will be dumped. Multiple schemas can be selected by specifying multiple -n options. The schema parameter is interpreted as a pattern according to the same rules used by the \d command of gsql. Therefore, multiple schemas can also be selected by writing wildcard characters in the pattern. When you use wildcards, quote the pattern to prevent the shell from expanding the wildcards.

              • If -n is specified, gs_dump does not dump any other database objects that the selected schemas might depend upon. Therefore, there is no guarantee that the results of a specific-schema dump can be automatically restored to an empty database.
              • If -n is specified, the non-schema objects are not dumped.
              @@ -117,10 +117,10 @@

              Specifies -N exclude schema name to exclude multiple schemas while dumping.

              For example:

              gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -N sch1 -N sch2
              -

              In the preceding example, sch1 and sch2 will be excluded during the dumping.

              +

              In the preceding example, sch1 and sch2 will be excluded during the dumping.

            8. -o, --oids

              Dumps object identifiers (OIDs) as parts of the data in each table. Use this parameter if your application references the OID columns in some way (for example, in a foreign key constraint). If the preceding situation does not occur, do not use this parameter.

            9. -O, --no-owner

              Do not output commands to set ownership of objects to match the original database. By default, gs_dump issues the ALTER OWNER or SET SESSION AUTHORIZATION command to set ownership of created database objects. These statements will fail when the script is running unless it is started by a system administrator (or the same user that owns all of the objects in the script). To make a script that can be stored by any user and give the user ownership of all objects, specify -O.

              -

              This parameter is used only for the plain-text format. For the archive format, you can specify the option when using gs_restore.

              +

              This parameter is used only for the plain-text format. For the archive format, you can specify the option when using gs_restore.

            10. -s, --schema-only

              Dumps only the object definition (schema) but not data.

            11. -S, --sysadmin=NAME

              Specifies a reserved port for function expansion. This parameter is not recommended.

            12. -t, --table=TABLE

              Specifies a list of tables, views, sequences, or foreign tables to be dumped. You can use multiple -t parameters or wildcard characters to specify tables.

              @@ -140,7 +140,7 @@

              When -t and -T are input, the object will be stored in -t list not -T table object.

              For example:

              gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -T table1 -T table2
              -

              In the preceding example, table1 and table2 are excluded from the dumping.

              +

              In the preceding example, table1 and table2 are excluded from the dumping.

            13. --exclude-table-file=FILENAME

              Specifies the table file to be dumped.

              Same as --include-table-file, the content format of this parameter is as follows:

              schema1.table1

              @@ -158,7 +158,7 @@

              However, since this option generates an independent command for each row, an error in reloading a row causes only the loss of the row rather than the entire table content. The restoration may fail if you rearrange the column order. The --column-inserts option is unaffected against column order changes, though even slower.

            14. --no-security-labels

              Specifies a reserved port for function expansion. This parameter is not recommended.

            15. --no-tablespaces

              Does not issue commands to select tablespaces. All the objects will be created during the restoration process, no matter which tablespace is selected when using this option.

              -

              This parameter is used only for the plain-text format. For the archive format, you can specify the option when using gs_restore.

              +

              This parameter is used only for the plain-text format. For the archive format, you can specify the option when using gs_restore.

            16. --no-unlogged-table-data

              Specifies a reserved port for function expansion. This parameter is not recommended.

            17. --non-lock-table

              Specifies a reserved port for function expansion. This parameter is not recommended.

            18. --quote-all-identifiers

              Forcibly quotes all identifiers. This parameter is useful when you dump a database for migration to a later version, in which additional keywords may be introduced.

              @@ -172,14 +172,14 @@
            19. --include-nodes

              Includes the TO NODE or TO GROUP statement in the dumped CREATE TABLE or CREATE FOREIGN TABLE statement. This parameter is valid only for HDFS and foreign tables.

            20. --include-extensions

              Includes extensions in the dump.

            21. --include-depend-objs

              Includes information about the objects that depend on the specified object in the backup result. This parameter takes effect only if the -t or --include-table-file parameter is specified.

              -
            22. --exclude-self

              Excludes information about the specified object from the backup result. This parameter takes effect only if the -t or --include-table-file parameter is specified.

              +
            23. --exclude-self

              Excludes information about the specified object from the backup result. This parameter takes effect only if the -t or --include-table-file parameter is specified.

            24. --dont-overwrite-file

              The existing files in plain-text, .tar, and custom formats will be overwritten. This parameter is not used for the directory format.

              For example:

              Assume that the backup.sql file exists in the current directory. If you specify -f backup.sql in the input command, and the backup.sql file is generated in the current directory, the original file will be overwritten.

              If the backup file already exists and --dont-overwrite-file is specified, an error will be reported with the message that the dump file exists.

              gs_dump -p port_number postgres -f backup.sql -F plain --dont-overwrite-file
    -
    • The -s/--schema-only and -a/--data-only parameters do not coexist.
    • The -c/--clean and -a/--data-only parameters do not coexist.
    • --inserts/--column-inserts and -o/--oids do not coexist, because OIDS cannot be set using the INSERT statement.
    • --role must be used in conjunction with --rolepassword.
    • --binary-upgrade-usermap must be used in conjunction with --binary-upgrade.
    • --include-depend-objs/--exclude-self takes effect only when -t/--include-table-file is specified.
    • --exclude-self must be used with --include-depend-objs.
    +
    • The -s/--schema-only and -a/--data-only parameters do not coexist.
    • The -c/--clean and -a/--data-only parameters do not coexist.
    • --inserts/--column-inserts and -o/--oids do not coexist, because OIDS cannot be set using the INSERT statement.
    • --role must be used in conjunction with --rolepassword.
    • --binary-upgrade-usermap must be used in conjunction with --binary-upgrade.
    • --include-depend-objs/--exclude-self takes effect only when -t/--include-table-file is specified.
    • --exclude-self must be used with --include-depend-objs.

    Connection parameters:

    • -h, --host=HOSTNAME

      Specifies the host name. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket. The default is taken from the PGHOST environment variable (if available). Otherwise, a Unix domain socket connection is attempted.

      diff --git a/docs/dws/tool/dws_07_0128.html b/docs/dws/tool/dws_07_0128.html index e48a2b5a..f1daccab 100644 --- a/docs/dws/tool/dws_07_0128.html +++ b/docs/dws/tool/dws_07_0128.html @@ -10,6 +10,8 @@ gds_user Run the kill command to stop GDS. 128954 in the command is the GDS process ID.
      kill -9 128954
      • +
    • If GDS is started using the gds_ctl.py command, run the following commands to stop GDS:
      cd /opt/bin/dws/gds/bin
+python3 gds_ctl.py stop

    • diff --git a/docs/dws/tool/dws_07_0173.html b/docs/dws/tool/dws_07_0173.html index e39968bd..5cdb0723 100644 --- a/docs/dws/tool/dws_07_0173.html +++ b/docs/dws/tool/dws_07_0173.html @@ -8,17 +8,7 @@ -

    2023-05-04

    - -

    This issue is the third official release,adapts to DWS 8.2.0.100.

    - - -

    2022-08-11

    - -

    This issue is the first second release,adapts to DWS 8.1.1.202.

    - - -

    2022-08-11

    +

    2024-04-17

    This issue is the first official release.

    diff --git a/docs/dws/tool/dws_07_0666.html b/docs/dws/tool/dws_07_0666.html deleted file mode 100644 index 2c383fa1..00000000 --- a/docs/dws/tool/dws_07_0666.html +++ /dev/null @@ -1,155 +0,0 @@ - - -

    MySQL SQL Configuration

    -

    MySQL parameters are used to customize rules for MySQL script migration.

    -

    Open the features-mysql.properties file in the config folder and configure parameters in the features-mysql.properties file as required.

    - -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 1 Parameters in the features-mysql.properties file

    Parameter

    -

    Description

    -

    Value Range

    -

    Default Value

    -

    Example

    -
    • table.databaseAsSchema
    • table.defaultSchema
    -

    Whether to use a database name as the schema name. If a database name does not exist, the user-defined schema specified by table.schema will be used. If table.schema is not specified, the default schema will be used.

    -
    • true
    • false
    • public
    -
    • true
    • public
    -
    • table.databaseAsSchema=true
    • table.defaultSchema=public
    -
    • table.schema
    -

    Name of the user-defined schema. If this parameter is specified, it will be directly used. In this case, even if useDatabaseAsSchema is set to true, the name of the current schema will be used.

    -
    • schemaName
    -
    • null
    -
    • table.schema=
    -
    • table.orientation
    -

    Default data storage mode. Value ROW means row storage, and value COLUMN means column storage.

    -
    • ROW
    • COLUMN
    -
    • ROW
    -
    • table.orientation=ROW
    -
    • table.type
    -

    Default table type, which can be partitioned table (HASH) or replication table (REPLICATION)

    -
    • HASH
    • REPLICATION
    -
    • HASH
    -
    • table.type=HASH
    -
    • table.tablespace
    -

    Tablespace options

    -
    • COMMENT
    • RESERVE
    -
    • RESERVE
    -
    • table.tablespace=RESERVE
    -
    • table.partition-key.choose.strategy
    -

    Policy for selecting the partition key

    -
    • partitionKeyChooserStrategy
    -
    • partitionKeyChooserStrategy
    -
    • table.partition-key.choose.strategy=partitionKeyChooserStrategy
    -
    • table.partition-key.name
    -

    Partition key. If this parameter is not specified, the default selection policy will be used. If there are multiple columns, separate them with commas (,). The column names are case insensitive.

    -
    • Reserved parameter
    -
    • null
    -
    • table.partition-key.name=
    -
    • table.compress.mode
    -

    Compression mode. If keyword COMPRESS is specified in CREATE TABLE, the compression feature will be triggered in the case of bulk INSERT operations. If this feature is enabled, a scan will be performed on all tuple data within the page to generate a dictionary and then the tuple data will be compressed and stored. If NOCOMPRESS is used, tables will not be compressed.

    -
    • COMPRESS
    • NOCOMPRESS
    -
    • NOCOMPRESS
    -
    • table.compress.mode=NOCOMPRESS
    -
    • table.compress.row

      -
    • table.compress.column
    -

    Compression level of table data. It determines the compression ratio and duration. Generally, the higher the level of compression, the higher the ratio, the longer the duration, vice versa. The actual compression ratio depends on the distribution mode of table data loaded. Valid values for row-store tables are YES and NO, and the default is NO. Valid values for column-store tables are YES, NO, LOW, MIDDLE, and HIGH, and the default is LOW.

    -
    • YES
    • NO

      -
    • YES
    • NO
    • LOW
    • MIDDLE
    • HIGH
    -
    • NO

      -

      -
    • LOW
    -
    • table.compress.row=NO

      -

      -
    • table.compress.column=LOW
    -
    • table.compress.level
    -

    Table data compression ratio and duration at the same compression level. This divides a compression level into sublevels, providing more choices for the compression ratio and duration. As the value becomes larger, the compression ratio becomes higher and duration longer at the same compression level.

    -
    • 0
    • 1
    • 2
    • 3
    -
    • 0
    -
    • table.compress.level=0
    -
    • table.database.template
    -

    Database template

    -
    • Reserved parameter
    -
    • template0
    -

    table.database.template=template0

    -
    -
    -
    -
    -
    -
    Parent topic: Configuring DSC
    -
    -
    - diff --git a/docs/dws/tool/dws_07_0675.html b/docs/dws/tool/dws_07_0675.html deleted file mode 100644 index b3c01fec..00000000 --- a/docs/dws/tool/dws_07_0675.html +++ /dev/null @@ -1,46 +0,0 @@ - - -

    Netezza SQL Migration

    -

    DSC supports the migration from Netezza to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.

    -

    Run the following commands to set the source database, input and output folder paths, log paths, application language, and conversion type:

    -

    Linux:

    -
    ./runDSC.sh 
---source-db Netezza 
-[--input-folder <input-script-path>] 
-[--output-folder <output-script-path>]
-[--log-folder <log-path>]
-[--application-lang SQL]
-[--conversion-type <conversion-type>]
    -

    Windows:

    -
    runDSC.bat
---source-db Netezza 
-[--input-folder <input-script-path>] 
-[--output-folder <output-script-path>]
-[--log-folder <log-path>]
-[--application-lang SQL]
-[--conversion-type <conversion-type>]
    -

    For example:

    -

    Linux:

    -
    ./runDSC.sh --source-db Netezza --input-folder /opt/DSC/DSC/input/mysql/ --output-folder /opt/DSC/DSC/output/ --application-lang SQL --conversion-type BULK --log-folder/opt/DSC/DSC/log/
    -

    Windows:

    -
    runDSC.bat --source-db Netezza--target-db GaussDBA --input-folder D:\test\conversion\input --output-folder D:\test\conversion\output --log-folder D:\test\conversion\log --application-lang SQL --conversion-type Bulk
    -

    During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console. Execution information and errors are written into log files.

    -
    ********************** Schema Conversion Started *************************  
-DSC process start time : Mon Jan 20 17:24:49 IST 2020  
-Statement count progress 100% completed [FILE(1/1)]    
-Schema Conversion Progress 100% completed  
-**************************************************************************   
-Total number of files in input folder : 1  
-**************************************************************************   
-Log file path :....../DSC/DSC/log/dsc.log 
-DSC process end time : Mon Jan 20 17:24:49 IST 2020  
-DSC total process time : 0 seconds  
-********************* Schema Conversion Completed ************************
    -

    For details about how to migrate Netezza SQL using DSC, see Migrating Data Using DSC.

    -
    -
    -
    -
    Parent topic: Using DSC
    -
    -
    - diff --git a/docs/dws/tool/dws_07_0676.html b/docs/dws/tool/dws_07_0676.html deleted file mode 100644 index b2e45152..00000000 --- a/docs/dws/tool/dws_07_0676.html +++ /dev/null @@ -1,73 +0,0 @@ - - -

    MySQL SQL Migration

    -

    DSC supports the migration from MySQL to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.

    -

    Performing MySQL Migration on Linux

    Run the following command on Linux to start the migration. You need to specify the source database, input and output folder paths, and log paths. The application language can be SQL or Perl. The default language is SQL. The migration type can be Bulk or BLogic.

    -
    ./runDSC.sh
---source-db MySQL 
-[--input-folder <input-script-path>] 
-[--output-folder <output-script-path>]
-[--application-lang SQL] 
-[--conversion-type <conversion-type>] 
-[--log-folder <log-path>]
    -

    During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console.

    -
    ********************** Schema Conversion Started *************************  
-DSC process start time : Mon Jan 20 17:24:49 IST 2020  
-Statement count progress 100% completed [FILE(1/1)]    
-Schema Conversion Progress 100% completed  
-**************************************************************************   
-Total number of files in input folder : 1  
-Total number of valid files in input folder : 1  
-**************************************************************************   
-Log file path :....../DSC/DSC/log/dsc.log  
-Error Log file :    
-DSC process end time : Mon Jan 20 17:24:49 IST 2020  
-DSC total process time : 0 seconds 
-********************* Schema Conversion Completed ************************
    -
    -

    Performing MySQL Migration on Windows

    Run the following command on Windows to start the migration. You need to specify the source database, input and output folder paths, and log paths. The application language can be SQL or Perl. The default language is SQL. The migration type can be Bulk or BLogic.

    -
    runDSC.bat
---source-db MySQL 
-[--input-folder <input-script-path>] 
-[--output-folder <output-script-path>]
-[--application-lang SQL] 
-[--conversion-type <conversion-type>] 
-[--log-folder <log-path>]
    -

    During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console.

    -
    ********************** Schema Conversion Started *************************  
-DSC process start time : Mon Jan 20 17:24:49 IST 2020  
-Statement count progress 100% completed [FILE(1/1)]    
-Schema Conversion Progress 100% completed  
-**************************************************************************   
-Total number of files in input folder : 1  
-**************************************************************************   
-Log file path :....../DSC/DSC/log/dsc.log  
-DSC process end time : Mon Jan 20 17:24:49 IST 2020  
-DSC total process time : 0 seconds  
-********************* Schema Conversion Completed ************************
    -
    • Run the following commands to migrate objects, such as functions, store procedures, and packages that contain PL/SQL statements:

      Linux:

      -
      ./runDSC.sh --source-db MySQL --input-folder /opt/DSC/DSC/input/mysql/ --output-folder /opt/DSC/DSC/output/ --application-lang SQL --conversion-type BULK --log-folder /opt/DSC/DSC/log/
      -

      Windows:

      -
      runDSC.bat --source-db MySQL--target-db GaussDBA --input-folder D:\test\conversion\input --output-folder D:\test\conversion\output --log-folder D:\test\conversion\log --application-lang SQL --conversion-type Bulk
      -

      During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console. Execution information and errors are written into log files.

      -
      ********************** Schema Conversion Started *************************
-DSC process start time : Mon Jan 20 17:24:49 IST 2020
-Statement count progress 100% completed [FILE(1/1)]
-
-Schema Conversion Progress 100% completed
-************************************************************************** 
-Total number of files in input folder : 1
-************************************************************************** 
-Log file path :....../DSC/DSC/log/dsc.log
-DSC process end time : Mon Jan 20 17:24:49 IST 2020
-DSC total process time : 0 seconds
-********************* Schema Conversion Completed ************************
      -
    -
    -
    -
    -
    -
    Parent topic: Using DSC
    -
    -
    - diff --git a/docs/dws/tool/dws_07_0682.html b/docs/dws/tool/dws_07_0682.html index 96588a8c..d47e3522 100644 --- a/docs/dws/tool/dws_07_0682.html +++ b/docs/dws/tool/dws_07_0682.html @@ -1,8 +1,8 @@ - +

    Netezza Syntax Migration

    - diff --git a/docs/dws/tool/dws_07_0684.html b/docs/dws/tool/dws_07_0684.html deleted file mode 100644 index 49dd00e3..00000000 --- a/docs/dws/tool/dws_07_0684.html +++ /dev/null @@ -1,25 +0,0 @@ - - -

    DB2 Syntax Migration

    -
    -
    - - -
    -
    Parent topic: DSC
    -
    -
    - diff --git a/docs/dws/tool/dws_07_0759.html b/docs/dws/tool/dws_07_0759.html index ddeebd22..a2dd5a4f 100644 --- a/docs/dws/tool/dws_07_0759.html +++ b/docs/dws/tool/dws_07_0759.html @@ -4,15 +4,15 @@

    Scenario

    GaussDB(DWS) uses GDS to allocate the source data for parallel data import. Deploy GDS on the data server.

    If a large volume of data is stored on multiple data servers, install, configure, and start GDS on each server. Then, data on all the servers can be imported in parallel. The procedure for installing, configuring, and starting GDS is the same on each data server. This section describes how to perform this procedure on one data server.

    -

    Context

    1. The GDS version must match the cluster version. For example, GDS V100R008C00 matches DWS 1.3.X. Otherwise, the import or export may fail, or the import or export process may fail to respond.

      Therefore, use the latest version of GDS. After the database is upgraded, download the latest version of GaussDB(DWS) GDS as instructed in Procedure. When the import or export starts, GaussDB(DWS) checks the GDS versions. If the versions do not match, an error message is displayed and the import or export is terminated.

      -

      To obtain the version number of GDS, run the following command in the GDS decompression directory:

      -
      gds -V
      -

      To view the database version, run the following SQL statement after connecting to the database:

      -
      1
      SELECT version();
+
      Context
      The GDS version must match the cluster version. For example, GDS V100R008C00 matches DWS 1.3.X. Otherwise, the import or export may fail, or the import or export process may fail to respond. Therefore, use the latest version of GDS.
      
+
      After the database is upgraded, download the latest version of GaussDB(DWS) GDS as instructed in Procedure. When the import or export starts, GaussDB(DWS) checks the GDS versions. If the versions do not match, an error message is displayed and the import or export is terminated.
      
+
      To obtain the version number of GDS, run the following command in the GDS decompression directory:
      
+
      gds -V
      
+
      To view the database version, run the following SQL statement after connecting to the database:
      
+
      1
      SELECT version();
 
      
 
 
      
-
 
      
 
      Procedure
      1. Before using GDS to import or export data, see Preparing an ECS as the GDS Server and Downloading the GDS Package in "Tutorial: Using GDS to Import Data from a Remote Server" in Data Warehouse Service (DWS) User Guide.
      2. Log in as user root to the data server where GDS is to be installed and run the following command to create the directory for storing the GDS package:
        mkdir -p /opt/bin/dws
        
 
      3. Upload the GDS package to the created directory.
        Use the SUSE Linux package as an example. Upload the GDS package dws_client_8.x.x_suse_x64.zip to the directory created in the previous step.
        
diff --git a/docs/dws/tool/dws_07_6814.html b/docs/dws/tool/dws_07_6814.html
index 311a89fb..990184b9 100644
--- a/docs/dws/tool/dws_07_6814.html
+++ b/docs/dws/tool/dws_07_6814.html
@@ -1,39 +1,74 @@
-
+
 
 
        COMPRESS Phrase
        
-
        Input – COMPRESS Phrase
        
-
        CREATE TABLE test_tab (
-  id            NUMBER(10)    NOT NULL,
-  description   VARCHAR2(100) NOT NULL,
-  created_date  DATE          NOT NULL,
-  created_by    VARCHAR2(50)  NOT NULL,
-  updated_date  DATE,
-  updated_by    VARCHAR2(50)
-)
-NOCOMPRESS
-PARTITION BY RANGE (created_date) (
-  PARTITION test_tab_q1 VALUES LESS THAN (TO_DATE('01/04/2003', 'DD/MM/YYYY')) COMPRESS,
-  PARTITION test_tab_q2 VALUES LESS THAN (MAXVALUE)
-);
        
-
        Output
        
-
        CREATE
-     TABLE
-          test_tab (
-               id NUMBER (10) NOT NULL
-               ,description VARCHAR2 (100) NOT NULL
-               ,created_date DATE NOT NULL
-               ,created_by VARCHAR2 (50) NOT NULL
-               ,updated_date DATE
-               ,updated_by VARCHAR2 (50)
-          ) /*NOCOMPRESS*/
-          PARTITION BY RANGE (created_date) (
-               PARTITION test_tab_q1
-               VALUES LESS THAN (
-                    TO_DATE( '01/04/2003' ,'DD/MM/YYYY' )
-               ) /*COMPRESS*/
-               ,PARTITION test_tab_q2
-               VALUES LESS THAN (MAXVALUE)
-) ;
        
+
        Input – COMPRESS Phrase
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
        CREATE TABLE test_tab (
+  id            NUMBER(10)    NOT NULL,
+  description   VARCHAR2(100) NOT NULL,
+  created_date  DATE          NOT NULL,
+  created_by    VARCHAR2(50)  NOT NULL,
+  updated_date  DATE,
+  updated_by    VARCHAR2(50)
+)
+NOCOMPRESS
+PARTITION BY RANGE (created_date) (
+  PARTITION test_tab_q1 VALUES LESS THAN (TO_DATE('01/04/2003', 'DD/MM/YYYY')) COMPRESS,
+  PARTITION test_tab_q2 VALUES LESS THAN (MAXVALUE)
+);
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
        CREATE
+     TABLE
+          test_tab (
+               id NUMBER (10) NOT NULL
+               ,description VARCHAR2 (100) NOT NULL
+               ,created_date DATE NOT NULL
+               ,created_by VARCHAR2 (50) NOT NULL
+               ,updated_date DATE
+               ,updated_by VARCHAR2 (50)
+          ) /*NOCOMPRESS*/
+          PARTITION BY RANGE (created_date) (
+               PARTITION test_tab_q1
+               VALUES LESS THAN (
+                    TO_DATE( '01/04/2003' ,'DD/MM/YYYY' )
+               ) /*COMPRESS*/
+               ,PARTITION test_tab_q2
+               VALUES LESS THAN (MAXVALUE)
+) ;
+
        
+
+
        
 
        
 
        
 
        
diff --git a/docs/dws/tool/dws_07_6815.html b/docs/dws/tool/dws_07_6815.html
index ad966d75..1a3c84f5 100644
--- a/docs/dws/tool/dws_07_6815.html
+++ b/docs/dws/tool/dws_07_6815.html
@@ -1,9 +1,9 @@
-
+
 
 
        Bitmap Index
        
-
        There is a configuration parameter that is introduced for this feature named BitmapIndexSupport which default value is comment, then the sample input and output are as follows:
        
-
        Input – Bitmap index
        
-
        1
+
        There is a configuration parameter that is introduced for this feature named BitmapIndexSupport which default value is comment, then the sample input and output are as follows:
        
+
        Input – Bitmap index
        
+
        1
 2
 3
        CREATE BITMAP INDEX 
 emp_bitmap_idx
@@ -11,14 +11,14 @@
 
        
 
 
        
-
        Output
        
-
        1
        /*CREATE BITMAP INDEX emp_bitmap_idx ON index_demo (gender);*/
+
        Output
        
+
        1
        /*CREATE BITMAP INDEX emp_bitmap_idx ON index_demo (gender);*/
 
        
 
 
        
-
        However, if the configuration parameter is set to BTREE, then the output is as follows:
        
-
        Output
        
-
        1
+
        However, if the configuration parameter is set to BTREE, then the output is as follows:
        
+
        Output
        
+
        1
 2
 3
 4
diff --git a/docs/dws/tool/dws_07_6816.html b/docs/dws/tool/dws_07_6816.html
index 7e459ad4..b69be350 100644
--- a/docs/dws/tool/dws_07_6816.html
+++ b/docs/dws/tool/dws_07_6816.html
@@ -1,8 +1,8 @@
-
+
 
 
        Custom Tablespace
        
-
        Input – custom tablespace
        
-
         1
+
        Input – custom tablespace
        
+
         1
  2
  3
  4
@@ -50,8 +50,8 @@
 
        
 
 
        
-
        Output
        
-
         1
+
        Output
        
+
         1
  2
  3
  4
diff --git a/docs/dws/tool/dws_07_6817.html b/docs/dws/tool/dws_07_6817.html
index d3174e76..f94c7a29 100644
--- a/docs/dws/tool/dws_07_6817.html
+++ b/docs/dws/tool/dws_07_6817.html
@@ -1,9 +1,9 @@
-
+
 
 
        Supplemental Log Data
        
-
        Supplemental columns can be recorded in redo log files. The process of recording these additional columns is called supplemental logging. The Oracle database supports this function, but GaussDB does not.
        
-
        Input
        
-
         1
+
        Supplemental columns can be recorded in redo log files. The process of recording these additional columns is called supplemental logging. Oracle supports this function, but GaussDB(DWS) does not.
        
+
        Input
        
+
         1
  2
  3
  4
@@ -47,8 +47,8 @@
 
        
 
 
        
-
        Output
        
-
         1
+
        Output
        
+
         1
  2
  3
  4
@@ -92,34 +92,61 @@
 
        
 
 
        
-
         
        The SUPPLEMENTAL LOG DATA functions that are not supported by GaussDB need to be commented out.
        
+
         
        The SUPPLEMENTAL LOG DATA functions that are not supported by GaussDB need to be commented out.
        
 
        
-
        SUPPLEMENTAL LOG DATA is not supported by CREATE TABLE and needs to be commented out.
        
-
        Input
        
-
         CREATE TABLE SAD.FND_DATA_CHANGE_LOGS_T
-   (    LOGID NUMBER,
-        TABLE_NAME VARCHAR2(40) NOT NULL ENABLE,
-        TABLE_KEY_COLUMNS VARCHAR2(200),
-        TABLE_KEY_VALUES VARCHAR2(200),
-        COLUMN_NAME VARCHAR2(40) NOT NULL ENABLE,
-        COLUMN_CHANGE_FROM_VALUE VARCHAR2(200),
-        COLUMN_CHANGE_TO_VALUE VARCHAR2(200),
-        DESCRIPTION VARCHAR2(500),
-         SUPPLEMENTAL LOG DATA (ALL) COLUMNS
-   );
        
-
        Output
        
-
        CREATE TABLE sad.fnd_data_change_logs_t 
-  ( 
-     logid                    NUMBER 
-     ,table_name               VARCHAR2 (40) NOT NULL /* ENABLE */ 
-     ,table_key_columns        VARCHAR2 (200)
-     ,table_key_values         VARCHAR2 (200) 
-     ,column_name              VARCHAR2 (40) NOT NULL /* ENABLE */ 
-     ,column_change_from_value VARCHAR2 (200)
-     ,column_change_to_value   VARCHAR2 (200) 
-     ,description              VARCHAR2 (500) 
-     /*, SUPPLEMENTAL LOG DATA (ALL) COLUMNS*/ 
-  )
        
+
        SUPPLEMENTAL LOG DATA is not supported by CREATE TABLE and needs to be commented out.
        
+
        Input
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
         CREATE TABLE SAD.FND_DATA_CHANGE_LOGS_T
+   (    LOGID NUMBER,
+        TABLE_NAME VARCHAR2(40) NOT NULL ENABLE,
+        TABLE_KEY_COLUMNS VARCHAR2(200),
+        TABLE_KEY_VALUES VARCHAR2(200),
+        COLUMN_NAME VARCHAR2(40) NOT NULL ENABLE,
+        COLUMN_CHANGE_FROM_VALUE VARCHAR2(200),
+        COLUMN_CHANGE_TO_VALUE VARCHAR2(200),
+        DESCRIPTION VARCHAR2(500),
+         SUPPLEMENTAL LOG DATA (ALL) COLUMNS
+   );
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        CREATE TABLE sad.fnd_data_change_logs_t 
+  ( 
+     logid                    NUMBER 
+     ,table_name               VARCHAR2 (40) NOT NULL /* ENABLE */ 
+     ,table_key_columns        VARCHAR2 (200)
+     ,table_key_values         VARCHAR2 (200) 
+     ,column_name              VARCHAR2 (40) NOT NULL /* ENABLE */ 
+     ,column_change_from_value VARCHAR2 (200)
+     ,column_change_to_value   VARCHAR2 (200) 
+     ,description              VARCHAR2 (500) 
+     /*, SUPPLEMENTAL LOG DATA (ALL) COLUMNS*/ 
+  )
+
        
+
+
        
 
        
 
        
 
        
diff --git a/docs/dws/tool/dws_07_6818.html b/docs/dws/tool/dws_07_6818.html
index 1f9a9087..6a8127a7 100644
--- a/docs/dws/tool/dws_07_6818.html
+++ b/docs/dws/tool/dws_07_6818.html
@@ -1,9 +1,9 @@
-
+
 
 
        LONG RAW
        
-
        "Data type LONG RAW" is not supported in the CREATE TABLE statement. LONG RAW data type needs to be replaced with Byte.
        
-
        Input
        
-
         1
+
        "Data type LONG RAW" is not supported in the CREATE TABLE statement. LONG RAW data type needs to be replaced with Byte.
        
+
        Input
        
+
         1
  2
  3
  4
@@ -33,8 +33,8 @@
 
        
 
 
        
-
        Output
        
-
         1
+
        Output
        
+
         1
  2
  3
  4
diff --git a/docs/dws/tool/dws_07_6819.html b/docs/dws/tool/dws_07_6819.html
index 30d180aa..05e4069b 100644
--- a/docs/dws/tool/dws_07_6819.html
+++ b/docs/dws/tool/dws_07_6819.html
@@ -1,47 +1,89 @@
-
+
 
 
        SYS_GUID
        
-
        SYS_GUID is a built-in function which returns the Global Unique Identifier (GUID) for a row in a table. It accepts no arguments and returns a RAW value of 16 bytes.
        
-
        Input
        
-
        CREATE TABLE sad.fnd_data_change_logs_t
-  (
-    logid                    NUMBER,
-    table_name               VARCHAR2 (40) NOT NULL /* ENABLE */
-    ,table_key_columns        VARCHAR2 (200),
- table_key_values         VARCHAR2 (200),
- column_name              VARCHAR2 (40) NOT NULL /* ENABLE */
- ,column_change_from_value VARCHAR2 (200),
- column_change_to_value   VARCHAR2 (200),
- organization_id          NUMBER,
- created_by               NUMBER (15, 0) NOT NULL /* ENABLE */
- ,creation_date            DATE NOT NULL /* ENABLE */
- ,last_updated_by          NUMBER (15, 0) NOT NULL /* ENABLE */
- ,last_update_date         DATE NOT NULL /* ENABLE */
- ,last_update_login        NUMBER (15, 0) DEFAULT 0 NOT NULL /* ENABLE */
- ,description              VARCHAR2 (500),
- sys_id                   VARCHAR2 (32) DEFAULT Sys_guid( )
- /*, SUPPLEMENTAL LOG DATA (ALL) COLUMNS*/
-  ); 
        
-
        Output
        
-
        CREATE TABLE sad.fnd_data_change_logs_t
-  (
-    logid                    NUMBER,
-    table_name               VARCHAR2 (40) NOT NULL /* ENABLE */
-    ,table_key_columns        VARCHAR2 (200),
- table_key_values         VARCHAR2 (200),
- column_name              VARCHAR2 (40) NOT NULL /* ENABLE */
- ,column_change_from_value VARCHAR2 (200),
- column_change_to_value   VARCHAR2 (200),
- organization_id          NUMBER,
- created_by               NUMBER (15, 0) NOT NULL /* ENABLE */
- ,creation_date            DATE NOT NULL /* ENABLE */
- ,last_updated_by          NUMBER (15, 0) NOT NULL /* ENABLE */
- ,last_update_date         DATE NOT NULL /* ENABLE */
- ,last_update_login        NUMBER (15, 0) DEFAULT 0 NOT NULL /* ENABLE */
- ,description              VARCHAR2 (500),
- sys_id                   VARCHAR2 (32) DEFAULT MIG_ORA_EXT.Sys_guid( )
- /*, SUPPLEMENTAL LOG DATA (ALL) COLUMNS*/
-  ); 
        
+
        SYS_GUID is a built-in function which returns the Global Unique Identifier (GUID) for a row in a table. It accepts no arguments and returns a RAW value of 16 bytes.
        
+
        Input
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
        CREATE TABLE sad.fnd_data_change_logs_t
+  (
+    logid                    NUMBER,
+    table_name               VARCHAR2 (40) NOT NULL /* ENABLE */
+    ,table_key_columns        VARCHAR2 (200),
+ table_key_values         VARCHAR2 (200),
+ column_name              VARCHAR2 (40) NOT NULL /* ENABLE */
+ ,column_change_from_value VARCHAR2 (200),
+ column_change_to_value   VARCHAR2 (200),
+ organization_id          NUMBER,
+ created_by               NUMBER (15, 0) NOT NULL /* ENABLE */
+ ,creation_date            DATE NOT NULL /* ENABLE */
+ ,last_updated_by          NUMBER (15, 0) NOT NULL /* ENABLE */
+ ,last_update_date         DATE NOT NULL /* ENABLE */
+ ,last_update_login        NUMBER (15, 0) DEFAULT 0 NOT NULL /* ENABLE */
+ ,description              VARCHAR2 (500),
+ sys_id                   VARCHAR2 (32) DEFAULT Sys_guid( )
+ /*, SUPPLEMENTAL LOG DATA (ALL) COLUMNS*/
+  ); 
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
        CREATE TABLE sad.fnd_data_change_logs_t
+  (
+    logid                    NUMBER,
+    table_name               VARCHAR2 (40) NOT NULL /* ENABLE */
+    ,table_key_columns        VARCHAR2 (200),
+ table_key_values         VARCHAR2 (200),
+ column_name              VARCHAR2 (40) NOT NULL /* ENABLE */
+ ,column_change_from_value VARCHAR2 (200),
+ column_change_to_value   VARCHAR2 (200),
+ organization_id          NUMBER,
+ created_by               NUMBER (15, 0) NOT NULL /* ENABLE */
+ ,creation_date            DATE NOT NULL /* ENABLE */
+ ,last_updated_by          NUMBER (15, 0) NOT NULL /* ENABLE */
+ ,last_update_date         DATE NOT NULL /* ENABLE */
+ ,last_update_login        NUMBER (15, 0) DEFAULT 0 NOT NULL /* ENABLE */
+ ,description              VARCHAR2 (500),
+ sys_id                   VARCHAR2 (32) DEFAULT MIG_ORA_EXT.Sys_guid( )
+ /*, SUPPLEMENTAL LOG DATA (ALL) COLUMNS*/
+  ); 
+
        
+
+
        
 
        
 
        
 
        
diff --git a/docs/dws/tool/dws_07_6821.html b/docs/dws/tool/dws_07_6821.html
index 91c5e9c8..c3ed5638 100644
--- a/docs/dws/tool/dws_07_6821.html
+++ b/docs/dws/tool/dws_07_6821.html
@@ -1,113 +1,193 @@
-
+
 
 
        Tables
        
-
        Distribution Key
        DISTRIBUTE ON (column) should be migrated to DISTRIBUTE BY HASH (column).
        
+
        Distribution Key
        DISTRIBUTE ON (column) should be migrated to DISTRIBUTE BY HASH (column).
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE TABLE  N_AG_AMT_H
-(
-     AG_NO                national character varying(50)    not null,
-     AG_CATEG_CD      national character varying(12)    not null,
-     AMT_TYPE_CD      national character varying(12)    not null,
-     DATA_START_DT   date                                      not null,
-     CCY_CD               national character varying(3)     not null,
-     DATA_END_DT      date
-)
-DISTRIBUTE ON (AG_NO, AG_CATEG_CD, AMT_TYPE_CD)
-ORGANIZE   ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT)
-;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        CREATE TABLE  N_AG_AMT_H
+(
+     AG_NO                national character varying(50)    not null,
+     AG_CATEG_CD      national character varying(12)    not null,
+     AMT_TYPE_CD      national character varying(12)    not null,
+     DATA_START_DT   date                                      not null,
+     CCY_CD               national character varying(3)     not null,
+     DATA_END_DT      date
+)
+DISTRIBUTE ON (AG_NO, AG_CATEG_CD, AMT_TYPE_CD)
+ORGANIZE   ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT)
+;
+
        
+
+
        
 
        CREATE TABLE  N_AG_AMT_H
-(
-     AG_NO                national character varying(50)    not null,
-     AG_CATEG_CD      national character varying(12)    not null,
-     AMT_TYPE_CD      national character varying(12)    not null,
-     DATA_START_DT   date                                      not null,
-     CCY_CD               national character varying(3)     not null,
-     DATA_END_DT      date
-) WITH(ORIENTATION=COLUMN)
-DISTRIBUTE BY HASH (AG_NO, AG_CATEG_CD, AMT_TYPE_CD)
-/* ORGANIZE   ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT) */
-;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        CREATE TABLE  N_AG_AMT_H
+(
+     AG_NO                national character varying(50)    not null,
+     AG_CATEG_CD      national character varying(12)    not null,
+     AMT_TYPE_CD      national character varying(12)    not null,
+     DATA_START_DT   date                                      not null,
+     CCY_CD               national character varying(3)     not null,
+     DATA_END_DT      date
+) WITH(ORIENTATION=COLUMN)
+DISTRIBUTE BY HASH (AG_NO, AG_CATEG_CD, AMT_TYPE_CD)
+/* ORGANIZE   ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT) */
+;
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
-
        ORGANIZE ON
        ORGANIZE ON will be commented out.
        
+
        ORGANIZE ON
        ORGANIZE ON will be commented out.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE TABLE  N_AG_AMT_H 
-( 
-     AG_NO               national character varying(50) not null, 
-     AG_CATEG_CD     national character varying(12) not null, 
-     AMT_TYPE_CD     national character varying(12) not null, 
-     DATA_START_DT  date                                      not null, 
-     CCY_CD              national character varying(3)     not null, 
-     DATA_END_DT     date 
-) 
-DISTRIBUTE ON (AG_NO, AG_CATEG_CD, AMT_TYPE_CD) 
-ORGANIZE ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT) 
-;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        CREATE TABLE  N_AG_AMT_H 
+( 
+     AG_NO               national character varying(50) not null, 
+     AG_CATEG_CD     national character varying(12) not null, 
+     AMT_TYPE_CD     national character varying(12) not null, 
+     DATA_START_DT  date                                      not null, 
+     CCY_CD              national character varying(3)     not null, 
+     DATA_END_DT     date 
+) 
+DISTRIBUTE ON (AG_NO, AG_CATEG_CD, AMT_TYPE_CD) 
+ORGANIZE ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT) 
+;
+
        
+
+
        
 
        CREATE TABLE  N_AG_AMT_H 
-( 
-     AG_NO                national character varying(50) not null, 
-     AG_CATEG_CD      national character varying(12) not null, 
-     AMT_TYPE_CD      national character varying(12) not null, 
-     DATA_START_DT date                                      not null, 
-     CCY_CD               national character varying(3)     not null, 
-   DATA_END_DT      date 
-) WITH(ORIENTATION=COLUMN) 
-DISTRIBUTE BY HASH (AG_NO, AG_CATEG_CD, AMT_TYPE_CD) 
-/* ORGANIZE ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT)*/
-;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        CREATE TABLE  N_AG_AMT_H 
+( 
+     AG_NO                national character varying(50) not null, 
+     AG_CATEG_CD      national character varying(12) not null, 
+     AMT_TYPE_CD      national character varying(12) not null, 
+     DATA_START_DT date                                      not null, 
+     CCY_CD               national character varying(3)     not null, 
+   DATA_END_DT      date 
+) WITH(ORIENTATION=COLUMN) 
+DISTRIBUTE BY HASH (AG_NO, AG_CATEG_CD, AMT_TYPE_CD) 
+/* ORGANIZE ON (AG_CATEG_CD, AMT_TYPE_CD, DATA_END_DT)*/
+;
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
-
        Large Field Type
        The row-store supports BLOB and CLOB. Column storage does not support BLOB, but it supports CLOB.
        
+
        Large Field Type
        The row-store supports BLOB and CLOB. Column storage does not support BLOB, but it supports CLOB.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
diff --git a/docs/dws/tool/dws_07_6822.html b/docs/dws/tool/dws_07_6822.html
index 5c31d584..7c756a4a 100644
--- a/docs/dws/tool/dws_07_6822.html
+++ b/docs/dws/tool/dws_07_6822.html
@@ -1,291 +1,539 @@
-
+
        PROCEDURE with RETURNS
        
-
        PROCEDURE with RETURNS will be modified to FUNCTION with RETURN.
        
+
        PROCEDURE with RETURNS will be modified to FUNCTION with RETURN.
        
 
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE TABLE  prod 
- ( 
-      prod_no              number(6)      not null, 
-      prod_name         national character varying(32)      not null, 
-      prod_desc          clob, 
-      prod_image        blob 
- ) 
- DISTRIBUTE ON (prod_no, prod_name) 
- ORGANIZE   ON (prod_no, prod_name) 
- ;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        CREATE TABLE  prod 
+ ( 
+      prod_no              number(6)      not null, 
+      prod_name         national character varying(32)      not null, 
+      prod_desc          clob, 
+      prod_image        blob 
+ ) 
+ DISTRIBUTE ON (prod_no, prod_name) 
+ ORGANIZE   ON (prod_no, prod_name) 
+ ;
+
        
+
+
        
 
        CREATE TABLE  prod 
- ( 
-      prod_no              number(6)      not null, 
-      prod_name         national character varying(32)      not null, 
-      prod_desc          clob, 
-      prod_image       bytea 
- ) WITH(ORIENTATION=COLUMN) 
- DISTRIBUTE BY HASH (prod_no, prod_name) 
- /* ORGANIZE   ON (prod_no, prod_name) */ 
- ;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        CREATE TABLE  prod 
+ ( 
+      prod_no              number(6)      not null, 
+      prod_name         national character varying(32)      not null, 
+      prod_desc          clob, 
+      prod_image       bytea 
+ ) WITH(ORIENTATION=COLUMN) 
+ DISTRIBUTE BY HASH (prod_no, prod_name) 
+ /* ORGANIZE   ON (prod_no, prod_name) */ 
+ ;
+
        
+
+
        
         		
 
        
         
 
 
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8)) 
-RETURNS INTEGER 
-LANGUAGE NZPLSQL AS 
-BEGIN_PROC 
-DECLARE
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO   NVARCHAR(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8)) 
+RETURNS INTEGER 
+LANGUAGE NZPLSQL AS 
+BEGIN_PROC 
+DECLARE
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO   NVARCHAR(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  --Writes logs and starts the recording process. 
-  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
+  --Writes logs and starts the recording process. 
+  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    --1.1
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    --1.1
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-END_PROC;
        
+END;
+END_PROC;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
-RETURN INTEGER
-AS
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO   NCHAR VARYING(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
+RETURN INTEGER
+AS
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO   NCHAR VARYING(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  /* Writes logs and starts the recording process. */
-  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
+  /* Writes logs and starts the recording process. */
+  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    /* 1.1 */
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    /* 1.1 */
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-/
        
+END;
+/
+
        
+
+
        
         		
 
        
         
 
        
 
        
-
        Qualifying Language
        Migrate the nzplSQL language to the plpgSQL language or delete the language.
        
+
        Qualifying Language
        Migrate the nzplSQL language to the plpgSQL language or delete the language.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8)) 
-RETURNS INTEGER 
-LANGUAGE NZPLSQL AS
-BEGIN_PROC 
-DECLARE
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO   NVARCHAR(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8)) 
+RETURNS INTEGER 
+LANGUAGE NZPLSQL AS
+BEGIN_PROC 
+DECLARE
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO   NVARCHAR(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  --Writes logs and starts the recording process. 
-  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
+  --Writes logs and starts the recording process. 
+  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    --1.1
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    --1.1
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-END_PROC;
        
+END;
+END_PROC;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
-RETURN INTEGER
-AS
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO   NCHAR VARYING(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
+RETURN INTEGER
+AS
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO   NCHAR VARYING(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  /* Writes logs and starts the recording process. */
-  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
+  /* Writes logs and starts the recording process. */
+  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    /* 1.1 */
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    /* 1.1 */
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-/
        
+END;
+/
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
-
        Process Compilation Specification
        The process which is started with Begin_PROC and ended with END_PROC should be removed.
        
+
        Process Compilation Specification
        The process which is started with Begin_PROC and ended with END_PROC should be removed.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
-RETURNS INTEGER
-LANGUAGE NZPLSQL AS
-BEGIN_PROC 
-DECLARE
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO   NVARCHAR(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
+RETURNS INTEGER
+LANGUAGE NZPLSQL AS
+BEGIN_PROC 
+DECLARE
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO   NVARCHAR(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  --Writes logs and starts the recording process. 
-  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
+  --Writes logs and starts the recording process. 
+  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    --1.1
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    --1.1
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-END_PROC;
        
+END;
+END_PROC;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
-RETURN INTEGER
-AS
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO  NCHAR VARYING(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
+RETURN INTEGER
+AS
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO  NCHAR VARYING(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  /* Writes logs and starts the recording process. */
-  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
+  /* Writes logs and starts the recording process. */
+  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    /* 1.1 */
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    /* 1.1 */
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-/
        
+END;
+/
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
-
        DECLARE Keyword to Declare the Local Variables
        DECLARE should be modified to AS.
        
+
        DECLARE Keyword to Declare the Local Variables
        DECLARE should be modified to AS.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
diff --git a/docs/dws/tool/dws_07_6823.html b/docs/dws/tool/dws_07_6823.html
index 8576bac1..70c438ce 100644
--- a/docs/dws/tool/dws_07_6823.html
+++ b/docs/dws/tool/dws_07_6823.html
@@ -1,791 +1,1410 @@
-
+
        Procedure
        
-
        Variable Data Type
        NVARCHAR changed to NCHAR VARING.
        
+
        Variable Data Type
        NVARCHAR changed to NCHAR VARING.
        
 
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
-RETURNS INTEGER
-LANGUAGE NZPLSQL AS
-BEGIN_PROC 
-DECLARE
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO   NVARCHAR(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
        CREATE OR REPLACE PROCEDURE "DWDB"."EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
+RETURNS INTEGER
+LANGUAGE NZPLSQL AS
+BEGIN_PROC 
+DECLARE
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO   NVARCHAR(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  --Writes logs and starts the recording process. 
-  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
+  --Writes logs and starts the recording process. 
+  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    --1.1
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    --1.1
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1';
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-END_PROC;
        
+END;
+END_PROC;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
-RETURN INTEGER
-AS
-    V_PAR_DAY ALIAS for $1;
-    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
-    V_CNT        INTEGER;
-    V_STEP_INFO  NCHAR VARYING(500);
-    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
-    O_RETURN INTEGER;
-BEGIN
-  O_RETURN := 0;
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
        CREATE OR REPLACE FUNCTION "EDW"."SP_O_HXYW_LNSACCTINFO_H"(CHARACTER VARYING(8))
+RETURN INTEGER
+AS
+    V_PAR_DAY ALIAS for $1;
+    V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H';
+    V_CNT        INTEGER;
+    V_STEP_INFO  NCHAR VARYING(500);
+    D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP;
+    O_RETURN INTEGER;
+BEGIN
+  O_RETURN := 0;
 
-  /* Writes logs and starts the recording process. */
-  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
+  /* Writes logs and starts the recording process. */
+  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
 
-  V_STEP_INFO := '1.Initialization';
-  BEGIN
-    /* 1.1 */
-    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
-    if V_CNT>0 then
-       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
-    end if;
-  END;
+  V_STEP_INFO := '1.Initialization';
+  BEGIN
+    /* 1.1 */
+    SELECT COUNT(*) INTO V_CNT FROM information_schema.columns WHERE TABLE_NAME=lower('TMPO_HXYW_LNSACCTINFO_H1');
+    if V_CNT>0 then
+       EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1';
+    end if;
+  END;
 
- RETURN O_RETURN;
+ RETURN O_RETURN;
 
-END;
-/
        
+END;
+/
+
        
+
+
        
         		
 
        
         
 
 
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE "NTZDB"."EDW"."SP_NTZ_NVARCHAR" 
-           (CHARACTER VARYING(8)) 
- RETURNS INTEGER 
- LANGUAGE NZPLSQL AS 
- BEGIN_PROC  
- DECLARE 
-     V_PAR_DAY ALIAS for $1; 
-     V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
-     V_CNT        INTEGER; 
-     V_STEP_INFO   NVARCHAR(500); 
-     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
-     O_RETURN INTEGER; 
- BEGIN 
-   O_RETURN := 0; 
-  
---Writes logs and starts the recording process. 
-  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
-  
-  V_STEP_INFO := '1.Initialization';
-  
-  RETURN O_RETURN; 
-  
- END; 
- END_PROC;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
        CREATE OR REPLACE PROCEDURE "NTZDB"."EDW"."SP_NTZ_NVARCHAR" 
+           (CHARACTER VARYING(8)) 
+ RETURNS INTEGER 
+ LANGUAGE NZPLSQL AS 
+ BEGIN_PROC  
+ DECLARE 
+     V_PAR_DAY ALIAS for $1; 
+     V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
+     V_CNT        INTEGER; 
+     V_STEP_INFO   NVARCHAR(500); 
+     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
+     O_RETURN INTEGER; 
+ BEGIN 
+   O_RETURN := 0; 
+  
+--Writes logs and starts the recording process. 
+  CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running ',' ');
+  
+  V_STEP_INFO := '1.Initialization';
+  
+  RETURN O_RETURN; 
+  
+ END; 
+ END_PROC;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION "EDW"."SP_NTZ_NVARCHAR" 
-            (CHARACTER VARYING(8)) 
- RETURN INTEGER 
- AS 
-     V_PAR_DAY ALIAS for $1; 
-     V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
-     V_CNT        INTEGER; 
-     V_STEP_INFO   NCHAR VARYING(500); 
-     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
-     O_RETURN INTEGER; 
- BEGIN 
-   O_RETURN := 0; 
-  
- /* Writes logs and starts the recording process. */
-  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
-  
-  V_STEP_INFO := '1.Initialization';
-  
-  RETURN O_RETURN; 
-  
- END; 
- /
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
        CREATE OR REPLACE FUNCTION "EDW"."SP_NTZ_NVARCHAR" 
+            (CHARACTER VARYING(8)) 
+ RETURN INTEGER 
+ AS 
+     V_PAR_DAY ALIAS for $1; 
+     V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
+     V_CNT        INTEGER; 
+     V_STEP_INFO   NCHAR VARYING(500); 
+     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
+     O_RETURN INTEGER; 
+ BEGIN 
+   O_RETURN := 0; 
+  
+ /* Writes logs and starts the recording process. */
+  SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0,'The process running',' ');
+  
+  V_STEP_INFO := '1.Initialization';
+  
+  RETURN O_RETURN; 
+  
+ END; 
+ /
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
-
        row counts
        The row_count function is supported for affected row counting.
        
+
        row counts
        The row_count function is supported for affected row counting.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE "NTZDB"."EDW"."SP_NTZ_ROWCOUNT" 
-        (CHARACTER VARYING(8)) 
- RETURNS INTEGER 
- LANGUAGE NZPLSQL AS 
- BEGIN_PROC  
- DECLARE 
-     V_PAR_DAY ALIAS for $1; 
-     O_RETURN INTEGER; 
- BEGIN 
-   O_RETURN := 0; 
-  
-  EXECUTE IMMEDIATE 'INSERT  INTO TMPO_HXYW_LNSACCTINFO_H1 
-            ( ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME ) 
-               SELECT ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME 
-                FROM O_HXYW_LNSACCTINFO T 
-              WHERE NOT EXISTS (SELECT 1 FROM O_HXYW_LNSACCT T1 
-                              WHERE T1.DATA_START_DT<='''||V_PAR_DAY||'''  
-                                AND T.MD5_VAL=T1.MD5_VAL)'; 
-  
-  O_RETURN := ROW_COUNT; 
-  
-  RETURN O_RETURN; 
-  
- END; 
- END_PROC;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
        CREATE OR REPLACE PROCEDURE "NTZDB"."EDW"."SP_NTZ_ROWCOUNT" 
+        (CHARACTER VARYING(8)) 
+ RETURNS INTEGER 
+ LANGUAGE NZPLSQL AS 
+ BEGIN_PROC  
+ DECLARE 
+     V_PAR_DAY ALIAS for $1; 
+     O_RETURN INTEGER; 
+ BEGIN 
+   O_RETURN := 0; 
+  
+  EXECUTE IMMEDIATE 'INSERT  INTO TMPO_HXYW_LNSACCTINFO_H1 
+            ( ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME ) 
+               SELECT ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME 
+                FROM O_HXYW_LNSACCTINFO T 
+              WHERE NOT EXISTS (SELECT 1 FROM O_HXYW_LNSACCT T1 
+                              WHERE T1.DATA_START_DT<='''||V_PAR_DAY||'''  
+                                AND T.MD5_VAL=T1.MD5_VAL)'; 
+  
+  O_RETURN := ROW_COUNT; 
+  
+  RETURN O_RETURN; 
+  
+ END; 
+ END_PROC;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION "EDW"."SP_NTZ_ROWCOUNT" 
-            (CHARACTER VARYING(8)) 
- RETURN INTEGER 
- AS 
-     V_PAR_DAY ALIAS for $1; 
-     O_RETURN INTEGER; 
- BEGIN 
-    O_RETURN := 0; 
-     EXECUTE IMMEDIATE 'INSERT  INTO TMPO_HXYW_LNSACCTINFO_H1 
-            ( ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME ) 
-               SELECT ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME 
-                FROM O_HXYW_LNSACCTINFO T 
-              WHERE NOT EXISTS (SELECT 1 FROM O_HXYW_LNSACCT T1 
-                              WHERE T1.DATA_START_DT<='''||V_PAR_DAY||'''  
-                                AND T.MD5_VAL=T1.MD5_VAL)'; 
-  
-    O_RETURN := SQL%ROWCOUNT; 
-  
-    RETURN O_RETURN; 
-  
- END; 
- /
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
        CREATE OR REPLACE FUNCTION "EDW"."SP_NTZ_ROWCOUNT" 
+            (CHARACTER VARYING(8)) 
+ RETURN INTEGER 
+ AS 
+     V_PAR_DAY ALIAS for $1; 
+     O_RETURN INTEGER; 
+ BEGIN 
+    O_RETURN := 0; 
+     EXECUTE IMMEDIATE 'INSERT  INTO TMPO_HXYW_LNSACCTINFO_H1 
+            ( ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME ) 
+               SELECT ACCTNO, ACCTYPE, SUBCTRLCODE, CCY, NAME 
+                FROM O_HXYW_LNSACCTINFO T 
+              WHERE NOT EXISTS (SELECT 1 FROM O_HXYW_LNSACCT T1 
+                              WHERE T1.DATA_START_DT<='''||V_PAR_DAY||'''  
+                                AND T.MD5_VAL=T1.MD5_VAL)'; 
+  
+    O_RETURN := SQL%ROWCOUNT; 
+  
+    RETURN O_RETURN; 
+  
+ END; 
+ /
+
        
+
+
        
         		
 
        
         
 
        
 
        
-
         
        ROW_COUNT identifies the number of rows associated with the previous SQL statement. If the previous SQL statement is a DELETE, INSERT, or UPDATE statement, ROW_COUNT identifies the number of rows that qualified for the operation.
        
+
         
        ROW_COUNT identifies the number of rows associated with the previous SQL statement. If the previous SQL statement is a DELETE, INSERT, or UPDATE statement, ROW_COUNT identifies the number of rows that qualified for the operation.
        
 
        
 
        
-
        System Tables
        System tables _V_SYS_COLUMNS is replaced with information_schema.columns.
        
+
        System Tables
        System tables _V_SYS_COLUMNS is replaced with information_schema.columns.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
         BEGIN 
-     SELECT COUNT(*) INTO V_CNT FROM _V_SYS_COLUMNS  
-        WHERE table_schem = 'SCOTT'  
-           AND TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1'; 
-     if V_CNT>0 then 
-        EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1'; 
-     end if; 
-   END;
        
+
        1
+2
+3
+4
+5
+6
+7
+8
         BEGIN 
+     SELECT COUNT(*) INTO V_CNT FROM _V_SYS_COLUMNS  
+        WHERE table_schem = 'SCOTT'  
+           AND TABLE_NAME='TMPO_HXYW_LNSACCTINFO_H1'; 
+     if V_CNT>0 then 
+        EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1'; 
+     end if; 
+   END;
+
        
+
+
        
 
        BEGIN 
-     SELECT COUNT(*) INTO V_CNT FROM information_schema.columns  
-       WHERE table_schema = lower('SCOTT') 
-            AND table_name = lower('TMPO_HXYW_LNSACCTINFO_H1'); 
-     if V_CNT>0 then 
-        EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1'; 
-     end if; 
-   END;
        
+
        1
+2
+3
+4
+5
+6
+7
+8
        BEGIN 
+     SELECT COUNT(*) INTO V_CNT FROM information_schema.columns  
+       WHERE table_schema = lower('SCOTT') 
+            AND table_name = lower('TMPO_HXYW_LNSACCTINFO_H1'); 
+     if V_CNT>0 then 
+        EXECUTE IMMEDIATE 'DROP TABLE TMPO_HXYW_LNSACCTINFO_H1'; 
+     end if; 
+   END;
+
        
+
+
        
         		
 
        
         
 
        
 
        
-
         
        Column mapping:
        
-
        • table_schem => table_schema
        • table_name => table_name
        • column_name => column_name
        • ordinal_position => ordinal_position
        • type_name => data_type
        • is_nullable => is_nullable
        
+
         
        Column mapping:
        
+
        • table_schem => table_schema
        • table_name => table_name
        • column_name => column_name
        • ordinal_position => ordinal_position
        • type_name => data_type
        • is_nullable => is_nullable
        
 
        
 
        
-
        For date subtraction, the corresponding Integer should be returned
        Return value should be integer for date subtraction.
        
+
        For date subtraction, the corresponding Integer should be returned
        Return value should be integer for date subtraction.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        SELECT CAST( T1.Buyback_Mature_Dt - CAST( '${gsTXDate}' AS DATE) AS CHAR( 5 ) ) 
-   FROM tab1 T1 
- WHERE T1.col1 > 10; 
- ----- 
- SELECT CURRENT_DATE - DATE '2019-03-30';
        
+
        1
+2
+3
+4
+5
        SELECT CAST( T1.Buyback_Mature_Dt - CAST( '${gsTXDate}' AS DATE) AS CHAR( 5 ) ) 
+   FROM tab1 T1 
+ WHERE T1.col1 > 10; 
+ ----- 
+ SELECT CURRENT_DATE - DATE '2019-03-30';
+
        
+
+
        
 
        SELECT CAST( EXTRACT( 'DAY' FROM ( T1.Buyback_Mature_Dt - CAST( '${gsTXDate}' AS DATE ) ) ) AS CHAR( 5 ) ) 
-    FROM tab1 T1 
-  WHERE T1.col1 > 10; 
- ------- 
- SELECT EXTRACT( 'DAY' FROM (CURRENT_DATE - CAST( '2019-03-30' AS DATE ) ) ); 
-  
-  
- 
- 
        
+
        1
+2
+3
+4
+5
+6
+7
+8
+9
        SELECT CAST( EXTRACT( 'DAY' FROM ( T1.Buyback_Mature_Dt - CAST( '${gsTXDate}' AS DATE ) ) ) AS CHAR( 5 ) ) 
+    FROM tab1 T1 
+  WHERE T1.col1 > 10; 
+ ------- 
+ SELECT EXTRACT( 'DAY' FROM (CURRENT_DATE - CAST( '2019-03-30' AS DATE ) ) ); 
+  
+  
+ 
+ 
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
-
        Support of TRANSLATE Function
        The SQL TRANSLATE() function replaces a sequence of characters in a string with another sequence of characters. The function replaces a single character at a time.
        
+
        Support of TRANSLATE Function
        The SQL TRANSLATE() function replaces a sequence of characters in a string with another sequence of characters. The function replaces a single character at a time.
        
 
-
        Netezza Syntax
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        TRANSLATE(param1) 
- TRANSLATE(1st param, 2nd param, 3rd param) 
- TRANSLATE(1st param, 2nd param, 3rd param, 4th param)
        
+
        1
+2
+3
        TRANSLATE(param1) 
+ TRANSLATE(1st param, 2nd param, 3rd param) 
+ TRANSLATE(1st param, 2nd param, 3rd param, 4th param)
+
        
+
+
        
 
        UPPER(param1) 
- TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), ' ')) 
- TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), 4th param))
        
+
        1
+2
+3
        UPPER(param1) 
+ TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), ' ')) 
+ TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), 4th param))
+
        
+
+
        
         		
 
        
         
 
        
 
        
-
         
        If it contains a single parameter, just excute the UPPER.
        
-
        UPPER(param1)
        
-
        If it contains two parameters, throw error.
        
-
        If it contains three parameters, TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), ' ')).
        
-
        If it contains four parameters, TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), 4th param)).
        
+
         
        If it contains a single parameter, just execute the UPPER.
        
+
        UPPER(param1)
        
+
        If it contains two parameters, throw error.
        
+
        If it contains three parameters, TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), ' ')).
        
+
        If it contains four parameters, TRANSLATE(1st param, 3rd param, RPAD(2nd param, LENGTH(3rd param), 4th param)).
        
 
        
 
        
-
        Data Type
        NATIONAL CHARACTER VARYING ( ANY )
        
+
        Data Type
        NATIONAL CHARACTER VARYING ( ANY )
        
 
-
        
+
        Netezza Syntax
        
+
        
-
-
-
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE sp_ntz_nchar_with_any  
-       ( NATIONAL CHARACTER VARYING(10) 
-       , NATIONAL CHARACTER VARYING(ANY) ) 
- RETURN NATIONAL CHARACTER VARYING(ANY)  
- LANGUAGE NZPLSQL AS 
- BEGIN_PROC  
- DECLARE 
-      I_LOAD_DT ALIAS FOR $1 ; 
-      -- ETL Date 
-      V_TASK_ID ALIAS FOR $2 ; 
- BEGIN 
-    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
- END; 
- END_PROC;
        
-
        CREATE OR REPLACE FUNCTION sp_ntz_nchar_with_any  
-           ( NATIONAL CHARACTER VARYING(10) 
-           , NATIONAL CHARACTER VARYING  ) 
- RETURN NATIONAL CHARACTER VARYING  
- AS  
-      I_LOAD_DT ALIAS FOR $1 ; 
-      /*  ETL Date */ 
-      V_TASK_ID ALIAS FOR $2 ; 
- BEGIN 
-    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
- END; 
- /
        
-
        
-
        
-
-
        CHARACTER VARYING ( ANY )
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
        CREATE OR REPLACE PROCEDURE sp_ntz_nchar_with_any  
+       ( NATIONAL CHARACTER VARYING(10) 
+       , NATIONAL CHARACTER VARYING(ANY) ) 
+ RETURN NATIONAL CHARACTER VARYING(ANY)  
+ LANGUAGE NZPLSQL AS 
+ BEGIN_PROC  
+ DECLARE 
+      I_LOAD_DT ALIAS FOR $1 ; 
+      -- ETL Date 
+      V_TASK_ID ALIAS FOR $2 ; 
+ BEGIN 
+    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
+ END; 
+ END_PROC;
+
        
 
-
        
-
-
-
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        CREATE OR REPLACE PROCEDURE sp_ntz_char_with_any  
-           ( NATIONAL CHARACTER VARYING(10) 
-           , CHARACTER VARYING(ANY) ) 
- RETURN CHARACTER VARYING(ANY)  
- LANGUAGE NZPLSQL AS 
- BEGIN_PROC  
- DECLARE 
-      I_LOAD_DT ALIAS FOR $1 ; 
-      -- ETL Date 
-      V_TASK_ID ALIAS FOR $2 ; 
- BEGIN 
-    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
- END; 
- END_PROC;
        
-
        CREATE OR REPLACE FUNCTION sp_ntz_char_with_any  
-          ( NATIONAL CHARACTER VARYING(10) 
-          , CHARACTER VARYING  ) 
- RETURN CHARACTER VARYING  
- AS  
-      I_LOAD_DT ALIAS FOR $1 ; 
-      /*  ETL Date */ 
-      V_TASK_ID ALIAS FOR $2 ; 
- BEGIN 
-    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
- END; 
- /
        
-
        
 
        
-
        Numeric (ANY)
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        CREATE OR REPLACE FUNCTION sp_ntz_nchar_with_any  
+           ( NATIONAL CHARACTER VARYING(10) 
+           , NATIONAL CHARACTER VARYING  ) 
+ RETURN NATIONAL CHARACTER VARYING  
+ AS  
+      I_LOAD_DT ALIAS FOR $1 ; 
+      /*  ETL Date */ 
+      V_TASK_ID ALIAS FOR $2 ; 
+ BEGIN 
+    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
+ END; 
+ /
+
        
 
-
        
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        CREATE or replace PROCEDURE sp_ntz_numeric_with_any 
-           ( NUMERIC(ANY) 
-           , NUMERIC(ANY) ) 
- RETURNS NATIONAL CHARACTER VARYING(ANY) 
- LANGUAGE NZPLSQL 
- AS BEGIN_PROC 
- DECLARE 
-   ERROR_INFO NVARCHAR(2000) := '';  
-   V_VC_YCBZ NVARCHAR(1) := 'N';    
-   V_VC_SUCCESS NVARCHAR(10) := 'SUCCESS';   
-  
-   p_l_begindate ALIAS FOR $1; 
-   p_l_enddate ALIAS FOR $2; 
- BEGIN 
-   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
-   if ERROR_INFO != V_VC_SUCCESS  then  
-     V_VC_YCBZ := 'C'; 
-   end if; 
-  
-   RETURN V_VC_SUCCESS; 
-  
- END; 
- END_PROC;
        
-
        CREATE or replace FUNCTION  sp_ntz_numeric_with_any 
-            ( NUMERIC 
-            , NUMERIC ) 
- RETURN NATIONAL CHARACTER VARYING 
- AS 
-   ERROR_INFO NCHAR VARYING(2000) := ''; 
-   V_VC_YCBZ NCHAR VARYING(1) := 'N'; 
-   V_VC_SUCCESS NCHAR VARYING(10) := 'SUCCESS'; 
-  
-   p_l_begindate ALIAS FOR $1; 
-   p_l_enddate ALIAS FOR $2; 
- BEGIN 
-   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
-   if ERROR_INFO != V_VC_SUCCESS  then  
-     V_VC_YCBZ := 'C'; 
-   end if; 
-  
-   RETURN V_VC_SUCCESS; 
-  
- END; 
- /
        
+
         		
 
        
         
 
        
 
        
-
        Exception
        TRANSACTION_ABORTED
        
+
        
+
        CHARACTER VARYING ( ANY )
        
 
-
        Netezza Syntax
        
+
        
-
-
-
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE sp_ntz_transaction_aborted 
-     ( NUMERIC(ANY) 
-     , NUMERIC(ANY) ) 
-     RETURNS NATIONAL CHARACTER VARYING(ANY) 
-     LANGUAGE NZPLSQL 
- AS BEGIN_PROC 
- DECLARE 
-   ERROR_INFO NVARCHAR(2000) := ''; 
-  
-  
-   p_l_begindate ALIAS FOR $1; 
-   p_l_enddate ALIAS FOR $2; 
- BEGIN 
-   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
-   RETURN ERROR_INFO; 
-  
-  
- EXCEPTION 
-   WHEN TRANSACTION_ABORTED THEN 
-   ROLLBACK; 
-   BEGIN 
-     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
-     RETURN ERROR_INFO; 
-   END; 
-  
-  
-   WHEN OTHERS THEN 
-   BEGIN 
-     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
-     RETURN ERROR_INFO; 
-   END; 
- END; 
- END_PROC;
        
-
        CREATE or replace FUNCTION sp_ntz_transaction_aborted 
-           ( NUMERIC 
-           , NUMERIC ) 
-     RETURN NATIONAL CHARACTER VARYING 
- AS 
-   ERROR_INFO NCHAR VARYING(2000) := ''; 
-  
-  
-   p_l_begindate ALIAS FOR $1; 
-   p_l_enddate ALIAS FOR $2; 
- BEGIN 
-   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
-   RETURN ERROR_INFO; 
-  
-  
- EXCEPTION  
-   WHEN INVALID_TRANSACTION_TERMINATION THEN 
-   ROLLBACK; 
-   BEGIN 
-     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
-     RETURN ERROR_INFO; 
-   END; 
-  
-  
-   WHEN OTHERS THEN 
-   BEGIN 
-     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
-     RETURN ERROR_INFO; 
-   END; 
- END; 
- /
        
-
        
-
        
-
-
        END statement is specified without semicolon (;)
        END statement specified without semicolon (;) is migrated as follows:
        
-
        END /
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
        CREATE OR REPLACE PROCEDURE sp_ntz_char_with_any  
+           ( NATIONAL CHARACTER VARYING(10) 
+           , CHARACTER VARYING(ANY) ) 
+ RETURN CHARACTER VARYING(ANY)  
+ LANGUAGE NZPLSQL AS 
+ BEGIN_PROC  
+ DECLARE 
+      I_LOAD_DT ALIAS FOR $1 ; 
+      -- ETL Date 
+      V_TASK_ID ALIAS FOR $2 ; 
+ BEGIN 
+    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
+ END; 
+ END_PROC;
+
        
 
-
        
-
-
-
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        CREATE or replace PROCEDURE sp_ntz_end_wo_semicolon 
-      ( NATIONAL CHARACTER VARYING(10) ) 
- RETURNS CHARACTER VARYING(ANY) 
- LANGUAGE NZPLSQL 
- AS  
- BEGIN_PROC 
- DECLARE 
-    v_B64 Varchar(64) := 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/'; 
-    v_I int := 0; 
-    v_J int := 0; 
-    v_K int := 0; 
-    v_N int := 0; 
-    v_out Numeric(38,0) := 0; 
-    I_LOAD_DT ALIAS FOR $1; 
-  
- BEGIN 
-     v_N:=Length(v_B64); 
-     FOR v_I In Reverse 1..Length(IN_base64)  
-     LOOP 
-       v_J:=Instr(v_B64,Substr(IN_base64,v_I,1))-1; 
-       If v_J <0 Then 
-         RETURN -1; 
-       End If; 
-       V_Out:=V_Out+v_J*(v_N**v_K); 
-       v_K:=v_K+1; 
-     END LOOP; 
-     RETURN V_Out; 
- END 
- END_PROC;
        
-
        CREATE or replace FUNCTION sp_ntz_end_wo_semicolon 
-      ( NATIONAL CHARACTER VARYING(10) ) 
-     RETURN CHARACTER VARYING 
- AS 
-    v_B64 Varchar(64) := 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/'; 
-    v_I int := 0; 
-    v_J int := 0; 
-    v_K int := 0; 
-    v_N int := 0; 
-    v_out Numeric(38,0) := 0; 
-    I_LOAD_DT ALIAS FOR $1; 
-  
-   BEGIN 
-     v_N:=Length(v_B64); 
-     FOR v_I In Reverse 1..Length(IN_base64)  
-     LOOP 
-       v_J:=Instr(v_B64,Substr(IN_base64,v_I,1))-1; 
-       If v_J <0 Then 
-         RETURN -1; 
-       End If; 
-       V_Out:=V_Out+v_J*(v_N**v_K); 
-       v_K:=v_K+1; 
-     END LOOP; 
-     RETURN V_Out; 
-   END; 
- /
        
-
        
 
        
-
        
-
        LOOP
        
-
        
-
-
-
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        CREATE OR REPLACE PROCEDURE sp_ntz_for_loop_with_more_dots 
-      ( INTEGER ) 
-     RETURNS CHARACTER VARYING(ANY) 
-     LANGUAGE NZPLSQL 
- AS BEGIN_PROC 
- DECLARE p_abc  INTEGER; 
-         p_bcd  INTEGER; 
-         p_var1 ALIAS FOR $1; 
- BEGIN 
-      p_bcd := ISNULL(p_var1, 10); 
-      RAISE NOTICE 'p_bcd=%', p_bcd; 
-  
-      FOR p_abc IN 0...(p_bcd) 
-      LOOP 
-           RAISE NOTICE 'hello world %', p_abc; 
-      END LOOP; 
-  
- END; 
- END_PROC;
        
 
        CREATE OR replace FUNCTION sp_ntz_for_loop_with_more_dots 
-      ( INTEGER ) 
-   RETURN CHARACTER VARYING  
-   AS  
-         p_abc INTEGER ; 
-         p_bcd  INTEGER; 
-         p_var1 ALIAS FOR $1; 
-  
- BEGIN 
-      p_bcd := NVL(p_var1, 10); 
-  
-      RAISE NOTICE 'p_bcd=%', p_bcd; 
-  
-      FOR p_abc IN 0..(p_bcd) 
-      LOOP 
-           RAISE NOTICE 'hello world %', p_abc; 
-  
-      END LOOP; 
-  
- END; 
- /
        
-
        
-
        
-
        
-
        Gauss keyword
        CURSOR
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        CREATE OR REPLACE FUNCTION sp_ntz_char_with_any  
+          ( NATIONAL CHARACTER VARYING(10) 
+          , CHARACTER VARYING  ) 
+ RETURN CHARACTER VARYING  
+ AS  
+      I_LOAD_DT ALIAS FOR $1 ; 
+      /*  ETL Date */ 
+      V_TASK_ID ALIAS FOR $2 ; 
+ BEGIN 
+    RETURN I_LOAD_DT || ',' || V_TASK_ID; 
+ END; 
+ /
+
        
 
-
        
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        CREATE OR REPLACE PROCEDURE sp_ntz_keyword_cursor() 
-     RETURNS INTEGER 
-     LANGUAGE NZPLSQL 
- AS BEGIN_PROC 
- DECLARE 
-    tablename NVARCHAR(100); 
-    cursor RECORD; 
- BEGIN 
-    FOR cursor IN SELECT t.TABLENAME FROM _V_TABLE t  
-                   WHERE TABLENAME LIKE 'T_ODS_CRM%' 
-    LOOP 
-         tablename := cursor.TABLENAME; 
-    END LOOP; 
- END; 
- END_PROC;
        
-
        CREATE OR REPLACE FUNCTION sp_ntz_keyword_cursor() 
-     RETURN INTEGER 
- AS  
-    tablename NCHAR VARYING(100); 
-    mig_cursor RECORD; 
- BEGIN 
-    FOR mig_cursor IN (SELECT t.TABLENAME FROM _V_TABLE t  
-                   WHERE TABLENAME LIKE 'T_ODS_CRM%') 
-    LOOP 
-         tablename := mig_cursor.TABLENAME; 
-    END LOOP; 
- END; 
- /
        
+
         		
 
        
         
 
        
 
        
-
        
-
        DECLARE
        
-
        
-
-
-
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        CREATE OR REPLACE PROCEDURE sp_ntz_declare_inside_begin 
-      ( NATIONAL CHARACTER VARYING(10) ) 
- RETURNS INTEGER 
- LANGUAGE NZPLSQL 
- AS BEGIN_PROC 
- DECLARE 
-     I_LOAD_DT ALIAS FOR $1;  
- BEGIN 
-    DECLARE 
-            MYCUR              RECORD; 
-            VIEWSQL1           NVARCHAR(4000); 
-    BEGIN  
-    FOR MYCUR IN ( SELECT VIEWNAME,VIEWSQL 
-                        FROM T_DDW_AUTO_F5_VIEW_DEFINE 
-        WHERE OWNER = 'ODS_PROD' ) 
-          LOOP 
-               VIEWSQL1 := MYCUR.VIEWSQL; 
-               WHILE INSTR(VIEWSQL1,'v_p_etldate') > 0  
-      LOOP 
-                   VIEWSQL1 := SUBSTR(VIEWSQL1,1,INSTR(VIEWSQL1,'v_p_etldate') - 1)||''''||I_LOAD_DT||''''||SUBSTR(VIEWSQL1,INSTR(VIEWSQL1,'v_p_etldate') + 11); 
-               END LOOP; 
-  
-  
-               EXECUTE IMMEDIATE VIEWSQL1; 
-          END LOOP; 
-    END; 
-  
-  
-    RETURN 0; 
- END; 
- END_PROC;
        
-
        CREATE OR REPLACE FUNCTION sp_ntz_declare_inside_begin 
-      ( NATIONAL CHARACTER VARYING(10) ) 
- RETURN INTEGER 
- AS 
-     I_LOAD_DT ALIAS FOR $1;  
- BEGIN 
-    DECLARE 
-            MYCUR              RECORD; 
-            VIEWSQL1           NCHAR VARYING(4000); 
-    BEGIN  
-    FOR MYCUR IN ( SELECT VIEWNAME,VIEWSQL 
-                        FROM T_DDW_AUTO_F5_VIEW_DEFINE 
-        WHERE OWNER = 'ODS_PROD' ) 
-          LOOP 
-               VIEWSQL1 := MYCUR.VIEWSQL; 
-               WHILE INSTR(VIEWSQL1,'v_p_etldate') > 0  
-      LOOP 
-                   VIEWSQL1 := SUBSTR(VIEWSQL1,1,INSTR(VIEWSQL1,'v_p_etldate') - 1)||''''||I_LOAD_DT||''''||SUBSTR(VIEWSQL1,INSTR(VIEWSQL1,'v_p_etldate') + 11); 
-               END LOOP; 
-  
-  
-               EXECUTE IMMEDIATE VIEWSQL1; 
-          END LOOP; 
-    END; 
-  
-  
-    RETURN 0; 
- END; 
- /
        
-
        
-
        
-
        
-
        EXECUTE AS CALLER
        
-
        
-
-
-
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        CREATE or replace PROCEDURE  sp_ntz_exec_as_caller 
-      ( CHARACTER VARYING(512) ) 
-     RETURNS INTEGER 
-     LANGUAGE NZPLSQL 
-     EXECUTE AS CALLER 
- AS BEGIN_PROC  
- DECLARE  
-  SQL ALIAS FOR $1;  
- BEGIN  
-  EXECUTE IMMEDIATE SQL;  
-  RETURN 0;  
- END;  
- END_PROC; 
- ------------------------ 
- CREATE or replace PROCEDURE  sp_ntz_exec_as_owner 
-      ( CHARACTER VARYING(512) ) 
-     RETURNS INTEGER 
-     LANGUAGE NZPLSQL 
-     EXECUTE AS OWNER 
- AS BEGIN_PROC  
- DECLARE  
-  SQL ALIAS FOR $1;  
- BEGIN  
-  EXECUTE IMMEDIATE SQL;  
-  RETURN 0;  
- END;  
- END_PROC;
        
-
        CREATE OR REPLACE FUNCTION sp_ntz_exec_as_caller 
-      ( CHARACTER VARYING(512) ) 
-     RETURN INTEGER 
-    SECURITY INVOKER 
- AS  
-  SQL ALIAS FOR $1;  
- BEGIN  
-     EXECUTE IMMEDIATE SQL;  
-     RETURN 0;  
- END;  
- / 
- ------------------------ 
- CREATE OR REPLACE FUNCTION sp_ntz_exec_as_owner 
-      ( CHARACTER VARYING(512) ) 
-     RETURN INTEGER 
-    SECURITY DEFINER 
- AS  
-  SQL ALIAS FOR $1;  
- BEGIN  
-     EXECUTE IMMEDIATE SQL;  
-     RETURN 0;  
- END;  
- /
        
-
        
-
        
-
        
-
        Expression
        SELECT result assign into variable.
        
+
        Numeric (ANY)
        
 
-
        Netezza Syntax
        
+
        
-
-
-
+
+
+
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE sp_sel_res_to_var 
-   ( NATIONAL CHARACTER VARYING(10) ) 
-     RETURNS CHARACTER VARYING(ANY) 
-     LANGUAGE NZPLSQL 
- AS BEGIN_PROC 
- DECLARE 
-      counts INTEGER := 0 ; 
-      I_LOAD_DT ALIAS FOR $1 ; 
- BEGIN 
-       
-         COUNTS := SELECT COUNT( * ) 
-                     FROM tb_sel_res_to_var 
-                    WHERE ETLDATE = I_LOAD_DT; 
-                           
-   EXECUTE IMMEDIATE 'insert into TABLES_COUNTS values( ''tb_sel_res_to_var'', ''' || I_LOAD_DT || ''', ' || COUNTS || ')' ; 
-       
-      RETURN '0' ; 
- END; 
- END_PROC;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
        CREATE or replace PROCEDURE sp_ntz_numeric_with_any 
+           ( NUMERIC(ANY) 
+           , NUMERIC(ANY) ) 
+ RETURNS NATIONAL CHARACTER VARYING(ANY) 
+ LANGUAGE NZPLSQL 
+ AS BEGIN_PROC 
+ DECLARE 
+   ERROR_INFO NVARCHAR(2000) := '';  
+   V_VC_YCBZ NVARCHAR(1) := 'N';    
+   V_VC_SUCCESS NVARCHAR(10) := 'SUCCESS';   
+  
+   p_l_begindate ALIAS FOR $1; 
+   p_l_enddate ALIAS FOR $2; 
+ BEGIN 
+   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
+   if ERROR_INFO != V_VC_SUCCESS  then  
+     V_VC_YCBZ := 'C'; 
+   end if; 
+  
+   RETURN V_VC_SUCCESS; 
+  
+ END; 
+ END_PROC;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION sp_sel_res_to_var 
-   ( NATIONAL CHARACTER VARYING(10) ) 
-     RETURN CHARACTER VARYING 
- AS  
-      counts INTEGER := 0 ; 
-      I_LOAD_DT ALIAS FOR $1 ; 
- BEGIN 
-       
-         SELECT COUNT(*) 
-     INTO COUNTS 
-           FROM tb_sel_res_to_var 
-          WHERE ETLDATE = I_LOAD_DT; 
-                           
-   EXECUTE IMMEDIATE 'insert into TABLES_COUNTS values( ''tb_sel_res_to_var'', ''' || I_LOAD_DT || ''', ' || COUNTS || ')' ; 
-       
-      RETURN '0' ; 
- END; 
- /
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
        CREATE or replace FUNCTION  sp_ntz_numeric_with_any 
+            ( NUMERIC 
+            , NUMERIC ) 
+ RETURN NATIONAL CHARACTER VARYING 
+ AS 
+   ERROR_INFO NCHAR VARYING(2000) := ''; 
+   V_VC_YCBZ NCHAR VARYING(1) := 'N'; 
+   V_VC_SUCCESS NCHAR VARYING(10) := 'SUCCESS'; 
+  
+   p_l_begindate ALIAS FOR $1; 
+   p_l_enddate ALIAS FOR $2; 
+ BEGIN 
+   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
+   if ERROR_INFO != V_VC_SUCCESS  then  
+     V_VC_YCBZ := 'C'; 
+   end if; 
+  
+   RETURN V_VC_SUCCESS; 
+  
+ END; 
+ /
+
        
+
+
        
+
        
+
        
+
        Exception
        TRANSACTION_ABORTED
        
+
+
        
+
+
+
+
+
+
+
+
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
        CREATE OR REPLACE PROCEDURE sp_ntz_transaction_aborted 
+     ( NUMERIC(ANY) 
+     , NUMERIC(ANY) ) 
+     RETURNS NATIONAL CHARACTER VARYING(ANY) 
+     LANGUAGE NZPLSQL 
+ AS BEGIN_PROC 
+ DECLARE 
+   ERROR_INFO NVARCHAR(2000) := ''; 
+  
+  
+   p_l_begindate ALIAS FOR $1; 
+   p_l_enddate ALIAS FOR $2; 
+ BEGIN 
+   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
+   RETURN ERROR_INFO; 
+  
+  
+ EXCEPTION 
+   WHEN TRANSACTION_ABORTED THEN 
+   ROLLBACK; 
+   BEGIN 
+     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
+     RETURN ERROR_INFO; 
+   END; 
+  
+  
+   WHEN OTHERS THEN 
+   BEGIN 
+     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
+     RETURN ERROR_INFO; 
+   END; 
+ END; 
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
        CREATE OR REPLACE FUNCTION sp_ntz_transaction_aborted 
+           ( NUMERIC 
+           , NUMERIC ) 
+     RETURN NATIONAL CHARACTER VARYING 
+ AS 
+   ERROR_INFO NCHAR VARYING(2000) := ''; 
+  
+  
+   p_l_begindate ALIAS FOR $1; 
+   p_l_enddate ALIAS FOR $2; 
+ BEGIN 
+   ERROR_INFO := CRHSP_CRH_ETL_EXCHDATE(p_l_begindate,p_l_enddate); 
+   RETURN ERROR_INFO; 
+  
+  
+ EXCEPTION  
+   WHEN INVALID_TRANSACTION_TERMINATION THEN 
+   ROLLBACK; 
+   BEGIN 
+     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
+     RETURN ERROR_INFO; 
+   END; 
+  
+  
+   WHEN OTHERS THEN 
+   BEGIN 
+     ERROR_INFO := SQLERRM||'  sp_o_transaction_aborted:'; 
+     RETURN ERROR_INFO; 
+   END; 
+ END; 
+ /
+
        
+
+
        
+
        
+
        
+
        
+
        END statement is specified without semicolon (;)
        END statement specified without semicolon (;) is migrated as follows:
        
+
        END /
        
+
+
        
+
+
+
+
+
+
+
+
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
        CREATE OR REPLACE PROCEDURE sp_ntz_end_wo_semicolon 
+      ( NATIONAL CHARACTER VARYING(10) ) 
+ RETURNS CHARACTER VARYING(ANY) 
+ LANGUAGE NZPLSQL 
+ AS  
+ BEGIN_PROC 
+ DECLARE 
+    v_B64 Varchar(64) := 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/'; 
+    v_I int := 0; 
+    v_J int := 0; 
+    v_K int := 0; 
+    v_N int := 0; 
+    v_out Numeric(38,0) := 0; 
+    I_LOAD_DT ALIAS FOR $1; 
+  
+ BEGIN 
+     v_N:=Length(v_B64); 
+     FOR v_I In Reverse 1..Length(IN_base64)  
+     LOOP 
+       v_J:=Instr(v_B64,Substr(IN_base64,v_I,1))-1; 
+       If v_J <0 Then 
+         RETURN -1; 
+       End If; 
+       V_Out:=V_Out+v_J*(v_N**v_K); 
+       v_K:=v_K+1; 
+     END LOOP; 
+     RETURN V_Out; 
+ END 
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
        CREATE OR REPLACE FUNCTION sp_ntz_end_wo_semicolon 
+      ( NATIONAL CHARACTER VARYING(10) ) 
+     RETURN CHARACTER VARYING 
+ AS 
+    v_B64 Varchar(64) := 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/'; 
+    v_I int := 0; 
+    v_J int := 0; 
+    v_K int := 0; 
+    v_N int := 0; 
+    v_out Numeric(38,0) := 0; 
+    I_LOAD_DT ALIAS FOR $1; 
+  
+   BEGIN 
+     v_N:=Length(v_B64); 
+     FOR v_I In Reverse 1..Length(IN_base64)  
+     LOOP 
+       v_J:=Instr(v_B64,Substr(IN_base64,v_I,1))-1; 
+       If v_J <0 Then 
+         RETURN -1; 
+       End If; 
+       V_Out:=V_Out+v_J*(v_N**v_K); 
+       v_K:=v_K+1; 
+     END LOOP; 
+     RETURN V_Out; 
+   END; 
+ /
+
        
+
+
        
+
        
+
        
+
        
+
        LOOP
        
+
        
+
+
+
+
+
+
+
+
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
        CREATE OR REPLACE PROCEDURE sp_ntz_for_loop_with_more_dots 
+      ( INTEGER ) 
+     RETURNS CHARACTER VARYING(ANY) 
+     LANGUAGE NZPLSQL 
+ AS BEGIN_PROC 
+ DECLARE p_abc  INTEGER; 
+         p_bcd  INTEGER; 
+         p_var1 ALIAS FOR $1; 
+ BEGIN 
+      p_bcd := ISNULL(p_var1, 10); 
+      RAISE NOTICE 'p_bcd=%', p_bcd; 
+  
+      FOR p_abc IN 0...(p_bcd) 
+      LOOP 
+           RAISE NOTICE 'hello world %', p_abc; 
+      END LOOP; 
+  
+ END; 
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
        CREATE OR REPLACE FUNCTION sp_ntz_for_loop_with_more_dots 
+      ( INTEGER ) 
+   RETURN CHARACTER VARYING  
+   AS  
+         p_abc INTEGER ; 
+         p_bcd  INTEGER; 
+         p_var1 ALIAS FOR $1; 
+  
+ BEGIN 
+      p_bcd := NVL(p_var1, 10); 
+  
+      RAISE NOTICE 'p_bcd=%', p_bcd; 
+  
+      FOR p_abc IN 0..(p_bcd) 
+      LOOP 
+           RAISE NOTICE 'hello world %', p_abc; 
+  
+      END LOOP; 
+  
+ END; 
+ /
+
        
+
+
        
+
        
+
        
+
        
+
        Gauss keyword
        CURSOR
        
+
+
        
+
+
+
+
+
+
+
+
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
        CREATE OR REPLACE PROCEDURE sp_ntz_keyword_cursor() 
+     RETURNS INTEGER 
+     LANGUAGE NZPLSQL 
+ AS BEGIN_PROC 
+ DECLARE 
+    tablename NVARCHAR(100); 
+    cursor RECORD; 
+ BEGIN 
+    FOR cursor IN SELECT t.TABLENAME FROM _V_TABLE t  
+                   WHERE TABLENAME LIKE 'T_ODS_CRM%' 
+    LOOP 
+         tablename := cursor.TABLENAME; 
+    END LOOP; 
+ END; 
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
        CREATE OR REPLACE FUNCTION sp_ntz_keyword_cursor() 
+     RETURN INTEGER 
+ AS  
+    tablename NCHAR VARYING(100); 
+    mig_cursor RECORD; 
+ BEGIN 
+    FOR mig_cursor IN (SELECT t.TABLENAME FROM _V_TABLE t  
+                   WHERE TABLENAME LIKE 'T_ODS_CRM%') 
+    LOOP 
+         tablename := mig_cursor.TABLENAME; 
+    END LOOP; 
+ END; 
+ /
+
        
+
+
        
+
        
+
        
+
        
+
        DECLARE
        
+
        
+
+
+
+
+
+
+
+
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
        CREATE OR REPLACE PROCEDURE sp_ntz_declare_inside_begin 
+      ( NATIONAL CHARACTER VARYING(10) ) 
+ RETURNS INTEGER 
+ LANGUAGE NZPLSQL 
+ AS BEGIN_PROC 
+ DECLARE 
+     I_LOAD_DT ALIAS FOR $1;  
+ BEGIN 
+    DECLARE 
+            MYCUR              RECORD; 
+            VIEWSQL1           NVARCHAR(4000); 
+    BEGIN  
+    FOR MYCUR IN ( SELECT VIEWNAME,VIEWSQL 
+                        FROM T_DDW_AUTO_F5_VIEW_DEFINE 
+        WHERE OWNER = 'ODS_PROD' ) 
+          LOOP 
+               VIEWSQL1 := MYCUR.VIEWSQL; 
+               WHILE INSTR(VIEWSQL1,'v_p_etldate') > 0  
+      LOOP 
+                   VIEWSQL1 := SUBSTR(VIEWSQL1,1,INSTR(VIEWSQL1,'v_p_etldate') - 1)||''''||I_LOAD_DT||''''||SUBSTR(VIEWSQL1,INSTR(VIEWSQL1,'v_p_etldate') + 11); 
+               END LOOP; 
+  
+  
+               EXECUTE IMMEDIATE VIEWSQL1; 
+          END LOOP; 
+    END; 
+  
+  
+    RETURN 0; 
+ END; 
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
        CREATE OR REPLACE FUNCTION sp_ntz_declare_inside_begin 
+      ( NATIONAL CHARACTER VARYING(10) ) 
+ RETURN INTEGER 
+ AS 
+     I_LOAD_DT ALIAS FOR $1;  
+ BEGIN 
+    DECLARE 
+            MYCUR              RECORD; 
+            VIEWSQL1           NCHAR VARYING(4000); 
+    BEGIN  
+    FOR MYCUR IN ( SELECT VIEWNAME,VIEWSQL 
+                        FROM T_DDW_AUTO_F5_VIEW_DEFINE 
+        WHERE OWNER = 'ODS_PROD' ) 
+          LOOP 
+               VIEWSQL1 := MYCUR.VIEWSQL; 
+               WHILE INSTR(VIEWSQL1,'v_p_etldate') > 0  
+      LOOP 
+                   VIEWSQL1 := SUBSTR(VIEWSQL1,1,INSTR(VIEWSQL1,'v_p_etldate') - 1)||''''||I_LOAD_DT||''''||SUBSTR(VIEWSQL1,INSTR(VIEWSQL1,'v_p_etldate') + 11); 
+               END LOOP; 
+  
+  
+               EXECUTE IMMEDIATE VIEWSQL1; 
+          END LOOP; 
+    END; 
+  
+  
+    RETURN 0; 
+ END; 
+ /
+
        
+
+
        
+
        
+
        
+
        
+
        EXECUTE AS CALLER
        
+
        
+
+
+
+
+
+
+
+
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
        CREATE OR REPLACE PROCEDURE  sp_ntz_exec_as_caller 
+      ( CHARACTER VARYING(512) ) 
+     RETURNS INTEGER 
+     LANGUAGE NZPLSQL 
+     EXECUTE AS CALLER 
+ AS BEGIN_PROC  
+ DECLARE  
+  SQL ALIAS FOR $1;  
+ BEGIN  
+  EXECUTE IMMEDIATE SQL;  
+  RETURN 0;  
+ END;  
+ END_PROC; 
+ ------------------------ 
+ CREATE or replace PROCEDURE  sp_ntz_exec_as_owner 
+      ( CHARACTER VARYING(512) ) 
+     RETURNS INTEGER 
+     LANGUAGE NZPLSQL 
+     EXECUTE AS OWNER 
+ AS BEGIN_PROC  
+ DECLARE  
+  SQL ALIAS FOR $1;  
+ BEGIN  
+  EXECUTE IMMEDIATE SQL;  
+  RETURN 0;  
+ END;  
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
        CREATE OR REPLACE FUNCTION sp_ntz_exec_as_caller 
+      ( CHARACTER VARYING(512) ) 
+     RETURN INTEGER 
+    SECURITY INVOKER 
+ AS  
+  SQL ALIAS FOR $1;  
+ BEGIN  
+     EXECUTE IMMEDIATE SQL;  
+     RETURN 0;  
+ END;  
+ / 
+ ------------------------ 
+ CREATE OR REPLACE FUNCTION sp_ntz_exec_as_owner 
+      ( CHARACTER VARYING(512) ) 
+     RETURN INTEGER 
+    SECURITY DEFINER 
+ AS  
+  SQL ALIAS FOR $1;  
+ BEGIN  
+     EXECUTE IMMEDIATE SQL;  
+     RETURN 0;  
+ END;  
+ /
+
        
+
+
        
+
        
+
        
+
        
+
        Expression
        SELECT result assign into variable.
        
+
+
        
+
+
+
+
+
diff --git a/docs/dws/tool/dws_07_6824.html b/docs/dws/tool/dws_07_6824.html
index 46bf9876..58897ae0 100644
--- a/docs/dws/tool/dws_07_6824.html
+++ b/docs/dws/tool/dws_07_6824.html
@@ -1,163 +1,274 @@
-
+
        System Functions
        
-
        ISNULL()
        
-
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
        CREATE OR REPLACE PROCEDURE sp_sel_res_to_var 
+   ( NATIONAL CHARACTER VARYING(10) ) 
+     RETURNS CHARACTER VARYING(ANY) 
+     LANGUAGE NZPLSQL 
+ AS BEGIN_PROC 
+ DECLARE 
+      counts INTEGER := 0 ; 
+      I_LOAD_DT ALIAS FOR $1 ; 
+ BEGIN 
+       
+         COUNTS := SELECT COUNT( * ) 
+                     FROM tb_sel_res_to_var 
+                    WHERE ETLDATE = I_LOAD_DT; 
+                           
+   EXECUTE IMMEDIATE 'insert into TABLES_COUNTS values( ''tb_sel_res_to_var'', ''' || I_LOAD_DT || ''', ' || COUNTS || ')' ; 
+       
+      RETURN '0' ; 
+ END; 
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
        CREATE OR REPLACE FUNCTION sp_sel_res_to_var 
+   ( NATIONAL CHARACTER VARYING(10) ) 
+     RETURN CHARACTER VARYING 
+ AS  
+      counts INTEGER := 0 ; 
+      I_LOAD_DT ALIAS FOR $1 ; 
+ BEGIN 
+       
+         SELECT COUNT(*) 
+     INTO COUNTS 
+           FROM tb_sel_res_to_var 
+          WHERE ETLDATE = I_LOAD_DT; 
+                           
+   EXECUTE IMMEDIATE 'insert into TABLES_COUNTS values( ''tb_sel_res_to_var'', ''' || I_LOAD_DT || ''', ' || COUNTS || ')' ; 
+       
+      RETURN '0' ; 
+ END; 
+ /
+
        
+
+
        
         		
 
        
         
 
 
        
+
        Netezza Syntax
        
+
        ISNULL()
        
+
        
-
-
-
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        SELECT A.ETL_DATE, A.BRANCH_CODE, A.CUST_NO 
-           , ISNULL (  B.RES_STOCK,0) AS RES_STOCK 
-           , ISNULL ( B.ZY_VOL ,0 ) AS ZY_VOL 
-           , ISNULL ( B.ZJ_VOL,0 ) AS ZJ_VOL 
-    FROM tab123;
        
-
        SELECT A.ETL_DATE, A.BRANCH_CODE, A.CUST_NO 
-            , NVL (  B.RES_STOCK,0) AS RES_STOCK 
-            , NVL ( B.ZY_VOL ,0 ) AS ZY_VOL 
-            , NVL ( B.ZJ_VOL,0 ) AS ZJ_VOL 
-    FROM tab123;
        
-
        
-
        
-
        
-
        NVL
        Second parameter is missing.
        
+
        1
+2
+3
+4
+5
        SELECT A.ETL_DATE, A.BRANCH_CODE, A.CUST_NO 
+           , ISNULL (  B.RES_STOCK,0) AS RES_STOCK 
+           , ISNULL ( B.ZY_VOL ,0 ) AS ZY_VOL 
+           , ISNULL ( B.ZJ_VOL,0 ) AS ZJ_VOL 
+    FROM tab123;
+
        
 
-
        
-
-
-
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        SELECT NVL( SUM(A3.DA_CPTL_BAL_YEAR) / NULLIF(V_YEAR_DAYS, 0) ) AS CPTL_BAL_AVE_YR  
-      , NVL( NVL(SUM (CASE WHEN A3.OPENACT_DT >= V_YEAR_START THEN A3.DA_CPTL_BAL_YEAR 
-       END) / NULLIF(V_YEAR_DAYS, 0) ), 0) AS CPTL_BAL_AVE_YR_OP  
-      , NVL( SUM(A3.DA_CPTL_BAL) / NULLIF(V_YEAR_DAYS, 0) ) AS CPTL_BAL_AVE 
-   FROM tab1 A3;
        
-
        ELECT NVL( SUM(A3.DA_CPTL_BAL_YEAR) / NULLIF(V_YEAR_DAYS, 0), NULL ) AS CPTL_BAL_AVE_YR  
-      , NVL( NVL(SUM (CASE WHEN A3.OPENACT_DT >= V_YEAR_START THEN A3.DA_CPTL_BAL_YEAR 
-       END) / NULLIF(V_YEAR_DAYS, 0), NULL), 0) AS CPTL_BAL_AVE_YR_OP  
-      , NVL( SUM(A3.DA_CPTL_BAL) / NULLIF(V_YEAR_DAYS, 0), NULL ) AS CPTL_BAL_AVE 
-   FROM tab1 A3;
        
-
        
 
        
-
        
-
        DATE
        Casting the data type.
        
+
        1
+2
+3
+4
+5
        SELECT A.ETL_DATE, A.BRANCH_CODE, A.CUST_NO 
+            , NVL (  B.RES_STOCK,0) AS RES_STOCK 
+            , NVL ( B.ZY_VOL ,0 ) AS ZY_VOL 
+            , NVL ( B.ZJ_VOL,0 ) AS ZJ_VOL 
+    FROM tab123;
+
        
 
-
        
-
-
-
-
-
        Netezza Syntax
        
-
        Syntax After Migration
        
-
        SELECT A1.ETL_DATE, A1.MARKET_CODE 
-      , A1.DECLARATION_DT 
-      , ROW_NUMBER() OVER(PARTITION BY A1.MARKET_CODE, A1.STOCK_CODE, DATE_PART('YEAR', DATE(A1.DECLARATION_DT)) ORDER BY A1.DECLARATION_DT DESC) AS RN 
-   FROM tb_date_type_casting A1; 
-  
-  
- SELECT A1.ETL_DATE, A1.MARKET_CODE 
-      , A1.DECLARATION_DT 
-      , ROW_NUMBER() OVER(PARTITION BY A1.MARKET_CODE, A1.STOCK_CODE, DATE_PART('YEAR', DATE(A1.DECLARATION_DT)) ORDER BY A1.DECLARATION_DT DESC) AS RN 
-   FROM tb_date_type_casting A1;
        
-
        SELECT A1.ETL_DATE, A1.MARKET_CODE 
-      , A1.DECLARATION_DT 
-      , ROW_NUMBER() OVER(PARTITION BY A1.MARKET_CODE, A1.STOCK_CODE, DATE_PART('YEAR', CAST(A1.DECLARATION_DT AS DATE)) ORDER BY A1.DECLARATION_DT DESC) AS RN 
-   FROM tb_date_type_casting A1;
        
+
         		
 
        
         
 
        
 
        
 
        
-
        analytic_function
        
-
        Netezza Syntax
        
+
        NVL
        Second parameter is missing.
        
+
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        SELECT COALESCE(NULLIF(GROUP_CONCAT(a.column_name),''),'*') 
-   FROM (SELECT a.column_name 
-           FROM tb_ntz_group_concat a 
-          WHERE UPPER(a.table_name) = 'EMP' 
-          ORDER BY a.column_pos) a; 
- ------------- 
- SELECT admin.group_concat('"top'||lpad(a.table_name,2,'0')||'":{'||a.column_name||'}') topofund_data 
-   FROM (SELECT a.table_name, a.column_name 
-           FROM tb_ntz_group_concat a 
-          WHERE UPPER(a.table_name) = 'EMP' 
-          ORDER BY a.column_pos) a;
        
+
        1
+2
+3
+4
+5
        SELECT NVL( SUM(A3.DA_CPTL_BAL_YEAR) / NULLIF(V_YEAR_DAYS, 0) ) AS CPTL_BAL_AVE_YR  
+      , NVL( NVL(SUM (CASE WHEN A3.OPENACT_DT >= V_YEAR_START THEN A3.DA_CPTL_BAL_YEAR 
+       END) / NULLIF(V_YEAR_DAYS, 0) ), 0) AS CPTL_BAL_AVE_YR_OP  
+      , NVL( SUM(A3.DA_CPTL_BAL) / NULLIF(V_YEAR_DAYS, 0) ) AS CPTL_BAL_AVE 
+   FROM tab1 A3;
+
        
+
+
        
 
        SELECT COALESCE(NULLIF(STRING_AGG(a.column_name, ','),''),'*') 
-   FROM (SELECT a.column_name 
-           FROM tb_ntz_group_concat a 
-          WHERE UPPER(a.table_name) = 'EMP' 
-          ORDER BY a.column_pos) a; 
- ------------- 
- SELECT STRING_AGG('"top'||lpad(a.table_name,3,'0')||'":{'||a.column_name||'}', ',') topofund_data 
-   FROM (SELECT a.table_name, a.column_name 
-           FROM tb_ntz_group_concat a 
-          WHERE UPPER(a.table_name) = 'EMP' 
-          ORDER BY a.column_pos) a;
        
+
        1
+2
+3
+4
+5
        ELECT NVL( SUM(A3.DA_CPTL_BAL_YEAR) / NULLIF(V_YEAR_DAYS, 0), NULL ) AS CPTL_BAL_AVE_YR  
+      , NVL( NVL(SUM (CASE WHEN A3.OPENACT_DT >= V_YEAR_START THEN A3.DA_CPTL_BAL_YEAR 
+       END) / NULLIF(V_YEAR_DAYS, 0), NULL), 0) AS CPTL_BAL_AVE_YR_OP  
+      , NVL( SUM(A3.DA_CPTL_BAL) / NULLIF(V_YEAR_DAYS, 0), NULL ) AS CPTL_BAL_AVE 
+   FROM tab1 A3;
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
        
-
        Stored Procedure
        
-
        Netezza Syntax
        
+
        DATE
        Casting the data type.
        
+
+
        
-
-
-
+
+
+
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE OR REPLACE PROCEDURE sp_ntz_proc_call 
-      ( CHARACTER VARYING(8) ) 
- RETURNS INTEGER 
- LANGUAGE NZPLSQL  
- AS 
- BEGIN_PROC  
- DECLARE 
-     V_PAR_DAY ALIAS for $1; 
-     V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
-     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
-     O_RETURN INTEGER; 
- BEGIN 
-   O_RETURN := 0; 
-   CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0); 
-  
-   RETURN O_RETURN; 
-  
- END; 
- END_PROC;
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        SELECT A1.ETL_DATE, A1.MARKET_CODE 
+      , A1.DECLARATION_DT 
+      , ROW_NUMBER() OVER(PARTITION BY A1.MARKET_CODE, A1.STOCK_CODE, DATE_PART('YEAR', DATE(A1.DECLARATION_DT)) ORDER BY A1.DECLARATION_DT DESC) AS RN 
+   FROM tb_date_type_casting A1; 
+  
+  
+ SELECT A1.ETL_DATE, A1.MARKET_CODE 
+      , A1.DECLARATION_DT 
+      , ROW_NUMBER() OVER(PARTITION BY A1.MARKET_CODE, A1.STOCK_CODE, DATE_PART('YEAR', DATE(A1.DECLARATION_DT)) ORDER BY A1.DECLARATION_DT DESC) AS RN 
+   FROM tb_date_type_casting A1;
+
        
+
+
        
 
        CREATE OR REPLACE FUNCTION sp_ntz_proc_call 
-      ( CHARACTER VARYING(8) ) 
- RETURN INTEGER 
- AS 
-     V_PAR_DAY ALIAS for $1; 
-     V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
-     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
-     O_RETURN INTEGER; 
- BEGIN 
-   O_RETURN := 0; 
-   SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0); 
-  
-   RETURN O_RETURN; 
-  
- END; 
- /
        
+
        1
+2
+3
+4
        SELECT A1.ETL_DATE, A1.MARKET_CODE 
+      , A1.DECLARATION_DT 
+      , ROW_NUMBER() OVER(PARTITION BY A1.MARKET_CODE, A1.STOCK_CODE, DATE_PART('YEAR', CAST(A1.DECLARATION_DT AS DATE)) ORDER BY A1.DECLARATION_DT DESC) AS RN 
+   FROM tb_date_type_casting A1;
+
        
+
+
        
+
        
+
        
+
        
+
        analytic_function
        
+
        
+
+
+
+
+
+
+
+
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
        SELECT COALESCE(NULLIF(GROUP_CONCAT(a.column_name),''),'*') 
+   FROM (SELECT a.column_name 
+           FROM tb_ntz_group_concat a 
+          WHERE UPPER(a.table_name) = 'EMP' 
+          ORDER BY a.column_pos) a; 
+ ------------- 
+ SELECT admin.group_concat('"top'||lpad(a.table_name,2,'0')||'":{'||a.column_name||'}') topofund_data 
+   FROM (SELECT a.table_name, a.column_name 
+           FROM tb_ntz_group_concat a 
+          WHERE UPPER(a.table_name) = 'EMP' 
+          ORDER BY a.column_pos) a;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
        SELECT COALESCE(NULLIF(STRING_AGG(a.column_name, ','),''),'*') 
+   FROM (SELECT a.column_name 
+           FROM tb_ntz_group_concat a 
+          WHERE UPPER(a.table_name) = 'EMP' 
+          ORDER BY a.column_pos) a; 
+ ------------- 
+ SELECT STRING_AGG('"top'||lpad(a.table_name,3,'0')||'":{'||a.column_name||'}', ',') topofund_data 
+   FROM (SELECT a.table_name, a.column_name 
+           FROM tb_ntz_group_concat a 
+          WHERE UPPER(a.table_name) = 'EMP' 
+          ORDER BY a.column_pos) a;
+
        
+
+
        
+
        
+
        
+
        
+
        Stored Procedure
        
+
        
+
+
+
+
+
diff --git a/docs/dws/tool/dws_07_6825.html b/docs/dws/tool/dws_07_6825.html
index ae9a8020..16a85ad9 100644
--- a/docs/dws/tool/dws_07_6825.html
+++ b/docs/dws/tool/dws_07_6825.html
@@ -1,32 +1,44 @@
-
+
        Operator
        
-
        **
        
-
        Netezza Syntax
        
+
        Syntax After Migration
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
        CREATE OR REPLACE PROCEDURE sp_ntz_proc_call 
+      ( CHARACTER VARYING(8) ) 
+ RETURNS INTEGER 
+ LANGUAGE NZPLSQL  
+ AS 
+ BEGIN_PROC  
+ DECLARE 
+     V_PAR_DAY ALIAS for $1; 
+     V_PRCNAME    NVARCHAR(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
+     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
+     O_RETURN INTEGER; 
+ BEGIN 
+   O_RETURN := 0; 
+   CALL SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0); 
+  
+   RETURN O_RETURN; 
+  
+ END; 
+ END_PROC;
+
        
+
+
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
        CREATE OR REPLACE FUNCTION sp_ntz_proc_call 
+      ( CHARACTER VARYING(8) ) 
+ RETURN INTEGER 
+ AS 
+     V_PAR_DAY ALIAS for $1; 
+     V_PRCNAME    NCHAR VARYING(50):= 'SP_O_HXYW_LNSACCTINFO_H'; 
+     D_TIME_START TIMESTAMP:= CURRENT_TIMESTAMP; 
+     O_RETURN INTEGER; 
+ BEGIN 
+   O_RETURN := 0; 
+   SP_LOG_EXEC(V_PRCNAME,V_PAR_DAY,D_TIME_START,0,0); 
+  
+   RETURN O_RETURN; 
+  
+ END; 
+ /
+
        
+
+
        
         		
 
        
         
 
 
        Netezza Syntax
        
+
        **
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        V_Out := V_Out + v_J * ( v_N ** v_K ) ;
        
+
        1
        V_Out := V_Out + v_J * ( v_N ** v_K ) ;
+
        
+
+
        
 
        V_Out := V_Out + v_J * ( v_N ^ v_K ) ;
        
+
        1
        V_Out := V_Out + v_J * ( v_N ^ v_K ) ;
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
        
-
        NOTNULL and ISNULL
        
-
        Netezza Syntax
        
+
        NOTNULL and ISNULL
        
+
        
-
-
-
diff --git a/docs/dws/tool/dws_07_6826.html b/docs/dws/tool/dws_07_6826.html
index cd05e739..280e3973 100644
--- a/docs/dws/tool/dws_07_6826.html
+++ b/docs/dws/tool/dws_07_6826.html
@@ -1,93 +1,139 @@
-
+
        DML
        
-
        Gauss keyword: SOURCE specified as column-alias without AS keyword
        
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CASE WHEN ((A1.EXCEPT_OFF_SEQU_NO NOTNULL) AND (A2.LOG_SEQU_NO ISNULL)) THEN 0 ELSE 1 END AS FLG
        
+
        1
        CASE WHEN ((A1.EXCEPT_OFF_SEQU_NO NOTNULL) AND (A2.LOG_SEQU_NO ISNULL)) THEN 0 ELSE 1 END AS FLG
+
        
+
+
        
 
        CASE WHEN ((A1.EXCEPT_OFF_SEQU_NO NOTNULL) AND (A2.LOG_SEQU_NO ISNULL)) THEN 0 ELSE 1 END AS FLG
        
+
        1
        CASE WHEN ((A1.EXCEPT_OFF_SEQU_NO NOTNULL) AND (A2.LOG_SEQU_NO ISNULL)) THEN 0 ELSE 1 END AS FLG
+
        
+
+
        
         		
 
        
         
 
 
        Netezza Syntax
        
+
        Gauss keyword: SOURCE specified as column-alias without AS keyword
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        SELECT SUBSTR( OP_SOURCE ,1 ,4 ) SOURCE
-     , ONLINE_FLAG, 'TRD' AS SRC_SYS
-     , CURRENT_TIMESTAMP AS ETL_LOAD_TIME
-  FROM tb_keyword_source;
        
+
        1
+2
+3
+4
        SELECT SUBSTR( OP_SOURCE ,1 ,4 ) SOURCE
+     , ONLINE_FLAG, 'TRD' AS SRC_SYS
+     , CURRENT_TIMESTAMP AS ETL_LOAD_TIME
+  FROM tb_keyword_source;
+
        
+
+
        
 
        SELECT SUBSTR( OP_SOURCE ,1 ,4 ) AS SOURCE
-     , ONLINE_FLAG, 'TRD' AS SRC_SYS
-     , CURRENT_TIMESTAMP AS ETL_LOAD_TIME
-  FROM tb_keyword_source;
        
+
        1
+2
+3
+4
        SELECT SUBSTR( OP_SOURCE ,1 ,4 ) AS SOURCE
+     , ONLINE_FLAG, 'TRD' AS SRC_SYS
+     , CURRENT_TIMESTAMP AS ETL_LOAD_TIME
+  FROM tb_keyword_source;
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
        
-
        FREEZE
        
-
        Netezza Syntax
        
+
        FREEZE
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        INSERT INTO tmp_tb_keyword_freeze 
-     ( BRANCH_CODE, FREEZE, UNFREEZE, BRAN_JYSDM )
-SELECT BRANCH_CODE, FREEZE, UNFREEZE, BRAN_JYSDM
-  FROM tb_keyword_freeze;
        
+
        1
+2
+3
+4
        INSERT INTO tmp_tb_keyword_freeze 
+     ( BRANCH_CODE, FREEZE, UNFREEZE, BRAN_JYSDM )
+SELECT BRANCH_CODE, FREEZE, UNFREEZE, BRAN_JYSDM
+  FROM tb_keyword_freeze;
+
        
+
+
        
 
        INSERT INTO tmp_tb_keyword_freeze 
-     ( BRANCH_CODE, "FREEZE", UNFREEZE, BRAN_JYSDM )
-SELECT BRANCH_CODE, "FREEZE", UNFREEZE, BRAN_JYSDM
-  FROM tb_keyword_freeze;
        
+
        1
+2
+3
+4
        INSERT INTO tmp_tb_keyword_freeze 
+     ( BRANCH_CODE, "FREEZE", UNFREEZE, BRAN_JYSDM )
+SELECT BRANCH_CODE, "FREEZE", UNFREEZE, BRAN_JYSDM
+  FROM tb_keyword_freeze;
+
        
+
+
        
         		
 
        
         
 
        
 
        
-
         
        A new configuration parameter "keywords_addressed_using_doublequote" should be introduced with the below value:
        
-
        keywords_addressed_using_doublequote=freeze
        
-
        keywords_addressed_using_as=owner,attribute,source,freeze
        
-
        create table t12 (c1 int, FREEZE varchar(10));  ==> create table t12 (c1 int, "freeze" varchar(10));
        
-
        select c1, Freeze from t12; ==> select c1, "freeze" from t12;
        
-
        select c1 freeze from t12; ==> select c1 as freeze from t12;
        
+
         
        A new configuration parameter "keywords_addressed_using_doublequote" should be introduced with the below value:
        
+
        keywords_addressed_using_doublequote=freeze
        
+
        keywords_addressed_using_as=owner,attribute,source,freeze
        
+
        create table t12 (c1 int, FREEZE varchar(10));  ==> create table t12 (c1 int, "freeze" varchar(10));
        
+
        select c1, Freeze from t12; ==> select c1, "freeze" from t12;
        
+
        select c1 freeze from t12; ==> select c1 as freeze from t12;
        
 
        
 
        
-
        OWNER (AS should be specified)
        
-
        Netezza Syntax
        
+
        OWNER (AS should be specified)
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        SELECT username owner
-  FROM tb_ntz_keyword_owner;
        
+
        1
+2
        SELECT username owner
+  FROM tb_ntz_keyword_owner;
+
        
+
+
        
 
        SELECT username AS owner
-  FROM tb_ntz_keyword_owner;
        
+
        1
+2
        SELECT username AS owner
+  FROM tb_ntz_keyword_owner;
+
        
+
+
        
         		
 
        
         
 
        
 
        
 
        
-
        ATTRIBUTE (AS should be specified)
        
-
        Netezza Syntax
        
+
        ATTRIBUTE (AS should be specified)
        
+
        
-
-
-
diff --git a/docs/dws/tool/dws_07_6827.html b/docs/dws/tool/dws_07_6827.html
index dbb6c2a3..8c676b16 100644
--- a/docs/dws/tool/dws_07_6827.html
+++ b/docs/dws/tool/dws_07_6827.html
@@ -1,129 +1,240 @@
-
+
 
-
        Index Migration
        
-
        Unique Index
        
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        SELECT t1.etl_date, substr(t1.attribute,1,1) attribute
-     , t1.cust_no, t1.branch_code
-  FROM ( SELECT etl_date,attribute,cust_no,branch_code
-           FROM tb_ntz_keyword_attribute
-          WHERE etl_date = CURRENT_DATE ) t1;
        
+
        1
+2
+3
+4
+5
        SELECT t1.etl_date, substr(t1.attribute,1,1) attribute
+     , t1.cust_no, t1.branch_code
+  FROM ( SELECT etl_date,attribute,cust_no,branch_code
+           FROM tb_ntz_keyword_attribute
+          WHERE etl_date = CURRENT_DATE ) t1;
+
        
+
+
        
 
        SELECT t1.etl_date, substr(t1.attribute,1,1) AS attribute
-     , t1.cust_no, t1.branch_code
-  FROM ( SELECT etl_date,attribute,cust_no,branch_code
-           FROM tb_ntz_keyword_attribute
-          WHERE etl_date = CURRENT_DATE ) t1;
        
+
        1
+2
+3
+4
+5
        SELECT t1.etl_date, substr(t1.attribute,1,1) AS attribute
+     , t1.cust_no, t1.branch_code
+  FROM ( SELECT etl_date,attribute,cust_no,branch_code
+           FROM tb_ntz_keyword_attribute
+          WHERE etl_date = CURRENT_DATE ) t1;
+
        
+
+
        
         		
 
        
 
        Netezza Syntax
        
+
        Unique Index
        
+
        Unique Index
        
+
        
-
-
-
        Netezza Syntax
        
 
        Syntax After Migration
        
+
        Syntax After Migration
        
         		
 
        
 
        CREATE TABLE  prod
-(
-     prod_no              number(6)      not null    unique,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-)
-DISTRIBUTE ON (prod_no)
-ORGANIZE   ON (prod_no, prod_name)
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null     
-     CONSTRAINT UQ_prod unique,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-)
-DISTRIBUTE ON (prod_no)
-ORGANIZE   ON (prod_no, prod_name)
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null    PRIMARY KEY,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-)
-DISTRIBUTE ON (prod_no)
-ORGANIZE   ON (prod_no, prod_name)
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob,
-     constraint          uq_prod    UNIQUE (prod_no)
-)
-DISTRIBUTE ON (prod_no)
-ORGANIZE   ON (prod_no, prod_name)
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-)
-DISTRIBUTE ON (prod_no)
-ORGANIZE   ON (prod_no, prod_name)
-;
-ALTER TABLE prod
-    ADD constraint          uq_prod    UNIQUE (prod_no);
-
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
+35
+36
+37
+38
+39
+40
+41
+42
+43
+44
+45
+46
+47
+48
+49
+50
+51
+52
+53
        CREATE TABLE  prod
+(
+     prod_no              number(6)      not null    unique,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+)
+DISTRIBUTE ON (prod_no)
+ORGANIZE   ON (prod_no, prod_name)
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null     
+     CONSTRAINT UQ_prod unique,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+)
+DISTRIBUTE ON (prod_no)
+ORGANIZE   ON (prod_no, prod_name)
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null    PRIMARY KEY,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+)
+DISTRIBUTE ON (prod_no)
+ORGANIZE   ON (prod_no, prod_name)
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob,
+     constraint          uq_prod    UNIQUE (prod_no)
+)
+DISTRIBUTE ON (prod_no)
+ORGANIZE   ON (prod_no, prod_name)
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+)
+DISTRIBUTE ON (prod_no)
+ORGANIZE   ON (prod_no, prod_name)
+;
+ALTER TABLE prod
+    ADD constraint          uq_prod    UNIQUE (prod_no);
+
        
+
+
        
 
        CREATE TABLE  prod
-(
-     prod_no              number(6)      not null   /* unique */,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-) WITH(ORIENTATION=COLUMN)
-DISTRIBUTE BY HASH (prod_no)
-/* ORGANIZE   ON (prod_no, prod_name) */
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null   
-  /* CONSTRAINT UQ_prod unique */,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-) WITH(ORIENTATION=COLUMN)
-DISTRIBUTE BY HASH (prod_no)
-/* ORGANIZE   ON (prod_no, prod_name) */
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null   /* PRIMARY KEY */,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-) WITH(ORIENTATION=COLUMN)
-DISTRIBUTE BY HASH (prod_no)
-/* ORGANIZE   ON (prod_no, prod_name) */
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob  /*,
-    constraint          uq_prod    UNIQUE (prod_no)  */
-) WITH(ORIENTATION=COLUMN)
-DISTRIBUTE BY HASH (prod_no)
-/* ORGANIZE   ON (prod_no, prod_name)*/
-;
-----------
-CREATE TABLE  prod
-(
-     prod_no              number(6)      not null,
-     prod_name         national character varying(32)      not null,
-     prod_desc          clob
-)
-DISTRIBUTE BY HASH (prod_no)
-/*ORGANIZE   ON (prod_no, prod_name)*/
-;
-/*
-ALTER TABLE prod
-    ADD constraint          uq_prod    UNIQUE (prod_no);
-*/
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
+35
+36
+37
+38
+39
+40
+41
+42
+43
+44
+45
+46
+47
+48
+49
+50
+51
+52
+53
+54
+55
        CREATE TABLE  prod
+(
+     prod_no              number(6)      not null   /* unique */,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+) WITH(ORIENTATION=COLUMN)
+DISTRIBUTE BY HASH (prod_no)
+/* ORGANIZE   ON (prod_no, prod_name) */
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null   
+  /* CONSTRAINT UQ_prod unique */,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+) WITH(ORIENTATION=COLUMN)
+DISTRIBUTE BY HASH (prod_no)
+/* ORGANIZE   ON (prod_no, prod_name) */
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null   /* PRIMARY KEY */,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+) WITH(ORIENTATION=COLUMN)
+DISTRIBUTE BY HASH (prod_no)
+/* ORGANIZE   ON (prod_no, prod_name) */
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob  /*,
+    constraint          uq_prod    UNIQUE (prod_no)  */
+) WITH(ORIENTATION=COLUMN)
+DISTRIBUTE BY HASH (prod_no)
+/* ORGANIZE   ON (prod_no, prod_name)*/
+;
+----------
+CREATE TABLE  prod
+(
+     prod_no              number(6)      not null,
+     prod_name         national character varying(32)      not null,
+     prod_desc          clob
+)
+DISTRIBUTE BY HASH (prod_no)
+/*ORGANIZE   ON (prod_no, prod_name)*/
+;
+/*
+ALTER TABLE prod
+    ADD constraint          uq_prod    UNIQUE (prod_no);
+*/
+
        
+
+
        
         		
 
        
         
 
        
 
        
-
         
        This feature is applicable only for COLUMN store. For ROW store, Unique Index should not be commented.
        
+
         
        This feature is applicable only for COLUMN store. For ROW store, Unique Index should not be commented.
        
 
        
 
        
 
        
diff --git a/docs/dws/tool/dws_07_6831.html b/docs/dws/tool/dws_07_6831.html
deleted file mode 100644
index 3243c8b7..00000000
--- a/docs/dws/tool/dws_07_6831.html
+++ /dev/null
@@ -1,757 +0,0 @@
-
-
-
        Basic Data Types
        
-
        Overview
        MySQL supports a number of basic data types, including numeric, date/time, string (character), LOB, set, binary, and Boolean types. GaussDB(DWS) does not support some basic MySQL data types, precision settings of some MySQL data types, or some MySQL keywords such as UNSIGNED and ZEROFILL. DSC performs migration based on GaussDB support.
        
-
        A data type is a basic data attribute. Occupied storage space and allowed operations vary according to data types. In a database, data is stored in tables, in which a data type is specified for each column. Data in the column must be of its allowed data type. For details of each types description, see Table 1
        
-
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 1 Basic description of data types
        Data Types
        
-
        Basic Description
        
-
        Numeric Types
        
-
        For details, see Numeric Types.
        
-
        Date/Time Types
        
-
        This document describes the following date/time types: DATETIME, TIME, TIMESTAMP, and YEAR. GaussDB(DWS) does not support these types, and DSC will convert them. For details, see Date/Time Types.
        
-
        String Types
        
-
        MySQL interprets length specifications in character column definitions in character units. This applies to the CHAR, VARCHAR, and TEXT types. For details, see String Types.
        
-
        Spatial Data Types
        
-
        MySQL has spatial data types corresponding to the OpenGIS class. For details, see Spatial Data Types.
        
-
        LOB Types
        
-
        A BLOB is a binary large object that can hold a variable amount of data. The four BLOB types are TINYBLOB, BLOB, MEDIUMBLOB, and LONGBLOB. The only difference between these four types is the maximum length of the values they can contain. For details, see LOB Types.
        
-
        Set Types
        
-
        1. In MySQL, an ENUM is a string object with a value chosen from a list of permitted values that are enumerated explicitly in the column specification at table creation.
        2. A SET is a string object that can have zero or more values, each of which must be chosen from a list of permitted values specified when the table is created.
          For details, see Set Types.
          
-
        
-
        Boolean Types
        
-
        MySQL supports both BOOL and BOOLEAN. For details, see Boolean Types.
        
-
        Binary Types
        
-
        1. In MySQL, the BIT data type is used to store bit values. A type of BIT(M) enables storage of M-bit values. M can range from 1 to 64.
        2. MySQL BINARY and VARBINARY types are similar to CHAR and VARCHAR, except that they contain binary strings rather than non-binary strings.
          For details, see Binary Types.
          
-
        
-
        
-
        
-
        
-
        Numeric Types
        
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 2 Numeric type mapping
        MySQL Numeric Type
        
-
        MySQL Input
        
-
        GaussDB(DWS) Output
        
-
        DEC
        
-
        DEC
        
-
        DEC[(M[,D])] [UNSIGNED] [ZEROFILL]
        
-
        DECIMAL
        
-
        DECIMAL[(M[,D])]
        
-
        DECIMAL
        
-
        DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL]
        
-
        DECIMAL[(M[,D])]
        
-
        DOUBLE PRECISION
        
-
        DOUBLE PRECISION
        
-
        DOUBLE PRECISION [(M[,D])] [UNSIGNED] [ZEROFILL]
        
-
        FLOAT
        
-
        FLOAT[(M)]
        
-
        DOUBLE
        
-
        DOUBLE[(M[,D])] [UNSIGNED] [ZEROFILL]
        
-
        FLOAT[(M)]
        
-
        FIXED
        
-
        FIXED
        
-
        FIXED[(M[,D])] [UNSIGNED] [ZEROFILL]
        
-
        DECIMAL
        
-
        DECIMAL[(M[,D])]
        
-
        FLOAT
        
-
        FLOAT
        
-
        FLOAT [(M[,D])] [UNSIGNED] [ZEROFILL]
        
-
        FLOAT(p) [UNSIGNED] [ZEROFILL]
        
-
        FLOAT
        
-
        FLOAT[(M)]
        
-
        FLOAT(p)
        
-
        INT
        
-
        INT
        
-
        INT(p) [UNSIGNED] [ZEROFILL]
        
-
        INTEGER
        
-
        INTEGER(p)
        
-
        INTEGER
        
-
        INTEGER
        
-
        INTEGER(p) [UNSIGNED] [ZEROFILL]
        
-
        INTEGER
        
-
        INTEGER(p)
        
-
        MEDIUMINT
        
-
        MEDIUMINT
        
-
        MEDIUMINT(p) [UNSIGNED] [ZEROFILL]
        
-
        INTEGER
        
-
        INTEGER(p)
        
-
        NUMERIC
        
-
        NUMERIC
        
-
        NUMERIC [(M[,D])] [UNSIGNED] [ZEROFILL]
        
-
        DECIMAL
        
-
        DECIMAL[(M[,D])]
        
-
        REAL
        
-
        REAL[(M[,D])]
        
-
        FLOAT[(M)]
        
-
        SMALLINT
        
-
        SMALLINT
        
-
        SMALLINT(p) [UNSIGNED] [ZEROFILL]
        
-
        SMALLINT
        
-
        TINYINT
        
-
        TINYINT
        
-
        TINYINT(n)
        
-
        TINYINT(n) ZEROFILL
        
-
        TINYINT(n) UNSIGNED ZEROFILL
        
-
        TINYINT
        
-
        TINYINT
        
-
        TINYINT
        
-
        SMALLINT
        
-
        
-
        
-
        Input: TINYINT
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` TINYINT,
-    `dataType_2` TINYINT(0),
-    `dataType_3` TINYINT(255),
-    `dataType_4` TINYINT(255) UNSIGNED ZEROFILL,
-    `dataType_5` TINYINT(255) ZEROFILL
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" TINYINT,
-  "datatype_2" TINYINT,
-  "datatype_3" TINYINT,
-  "datatype_4" SMALLINT,
-  "datatype_5" TINYINT
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        
-
        Date/Time Types
        
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 3 Date/Time type mapping
        MySQL Date/Time Type
        
-
        MySQL Input
        
-
        GaussDB(DWS) Output
        
-
        DATETIME
        
-
        DATETIME[(fsp)]
        
-
        TIMESTAMP[(fsp)] WITHOUT TIME ZONE
        
-
        TIME
        
-
        TIME[(fsp)]
        
-
        TIME[(fsp)] WITHOUT TIME ZONE
        
-
        TIMESTAMP
        
-
        TIMESTAMP[(fsp)]
        
-
        TIMESTAMP[(fsp)] WITH TIME ZONE
        
-
        YEAR
        
-
        YEAR[(4)]
        
-
        VARCHAR(4)
        
-
        
-
        
-
         
        The value of fsp must be in the range [0, 6]. Value 0 indicates no decimal. If this parameter is omitted, the default precision will be 0.
        
-
        
-
        Input: DATETIME
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` DATETIME,
-    `dataType_2` DATETIME(0),
-    `dataType_3` DATETIME(6),
-    `dataType_4` DATETIME DEFAULT NULL,
-    `dataType_5` DATETIME DEFAULT '2018-10-12 15:27:33.999999'
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" TIMESTAMP WITHOUT TIME ZONE,
-  "datatype_2" TIMESTAMP(0) WITHOUT TIME ZONE,
-  "datatype_3" TIMESTAMP(6) WITHOUT TIME ZONE,
-  "datatype_4" TIMESTAMP WITHOUT TIME ZONE DEFAULT NULL,
-  "datatype_5" TIMESTAMP WITHOUT TIME ZONE DEFAULT '2018-10-12 15:27:33.999999'
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        Input: TIME
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` TIME DEFAULT '20:58:10',
-    `dataType_2` TIME(3) DEFAULT '20:58:10',
-    `dataType_3` TIME(6) DEFAULT '20:58:10',
-    `dataType_4` TIME(6) DEFAULT '2018-10-11 20:00:00',
-    `dataType_5` TIME(6) DEFAULT '20:58:10.01234',
-    `dataType_6` TIME(6) DEFAULT '2018-10-11 20:00:00.01234',
-    `dataType_7` TIME DEFAULT NULL,
-    `dataType_8` TIME(6) DEFAULT NULL,
-    PRIMARY KEY (dataType_1)
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" TIME WITHOUT TIME ZONE DEFAULT '20:58:10',
-  "datatype_2" TIME(3) WITHOUT TIME ZONE DEFAULT '20:58:10',
-  "datatype_3" TIME(6) WITHOUT TIME ZONE DEFAULT '20:58:10',
-  "datatype_4" TIME(6) WITHOUT TIME ZONE DEFAULT '2018-10-11 20:00:00',
-  "datatype_5" TIME(6) WITHOUT TIME ZONE DEFAULT '20:58:10.01234',
-  "datatype_6" TIME(6) WITHOUT TIME ZONE DEFAULT '2018-10-11 20:00:00.01234',
-  "datatype_7" TIME WITHOUT TIME ZONE DEFAULT NULL,
-  "datatype_8" TIME(6) WITHOUT TIME ZONE DEFAULT NULL,
-  PRIMARY KEY ("datatype_1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        Input: TIMESTAMP
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-   `dataType_1` TIMESTAMP,
-   `dateType_4` TIMESTAMP DEFAULT '2018-10-12 15:27:33',
-   `dateType_5` TIMESTAMP DEFAULT '2018-10-12 15:27:33.999999',
-   `dateType_6` TIMESTAMP DEFAULT '2018-10-12 15:27:33',
-   `dateType_7` TIMESTAMP DEFAULT '2018-10-12 15:27:33',
-   `dataType_8` TIMESTAMP(0) DEFAULT '2018-10-12 15:27:33',
-   `dateType_9` TIMESTAMP(6) DEFAULT '2018-10-12 15:27:33'
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" TIMESTAMP WITH TIME ZONE,
-  "datetype_4" TIMESTAMP WITH TIME ZONE DEFAULT '2018-10-12 15:27:33',
-  "datetype_5" TIMESTAMP WITH TIME ZONE DEFAULT '2018-10-12 15:27:33.999999',
-  "datetype_6" TIMESTAMP WITH TIME ZONE DEFAULT '2018-10-12 15:27:33',
-  "datetype_7" TIMESTAMP WITH TIME ZONE DEFAULT '2018-10-12 15:27:33',
-  "datatype_8" TIMESTAMP(0) WITH TIME ZONE DEFAULT '2018-10-12 15:27:33',
-  "datetype_9" TIMESTAMP(6) WITH TIME ZONE DEFAULT '2018-10-12 15:27:33'
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        Input: YEAR
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` YEAR,
-    `dataType_2` YEAR(4),
-    `dataType_3` YEAR DEFAULT '2018',
-    `dataType_4` TIME DEFAULT NULL
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" VARCHAR(4),
-  "datatype_2" VARCHAR(4),
-  "datatype_3" VARCHAR(4) DEFAULT '2018',
-  "datatype_4" TIME WITHOUT TIME ZONE DEFAULT NULL 
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        
-
        String Types
        
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 4 String type mapping
        MySQL String Type
        
-
        MySQL Input
        
-
        GaussDB(DWS) Output
        
-
        CHAR
        
-
        CHAR[(0)]
        
-
        CHAR[(1)]
        
-
        LONGTEXT
        
-
        LONGTEXT
        
-
        TEXT
        
-
        MEDIUMTEXT
        
-
        MEDIUMTEXT
        
-
        TEXT
        
-
        TEXT
        
-
        TEXT
        
-
        TEXT
        
-
        TINYTEXT
        
-
        TINYTEXT
        
-
        TEXT
        
-
        VARCHAR
        
-
        VARCHAR[(0)]
        
-
        VARCHAR[(1)]
        
-
        
-
        
-
        Input: CHAR
        
-
        In MySQL, the length of a CHAR column is fixed to the length that you declare when you create the table. The length can be any value from 0 to 255. When CHAR values are stored, they are right-padded with spaces to the specified length.
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-   `dataType_1` CHAR NOT NULL,
-   `dataType_2` CHAR(0) NOT NULL,
-   `dataType_3` CHAR(255) NOT NULL
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" CHAR NOT NULL,
-  "datatype_2" CHAR(1) NOT NULL,
-  "datatype_3" CHAR(255) NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        Input: [LONG|MEDIUM|TINY]TEXT
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` LONGTEXT,
-    `dataType_2` MEDIUMTEXT,
-    `dataType_3` TEXT,
-    `dataType_4` TINYTEXT
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" TEXT,
-  "datatype_2" TEXT,
-  "datatype_3" TEXT,
-  "datatype_4" TEXT
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        Input: VARCHAR
        
-
        In MySQL, values in VARCHAR columns are variable-length strings. The length can be any value from 0 to 65,535.
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` VARCHAR(0),
-    `dataType_2` VARCHAR(1845)
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" VARCHAR(1),
-  "datatype_2" VARCHAR(1845)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        
-
        Spatial Data Types
        
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 5 Spatial type mapping
        MySQL Spatial Type
        
-
        MySQL Input
        
-
        GaussDB(DWS) Output
        
-
        GEOMETRY
        
-
        GEOMETRY
        
-
        CIRCLE
        
-
        POINT
        
-
        POINT
        
-
        POINT
        
-
        LINESTRING
        
-
        LINESTRING
        
-
        POLYGON
        
-
        POLYGON
        
-
        POLYGON
        
-
        POLYGON
        
-
        MULTIPOINT
        
-
        MULTIPOINT
        
-
        BOX
        
-
        MULTILINESTRING
        
-
        MULTILINESTRING
        
-
        BOX
        
-
        MULTIPOLYGON
        
-
        MULTIPOLYGON
        
-
        POLYGON
        
-
        GEOMETRYCOLLECTION
        
-
        GEOMETRYCOLLECTION
        
-
        CIRCLE
        
-
        
-
        
-
        • GEOMETRY can store geometry values of any type. The other single-value types (POINT, LINESTRING, and POLYGON) restrict their values to a particular geometry type.
        • GEOMETRYCOLLECTION can store a collection of objects of any type. The other collection types (MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, and GEOMETRYCOLLECTION) restrict collection members to those having a particular geometry type.
          Input
          
-
          CREATE TABLE `t_geo_test2`  (
-  `id` int(11) NOT NULL,
-  `name` varchar(255),
-  `geometry_1` geometry NOT NULL,
-  `point_1` point NOT NULL,
-  `linestring_1` linestring NOT NULL,
-  `polygon_1` polygon NOT NULL,
-  `multipoint_1` multipoint NOT NULL,
-  `multilinestring_1` multilinestring NOT NULL,
-  `multipolygon_1` multipolygon NOT NULL,
-  `geometrycollection_1` geometrycollection NOT NULL,
-  PRIMARY KEY (`id`) USING BTREE
-) ENGINE = InnoDB;
          
-
          Output
          
-
          CREATE TABLE "public"."t_geo_test2"
-(
-  "id" INTEGER(11) NOT NULL,
-  "name" VARCHAR(255),
-  "geometry_1" CIRCLE NOT NULL,
-  "point_1" POINT NOT NULL,
-  "linestring_1" POLYGON NOT NULL,
-  "polygon_1" POLYGON NOT NULL,
-  "multipoint_1" BOX NOT NULL,
-  "multilinestring_1" BOX NOT NULL,
-  "multipolygon_1" POLYGON NOT NULL,
-  "geometrycollection_1" CIRCLE NOT NULL,
-  PRIMARY KEY ("id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
          
-
        
-
        
-
        LOB Types
        
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 6 LOB type mapping
        MySQL LOB Type
        
-
        MySQL Input
        
-
        GaussDB(DWS) Output
        
-
        TINYBLOB
        
-
        TINYBLOB
        
-
        BLOB
        
-
        BLOB
        
-
        BLOB
        
-
        BLOB
        
-
        MEDIUMBLOB
        
-
        MEDIUMBLOB
        
-
        BLOB
        
-
        LONGBLOB
        
-
        LONGBLOB
        
-
        BLOB
        
-
        
-
        
-
        Input: [TINY|MEDIUM|LONG]BLOB
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` BIGINT,
-    `dataType_2` TINYBLOB,
-    `dataType_3` BLOB,
-    `dataType_4` MEDIUMBLOB,
-    `dataType_5` LONGBLOB
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" BIGINT,
-  "datatype_2" BLOB,
-  "datatype_3" BLOB,
-  "datatype_4" BLOB,
-  "datatype_5" BLOB
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        
-
        Set Types
        
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 7 Set type mapping
        MySQL Set Type
        
-
        MySQL Input
        
-
        GaussDB(DWS) Output
        
-
        ENUM
        
-
        ENUM
        
-
        VARCHAR(14)
        
-
        SET
        
-
        SET
        
-
        VARCHAR(14)
        
-
        
-
        
-
        Input: ENUM
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-     id   int(2) PRIMARY KEY,
-    `dataType_17` ENUM('dws-1', 'dws-2', 'dws-3')
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "id" INTEGER(2) PRIMARY KEY,
-  "datatype_17" VARCHAR(14)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
        
-
        Input: SET
        
-
        CREATE TABLE IF NOT EXISTS `runoob_tbl_test`(
-    `dataType_18` SET('dws-1', 'dws-2', 'dws-3')
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_test"
-(
-  "datatype_18" VARCHAR(14)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_18");
        
-
        
-
        Boolean Types
        Input: BOOL/BOOLEAN
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` INT,
-    `dataType_2` BOOL,
-    `dataType_3` BOOLEAN
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" INTEGER,
-  "datatype_2" BOOLEAN,
-  "datatype_3" BOOLEAN
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        
-
        Binary Types
        
-
        
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
        Table 8 Binary type mapping
        MySQL Binary Type
        
-
        MySQL Input
        
-
        GaussDB(DWS) Output
        
-
        BIT[(M)]
        
-
        BIT[(M)]
        
-
        BIT[(M)]
        
-
        BINARY[(M)]
        
-
        BINARY[(M)]
        
-
        BYTEA
        
-
        VARBINARY[(M)]
        
-
        VARBINARY[(M)]
        
-
        BYTEA
        
-
        
-
        
-
        Input: BIT
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` INT,
-    `dataType_2` BIT(1),
-    `dataType_3` BIT(64)
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" INTEGER,
-  "datatype_2" BIT(1),
-  "datatype_3" BIT(64)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        Input: [VAR]BINARY
        
-
        CREATE TABLE IF NOT EXISTS `runoob_dataType_test`(
-    `dataType_1` INT,
-    `dataType_2` BINARY,
-    `dataType_3` BINARY(0),
-    `dataType_4` BINARY(255),
-    `dataType_5` VARBINARY(0),
-    `dataType_6` VARBINARY(6553)
-);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_datatype_test"
-(
-  "datatype_1" INTEGER,
-  "datatype_2" BYTEA,
-  "datatype_3" BYTEA,
-  "datatype_4" BYTEA,
-  "datatype_5" BYTEA,
-  "datatype_6" BYTEA
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
        
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6832.html b/docs/dws/tool/dws_07_6832.html
deleted file mode 100644
index 024d5ca7..00000000
--- a/docs/dws/tool/dws_07_6832.html
+++ /dev/null
@@ -1,644 +0,0 @@
-
-
-
        Table (Optional)
        
-
        This section describes the migration syntax of MySQL tables (optional parameter). The migration syntax determines how the keywords and features are migrated. GaussDB(DWS) does not support table migration. Currently, all table migration methods are temporary.
        
-
        AUTO_INCREMENT
        In database application, unique numbers that increase automatically are needed to identify records. In MySQL, the AUTO_INCREMENT attribute of a data column can be used to automatically generate the numbers. When creating a table, you can use AUTO_INCREMENT=n to specify a start value. You can also use the ALTER TABLE TABLE_NAME AUTO_INCREMENT=n command to reset the start value. GaussDB(DWS) does not support this attribute, which will be converted to SERIAL and deleted by DSC during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`job_instance` (
-  `job_sche_id` int(11) NOT NULL AUTO_INCREMENT,
-  `task_name` varchar(100) NOT NULL DEFAULT '',
-  PRIMARY KEY (`job_sche_id`)
-) ENGINE=InnoDB AUTO_INCREMENT=219 DEFAULT CHARSET=utf8;
        
-
        Output
        
-
        CREATE TABLE "public"."job_instance"
-(
-  "job_sche_id" SERIAL NOT NULL,
-  "task_name" VARCHAR(100) NOT NULL DEFAULT '',
-  PRIMARY KEY ("job_sche_id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("job_sche_id");
        
-
        In addition, GaussDB(DWS) does not support table definition modification using the AUTO_INCREMENT attribute. DSC will delete this attribute during migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    PRIMARY KEY(`dataType1`)
-);
-
-ALTER TABLE runoob_alter_test AUTO_INCREMENT 100;
-ALTER TABLE runoob_alter_test AUTO_INCREMENT=100;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        AVG_ROW_LENGTH
        Input
        
-
        CREATE TABLE `public`.`runoob_tbl_test`(
-    `runoob_id` VARCHAR(30),
-    `runoob_title` VARCHAR(100) NOT NULL,
-    `runoob_author` VARCHAR(40) NOT NULL,
-    `submission_date` VARCHAR(30)
-)AVG_ROW_LENGTH=10000;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_test"
-(
-  "runoob_id" VARCHAR(30),
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR(30)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
        
-
        In addition, GaussDB(DWS) does not allow using the AUTO_INCREMENT attribute to modify tables. DSC will delete the attribute after migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `public`.`runoob_alter_test`( 
-    `dataType1` int NOT NULL AUTO_INCREMENT, 
-    `dataType2` FLOAT(10,2), 
-    PRIMARY KEY(`dataType1`) 
-); 
- 
-ALTER TABLE runoob_alter_test AUTO_INCREMENT 100; 
-ALTER TABLE runoob_alter_test AUTO_INCREMENT=100;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test" 
-( 
-  "datatype1" SERIAL NOT NULL, 
-  "datatype2" FLOAT(10), 
-  PRIMARY KEY ("datatype1") 
-) 
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO ) 
-  NOCOMPRESS 
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        CHARSET
        CHARSET specifies the default character set for a table. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_tbl_test`(
-    `runoob_id` VARCHAR(30),
-    `runoob_title` VARCHAR(100) NOT NULL,
-    `runoob_author` VARCHAR(40) NOT NULL,
-    `submission_date` VARCHAR(30)
-)DEFAULT CHARSET=utf8;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_test"
-(
-  "runoob_id" VARCHAR(30),
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR(30)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
        
-
        
-
        CHECKSUM
        In MySQL, CHECKSUM maintains a live checksum for all rows. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    `dataType3` DOUBLE(20,8),
-    PRIMARY KEY(`dataType1`)
-) CHECKSUM=1;
-
-ALTER TABLE runoob_alter_test CHECKSUM 0;
-ALTER TABLE runoob_alter_test CHECKSUM=0;
-
-ALTER TABLE runoob_alter_test CHECKSUM 1;
-ALTER TABLE runoob_alter_test CHECKSUM=1;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  "datatype3" FLOAT(20),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        COLLATE
        In MySQL, COLLATE specifies a default database sorting rule. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the keyword during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_tbl_test`(
-    `runoob_id` VARCHAR(30),
-    `runoob_title` VARCHAR(100) NOT NULL,
-    `runoob_author` VARCHAR(40) NOT NULL,
-    `submission_date` VARCHAR(30)
-) COLLATE=utf8_general_ci;
-
-ALTER TABLE `public`.`runoob_tbl_test` COLLATE=utf8mb4_bin;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_test"
-(
-  "runoob_id" VARCHAR(30),
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR(30)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
        
-
        
-
        COMMENT
        In MySQL, COMMENT is a comment for a table. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the attribute during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    PRIMARY KEY(`dataType1`)
-) comment='table comment'; 
-
-ALTER TABLE `public`.`runoob_alter_test` COMMENT 'table comment after modification';
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        CONNECTION
        GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the attribute during migration.
        
-
         
        In MySQL, the keyword CONNECTION is used as a referenced, external data source. Currently, DSC cannot completely migrate the feature of CONNECTION. So as a workaround, it simply deletes the keyword.
        
-
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    `dataType4` YEAR NOT NULL DEFAULT '2018',
-    PRIMARY KEY(`dataType1`)
-);
-
-ALTER TABLE runoob_alter_test CONNECTION 'hello';
-ALTER TABLE runoob_alter_test CONNECTION='hello';
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  "datatype3" TEXT NOT NULL,
-  "datatype4" VARCHAR(4) NOT NULL DEFAULT '2018',
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        DELAY_KEY_WRITE
        DELAY_KEY_WRITE is valid only for MyISAM tables. It is used to delay updates until the table is closed. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the attribute during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_tbl_test`(
-    `runoob_id` VARCHAR(30),
-    `runoob_title` VARCHAR(100) NOT NULL,
-    `runoob_author` VARCHAR(40) NOT NULL,
-    `submission_date` VARCHAR(30)
-) ENGINE=MyISAM, DELAY_KEY_WRITE=0;
-
-ALTER TABLE `public`.`runoob_tbl_test6` DELAY_KEY_WRITE=1;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_test"
-(
-  "runoob_id" VARCHAR(30),
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR(30)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
        
-
        
-
        DIRECTORY
        DIRECTORY enables a tablespace to be created outside the data directory and index directory. It allows DATA DIRECTORY and INDEX DIRECTORY. GaussDB(DWS) does not support table definition modification using this attribute. DSC will delete the attribute during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_tbl_test1` (
-`dataType1` int NOT NULL AUTO_INCREMENT,    
-`dataType2` DOUBLE(20,8),       
-PRIMARY KEY(`dataType1`)
-) ENGINE=MYISAM DATA DIRECTORY = 'D:\\input' INDEX DIRECTORY= 'D:\\input';
-
-CREATE TABLE `public`.`runoob_tbl_test2` (
-`dataType1` int NOT NULL AUTO_INCREMENT,    
-`dataType2` DOUBLE(20,8),       
-PRIMARY KEY(`dataType1`)
-) ENGINE=INNODB DATA DIRECTORY = 'D:\\input';
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_test1"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
-CREATE TABLE "public"."runoob_tbl_test2"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        ENGINE
        In MySQL, ENGINE specifies the storage engine for a table. When the storage engine is ARCHIVE, BLACKHOLE, CSV, FEDERATED, INNODB, MYISAM, MEMORY, MRG_MYISAM, NDB, NDBCLUSTER, or PERFORMANCE_SCHEMA, this attribute can be migrated and will be deleted during the migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(    
-`dataType1` int NOT NULL,    
-`dataType2` DOUBLE(20,8),        
-PRIMARY KEY(`dataType1`)
-)ENGINE=MYISAM;
-
-## A.
-ALTER TABLE runoob_alter_test ENGINE INNODB;
-ALTER TABLE runoob_alter_test ENGINE=INNODB;
-
-## B.
-ALTER TABLE runoob_alter_test ENGINE MYISAM;
-ALTER TABLE runoob_alter_test ENGINE=MYISAM;
-
-## C.
-ALTER TABLE runoob_alter_test ENGINE MEMORY;
-ALTER TABLE runoob_alter_test ENGINE=MEMORY;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" INTEGER NOT NULL,
-  "datatype2" FLOAT(20),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
--- A.
-
--- B.
-
--- C.
        
-
        
-
        INSERT_METHOD
        INSERT_METHOD specifies the table into which the row should be inserted. Use a value of FIRST or LAST to have inserts go to the first or last table, or a value of NO to prevent inserts. DSC will delete this attribute during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-) INSERT_METHOD=LAST;
-
-ALTER TABLE runoob_alter_test INSERT_METHOD NO;
-ALTER TABLE runoob_alter_test INSERT_METHOD=NO;
-ALTER TABLE runoob_alter_test INSERT_METHOD FIRST;
-ALTER TABLE runoob_alter_test INSERT_METHOD=FIRST;
-ALTER TABLE runoob_alter_test INSERT_METHOD LAST;
-ALTER TABLE runoob_alter_test INSERT_METHOD=LAST;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  "datatype3" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        KEY_BLOCK_SIZE
        KEY_BLOCK_SIZE choices vary depending on the storage engine used for a table. For MyISAM tables, KEY_BLOCK_SIZE optionally specifies the size in bytes to be used for index key blocks. For InnoDB tables, KEY_BLOCK_SIZE specifies the page size in kilobytes to be used for compressed InnoDB tables. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_tbl_test`(
-    `runoob_id` VARCHAR(30),
-    `runoob_title` VARCHAR(100) NOT NULL,
-    `runoob_author` VARCHAR(40) NOT NULL,
-    `submission_date` VARCHAR(30)
-) ENGINE=MyISAM KEY_BLOCK_SIZE=8;
-
-ALTER TABLE runoob_tbl_test ENGINE=InnoDB;
-ALTER TABLE runoob_tbl_test KEY_BLOCK_SIZE=0;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_test"
-(
-  "runoob_id" VARCHAR(30),
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR(30)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
        
-
        
-
        MAX_ROWS
        In MySQL, MAX_ROWS indicates the maximum number of rows that can be stored in a table. This attribute will be deleted during migration using DSC.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-);
-
-ALTER TABLE runoob_alter_test MAX_ROWS 100000;
-ALTER TABLE runoob_alter_test MAX_ROWS=100000;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  "datatype3" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        MIN_ROWS
        MIN_ROWS indicates the minimum number of rows that can be stored in a table. This attribute will be deleted during migration using DSC.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-);
-ALTER TABLE runoob_alter_test MIN_ROWS 10000;
-ALTER TABLE runoob_alter_test MIN_ROWS=10000;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  "datatype3" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        PACK_KEYS
        In MySQL, PACK_KEYS specifies the index compression mode in the MyISAM storage engine. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-) ENGINE=MyISAM PACK_KEYS=1;
-
-##A
-ALTER TABLE runoob_alter_test PACK_KEYS 0;
-ALTER TABLE runoob_alter_test PACK_KEYS=0;
-
-##B
-ALTER TABLE runoob_alter_test PACK_KEYS 1;
-ALTER TABLE runoob_alter_test PACK_KEYS=1;
-
-##C
-ALTER TABLE runoob_alter_test PACK_KEYS DEFAULT;
-ALTER TABLE runoob_alter_test PACK_KEYS=DEFAULT;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  "datatype3" FLOAT(20),
-  "datatype4" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
---A
-
---B
-
---C
        
-
        
-
        PASSWORD
        In MySQL, PASSWORD indicates the user password. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-);
-ALTER TABLE runoob_alter_test PASSWORD 'HELLO';
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  "datatype3" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        ROW_FORMAT
        ROW_FORMAT defines the physical format in which the rows are stored. Row format choices vary depending on the storage engine used for the table. If you specify a row format that is not supported by the storage engine that is used for the table, the table will be created using that storage engine's default row format. If ROW_FORMAT is set to DEFAULT, the value will be migrated to SET NOCOMPRESS. If ROW_FORMAT is set to COMPRESSED, the value will be migrated to SET COMPRESS. GaussDB(DWS) supports only the preceding two ROW_FORMAT values. If other values are used, they will be deleted by DSC.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    `dataType3` DOUBLE(20,8),
-    `dataType4` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-) ENGINE=InnoDB;
-
-## A.
-ALTER TABLE runoob_alter_test ROW_FORMAT DEFAULT;
-ALTER TABLE runoob_alter_test ROW_FORMAT=DEFAULT;
-
-## B.
-ALTER TABLE runoob_alter_test ROW_FORMAT DYNAMIC;
-ALTER TABLE runoob_alter_test ROW_FORMAT=DYNAMIC;
-
-## C.
-ALTER TABLE runoob_alter_test ROW_FORMAT COMPRESSED;
-ALTER TABLE runoob_alter_test ROW_FORMAT=COMPRESSED;
-
-## D.
-ALTER TABLE runoob_alter_test ROW_FORMAT REDUNDANT;
-ALTER TABLE runoob_alter_test ROW_FORMAT=REDUNDANT;
-
-## E.
-ALTER TABLE runoob_alter_test ROW_FORMAT COMPACT;
-ALTER TABLE runoob_alter_test ROW_FORMAT=COMPACT;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  "datatype3" FLOAT(20),
-  "datatype4" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
--- A.
-ALTER TABLE "public"."runoob_alter_test" SET NOCOMPRESS;
-ALTER TABLE "public"."runoob_alter_test" SET NOCOMPRESS;
-
--- B.
-
--- C.
-ALTER TABLE "public"."runoob_alter_test" SET COMPRESS;
-ALTER TABLE "public"."runoob_alter_test" SET COMPRESS;
-
--- D.
-
--- E.
        
-
        
-
        STATS_AUTO_RECALC
        STATS_AUTO_RECALC specifies whether to automatically recalculate persistent statistics for an InnoDB table. GaussDB(DWS) does not support this attribute, which will be deleted by DSC during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `runoob_id` VARCHAR(30),
-    `runoob_title` VARCHAR(100) NOT NULL,
-    `runoob_author` VARCHAR(40) NOT NULL,
-    `submission_date` VARCHAR(30)
-) ENGINE=InnoDB, STATS_AUTO_RECALC=DEFAULT;
-
-## A.
-ALTER TABLE runoob_alter_test STATS_AUTO_RECALC DEFAULT;
-ALTER TABLE runoob_alter_test STATS_AUTO_RECALC=DEFAULT;
-
-## B.
-ALTER TABLE runoob_alter_test STATS_AUTO_RECALC 0;
-ALTER TABLE runoob_alter_test STATS_AUTO_RECALC=0;
-
-## C.
-ALTER TABLE runoob_alter_test STATS_AUTO_RECALC 1;
-ALTER TABLE runoob_alter_test STATS_AUTO_RECALC=1;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "runoob_id" VARCHAR(30),
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR(30)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
-
--- A.
-
--- B.
-
--- C.
-
        
-
        
-
        STATS_PERSISTENT
        In MySQL, STATS_PERSISTENT specifies whether to enable persistence statistics for an InnoDB table. The CREATE TABLE and ALTER TABLE statements can be used to enable persistence statistics. DSC will delete this attribute during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-) ENGINE=InnoDB, STATS_PERSISTENT=0;
-
-## A.
-ALTER TABLE runoob_alter_test STATS_PERSISTENT DEFAULT;
-ALTER TABLE runoob_alter_test STATS_PERSISTENT=DEFAULT;
-
-## B.
-ALTER TABLE runoob_alter_test STATS_PERSISTENT 0;
-ALTER TABLE runoob_alter_test STATS_PERSISTENT=0;
-
-## C.
-ALTER TABLE runoob_alter_test STATS_PERSISTENT 1;
-ALTER TABLE runoob_alter_test STATS_PERSISTENT=1;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  "datatype3" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
--- A.
-
--- B.
-
--- C.
        
-
        
-
        STATS_SAMPLE_PAGES
        STATS_SAMPLE_PAGES specifies the number of index pages to sample when cardinality and other statistics for an indexed column are estimated. DSC will delete this attribute during migration.
        
-
        Input
        
-
        CREATE TABLE `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` DOUBLE(20,8),
-    `dataType3` TEXT NOT NULL,
-    PRIMARY KEY(`dataType1`)
-) ENGINE=InnoDB,STATS_SAMPLE_PAGES=25;
-
-ALTER TABLE runoob_alter_test STATS_SAMPLE_PAGES 100;
-ALTER TABLE runoob_alter_test STATS_SAMPLE_PAGES=100;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(20),
-  "datatype3" TEXT NOT NULL,
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
        
-
        
-
        UNION
        UNION is a table creation parameter of the MERGE storage engine. Creating a table using this keyword is similar to creating a common view. The created table logically combines the data of multiple tables that are specified by UNION. DSC migrates this feature to the view creation statement in GaussDB.
        
-
        Input
        
-
        CREATE TABLE t1 (
-    a INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
-    message CHAR(20)
-) ENGINE=MyISAM;
-
-CREATE TABLE t2 (
-    a INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
-    message CHAR(20)
-) ENGINE=MyISAM;
-
-CREATE TABLE total (
-    a INT NOT NULL AUTO_INCREMENT,
-    message CHAR(20))
-ENGINE=MERGE UNION=(t1,t2) INSERT_METHOD=LAST;
        
-
        Output
        
-
        CREATE TABLE t1 (
-    a SERIAL NOT NULL PRIMARY KEY,
-    message CHAR(20)
-)
-WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-NOCOMPRESS
-DISTRIBUTE BY HASH ("a");
-
-CREATE TABLE t2 (
-    a SERIAL NOT NULL PRIMARY KEY,
-    message CHAR(20)
-)
-WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-NOCOMPRESS
-DISTRIBUTE BY HASH ("a");
-
-CREATE VIEW total(a, message) AS
-SELECT * FROM t1
-UNION ALL
-SELECT * FROM t2;
        
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6833.html b/docs/dws/tool/dws_07_6833.html
deleted file mode 100644
index 7c67853e..00000000
--- a/docs/dws/tool/dws_07_6833.html
+++ /dev/null
@@ -1,367 +0,0 @@
-
-
-
        Table Operations
        
-
        This section contains the migration syntax for migrating MySQL table operation. The migration syntax decides how the supported keywords/features are migrated.
        
-
        For details, see the following topics:
        
-
-
        LIKE (Table Cloning)
        MySQL databases support CREATE TABLE. LIKE is a method with which a table is created by cloning the old table structure, and this method is supported by GaussDB(DWS). DSC will add additional table attribute information during migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `public`.`runoob_tbl_old`(
-    `dataType_1` YEAR,
-    `dataType_2` YEAR(4),
-    `dataType_3` YEAR DEFAULT '2018',
-    `dataType_4` TIME DEFAULT NULL
-);
-
-CREATE TABLE `runoob_tbl` (like `runoob_tbl_old`);
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_tbl_old"
-(
-  "datatype_1" VARCHAR(4),
-  "datatype_2" VARCHAR(4),
-  "datatype_3" VARCHAR(4) DEFAULT '2018',
-  "datatype_4" TIME WITHOUT TIME ZONE DEFAULT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype_1");
-
-CREATE TABLE "public"."runoob_tbl"( LIKE "public"."runoob_tbl_old"
-   INCLUDING COMMENTS INCLUDING CONSTRAINTS INCLUDING DEFAULTS INCLUDING INDEXES INCLUDING STORAGE);
        
-
        
-
        ADD|DROP COLUMN
        MySQL and GaussDB(DWS) use different statements for adding and deleting columns. DSC will perform adaptation based on GaussDB features during migration.
        
-
         
        GaussDB does not support the update of sequence numbers in table definitions. Temporarily, DSC does not support the complete migration of the FIRST and AFTER features. So as a workaround, it simply deletes the keywords.
        
-
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    `dataType3` DOUBLE(20,8),
-    `dataType4` TEXT NOT NULL,
-    `dataType5` YEAR NOT NULL DEFAULT '2018',
-    `dataType6` DATETIME NOT NULL DEFAULT '2018-10-12 15:27:33.999999',
-    `dataType7` CHAR NOT NULL DEFAULT '',
-    `dataType8` VARCHAR(50),
-    `dataType9` VARCHAR(50) NOT NULL DEFAULT '',
-    `dataType10` TIME NOT NULL DEFAULT '10:20:59',
-    PRIMARY KEY(`dataType1`)
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-## A.
-ALTER TABLE runoob_alter_test ADD dataType1_1 INT NOT NULL AFTER dataType1;
-ALTER TABLE runoob_alter_test DROP dataType1_1;
-
-## B.
-ALTER TABLE runoob_alter_test ADD dataType1_1 INT NOT NULL FIRST;
-ALTER TABLE runoob_alter_test DROP dataType1_1;
-
-## C.
-ALTER TABLE runoob_alter_test ADD COLUMN dataType1_1 INT NOT NULL AFTER dataType2;
-ALTER TABLE runoob_alter_test DROP COLUMN dataType1_1;
-
-## D.
-ALTER TABLE runoob_alter_test ADD COLUMN dataType1_1 INT NOT NULL FIRST;
-ALTER TABLE runoob_alter_test DROP COLUMN dataType1_1;
-
-## E.
-ALTER TABLE runoob_alter_test ADD COLUMN(dataType1_1 INT NOT NULL, dataType1_2 VARCHAR(200) NOT NULL);
-ALTER TABLE runoob_alter_test DROP COLUMN dataType1_1, DROP COLUMN dataType1_2;
-
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  "datatype3" FLOAT(20),
-  "datatype4" TEXT NOT NULL,
-  "datatype5" VARCHAR(4) NOT NULL DEFAULT '2018',
-  "datatype6" TIMESTAMP WITHOUT TIME ZONE NOT NULL DEFAULT '2018-10-12 15:27:33.999999',
-  "datatype7" CHAR NOT NULL DEFAULT '',
-  "datatype8" VARCHAR(50),
-  "datatype9" VARCHAR(50) NOT NULL DEFAULT '',
-  "datatype10" TIME WITHOUT TIME ZONE NOT NULL DEFAULT '10:20:59',
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
--- A.
-ALTER TABLE "public"."runoob_alter_test" ADD COLUMN "datatype1_1" INTEGER NOT NULL;
-ALTER TABLE "public"."runoob_alter_test" DROP COLUMN "datatype1_1" RESTRICT;
-
--- B.
-ALTER TABLE "public"."runoob_alter_test" ADD COLUMN "datatype1_1" INTEGER NOT NULL;
-ALTER TABLE "public"."runoob_alter_test" DROP COLUMN "datatype1_1" RESTRICT;
-
--- C.
-ALTER TABLE "public"."runoob_alter_test" ADD COLUMN "datatype1_1" INTEGER NOT NULL;
-ALTER TABLE "public"."runoob_alter_test" DROP COLUMN "datatype1_1" RESTRICT;
-
--- D.
-ALTER TABLE "public"."runoob_alter_test" ADD COLUMN "datatype1_1" INTEGER NOT NULL;
-ALTER TABLE "public"."runoob_alter_test" DROP COLUMN "datatype1_1" RESTRICT;
-
--- E.
-ALTER TABLE "public"."runoob_alter_test" ADD COLUMN "datatype1_1" VARCHAR(200) NOT NULL, ADD COLUMN "datatype1_2" VARCHAR(200) NOT NULL;
-ALTER TABLE "public"."runoob_alter_test" DROP COLUMN "datatype1_1" RESTRICT, DROP COLUMN "datatype1_2" RESTRICT;
        
-
        
-
        MODIFY (Column Modification)
        MySQL uses the MODIFY keyword to change column data types and set NOT NULL constraints. DSC will perform adaptation based on GaussDB features during migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `runoob_alter_test`(
-    `dataType0` varchar(100),
-    `dataType1` bigint,
-    `dataType2` bigint,
-    `dataType3` bigint
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-## A.
-ALTER TABLE runoob_alter_test MODIFY dataType1 smallint;
-
-## B.
-ALTER TABLE runoob_alter_test MODIFY dataType1 smallint NOT NULL;
-
-## C.
-ALTER TABLE runoob_alter_test MODIFY dataType1 smallint NOT NULL FIRST;
-
-## D.
-ALTER TABLE runoob_alter_test MODIFY dataType1 smallint NOT NULL AFTER dataType3;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype0" VARCHAR(100),
-  "datatype1" BIGINT,
-  "datatype2" BIGINT,
-  "datatype3" BIGINT
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype0");
-
--- A.
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype1" SET DATA TYPE SMALLINT;
-
--- B.
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype1" SET DATA TYPE SMALLINT, ALTER COLUMN "datatype1" SET NOT NULL;
-
--- C.
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype1" SET DATA TYPE SMALLINT, ALTER COLUMN "datatype1" SET NOT NULL;
-
--- D.
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype1" SET DATA TYPE SMALLINT, ALTER COLUMN "datatype1" SET NOT NULL;
        
-
        
-
        CHANGE (Column Modification)
        MySQL uses the CHANGE keyword to change column names and data types and set NOT NULL constraints. DSC will perform adaptation based on GaussDB features during migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `runoob_alter_test`(
-    `dataType0` varchar(128),
-    `dataType1` bigint,
-    `dataType2` bigint,
-    `dataType3` bigint,
-    `dataType4` bigint
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-## A.
-ALTER TABLE runoob_alter_test CHANGE dataType1 dataType1New VARCHAR(50);
-
-## B.
-ALTER TABLE runoob_alter_test CHANGE dataType2 dataType2New VARCHAR(50) NOT NULL;
-
-## C.
-ALTER TABLE runoob_alter_test CHANGE dataType3 dataType3New VARCHAR(100) FIRST;
-
-## D.
-ALTER TABLE runoob_alter_test CHANGE dataType4 dataType4New VARCHAR(50) AFTER dataType1;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype0" VARCHAR(128),
-  "datatype1" BIGINT,
-  "datatype2" BIGINT,
-  "datatype3" BIGINT,
-  "datatype4" BIGINT
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype0");
-
--- A.
-ALTER TABLE "public"."runoob_alter_test" RENAME COLUMN "datatype1" TO "datatype1new";
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype1new" SET DATA TYPE VARCHAR(50);
-
--- B.
-ALTER TABLE "public"."runoob_alter_test" RENAME COLUMN "datatype2" TO "datatype2new";
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype2new" SET DATA TYPE VARCHAR(50), ALTER COLUMN "datatype2new" SET NOT NULL;
-
--- C.
-ALTER TABLE "public"."runoob_alter_test" RENAME COLUMN "datatype3" TO "datatype3new";
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype3new" SET DATA TYPE VARCHAR(100);
-
--- D.
-ALTER TABLE "public"."runoob_alter_test" RENAME COLUMN "datatype4" TO "datatype4new";
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype4new" SET DATA TYPE VARCHAR(50);
        
-
        
-
        SET|DROP COLUMN DEFAULT VALUE
        In MySQL, the COLUMN keyword can be omitted when the ALTER statement is used to set the default value of a column. DSC will perform adaptation based on GaussDB features during migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    `dataType3` DOUBLE(20,8),
-    `dataType4` TEXT NOT NULL,
-    `dataType5` YEAR NOT NULL DEFAULT '2018',
-    `dataType6` DATETIME NOT NULL DEFAULT '2018-10-12 15:27:33.999999',
-    `dataType7` CHAR NOT NULL DEFAULT '',
-    `dataType8` VARCHAR(50),
-    `dataType9` VARCHAR(50) NOT NULL DEFAULT '',
-    `dataType10` TIME NOT NULL DEFAULT '10:20:59',
-    PRIMARY KEY(`dataType1`)
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-ALTER TABLE runoob_alter_test ALTER dataType2 SET DEFAULT 1;
-ALTER TABLE runoob_alter_test ALTER COLUMN dataType2 SET DEFAULT 3;
-ALTER TABLE runoob_alter_test ALTER dataType2 DROP DEFAULT;
-ALTER TABLE runoob_alter_test ALTER COLUMN dataType2 DROP DEFAULT;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  "datatype3" FLOAT(20),
-  "datatype4" TEXT NOT NULL,
-  "datatype5" VARCHAR(4) NOT NULL DEFAULT '2018',
-  "datatype6" TIMESTAMP WITHOUT TIME ZONE NOT NULL DEFAULT '2018-10-12 15:27:33.999999',
-  "datatype7" CHAR NOT NULL DEFAULT '',
-  "datatype8" VARCHAR(50),
-  "datatype9" VARCHAR(50) NOT NULL DEFAULT '',
-  "datatype10" TIME WITHOUT TIME ZONE NOT NULL DEFAULT '10:20:59',
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype2" SET DEFAULT 1;
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype2" SET DEFAULT 3;
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype2" DROP DEFAULT;
-ALTER TABLE "public"."runoob_alter_test" ALTER COLUMN "datatype2" DROP DEFAULT;
        
-
        
-
        DROP (Table Deletion)
        Both GaussDB(DWS) and MySQL can use the DROP statement to delete tables, but GaussDB(DWS) does not support the RESTRICT | CASCADE keyword in DROP. DSC will delete the keywords during migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `public`.`express_elb_server`(
-   `runoob_id` VARCHAR(10),
-   `runoob_title` VARCHAR(100) NOT NULL,
-   `runoob_author` VARCHAR(40) NOT NULL,
-   `submission_date` VARCHAR(10)
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-DROP TABLE  `public`.`express_elb_server` RESTRICT;
        
-
        Output
        
-
        CREATE TABLE "public"."express_elb_server"
-(
-  "runoob_id" VARCHAR(10),
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR(10)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
-DROP TABLE "public"."express_elb_server";
        
-
        
-
        TRUNCATE (Table Deletion)
        In MySQL, the TABLE keyword can be omitted when the TRUNCATE statement is used to delete table data. GaussDB does not support this usage. In addition, DSC will add CONTINUE IDENTITY RESTRICT during TRUNCATE migration.
        
-
        Input
        
-
        TRUNCATE TABLE `public`.`test_create_table01`;
-TRUNCATE TEST_CREATE_TABLE01;
        
-
        Output
        
-
        TRUNCATE TABLE "public"."test_create_table01" CONTINUE IDENTITY RESTRICT;
-TRUNCATE TABLE "public"."test_create_table01" CONTINUE IDENTITY RESTRICT;
        
-
        
-
        LOCK
        GaussDB(DWS) does not support the ALTER TABLE tbName LOCK statement of MySQL, which will be deleted by DSC during migration.
        
-
        Input
        
-
        CREATE TABLE IF NOT EXISTS `runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10),
-    `dataType4` TEXT NOT NULL,
-    `dataType5` YEAR NOT NULL DEFAULT '2018',
-    `dataType6` DATETIME NOT NULL,
-    `dataType7` CHAR NOT NULL DEFAULT '',
-    `dataType8` VARCHAR(50),
-    `dataType9` VARCHAR(50) NOT NULL DEFAULT '',
-    `dataType10` TIME NOT NULL DEFAULT '10:20:59',
-    PRIMARY KEY(`dataType1`)
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-## A.
-ALTER TABLE runoob_alter_test LOCK DEFAULT;
-
-## B.
-ALTER TABLE runoob_alter_test LOCK=DEFAULT;
-
-## C.
-ALTER TABLE runoob_alter_test LOCK EXCLUSIVE;
-
-## D.
-ALTER TABLE runoob_alter_test LOCK=EXCLUSIVE;
        
-
        Output
        
-
        CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  "datatype4" TEXT NOT NULL,
-  "datatype5" VARCHAR(4) NOT NULL DEFAULT '2018',
-  "datatype6" TIMESTAMP WITHOUT TIME ZONE NOT NULL,
-  "datatype7" CHAR NOT NULL DEFAULT '',
-  "datatype8" VARCHAR(50),
-  "datatype9" VARCHAR(50) NOT NULL DEFAULT '',
-  "datatype10" TIME WITHOUT TIME ZONE NOT NULL DEFAULT '10:20:59',
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
--- A.
-
--- B.
-
--- C.
-
--- D.
        
-
        
-
        
-
        RENAME (Table Renaming)
        The statement for renaming a table in MySQL is slightly different from that in GaussDB(DWS). DSC will perform adaptation based on GaussDB features during migration.
        
-
         
        Currently, DSC does not support original table names prefixed with DATABASE/SCHEMA.
        
-
        
-
        1. MySQL uses the RENAME TABLE statement to change a table name.
          Input
          
-
          # Rename a single table. 
-RENAME TABLE DEPARTMENT TO NEWDEPT;
-
- # Rename multiple tables. 
-RENAME TABLE NEWDEPT TO NEWDEPT_02,PEOPLE TO PEOPLE_02;
          
-
          Output
          
-
          -- Rename a single table. 
-ALTER TABLE "public"."department" RENAME TO "newdept";
-
--- Rename multiple tables. 
-ALTER TABLE "public"."newdept" RENAME TO "newdept_02";
-ALTER TABLE "public"."people" RENAME TO "people_02";
          
-
        2. In MySQL, the ALTER TABLE RENAME statement is used to change a table name. When this statement is migrated by DSC, the keyword AS is converted to TO.
          Input
          
-
          ## A.
-ALTER TABLE runoob_alter_test RENAME TO runoob_alter_testnew;
-
-## B.
-ALTER TABLE runoob_alter_testnew RENAME AS runoob_alter_testnewnew;
          
-
          Output
          
-
          -- A.
-ALTER TABLE "public"."runoob_alter_test" RENAME TO "runoob_alter_testnew";
-
--- B.
-ALTER TABLE "public"."runoob_alter_testnew" RENAME TO "runoob_alter_testnewnew";
          
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6834.html b/docs/dws/tool/dws_07_6834.html
deleted file mode 100644
index 04e6b5f9..00000000
--- a/docs/dws/tool/dws_07_6834.html
+++ /dev/null
@@ -1,113 +0,0 @@
-
-
-
        Unique Indexes
        
-
         
        If MySQL unique indexes (constraints) and primary key constraints are used together during migration, OLAP distribution keys may become unavailable. Therefore, this scenario is not supported by DSC.
        
-
        
-
        1. If there is an inline unique index, DSC will delete it directly.
          Input
          
-
          CREATE TABLE IF NOT EXISTS `public`.`runoob_dataType_test`
-(
-  `id` INT PRIMARY KEY AUTO_INCREMENT,
-  `name` VARCHAR(128) NOT NULL,
-  UNIQUE (id ASC)
-);
          
-
          Output
          
-
          CREATE TABLE "public"."runoob_datatype_test"
-(
-  "id" SERIAL PRIMARY KEY,
-  "name" VARCHAR(128) NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
          
-
        2. If there is a unique index created by ALTER TABLE, DSC will create a normal index based on GaussDB features.
          Input
          
-
          CREATE TABLE IF NOT EXISTS `public`.`runoob_alter_test`(
-    `dataType1` int,
-    `dataType2` FLOAT(10,2),
-    `dataType3` DOUBLE(20,8)
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-ALTER TABLE runoob_alter_test ADD UNIQUE idx_runoob_alter_test_datatype1(dataType1);
-ALTER TABLE runoob_alter_test ADD UNIQUE INDEX idx_runoob_alter_test_datatype1(dataType2);
-ALTER TABLE runoob_alter_test ADD UNIQUE KEY idx_runoob_alter_test_datatype1(dataType3);
-
-CREATE TABLE IF NOT EXISTS `public`.`runoob_alter_test`(
-    `dataType1` int,
-    `dataType2` FLOAT(10,2),
-    `dataType3` DOUBLE(20,8),
-    `dataType4` TEXT NOT NULL,
-    `dataType5` YEAR NOT NULL DEFAULT '2018',
-    `dataType6` DATETIME NOT NULL DEFAULT '2018-10-12 15:27:33.999999'
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-ALTER TABLE runoob_alter_test ADD CONSTRAINT UNIQUE idx_runoob_alter_test_datatype1(dataType1);
-ALTER TABLE runoob_alter_test ADD CONSTRAINT UNIQUE INDEX idx_runoob_alter_test_datatype2(dataType2);
-ALTER TABLE runoob_alter_test ADD CONSTRAINT UNIQUE KEY idx_runoob_alter_test_datatype3(dataType3);
-ALTER TABLE runoob_alter_test ADD CONSTRAINT constraint_dataType UNIQUE idx_runoob_alter_test_datatype4(dataType4);
-ALTER TABLE runoob_alter_test ADD CONSTRAINT constraint_dataType UNIQUE INDEX idx_runoob_alter_test_datatype5(dataType5);
-ALTER TABLE runoob_alter_test ADD CONSTRAINT constraint_dataType UNIQUE KEY idx_runoob_alter_test_datatype6(dataType6);
          
-
          Output
          
-
          CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" INTEGER,
-  "datatype2" FLOAT(10),
-  "datatype3" FLOAT(20)
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
-CREATE INDEX "idx_runoob_alter_test_datatype1" ON "public"."runoob_alter_test" ("datatype1");
-CREATE INDEX "idx_runoob_alter_test_datatype1" ON "public"."runoob_alter_test" ("datatype2");
-CREATE INDEX "idx_runoob_alter_test_datatype1" ON "public"."runoob_alter_test" ("datatype3");
-
-CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" INTEGER,
-  "datatype2" FLOAT(10),
-  "datatype3" FLOAT(20),
-  "datatype4" TEXT NOT NULL,
-  "datatype5" VARCHAR(4) NOT NULL DEFAULT '2018',
-  "datatype6" TIMESTAMP WITHOUT TIME ZONE NOT NULL DEFAULT '2018-10-12 15:27:33.999999'
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
-CREATE INDEX "idx_runoob_alter_test_datatype1" ON "public"."runoob_alter_test" ("datatype1");
-CREATE INDEX "idx_runoob_alter_test_datatype2" ON "public"."runoob_alter_test" ("datatype2");
-CREATE INDEX "idx_runoob_alter_test_datatype3" ON "public"."runoob_alter_test" ("datatype3");
-CREATE INDEX "idx_runoob_alter_test_datatype4" ON "public"."runoob_alter_test" ("datatype4");
-CREATE INDEX "idx_runoob_alter_test_datatype5" ON "public"."runoob_alter_test" ("datatype5");
-CREATE INDEX "idx_runoob_alter_test_datatype6" ON "public"."runoob_alter_test" ("datatype6");
          
-
        3. If there is a unique index created by CREATE INDEX, DSC will create a normal index based on GaussDB features.
          Input
          
-
          CREATE TABLE `public`.`test_index_table01` (
-	`TABLE01_ID` INT(11) NOT NULL,
-	`TABLE01_THEME` VARCHAR(100) NULL DEFAULT NULL,
-	`AUTHOR_NAME` CHAR(10) NULL DEFAULT NULL,
-	`AUTHOR_ID` INT(11) NULL DEFAULT NULL,
-	`CREATE_TIME` INT NULL DEFAULT NULL,
-	PRIMARY KEY(`TABLE01_ID`)
-);
-CREATE UNIQUE INDEX AUTHOR_INDEX ON `test_index_table01`(AUTHOR_ID);
          
-
          Output
          
-
          CREATE TABLE "public"."test_index_table01"
-(
-  "table01_id" INTEGER(11) NOT NULL,
-  "table01_theme" VARCHAR(100) DEFAULT NULL,
-  "author_name" CHAR(10) DEFAULT NULL,
-  "author_id" INTEGER(11) DEFAULT NULL,
-  "create_time" INTEGER DEFAULT NULL,
-  PRIMARY KEY ("table01_id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("table01_id");
-CREATE INDEX "author_index" ON "public"."test_index_table01" ("author_id");
          
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6835.html b/docs/dws/tool/dws_07_6835.html
deleted file mode 100644
index 13a687cf..00000000
--- a/docs/dws/tool/dws_07_6835.html
+++ /dev/null
@@ -1,73 +0,0 @@
-
-
-
        Normal and Prefix Indexes
        
-
        GaussDB(DWS) does not support prefix indexes or inline normal indexes. DSC will replace these indexes with normal indexes based on GaussDB features.
        
-
        1. Inline normal/prefix index
          Input
          
-
          CREATE TABLE IF NOT EXISTS `public`.`runoob_dataType_test`
-(
-  `id` INT PRIMARY KEY AUTO_INCREMENT,
-  `name` VARCHAR(128) NOT NULL,
-  INDEX index_single(name(10))
-);
          
-
          Output
          
-
          CREATE TABLE "public"."runoob_datatype_test"
-(
-  "id" SERIAL PRIMARY KEY,
-  "name" VARCHAR(128) NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
-CREATE INDEX "index_single" ON "public"."runoob_datatype_test" USING BTREE ("name");
          
-
        2. Normal/Prefix index created by ALTER TABLE
          Input
          
-
          CREATE TABLE `public`.`test_create_table05` (
- `ID` INT(11) NOT NULL AUTO_INCREMENT,
- `USER_ID` INT(20) NOT NULL,
- `USER_NAME` CHAR(20) NULL DEFAULT NULL,
- `DETAIL` VARCHAR(100) NULL DEFAULT NULL,
- PRIMARY KEY (`ID`)
-);
-
-ALTER TABLE TEST_CREATE_TABLE05 ADD INDEX USER_NAME_INDEX_02(USER_NAME(10));
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table05"
-(
-  "id" SERIAL NOT NULL,
-  "user_id" INTEGER(20) NOT NULL,
-  "user_name" CHAR(20) DEFAULT NULL,
-  "detail" VARCHAR(100) DEFAULT NULL,
-  PRIMARY KEY ("id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
-
-CREATE INDEX "user_name_index_02" ON "public"."test_create_table05" ("user_name");
          
-
        3. Normal/Prefix index created by CREATE INDEX
          Input
          
-
          CREATE TABLE IF NOT EXISTS `public`.`customer`(
-    `name` varchar(64) primary key,
-	id integer,
-	id2 integer
-);
-
-CREATE INDEX part_of_name ON customer (name(10));
          
-
          Output
          
-
          CREATE TABLE "public"."customer"
-(
-  "name" VARCHAR(64) PRIMARY KEY,
-  "id" INTEGER,
-  "id2" INTEGER
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("name");
-
-CREATE INDEX "part_of_name" ON "public"."customer" USING BTREE ("name");
          
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6836.html b/docs/dws/tool/dws_07_6836.html
deleted file mode 100644
index fc413bde..00000000
--- a/docs/dws/tool/dws_07_6836.html
+++ /dev/null
@@ -1,84 +0,0 @@
-
-
-
        Hash Indexes
        
-
        GaussDB(DWS) does not support hash indexes. DSC will replace these indexes with normal indexes based on GaussDB features.
        
-
        1. Inline hash index
          Input
          
-
          CREATE TABLE `public`.`test_create_table03` (
-	`DEMAND_ID` INT(11) NOT NULL AUTO_INCREMENT,
-	`DEMAND_NAME` CHAR(100) NOT NULL,
-	`THEME` VARCHAR(200) NULL DEFAULT NULL,
-	`SEND_ID` INT(11) NULL DEFAULT NULL,
-	`SEND_NAME` CHAR(20) NULL DEFAULT NULL,
-	`SEND_TIME` DATETIME NULL DEFAULT NULL,
-	`DEMAND_CONTENT` TEXT NOT NULL,
-	PRIMARY KEY(`DEMAND_ID`),
-    INDEX CON_INDEX(DEMAND_CONTENT(100)) USING HASH ,
-    INDEX SEND_INFO_INDEX USING HASH (SEND_ID,SEND_NAME(10),SEND_TIME)
-);
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table03"
-(
-  "demand_id" SERIAL NOT NULL,
-  "demand_name" CHAR(100) NOT NULL,
-  "theme" VARCHAR(200) DEFAULT NULL,
-  "send_id" INTEGER(11) DEFAULT NULL,
-  "send_name" CHAR(20) DEFAULT NULL,
-  "send_time" TIMESTAMP WITHOUT TIME ZONE DEFAULT NULL,
-  "demand_content" TEXT NOT NULL,
-  PRIMARY KEY ("demand_id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("demand_id");
-CREATE INDEX "con_index" ON "public"."test_create_table03" ("demand_content");
-CREATE INDEX "send_info_index" ON "public"."test_create_table03" ("send_id","send_name","send_time");
          
-
        2. Hash index created by ALTER TABLE
          Input
          
-
          CREATE TABLE IF NOT EXISTS `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    PRIMARY KEY(`dataType1`)
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
-
-ALTER TABLE runoob_alter_test ADD KEY alterTable_addKey_indexType(dataType1) USING HASH;
          
-
          Output
          
-
          CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
-CREATE INDEX "altertable_addkey_indextype" ON "public"."runoob_alter_test" ("datatype1");
          
-
        3. Hash index created by CREATE INDEX
          Input
          
-
          CREATE TABLE `public`.`test_index_table06` (
-	`ID` INT(11) NOT NULL AUTO_INCREMENT,
-	`FNAME` VARCHAR(30) NOT NULL,
-	`INAME` VARCHAR(30) NOT NULL,
-	PRIMARY KEY (`ID`)
-);
-CREATE INDEX FNAME_INDEX ON TEST_INDEX_TABLE06(FNAME(10)) USING HASH;
-CREATE INDEX NAME_01 ON TEST_INDEX_TABLE06(FNAME(10),INAME(10)) USING HASH;
          
-
          Output
          
-
          CREATE TABLE "public"."test_index_table06"
-(
-  "id" SERIAL NOT NULL,
-  "fname" VARCHAR(30) NOT NULL,
-  "iname" VARCHAR(30) NOT NULL,
-  PRIMARY KEY ("id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
-CREATE INDEX "fname_index" ON "public"."test_index_table06" ("fname");
-CREATE INDEX "name_01" ON "public"."test_index_table06" ("fname","iname");
          
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6837.html b/docs/dws/tool/dws_07_6837.html
deleted file mode 100644
index eadc8d31..00000000
--- a/docs/dws/tool/dws_07_6837.html
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-
        B-tree Indexes
        
-
        GaussDB(DWS) supports B-tree indexes, but the position of the USING BTREE keyword in a statement is different from that in MySQL. DSC will perform adaptation based on GaussDB features during migration.
        
-
        1. Inline B-tree index
          Input
          
-
          CREATE TABLE `public`.`test_create_table03` (
-	`DEMAND_ID` INT(11) NOT NULL AUTO_INCREMENT,
-	`DEMAND_NAME` CHAR(100) NOT NULL,
-	`THEME` VARCHAR(200) NULL DEFAULT NULL,
-	`SEND_ID` INT(11) NULL DEFAULT NULL,
-	`SEND_NAME` CHAR(20) NULL DEFAULT NULL,
-	`SEND_TIME` DATETIME NULL DEFAULT NULL,
-	`DEMAND_CONTENT` TEXT NOT NULL,
-	PRIMARY KEY(`DEMAND_ID`),
-	INDEX THEME_INDEX(THEME) USING BTREE,
-    INDEX NAME_INDEX USING BTREE (SEND_NAME(10))
-);
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table03"
-(
-  "demand_id" SERIAL NOT NULL,
-  "demand_name" CHAR(100) NOT NULL,
-  "theme" VARCHAR(200) DEFAULT NULL,
-  "send_id" INTEGER(11) DEFAULT NULL,
-  "send_name" CHAR(20) DEFAULT NULL,
-  "send_time" TIMESTAMP WITHOUT TIME ZONE DEFAULT NULL,
-  "demand_content" TEXT NOT NULL,
-  PRIMARY KEY ("demand_id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("demand_id");
-CREATE INDEX "theme_index" ON "public"."test_create_table03" USING BTREE ("theme");
-CREATE INDEX "name_index" ON "public"."test_create_table03" USING BTREE ("send_name");
          
-
        2. B-tree index created by ALTER TABLE
          Input
          
-
          CREATE TABLE IF NOT EXISTS `public`.`runoob_alter_test`(
-    `dataType1` int NOT NULL AUTO_INCREMENT,
-    `dataType2` FLOAT(10,2),
-    PRIMARY KEY(`dataType1`)
-);
-
-ALTER TABLE runoob_alter_test ADD KEY alterTable_addKey_indexType (dataType1) USING BTREE;
          
-
          Output
          
-
          CREATE TABLE "public"."runoob_alter_test"
-(
-  "datatype1" SERIAL NOT NULL,
-  "datatype2" FLOAT(10),
-  PRIMARY KEY ("datatype1")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("datatype1");
-
-CREATE INDEX "altertable_addkey_indextype" ON "public"."runoob_alter_test" ("datatype1");
          
-
        3. B-tree index created by CREATE INDEX
          Input
          
-
          CREATE TABLE `public`.`test_create_table03` (
-	`DEMAND_ID` INT(11) NOT NULL AUTO_INCREMENT,
-	`DEMAND_NAME` CHAR(100) NOT NULL,
-	`THEME` VARCHAR(200) NULL DEFAULT NULL,
-	`SEND_ID` INT(11) NULL DEFAULT NULL,
-	`SEND_NAME` CHAR(20) NULL DEFAULT NULL,
-	`SEND_TIME` DATETIME NULL DEFAULT NULL,
-	`DEMAND_CONTENT` TEXT NOT NULL,
-	PRIMARY KEY(`DEMAND_ID`),
-    INDEX CON_INDEX(DEMAND_CONTENT(100)) USING HASH ,
-    INDEX SEND_INFO_INDEX USING HASH (SEND_ID,SEND_NAME(10),SEND_TIME)
-);
-
-
-CREATE TABLE `public`.`test_index_table05` (
-	`ID` INT(11) NOT NULL AUTO_INCREMENT,
-	`USER_ID` INT(20) NOT NULL,
-	`USER_NAME` CHAR(20) NULL DEFAULT NULL,
-	`DETAIL` VARCHAR(100) NULL DEFAULT NULL,
-	PRIMARY KEY (`ID`)
-);
-CREATE UNIQUE INDEX USER_ID_INDEX USING BTREE ON TEST_INDEX_TABLE05(USER_ID);
-CREATE INDEX USER_NAME_INDEX USING BTREE ON TEST_INDEX_TABLE05(USER_NAME(10));
-CREATE INDEX DETAIL_INDEX ON TEST_INDEX_TABLE05(DETAIL(50)) USING BTREE;
-CREATE INDEX USER_INFO_INDEX USING BTREE ON TEST_INDEX_TABLE05(USER_ID,USER_NAME(10));
          
-
          Output
          
-
          CREATE TABLE "public"."test_index_table05"
-(
-  "id" SERIAL NOT NULL,
-  "user_id" INTEGER(20) NOT NULL,
-  "user_name" CHAR(20) DEFAULT NULL,
-  "detail" VARCHAR(100) DEFAULT NULL,
-  PRIMARY KEY ("id")
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
-CREATE INDEX "user_id_index" ON "public"."test_index_table05" ("user_id");
-CREATE INDEX "user_name_index" ON "public"."test_index_table05" USING BTREE ("user_name");
-CREATE INDEX "detail_index" ON "public"."test_index_table05" USING BTREE ("detail");
-CREATE INDEX "user_info_index" ON "public"."test_index_table05" USING BTREE ("user_id","user_name");
          
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6838.html b/docs/dws/tool/dws_07_6838.html
deleted file mode 100644
index bfee716d..00000000
--- a/docs/dws/tool/dws_07_6838.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
        Spatial Indexes
        
-
        GaussDB(DWS) does not support spatial indexes. DSC will perform adaptation based on GaussDB features during migration.
        
-
        1. Inline spatial index
          Input
          
-
          CREATE TABLE `public`.`test_create_table04` (
-	`ID` INT(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,
-	`A` POINT NOT NULL,
-	`B` POLYGON NOT NULL,
-	`C` GEOMETRYCOLLECTION NOT NULL,
-	`D` LINESTRING NOT NULL,
-	`E` MULTILINESTRING NOT NULL,
-	`F` MULTIPOINT NOT NULL,
-	`G` MULTIPOLYGON NOT NULL,
-	SPATIAL INDEX A_INDEX(A),
-	SPATIAL INDEX B_INDEX(B),
-	SPATIAL INDEX C_INDEX(C),
-	SPATIAL KEY D_INDEX(D),
-	SPATIAL KEY E_INDEX(E),
-	SPATIAL KEY F_INDEX(F),
-	SPATIAL INDEX G_INDEX(G)
-);
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table04"
-(
-  "id" SERIAL NOT NULL PRIMARY KEY,
-  "a" POINT NOT NULL,
-  "b" POLYGON NOT NULL,
-  "c" CIRCLE NOT NULL,
-  "d" POLYGON NOT NULL,
-  "e" BOX NOT NULL,
-  "f" BOX NOT NULL,
-  "g" POLYGON NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
-CREATE INDEX "a_index" ON "public"."test_create_table04" USING GIST ("a");
-CREATE INDEX "b_index" ON "public"."test_create_table04" USING GIST ("b");
-CREATE INDEX "c_index" ON "public"."test_create_table04" USING GIST ("c");
-CREATE INDEX "d_index" ON "public"."test_create_table04" USING GIST ("d");
-CREATE INDEX "e_index" ON "public"."test_create_table04" USING GIST ("e");
-CREATE INDEX "f_index" ON "public"."test_create_table04" USING GIST ("f");
-CREATE INDEX "g_index" ON "public"."test_create_table04" USING GIST ("g");
          
-
        2. Spatial index created by ALTER TABLE
          Input
          
-
          CREATE TABLE `public`.`test_create_table04` (
- `ID` INT(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,
- `A` POINT NOT NULL,
- `B` POLYGON NOT NULL,
- `C` GEOMETRYCOLLECTION NOT NULL,
- `D` LINESTRING NOT NULL,
- `E` MULTILINESTRING NOT NULL,
- `F` MULTIPOINT NOT NULL,
- `G` MULTIPOLYGON NOT NULL
-);
-
-ALTER TABLE `test_create_table04` ADD SPATIAL INDEX A_INDEX(A);
-ALTER TABLE `test_create_table04` ADD SPATIAL INDEX E_INDEX(E) USING BTREE;
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table04"
-(
-  "id" SERIAL NOT NULL PRIMARY KEY,
-  "a" POINT NOT NULL,
-  "b" POLYGON NOT NULL,
-  "c" CIRCLE NOT NULL,
-  "d" POLYGON NOT NULL,
-  "e" BOX NOT NULL,
-  "f" BOX NOT NULL,
-  "g" POLYGON NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
-
-CREATE INDEX "a_index" ON "public"."test_create_table04" USING GIST ("a");
-CREATE INDEX "e_index" ON "public"."test_create_table04" USING GIST ("e");
          
-
        3. Spatial index created by CREATE INDEX
          Input
          
-
          CREATE TABLE `public`.`test_create_table04` (
-	`ID` INT(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,
-	`A` POINT NOT NULL,
-	`B` POLYGON NOT NULL,
-	`C` GEOMETRYCOLLECTION NOT NULL,
-	`D` LINESTRING NOT NULL,
-	`E` MULTILINESTRING NOT NULL,
-	`F` MULTIPOINT NOT NULL,
-	`G` MULTIPOLYGON NOT NULL
-);
-
-CREATE SPATIAL INDEX A_INDEX ON `test_create_table04`(A);
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table04"
-(
-  "id" SERIAL NOT NULL PRIMARY KEY,
-  "a" POINT NOT NULL,
-  "b" POLYGON NOT NULL,
-  "c" CIRCLE NOT NULL,
-  "d" POLYGON NOT NULL,
-  "e" BOX NOT NULL,
-  "f" BOX NOT NULL,
-  "g" POLYGON NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("id");
-
-CREATE INDEX "a_index" ON "public"."test_create_table04" USING GIST ("a");
          
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6841.html b/docs/dws/tool/dws_07_6841.html
deleted file mode 100644
index a836a979..00000000
--- a/docs/dws/tool/dws_07_6841.html
+++ /dev/null
@@ -1,376 +0,0 @@
-
-
-
        Tables
        
-
        GaussDB Keyword
        If a keyword is used as a column name, quotes (") must be added, for example, "order".
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_bd2 
- ( 
- ORDER NUMBER(10), 
- USER varchar2(30), 
- DATE VARCHAR(10 
- );
        
-
        CREATE TABLE tbl_bd2 
- ( 
- "ORDER" NUMBER(10), 
- "USER" varchar2(30),  
- "DATE" VARCHAR(10 
- );
        
-
        
-
        
-
        
-
        Data Type (I)
        LONG VARCHAR should be changed to CLOB.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID VARCHAR(36), 
- NAME LONG VARCHAR 
- );
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID VARCHAR(36), 
- NAME CLOB 
- );
        
-
        
-
        
-
        
-
        LONG VARGRAPHIC.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID VARCHAR(36), 
- NAME LONG VARGRAPHIC 
- );
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID VARCHAR(36), 
- NAME CLOB  
- );
        
-
        
-
        
-
        Foreign Key
        Below attributes of Foreign key constraint should be commented:
        
-
        • ON UPDATE RESTRICT
        • ENFORCED
        • ENABLE QUERY OPTIMIZATION
-
          
-
-
-
-
-
-
-
-
          DB2 Syntax
          
-
          Syntax After Migration
          
-
          ALTER TABLE "SCH"."TBL_DB2" 
- ADD CONSTRAINT "Const_Name" FOREIGN KEY("ID") 
- REFRENCES "SCH"."TBL_DB2_1"("ID") 
- ON DELETE CASCADE 
- ON UPDATE RESTRICT 
- ENFORCED 
- ENABLE QUERY OPTIMIZATION;
          
-
          ALTER TABLE "SCH"."TBL_DB2" 
- ADD CONSTRAINT "Const_Name" FOREIGN KEY("ID") 
- REFRENCES "SCH"."TBL_DB2_1"("ID") 
- ON DELETE CASCADE 
- /*ON UPDATE RESTRICT 
- ENFORCED 
- ENABLE QUERY OPTIMIZATION*/;
          
-
          
-
          
-
        
-
        
-
        Sequence
        built-in auto-increment function.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID BIGINT NOT NULL GENERATED BY DEFAULT AS IDENTITY (   
-       START WITH +1   
-       INCREMENT BY +1   
-       MINVALUE +1   
-       MAXVALUE +9223372036854775807   
-       NO CYCLE   
-       CACHE 20   
-       NO ORDER ) , 
- NAME VARCHAR2(50), 
- ORDER VARCHAR2(100) 
- ); 
- 
- 
        
-
        CREATE SEQUENCE mseq_tbl_db2_id 
- START WITH +1 
- INCREMENT BY +1 
- MINVALUE +1 
- MAXVALUE +9223372036854775807 
- NOCYCLE 
- CACHE 20 
- NOORDER; 
- CREATE TABLE tbl_db2 
- ( 
- ID BIGINT NOT NULL DEFAULT mseq_tbl_db2_id.NEXTVAL, 
- NAME VARCHAR2(50), 
- "ORDER" VARCHAR2(100) 
- );
        
-
        
-
        
-
        
-
        Tablespace
        TABLESPACE for a table to be placed is specified with IN clause.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) NOT NULL DEFAULT IDENTITY.NEXTVAL, 
- NAME VARCHAR2(50) 
- ) 
- IN tbs1 ; 
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) NOT NULL DEFAULT IDENTITY.NEXTVAL, 
- NAME VARCHAR2(50) 
- ) 
- TABLESPACE tbs1 ; 
        
-
        
-
        
-
        
-
        Default
        WITH DEFAULT is specified to specified DEFAULT value.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- STATUS CHAR(1) WITH DEFAULT '0' 
- );
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- STATUS CHAR(1) DEFAULT '0' 
- );
        
-
        
-
        
-
        
-
        DEFAULT specified without value.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- STATUS CHAR(1) WITH DEFAULT 
- );
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- STATUS CHAR(1)  
- );
        
-
        
-
        
-
        Data Type (II)
        CLOB(1048576)
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- REMARKS CLOB(1048576));
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- REMARKS CLOB 
- );
        
-
        
-
        
-
        
-
        BLOB(2048000)
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- REMARKS BLOB(2048000) 
- );
        
-
        CREATE TABLE tbl_db2 
- ( 
- ID number(20) , 
- NAME VARCHAR2(50), 
- REMARKS BLOB 
- );
        
-
        
-
        
-
        LOB Options
        LOGGED/UNLOGGED
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- "ID" number(20) , 
- "NAME" VARCHAR2(50), 
- "REMARKS" BLOB LOGGED 
- );
        
-
        CREATE TABLE tbl_db2 
- ( 
- "ID" number(20) , 
- "NAME" VARCHAR2(50), 
- "REMARKS" BLOB /*LOGGED */  
- );
        
-
        
-
        
-
        
-
        COMPACT/NOT COMPACT
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- "ID" number(20) , 
- "NAME" VARCHAR2(50), 
- "REMARKS" BLOB LOGGED NOT COMPACT 
- );
        
-
        CREATE TABLE tbl_db2 
- ( 
- "ID" number(20) , 
- "NAME" VARCHAR2(50), 
- "REMARKS" BLOB /*LOGGED */ /* NOT COMPACT*/ 
- );
        
-
        
-
        
-
        Organize By
        Organize By
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE TABLE tbl_db2 
- ( 
- "ID" number(20) , 
- "NAME" VARCHAR2(50), 
- "REMARKS" BLOB 
- ) 
- IN tbs1 
- ORGANIZE BY ("ID","NAME");
        
-
        CREATE TABLE tbl_db2 
- ( 
- "ID" number(20) , 
- "NAME" VARCHAR2(50), 
- "REMARKS" BLOB 
- ) 
- TABLESPACE tbs1 
- /*ORGANIZE BY ("ID","NAME")*/;
        
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: DB2 Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6842.html b/docs/dws/tool/dws_07_6842.html
deleted file mode 100644
index a8a524ba..00000000
--- a/docs/dws/tool/dws_07_6842.html
+++ /dev/null
@@ -1,122 +0,0 @@
-
-
-
        DML
        
-
        SELECT
        FETCH clause
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT empno, ename, deptno  
-   FROM emp_t  
-  ORDER BY salary     
-  FETCH FIRST ROW ONLY 
- ----- 
- SELECT empno, ename  
-   FROM emp_t  
-  WHERE deptno = 10 
-  ORDER BY salary  
- fetch first 2 rows only;
        
-
        SELECT empno, ename, deptno  
-   FROM emp_t  
-  ORDER BY salary     
-  LIMIT 1; 
- ----- 
- SELECT empno, ename  
-   FROM emp_t  
-  WHERE deptno = 10 
-  ORDER BY salary  
- LIMIT 2;
        
-
        
-
        
-
         
        The fetch-first-clause sets a maximum number of rows that can be retrieved.
        
-
        
-
        
-
        WITH AS
        WITH AS with column list
        
-
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        WITH rec (emp_no, emp_name, dept_name, dept_no) AS
-   ( SELECT empno, ename, cast('admin' as varchar(90)), 100 AS deptno
-       FROM emp_t )
-SELECT * FROM rec;
        
-
        WITH rec AS
-   ( SELECT empno AS emp_no, ename AS emp_name, cast('admin' as varchar(90)) AS dept_name, 100 AS dept_no
-       FROM emp_t )
-SELECT * FROM rec;
        
-
        
-
        
-
        WITH AS with VALUES clause
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
         WITH rec (baseschema, basename, baselevel) AS 
-    ( VALUES( cast('SCOTT' as varchar(90)), cast('EMP' as varchar(90)), 10000 ) )   
-   SELECT owner, table_name, baselevel -1    
-     FROM ALL_TABLES, REC    
-    WHERE owner = BASESCHEMA 
-      AND table_name   = BASENAME;
        
-
         WITH rec AS 
-    ( SELECT cast('SCOTT' as varchar(90)) AS baseschema, cast('EMP' as varchar(90)) AS basename, 10000 AS baselevel
-From dual )   
-   SELECT owner, table_name, baselevel -1    
-     FROM ALL_TABLES, REC    
-    WHERE owner       = BASESCHEMA 
-      AND table_name  = BASENAME;
        
-
        
-
        
-
        Table Function
        TABLE function is specified with subquery.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT prod_code, prod_desc, (received_qty-issued_qty) stk
-  FROM prod p, TABLE(select prod_code, SUM(received_qty) received_qty FROM prod_recd) r
-     , TABLE(select prod_code, SUM(issued_qty) issued_qty FROM prod_issue) i
- WHERE r.prod_code = p.prod_code
-   AND i.prod_code = p.prod_code; 
        
-
        SELECT prod_code, prod_desc, (received_qty-issued_qty) stk
-  FROM prod p, (select prod_code, SUM(received_qty) received_qty FROM prod_recd) r
-     , (select prod_code, SUM(issued_qty) issued_qty FROM prod_issue) i
- WHERE r.prod_code = p.prod_code
-   AND i.prod_code = p.prod_code;
        
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: DB2 Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6843.html b/docs/dws/tool/dws_07_6843.html
deleted file mode 100644
index 7eb92369..00000000
--- a/docs/dws/tool/dws_07_6843.html
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
        Index Migration (DB2)
        
-
        Reverse Scans
        Reverse Scans
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE INDEX IDX_1 ON EMP  
-   (ID ASC) ALLOW REVERSE SCANS; 
- CREATE INDEX IDX_1 ON EMP  
-   (ID ASC) DISALLOW REVERSE SCANS;
        
-
        CREATE INDEX IDX_1 ON EMP  
-   (ID ASC) /*ALLOW REVERSE SCANS*/; 
- CREATE INDEX IDX_1 ON EMP  
-   (ID ASC) /*DISALLOW REVERSE SCANS*/;
        
-
        
-
        
-
        
-
        Schema
        index's schema is different from its table's schema.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE INDEX IDXSC.IDX_1 ON EMP (ID ASC);
        
-
        CREATE INDEX IDX_1 ON EMP (ID ASC);
        
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: DB2 Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6844.html b/docs/dws/tool/dws_07_6844.html
deleted file mode 100644
index d8f891df..00000000
--- a/docs/dws/tool/dws_07_6844.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
        NICKNAME
        
-
        NICKNAME
        Synonym is referred to Nickname in DB2.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE NICKNAME  sc2.emp FOR sc.emp;
        
-
        CREATE SYNONYM sc2.emp FOR sc.emp;
        
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: DB2 Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6845.html b/docs/dws/tool/dws_07_6845.html
deleted file mode 100644
index 8ae9a46e..00000000
--- a/docs/dws/tool/dws_07_6845.html
+++ /dev/null
@@ -1,57 +0,0 @@
-
-
-
        Statement
        
-
        CURRENT SCHEMA
        SET CURRENT SCHEMA
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CREATE NICKNAME  sc2.emp FOR sc.emp;
        
-
        CREATE SYNONYM sc2.emp FOR sc.emp;
        
-
        
-
        
-
        
-
        GET DIAGNOSTICS with ROW_COUNT
        
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        CC_ORDER_HY_CUSTORCOUNT SET '               
-           ||STR_CUST_COUNT||'_COUNT='||char(CUST_COUNT)||' ,'                               
-           ||'SELF_UPDATE_TIME ='||''''||STR_DATE||''''||' ,'  
-           ||'SUB_UPDATE_TIME ='||''''||STR_DATE1||''''||','  
-           ||'REPORT_STATE ='||''''|| STR_CHAR ||''''  
-           ||' WHERE ORG_CODE ='||''''||TEMP_ORG_CODE||'''' 
-          ||' AND Y='||char(TEMP_YEAR)||' AND HY='||char(TEMP_HY) 
-           ||' AND REGION_CODE='||''''||TEMP_SALE_REG_CODE||''''||' AND BRAND_CODE='||''''||TEMP_BRAND_CODE||'''' 
-           ||' AND exists (select 1 from CC_ORDER_HY_CUSTORCOUNT' 
-           ||' where ORG_CODE ='||''''||TEMP_ORG_CODE||'''' 
-          ||' AND Y='||char(TEMP_YEAR)||' AND HY='||char(TEMP_HY) 
-           ||' AND REGION_CODE='||''''||TEMP_SALE_REG_CODE||''''||' AND BRAND_CODE='||''''||TEMP_BRAND_CODE||''''||')';-- 
- PREPARE S1 FROM STR_UPDATE1; 
- EXECUTE S1;  -- 
- GET DIAGNOSTICS V_NUMRECORDS = ROW_COUNT;    
        
-
        V_NUMRECORDS = SQL%ROWCOUNT;
        
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: DB2 Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_6846.html b/docs/dws/tool/dws_07_6846.html
deleted file mode 100644
index 8ab56ef1..00000000
--- a/docs/dws/tool/dws_07_6846.html
+++ /dev/null
@@ -1,158 +0,0 @@
-
-
-
        System Functions
        
-
        DAY
        Day
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT DAYS(doj) FROM emp;
        
-
        SELECT (TRUNC(doj - TO_DATE('0001/01/01', 'YYYY/MM/DD'))+1) FROM emp;
        
-
        
-
        
-
        
-
        MONTH
        Month
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT (MONTH(ORDER_DATE)-1)/6+1 as TEMP_HY;
        
-
        SELECT (EXTRACT (MONTH FROM ORDER_DATE) -1)/6+1 as TEMP_HY;
        
-
        
-
        
-
        
-
        YEAR
        Year
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT YEAR(ORDER_DATE) as TEMP_HY;
        
-
        SELECT EXTRACT (YEAR FROM ORDER_DATE) as TEMP_HY;
        
-
        
-
        
-
        
-
        CURRENT DATE
        Current date
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT CURRENT DATE FROM DUAL;
        
-
        SELECT CURRENT_DATE FROM DUAL;
        
-
        
-
        
-
        
-
        CURRENT TIMESTAMP
        Current timestamp
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT CURRENT TIMESTAMP - 7 DAYS;
        
-
        SELECT CURRENT_TIMESTAMP - 7 DAYS;
        
-
        
-
        
-
        
-
        POSSTR
        POSSTR
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT POSSTR('THIS IS TEST','TEST') FROM DUAL;
        
-
        SELECT INSTR('THIS IS TEST','TEST') FROM DUAL;
        
-
        
-
        
-
        
-
        VALUE
        Value
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        Select VALUE('abc','') from dual;
        
-
        Select Coalesce('abc','') from dual;
        
-
        
-
        
-
        
-
        Date
        The date function returns a date using a value.
        
-
-
        
-
-
-
-
-
-
-
-
        DB2 Syntax
        
-
        Syntax After Migration
        
-
        SELECT org_code, DATE(order_date) 
-   FROM view_cc_order 
-  WHERE order_date = DATE((SELECT start_date FROM year_week_mark  
-          WHERE year=TEMP_YEAR and week=TEMP_WEEK)); 
- --- 
- SELECT deptno, deptname, DATE(SELECT max(doj) FROM emp e WHERE e.deptno = d.deptno) 
-   FROM dept d;
        
-
        SELECT org_code, mig_db2_ext.mig_db2_fn_date(order_date) 
-   FROM view_cc_order 
-  WHERE order_date = mig_db2_ext.mig_db2_fn_date((SELECT start_date FROM year_week_mark  
-          WHERE year=TEMP_YEAR and week=TEMP_WEEK)); 
- --- 
- SELECT deptno, deptname, mig_db2_ext.mig_db2_fn_date((SELECT max(doj) FROM emp e WHERE e.deptno = d.deptno)) 
-   FROM dept d;
        
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: DB2 Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8111.html b/docs/dws/tool/dws_07_8111.html
deleted file mode 100644
index f9b4d69a..00000000
--- a/docs/dws/tool/dws_07_8111.html
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
        SHOW STATS VALUES SEQUENCED
        
-
        This command displays the COLLECT STATISTICS statement with statistics. Gauss does not have an equivalent for this. Since it does not affect the functionality, this command can be commented.
        
-
        Input
        
-
        SHOW STATS VALUES SEQUENCED on "temp"."table"
        
-
        Output
        
-
        /*SHOW STATS VALUES SEQUENCED on "temp"."table"*/
        
-
        
-
        
-
        
-
        Parent topic: Teradata Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8120.html b/docs/dws/tool/dws_07_8120.html
deleted file mode 100644
index f2ea6c13..00000000
--- a/docs/dws/tool/dws_07_8120.html
+++ /dev/null
@@ -1,595 +0,0 @@
-
-
-
        BTEQ Utility Command
        
-
        The BTEQ utility commands are as follows:
        
-
        LOGOFF QUIT
        LOGOFF ends the current RDBMS sessions without exiting BTEQ.
        
-
        QUIT command ends the current Teradata database sessions and exits BTEQ.
        
-
        
-
        Input
        
-
        SELECT 'StartDTTM' as a
-            ,CURRENT_TIMESTAMP (FORMAT 'HH:MI:SSBMMMBDD,BYYYY') ;
-.LOGOFF;
-.QUIT;
        
-
        Output
        
-
        SELECT 'StartDTTM' as a
-            ,CURRENT_TIMESTAMP (FORMAT 'HH:MI:SSBMMMBDD,BYYYY') ;
-.LOGOFF;
-.QUIT;
        
-
         
        Gauss does not support, so it is required to comment.
        
-
        
-
        .IF ERRORCODE and .QUIT
        BTEQ statements specified with .IF and .QUIT.
        
-
        
-
        Input
        
-
        COLLECT STATISTICS 
- USING SAMPLE 5.00 PERCENT 
- COLUMN ( CDR_TYPE_KEY ) , 
- COLUMN ( PARTITION ) , 
- COLUMN ( SRC ) , 
- COLUMN ( PARTITION,SBSCRPN_KEY ) 
- ON DT_SDM.FCT_OTGO_NTWK_ACTVY_DAILY ;
- 
-
        
-
        Output
        
-
        SET
-default_statistics_target = 5.00 ;
-ANALYZE DT_SDM.FCT_OTGO_NTWK_ACTVY_DAILY (CDR_TYPE_KEY) ;
-ANALYZE DT_SDM.FCT_OTGO_NTWK_ACTVY_DAILY (PARTITION) ;
-ANALYZE DT_SDM.FCT_OTGO_NTWK_ACTVY_DAILY (SRC) ;
-ANALYZE DT_SDM.FCT_OTGO_NTWK_ACTVY_DAILY (PARTITION,SBSCRPN_KEY) ;
- RESET default_statistics_target ;
        
-
        .IF
        Input:
        
-
        .IF END_MONTH_FLAG <> 'Y' THEN .GOTO LABEL_1; 
        
-
        Output:
        
-
        IF END_MONTH_FLAG <> 'Y' THEN
-               GOTO LABEL_1 ;
-END IF ;
        
-
        
-
        .QUIT
        Input:
        
-
        .IF ERRORCODE <> 0 THEN .QUIT 12;
        
-
        Output:
        
-
        IF ERRORCODE <> 0 THEN
-          RAISE EXCEPTION '12' ;
-END IF;
        
-
        
-
        .IF & .QUIT
        .IF and .QUIT should be moved inside the block.
        
-
        
-
-
        
-
-
-
-
-
-
-
-
        Oracle Syntax
        
-
        Syntax After Migration
        
-
        INSERT INTO EMP 
-SELECT * FROM EMP;
-.IF ERRORCODE <> 0 THEN .QUIT 12;
        
-
        DECLARE 
-lv_mig_errorcode NUMBER ( 4 ) ;
-BEGIN
-     BEGIN
-      INSERT INTO EMP 
-     SELECT * FROM EMP;
-     lv_mig_errorcode := 0 ;
-      EXCEPTION
-          WHEN OTHERS THEN
-           lv_mig_errorcode := - 1 ;
-     END ;
-     IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12' ;
-     END IF ;
- END ;
-/
        
-
        
-
        
-
        .RETURN
        Input:
        
-
        .if ERRORCODE = 0 then .RETURN; 
        
-
        Output:
        
-
        IF ERRORCODE = 0 THEN
-          RETURN;
-END IF;
        
-
        
-
        .GOTO
        Input:
        
-
        .IF END_MONTH_FLAG <> 'Y' THEN .GOTO LABEL_1; 
        
-
        Output:
        
-
        IF END_MONTH_FLAG <> 'Y' THEN
-      GOTO LABEL_1;
-END IF ;
        
-
        
-
        Label
        Input:
        
-
        .LABEL LABEL_1
        
-
        Output:
        
-
        <<LABEL_1>>
        
-
        
-
        ERRORCODE 3807
        Input:
        
-
        SELECT end_mon AS END_MONTH_FLAG
-  FROM tab2 ;
-
-.IF END_MONTH_FLAG <> 'Y' THEN
-        .GOTO LABEL_1;
-
-.IF ERRORCODE = 3807 THEN 
-       .QUIT 8888;
        
-
        Output
        
-
        DECLARE lv_mig_errorcode NUMBER (4);
-      lv_mig_END_MONTH_FLAG TEXT;
-BEGIN
-     BEGIN
-          SELECT end_mon 
-             INTO lv_mig_END_MONTH_FLAG
-            FROM tab2 ;
-
-            lv_mig_errorcode := 0 ;
-     EXCEPTION
-           WHEN UNDEFINED_TABLE THEN
-                 lv_mig_errorcode := 3807 ;
-
-          WHEN OTHERS THEN
-               lv_mig_errorcode := - 1 ;
-     END ;
-
-     IF lv_mig_END_MONTH_FLAG <> 'Y' THEN
-               GOTO LABEL_1 ;
-     END IF ;
-     IF lv_mig_errorcode = 3807 THEN
-          RAISE EXCEPTION '8888' ;
-     END IF ;
-END;
-/
        
-
        
-
        BT with BTEQ commands
        Input
        
-
        BT;
-
-delete from ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL 
-where DW_Job_Seq = ${v_Group_No};
-
-.if ERRORCODE <> 0 then .quit 12;
-
-insert into ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL 
-(
-   Cust_Id
-  ,Cust_UID
-  ,DW_Upd_Dt
-  ,DW_Upd_Tm
-  ,DW_Job_Seq
-  ,DW_Etl_Dt
-)
-select
-   a.Cust_Id
-  ,a.Cust_UID
-  ,current_date as Dw_Upd_Dt
-  ,current_time(0) as DW_Upd_Tm
-  ,cast(${v_Group_No} as byteint) as DW_Job_Seq
-  ,cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_Etl_Dt
-from ${BRTL_VCOR}.BRTL_CS_CUST_CID_UID_REL_S a
-where a.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd');
-
-.if ERRORCODE <> 0 then .quit 12;
-
        
-
        Output
        
-
        BEGIN
---    
-   BEGIN          
-      delete from ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL  
-       where DW_Job_Seq = ${v_Group_No};
-         lv_mig_errorcode = 0;
-   EXCEPTION
-      WHEN OTHERS THEN
-         lv_mig_errorcode = -1;
-   END;
-
-   IF lv_mig_errorcode <> 0 THEN
-        RAISE EXCEPTION '12';
-   END IF;
        
-
        
-
        ET with BTEQ Commands
        Input
        
-
        ET;
-BEGIN
-
-   BEGIN          
-      delete from ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL  
-       where DW_Job_Seq = ${v_Group_No};
-         lv_mig_errorcode = 0;
-   EXCEPTION
-      WHEN OTHERS THEN
-         lv_mig_errorcode = -1;
-   END;
-
-   IF lv_mig_errorcode <> 0 THEN
-        RAISE EXCEPTION '12';
-   END IF;
-
-
-   BEGIN
-        insert into ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL 
-        (
-          Cust_Id
-         ,Cust_UID
-         ,DW_Upd_Dt
-         ,DW_Upd_Tm
-         ,DW_Job_Seq
-         ,DW_Etl_Dt
-       )
-      select
-          a.Cust_Id
-         ,a.Cust_UID
-         ,current_date as Dw_Upd_Dt
-         ,current_time(0) as DW_Upd_Tm
-         ,cast(${v_Group_No} as byteint) as DW_Job_Seq
-         ,cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_Etl_Dt
-       from ${BRTL_VCOR}.BRTL_CS_CUST_CID_UID_REL_S a
-     where a.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd');
-   EXCEPTION
-      WHEN OTHERS THEN
-         lv_mig_errorcode = -1;
-   END;
-
-   IF lv_mig_errorcode <> 0 THEN
-        RAISE EXCEPTION '12';
-   END IF;
-
-END;
        
-
        Output
        
-
        
-
        --     
-   BEGIN
-        insert into ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL 
-        (
-          Cust_Id
-         ,Cust_UID
-         ,DW_Upd_Dt
-         ,DW_Upd_Tm
-         ,DW_Job_Seq
-         ,DW_Etl_Dt
-       )
-      select
-          a.Cust_Id
-         ,a.Cust_UID
-         ,current_date as Dw_Upd_Dt
-         ,current_time(0) as DW_Upd_Tm
-         ,cast(${v_Group_No} as byteint) as DW_Job_Seq
-         ,cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_Etl_Dt
-       from ${BRTL_VCOR}.BRTL_CS_CUST_CID_UID_REL_S a
-     where a.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd');
-   EXCEPTION
-      WHEN OTHERS THEN
-         lv_mig_errorcode = -1;
-   END;
-
-   IF lv_mig_errorcode <> 0 THEN
-        RAISE EXCEPTION '12';
-   END IF;
-
-END;
        
-
        .Export FILE
        .EXPORT FILE should be changed to COPY and teradata utilities is set to false.
        
-
        
-
-
        
-
-
-
-
-
-
-
-
        Oracle Syntax
        
-
        Syntax After Migration
        
-
        .export file = $FILENAME;
-select empno, ename from emp where deptno = 1;
        
-
        COPY (select empno, ename from emp where deptno = 1) TO '$FILENAME' CSV HEADER DELIMITER E'\t';
        
-
        
-
        
-
        .EXPORT FILE should be changed to $q$COPY and moved inside the block when teradataUtilities is set to true.
        
-
-
        
-
-
-
-
-
-
-
-
        Oracle Syntax
        
-
        Syntax After Migration
        
-
        print BTEQ <<ENDOFINPUT;
-   DATABASE HPBUS;
-.export file = $FILENAME;
-select empno, ename from emp where deptno = 1;
-.IF ERRORCODE <> 0 THEN .QUIT 12;
-.LOGOFF;
-.QUIT 0;
-ENDOFINPUT
        
-
        DECLARE lv_mig_obj_exists_check NUMBER(1);
- lv_mig_errorcode NUMBER(4);
-BEGIN
- SET SESSION CURRENT_SCHEMA TO public ;
-
-    BEGIN
-  SELECT COUNT(*) INTO lv_mig_obj_exists_check
-    FROM (select empno, ename from emp where deptno = 1);
-        lv_mig_errorcode := 0;
-
-    EXCEPTION
-        WHEN OTHERS THEN
-            lv_mig_errorcode := -1;
-    END ;
- EXECUTE $q$COPY (select empno, ename from emp where deptno = 1) TO '$FILENAME' CSV HEADER DELIMITER E'\t'$q$;
-
-    IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12';
-    END IF ;
- RAISE EXCEPTION '-99';
-    RETURN ;
-END ;
-/
        
-
        
-
        
-
        SQL_Lang & BTEQ
        Multiple tag names should be handled for SQL_Lang.
        
-
        
-
-
        
-
-
-
-
-
-
-
-
        Oracle Syntax
        
-
        Syntax After Migration
        
-
        #!/usr/bin/perl
-######################################################################
-# BTEQ script in Perl
-# Date Time    : 2013-10-15
-# Table        : TB_NET_LTE_GPRS_CDR (4G GPRS»°µ¥)
-# Script Name  : XXX00_TB_NET_LTE_GPRS_CDR
-# Source Table :  TB_04024-GPRS
-# Load strategy: S4
-use strict; # Declare using Perl strict syntax
-
-my $HOME = $ENV{"AUTO_HOME"};
-unshift(@INC, "$HOME/bin");
-require etl_pub;   
-
-# ------------ Variable Section ------------
-# DATABASE NAMES
-my $TEMPDB = $ETL::TEMPDB;
-my $SDATADB = $ETL::SDATADB;
-my $PDATADB = $ETL::PDATADB;
-my $PARADB = $ETL::PARADB;
-my $PDDL = $ETL::PDDL;
-
-my $PCODE = $ETL::PCODE;
-if ( $#ARGV < 0 ) {
-   exit(1);
-}
-my $CONTROL_FILE = $ARGV[0];
-my $TX_DATE = substr(${CONTROL_FILE},length(${CONTROL_FILE})-12, 8);
-
-open(STDERR, ">&STDOUT");
-my $TRG_COL_LIST =<<TRGCOLLIST;
- MSISDN
-,dat_rcd_dt
-,vst_rgn_cd
-
-TRGCOLLIST
-
-my $MAP_COL_LIST =<<MAPCOLLIST;
- TB_04024.msisdn
- ,CAST('$TX_DATE' AS DATE FORMAT 'YYYYMMDD')
- ,TB_04024.vst_rgn_cd
-MAPCOLLIST
-
-my $FILTER = "CMCC_Prov_Prvd_Id=$PCODE";
-my $table_today ="${TEMPDB}.TB_04024_${PCODE}";
-my $table_target = "Z" . substr($PCODE,1,2) . "NET_LTE_GPRS_CDR";
-my $UNIT_FLAG;
-
-sub BTEQ_S4
-{
- my ($dbh) = @_;
- my $BTEQ_CMD_S4 = <<ENDOFINPUT;
-
-INSERT INTO ${PDATADB}.$table_target (
-$TRG_COL_LIST)
-SELECT
-$MAP_COL_LIST
-FROM $SDATADB.TB_${PCODE}_04024_${UNIT_FLAG}_${TX_DATE} TB_04024;
-.IF ERRORCODE <> 0 THEN .QUIT 12;
-ENDOFINPUT
- return $BTEQ_CMD_S4;
-}
-my $unit_num = "04024";
-
-sub BTEQ_Z1
-{
- my $BTEQ_CMD_Z1 = <<ENDOFINPUT;
-INSERT INTO ${PDATADB}.$table_target (
-$TRG_COL_LIST)
-SELECT 
-$MAP_COL_LIST
-FROM $SDATADB.TB_${PCODE}_${unit_num}_${UNIT_FLAG}_${TX_DATE} tb_${unit_num}; 
-.IF ERRORCODE <> 0 THEN .QUIT 12;
-ENDOFINPUT
- return $BTEQ_CMD_Z1;
-}
-
-sub main()
-{
- my $dbh=ETL::DBconnect();
-# SDATA 
- $UNIT_FLAG = ETL::get_UNIT_FLAG($dbh, "TB_04024", $PCODE, $TX_DATE);
- my $BTEQCMD = "";
- if ( $UNIT_FLAG eq " " ) {
-  print "Ô!\n";
-  ETL::disconnectETL($dbh);
-  return 1;
- } elsif ($UNIT_FLAG eq "S") {
-  $BTEQCMD = BTEQ_S4($dbh);
- } elsif ($UNIT_FLAG eq "Z") {
-  $BTEQCMD = BTEQ_Z1($dbh);
- } else {
-  print "\n";
-  return 1;
- }
- ETL::disconnectETL($dbh);
-
- return ETL::ExecuteBTEQ($BTEQCMD, $TX_DATE);
-}
-my $ret= main();
-exit($ret); 
-
        
-
        #!/usr/bin/perl
-######################################################################
-# BTEQ script in Perl
-# Date Time    : 2013-10-15
-# Table        : TB_NET_LTE_GPRS_CDR (4G GPRS)
-# Script Name  : XXX00_TB_NET_LTE_GPRS_CDR
-# Source Table :  TB_04024-GPRS
-# Load strategy: S4
-use strict; # Declare using Perl strict syntax
-
-my $HOME = $ENV{"AUTO_HOME"};
-unshift(@INC, "$HOME/bin");
-require etl_pub;    
-
-# ------------ Variable Section ------------
-# DATABASE NAMES
-my $TEMPDB = $ETL::TEMPDB;
-my $SDATADB = $ETL::SDATADB;
-my $PDATADB = $ETL::PDATADB;
-my $PARADB = $ETL::PARADB;
-my $PDDL = $ETL::PDDL;
-
-my $PCODE = $ETL::PCODE;
-if ( $#ARGV < 0 ) {
-   exit(1);
-}
-my $CONTROL_FILE = $ARGV[0];
-my $TX_DATE = substr(${CONTROL_FILE},length(${CONTROL_FILE})-12, 8);
-
-open(STDERR, ">&STDOUT");
-my $TRG_COL_LIST=<<TRGCOLLIST ;
-MSISDN
-,dat_rcd_dt
-,vst_rgn_cd
-
-TRGCOLLIST
-
-my $MAP_COL_LIST=<<MAPCOLLIST ;
-TB_04024.msisdn
-,CAST( '$TX_DATE' AS DATE )
-,TB_04024.vst_rgn_cd
-MAPCOLLIST
-
-my $FILTER = "CMCC_Prov_Prvd_Id=$PCODE";
-my $table_today ="${TEMPDB}.TB_04024_${PCODE}";
-my $table_target = "Z" . substr($PCODE,1,2) . "NET_LTE_GPRS_CDR";
-my $UNIT_FLAG;
-
-
-sub BTEQ_S4
-{
- my ($dbh) = @_;
-my $BTEQ_CMD_S4=<<ENDOFINPUT ;
-
-DECLARE lv_mig_obj_exists_check NUMBER ( 1 ) ;
-lv_mig_errorcode NUMBER ( 4 ) ;
-
-BEGIN
-
-
-    
-     BEGIN
-          INSERT INTO ${PDATADB}.$table_target ($TRG_COL_LIST)
-          SELECT
-                    $MAP_COL_LIST
-               FROM
-                    $SDATADB.TB_${PCODE}_04024_${UNIT_FLAG}_${TX_DATE} TB_04024 ;
-                    lv_mig_errorcode := 0 ;
-
-               EXCEPTION
-                    WHEN OTHERS THEN
-                    lv_mig_errorcode := - 1 ;
-
-     END ;
-     IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12' ;
-
-     END IF ;
-
-END ;
-/
-ENDOFINPUT
- return $BTEQ_CMD_S4;
-}
-my $unit_num = "04024";
-
-sub BTEQ_Z1
-{
-my $BTEQ_CMD_Z1=<<ENDOFINPUT ;
-
-DECLARE lv_mig_obj_exists_check NUMBER ( 1 ) ;
-lv_mig_errorcode NUMBER ( 4 ) ;
-
-     BEGIN
-          INSERT INTO ${PDATADB}.$table_target ($TRG_COL_LIST)
-          SELECT
-                    $MAP_COL_LIST
-               FROM
-                    $SDATADB.TB_${PCODE}_${unit_num}_${UNIT_FLAG}_${TX_DATE} tb_${unit_num} ;
-                    lv_mig_errorcode := 0 ;
-
-               EXCEPTION
-                    WHEN OTHERS THEN
-                    lv_mig_errorcode := - 1 ;
-
-     END ;
-     IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12' ;
-
-     END IF ;
-
-END ;
-/
-ENDOFINPUT
- return $BTEQ_CMD_Z1;
-}
-
-sub main()
-{
- my $dbh=ETL::DBconnect();
-# SDATA 
- $UNIT_FLAG = ETL::get_UNIT_FLAG($dbh, "TB_04024", $PCODE, $TX_DATE);
- my $BTEQCMD = "";
- if ( $UNIT_FLAG eq " " ) {
-  print "!\n";
-  ETL::disconnectETL($dbh);
-  return 1;
- } elsif ($UNIT_FLAG eq "S") {
-  $BTEQCMD = BTEQ_S4($dbh);
- } elsif ($UNIT_FLAG eq "Z") {
-  $BTEQCMD = BTEQ_Z1($dbh);
- } else {
-  print "¸\n";
-  return 1;
- }
- ETL::disconnectETL($dbh);
-
- return ETL::ExecuteBTEQ($BTEQCMD, $TX_DATE);
-}
-my $ret= main();
-exit($ret); 
-
        
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: Teradata Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8121.html b/docs/dws/tool/dws_07_8121.html
deleted file mode 100644
index d25d1d63..00000000
--- a/docs/dws/tool/dws_07_8121.html
+++ /dev/null
@@ -1,303 +0,0 @@
-
-
-
        DSQL
        
-
        DSQL Variable: With AS
        Input
        
-
        
-
        /* VARIABLE INPUT */
-select cast(cast('${TX_DATE}' as date format 'yyyymmdd') as date format 'yyyy-mm-dd') as v_Trx_Dt;
-.IF ERRORCODE <> 0 THEN .QUIT 12 ;
-
-insert into VT_RTL_ACT_ORG_INF          /* VT_         */
-(
-   Act_Id          /*      */
-  ,Act_Mdf          /*       */
-  ,Act_Agr_Typ_Cd          /*          */
-  ,Opn_BBK          /*      */
-  ,Opn_BRN          /*      */
-)
-select 
-   a.Agr_Id as Act_Id          /*      */
-  ,a.Agr_Mdf as Act_Mdf          /*       */
-  ,a.Agr_Typ_Cd as Act_Agr_Typ_Cd          /*          */
-  ,a.BBK_Org_Id as Opn_BBK          /*      */
-  ,a.Opn_Org_Id as Opn_BRN          /*      */
-from ${PDM_VIEW}.T03_AGR_TRSR_BND_ACT as a          /*   _     */
-where  a.DW_Start_Dt <= cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd')          
-           AND a.DW_End_Dt > cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd')          
-           AND a.Agr_Typ_Cd IN ('20301')          /*      */
-;
-.IF ERRORCODE <> 0 THEN .QUIT 12 ;
        
-
        Output
        
-
        DECLARE lv_mig_obj_exists_check    NUMBER ( 1 ) ;
- lv_mig_errorcode           NUMBER ( 4 ) ;
- lv_mig_v_Trx_Dt            TEXT ;
-
-BEGIN
-      /*VARIABLE INPUT */
-     BEGIN
-          SELECT CAST( CAST( '${TX_DATE}' AS DATE ) AS DATE ) 
-     INTO lv_mig_v_Trx_Dt ;
-
-   lv_mig_errorcode := 0 ;
-
-     EXCEPTION
-          WHEN OTHERS THEN
-              lv_mig_errorcode := -1;
-
-     END;
-     IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12' ;
-     END IF ;
-
-     BEGIN
-          INSERT INTO VT_RTL_ACT_ORG_INF /* VT_         */
-          (
-               Act_Id /*      */
-               ,Act_Mdf /*       */
-               ,Act_Agr_Typ_Cd /*          */
-               ,Opn_BBK /*      */
-               ,Opn_BRN /*      */
-          )
-          SELECT     a.Agr_Id AS Act_Id /*      */
-                    ,a.Agr_Mdf AS Act_Mdf /*       */
-                    ,a.Agr_Typ_Cd AS Act_Agr_Typ_Cd /*          */
-                    ,a.BBK_Org_Id AS Opn_BBK /*      */
-                    ,a.Opn_Org_Id AS Opn_BRN /*      */
-               FROM ${PDM_VIEW}.T03_AGR_TRSR_BND_ACT AS a /*   _     */
-              WHERE a.DW_Start_Dt <= CAST( lv_mig_v_Trx_Dt AS DATE )
-                    AND a.DW_End_Dt > CAST( lv_mig_v_Trx_Dt AS DATE )
-                    AND a.Agr_Typ_Cd IN ( '20301' ) /*      */
-                    ;
-                    lv_mig_errorcode := 0 ;
-
-     EXCEPTION
-          WHEN OTHERS THEN
-              lv_mig_errorcode := -1;
-
-     END ;
-     IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12' ;
-     END IF ;
-
-END ;
-/
        
-
        DSQL Variable: Without AS
        Input
        
-
        
-
        /* SESSION INPUT */
-select Session ;
-.IF ERRORCODE <> 0 THEN .QUIT 12 ;
-
-select username,clientsystemuserid,clientipaddress,clientprogramname 
-  from dbc.sessioninfoV 
- where sessionno = '$Session' ;
-.IF ERRORCODE <> 0 THEN .QUIT 12 ;
        
-
        Output
        
-
        DECLARE lv_mig_obj_exists_check    NUMBER ( 1 ) ;
- lv_mig_errorcode           NUMBER ( 4 ) ;
- lv_mig_Session             TEXT ;
-
-BEGIN
-    /*SESSION INPUT */
-     BEGIN
-          SELECT pg_backend_pid ( ) 
-     INTO lv_mig_Session ;
-
-   lv_mig_errorcode := 0 ;
-
-     EXCEPTION
-         WHEN OTHERS THEN
-            lv_mig_errorcode := - 1 ;          
-     END ;
-
-     IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12' ;
-     END IF ;
-
-     BEGIN
-          SELECT COUNT( * ) INTO lv_mig_obj_exists_check
-            FROM ( SELECT username
-                         ,clientsystemuserid
-                         ,clientipaddress
-                         ,clientprogramname
-                    FROM dbc.sessioninfoV
-                   WHERE sessionno = lv_mig_Session ) 
-     LIMIT 1 ;
-
-     lv_mig_errorcode := 0 ;
-
-     EXCEPTION
-         WHEN OTHERS THEN
-             lv_mig_errorcode := - 1 ;          
-     END ;
-
-     IF lv_mig_errorcode <> 0 THEN
-          RAISE EXCEPTION '12' ;
-     END IF ;
-
-END ;
-/
        
-
        Specifying Variables in BTEQ Statements
        Input
        
-
        select case when cast('${v_Trx_Dt}' as date format'yyyy-mm-dd') = cast('${v_Tx_Mon_End_Date}' as date format'yyyy-mm-dd')         then '0'         else '1' end  as v_IsLastDay;
-.IF ERRORCODE <> 0 THEN .QUIT 12 ;
-insert into VT_AS_CUST_WLTH_GRP          /* VT_       */
-(
-   Cust_UID          /*   UID */
-  ,BBK_Org_Id          /*        */
-  ,Wlth_grp_Cd          /*        */
-  ,Card_Grd_Cd          /*      */
-)
-select 
-   a.Cust_UID as Cust_UID          /*   UID */
-  ,a.BBK_Org_Id as BBK_Org_Id          /*        */
-  ,'11' as Wlth_grp_Cd          /*        */
-  ,coalesce(b.Card_Grd_Cd,'') as Card_Grd_Cd          /*      */
-from VT_CUST_WLTH_GRP_LAST as a          /* VT_           */
-LEFT OUTER JOIN ${BRTL_VEXT}.BRTL_AS_CUST_CARD_GRD_S as b          /* AS_         */
-  on  b.Cust_Uid = a.Cust_Uid          
-  AND b.BBK_Org_Id = a.BBK_Org_Id          
-  AND b.Card_Sts_Scp_Cd = '001'          /* 001-         */
-  AND b.Card_Grd_Cd IN ('080','060','040','020','010','000')          
-  AND b.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format'yyyy-mm-dd')          
-where  b.Cust_UID IS null          
-;
-.IF v_IsLastDay = 1 THEN .GOTO doit
        
-
        Output
        
-
        
-
        BEGIN
-    select case when cast('${v_Trx_Dt}' as date format'yyyy-mm-dd') = cast('${v_Tx_Mon_End_Date}' as date format'yyyy-mm-dd')     then '0'         else '1' end  INTO lv_mig_v_IsLastDay;
-      lv_mig_ERRORCODE = 0;
-EXCEPTION
-    WHEN OTHERS THEN
-        lv_mig_ERRORCODE = -1;
-END;
-IF lv_mig_ERRORCODE <> 0 THEN 
-  RAISE EXCEPTION '12';
-END IF;
-
-insert into VT_AS_CUST_WLTH_GRP          /* VT_       */
-(
-   Cust_UID          /*   UID */
-  ,BBK_Org_Id          /*        */
-  ,Wlth_grp_Cd          /*        */
-  ,Card_Grd_Cd          /*      */
-)
-select 
-   a.Cust_UID as Cust_UID          /*   UID */
-  ,a.BBK_Org_Id as BBK_Org_Id          /*        */
-  ,'11' as Wlth_grp_Cd          /*        */
-  ,coalesce(b.Card_Grd_Cd,'') as Card_Grd_Cd          /*      */
-from VT_CUST_WLTH_GRP_LAST as a          /* VT_           */
-LEFT OUTER JOIN ${BRTL_VEXT}.BRTL_AS_CUST_CARD_GRD_S as b          /* AS_         */
-  on  b.Cust_Uid = a.Cust_Uid          
-  AND b.BBK_Org_Id = a.BBK_Org_Id          
-  AND b.Card_Sts_Scp_Cd = '001'          /* 001-         */
-  AND b.Card_Grd_Cd IN ('080','060','040','020','010','000')          
-  AND b.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format'yyyy-mm-dd')          
-where  b.Cust_UID IS null          
-;
-IF lv_mig_v_IsLastDay = 1 THEN 
-           GOTO doit;
-END IF;
-
        
-
        Specifying Variables Using SELECT EXTRACT FROM
        Input
        
-
        select EXTRACT (MONTH FROM cast('${TX_DATE}' as  date format 'YYYYMMDD')) as CURR_MON;
-.if ERRORCODE <> 0 then .quit 12;
---    
-.IF CURR_MON <> 1 THEN .goto NON_JAN;
-.if ERRORCODE <> 0 then .quit 12;
        
-
        Output
        
-
        BEGIN
-   select EXTRACT (MONTH FROM cast('${TX_DATE}' as  date format 'YYYYMMDD')) INTO CURR_MON;
-…
-END;
-…
        
-
        
-
        DATE Type Casting: Specifying DSQL Variables
        Input
        
-
        select 
-   case when a.DW_Stat_Dt in 
-(date'${v_Tx_Pre_1_Mon_End_Date}'
-,date'${v_Tx_Pre_2_Mon_End_Date}'
-,date'${v_Tx_Pre_3_Mon_End_Date}')
-then '1' else '2' end as Quarter_Flg          /* PK-     1--    2--     3--   */
-  ,a.BBK_Org_Id as BBK_Org_Id          /* PK-         */
-  ,a.Cust_UID as Cust_UID          /* PK-  UID */
-  ,a.Entp_Cust_Id as Entp_Cust_Id          /* PK-       */
-  ,coalesce(b.BBK_Nbr,'') as Agn_BBK_Org_Id          /* PK-       */
-from ${BRTL_VEXT}.BRTL_AS_AGN_ENTP_CUID_TRX_SR as a          /* AS_      UID     */
-LEFT OUTER JOIN ${BRTL_VCOR}.BRTL_OR_RTL_ORG_INF_S as b          /* OR_         */
-  on  a.Agn_BRN_Org_Id = b.Rtl_Org_Id  
-and b.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd')          
-where  a.DW_Stat_Dt IN (date'${v_Tx_Pre_1_Mon_End_Date}'
-,date'${v_Tx_Pre_2_Mon_End_Date}'
-,date'${v_Tx_Pre_3_Mon_End_Date}'
-,date'${v_Tx_Pre_4_Mon_End_Date}'
-,date'${v_Tx_Pre_5_Mon_End_Date}'
-,date'${v_Tx_Pre_6_Mon_End_Date}')          
-           AND a.Stat_Prd_Cd = 'M001'          
-group by Quarter_Flg, a.BBK_Org_Id, a.Cust_UID, a.Entp_Cust_Id, coalesce(b.BBK_Nbr,'')        
-;
-should be migrated as below:
-           SELECT
-                     CASE WHEN a.DW_Stat_Dt IN 
-        ( CAST(lv_mig_v_Tx_Pre_1_Mon_End_Date AS DATE)
-                      , CAST(lv_mig_v_Tx_Pre_2_Mon_End_Date AS DATE)
-                      , CAST(lv_mig_v_Tx_Pre_3_Mon_End_Date AS DATE) )
-                          THEN '1'
-                        ELSE '2'
-                     END AS Quarter_Flg /* PK-     1--    2--     3--   */
-                     ,a.BBK_Org_Id AS BBK_Org_Id /* PK-         */
-                     ,a.Cust_UID AS Cust_UID /* PK-  UID */
-                     ,a.Entp_Cust_Id AS Entp_Cust_Id /* PK-       */
-                     ,COALESCE( b.BBK_Nbr ,'' ) AS Agn_BBK_Org_Id /* PK-       */
-                FROM
-                     BRTL_VEXT.BRTL_AS_AGN_ENTP_CUID_TRX_SR AS a /* AS_      UID     */
-                     LEFT OUTER JOIN BRTL_VCOR.BRTL_OR_RTL_ORG_INF_S AS b /* OR_         */
-                          ON a.Agn_BRN_Org_Id = b.Rtl_Org_Id
-                     AND b.DW_Snsh_Dt = CAST( lv_mig_v_Trx_Dt AS DATE )
-                WHERE
-                     a.DW_Stat_Dt IN ( CAST(lv_mig_v_Tx_Pre_1_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_2_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_3_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_4_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_5_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_6_Mon_End_Date AS DATE) )
-                     AND a.Stat_Prd_Cd = 'M001'
-                GROUP BY Quarter_Flg, a.BBK_Org_Id, a.Cust_UID, a.Entp_Cust_Id, COALESCE( b.BBK_Nbr ,'' ) 
-  ;
        
-
        Output
        
-
        
-
         SELECT
-                     CASE WHEN a.DW_Stat_Dt IN 
-        ( CAST(lv_mig_v_Tx_Pre_1_Mon_End_Date AS DATE)
-                      , CAST(lv_mig_v_Tx_Pre_2_Mon_End_Date AS DATE)
-                      , CAST(lv_mig_v_Tx_Pre_3_Mon_End_Date AS DATE) )
-                          THEN '1'
-                        ELSE '2'
-                     END AS Quarter_Flg /* PK-     1--    2--     3--   */
-                     ,a.BBK_Org_Id AS BBK_Org_Id /* PK-         */
-                     ,a.Cust_UID AS Cust_UID /* PK-  UID */
-                     ,a.Entp_Cust_Id AS Entp_Cust_Id /* PK-       */
-                     ,COALESCE( b.BBK_Nbr ,'' ) AS Agn_BBK_Org_Id /* PK-       */
-                FROM
-                     BRTL_VEXT.BRTL_AS_AGN_ENTP_CUID_TRX_SR AS a /* AS_      UID     */
-                     LEFT OUTER JOIN BRTL_VCOR.BRTL_OR_RTL_ORG_INF_S AS b /* OR_         */
-                          ON a.Agn_BRN_Org_Id = b.Rtl_Org_Id
-                     AND b.DW_Snsh_Dt = CAST( lv_mig_v_Trx_Dt AS DATE )
-                WHERE
-                     a.DW_Stat_Dt IN ( CAST(lv_mig_v_Tx_Pre_1_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_2_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_3_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_4_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_5_Mon_End_Date AS DATE)
-                     ,CAST(lv_mig_v_Tx_Pre_6_Mon_End_Date AS DATE) )
-                     AND a.Stat_Prd_Cd = 'M001'
-                GROUP BY Quarter_Flg, a.BBK_Org_Id, a.Cust_UID, a.Entp_Cust_Id, COALESCE( b.BBK_Nbr ,'' ) 
-  ;
        
-
        
-
        
-
        
-
        
-
        Parent topic: Teradata Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8310.html b/docs/dws/tool/dws_07_8310.html
deleted file mode 100644
index b97476fc..00000000
--- a/docs/dws/tool/dws_07_8310.html
+++ /dev/null
@@ -1,82 +0,0 @@
-
-
-
        Delete an Index
        
-
        MySQL supports both DROP INDEX and ALTER TABLE DROP INDEX for deleting indexes. DSC will perform adaptation based on GaussDB features during migration.
        
-
        1. DROP INDEX
          Input
          
-
          CREATE TABLE `test_create_table03` (
-	`DEMAND_ID` INT(11) NOT NULL,
-	`DEMAND_NAME` CHAR(100) NOT NULL,
-	`THEME` VARCHAR(200) NULL DEFAULT NULL,
-	`SEND_ID` INT(11) NULL DEFAULT NULL,
-	`SEND_NAME` CHAR(20) NULL DEFAULT NULL,
-	`SEND_TIME` DATETIME NULL DEFAULT NULL,
-	`DEMAND_CONTENT` TEXT NOT NULL
-)
-COLLATE='utf8_general_ci'
-ENGINE=InnoDB;
-
-CREATE UNIQUE INDEX DEMAND_NAME_INDEX ON TEST_CREATE_TABLE03(DEMAND_NAME);
-DROP INDEX DEMAND_NAME_INDEX ON TEST_CREATE_TABLE03;
-
-CREATE INDEX SEND_ID_INDEX ON TEST_CREATE_TABLE03(SEND_ID);
-DROP INDEX SEND_ID_INDEX ON TEST_CREATE_TABLE03;
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table03"
-(
-  "demand_id" INTEGER(11) NOT NULL,
-  "demand_name" CHAR(100) NOT NULL,
-  "theme" VARCHAR(200) DEFAULT NULL,
-  "send_id" INTEGER(11) DEFAULT NULL,
-  "send_name" CHAR(20) DEFAULT NULL,
-  "send_time" TIMESTAMP WITHOUT TIME ZONE DEFAULT NULL,
-  "demand_content" TEXT NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("demand_id");
-
-CREATE INDEX "demand_name_index" ON "public"."test_create_table03" ("demand_name");
-DROP INDEX "demand_name_index" RESTRICT;
-
-CREATE INDEX "send_id_index" ON "public"."test_create_table03" USING BTREE ("send_id");
-DROP INDEX "send_id_index" RESTRICT;
          
-
        2. ALTER TABLE DROP INDEX
          Input
          
-
          CREATE TABLE `test_create_table03` (
-	`DEMAND_ID` INT(11) NOT NULL,
-	`DEMAND_NAME` CHAR(100) NOT NULL,
-	`THEME` VARCHAR(200) NULL DEFAULT NULL,
-	`SEND_ID` INT(11) NULL DEFAULT NULL,
-	`SEND_NAME` CHAR(20) NULL DEFAULT NULL,
-	`SEND_TIME` DATETIME NULL DEFAULT NULL,
-	`DEMAND_CONTENT` TEXT NOT NULL
-)
-COLLATE='utf8_general_ci'
-ENGINE=InnoDB;
-
-ALTER TABLE TEST_CREATE_TABLE03 ADD UNIQUE INDEX TEST_CREATE_TABLE03_NAME_INDEX(DEMAND_NAME(50));
-ALTER TABLE TEST_CREATE_TABLE03 DROP INDEX TEST_CREATE_TABLE03_NAME_INDEX;
          
-
          Output
          
-
          CREATE TABLE "public"."test_create_table03"
-(
-  "demand_id" INTEGER(11) NOT NULL,
-  "demand_name" CHAR(100) NOT NULL,
-  "theme" VARCHAR(200) DEFAULT NULL,
-  "send_id" INTEGER(11) DEFAULT NULL,
-  "send_name" CHAR(20) DEFAULT NULL,
-  "send_time" TIMESTAMP WITHOUT TIME ZONE DEFAULT NULL,
-  "demand_content" TEXT NOT NULL
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("demand_id");
-
-CREATE INDEX "test_create_table03_name_index" ON "public"."test_create_table03" ("demand_name");
-DROP INDEX "test_create_table03_name_index" RESTRICT;
          
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8311.html b/docs/dws/tool/dws_07_8311.html
deleted file mode 100644
index fbb0a23c..00000000
--- a/docs/dws/tool/dws_07_8311.html
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
        Comments
        
-
        To comment out a single line, MySQL uses # or --, and GaussDB(DWS) uses --. DSC will replace # with -- for commenting out a single line during migration.
        
-
        Input
        
-
        ## comment sample create a table
-CREATE TABLE IF NOT EXISTS `public`.`runoob_tbl`(
-   `runoob_id` VARCHAR,
-   `runoob_title` VARCHAR(100) NOT NULL,
-   `runoob_author` VARCHAR(40) NOT NULL,
-   `submission_date` VARCHAR
-)ENGINE=InnoDB DEFAULT CHARSET=utf8;
        
-
        Output
        
-
        -- comment sample create a table
-CREATE TABLE "public"."runoob_tbl"
-(
-  "runoob_id" VARCHAR,
-  "runoob_title" VARCHAR(100) NOT NULL,
-  "runoob_author" VARCHAR(40) NOT NULL,
-  "submission_date" VARCHAR
-)
-  WITH ( ORIENTATION = ROW, COMPRESSION = NO )
-  NOCOMPRESS
-  DISTRIBUTE BY HASH ("runoob_id");
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8312.html b/docs/dws/tool/dws_07_8312.html
deleted file mode 100644
index 9d664331..00000000
--- a/docs/dws/tool/dws_07_8312.html
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
        Databases
        
-
        In MySQL, DATABASE is a schema object, which is equivalent to the SCHEMA of Oracle and GaussDB(DWS). DSC supports the following two scenarios:
        
-
        1. Database creation
          Input
          
-
          create database IF NOT EXISTS dbname1 CHARACTER SET=utf8 COLLATE=utf8_unicode_ci;
-create database IF NOT EXISTS dbname2;
-
-drop database if exists dbname1;
-drop database if exists dbname2;
          
-
          Output
          
-
          CREATE SCHEMA "dbname1";
-CREATE SCHEMA "dbname2";
-
-DROP SCHEMA IF EXISTS "dbname1";
-DROP SCHEMA IF EXISTS "dbname2";
          
-
        2. Database use
          Input
          
-
          drop database if exists test;
-create database if not exists test;
-use test;
          
-
          Output
          
-
          DROP SCHEMA IF EXISTS "test";
-CREATE SCHEMA "test";
-SET CURRENT_SCHEMA = "test";
          
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8313.html b/docs/dws/tool/dws_07_8313.html
deleted file mode 100644
index 0dd6d83a..00000000
--- a/docs/dws/tool/dws_07_8313.html
+++ /dev/null
@@ -1,287 +0,0 @@
-
-
-
        Data Manipulation Language (DML)
        
-
        This section describes the migration syntax of MySQL DML. The migration syntax determines how the keywords and features are migrated.
        
-
        For details, see the following topics:
        
-
-
        INSERT
        In MySQL, INSERT allows the following keywords: HIGH_PRIORITY, LOW_PRIORITY, PARTITION, DELAYED, IGNORE, VALUES, and ON DUPLICATE KEY UPDATE. GaussDB(DWS) does not support these keywords, and DSC will convert them.
        
-
        1. HIGH_PRIORITY
          MySQL uses HIGH_PRIORITY will override the effect of the LOW_PRIORITY option.
          
-
          Input
          
-
          # HIGH_PRIORITY 
-INSERT HIGH_PRIORITY INTO  exmp_tb2 VALUES(100, 12.3, 'cheap', '2018-11-11');
-INSERT HIGH_PRIORITY INTO  exmp_tb2 VALUES(DEFAULT, 128.23, 'nice', '2018-10-11');
-INSERT HIGH_PRIORITY INTO  exmp_tb2 VALUES(DEFAULT, DEFAULT, 'nice', '2018-12-14');
-INSERT HIGH_PRIORITY INTO  exmp_tb2 VALUES(DEFAULT, DEFAULT, 'nice', DEFAULT);
-INSERT HIGH_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price) VALUES(DEFAULT, DEFAULT);
-INSERT HIGH_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note) VALUES(DEFAULT, DEFAULT, DEFAULT);
-INSERT HIGH_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price , tb2_note) VALUES(DEFAULT, DEFAULT, DEFAULT);
-INSERT HIGH_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note, tb2_date) VALUES(DEFAULT, DEFAULT, DEFAULT, DEFAULT);
          
-
          Output
          
-
          -- HIGH_PRIORITY 
-INSERT INTO "public"."exmp_tb2"  VALUES (100,12.3,'cheap','2018-11-11');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,128.23,'nice','2018-10-11');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice','2018-12-14');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice',DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (DEFAULT,DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (DEFAULT,DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note","tb2_date") VALUES (DEFAULT,DEFAULT,DEFAULT,DEFAULT);
          
-
        2. LOW_PRIORITY
          When the LOW_PRIORITY modifier is used, execution of INSERT is delayed.
          
-
          Input
          
-
          # LOW_PRIORITY 
-INSERT LOW_PRIORITY INTO  exmp_tb2 VALUES( DEFAULT, '128.23', 'nice', '2018-10-11');
-INSERT LOW_PRIORITY INTO  exmp_tb2 VALUES(DEFAULT, DEFAULT, 'nice', '2018-12-14' );
-INSERT LOW_PRIORITY INTO  exmp_tb2 VALUES(DEFAULT, DEFAULT, 'nice', DEFAULT);
-INSERT LOW_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price) VALUES(DEFAULT, DEFAULT);
-INSERT LOW_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note) VALUES(DEFAULT, DEFAULT, DEFAULT);
          
-
          Output
          
-
          -- LOW_PRIORITY 
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,'128.23','nice','2018-10-11');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice','2018-12-14');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice',DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (DEFAULT,DEFAULT,DEFAULT);
          
-
        3. PRATITION
          When inserting into a partitioned table, you can control which partitions and subpartitions accept new rows.
          
-
          Input
          
-
          INSERT INTO employees PARTITION(p3) VALUES (19, 'Frank1', 'Williams', 1, 2);
-INSERT INTO employees PARTITION(p0) VALUES (4, 'Frank1', 'Williams', 1, 2);
-INSERT INTO employees PARTITION(p1) VALUES (9, 'Frank1', 'Williams', 1, 2);
-INSERT INTO employees PARTITION(p2) VALUES (10, 'Frank1', 'Williams', 1, 2);
-INSERT INTO employees PARTITION(p2) VALUES (11, 'Frank1', 'Williams', 1, 2);
          
-
          Output
          
-
          INSERT INTO "public"."employees"  VALUES (19,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (4,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (9,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (10,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (11,'Frank1','Williams',1,2);
          
-
        4. DELAYED
           
          In MySQL 5.7, the DELAYED keyword is recognized but ignored by the server.
          
-
          
-
          Input
          
-
          # DELAYED 
-INSERT DELAYED INTO  exmp_tb2 VALUES(99, 15.68, 'good', '2018-11-12');
-INSERT DELAYED INTO  exmp_tb2 VALUES(80, 12.3, 'cheap', '2018-11-11');
-INSERT DELAYED INTO  exmp_tb2 VALUES(DEFAULT, 128.23, 'nice', '2018-10-11');
-INSERT DELAYED INTO  exmp_tb2 VALUES(DEFAULT, DEFAULT, 'nice', '2018-12-14');
-INSERT DELAYED INTO  exmp_tb2 VALUES(DEFAULT, DEFAULT, 'nice', DEFAULT);
-INSERT DELAYED INTO  exmp_tb2 (tb2_id, tb2_price) VALUES(DEFAULT, DEFAULT);
-INSERT DELAYED INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note) VALUES(DEFAULT, DEFAULT, DEFAULT);
-INSERT DELAYED INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note, tb2_date) VALUES(DEFAULT, DEFAULT, DEFAULT, DEFAULT);
          
-
          Output
          
-
          -- DELAYED 
-INSERT INTO "public"."exmp_tb2"  VALUES (99,15.68,'good','2018-11-12');
-INSERT INTO "public"."exmp_tb2"  VALUES (80,12.3,'cheap','2018-11-11');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,128.23,'nice','2018-10-11');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice','2018-12-14');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice',DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (DEFAULT,DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note","tb2_date") VALUES (DEFAULT,DEFAULT,DEFAULT,DEFAULT);
          
-
        5. IGNORE
          When the IGNORE modifier is used, errors that occur during INSERT execution are ignored.
          
-
          Input
          
-
          # New data will be ignored if there is duplicate in the table.
-INSERT IGNORE INTO  exmp_tb2 VALUES(189, '189.23','nice','2017-11-12');
-INSERT IGNORE INTO  exmp_tb2 VALUES(130,'189.23','nice','2017-11-12');
-INSERT IGNORE INTO  exmp_tb2 VALUES(120,15.68,'good','2018-11-12');
-INSERT IGNORE INTO  exmp_tb2 VALUES(DEFAULT,128.23,'nice','2018-10-11');
-INSERT IGNORE INTO  exmp_tb2 VALUES(DEFAULT,DEFAULT,'nice','2018-12-14');
-INSERT IGNORE INTO  exmp_tb2 VALUES(DEFAULT,DEFAULT,'nice',DEFAULT);test
-INSERT IGNORE INTO  exmp_tb2 (tb2_id,tb2_price) VALUES(DEFAULT,DEFAULT);
-INSERT IGNORE INTO  exmp_tb2 (tb2_id,tb2_price,tb2_note) VALUES(DEFAULT,DEFAULT,DEFAULT);
-INSERT IGNORE INTO  exmp_tb2 (tb2_id,tb2_price,tb2_note,tb2_date) VALUES(DEFAULT,DEFAULT,DEFAULT,DEFAULT);
          
-
          Output
          
-
          -- New data will be ignored if there is duplicate in the table.
-INSERT INTO "public"."exmp_tb2"  VALUES (101,'189.23','nice','2017-11-12');
-INSERT INTO "public"."exmp_tb2"  VALUES (130,'189.23','nice','2017-11-12');
-INSERT INTO "public"."exmp_tb2"  VALUES (120,15.68,'good','2018-11-12');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,128.23,'nice','2018-10-11');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice','2018-12-14');
-INSERT INTO "public"."exmp_tb2"  VALUES (DEFAULT,DEFAULT,'nice',DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (DEFAULT,DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note","tb2_date") VALUES (DEFAULT,DEFAULT,DEFAULT,DEFAULT);
          
-
        6. VALUES
          INSERT statements use the VALUES syntax can insert multiple lines, separated by commas.
          
-
          Input
          
-
          INSERT INTO  exmp_tb1 (tb1_name,tb1_sex,tb1_address,tb1_number) VALUES('David','male','NewYork','01015827875'),('Rachel','female','NewYork','01015827749'),('Monica','female','NewYork','010158996743');
          
-
          Output
          
-
          INSERT INTO "public"."exmp_tb1" ("tb1_name","tb1_sex","tb1_address","tb1_number") VALUES ('David','male','NewYork','01015827875');
-INSERT INTO "public"."exmp_tb1" ("tb1_name","tb1_sex","tb1_address","tb1_number") VALUES ('Rachel','female','NewYork','01015827749');
-INSERT INTO "public"."exmp_tb1" ("tb1_name","tb1_sex","tb1_address","tb1_number") VALUES ('Monica','female','NewYork','010158996743');
          
-
        7. ON DUPLICATE KEY UPDATE
          INSERT uses the ON DUPLICATE KEY UPDATE clause to update existing rows.
          
-
          Input
          
-
          # ON DUPLICATE KEY UPDATE (If new data will cause a duplicate value in the primary/unique key, UPDATE will work. Otherwise, INSERT will work.) 
-INSERT INTO  exmp_tb2(tb2_id,tb2_price) VALUES(3,12.3) ON DUPLICATE KEY UPDATE tb2_price=12.3;
-INSERT INTO  exmp_tb2(tb2_id,tb2_price) VALUES(4,12.3) ON DUPLICATE KEY UPDATE tb2_price=12.3;
-INSERT INTO  exmp_tb2(tb2_id,tb2_price,tb2_note) VALUES(10,DEFAULT,DEFAULT) ON DUPLICATE KEY UPDATE tb2_price=66.6;
-INSERT INTO  exmp_tb2(tb2_id,tb2_price,tb2_note,tb2_date) VALUES(11,DEFAULT,DEFAULT,DEFAULT) ON DUPLICATE KEY UPDATE tb2_price=66.6;
          
-
          Output
          
-
          -- ON DUPLICATE KEY UPDATE (If new data will cause a duplicate value in the primary/unique key, UPDATE will work. Otherwise, INSERT will work.) 
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (3,12.3);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (4,12.3);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (10,DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note","tb2_date") VALUES (11,DEFAULT,DEFAULT,DEFAULT);
          
-
        8. SET
          MySQL INSERT...SET statement inserts rows based on explicitly specified values.
          
-
          Input
          
-
          # INSERT INTO  SET (Data records can be inserted specially. One record can be inserted at a time, and batch insertion is not supported.) 
-INSERT INTO  exmp_tb2 SET tb2_price=56.1,tb2_note='unbelievable',tb2_date='2018-11-13';
-INSERT INTO  exmp_tb2 SET tb2_price=99.9,tb2_note='perfect',tb2_date='2018-10-13';
-INSERT INTO  exmp_tb2 SET tb2_id=9,tb2_price=99.9,tb2_note='perfect',tb2_date='2018-10-13';
          
-
          Output
          
-
          -- INSERT INTO  SET (Data records can be inserted specially. One record can be inserted at a time, and batch insertion is not supported.) 
-INSERT INTO "public"."exmp_tb2" ("tb2_price","tb2_note","tb2_date") VALUES (56.1,'unbelievable','2018-11-13');
-INSERT INTO "public"."exmp_tb2" ("tb2_price","tb2_note","tb2_date") VALUES (99.9,'perfect','2018-10-13');
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note","tb2_date") VALUES (9,99.9,'perfect','2018-10-13');
          
-
        
-
        
-
        UPDATE
        In MySQL, UPDATE allows the following keywords: LOW_PRIORITY, ORDER BY, LIMIT, and IGNORE. GaussDB(DWS) does not support these keywords, and DSC will convert them.
        
-
        1. LOW_PRIORITY
          With the LOW_PRIORITY modifier, execution of UPDATE is delayed.
          
-
          Input
          
-
          # LOW_PRIORITY 
-UPDATE LOW_PRIORITY employees SET department_id=2;
          
-
          Output
          
-
          -- LOW_PRIORITY     
-UPDATE "public"."employees" SET "department_id" = 2;
          
-
        2. ORDER_BY
          In MySQL, if an UPDATE statement includes an ORDER BY clause, the rows will be updated in the order specified by the clause.
          
-
          Input
          
-
          # ORDER BY 
-UPDATE  employees SET department_id=department_id+1  ORDER BY id;
          
-
          Output
          
-
          -- ORDER BY 
-UPDATE "public"."employees" SET "department_id" = department_id+1;
          
-
        3. LIMIT
          UPDATE LIMIT syntax can be used to limit the scope. A clause is a limit on row matching. As long as the rows that satisfy the clause are found, the statements will stop, regardless of whether they have actually changed.
          
-
          Input
          
-
          # LIMIT 
-UPDATE  employees SET department_id=department_id+1   LIMIT 3 ;
-UPDATE  employees SET department_id=department_id+1   LIMIT 3 , 10 ;
-
-# LIMIT + OFFSET 
-UPDATE  employees SET department_id=department_id+1   LIMIT 3   OFFSET 2;
-
-# LIMIT + ORDER BY 
-UPDATE  employees SET department_id=department_id+1 ORDER BY fname  LIMIT 3 ;
-
-# LIMIT + WHERE + ORDER BY 
-UPDATE  employees SET department_id=department_id+1 WHERE id<5 ORDER BY  fname  LIMIT 3 ;
-
-# LIMIT + WHERE + ORDER BY + OFFSET 
-UPDATE  employees SET department_id=department_id+1 WHERE id<5 ORDER BY  fname  LIMIT 3 OFFSET 2 ;
          
-
          Output
          
-
          -- LIMIT 
-UPDATE "public"."employees" SET "department_id" = department_id+1;
-UPDATE "public"."employees" SET "department_id" = department_id+1;
-
--- LIMIT + OFFSET 
-UPDATE "public"."employees" SET "department_id" = department_id+1;
-
--- LIMIT + ORDER BY 
-UPDATE "public"."employees" SET "department_id" = department_id+1;
-
--- LIMIT + WHERE + ORDER BY 
-UPDATE "public"."employees" SET "department_id" = department_id+1 WHERE id<5;
-
--- LIMIT + WHERE + ORDER BY + OFFSET 
-UPDATE "public"."employees" SET "department_id" = department_id+1 WHERE id<5;
          
-
        4. IGNORE
          With the IGNORE modifier, the UPDATE statement does not abort even if errors occur during execution.
          
-
          Input
          
-
          # IGNORE 
-UPDATE IGNORE employees SET department_id=3;
          
-
          Output
          
-
          -- IGNORE 
-UPDATE "public"."employees" SET "department_id" = 3;
          
-
        
-
        
-
        REPLACE
        In MySQL, REPLACE allows the following keywords: LOW_PRIORITY, PARTITION, DELAYED, VALUES, and SET. The following examples are temporary migration solutions only.
        
-
         
        REPLACE works exactly like INSERT, except that if an old row in the table has the same value as a new row for a primary key or unique index, the old row is deleted before the new row is inserted.
        
-
        
-
        1. LOW_PRIORITY
          MySQL REPLACE supports the use of LOW_PRIORITY, which is converted by the Migration tool.
          
-
          Input
          
-
          # LOW_PRIORITY 
-Replace LOW_PRIORITY INTO  exmp_tb2 VALUES(1, '128.23', 'nice', '2018-10-11 19:00:00');
-Replace LOW_PRIORITY INTO  exmp_tb2 VALUES(2, DEFAULT, 'nice', '2018-12-14 19:00:00' );
-Replace LOW_PRIORITY INTO  exmp_tb2 VALUES(3, DEFAULT, 'nice', DEFAULT);
-Replace LOW_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price) VALUES(5, DEFAULT);
-Replace LOW_PRIORITY INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note) VALUES(4, DEFAULT, DEFAULT);
          
-
          Output
          
-
          -- LOW_PRIORITY 
-INSERT INTO "public"."exmp_tb2"  VALUES (1,'128.23','nice','2018-10-11 19:00:00');
-INSERT INTO "public"."exmp_tb2"  VALUES (2,DEFAULT,'nice','2018-12-14 19:00:00');
-INSERT INTO "public"."exmp_tb2"  VALUES (3,DEFAULT,'nice',DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (5,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (4,DEFAULT,DEFAULT);
          
-
        2. PARTITION
          MySQL REPLACE supports explicit partitioning selection using the PARTITION keyword and a comma-separated name list for partitions, subpartitions, or both.
          
-
          Input
          
-
          replace INTO employees PARTITION(p3) VALUES (19, 'Frank1', 'Williams', 1, 2);
-replace INTO employees PARTITION(p0) VALUES (4, 'Frank1', 'Williams', 1, 2);
-replace INTO employees PARTITION(p1) VALUES (9, 'Frank1', 'Williams', 1, 2);
-replace INTO employees PARTITION(p2) VALUES (10, 'Frank1', 'Williams', 1, 2);
-replace INTO employees PARTITION(p2) VALUES (11, 'Frank1', 'Williams', 1, 2);
          
-
          Output
          
-
          INSERT INTO "public"."employees"  VALUES (19,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (4,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (9,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (10,'Frank1','Williams',1,2);
-INSERT INTO "public"."employees"  VALUES (11,'Frank1','Williams',1,2);
          
-
        3. DELAYED
           
          DELAYED INSERT and REPLACE operations were deprecated in MySQL 5.6. In MySQL 5.7, DELAYED was not supported. The server recognizes but ignores the DELAYED keyword, handles REPLACE as a non-delayed one, and generates an ER_WARN_LEGACY_SYNTAX_CONVERTED warning. (REPLACE DELAYED is no longer supported, and the statement is converted to REPLACE.) The keyword DELAYED will be deleted in later versions.
          
-
          
-
          Input
          
-
          #DELAYED INSERT DELAYED works only with MyISAM, MEMORY, ARCHIVE, and BLACKHOLE tables. 
-#If you execute INSERT DELAYED with another storage engine, 
-#you will get an error like this: ERROR 1616 (HY000): DELAYED option not supported 
-Replace DELAYED INTO  exmp_tb2 VALUES(10, 128.23, 'nice', '2018-10-11 19:00:00');
-Replace DELAYED INTO  exmp_tb2 VALUES(6, DEFAULT, 'nice', '2018-12-14 19:00:00');
-Replace DELAYED INTO  exmp_tb2 VALUES(7, 20, 'nice', DEFAULT);
-Replace DELAYED INTO  exmp_tb2 (tb2_id, tb2_price) VALUES(11, DEFAULT);
-Replace DELAYED INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note) VALUES(12, DEFAULT, DEFAULT);
-Replace DELAYED INTO  exmp_tb2 (tb2_id, tb2_price, tb2_note, tb2_date) VALUES(13, DEFAULT, DEFAULT, DEFAULT);
          
-
          Output
          
-
          --DELAYED INSERT DELAYED works only with MyISAM, MEMORY, ARCHIVE, and BLACKHOLE tables. 
---If you execute INSERT DELAYED with another storage engine, 
---you will get an error like this: ERROR 1616 (HY000): DELAYED option not supported. 
-INSERT INTO "public"."exmp_tb2"  VALUES (10,128.23,'nice','2018-10-11 19:00:00');
-INSERT INTO "public"."exmp_tb2"  VALUES (6,DEFAULT,'nice','2018-12-14 19:00:00');
-INSERT INTO "public"."exmp_tb2"  VALUES (7,20,'nice',DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price") VALUES (11,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note") VALUES (12,DEFAULT,DEFAULT);
-INSERT INTO "public"."exmp_tb2" ("tb2_id","tb2_price","tb2_note","tb2_date") VALUES (13,DEFAULT,DEFAULT,DEFAULT);
          
-
        4. VALUES
          MySQL REPLACE supports a statement to insert or delete multiple values, separated by commas.
          
-
          Input
          
-
          # If data is available, replacement will be performed. Otherwise, insertion will be performed. 
-Replace INTO  exmp_tb1 (tb1_id,tb1_name,tb1_sex,tb1_address,tb1_number) VALUES(17,'David','male','NewYork11','01015827875'),(18,'Rachel','female','NewYork22','01015827749'),(20,'Monica','female','NewYork','010158996743');
-Replace INTO  exmp_tb1 (tb1_id,tb1_name,tb1_sex,tb1_address,tb1_number) VALUES(17,'David1','male','NewYork11','01015827875'),(21,'Rachel','female','NewYork22','01015827749'),(22,'Monica','female','NewYork','010158996743');
-Replace INTO  exmp_tb1 (tb1_id,tb1_name,tb1_sex,tb1_address,tb1_number,tb1_date) VALUES(17,'David2',DEFAULT,'NewYork11','01015827875',DEFAULT),(18,'Rachel','female',DEFAULT,'01015827749','2018-12-14 10:44:20'),(DEFAULT,'Monica','female',DEFAULT,DEFAULT,'2018-12-14 10:44:20');
-Replace INTO  exmp_tb1 VALUES(DEFAULT,'David',DEFAULT,'NewYork11','01015827875',DEFAULT),(18,'Rachel','female',DEFAULT,'01015827749','2018-12-14 10:44:20'),(DEFAULT,'Monica','female',DEFAULT,DEFAULT,'2018-12-14 10:44:20');
          
-
          Output
          
-
          -- If data is available, replacement will be performed. Otherwise, insertion will be performed. 
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number") VALUES (17,'David','male','NewYork11','01015827875');
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number") VALUES (18,'Rachel','female','NewYork22','01015827749');
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number") VALUES (20,'Monica','female','NewYork','010158996743');
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number") VALUES (17,'David1','male','NewYork11','01015827875');
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number") VALUES (21,'Rachel','female','NewYork22','01015827749');
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number") VALUES (22,'Monica','female','NewYork','010158996743');
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number","tb1_date") VALUES (17,'David2',DEFAULT,'NewYork11','01015827875',DEFAULT);
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number","tb1_date") VALUES (18,'Rachel','female',DEFAULT,'01015827749','2018-12-14 10:44:20');
-INSERT INTO "public"."exmp_tb1" ("tb1_id","tb1_name","tb1_sex","tb1_address","tb1_number","tb1_date") VALUES (DEFAULT,'Monica','female',DEFAULT,DEFAULT,'2018-12-14 10:44:20');
-INSERT INTO "public"."exmp_tb1"  VALUES (DEFAULT,'David',DEFAULT,'NewYork11','01015827875',DEFAULT);
-INSERT INTO "public"."exmp_tb1"  VALUES (18,'Rachel','female',DEFAULT,'01015827749','2018-12-14 10:44:20');
-INSERT INTO "public"."exmp_tb1"  VALUES (DEFAULT,'Monica','female',DEFAULT,DEFAULT,'2018-12-14 10:44:20');
          
-
        5. SET
          MySQL REPLACE supports the use of SET settings, which the Migration tool will convert.
          
-
          Input
          
-
          replace INTO `runoob_datatype_test` VALUES (100, 100, 100, 0, 1);
-replace INTO `runoob_datatype_test` VALUES (100.23, 100.25, 100.26, 0.12,1.5);
-replace INTO `runoob_datatype_test` (dataType_numeric,dataType_numeric1) VALUES (100.23, 100.25);
-replace INTO `runoob_datatype_test` (dataType_numeric,dataType_numeric1,dataType_numeric2) VALUES (100.23, 100.25, 2.34);
-replace into runoob_datatype_test set dataType_numeric=23.1, dataType_numeric4 = 25.12 ;
          
-
          Output
          
-
          INSERT INTO "public"."runoob_datatype_test"  VALUES (100,100,100,0,1);
-INSERT INTO "public"."runoob_datatype_test"  VALUES (100.23,100.25,100.26,0.12,1.5);
-INSERT INTO "public"."runoob_datatype_test" ("datatype_numeric","datatype_numeric1") VALUES (100.23,100.25);
-INSERT INTO "public"."runoob_datatype_test" ("datatype_numeric","datatype_numeric1","datatype_numeric2") VALUES (100.23,100.25,2.34);
-INSERT INTO "public"."runoob_datatype_test" ("datatype_numeric","datatype_numeric4") VALUES (23.1,25.12);
          
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_07_8314.html b/docs/dws/tool/dws_07_8314.html
deleted file mode 100644
index c6a2c927..00000000
--- a/docs/dws/tool/dws_07_8314.html
+++ /dev/null
@@ -1,276 +0,0 @@
-
-
-
        Transaction Management and Database Management
        
-
        This section describes how to migrate keywords and features related to MySQL transaction and database management.
        
-
        Transaction Management
        1. TRANSACTION
          DSC will perform adaptation based on GaussDB features during MySQL transaction statement migration.
          
-
          Input
          
-
          ## Each statement applies only to the next single transaction performed within the session. 
-SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
-SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
-SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
-SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
-SET TRANSACTION READ ONLY;
-SET TRANSACTION READ WRITE;
-SET TRANSACTION ISOLATION LEVEL READ COMMITTED,READ ONLY;
-SET TRANSACTION ISOLATION LEVEL SERIALIZABLE,READ WRITE;
-## Each statement (with the SESSION keyword) applies to all subsequent transactions performed within the current session. 
-START TRANSACTION;
-SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;
-SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;
-SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE;
-SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE;
-commit ;
          
-
          
-
          Output
          
-
          -- Each statement applies only to the next single transaction performed within the session. 
-SET LOCAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
-SET LOCAL TRANSACTION ISOLATION LEVEL REPEATABLE READ;
-SET LOCAL TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
-SET LOCAL TRANSACTION ISOLATION LEVEL SERIALIZABLE;
-SET LOCAL TRANSACTION READ ONLY;
-SET LOCAL TRANSACTION READ WRITE;
-SET LOCAL TRANSACTION ISOLATION LEVEL READ COMMITTED READ ONLY;
-SET LOCAL TRANSACTION ISOLATION LEVEL SERIALIZABLE READ WRITE;
--- Each statement (with the SESSIONkeyword) applies to all subsequent transactions performed within the current session. 
-START TRANSACTION;
-SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ COMMITTED;
-SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ COMMITTED;
-SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL SERIALIZABLE;
-SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL SERIALIZABLE;
-COMMIT WORK;
          
-
          
-
        2. LOCK
          DSC will perform adaptation based on GaussDB features during the migration of MySQL table locking statements which are used in transaction processing.
          
-
          Input
          
-
          ## A.
-START TRANSACTION;
-LOCK TABLES `mt`.`runoob_tbl` WRITE,`mt`.`runoob_tb2` READ;
-commit;
-
-## B.
-START TRANSACTION;
-LOCK TABLES `mt`.`runoob_tbl` WRITE;
-commit;
-
-## C.
-START TRANSACTION;
-LOCK TABLES `mt`.`runoob_tbl` READ,`mt`.`runoob_tbl` AS t1 READ;
-commit;
          
-
          
-
          Output
          
-
          -- A.
-START TRANSACTION;
-LOCK TABLE "mt"."runoob_tbl" IN ACCESS EXCLUSIVE MODE;
-LOCK TABLE "mt"."runoob_tb2" IN ACCESS SHARE MODE;
-COMMIT WORK;
-
--- B.
-START TRANSACTION;
-LOCK TABLE "mt"."runoob_tbl" IN ACCESS EXCLUSIVE MODE;
-COMMIT WORK;
-
--- C.
-START TRANSACTION;
-LOCK TABLE "mt"."runoob_tbl" IN ACCESS SHARE MODE;
-COMMIT WORK;
          
-
          
-
        
-
        
-
        Database Management
        1. SET CHARACTER
          DSC will replace MySQL SET CHARACTER SET with SET SESSION NAMES during migration. The following table lists character set mapping.
          
-
-
          
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
          Table 1 
          MySQL CHARACTER SET
          
-
          GaussDB SESSION NAMES
          
-
          ASCII
          
-
          SQL_ASCII
          
-
          BIG5
          
-
          BIG5
          
-
          CP1250
          
-
          WIN1250
          
-
          CP1251
          
-
          WIN1251
          
-
          CP1256
          
-
          WIN1256
          
-
          CP1257
          
-
          WIN1257
          
-
          CP932
          
-
          SJIS
          
-
          EUCJPMS
          
-
          EUC_JP
          
-
          EUCKR
          
-
          EUC_KR
          
-
          GB2312
          
-
          GB18030
          
-
          GBK
          
-
          GBK
          
-
          GREEK
          
-
          ISO_8859_7
          
-
          HEBREW
          
-
          ISO_8859_8
          
-
          KOI8R
          
-
          KOI8R
          
-
          KOI8U
          
-
          KOI8U
          
-
          LATIN1
          
-
          LATIN1
          
-
          LATIN2
          
-
          LATIN2
          
-
          LATIN5
          
-
          LATIN5
          
-
          LATIN7
          
-
          LATIN7
          
-
          SJIS
          
-
          SJIS
          
-
          SWE7
          
-
          UTF8
          
-
          TIS620
          
-
          WIN874
          
-
          UTF8
          
-
          UTF8
          
-
          UTF8MB4
          
-
          UTF8
          
-
          
-
          
-
          Input
          
-
          SET CHARACTER SET 'ASCII';
-SET CHARACTER SET 'BIG5';
-SET CHARACTER SET 'CP1250';
-SET CHARACTER SET 'CP1251';
-SET CHARACTER SET 'CP1256';
-SET CHARACTER SET 'CP1257';
-SET CHARACTER SET 'CP932';
-SET CHARACTER SET 'EUCJPMS';
-SET CHARACTER SET 'EUCKR';
-SET CHARACTER SET 'GB2312';
-SET CHARACTER SET 'GBK';
-SET CHARACTER SET 'GREEK';
-SET CHARACTER SET 'HEBREW';
-SET CHARACTER SET 'KOI8R';
-SET CHARACTER SET 'KOI8U';
-SET CHARACTER SET 'LATIN1';
-SET CHARACTER SET 'LATIN2';
-SET CHARACTER SET 'LATIN5';
-SET CHARACTER SET 'LATIN7';
-SET CHARACTER SET 'SJIS';
-SET CHARACTER SET 'SWE7';
-SET CHARACTER SET 'TIS620';
-SET CHARACTER SET 'UTF8';
-SET CHARACTER SET 'UTF8MB4';
-## MySQL does not support SET CHARACTER SET 'UCS2';. 
-## MySQL does not support SET CHARACTER SET 'UTF16';. 
-## MySQL does not support SET CHARACTER SET 'UTF16LE';. 
-## MySQL does not support SET CHARACTER SET 'UTF32';.
          
-
          
-
          Output
          
-
          SET SESSION NAMES 'SQL_ASCII';
-SET SESSION NAMES 'BIG5';
-SET SESSION NAMES 'WIN1250';
-SET SESSION NAMES 'WIN1251';
-SET SESSION NAMES 'WIN1256';
-SET SESSION NAMES 'WIN1257';
-SET SESSION NAMES 'SJIS';
-SET SESSION NAMES 'EUC_JP';
-SET SESSION NAMES 'EUC_KR';
-SET SESSION NAMES 'GB18030';
-SET SESSION NAMES 'GBK';
-SET SESSION NAMES 'ISO_8859_7';
-SET SESSION NAMES 'ISO_8859_8';
-SET SESSION NAMES 'KOI8R';
-SET SESSION NAMES 'KOI8U';
-SET SESSION NAMES 'LATIN1';
-SET SESSION NAMES 'LATIN2';
-SET SESSION NAMES 'LATIN5';
-SET SESSION NAMES 'LATIN7';
-SET SESSION NAMES 'SJIS';
-SET SESSION NAMES 'UTF8';
-SET SESSION NAMES 'WIN874';
-SET SESSION NAMES 'UTF8';
-SET SESSION NAMES 'UTF8';
--- MySQL does not support SET CHARACTER SET 'UCS2';. 
--- MySQL does not support SET CHARACTER SET 'UTF16';. 
--- MySQL does not support SET CHARACTER SET 'UTF16LE';. 
--- MySQL does not support SET CHARACTER SET 'UTF32';.
          
-
        
-
        
-
        
-
        
-
        
-
        Parent topic: MySQL Syntax Migration
        
-
        
-
        
-
diff --git a/docs/dws/tool/dws_16_0001.html b/docs/dws/tool/dws_16_0001.html
new file mode 100644
index 00000000..94c851f0
--- /dev/null
+++ b/docs/dws/tool/dws_16_0001.html
@@ -0,0 +1,22 @@
+
+
+
        About This Document
        
+
        
+    
        
+
+  
        
+
        
+
+
+
        
+
        Parent topic: DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0002.html b/docs/dws/tool/dws_16_0002.html
new file mode 100644
index 00000000..6ecc8f07
--- /dev/null
+++ b/docs/dws/tool/dws_16_0002.html
@@ -0,0 +1,14 @@
+
+
+
        Intended Audience
        
+
        This document is intended for the following DSC users:
        
+
        • Database migration engineers
        • Database administrators
        • Technical support engineers
        
+
        DSC users need to have a basic knowledge of:
        
+
        • Basic concepts and policies of database migration
        • Teradata/MySQL(ADB For MySQL)
        • GaussDB(DWS)
        
+
        
+
        
+
        
+
        Parent topic: About This Document
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0003.html b/docs/dws/tool/dws_16_0003.html
new file mode 100644
index 00000000..b829f5ab
--- /dev/null
+++ b/docs/dws/tool/dws_16_0003.html
@@ -0,0 +1,109 @@
+
+
+
        Document Conventions
        
+
        This section describes the content, symbol, and command conventions of this document.
        
+
        Disclaimer
        The purchased products, services, and features are subject to the signed contract. All or part of the products, services, and features described in this document may not be available for purchasing or using. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided in the form of "as-is" and do not constitute a warranty, guarantee, or representation of any kind, express or implied.
        
+
        
+
        Symbol Convention
        Symbols that may be found in this document are defined as follows:
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Symbol
        
+
        Description
        
+
        
+
        Indicates an imminently hazardous situation which, if not avoided, will result in serious injury or death.
        
+
        
+
        Indicates a potentially hazardous situation which, if not avoided, will result in death or serious injury.
        
+
        
+
        Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury.
        
+
        
+
        Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results. 
        
+
        NOTICE is used to address practices not related to personal injury.
        
+
        
+
        Provides additional information to emphasize or supplement important points of the main text.
        
+
        NOTE is used to address information not related to personal injury, equipment damage, or environment damage.
        
+
        
+
        
+
        
+
        Command Conventions
        Commands in this document comply with the following conventions:
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Command conventions
        Format
        
+
        Description
        
+
        Boldface
        
+
        The keywords of a command are in Boldface.
        
+
        Italic
        
+
        Command arguments, paths, files, or folders are in italics.
        
+
        [ ]
        
+
        Square brackets enclose syntax choices (keywords or arguments) that are optional.
        
+
        { x | y | ... }
        
+
        Braces enclose a set of required syntax choices separated by vertical bars (|), from which you select one.
        
+
        [ x | y | ... ]
        
+
        Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none.
        
+
        { x | y | ... }*
        
+
        Asterisk marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one.
        
+
        [ x | y | ... ]*
        
+
        Asterisk marked square brackets enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none.
        
+
        &<1-n>
        
+
        The argument or keyword and argument combination before the ampersand (&) sign can be entered 1 to n times.
        
+
        #
        
+
        A line that starts with a pound (#) sign is comments.
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: About This Document
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0005.html b/docs/dws/tool/dws_16_0005.html
new file mode 100644
index 00000000..67204027
--- /dev/null
+++ b/docs/dws/tool/dws_16_0005.html
@@ -0,0 +1,12 @@
+
+
+
        Third-party Licenses
        
+
        This section lists the applicable third-party licenses.
        
+
        • ANTLR v4.9.3
        • Apache Commons IO 2.11
        • Apache Commons CLI 1.5
        • Apache Log4j 2.17.2
        • JSON.org json 20220320
        • postgresql 42.4.1
        • sql-formatter 2.0.3
        
+
        
+
        
+
        
+
        Parent topic: About This Document
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0006.html b/docs/dws/tool/dws_16_0006.html
new file mode 100644
index 00000000..9cfe63b3
--- /dev/null
+++ b/docs/dws/tool/dws_16_0006.html
@@ -0,0 +1,18 @@
+
+
+
        Introduction to DSC
        
+
        
+
        
+
        
+
+
+
        
+
        Parent topic: DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0008.html b/docs/dws/tool/dws_16_0008.html
new file mode 100644
index 00000000..d3d443fe
--- /dev/null
+++ b/docs/dws/tool/dws_16_0008.html
@@ -0,0 +1,260 @@
+
+
+
        Operating Environment
        
+
        Supported Databases
        The following table lists the source databases supported by DSC.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Source databases supported by DSC
        Database
        
+
        Version
        
+
        Teradata
        
+
        13.1
        
+
        MySQL
        
+
        8.0
        
+
        
+
        
+
        The following table lists the destination databases supported by DSC.
        
+
+
        
+
+
+
+
+
+
+
+
        Table 2 Destination databases supported by DSC
        Database
        
+
        Version
        
+
        GaussDB(DWS)
        
+
        GaussDB(DWS) 8.1.0 or later
        
+
        
+
        
+
        
+
        Hardware Requirements
        Table 3 lists the hardware requirements of DSC.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 3 Hardware requirements of DSC
        Hardware
        
+
        Configuration
        
+
        CPU
        
+
        AMD or Intel Pentium (minimum frequency: 500 MHz)
        
+
        Min memory
        
+
        1 GB
        
+
        Disk space
        
+
        1 GB
        
+
        
+
        
+
        
+
        Software Requirements
        OS
        
+
        Table 4 lists the operating systems compatible with DSC.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 4 OSs compatible with DSC
        Server
        
+
        OS
        
+
        Version
        
+
        x86 servers
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        SUSE Linux Enterprise Server 11
        
+
        SP1 (SUSE 11.1)
        
+
        SP2 (SUSE 11.2)
        
+
        SP3 (SUSE 11.3)
        
+
        SP4 (SUSE 11.4)
        
+
        SUSE Linux Enterprise Server 12
        
+
        
+
        SP0 (SUSE 12.0)
        
+
        SP1 (SUSE 12.1)
        
+
        SP2 (SUSE 12.2)
        
+
        SP3 (SUSE 12.3)
        
+
        RHEL
        
+
        
+
        6.4-x86_64 (RHEL 6.4)
        
+
        6.5-x86_64 (RHEL 6.5)
        
+
        6.6-x86_64 (RHEL 6.6)
        
+
        6.7-x86_64 (RHEL 6.7)
        
+
        6.8-x86_64 (RHEL 6.8)
        
+
        6.9-x86_64 (RHEL 6.9)
        
+
        7.0-x86_64 (RHEL 7.0)
        
+
        7.1-x86_64 (RHEL 7.1)
        
+
        7.2-x86_64 (RHEL 7.2)
        
+
        7.3-x86_64 (RHEL 7.3)
        
+
        7.4-x86_64 (RHEL 7.4)
        
+
        CentOS
        
+
        
+
        6.4 (CentOS 6.4)
        
+
        6.5 (CentOS 6.5)
        
+
        6.6 (CentOS 6.6)
        
+
        6.7 (CentOS 6.7)
        
+
        6.8 (CentOS 6.8)
        
+
        6.9 (CentOS 6.9)
        
+
        7.0 (CentOS 7.0)
        
+
        7.1 (CentOS 7.1)
        
+
        7.2 (CentOS 7.2)
        
+
        7.3 (CentOS 7.3)
        
+
        7.4 (CentOS 7.4)
        
+
        Windows
        
+
        7.0, 10, 11
        
+
        
+
        
+
        Other software requirements
        
+
        Table 5 lists the requirements of DSC on other software versions.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 5 Requirements of DSC on other software versions
        Software
        
+
        Description
        
+
        JDK 1.8.0_141 or later
        
+
        Used to run DSC.
        
+
        Perl 5.8.8
        
+
        Used to migrate Perl  files.
        
+
        Perl 5.28.2 and later
        
+
        Used to migrate Perl files in  Windows.
        
+
        Python 3.8.2
        
+
        Used to verify post migration  script.
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Introduction to DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0009.html b/docs/dws/tool/dws_16_0009.html
new file mode 100644
index 00000000..a366a527
--- /dev/null
+++ b/docs/dws/tool/dws_16_0009.html
@@ -0,0 +1,26 @@
+
+
+
        Using DSC
        
+
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0010.html b/docs/dws/tool/dws_16_0010.html
new file mode 100644
index 00000000..507ce640
--- /dev/null
+++ b/docs/dws/tool/dws_16_0010.html
@@ -0,0 +1,19 @@
+
+
+
        Overview
        
+
        This chapter describes how to use DSC, including how to install and configure DSC and how to use DSC to migrate data.
        
+
         
        Use the latest patches to update the operating system and related software to prevent vulnerabilities and other security issues.
        
+
        
+
        Security in DSC is managed by access control to the files and folders that are created by the tool. To access these files and folders, you must have the required permissions. For example, you need the permission 600/400 to access target files and log files, and the permission 700 to access target folders and log folders. The tool also ensures data security by not saving sensitive data in the log files.
        
+
        The file or folder specified in --input-folder must not have write privileges to GROUP and/or OTHERS. For security reasons, the tool will not execute if the input files/folders have write privileges.
        
+
        It is required that the root privileged user must not be used for installation and execution of the DSC for Linux.
        
+
        The umask value provided in the DSC file is a set value that is related to file permissions. It is recommended that users do not modify this value. Modifying this value will affect file permissions.
        
+
         
        DSC is a standalone application that can run without any network or database connection. It can run on any machine that is isolated from any network.
        
+
        
+
        
+
        
+
        
+
        Parent topic: Using DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0012.html b/docs/dws/tool/dws_16_0012.html
new file mode 100644
index 00000000..d9face08
--- /dev/null
+++ b/docs/dws/tool/dws_16_0012.html
@@ -0,0 +1,26 @@
+
+
+
        Configuring DSC
        
+
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0013.html b/docs/dws/tool/dws_16_0013.html
new file mode 100644
index 00000000..68fcfae5
--- /dev/null
+++ b/docs/dws/tool/dws_16_0013.html
@@ -0,0 +1,347 @@
+
+
+
        DSC Configuration
        
+
        Configure the following items:
        
+
        • Setting application.properties: Configure the migration behavior of DSC, for example, whether to overwrite the files in the target folder and whether to format the SQL files.
        • Setting Java Memory Allocation: Configure the memory that can be used by DSC. If the memory usage exceeds the threshold, DSC displays an error and exits.
        
+
        Setting application.properties
        The application.properties file contains DSC behavior parameters, which are applicable to Teradata, Oracle.
        
+
        Perform the following steps to configure the parameters:
        
+
        1. Open the application.properties file in the config folder.
        2. Set parameters in the application.properties file as needed.
          Table 1 describes the parameters in the application.properties file.
           
          • Parameter values are case-insensitive.
          • Do not modify any other parameter except the listed ones.
          
+
          
+
          
+
        3. Save the configuration and exit.
        
+
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Parameters in the application.properties file
        Parameter
        
+
        Description
        
+
        Value Range
        
+
        Default Value
        
+
        Example
        
+
        • formatterrequired
        
+
        If there are any changes in this configuration item, then the tool will not function as expected.
        
+
        • true
        • false
        
+
        true
        
+
        formatterrequired=true
        
+
        • prevalidationFlag
        
+
        If there are any changes in this configuration item, then the tool will not function as expected.
        
+
        • true
        • false
        
+
        true
        
+
        prevalidationFlag=true
        
+
        • commentSeparatorFlag
        
+
        If there are any changes in this configuration item, then the tool will not function as expected.
        
+
        • true
        • false
        
+
        true
        
+
        commentSeparatorFlag=true
        
+
        • queryDelimiter
        
+
        If there are any changes in this configuration item, then the tool will not function as expected.
        
+
        N/A
        
+
        N/A
        
+
        queryDelimiter=;
        
+
        • blogicDelimiter
        
+
        If there are any changes in this configuration item, then the tool will not function as expected.
        
+
        N/A
        
+
        N/A
        
+
        blogicDelimiter=/
        
+
        • Timeout
        
+
        Tool migration timeout duration.
        
+
        If there are any changes in this configuration item, then the tool will not function as expected.
        
+
        -
        
+
        4 hours
        
+
        Timeout=4
        
+
        • fileExtension
        
+
        Valid file extension separated by comma.
        
+
        If there are any modifications in this configuration item, then the tool will not function as expected.
        
+
         NOTE: 
        The exported scripts must be with the following postfix such as:
        
+
        • .sql
        • .txt
        • .fnc
        • .proc
        • .tbl
        • .tbs
        • .pl
        • .dsql
        
+
        and so on.
        
+
        
+
        • csv
        • txt
        • SQL
        
+
        SQL
        
+
        fileExtension=SQL
        
+
        • formattedSourceRequired
        
+
        Whether to use SQL Formatter to format the source SQL files.
        
+
        If this parameter is set to true, the copies of the input files are formatted and saved to the Output path/formattedSource directory.
        
+
        • true
        • false
        
+
        true
        
+
        formattedSourceRequired=true
        
+
        • target_files
        
+
        Specifies the operations to be performed on the output folder.
        
+
        Overwrite:
        
+
        This option specifies whether the files in the output folder must be overwritten.
        
+
        Delete: deletes all files in the output folder.
        
+
        Cancel: cancels an operation on the output folder that contains files.
        
+
        • overwrite
        • delete
        • cancel
        
+
        overwrite
        
+
        target_files=overwrite
        
+
        • encodingFormat
        
+
        Encoding format of input files.
        
+
        If this parameter is not set (or is commented out), DSC uses the default encoding format based on locale settings.
        
+
         NOTE: 
        • The auto detection of file encoding is inaccurate. To ensure that the correct encoding format is used, specify the format using this parameter.
        
+
        
+
        • UTF8
        • UTF16
        • UTF32
        • GB2312
        • ASCII and others
        
+
        Default based on locale
        
+
        encodingFormat=UTF8
        
+
        • NoOfThreads
        
+
        Number of threads used for migration
        
+
        Depending on available system resources
        
+
        3
        
+
        NoOfThreads=3
        
+
        • MaxFileSizeWarning
        
+
        Warning threshold for the input file size (unit: KB, MB, or GB).
        
+
        If an invalid value is specified, the default value is used.
        
+
        The following warning will be displayed if the specified source file size exceeds the threshold:
        
+
        *****************
+[WARNING] : Migration of the following files(>100KB) will take more time:
+bigfile001.SQL
+bigfile008.SQL
+*****************
        
+
        10 KB 1 GB
        
+
        10MB
        
+
        MaxFileSizeWarning=10MB
        
+
        • MaxFileSize
        
+
        Maximum size of the input file allowed. If crossing this limit, the file migration will be skipped.
        
+
        -
        
+
        20MB
        
+
        MaxFileSize=20MB
        
+
        • MaxSqlLen
        
+
        Maximum size of a query to be migrated.
        
+
        If an invalid value is specified, DSC resets it to the default value and displays the following warning:
        
+
        The query length parameter (MaxSqlLen) value is out of range. Resetting to default value.
        
+
        If an input query exceeds the specified maximum length, the pre-validation of the query migration will fail. DSC skips this query and logs the following error:
        
+
        2018-07-06 12:05:57,598 ERROR TeradataBulkHandler:195 Error occurred during processing of input in Bulk Migration. PreQueryValidation failed due to: Invalid termination; OR exclude keyword found in query; OR query exceeds maximum length (MaxSqlLen config parameter). filename.SQL for Query in position : xx
        
+
        1 .. 52,428,800 bytes
        
+
        (1 byte to 50 MB)
        
+
        1048576
        
+
        (1 MB)
        
+
        MaxSqlLen=1048576
        
+
        • initialJVMMemory
        
+
        Initial memory
        
+
        N/A
        
+
        256 MB
        
+
        initialJVMMemory=256MB
        
+
        This indicates that the process will start up with 256 MB of memory
        
+
        • maxJVMMemory
        
+
        Maximum memory
        
+
        N/A
        
+
        1024 MB
        
+
        maxJVMMemory=2048m
        
+
        This indicates that the process will use up to 2048 MB of memory.
        
+
        • executesqlingauss
        
+
        Run the migrated script in GaussDB. The value can be true or false. The script can be executed only on the server running the Linux operating system.
        
+
        • true
        • false
        
+
        false
        
+
        executesqlingauss=false
        
+
        
+
        
+
         
        • If a parameter is set to an incorrect or invalid value, DSC uses the default value of the parameter.
        • If the extensions (for example, .doc) are not supported, then it is recommended you add extension in fileExtension configuration parameter in application.properties file.
        
+
        
+
        Setting Java Memory Allocation
        DSC has preset settings for the memory allocation of the Java Virtual Machine (JVM).
        
+
        If the memory usage exceeds the limit during migration, DSC displays the "java.lang.OutOfMemoryError: GC overhead limit exceeded" error and exit. In this case, you can increase the values of initialJVMMemory and maxJVMMemory in the application.properties file to allocate more memory.
        
+
         
        The available system resources also determine the memory allocation.
        
+
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 2 Parameters for JVM memory allocation
        Parameter
        
+
        Description
        
+
        Recommended Value
        
+
        Xms
        
+
        Initial memory allocation (unit: MB)
        
+
        The minimum value is 256 MB. The maximum value depends on the available system resources.
        
+
        Default value: 256
        
+
        Xmx
        
+
        Upper limit for memory allocation (unit: MB)
        
+
        The minimum value is 1024 MB. The maximum value depends on the available system resources.
        
+
        Default value: 1024
        
+
        
+
        
+
        Open the gaussdb.properties file in the config folder of the verification file and configure parameters by referring to Table 3 to connect to GaussDB(DWS).
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 3 Parameters in the gaussdb.properties file
        Parameter
        
+
        Description
        
+
        Value Range
        
+
        Default
        
+
        Example
        
+
        gaussdb-user
        
+
        GaussDB(DWS) database user who has all permissions.
        
+
        NA
        
+
        NA
        
+
        user1
        
+
        gaussdb-port
        
+
        Port of the GaussDB(DWS) database
        
+
        NA
        
+
        NA
        
+
        2002
        
+
        gaussdb-name
        
+
        Name of the GaussDB(DWS) database
        
+
        NA
        
+
        NA
        
+
        GaussDB A
        
+
        gaussdb-ip
        
+
        IP address of the GaussDB(DWS) database
        
+
        NA
        
+
        NA
        
+
        10.XX.XX.XX
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Configuring DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0014.html b/docs/dws/tool/dws_16_0014.html
new file mode 100644
index 00000000..54591ce4
--- /dev/null
+++ b/docs/dws/tool/dws_16_0014.html
@@ -0,0 +1,338 @@
+
+
+
        Teradata SQL Configuration
        
+
        Teradata parameters are used to customize rules for Teradata script migration.
        
+
        Open the features-teradata.properties file in the config folder and set the parameters in Table 1 as required.
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Parameters in the features-teradata.properties file
        Parameter
        
+
        Description
        
+
        Value Range
        
+
        Default Value
        
+
        Example
        
+
        • deleteToTruncate
        
+
        Rule for migrating DELETE statements without a WHERE clause.
        
+
        true: enables the migration of DELETE to TRUNCATE. false: disables the migration of DELETE to TRUNCATE.
        
+
        • true
        • false
        
+
        false
        
+
        deleteToTruncate=true
        
+
        • distributeByHash
        
+
        Which columns specified in the primary index will be used for data distribution across nodes in the cluster.
        
+
        one: Data is distributed based on the first column specified in the primary index.
        
+
        many: Data is distributed based on all the columns specified in the primary index.
        
+
        This function is addressed by using the DISTRIBUTE BY clause.
        
+
         NOTE: 
        This parameter is set to one in V100R002C60 because this version does not support multiple columns in the DISTRIBUTE BY clause.
        
+
        
+
        • one
        • many
        
+
        many
        
+
        distributeByHash
        
+
        =many
        
+
        • extendedGroupByClause
        
+
        This parameter is used to enable or disable Group By (grouping sets/cube/rollup) migration.
        
+
        true: enables the migration of GROUP BY().
        
+
        false: disables the migration of GROUP BY().
        
+
        • true
        • false
        
+
        false
        
+
        extendedGroupByClause=false
        
+
        • inToExists
        
+
        This parameter can be used to enable and disable query optimization from IN/NOT IN to EXISTS/NOT EXISTS.
        
+
        • true
        • false
        
+
        false
        
+
        inToExists=false
        
+
        • rowstoreToColumnstore
        
+
        Whether to convert row-store tables to column-store tables.
        
+
        If this parameter is set to true, all row-store tables are converted to column-store tables during script migration.
        
+
        • true
        • false
        
+
        false
        
+
        rowstoreToColumnstore=false
        
+
        • session_mode
        
+
        Default table type (SET/MULTISET) for CREATE TABLE.
        
+
        Teradata: The default table type is SET.
        
+
        ANSI: The default table type is MULTISET.
        
+
        • Teradata
        • ANSI
        
+
        Teradata
        
+
        session_mode=ANSI
        
+
        • tdMigrateALIAS
        
+
        Whether to enable the migration of ALIAS.
        
+
        true: enables the migration of ALIAS.
        
+
        false: disables the migration of ALIAS.
        
+
        • true
        • false
        
+
        false
        
+
        tdMigrateALIAS=true
        
+
        • tdMigrateDOLLAR
        
+
        Whether to enable the migration of static objects whose name starts with a dollar sign ($). This parameter is not applicable to dynamic objects, in format of ${}.
        
+
        true: Enclose the name of a static object with double quotation marks (").
        
+
        false: Disable the migration of static objects.
        
+
         NOTE: 
        For details, see Object name starting with $.
        
+
        
+
        • true
        • false
        
+
        true
        
+
        tdMigrateDOLLAR=true
        
+
        • tdMigrateLOCKoption
        
+
        Whether to enable the migration of queries with the LOCK keyword.
        
+
        true: enables the migration of such queries and comments out the LOCK keyword.
        
+
        false: disables the migration of such queries. DSC Migration Tool skips this query and logs the following information:
        
+
        Gauss does not have equivalent syntax for LOCK option in CREATE VIEW and INSERT statement. Please enable the config_param tdMigrateLockOption to comment the LOCK syntax in the statement.
        
+
         NOTE: 
        For details, see ACCESS LOCK.
        
+
        
+
        • true
        • false
        
+
        false
        
+
        tdMigrateLOCKoption=true
        
+
        • tdMigrateNULLIFZERO
        
+
        Whether to enable the migration of ZEROIFNULL().
        
+
        true: enables the migration of NULLIFZERO().
        
+
        false: disables the migration of NULLIFZERO().
        
+
        • true
        • false
        
+
        true
        
+
        tdMigrateNullIFZero=true
        
+
        • tdMigrateVIEWCHECKOPTION
        
+
        Whether to enable the migration of views containing CHECK OPTION.
        
+
        true: comments out such views during migration.
        
+
        If this parameter is set to false, such views are not migrated. The tool will copy the query as it is and record the following message:
        
+
        Gauss does not support WITH CHECK OPTION in CREATE VIEW. Please enable the config_param tdMigrateViewCheckOption to comment the WITH CHECK OPTION syntax in the statement.
        
+
        • true
        • false
        
+
        false
        
+
        tdMigrateVIEWCHECKOPTION=true
        
+
        • tdMigrateZEROIFNULL
        
+
        Whether to enable the migration of ZEROIFNULL.
        
+
        true: enables the migration of ZEROIFNULL().
        
+
        false: disables the migration of ZEROIFNULL().
        
+
        • true
        • false
        
+
        true
        
+
        tdMigrateZEROIFNULL=true
        
+
        • volatile
        
+
        Type of tables whose data is specific to a session and is stored only for the session. When the session ends, the data and tables are deleted.
        
+
        A volatile table can be a Migrating Tables table or an unlogged table.
        
+
         NOTE: 
        unlogged is supported in V100R002C60 and local temporary is not.
        
+
        
+
        • local temporary
        • unlogged
        
+
        local temporary
        
+
        volatile=unlogged
        
+
        • tdMigrateCharsetCase
        
+
        Whether to enable the migration of CHARACTER SET and CASESPECIFIC.
        
+
        true: comments out CHARACTER SET and CASESPECIFIC during script migration.
        
+
        false: disables the migration of CHARACTER SET and DSC. In this case, DSC copies CHARACTER SET, CASESPECIFIC and logs the following information with query details (such as the file name and statement position):
        
+
        Gauss does not have an equivalent syntax for CHARACTER SET & CASE SPECIFIC option in column-level. 
+You can rewrite this statement or set the configuration parameter tdMigrateCharsetCase to TRUE to comment the Character set & Case specific syntax in this statement.
        
+
        • true
        • false
        
+
        false
        
+
        tdMigrateCharsetCase=false
        
+
         NOTE: 
        If tdminatecharsetcase is set to true, comment out the special keyword of the character.
        
+
        
+
        • terdataUtilities
        
+
        Specifies whether the Teradata command line tool can be migrated.
        
+
        The following options are supported:
        
+
        • true
        • false
        
+
        • true
        • false
        
+
        true
        
+
        terdataUtilities=true
        
+
        • unique_primary_index_in_column_table
        
+
        Specifies whether unique indexes can be created for column-store tables.
        
+
        • true
        • false
        
+
        true
        
+
        unique_primary_index_in_column_table=true
        
+
        • default_charset
        
+
        Specifies whether default_charset can be migrated.
        
+
        The following options are supported:
        
+
        • LATIN
        • UNICODE
        • GRAPHIC
        
+
        • LATIN
        • UNICODE
        • GRAPHIC
        
+
        LATIN
        
+
        default_charset=LATIN
        
+
        • mergeImplementation
        
+
        mergeImplementation has the following two types:
        
+
        • using WITH clause
        • splitting the queries
        
+
        The following options are supported:
        
+
        • With
        • Split
        • None
        
+
        • With
        • Split
        • None
        
+
        None
        
+
        mergeImplementation=None
        
+
        • dsqlSupport
        
+
        Specifies whether dsql is supported.
        
+
        The following options are supported:
        
+
        • true
        • false
        
+
        • true
        • false
        
+
        false
        
+
        dsqlSupport=false
        
+
        • tdcolumnInSensitive
        
+
        Whether to remove column names that contain double quotes during migration.
        
+
        The following options are supported:
        
+
        • true
        • false
        
+
        • true
        • false
        
+
        false
        
+
        tdcolumnInSensitive=false
        
+
        • tdMigrateCASE_N
        
+
        Specifies the migration mode of the CASE_N for partitioning. Gauss does not support multilevel (nested) partitioning:
        
+
        The following options are supported:
        
+
        • comment
        • none
        
+
        • comment
        • none
        
+
        comment
        
+
        tdMigrateCASE_N=comment
        
+
        • tdMigrateRANGE_N
        
+
        Specifies the migration mode of the RANGE_N for partitioning. Gauss does not support multilevel (nested) partitioning:
        
+
        The following options are supported:
        
+
        • comment
        • none
        • range
        
+
        • comment
        • none
        • range
        
+
        range
        
+
        tdMigrateRANGE_N=range
        
+
        • tdMigrateAddMonth
        
+
        Specifies whether addMonth can be migrated.
        
+
        The following options are supported:
        
+
        • true
        • false
        
+
        If this parameter is set to true, ADD_MONTHS changes into mig_td_ext.ADD_MONTHS (added mig_td_ext) after the migration. Otherwise, migration is not supported.
        
+
        • true
        • false
        
+
        false
        
+
        tdMigrateAddMonth=false
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Configuring DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0015.html b/docs/dws/tool/dws_16_0015.html
new file mode 100644
index 00000000..3ddee55f
--- /dev/null
+++ b/docs/dws/tool/dws_16_0015.html
@@ -0,0 +1,222 @@
+
+
+
        Teradata Perl Configuration
        
+
        Teradata Perl parameters are used to customize rules for Teradata Perl script migration.
        
+
        Open the perl-migration.properties file in the config folder and set parameters in Table 1 as required.
        
+
         
        • Parameter values are case-insensitive.
        • You can modify the values of the following two parameters db-bteq-tag-name and db-tdsql-tag-name parameters in the following table:
        
+
        
+
        
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Parameters in the perl-migration.properties file
        Parameter
        
+
        Description
        
+
        Value Range
        
+
        Default
        
+
        Example
        
+
        • db-bteq-tag-name
        
+
        Scripts to be processed in Perl files.
        
+
        BTEQ: Only the scripts under the BTEQ tag are processed.
        
+
        • bteq
        
+
        bteq
        
+
        db-bteq-tag-name=bteq
        
+
        • db-tdsql-tag-name
        
+
        Only the scripts under the db-tdsql-tag-name tag are processed.
        
+
        SQL_LANG: Only the scripts under the SQL_LANG tag are processed.
        
+
        sql_lang
        
+
        sql_lang
        
+
        db-tdsql-tag-name=sql_lang
        
+
        • add-timing-on
        
+
        Whether to enable the insertion of scripts to calculate execution time.
        
+
        If it is enabled, the script will be added to each input file.
        
+
        • true
        • false
        
+
        false
        
+
        add-timing-on=true
        
+
        • remove-intermediate-files
        
+
        Whether to delete the intermediate SQL file generated by the DSC after the migration is complete.
        
+
        The intermediate files contain the BTEQ and SQL_LANG syntax in SQL files. These files are used as input for DSC.
        
+
        true: deletes the intermediate files.
        
+
        false: does not delete the intermediate files.
        
+
        • true
        • false
        
+
        true
        
+
        remove-intermediate-files=true
        
+
        • migrate-variables
        
+
        Whether to enable the migration of Perl variables containing SQL statements.
        
+
        Perl files can contain Perl variables with SQL statements. These variables are executed by using the PREPARE and EXECUTE statement in Perl. DSC can extract SQL statements from Perl variables and migrate them.
        
+
        true: enables the migration of Perl variables containing SQL statements.
        
+
        false: disables the migration of Perl variables containing SQL statements.
        
+
        Example 1:
        
+
        migrate-variables is set to true and input is as follows:
        
+
        1
        $V_SQL = "CT X1(C1 INT,C2 CHAR(30))";
+
        
+
+
        
+
        Output
        
+
        1
        CREATE TABLE X1(C1 INT,C2 CHAR(30));
+
        
+
+
        
+
        Example 2:
        
+
        Input
        
+
        1
+2
+3
+4
        $onesql ="SELECT trim(tablename) from dbc.tables       
+           WHERE databasename = '${AUTO_DQDB}' and tablename like 'V_%' 
+           order by 1;";
+  $sth_rundq = $dbh->execute_query($onesql);
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
          $onesql ="SELECT
+          TRIM( tablename )
+     FROM
+          dbc.tables
+     WHERE
+          databasename = '${AUTO_DQDB}'
+          AND tablename LIKE 'V_%'
+     ORDER BY
+          1
+;
+
+";
+  $sth_rundq = $dbh->execute_query($onesql);
+
        
+
+
        
+
        • true
        • false
        
+
        true
        
+
        migrate-variables=true
        
+
        • logging-level
        
+
        Logging level of Teradata Perl migration log files.
        
+
        error: Log only errors.
        
+
        warning: Log errors and warnings.
        
+
        info: Log errors, warnings, and activity information. This level contains all log information.
        
+
        • error
        • warning
        • info
        
+
        info
        
+
        logging-level=info
        
+
        • log-file-count
        
+
        Maximum number of log files retained, including the log files in use and archived log files.
        
+
        If the number of log files exceeds the upper limit, the earliest files will be deleted until the new log files are successfully archived.
        
+
        3 - 10
        
+
        5
        
+
        log-file-count=10
        
+
        • log-file-size
        
+
        Maximum file size.
        
+
        Upon reaching the specified size, a file is archived by adding a timestamp to the file name.
        
+
        Example:
        
+
        perlDSC_2018-07-08_16_12_08.log
        
+
        After the archiving, a new log file perlDSC.log with a timestamp is generated.
        
+
        1MB - 10MB
        
+
        5MB
        
+
        log-file-size=10MB
        
+
        • migrate-executequery
        
+
        Whether to enable the migration of execute_query containing SQL statements.
        
+
        true: enables the migration of execute_query containing SQL statements.
        
+
        false: disables the migration of execute_query containing SQL statements.
        
+
        The following is an example:
        
+
        migrate-executequery is set to true and input is as follows:
        
+
        1
+2
        my $rows1=$conn1->execute_query("sel ${selectclause} from ${databasename}.${tablename};
+         ");
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
        my $rows1=$conn1->execute_query("SELECT
+          ${selectclause}
+     FROM
+          ${databasename}.${tablename}
+;");
+
        
+
+
        
+
        • true
        • false
        
+
        true
        
+
        migrate-executequery =true
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Configuring DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0016.html b/docs/dws/tool/dws_16_0016.html
new file mode 100644
index 00000000..07e678bd
--- /dev/null
+++ b/docs/dws/tool/dws_16_0016.html
@@ -0,0 +1,199 @@
+
+
+
        MySQL Configuration
        
+
        MySQL parameters are used to customize rules for MySQL script migration.
        
+
        Open the features-mysql.properties file in the config folder and configure Parameters in the features-mysql.properties file as required.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Parameters in the features-mysql.properties file
        Parameter
        
+
        Description
        
+
        Value Range
        
+
        Default Value
        
+
        Example
        
+
        • table.databaseAsSchema
        • table.defaultSchema
        
+
        Whether to use a database name as the schema name. If a database name does not exist, the user-defined schema specified by table.schema will be used. If table.schema is not specified, the default schema will be used.
        
+
        • true
        • false
        • public
        
+
        • true
        • public
        
+
        • table.databaseAsSchema=true
        • table.defaultSchema=public
        
+
        • table.schema
        
+
        Name of the user-defined schema. If this parameter is specified, it will be directly used. In this case, even if useDatabaseAsSchema is set to true, the name of the current schema will be used.
        
+
        • schemaName
        
+
        • null
        
+
        • table.schema=
        
+
        • table.orientation
        
+
        Default data storage mode. Value ROW means row storage, and value COLUMN means column storage.
        
+
        • ROW
        • COLUMN
        
+
        • ROW
        
+
        • table.orientation=ROW
        
+
        • table.type
        
+
        Default table type, which can be partitioned table, replication table, round-robin table, and hash table.
        
+
        • HASH
        • REPLICATION
        • ROUND-ROBIN
        
+
        • HASH
        
+
        • table.type=HASH
        
+
        • table.tablespace
        
+
        Tablespace options
        
+
        • COMMENT
        • RESERVE
        
+
        • RESERVE
        
+
        • table.tablespace=RESERVE
        
+
        • table.partition-key.choose.strategy
        
+
        Policy for selecting the partition key
        
+
        • partitionKeyChooserStrategy
        
+
        • partitionKeyChooserStrategy
        
+
        • table.partition-key.choose.strategy=partitionKeyChooserStrategy
        
+
        • table.partition-key.name
        
+
        Partition key. If this parameter is not specified, the default selection policy will be used. If there are multiple columns, separate them with commas (,). The column names are case insensitive.
        
+
        • Reserved parameter
        
+
        • null
        
+
        • table.partition-key.name=
        
+
        • table.compress.mode
        
+
        Compression mode. If keyword COMPRESS is specified in CREATE TABLE, the compression feature will be triggered in the case of bulk INSERT operations. If this feature is enabled, a scan will be performed on all tuple data within the page to generate a dictionary and then the tuple data will be compressed and stored. If NOCOMPRESS is used, tables will not be compressed.
        
+
        • COMPRESS
        • NOCOMPRESS
        
+
        • NOCOMPRESS
        
+
        • table.compress.mode=NOCOMPRESS
        
+
        • table.compress.row
          
+
        • table.compress.column
        
+
        Compression level of table data. It determines the compression ratio and duration.
        
+
        • YES
        • NO
          
+
        • YES
        • NO
        • LOW
        • MIDDLE
        • HIGH
        
+
        • NO
          
+
          
+
        • LOW
        
+
        • table.compress.row=NO
          
+
          
+
        • table.compress.column=LOW
        
+
        • table.compress.level
        
+
        Table data compression ratio and duration at the same compression level. This divides a compression level into sublevels, providing more choices for the compression ratio and duration. As the value becomes larger, the compression ratio becomes higher and duration longer at the same compression level.
        
+
        • 0
        • 1
        • 2
        • 3
        
+
        • 0
        
+
        • table.compress.level=0
        
+
        • table.database.template
        
+
        Database template
        
+
        • Reserved parameter
        
+
        • template0
        
+
        table.database.template=template0
        
+
        • table.database.encoding
        
+
        A database code.
        
+
        • UTF8
        • SQL_ASCII
        • GBK
        • Latin1 codes
        
+
        • UTF8
        
+
        table.database.encoding=UTF8
        
+
        • table.index.rename
        
+
        Whether to rename an index when creating the index.
        
+
        • true
        • false
        
+
        false
        
+
        table.index.rename=false
        
+
        • table.database.onlyFullGroupBy
        
+
        Whether all non-aggregation columns after SELECT are displayed in GROUP BY.
        
+
        • true
        • false
        
+
        true
        
+
        table.database.onlyFullGroupBy=true
        
+
        • table.database.realAsFloat
        
+
        Used for converting the data type. The default value is false, indicating that the data type is converted to DOUBLE PRECISION. When the value is changed to true, the data type is converted to REAL.
        
+
        • true
        • false
        
+
        false
        
+
        table.database.realAsFloat=false
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Configuring DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0017.html b/docs/dws/tool/dws_16_0017.html
new file mode 100644
index 00000000..283f6558
--- /dev/null
+++ b/docs/dws/tool/dws_16_0017.html
@@ -0,0 +1,24 @@
+
+
+
        Migration Process
        
+
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0018.html b/docs/dws/tool/dws_16_0018.html
new file mode 100644
index 00000000..724944ea
--- /dev/null
+++ b/docs/dws/tool/dws_16_0018.html
@@ -0,0 +1,266 @@
+
+
+
        Prerequisites
        
+
        Executing Custom DB Scripts
        Custom scripts are executed to support input keywords that do not exist in certain versions of the target database. These scripts must be executed in each target database before the migration.
        
+
        Table 1 describes the custom scripts in the DSC/scripts/ directory. For details about how to execute custom scripts, see Custom DB Script Configuration.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Custom DB scripts
        Script
        
+
        Description
        
+
        mig_fn_get_datatype_short_name.sql
        
+
        Custom DB script for Teradata functions
        
+
        mig_fn_castasint.sql
        
+
        Custom DB script for migration of CAST AS INTEGER
        
+
        vw_td_dbc_tables.sql
        
+
        Custom DB script for migration of DBC.TABLES
        
+
        vw_td_dbc_indices.sql
        
+
        Custom DB script for migration of DBC.INDICES
        
+
        
+
        
+
        
+
        Follow the steps to execute custom DB scripts:
        
+
        1. Use any of the following methods to execute the required scripts in all target databases for which migration is to be performed:
          • Use gsql.
            • Use gsql to connect to the target database and paste all content in the SQL file to gsql, which will automatically execute the pasted contents.
              Run the following command to connect to the database:
              
+
              1
              gsql -h <host_addr_xxx.xxx.xxx.xxx> -d <database_name> -U <user_name> -W <password> -p <port_number> -r
+
              
+
+
              
+
            • Use gsql to connect to the target database and execute a SQL file.
              Run the following command to connect to the database and run the SQL file:
              
+
              1
              gsql -h <host_addr_xxx.xxx.xxx.xxx> -d <database_name> -U <user_name>  -W <password>  -p <port_number> -f <filename.sql> -o <output_filename> -L <log_filename.log>  -r
+
              
+
+
              
+
            
+
          • Use Data Studio.
            Use Data Studio to connect to the target database, and then open and run the SQL file in Data Studio.
            
+
          
+
        
+
        Custom DB Script Configuration
        Custom scripts are SQL files used to migrate from Teradata/Oracle the input keywords that do not exist in the target database.
        
+
        These scripts must be executed in each target database before the migration.
        
+
        Open the scripts folder in the release package. Table 2 lists the folders and files in the scripts folder.
        
+
        The SQL files contain the scripts for the custom migration functions. The GaussDB(DWS) database needs to use these functions to support specific features of Teradata.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 2 Custom DB scripts for DSC
        Folder
        
+
        Script File
        
+
        Description
        
+
        -- scripts
        
+
        -
        
+
        Folder: all scripts
        
+
        ------ teradata
        
+
        -
        
+
        Folder: Teradata functions and scripts
        
+
        -------- view
        
+
        -
        
+
        Folder: scripts to configure views
        
+
        -
        
+
        vw_td_dbc_tables.sql
        
+
        Script: used to enable migration of Teradata DBC.TABLES
        
+
        -
        
+
        vw_td_dbc_indices.sql
        
+
        Script: used to enable migration of Teradata DBC.INDICES
        
+
        -------- function
        
+
        -
        
+
        Folder: scripts to configure Teradata system functions
        
+
        -X
        
+
        mig_fn_get_datatype_short_name.sql
        
+
        Script: used to enable migration of Teradata DBC.COLUMNS
        
+
        -
        
+
        mig_fn_castasint.sql
        
+
        Script: used to enable migration of CAST AS INTEGER
        
+
        --------db_scripts
        
+
        -
        
+
        Folder: scripts to enable Teradata custom functions
        
+
        -
        
+
        mig_fn_get_datatype_short_name.sql
        
+
        Script: used to enable migration of Teradata DBC.COLUMNS
        
+
        --------core
        
+
        -
        
+
        Folder: Teradata core scripts
        
+
        -
        
+
        teradatacore.pm
        
+
        Script: used to perform Perl migration
        
+
        
+
        
+
        
+
        Configuring DSC and Migration Properties
        To configure DSC, configure parameters in the configuration files in the config folder of DSC. Table 3 describes the parameters.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 3 Parameters for configuring DSC
        Migration
        
+
        Configuration File
        
+
        Parameter
        
+
        Teradata SQL Migration
        
+
        
+        		
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
        deleteToTruncate=True/False
+distributeByHash=one/many
+extendedGroupByClause=True/False
+inToExists=True/False
+rowstoreToColumnstore=True/False
+session_mode=Teradata/ANSI
+tdMigrateDollar=True/False
+tdMigrateALIAS=True/False
+tdMigrateNULLIFZero=True/False
+tdMigrateZEROIFNULL=True/False
+volatile=local temporary/unlogged
+
        
+
+
        
+
        Teradata Perl Migration
        
+        		
+
        1
+2
+3
+4
+5
+6
+7
+8
        add-timing-on=True/False
+db-bteq-tag-name=bteq
+db-tdsql-tag-name=sql_lang
+logging-level=error/warning/info
+migrate-variables=True/False
+remove-intermediate-files=True/False
+target_files=overwrite/cancel
+migrate-executequery=True/False
+
        
+
+
        
+
        MySQL SQL Migration
        
+        		
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
        table.databaseAsSchema=true
+table.defaultSchema=public
+table.schema=
+table.orientation=ROW
+table.type=HASH
+table.partition-key.choose.strategy=partitionKeyChooserStrategy
+table.partition-key.name=
+table.compress.mode=NOCOMPRESS
+table.compress.level=0
+table.compress.row=NO
+table.compress.column=LOW
+table.database.template=template0
+table.index.rename=false
+table.database.onlyFullGroupBy=true
+table.database.realAsFloat=false
+
        
+
+
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Migration Process
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0019.html b/docs/dws/tool/dws_16_0019.html
new file mode 100644
index 00000000..6e5560cb
--- /dev/null
+++ b/docs/dws/tool/dws_16_0019.html
@@ -0,0 +1,21 @@
+
+
+
        Preparations
        
+
        Before the migration, create an input folder and an output folder, and copy all the SQL scripts to be migrated to the input folder. The following procedure describes how to prepare for the migration in Linux.
        
+
        1. Run the following commands to create an input folder and an output folder. You can create the folder anywhere based on your preferences. You can also use the default folders for input, output, provided as part of package.
          mkdir input
+mkdir output
          
+
           
          The tool reads the input folder in batches randomly. After the migration starts, it is recommended the users should not perform any modification on the input folder and files. Abnormal operations will affect the output result of the tool.
          
+
          
+
        2. Copy all SQL scripts to be migrated to the input folder.
           
          • If the encoding format of source files is not UTF-8, perform the following steps:
            1. Open the application.properties file in the config folder.
            2. Change the value of encodingFormat in the application.properties file to the required encoding format.
            
+
            DSC supports the UTF-8, ASCII, and GB2312 encoding formats. The values of encodingFormat are case-insensitive.
            
+
          • To obtain the encoding format of a source file in Linux, run the following command on the server where the source file is located:
            file -bi <Input file name>
            
+
          
+
          
+
        
+
        
+
        
+
        
+
        Parent topic: Migration Process
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0020.html b/docs/dws/tool/dws_16_0020.html
new file mode 100644
index 00000000..d4596158
--- /dev/null
+++ b/docs/dws/tool/dws_16_0020.html
@@ -0,0 +1,109 @@
+
+
+
        Executing DSC
        
+
        Important Notes
        • Before starting DSC, specify the output folder path. Separate the input folder path, output folder path, and log path with spaces. The input folder path cannot contain spaces which will cause an error when DSC is used for migrating data. For details, see Troubleshooting.
        
+
        
+
        • If the output folder contains subfolders or files, DSC deletes the subfolders and files or overwrites them based on parameter settings in the application.properties configuration file in the config folder before the migration. Deleted or overwritten subfolders and files cannot be restored by DSC.
        • If migration tasks are performed concurrently on the same server (by the same or different DSCs), different migration tasks must use different output folder paths and log paths.
        • You can specify a log path by configuring optional parameters. If the path is not specified, DSC automatically creates a log folder under TOOL_HOME. For details, see Log Reference.
        
+
        Migration Methods
        You can run the runDSC.sh or runDSC.bat command to perform a migration task on Windows and Linux. For details, see Table 1.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Migration on Windows and Linux
        Migration
        
+
        CLI Parameter
        
+
        Teradata SQL Migration
        
+
        
+
        
+
        > ./runDSC.sh
+ --source-db Teradata
+[--application-lang SQL]
+[ --input-folder <input-script-path> ]
+[--output-folder <output-script-path> ]
+[--log-folder <log-path>]
+[--target-db/-T][Optional]
        
+
        > runDSC.bat
+--source-db Teradata
+[--application-lang SQL]
+[ --input-folder <input-script-path> ]
+[--output-folder <output-script-path> ]
+[--log-folder <log-path>]
+[--target-db/-T][Optional]
        
+
        Teradata Perl Migration
        
+
        
+
        > ./runDSC.sh
+--source-db Teradata
+[--application-lang Perl]
+[--input-folder <input-script-path> ]
+[--output-folder <output-script-path> ]
+[--log-folder <log-path>]
+[--target-db/-T][Optional]
        
+
        > runDSC.bat
+  --source-db Teradata
+[--application-lang Perl]
+[--input-folder <input-script-path> ]
+[--output-folder <output-script-path> ]
+[--log-folder <log-path>]
+[--target-db/-T][Optional]
        
+
        MySQL SQL Migration
        
+
        
+
        > ./runDSC.sh
+--source-db MySql
+[--application-lang SQL]
+[--input-folder <input-script-path>]
+[--output-folder <output-script-path>]
+[--log-folder <log-path>]
+[--conversion-type <conversion-Type-BulkOrBlogic>]
+[--target-db/-T]
        
+
        > runDSC.bat
+--source-db MySql
+[--application-lang SQL]
+[--input-folder <input-script-path>]
+[--output-folder <output-script-path>]
+[--log-folder <log-path>]
+[--conversion-type <conversion-Type-BulkOrBlogic>]
+[--target-db/-T]
        
+
        
+
        
+
        
+
         
        • The CLI parameters are described as follows:
          • source-db specifies the source database. The value can be Teradata, which is case-insensitive.
          • conversion-type specifies the migration type. This parameter is optional. DSC supports the following migration types:
            Bulk: migrates DML and DDL scripts.
            
+
            BLogic: migrates service logic, such as stored procedures and functions.
            
+
          • target-db specifies the target database. The parameter value is GaussDB A.
          
+
        • Command output description:
          Migration process start time indicates the migration start time and Migration process end time indicates the migration end time. Total process time indicates the total migration duration, in milliseconds. In addition, the total number of migrated files, total number of processors, number of used processors, log file path, and error log file path are also displayed on the console.
          
+
        
+
        
+
        Examples
        • Example 1: Run the following command to migrate the SQL file of the Oracle database to the SQL script of GaussDB on Linux:
          ./runDSC.sh --source-db Teradata --input-folder D:\test\conversion\input --output-folder D:\test\conversion\output --log-folder D:\test\conversion\log --conversion-type ddl --targetdb gaussdbA
          
+
        • Example 2: Run the following command to migrate the SQL file of the Oracle database to the SQL script of GaussDB on Windows:
          runDSC.bat --source-db Teradata --input-folder D:\test\conversion\input --output-folder D:\test\conversion\output --log-folder D:\test\conversion\log --conversion-type ddl --targetdb gaussdbA
          
+
        
+
        Migration details are displayed on the console (including the progress and completion status):
        
+
        ********************** Schema Conversion Started *************************  
+DSC process start time : Mon Jan 20 17:24:49 IST 2020  
+Statement count progress 100% completed [FILE(1/1)]    
+Schema Conversion Progress 100% completed  
+**************************************************************************   
+Total number of files in input folder : 1  
+Total number of valid files in input folder : 1  
+**************************************************************************   
+Log file path :....../DSC/DSC/log/dsc.log  
+Error Log file :    
+DSC process end time : Mon Jan 20 17:24:49 IST 2020  
+DSC total process time : 0 seconds  
+********************* Schema Conversion Completed ************************
        
+
        
+
        
+
        
+
        
+
        Parent topic: Migration Process
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0021.html b/docs/dws/tool/dws_16_0021.html
new file mode 100644
index 00000000..342b6204
--- /dev/null
+++ b/docs/dws/tool/dws_16_0021.html
@@ -0,0 +1,24 @@
+
+
+
        Viewing Output Files and Logs
        
+
        Viewing and Verifying Output Files
        After the migration is complete, you can use a comparison tool (for example, BeyondCompare®) to compare the output file with its input file. Input SQL files can also be formatted for easier comparison.
        
+
        
+
        1. Run the following command in Linux and view output files in the output folder. Operations in Windows are not described here.
          cd OUTPUT
+ls
          
+
          Information similar to the following is displayed:
          
+
          formattedSource    output
+user1@node79:~/Documentation/DSC/OUTPUT> cd output
+user1@node79:~/Documentation/DSC/OUTPUT/output> ls
+in_index.sql    input.sql    Input_table.sql    in_view.sql    MetadataInput.sql
+user1@node79:~/Documentation/DSC/OUTPUT/output>
          
+
        1. Use the comparison tool to compare the output file with its input file. Check whether the keywords in the migrated SQL file meet the requirements of the target database. If not, contact technical support.
        
+
        Viewing Log Files
        Execution information and error messages are written into corresponding log files. For details, see Log Reference.
        
+
        Check whether errors are logged. If they are, rectify the faults by following the instructions in Troubleshooting.
        
+
        
+
        
+
        
+
        
+
        Parent topic: Migration Process
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0022.html b/docs/dws/tool/dws_16_0022.html
new file mode 100644
index 00000000..967d21b2
--- /dev/null
+++ b/docs/dws/tool/dws_16_0022.html
@@ -0,0 +1,12 @@
+
+
+
        Troubleshooting
        
+
        Migration related issues can be classified into:
        
+
        • Tool execution issues: No output or incorrect output is displayed because DSC partially or fully failed to be executed. For more information about known issues and their solutions, see Troubleshooting.
        • Migration syntax issues: DSC did not correctly recognize or migrate the migration syntax. For details, see Constraints and Limitations.
        
+
        
+
        
+
        
+
        Parent topic: Migration Process
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0023.html b/docs/dws/tool/dws_16_0023.html
new file mode 100644
index 00000000..42fb0555
--- /dev/null
+++ b/docs/dws/tool/dws_16_0023.html
@@ -0,0 +1,20 @@
+
+
+
        CLI Reference
        
+
        
+
        
+
        
+
+
+
        
+
        Parent topic: Using DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0024.html b/docs/dws/tool/dws_16_0024.html
new file mode 100644
index 00000000..ff5db3f9
--- /dev/null
+++ b/docs/dws/tool/dws_16_0024.html
@@ -0,0 +1,29 @@
+
+
+
        Database Schema Conversion
        
+
        Functionality
        runDSC.sh and runDSC.bat are used to migrate the schemas and queries of Teradata and MySQL to GaussDB(DWS), respectively.
        
+
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0025.html b/docs/dws/tool/dws_16_0025.html
new file mode 100644
index 00000000..39dac053
--- /dev/null
+++ b/docs/dws/tool/dws_16_0025.html
@@ -0,0 +1,206 @@
+
+
+
        Migration Parameters
        
+
        Parameter Description
        
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Parameters
        Long
        
+
        Short
        
+
        Data Type
        
+
        Description
        
+
        Value Range
        
+
        Default Value
        
+
        Example
        
+
        --source-db
        
+
        -S
        
+
        String
        
+
        Source database
        
+
        • Teradata
        • MySQL
        
+
        N/A
        
+
        --source-db Teradata(or)
        
+
        -S Teradata
        
+
        --input-folder
        
+
        -I
        
+
        String
        
+
        Input folder containing Teradata or Oracle scripts
        
+
        N/A
        
+
        N/A
        
+
        --input-folder /home/testmigration/Documentation/input
        
+
        (or)
        
+
        -I /home/testmigration/Documentation/input
        
+
        --output-folder
        
+
        -O
        
+
        String
        
+
        Output folder where the migrated scripts are saved
        
+
        N/A
        
+
        N/A
        
+
        --output-folder /home/testmigration/Documentation/output(or)-O /home/testmigration/Documentation/output
        
+
        --application-lang
        
+
        -A
        
+
        String
        
+
        Application language parser used for migration
        
+
        SQL: Migrate SQL schemas or scripts in SQL files.
        
+
        Perl: Migrate BTEQ or SQL_LANG scripts in Perl files.
        
+
        • SQL
        • Perl
        
+
        SQL
        
+
        --application-lang Perl
        
+
        or
        
+
        -A Perl
        
+
        --conversion-type
        
+
        -M
        
+
        String
        
+
        Migration type. Set this parameter based on input scripts.
        
+
        Bulk: Migrate DML and DDL scripts.
        
+
        BLogic: Migrate service logic, such as procedures and functions.
        
+
        BLogic is used only for Oracle PL/SQL.
        
+
        • Bulk
        • BLogic
        
+
        Bulk
        
+
        --conversion-type ddl
        
+
        or
        
+
        -M ddl
        
+
        --log-folder
        
+
        -L
        
+
        String
        
+
        Log file Path
        
+
        N/A
        
+
        N/A
        
+
        --log-folder /home/testmigration/Documentation(or)-L /home/testmigration/Documentation
        
+
        --version-number
        
+
        -VN
        
+
        String
        
+
        Oracle specified parameter
        
+
        Oracle
        
+
        N/A
        
+
        --version-number
        
+
        or
        
+
        -V1R8_330
        
+
        --target-db
        
+
        -T
        
+
        String
        
+
        Target database
        
+
        • gaussdbA
        
+
        gaussdbA
        
+
        --target-db gaussdbA (or)
        
+
        -T gaussdbA
        
+
        
+
        
+
        
+
        Usage Guideline
        It is mandatory to specify the source database, input folder path, and output folder path, and optional to specify the migration type and log path.
        
+
         
        If a user does not specify the logging path, then the tool creates the log folder in the TOOL_HOME path and saves all the logs in this log folder.
        
+
        
+
        
+
        Examples
        ./runDSC.sh --source-db Teradata --input-folder opt/DSC/DSC/input/oracle/ --output-folder /opt/DSC/DSC/output/ --log-folder /opt/DSC/DSC/log/ --application-lang SQL --conversion-type ddl --targetdb gaussdbA
        
+
        
+
        System Response
        ********************** Schema Conversion Started *************************
+DSC process start time : Mon Jan 20 17:24:49 IST 2020
+Statement count progress 100% completed [FILE(1/1)]
+
+Schema Conversion Progress 100% completed
+************************************************************************** 
+Total number of files in input folder : 1
+************************************************************************** 
+Log file path :....../DSC/DSC/log/dsc.log
+DSC process end time : Mon Jan 20 17:24:49 IST 2020
+DSC total process time : 0 seconds
+********************* Schema Conversion Completed ************************
        
+
         
        If there is no sql file present in the input folder, then the following message is displayed in console:
        
+
        
+
        
+
        
+
        Environment Creation and Restoration Procedure (database and database user)
        Creating a GaussDB(DWS) - Database and Schema
        
+
        1. Log in to postgres:
          gsql -p <port> -d postgres 
+drop database <database name>;
+create database <database name>;
+\c <database name>
+GRANT ALL PRIVILEGES ON DATABASE <database name> TO <user>;
+grant database to <user>;\q
+gsql -p <port> -d <database name> -U <user> -W <password> -h <IP> -f
+drop database <database name>;
+create database <database name>;
+\c <database name>;
+GRANT ALL PRIVILEGES ON DATABASE <database name> TO <user>;
+gsql -p <port> -d <database name> -U <user> -W <password>  -f
          
+
        2. Run all files in setup.
        
+
        Commands:
        
+
        sh runDSC.sh -S oracle -M blogic -I <input path> 
+sh runDSC.sh -I input/ -S oracle -M ddl -L log_temp -P input/bulk/1_table/ 
        
+
        
+
        
+
        
+
        
+
        Parent topic: Database Schema Conversion
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0026.html b/docs/dws/tool/dws_16_0026.html
new file mode 100644
index 00000000..c778c7ef
--- /dev/null
+++ b/docs/dws/tool/dws_16_0026.html
@@ -0,0 +1,51 @@
+
+
+
        Teradata SQL Migration
        
+
        DSC supports the migration from Teradata to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and type conversion.
        
+
        Performing Teradata SQL Migration
        Run the following commands to set the source database, input and output folder paths, log paths, and application language.
        
+
        Linux:
        
+
        ./runDSC.sh 
+--source-db Teradata
+[--input-folder <input-script-path>] 
+[--output-folder <output-script-path>]
+[--log-folder <log-path>]
+[--application-lang SQL]
        
+
        Windows:
        
+
        runDSC.bat 
+--source-db Teradata
+[--input-folder <input-script-path>] 
+[--output-folder <output-script-path>]
+[--log-folder <log-path>]
+[--application-lang SQL]
        
+
        For example:
        
+
        Linux:
        
+
        ./runDSC.sh --source-db Teradata --target-db GaussDBA --input-folder /opt/DSC/DSC/input/teradata/ --output-folder /opt/DSC/DSC/output/ --log-folder /opt/DSC/DSC/log/ --application-lang SQL --conversion-type Bulk
        
+
        Windows:
        
+
        runDSC.bat --source-db Teradata --target-db GaussDBA --input-folder D:\test\conversion\input --output-folder D:\test\conversion\output --log-folder D:\test\conversion\log --application-lang SQL --conversion-type Bulk
        
+
        During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console. Execution information and errors will be recorded in SQL Migration Logs.
        
+
        ********************** Schema Conversion Started *************************  
+DSC process start time : Mon Jan 20 17:24:49 IST 2020  
+Statement count progress 100% completed [FILE(1/1)]    
+Schema Conversion Progress 100% completed  
+**************************************************************************   
+Total number of files in input folder : 1  
+**************************************************************************   
+Log file path :....../DSC/DSC/log/dsc.log  
+DSC process end time : Mon Jan 20 17:24:49 IST 2020  
+DSC total process time : 0 seconds  
+********************* Schema Conversion Completed ************************
        
+
        For details about how to migrate Teradata SQL using DSC, see Executing DSC.
        
+
         
        During the migration, the metadata of the input script can be called and is stored in the following files:
        
+
        • Teradata migration
          1.teradata-set-table.properties
          
+
        
+
        Clear the preceding files in the following scenarios:
        
+
        • Migration of different files
        • Migration of the same file with different parameter settings
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Database Schema Conversion
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0027.html b/docs/dws/tool/dws_16_0027.html
new file mode 100644
index 00000000..ae5f7911
--- /dev/null
+++ b/docs/dws/tool/dws_16_0027.html
@@ -0,0 +1,96 @@
+
+
+
        Teradata Perl Migration
        
+
        Overview
        This section describes how to migrate Teradata Perl files.
        
+
        Run the runDSC.sh or runDSC.bat command and set --application-lang to perl to migrate Teradata BTEQ or SQL_LANG scripts in Perl files to Perl-compatible GaussDB(DWS). After migrating Perl files, you can verify the migration by comparing the output file with its input file using a comparison tool.
        
+
        The Perl file migration process is as follows:
        
+
        1. Complete the steps in section Prerequisites.
        2. Create an input folder and copy the Perl files to be migrated to the folder. For example, create a /migrationfiles/perlfiles folder.
        3. Execute DSC to migrate Perl scripts and set db-bteq-tag-name to BTEQ or db-tdsql-tag-name to SQL_LANG.
          1. The DSC extracts the BTEQ or SQL_LANG scripts from the Perl files.
            1. BTEQ is the tag name, which contains a set of BTEQ scripts. This tag name is configurable using the db-bteq-tag-name configuration parameter in perl-migration.properties file.
            2. SQL_LANG is another tag name, which contains Teradata SQL statements. This is also configurable using the db-tdsql-tag-name configuration parameter.
            
+
          2. DSC invokes the Teradata SQL to migrate the extracted SQL scripts. For details about Teradata SQL migration, see Teradata SQL Migration.
          3. Perl files are embedded in the migrated scripts.
          
+
        4. DSC creates the migrated files in the specified output folder. If no output folder is specified, DSC creates an output folder named converted in the input folder, for example, /migrationfiles/perlfiles/converted.
           
          • Perl variables containing SQL statements can also be migrated to SQL by setting the migrate-variables parameter.
          • For perl v 5.10.0 and later are compatible.
          
+
          
+
        
+
        
+
        Teradata Perl Migration
        To migrate Perl files, execute DSC with --source-db Teradata and --application-lang Perl parameter values. DSC supports the migration of BTEQ and SQL_LANG scripts. You can specify the scripts to be migrated by setting db-bteq-tag-name or db-tdsql-tag-name.
        
+
        
+
        Run the following commands to set the source database, input and output folder paths, log paths, and application language.
        
+
        Linux:
        
+
        ./runDSC.sh 
+--source-db|-S Teradata
+[--application-lang|-A Perl]
+[--input-folder|-I <input-script-path>]
+[--output-folder|-O <output-script-path>] 
+[--conversion-type|-M <Bulk or BLogic>]
+[--log-folder|-L <log-path>]
        
+
        Windows:
        
+
        runDSC.bat
+--source-db|-S Teradata
+[--application-lang|-A Perl]
+[--input-folder|-I <input-script-path>]
+[--output-folder|-O <output-script-path>] 
+[--conversion-type|-M <Bulk or BLogic>]
+[--log-folder|-L <log-path>]
        
+
        For example:
        ./runDSC.sh --input-folder /opt/DSC/DSC/input/teradata_perl/ --output-folder /opt/DSC/DSC/output/ --source-db teradata --conversion-type Bulk --application-lang PERL
        
+
        
+
        During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console.
        
+
        ********************** Schema Conversion Started *************************  
+DSC process start time : Mon Jan 20 17:24:49 IST 2020  
+Statement count progress 100% completed [FILE(1/1)]    
+Schema Conversion Progress 100% completed  
+**************************************************************************   
+Total number of files in input folder : 1  
+**************************************************************************  
+Log file path :....../DSC/DSC/log/dsc.log  
+DSC process end time : Mon Jan 20 17:24:49 IST 2020  
+DSC total process time : 0 seconds 
+ ********************* Schema Conversion Completed ************************
        
+
        For details about the parameters for Teradata Perl migration, see Teradata Perl Configuration.
        
+
        For details about CLI parameters, see Database Schema Conversion.
        
+
         
        • DSC formats the input files and saves them in the output folder. You can compare the formatted input files with the output files.
        • Ensure that there are no spaces in the input path. If there is a space, DSC throws an error. For details, see Troubleshooting.
        • For details about logs, see Log Reference.
        • If the output folder contains subfolders or files, DSC deletes the subfolders and files or overwrites them based on parameter settings in the application.properties configuration file in the config folder before the migration. Deleted or overwritten subfolders and files cannot be restored by DSC.
        • Process start time indicates the migration start time and Process end time indicates the migration end time. Process total time indicates the total migration duration, in milliseconds. In addition, the total number of migrated files, total number of processors, number of used processors, log file path, and error log file path are also displayed on the console.
        • Set --add-timing-on to true in the perl-migration.properties file to add a custom script to calculate statement execution time.
          Example:
          
+
          Input
          1
+2
+3
+4
          $V_SQL2 = "SELECT T1.userTypeInd FROM T07_EBM_CAMP T1  WHERE T1.Camp_List_Id = '$abc'";
+$STH = $dbh->prepare($V_SQL2);
+$sth->execute();
+@rows = $sth->fetchrow();
+
          
+
+
          
+
          
+
          Output
          $V_SQL2 = "SELECT T1.userTypeInd FROM T07_EBM_CAMP T1  WHERE T1.Camp_List_Id = '$abc'";
+$STH = $dbh->prepare($V_SQL2);
+use Time::HiRes qw/gettimeofday/;
+my $start = [Time::HiRes::gettimeofday()];
+$sth->execute();
+my $elapsed = Time::HiRes::tv_interval($start);
+$elapsed = $elapsed * 1000;
+printf("Time: %.3f ms\n", $elapsed);
+@rows = $sth->fetchrow();
          
+
          
+
        • GROUP and OTHERS must not have write permission for the files or folders specified by--input-folder. That is, the privilege for the folder specified by --input-folder must not be higher than 755. For security purposes, DSC will not be executed if the input files or folders have the write permission.
        • If migration tasks are executed concurrently, the input folder must be unique for each task.
        
+
        
+
        Best Practices
        To optimize the migration, you are advised to follow the standard practices:
        
+
        • BTEQ scripts must be in the following format:
          print BTEQ <<ENDOFINPUT;
+TRUNCATE TABLE employee;
+ENDOFINPUT
+close(BTEQ);
          
+
        
+
        • SQL_LANG scripts must be in the following format:
          1
+2
+3
          my $sSQL=<<SQL_LANG;
+TRUNCATE TABLE employee;
+SQL_LANG
+
          
+
+
          
+
        
+
        • Comment must not contain the following information:
          • print BTEQ <<ENDOFINPUT
          • ENDOFINPUT
          • close(BTEQ)
          • my $sSQL=<<SQL_LANG
          • SQL_LANG
          
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Database Schema Conversion
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0028.html b/docs/dws/tool/dws_16_0028.html
new file mode 100644
index 00000000..1fdfdf70
--- /dev/null
+++ b/docs/dws/tool/dws_16_0028.html
@@ -0,0 +1,57 @@
+
+
+
        MySQL SQL Migration
        
+
        DSC supports the migration from MySQL to GaussDB(DWS), including the migration of schemas, DML, queries, system functions, and PL/SQL.
        
+
        Performing MySQL Migration on Linux
        Run the following command on Linux to start the migration. You need to specify the source database, input and output folder paths, and log paths. The application language is SQL.
        
+
        ./runDSC.sh
+--source-db MySQL 
+[--input-folder <input-script-path>] 
+[--output-folder <output-script-path>]
+[--application-lang SQL] 
+[--conversion-type <conversion-type>] 
+[--log-folder <log-path>]
        
+
        During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console.
        
+
        ./runDSC.sh --source-db MySQL --input-folder /opt/DSC/DSC/input/mysql/ --output-folder /opt/DSC/DSC/output/ --application-lang SQL --conversion-type BULK --log-folder/opt/DSC/DSC/log/
        
+
        ********************** Schema Conversion Started *************************  
+DSC process start time : Mon Jan 20 17:24:49 IST 2020  
+Statement count progress 100% completed [FILE(1/1)]    
+Schema Conversion Progress 100% completed  
+**************************************************************************   
+Total number of files in input folder : 1  
+Total number of valid files in input folder : 1  
+**************************************************************************   
+Log file path :....../DSC/DSC/log/dsc.log  
+Error Log file :    
+DSC process end time : Mon Jan 20 17:24:49 IST 2020  
+DSC total process time : 0 seconds 
+********************* Schema Conversion Completed ************************
        
+
        
+
        Performing MySQL Migration on Windows
        Run the following command on Windows to start the migration. You need to specify the source database, input and output folder paths, and log paths. The application language can be SQL or Perl. The default language is SQL. The migration type can be Bulk or BLogic.
        
+
        runDSC.bat
+--source-db MySQL 
+[--input-folder <input-script-path>] 
+[--output-folder <output-script-path>]
+[--application-lang SQL] 
+[--conversion-type <conversion-type>] 
+[--log-folder <log-path>]
        
+
        During the execution of DSC, the migration summary, including the progress and completion status, is displayed on the console.
        
+
        runDSC.bat --source-db MySQL --target-db GaussDBA --input-folder D:\test\conversion\input --output-folder D:\test\conversion\output --log-folder D:\test\conversion\log --application-lang SQL --conversion-type  BULK
        
+
        ********************** Schema Conversion Started *************************  
+DSC process start time : Mon Jan 20 17:24:49 IST 2020  
+Statement count progress 100% completed [FILE(1/1)]    
+Schema Conversion Progress 100% completed  
+**************************************************************************   
+Total number of files in input folder : 1  
+**************************************************************************   
+Log file path :....../DSC/DSC/log/dsc.log  
+DSC process end time : Mon Jan 20 17:24:49 IST 2020  
+DSC total process time : 0 seconds  
+********************* Schema Conversion Completed ************************
        
+
        
+
        
+
        
+
        
+
        Parent topic: Database Schema Conversion
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0029.html b/docs/dws/tool/dws_16_0029.html
new file mode 100644
index 00000000..316a5419
--- /dev/null
+++ b/docs/dws/tool/dws_16_0029.html
@@ -0,0 +1,54 @@
+
+
+
        Verification
        
+
        Verification After Migration
        After DSC converts the source sql files, execute the converted files on target GaussDB(DWS) and provide a report with details of number of statements succeeded and failed.
        
+
        After the DSC finishes the translation, it will invoke (controlled through a configuration item) post migration verification script. The verification script (for details about the configuration, see the configuration file) is connected to the target GaussDB database and executed.
        
+
        The post migration verification script will connect to the target gauss database (details are configured in a configuration file) and executes the scripts.
        
+
        1. application.properties in config folder
          Execute migrated script on Gauss DB: true/false, default value = false
          
+
          executesqlingauss=true
          
+
          true: It will execute the migrated script on gaussdb
          
+
        2. gaussdb.properties in config folder
          #Target Database configurations
          
+
          #gauss database user with all privileges  
+ gaussdb-user=  
+ gaussdb-port=  
+ #Database name for GaussDBA  
+ gaussdb-name=  
+ #gaussdb ip  
+ gaussdb-ip=
          
+
          Dependency on the gsql client:
          
+
          1. gsql (GaussDB(DWS)) is required for executing scripts on GaussDB(DWS). Therefore, to ensure the smooth running of DSC, DSC is required to run on a node installed with a GaussDB(DWS) instance or client (gsql), and the user that performs verification must have the permission for executing commands using gsql.
          2. Since the Gauss DB Instance/Client can be installed on a Linux OS only, this can be used to verify functionality only on a Linux environment.
          3. To execute the gsql command on a remote GaussDB instance, it is advised to add the client system IP/hostname in the following configuration file of Gauss DB instance.
            /home/gsmig/database/coordinator
+---pg_hba.conf
            
+
          
+
        
+
        Response
        
+
        GaussDB(DWS)
        
+
        ********************** Verification Started ****************************** 
+Sql script execution on Gauss DB start time : Wed Jan 22 17:27:07 CST 2020 
+Sql script execution on Gauss DB end time : Wed Jan 22 17:27:44 CST 2020 
+ 
+Summary of Verification : 
+================================================================================================================================== 
+Statement                | Total               | Passed              | Failed              | Success Rate(%) 
+----------------------------------------------------------------------------------------------------------------------------------- 
+COMMENT                  | 15                  | 15                  | 0                   | 100 
+CREATE VIEW              | 4                   | 3                   | 1                   | 75 
+CREATE INDEX             | 4                   | 3                   | 1                   | 75 
+CREATE TABLE             | 6                   | 6                   | 0                   | 100 
+ALTER TABLE              | 3                   | 3                   | 0                   | 100 
+--------------------------------------------------------------------------------------------------------------------------------- 
+Total                    | 32                  | 30                  | 2                   | 93 
+ 
+Gauss Execution Log file : /home/gsmig/18Jan/DSC/DSC/log/gaussexecutionlog.log 
+Gauss Execution Error Log file : /home/gsmig/18Jan/DSC/DSC/log/gaussexecutionerror.log 
+Verification finished in 38 seconds 
+ 
+********************** Verification Completed ****************************
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Database Schema Conversion
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0030.html b/docs/dws/tool/dws_16_0030.html
new file mode 100644
index 00000000..cf7dd1d5
--- /dev/null
+++ b/docs/dws/tool/dws_16_0030.html
@@ -0,0 +1,24 @@
+
+
+
        VERSION
        
+
        Functionality
        The version command is used to display the version number of the DSC.
        
+
        
+
        Syntax
        Linux:
        
+
        ./runDSC.sh --version 
        
+
        Windows:
        
+
        runDSC.bat --version
        
+
        
+
        How to Use
        Linux:
        
+
        ./runDSC.sh --version
        
+
        Windows:
        
+
        runDSC.bat --version
        
+
        
+
        System Response
        Version: DSC (Gauss Tools v2.0.0)
        
+
        
+
        
+
        
+
        
+
        Parent topic: CLI Reference
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0031.html b/docs/dws/tool/dws_16_0031.html
new file mode 100644
index 00000000..85d8d09e
--- /dev/null
+++ b/docs/dws/tool/dws_16_0031.html
@@ -0,0 +1,137 @@
+
+
+
        HELP
        
+
        Functionality
        The help command is used to provide the help information for the commands supported by DSC.
        
+
        
+
        Syntax
        Linux:
        
+
        ./runDSC.sh --help 
        
+
        Windows:
        
+
        runDSC.bat --help 
        
+
        
+
        Examples
        Linux:
        
+
        ./runDSC.sh --help 
        
+
        Windows:
        
+
        runDSC.bat --help 
        
+
        
+
        System Response
        Linux:
        
+
        ./runDSC.sh --help 
+To migrate teradata/oracle/netezza/mysql/db2 database scripts to DWS
+runDSC.sh -S <source-database> [-T <target-database>] -I <input-script-path> -O <output-script-path> [-M <conversion-type>]  [-A <application-lang>]  [-L <log-path>]  [-VN <version-number>]
+
+
+    -S | --source-db
+    The source database, which can be either Teradata or Oracle or Netezza or MySql or DB2.
+
+
+    -T | --target-db
+    The target database, which can be either GaussDBT or GaussDBA.
+
+
+    -I | --input-folder
+    The input/source folder that contains the Teradata/Oracle/Netezza/MySql/DB2 scripts to be migrated.
+
+
+    -O | --output-folder
+    The output/target folder where the migrated scripts are placed.
+
+
+    -M | --conversion-type
+    The conversion type, which can be either Bulk or BLogic.
+
+
+    -A | --application-lang
+    The application language type, which can be either SQL or Perl.
+
+
+    -L | --log-folder
+    The log file path where the log files are created.
+
+
+    -VN | --version-number
+    The version number, which can be either V1R7 or V1R8_330.
+
+   " -P | --pre-execution-path%n" + " 
+    Path containig the dependent Objects scripts which needs to be executed before the verification step.%n" + "%n" +
+
+
+
+To display DSC version details
+runDSC.sh -V | --version
+
+
+To display DSC help details
+runDSC.sh -H | --help
+
+
+[Internal] To guess encoding for a file
+runDSC.sh guessencoding -F <filename>
+
+
+    -F | --file-name
+    The filename for which the encoding must be guessed.
+
+
+Refer the user manual for more details.
        
+
        Windows:
        
+
        runDSC.bat --help 
+To migrate teradata/oracle/netezza/mysql/db2 database scripts to DWS
+runDSC.bat -S <source-database> [-T <target-database>] -I <input-script-path> -O <output-script-path> [-M <conversion-type>]  [-A <application-lang>]  [-L <log-path>]  [-VN <version-number>]
+
+
+    -S | --source-db
+    The source database, which can be either Teradata or Oracle or Netezza or MySql or DB2.
+
+
+    -T | --target-db
+    The target database, which can be either GaussDBT or GaussDBA.
+
+
+    -I | --input-folder
+    The input/source folder that contains the Teradata/Oracle/Netezza/MySql/DB2 scripts to be migrated.
+
+
+    -O | --output-folder
+    The output/target folder where the migrated scripts are placed.
+
+
+    -M | --conversion-type
+    The conversion type, which can be either Bulk or BLogic.
+
+
+    -A | --application-lang
+    The application language type, which can be either SQL or Perl.
+
+
+    -L | --log-folder
+    The log file path where the log files are created.
+
+
+    -VN | --version-number
+    The version number, which can be either V1R7 or V1R8_330.
+
+
+To display DSC version details
+runDSC.sh -V | --version
+
+
+To display DSC help details
+runDSC.sh -H | --help
+
+
+[Internal] To guess encoding for a file
+runDSC.sh guessencoding -F <filename>
+
+
+    -F | --file-name
+    The filename for which the encoding must be guessed.
+
+
+Refer the user manual for more details.
        
+
        
+
        
+
        
+
        
+
        Parent topic: CLI Reference
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0032.html b/docs/dws/tool/dws_16_0032.html
new file mode 100644
index 00000000..7d92a845
--- /dev/null
+++ b/docs/dws/tool/dws_16_0032.html
@@ -0,0 +1,20 @@
+
+
+
        Log Reference
        
+
        
+
        
+
        
+
+
+
        
+
        Parent topic: Using DSC
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0033.html b/docs/dws/tool/dws_16_0033.html
new file mode 100644
index 00000000..2ab9d9a9
--- /dev/null
+++ b/docs/dws/tool/dws_16_0033.html
@@ -0,0 +1,75 @@
+
+
+
        SQL Migration Logs
        
+
        The SQL DSC (DSC.jar) supports the following types of logging:
        
+
        • Activity logging
        • Error logging
        • successRead
        • successWrite
        
+
         
        • If a user specifies a log path, then all the logs are saved in the specified log path.
        • If a user does not specify the logging path, then the tool creates the log folder in the TOOL_HOME path and saves all the logs in this log folder.
        • To control the disk space usage, the maximum size of a log file is 10 MB. You can have a maximum of 10 log files.
        • The tool does not log sensitive data such as queries.
        
+
        
+
        Activity Logging
        DSC saves all log and error information to DSC.log. This file is available in the log folder. The DSC.log file consists of details such as user who executed the migration and files that have been migrated along with the timestamp. The logging level for activity logging is INFO.
        
+
        The file structure of the DSC.log file is as follows:
        
+
        2020-01-22 09:35:10,769 INFO CLMigrationUtility:159 DSC is initiated by xxxxx
+2020-01-22 09:35:10,828 INFO CLMigrationUtility:456 Successfully changed permission of files in D:\Migration\Gauss_Tools_18_Migration\code\migration\config
+2020-01-22 09:35:10,832 INFO PropertyLoader:90 Successfully loaded Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\application.properties
+2020-01-22 09:35:10,833 INFO ApplicationPropertyLoader:42 Application properties have been loaded Successfully
+2020-01-22 09:35:10,917 INFO MigrationValidatorService:549 Files in output directory has been overwritten as configured by xxxxx
+2020-01-22 09:35:10,920 INFO PropertyLoader:90 Successfully loaded Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\features-oracle.properties
+2020-01-22 09:35:10,921 INFO FeatureLoader:41 Features have been loaded Successfully
+2020-01-22 09:35:10,926 INFO MigrationService:80 DSC process start time : Wed Jan 22 09:35:10 GMT+05:30 2020
+2020-01-22 09:35:10,933 INFO FileHandler:179  File is not supported. D:\Migration_Output\Source\ARRYTYPE.sql-
+2020-01-22 09:35:10,934 INFO FileHandler:179  File is not supported. D:\Migration_Output\Source\varray.sql-
+2020-01-22 09:35:12,816 INFO PropertyLoader:90 Successfully loaded Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\global-temp-tables.properties
+2020-01-22 09:35:12,830 INFO PropertyLoader:90 Successfully loaded Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\create-types-UDT.properties
+2020-01-22 09:35:12,834 INFO PropertyLoader:90 Successfully loaded Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\package-names-oracle.properties
+2020-01-22 09:35:12,849 INFO DBMigrationService:76 Number of Available Processors: 4
+2020-01-22 09:35:12,850 INFO DBMigrationService:78 Configured simultaneous processes in the Tool : 3
+2020-01-22 09:35:13,032 INFO MigrationProcessor:94 File name: D:\Migration_Output\Source\Input.sql is started
+2020-01-22 09:35:13,270 INFO FileHandler:606 guessencoding command output = Error: Unable to access jarfile D:\Migration\Gauss_Tools_18_Migration\code\migration\RE_migration\target\dsctool.jar , for file= D:\Migration_Output\Source\Input.sql
+2020-01-22 09:35:13,272 INFO FileHandler:625 couldn't get the encoding format, so using the default charset for D:\Migration_Output\Source\Input.sql
+2020-01-22 09:35:13,272 INFO FileHandler:310 File D:\Migration_Output\Source\Input.sql will be read with charset : UTF-8
+2020-01-22 09:35:13,390 INFO FileHandler:668 D:\Migration_Output\target\output\Input.sql - File already exists/Failed to create target file
+2020-01-22 09:35:13,562 INFO FileHandler:606 guessencoding command output = Error: Unable to access jarfile D:\Migration\Gauss_Tools_18_Migration\code\migration\RE_migration\target\dsctool.jar , for file= D:\Migration_Output\Source\Input.sql
+2020-01-22 09:35:13,563 INFO FileHandler:625 couldn't get the encoding format, so using the default charset for D:\Migration_Output\Source\Input.sql
+2020-01-22 09:35:13,563 INFO FileHandler:675 File D:\Migration_Output\Source\Input.sql will be written with charset : UTF-8
+2020-01-22 09:35:13,604 INFO MigrationProcessor:139 File name: D:\Migration_Output\Source\Input.sql is processed successfully
+2020-01-22 09:35:13,605 INFO MigrationService:147 Total number of files in Input folder : 3
+2020-01-22 09:35:13,605 INFO MigrationService:148 Total number of queries : 1
+22020-01-22 09:35:13,607 INFO PropertyLoader:164 Successfully updated Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\global-temp-tables.properties
+2020-01-22 09:35:13,630 INFO PropertyLoader:164 Successfully updated Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\create-types-UDT.properties
+2020-01-22 09:35:13,631 INFO PropertyLoader:164 Successfully updated Property file : D:\Migration\Gauss_Tools_18_Migration\code\migration\config\package-names-oracle.properties
+2020-01-22 09:35:13,632 INFO CLMigrationUtility:305 Log file : dsc.log and the file is present in the path : D:\Migration_Output\log
+2020-01-22 09:35:13,632 INFO CLMigrationUtility:312 DSC process end time : Wed Jan 22 09:35:13 GMT+05:30 2020
+2020-01-22 09:35:13,632 INFO CLMigrationUtility:217 Total process time : 2842 seconds
        
+
        
+
        Error Logging
        DSC logs only the errors that are encountered during the migration process to DSCError.log. This file is available in the log folder. The DSCError.log file consists of details such as date and time of the error and the details of the file (file name) along with the query position. The logging level for error logging is ERROR.
        
+
        The file structure of the DSCError.log file is as follows:
        
+
        2017-06-29 14:07:39,585 ERROR TeradataBulkHandler:172 Error occurred during processing of input in Bulk Migration. PreQueryValidation failed in not proper termination or exclude keyword. /home/testmigration/Documentation/Input/c005.sql for Query in position : 4
+2017-06-29 14:07:39,962 ERROR TeradataBulkHandler:172 Error occurred during processing of input in Bulk Migration. PreQueryValidation failed in not proper termination or exclude keyword. /home/testmigration/Documentation/Input/c013.sql for Query in position : 11
+2017-06-29 14:07:40,136 ERROR QueryConversionUtility:250 Query is not converted as it contains unsupported keyword: join select
+2017-06-29 14:07:40,136 ERROR TeradataBulkHandler:172 Error occurred during processing of input in Bulk Migration. PreQueryValidation failed in not proper termination or exclude keyword. /home/testmigration/Documentation/Input/sample.sql for Query in position : 1
+2017-06-29 14:07:40,136 ERROR TeradataBulkHandler:172 Error occurred during processing of input in Bulk Migration. PreQueryValidation failed in not proper termination or exclude keyword. /home/testmigration/Documentation/Input/sample.sql for Query in position : 3
        
+
        
+
        successRead
        After a file has been read by the DSC, the file is logged for tracking purposes. In certain scenarios, these logs let the user know the status of the execution of files. This file is available in the log folder. The log file consists of details such as date and time, and the details of the file name. The logging level for this log file is INFO.
        
+
        The file structure of the successRead.log file is as follows:
        
+
        2017-07-21 14:13:00,461 INFO readlogger:213 /home/testmigration/Documentation/is not in.sql is read successfully.
+2017-07-21 14:13:00,957 INFO readlogger:213 /home/testmigration/Documentation/date quotes.sql is read successfully.
+2017-07-21 14:13:01,509 INFO readlogger:213 /home/testmigration/Documentation/column alias replace.sql is read successfully.
+2017-07-21 14:13:02,034 INFO readlogger:213 /home/testmigration/Documentation/sampleRownum.sql is read successfully.
+2017-07-21 14:13:02,578 INFO readlogger:213 /home/testmigration/Documentation/samp.sql is read successfully.
+2017-07-21 14:13:03,145 INFO readlogger:213 /home/testmigration/Documentation/2.6BuildInputs/testWithNodataSamples.sql is read successfully.
        
+
        
+
        successWrite
        DSC reads a file, processes it, and writes the output to the disk. This is logged to the success write log file. In some scenarios, this log lets the user know which of the files are successfully processed. In case of a re-run, the user can skip these files and run the remaining files. This file is available in the log folder. The log file consists of details such as date and time, and the details of the file name. The logging level for this log file is INFO.
        
+
        The file structure of the successWrite.log file is as follows:
        
+
        2017-07-21 14:13:00,616 INFO writelogger:595 /home/testmigration/Documentation/is not in.sql has written successfully.
+2017-07-21 14:13:01,055 INFO writelogger:595 /home/testmigration/Documentation/date quotes.sql has written successfully.
+2017-07-21 14:13:01,569 INFO writelogger:595 /home/testmigration/Documentation/column alias replace.sql has written successfully.
+2017-07-21 14:13:02,055 INFO writelogger:595 /home/testmigration/Documentation/sampleRownum.sql has written successfully.
+2017-07-21 14:13:02,597 INFO writelogger:595 /home/testmigration/Documentation/samp.sql has written successfully.
+2017-07-21 14:13:03,178 INFO writelogger:595 /home/testmigration/Documentation/testWithNodataSamples.sql has written successfully.
        
+
        
+
        
+
        
+
        
+
        Parent topic: Log Reference
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0034.html b/docs/dws/tool/dws_16_0034.html
new file mode 100644
index 00000000..935d16bb
--- /dev/null
+++ b/docs/dws/tool/dws_16_0034.html
@@ -0,0 +1,42 @@
+
+
+
        Perl Migration Logs
        
+
        The DSC writes all log information to a single file, perlDSC.log.
        
+
         
        Since the DSC will execute the SQL to migrate the SQL scripts inside Perl files, the following SQL migration logs are also supported:
        
+
        • Activity Logging
        • Error Logging
        • successRead
        • successWrite
        
+
        
+
        Logging Levels
        The logging level for Perl Migration logs is configured using the logging-level parameter.
        
+
        
+
        Logging
        DSC saves all logs, warnings and error information to perlDSC.log. This file is available in the log folder. The log file consists of details such as user who executed the migration and files that have been migrated along with the timestamp.
        
+
        The structure of the perlDSC.log file is as follows:
        
+
        
+
        2018-07-08 13:35:10 INFO teradatacore.pm:1316 Extracting SQL contents from perl files started
+2018-07-08 13:35:10 INFO teradatacore.pm:1329 Extracting SQL contents from perl files completed
+2018-07-08 13:35:10 INFO teradatacore.pm:1331 Migrating SQL files
+2018-07-08 13:35:12 INFO teradatacore.pm:1348 Migrating SQL files completed
+2018-07-08 13:35:12 INFO teradatacore.pm:1349 Merging migrated SQL contents to perl files started
+2018-07-08 13:35:12 INFO teradatacore.pm:1362 Merging migrated SQL contents to perl files completed
+2018-07-08 13:35:12 INFO teradatacore.pm:1364 Perl file migration completed
+2018-07-08 13:35:32 INFO teradatacore.pm:1316 Extracting SQL contents from perl files started
+2018-07-08 13:35:58 ERROR teradatacore.pm:426 opendir ../../../../../perltest/ failed
+2018-07-08 13:36:17 INFO teradatacore.pm:1316 Extracting SQL contents from perl files started
+2018-07-08 13:38:21 INFO teradatacore.pm:1329 Extracting SQL contents from perl files completed
+2018-07-08 13:38:21 INFO teradatacore.pm:1331 Migrating SQL files
+2018-07-08 13:38:22 INFO teradatacore.pm:1348 Migrating SQL files completed
+2018-07-08 13:38:22 INFO teradatacore.pm:1349 Merging migrated SQL contents to perl files started
+2018-07-08 13:38:37 ERROR teradatacore.pm:1044 Directory ../../../../../perltest/ should have 700, but has   0 permission
+2018-07-08 13:38:53 ERROR teradatacore.pm:1241 Another migration process is running on same folder, re-execute after the process has completed
+2018-07-08 13:39:01 INFO teradatacore.pm:1316 Extracting SQL contents from perl files started
+2018-07-08 13:39:51 INFO teradatacore.pm:1329 Extracting SQL contents from perl files completed
+2018-07-08 13:39:51 INFO teradatacore.pm:1331 Migrating SQL files
+2018-07-08 13:39:53 INFO teradatacore.pm:1348 Migrating SQL files completed
+2018-07-08 13:39:54 INFO teradatacore.pm:1349 Merging migrated SQL contents to perl files started
+2018-07-08 13:39:55 INFO teradatacore.pm:1362 Merging migrated SQL contents to perl files completed
+2018-07-08 13:39:57 INFO teradatacore.pm:1364 Perl file migration completed
        
+
        
+
        
+
        
+
        Parent topic: Log Reference
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0035.html b/docs/dws/tool/dws_16_0035.html
new file mode 100644
index 00000000..e31653e7
--- /dev/null
+++ b/docs/dws/tool/dws_16_0035.html
@@ -0,0 +1,22 @@
+
+
+
        SQL Syntax Migration Reference
        
+
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0036.html b/docs/dws/tool/dws_16_0036.html
new file mode 100644
index 00000000..ce9e43b0
--- /dev/null
+++ b/docs/dws/tool/dws_16_0036.html
@@ -0,0 +1,33 @@
+
+
+
        Teradata Syntax Migration
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0038.html b/docs/dws/tool/dws_16_0038.html
new file mode 100644
index 00000000..916675d3
--- /dev/null
+++ b/docs/dws/tool/dws_16_0038.html
@@ -0,0 +1,429 @@
+
+
+
        Supported Keywords and Features
        
+
        Table 1 lists the Teradata keywords and features that can be migrated.
        
+
+
        
+
        
+
        
+
        Parent topic: Teradata Syntax Migration
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0039.html b/docs/dws/tool/dws_16_0039.html
new file mode 100644
index 00000000..b433ad45
--- /dev/null
+++ b/docs/dws/tool/dws_16_0039.html
@@ -0,0 +1,82 @@
+
+
+
        Constraints and Limitations
        
+
        The restrictions on using DSC to migrate data from TD are as follows:
        
+
        • DSC is used only for syntax migration and not for data migration.
        
+
        • If the SELECT clause of a subquery contains an aggregate function when the IN or NOT IN operator is converted to EXISTS or NOT EXISTS, errors may occur during script migration.
        
+
        Teradata
        • If a case statement containing FORMAT is not enclosed in parentheses, this statement will not be processed.
          Examples are as follows:
          1
          case when column1='0' then column1='value' end (FORMAT 'YYYYMMDD')as alias1
+
          
+
+
          
+
          
+
          In this example, case when column1= "0", column1= "value" end is not enclosed in parentheses and it will not be processed.
          
+
        
+
        
+
        • If SELECT * and QUALIFY clauses are both used in an input query, the migrated query returns an additional column for the QUALIFY clause.
          An example is as follows:
          
+
          Teradata query
          
+
          1
+2
+3
+4
          SELECT * FROM dwQErrDtl_mc.C03_CORP_TIME_DPSIT_ACCT
+WHERE 1 = 1
+AND Data_Dt = CAST( '20150801' AS DATE FORMAT 'YYYYMMDD' )
+QUALIFY ROW_NUMBER( ) OVER( PARTITION BY Agt_Num, Agt_Modif_Num ORDER BY NULL ) = 1;
+
          
+
+
          
+
          Query after migration
          
+
          1
+2
+3
+4
+5
+6
+7
          SELECT * FROM (
+SELECT *, ROW_NUMBER( ) OVER( PARTITION BY Agt_Num, Agt_Modif_Num ORDER BY NULL ) AS ROW_NUM1
+FROM dwQErrDtl_mc.C03_CORP_TIME_DPSIT_ACCT
+WHERE 1 = 1
+AND Data_Dt = CAST( '20150801' AS DATE )
+) Q1
+WHERE Q1.ROW_NUM1 = 1;
+
          
+
+
          
+
          In the migrated query, the ROW_NUMBER() OVER(PARTITION BY Agt_Num and Agt_Modif_Num ORDER BY NULL) AS ROW_NUM1 column is returned additionally.
          
+
        • Named references to a table in a query cannot be migrated from subqueries or functions.
          For example, if the input query contains a table named foo, DSC will not migrate any named references to the table from a subquery (foo.fooid) or when called from a function (getfoo(foo.fooid)).
          1
+2
+3
+4
+5
+6
          SELECT * FROM foo
+ WHERE foosubid IN (
+                     SELECT foosubid
+                       FROM getfoo(foo.fooid) z
+                      WHERE z.fooid = foo.fooid
+                      );
+
          
+
+
          
+
          
+
        • The database with the schema name should be changed to SET SESSION CURRENT_SCHEMA.
+
          
+
+
+
+
+
+
+
+
          TD Syntax
          
+
          Syntax After Migration
          
+
          DATABASE SCHTERA 
          
+
          SET SESSION CURRENT_SCHEMA TO SCHTERA
          
+
          
+
          
+
        • The input file contains the table-specific keyword MULTISET VOLATILE, but GaussDB T, GaussDB A, and GaussDB(DWS) do not support it. Therefore, the tool replaces it with the LOCAL TEMPORARY/UNLOGGED keyword during the migration process. Use the session_mode configuration parameter to set the default table type (SET/MULTISET) for CREATE TABLE.
        
+
        
+
        
+
        
+
        Parent topic: Teradata Syntax Migration
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0040.html b/docs/dws/tool/dws_16_0040.html
new file mode 100644
index 00000000..42594737
--- /dev/null
+++ b/docs/dws/tool/dws_16_0040.html
@@ -0,0 +1,172 @@
+
+
+
        Data Type
        
+
        
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Data Type
        
+
        Input
        
+
        Output
        
+
        Numeric
        
+
        BIGINT
        
+
        BIGINT
        
+
        BYTEINT
        
+
        SMALLINT
        
+
        DECIMAL [(n[,m])]
        
+
        DECIMAL [(n[,m])]
        
+
        DOUBLE PRECISION
        
+
        DOUBLE PRECISION
        
+
        FLOAT
        
+
        DOUBLE PRECISION
        
+
        INT / INTEGER
        
+
        INTEGER
        
+
        NUMBER / NUMERIC
        
+
        NUMERIC
        
+
        NUMBER(n[,m])
        
+
        NUMERIC (n[,m])
        
+
        REAL
        
+
        REAL
        
+
        SMALLINT
        
+
        SMALLINT
        
+
        Character
        
+
        CHAR[(n)] / CHARACTER [(n)]
        
+
        CHAR(n)
        
+
        CLOB
        
+
        CLOB
        
+
        LONG VARCHAR
        
+
        TEXT
        
+
        VARCHAR(n) / CHAR VARYING(n) / CHARACTER VARYING(n)
        
+
        VARCHAR(n)
        
+
        Date/Time
        
+
        DATE
        
+
        DATE
        
+
        TIME [(n)]
        
+
        TIME [(n)]
        
+
        TIME [(n)] WITH TIME ZONE
        
+
        TIME [(n)] WITH TIME ZONE
        
+
        TIMESTAMP [(n)]
        
+
        TIMESTAMP [(n)]
        
+
        TIMESTAMP [(n)] WITH TIME ZONE
        
+
        TIMESTAMP [(n)] WITH TIME ZONE
        
+
        Range
        
+
        PERIOD(DATE)
        
+
        daterange
        
+
        PERIOD(TIME [(n)])
        
+
        tsrange [(n)]
        
+
        PERIOD(TIME WITH TIME ZONE)
        
+
        tstzrange
        
+
        PERIOD(TIMESTAMP [(n)])
        
+
        tsrange [(n)]
        
+
        PERIOD(TIMESTAMP WITH TIME ZONE)
        
+
        tstzrange
        
+
        Binary
        
+
        BLOB[(n)]
        
+
        blob
        
+
        BYTE[(n)]
        
+
        bytea
        
+
        VARBYTE[(n)]
        
+
        bytea
        
+
        
+
        
+
        BYTEINT
        Input
        
+
        select cast(col as byteint) from tab;
        
+
        Output
        
+
        
+
        SELECT CAST( col AS SMALLINT ) FROM tab ;
        
+
        
+
        
+
        
+
        Parent topic: Teradata Syntax Migration
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0041.html b/docs/dws/tool/dws_16_0041.html
new file mode 100644
index 00000000..6ee09d98
--- /dev/null
+++ b/docs/dws/tool/dws_16_0041.html
@@ -0,0 +1,29 @@
+
+
+
        Functions and Operators
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0043.html b/docs/dws/tool/dws_16_0043.html
new file mode 100644
index 00000000..a0175a18
--- /dev/null
+++ b/docs/dws/tool/dws_16_0043.html
@@ -0,0 +1,343 @@
+
+
+
        Analytical Functions
        
+
        Analytical functions are collectively called ordered analytical functions in Teradata, and they provide powerful analytical abilities for data mining, analysis and business intelligence.
        
+
        Analytical Functions in ORDER BY
        Input: Analytic function in ORDER BY clause
        
+
        
+
        1
+2
+3
+4
        SELECT customer_id, customer_name, RANK(customer_id, customer_address DESC) 
+   FROM customer_t
+ WHERE  customer_state = 'CA'
+ ORDER BY RANK(customer_id, customer_address DESC);
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
        SELECT customer_id, customer_name, RANK() over(order by customer_id, customer_address DESC) 
+   FROM customer_t
+ WHERE  customer_state = 'CA'
+ ORDER BY RANK() over(order by customer_id DESC, customer_address DESC) ;
+
        
+
+
        
+
        Input: Analytic function in GROUP BY clause
        
+
        1
+2
+3
+4
+5
+6
+7
        SELECT customer_city, customer_state, postal_code
+     , rank(postal_code)
+     , rank() over(partition by customer_state order by postal_code)
+    , rank() over(order by postal_code)
+  FROM Customer_T 
+  GROUP BY customer_state
+  ORDER BY customer_state;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
+6
        SELECT customer_city, customer_state, postal_code
+     , rank() over(PARTITION BY customer_state ORDER BY postal_code DESC) 
+     , rank() over(partition by customer_state order by postal_code)
+     , rank() over(order by postal_code)
+  FROM Customer_T 
+  ORDER BY customer_state;
+
        
+
+
        
+
        Analytical Functions in PARTITION BY
        When the input script contains a numeric value in the PARTITION BY clause, the migrated script retains the numeric value as it is.
        
+
        
+
        Input: Analytic function in PARTITION BY clause (with numeric value)
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
        SELECT
+          Customer_id
+          ,customer_name
+          ,rank (
+          ) over( partition BY 1 ORDER BY Customer_id )
+          ,rank (customer_name)
+     FROM
+          Customer_t
+     GROUP BY
+          1
+;
+
        
+
+
        
+
        Output
        
+
        SELECT
+          Customer_id
+          ,customer_name
+          ,rank (
+          ) over( partition BY 1 ORDER BY Customer_id )
+          ,rank (
+          ) over( PARTITION BY Customer_id ORDER BY customer_name DESC )
+     FROM
+          Customer_t
+;
        
+
        Window Functions
        Window functions perform calculations across rows of the query result. DSC supports the following Teradata window functions:
        
+
         
        The DSC supports only single occurrence of window function in QUALIFY clause. Multiple window functions in a QUALIFY may result in invalid migration.
        
+
        
+
        
+
        CSUM
        The Cumulative Sum (CSUM) function provides a running or cumulative total for a column's numeric value. It is recommended that ALIAS be used in the QUALIFY statements.
        
+
        
+
        Input - CSUM with GROUP_ID
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        INSERT INTO GSIS_SUM.DW_DAT71 (
+   col1
+  ,PROD_GROUP
+)
+   SELECT 
+      CSUM(1, T1.col1)
+      ,T1.PROD_GROUP
+     FROM tab1  T1
+    WHERE T1.col1 = 'ABC'
+;
+
        
+
+
        
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
        INSERT
+     INTO
+          GSIS_SUM.DW_DAT71 (
+               col1
+               ,PROD_GROUP
+          ) SELECT
+                    SUM (1) over( ORDER BY T1.col1 ROWS UNBOUNDED PRECEDING )
+                    ,T1.PROD_GROUP
+               FROM
+                    tab1 T1
+               WHERE
+                    T1.col1 = 'ABC'
+;
+
        
+
+
        
+
        Input - CSUM with GROUP_ID
        1
+2
+3
+4
+5
        SELECT  top 10
+      CSUM(1, T1.Test_GROUP)
+      ,T1.col1
+  FROM  $[schema}.  T1
+ WHERE T1.Test_GROUP = 'Test_group' group by Test_group order by Test_Group;
+
        
+
+
        
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        SELECT
+       SUM (1) over( partition BY Test_group ORDER BY T1.Test_GROUP ROWS UNBOUNDED PRECEDING )
+       ,T1.col1
+  FROM
+       $[schema}. T1
+ WHERE
+       T1.Test_GROUP = 'Test_group'
+ ORDER BY
+       Test_Group LIMIT 10
+;
+
        
+
+
        
+
        Input - CSUM with GROUP BY + QUALIFY
        1
+2
+3
+4
        SELECT c1, c2, c3, CSUM(c4, c3) 
+  FROM tab1 
+QUALIFY ROW_NUMBER(c4) = 1  
+GROUP BY 1, 2;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
+6
+7
        SELECT c1, c2, c3, ColumnAlias1
+  FROM ( SELECT c1, c2, c3
+              , SUM (c4) OVER(PARTITION BY 1 ,2 ORDER BY c3 ROWS UNBOUNDED PRECEDING) AS ColumnAlias1
+              , ROW_NUMBER( ) OVER(PARTITION BY 1, 2 ORDER BY c4) AS ROW_NUM1
+           FROM tab1
+       ) Q1
+   WHERE Q1.ROW_NUM1 = 1;
+
        
+
+
        
+
        MDIFF
        The MDIFF function calculates the moving difference for a column based on the preset query width. The query width is the specified number of rows. It is recommended that ALIAS be used in the QUALIFY statements.
        
+
        
+
        Input: MDIFF with QUALIFY
        
+
        1
+2
+3
+4
+5
+6
        SELECT DT_A.Acct_ID, DT_A.Trade_Date, DT_A.Stat_PBU_ID
+      , CAST( MDIFF( Stat_PBU_ID_3, 1, DT_A.Trade_No ASC ) AS DECIMAL(20,0) ) AS MDIFF_Stat_PBU_ID
+   FROM Trade_His DT_A
+  WHERE Trade_Date >= CAST( '20170101' AS DATE FORMAT 'YYYYMMDD' ) 
+  GROUP BY DT_A.Acct_ID, DT_A.Trade_Date
+ QUALIFY MDIFF_Stat_PBU_ID <> 0 OR MDIFF_Stat_PBU_ID IS NULL;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
+6
+7
        SELECT Acct_ID, Trade_Date, Stat_PBU_ID, MDIFF_Stat_PBU_ID
+   FROM (SELECT DT_A.Acct_ID, DT_A.Trade_Date, DT_A.Stat_PBU_ID
+         , CAST( (Stat_PBU_ID_3 - (LAG(Stat_PBU_ID_3, 1, NULL) OVER (PARTITION BY DT_A.Acct_ID, DT_A.Trade_Date ORDER BY DT_A.Trade_No ASC)))  AS MDIFF_Stat_PBU_ID
+           FROM Trade_His DT_A
+          WHERE Trade_Date >= CAST( '20170101' AS DATE)
+                )
+ WHERE MDIFF_Stat_PBU_ID <> 0 OR MDIFF_Stat_PBU_ID IS NULL;
+
        
+
+
        
+
        RANK
        RANK(col1, col2...)
        
+
        
+
        Input: RANK with GROUP BY
        
+
        1
+2
+3
+4
        SELECT  c1, c2, c3, RANK(c4, c1 DESC, c3) AS Rank1 
+  FROM  tab1 
+ WHERE  ... 
+ GROUP BY c1;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
        SELECT c1, c2, c3, RANK() OVER (PARTITION BY c1 ORDER BY c4, c1 DESC ,c3) AS Rank1
+  FROM tab1
+ WHERE ...;
+
        
+
+
        
+
        ROW_NUMBER
        ROW_NUMBER(col1, col2...)
        
+
        
+
        Input: ROW NUMBER with GROUP BY + QUALIFY
        
+
        1
+2
+3
+4
        SELECT c1, c2, c3, ROW_NUMBER(c4, c3) 
+   FROM tab1 
+QUALIFY RANK(c4) = 1  
+  GROUP BY 1, 2;
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
        SELECT
+      c1
+     ,c2
+     ,c3
+     ,ColumnAlias1
+  FROM
+      (
+        SELECT
+                c1
+               ,c2
+               ,c3
+               ,ROW_NUMBER( ) over( PARTITION BY 1 ,2 ORDER BY c4 ,c3 ) AS ColumnAlias1
+               ,RANK (
+               ) over( PARTITION BY 1 ,2 ORDER BY c4 ) AS ROW_NUM1
+          FROM
+              tab1
+      ) Q1
+ WHERE
+      Q1.ROW_NUM1 = 1
+;
+
        
+
+
        
+
        COMPRESS (specified with *****)
        Input
        
+
        ORDCADBRN VARCHAR(6) CHARACTER SET LATIN CASESPECIFIC TITLE '    ' COMPRESS '******'
        
+
        Output
        
+
        
+
        ORDCADBRN VARCHAR( 6 ) /* CHARACTER SET LATIN*/ /* CASESPECIFIC*/ /*TITLE '    '*/ /* COMPRESS  '******' */
        
+
        
+
        
+
        
+
        Parent topic: Functions and Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0044.html b/docs/dws/tool/dws_16_0044.html
new file mode 100644
index 00000000..8eb225f1
--- /dev/null
+++ b/docs/dws/tool/dws_16_0044.html
@@ -0,0 +1,94 @@
+
+
+
        Math Functions
        
+
        **
        Input: **
        
+
        
+
        1
        expr1 ** expr2
+
        
+
+
        
+
        Output
        
+
        1
        expr1 ^ expr2
+
        
+
+
        
+
        MOD
        Input: MOD
        
+
        1
        expr1 MOD expr2
+
        
+
+
        
+
        Output
        
+
        1
         expr1 % expr2
+
        
+
+
        
+
        
+
        NULLIFZERO
        Use the tdMigrateNULLIFZERO configuration parameter to configure migration of NULLIFZERO.
        
+
        
+
        Input: NULLIFZERO
        1
+2
        SELECT NULLIFZERO(expr1) FROM tab1 
+WHERE ... ;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
        SELECT NULLIF(expr1, 0) FROM tab1 
+WHERE ... ;
+
        
+
+
        
+
        ZEROIFNULL
        Use the tdMigrateZEROIFNULL configuration parameter to configure migration of ZEROIFNULL.
        
+
        
+
        Input: ZEROIFNULL
        1
+2
        SELECT ZEROIFNULL(expr1) FROM tab1 
+WHERE ... ;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
        SELECT COALESCE(expr1, 0) FROM tab1 
+WHERE ... ;
+
        
+
+
        
+
        Declaring a Hexadecimal Character Literal Value
        Input
        
+
        SELECT 
+ (COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.ID),''))
+ ||'7E'xc||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Code),''))
+ ||'7E'xc||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Description),''))
+ ||'7E'xc||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Name),''))
+ ||'7E'xc||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Host_Product_Id),''))
+FROM DP_VTXEDW.VTX_D_RPT_0017_WMSE12_01_01   VTX_D_RPT_0017_WMSE12_01_01
+WHERE 1=1
+;
        
+
        Output
        
+
        
+
        SELECT 
+ (COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.ID),''))
+ ||E'\x7E'||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Code),''))
+ ||E'\x7E'||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Description),''))
+ ||E'\x7E'||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Name),''))
+ ||E'\x7E'||(COALESCE(TRIM(BOTH FROM VTX_D_RPT_0017_WMSE12_01_01.Host_Product_Id),''))
+FROM DP_VTXEDW.VTX_D_RPT_0017_WMSE12_01_01   VTX_D_RPT_0017_WMSE12_01_01
+WHERE 1=1
+;
        
+
        Declaring a Hexadecimal Binary Literal Value
        Input
        
+
        CREATE MULTISET TABLE bvalues (IDVal INTEGER, CodeVal BYTE(2));
+INSERT INTO bvalues VALUES (112193, '7879'XB) ;
+SELECT IDVal, CodeVal FROM bvalues WHERE CodeVal = '7879'XB ; 
        
+
        Output
        
+
        
+
        CREATE TABLE bvalues (IDVal INTEGER, CodeVal BYTEA);
+INSERT INTO bvalues VALUES (112193, BYTEA '\x7879') ;
+SELECT IDVal, CodeVal FROM bvalues WHERE CodeVal = BYTEA '\x7879' ; 
        
+
        
+
        
+
        
+
        Parent topic: Functions and Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0045.html b/docs/dws/tool/dws_16_0045.html
new file mode 100644
index 00000000..7f38c06a
--- /dev/null
+++ b/docs/dws/tool/dws_16_0045.html
@@ -0,0 +1,105 @@
+
+
+
        String Functions
        
+
        CHAR Function
        Input: CHAR
        
+
        
+
        1
        CHAR( expression1 )
+
        
+
+
        
+
        Output
        
+
        1
        LENGTH( expression1 )
+
        
+
+
        
+
        CHARACTERS
        Input: CHARACTERS
        
+
        
+
        1
        CHARACTERS( expression1 )
+
        
+
+
        
+
        Output
        
+
        1
        LENGTH( expression1 )
+
        
+
+
        
+
        INDEX
        Input: INDEX
        
+
        1
+2
+3
        SELECT INDEX(expr1/string, substring)
+  FROM tab1 
+WHERE ... ;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
         SELECT INSTR(expr1/string, substring)
+  FROM tab1 
+WHERE ... ;
+
        
+
+
        
+
        
+
        STRREPLACE
        Input: STRREPLACE
        1
+2
+3
        SELECT STRREPLACE(c2, '.', '')
+  FROM tab1
+ WHERE ...;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
        SELECT REPLACE(c2, '.', '')
+  FROM tab1
+ WHERE ...;
+
        
+
+
        
+
        
+
        OREPLACE
        Input: OREPLACE
        1
+2
+3
        SELECT OREPLACE (c2, '.', '')
+  FROM tab1
+WHERE ... ;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
         SELECT REPLACE(c2, '.', '') 
+  FROM tab1
+WHERE ... ;
+
        
+
+
        
+
        
+
        STRTOK
        
+
        
+
+
+
+
+
+
+
+
        Input
        
+
        Output
        
+
        LENGTH(STRTOK(STRTOK(JOB_NAME_TADD,'-',4),'_',2))
        
+
        LENGTH(split_part(split_part(JOB_NAME_TADD,'-',4),'_',2))
        
+
        
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Functions and Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0046.html b/docs/dws/tool/dws_16_0046.html
new file mode 100644
index 00000000..b9ef0e74
--- /dev/null
+++ b/docs/dws/tool/dws_16_0046.html
@@ -0,0 +1,317 @@
+
+
+
        Date and Time Functions
        
+
        DATE
        Migration tools support the migration of Teradata DATE FORMAT in SELECT statements, using TO_CHAR to display the date in the source format. This conversion is not done if the date format is an expression (example: Start_Dt + 30) or if the WHERE statement contains an expression (Example: WHERE Start_Dt > End_Dt).
        
+
        For details, see: Type Casting to DATE without DATE Keyword
        
+
         
        • Migration is supported for SELECT statements with and without column alias.
        • Date formatting is not supported in the sub-levels and in inner queries. It is supported only at the outer query level.
        • For date formatting, if a table is created with SCHEMA name, subsequent SELECT statements must also include the schema name. In the following example, the table TEMP_TBL in the SELECT statement will not be migrated and the table retained as it was.
          1
+2
+3
+4
+5
+6
          CREATE TABLE ${SCH}.TEMP_TBL
+         (C1 INTEGER
+         ,C2 DATE FORMAT 'YYYY-MM-DD')
+PRIMARY INDEX(C1,C2);
+ 
+SELECT ${SCH}.TEMP_TBL.C2 FROM TEMP_TBL where ${SCH}.TEMP_TBL.C2 is not null;
+
          
+
+
          
+
        
+
        
+
        Input: DATE FORMAT
        
+
        1
+2
+3
+4
+5
+6
+7
+8
+9
        SELECT 
+          CASE 
+               WHEN SUBSTR( CAST( CAST( SUBSTR( '20180631' ,1 ,6 ) || '01' AS DATE FORMAT 'YYYYMMDD' ) + abc_day - 1 AS FORMAT 'YYYYMMDD' ) ,1 ,6 ) = SUBSTR( '20180631' ,1 ,6 ) 
+               THEN 1 
+               ELSE 0 
+          END 
+     FROM 
+          tab1 
+;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
+6
+7
+8
+9
        SELECT 
+          CASE 
+               WHEN SUBSTR( TO_CHAR( CAST( SUBSTR( '20180631' ,1 ,6 ) || '01' AS DATE ) + abc_day - 1 ,'YYYYMMDD' ) ,1 ,6 ) = SUBSTR( '20180631' ,1 ,6 ) 
+               THEN 1 
+               ELSE 0 
+          END 
+     FROM 
+          tab1 
+;
+
        
+
+
        
+
        
+
        DSC supports migration of the date value. If the input DATE is followed by "YYYY-MM-DD", then the date is not changed in the output. The following examples show conversion of DATE to CURRENT_DATE.
        
+
        Input: DATE
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        SELECT 
+        t1.c1 
+        ,t2.c2 
+  FROM 
+        $schema.tab1 t1 
+        ,$schema.tab2 t2 
+  WHERE 
+        t1.c3 ^ = t1.c3 
+        AND t2.c4 GT DATE 
+;
+
        
+
+
        
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        SELECT 
+        t1.c1 
+        ,t2.c2 
+  FROM 
+        "$schema".tab1 t1 
+        ,"$schema".tab2 t2 
+ WHERE 
+        t1.c3 <> t1.c3 
+        AND t2.c4 > CURRENT_DATE 
+;
+
        
+
+
        
+
        Input: DATE with "YYYY-MM-DD"
        
+
        1
+2
+3
+4
+5
        ALTER TABLE 
+     $abc . tab1 ADD ( 
+          col_date DATE DEFAULT DATE '2000-01-01' 
+     ) 
+;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
        ALTER TABLE 
+     "$abc" . tab1 ADD ( 
+          col_date DATE DEFAULT DATE '2000-01-01' 
+     ) 
+;
+
        
+
+
        
+
        Input: DATE subtraction
        
+
        1
+2
+3
+4
+5
+6
+7
        SELECT
+          CAST( T1.Buyback_Mature_Dt - CAST( '${gsTXDate}' AS DATE FORMAT 'YYYYMMDD' ) AS CHAR( 5 ) )
+     FROM
+          tab1 T1
+     WHERE
+          T1.col1 > 10
+;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
+6
+7
        SELECT
+          CAST( EXTRACT( 'DAY' FROM ( T1.Buyback_Mature_Dt - CAST( '${gsTXDate}' AS DATE ) ) ) AS CHAR( 5 ) )
+     FROM
+          tab1 T1
+     WHERE
+          T1.col1 > 10
+;
+
        
+
+
        
+
        ADD_MONTHS
        Input
        
+
        ADD_MONTHS(CAST(substr(T1.GRANT_DATE,1,8)||'01'AS DATE FORMAT 'YYYY-MM-DD'),1)-1
        
+
        Output
        
+
        
+
        mig_td_ext.ADD_MONTHS(CAST(substr(T1.GRANT_DATE,1,8)||'01'AS DATE FORMAT 'YYYY-MM-DD'),1)-1
        
+
        TIMESTAMP
        Input: TIMESTAMP
        
+
        select CAST('20190811'||' '||'01:00:00' 
+AS TIMESTAMP(0) 
+FORMAT 'YYYYMMDDBHH:MI:SS'
+) ;
        
+
        
+
        Output
        
+
        1
        SELECT TO_TIMESTAMP( '20190811' || ' ' || '01:00:00' ,'YYYYMMDD HH24:MI:SS' ) ;
+
        
+
+
        
+
        TIME FORMAT
        Input
        
+
        COALESCE(t3.Crt_Tm , CAST('00:00:00' AS TIME FORMAT 'HH:MI:SS'))
+COALESCE(LI07_F3EABCTLP.CTLREGTIM,CAST('${NULL_TIME}' AS TIME FORMAT 'HH:MI:sS'))
+trim(cast(cast(a.Ases_Orig_Tm as time format'hhmiss') as varchar(10)))
        
+
        
+
        Output
        
+
        CAST('00:00:00' AS TIME FORMAT 'HH:MI:SS')
+should be migrated as
+SELECT CAST(TO_TIMESTAMP('00:00:00', 'HH24:MI:SS') AS TIME)
+---
+CAST(abc AS TIME FORMAT 'HH:MI:sS')
+=>
+CAST(TO_TIMESTAMP(abc, 'HH24:MI:SS') AS TIME)
+---
+CAST(abc AS TIME FORMAT 'HH:MI:sS')
+=>
+CAST(TO_TIMESTAMP(abc, 'HH24:MI:SS') AS TIME)
        
+
        
+
        TIMESTAMP FORMAT
        Input
        
+
        select 
+   a.Org_Id as Brn_Org_Id          /*        */
+  ,a.Evt_Id as Vst_Srl_Nbr          /*       */
+  ,a.EAC_Id as EAC_Id          /*    */
+  ,cast(cast(cast(Prt_Tm as timestamp format 'YYYY-MM-DDBHH:MI:SS' ) as varchar(19) )as timestamp(0)) as Tsk_Start_Tm          /*        */
+from ${BRTL_VCOR}.BRTL_BC_SLF_TMN_RTL_PRT_JNL as a          /* BC_           */
+where   a.DW_Dat_Dt  = CAST('${v_Trx_Dt}' AS DATE FORMAT 'YYYY-MM-DD')  ;
        
+
        
+
        Output
        
+
        SELECT
+          a.Org_Id AS Brn_Org_Id /*        */
+          ,a.Evt_Id AS Vst_Srl_Nbr /*       */
+          ,a.EAC_Id AS EAC_Id /*    */
+          ,CAST( CAST( TO_TIMESTAMP( Prt_Tm ,'YYYY-MM-DD HH24:MI:SS' ) AS VARCHAR( 19 ) ) AS TIMESTAMP ( 0 ) ) AS Tsk_Start_Tm /*        */
+     FROM ${BRTL_VCOR}.BRTL_BC_SLF_TMN_RTL_PRT_JNL AS a /* BC_           */
+     WHERE
+          a.DW_Dat_Dt = CAST( '${v_Trx_Dt}' AS DATE ) ;
+
        
+
        TIMESTAMP(n) FORMAT
        Input
        
+
        select 
+   cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_Snsh_Dt          /*      */
+  ,coalesce(a.CRE_DAT,cast('0001-01-01 00:00:01' as timestamp(6) format 'yyyy-mm-ddbhh:mi:ssds(6)')) as Crt_Tm          /*      */
+  ,cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_ETL_Dt          /*      */
+  ,cast(current_date as date format 'yyyy-mm-dd') as DW_Upd_Dt          /*      */
+  ,current_time(0) as DW_Upd_Tm          /*      */
+  ,1 as DW_Job_Seq          /*      */
+from ${NDS_VIEW}.NLV65_MGM_GLDCUS_INF_NEW as a          /*    MGM    */
+;
+-----------
+cast('0001-01-01 00:00:00' as timestamp(6) format 'yyyy-mm-ddbhh:mi:ssds(6)')
+TO_TIMESTAMP('0001-01-01 00:00:00', 'yyyy-mm-dd HH24:MI:SS.US' )
+----------
+cast('0001-01-01 00:00:00.000000' as timestamp(6))
+cast('0001-01-01 00:00:00.000000' as timestamp(6))
+----------
+CAST('0001-01-01 00:00:00.000000' AS TIMESTAMP(6) FORMAT 'YYYY-MM-DDBHH:MI:SS.S(6)')
+TO_TIMESTAMP('0001-01-01 00:00:00.000000', 'yyyy-mm-dd HH24:MI:SS.US' )
+----------
+cast(LA02_USERLOG_M.LOGTIME as TIMESTAMP(6) FORMAT 'YYYY-MM-DD HH:MI:SS.S(0)' )
+TO_TIMESTAMP(LA02_USERLOG_M.LOGTIME, 'YYYY-MM-DD HH24:MI:SS' )
+----------
+cast('0001-01-01 00:00:00' as timestamp(3) format 'yyyy-mm-ddbhh:mi:ssds(3)')
+TO_TIMESTAMP('0001-01-01 00:00:00', 'yyyy-mm-dd HH24:MI:SS.MS' )
+-----------
+CAST( '0001-01-01 00:00:01.000000' AS TIMESTAMP ( 6 ) format 'yyyy-mm-ddbhh:mi:ssds(6)' )
+TO_TIMESTAMP('0001-01-01 00:00:01.000000', 'yyyy-mm-dd HH24:MI:SS.US' )
        
+
        
+
        Output
        
+
        cast('0001-01-01 00:00:00' as timestamp(6) format 'yyyy-mm-ddbhh:mi:ssds(6)')
+TO_TIMESTAMP('0001-01-01 00:00:00', 'yyyy-mm-dd HH24:MI:SS.US' )
+----------
+cast('0001-01-01 00:00:00.000000' as timestamp(6))
+cast('0001-01-01 00:00:00.000000' as timestamp(6))
+----------
+CAST('0001-01-01 00:00:00.000000' AS TIMESTAMP(6) FORMAT 'YYYY-MM-DDBHH:MI:SS.S(6)')
+TO_TIMESTAMP('0001-01-01 00:00:00.000000', 'yyyy-mm-dd HH24:MI:SS.US' )
+----------
+cast(LA02_USERLOG_M.LOGTIME as TIMESTAMP(6) FORMAT 'YYYY-MM-DD HH:MI:SS.S(0)' )
+TO_TIMESTAMP(LA02_USERLOG_M.LOGTIME, 'YYYY-MM-DD HH24:MI:SS' )
+----------
+cast('0001-01-01 00:00:00' as timestamp(3) format 'yyyy-mm-ddbhh:mi:ssds(3)')
+TO_TIMESTAMP('0001-01-01 00:00:00', 'yyyy-mm-dd HH24:MI:SS.MS' )
+-----------
+CAST( '0001-01-01 00:00:01.000000' AS TIMESTAMP ( 6 ) format 'yyyy-mm-ddbhh:mi:ssds(6)' )
+TO_TIMESTAMP('0001-01-01 00:00:01.000000', 'yyyy-mm-dd HH24:MI:SS.US' )
        
+
        trunc(<date>, 'MM') trunc(<date>, 'YY')
        Input
        
+
        select 
+   cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_Stat_Dt          /*  */
+  ,coalesce(d.IAC_Id,'') as IAC_Id          /*  */
+  ,coalesce(d.IAC_Mdf,'') as IAC_Mdf          /*  */
+  ,coalesce(c.Rtl_Wlth_Prod_Id,'') as Rtl_Wlth_Prod_Id          /*  */
+  ,coalesce(c.Ccy_Cd,'') as Ccy_Cd          /*  */
+  ,0 as Lot_Bal          /*  */
+  ,cast(sum(case when s2.Nvld_Dt > cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') then s2.Pos_Amt else 0 end) as decimal(18,2)) as NP_Occy_TMKV          /*          */
+  ,cast(
+        sum(s2.Pos_Amt *
+          ((case when s2.Nvld_Dt > cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') 
+                    then cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') else s2.Nvld_Dt - 1 end)
+          -
+           (case when s2.Eft_Dt > trunc(cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd'),'MM')
+              then s2.Eft_Dt else trunc(cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd'),'MM')
+           end)
+          + 1
+          )
+           ) 
+/
        
+
        
+
        Output
        
+
        date_trunc('month', cast('${v_Trx_Dt}' as date))
+date_trunc('year', cast('${v_Trx_Dt}' as date))
        
+
        NEXT
        Input: NEXT
        SELECT c1, c2 
+  FROM tab1 
+ WHERE NEXT(c3) = CAST('2004-01-04' AS DATE FORMAT 'YYYY-MM-DD');
        
+
        
+
        Output
        
+
        1
+2
+3
         SELECT c1, c2
+  FROM tab1
+ WHERE c3 + 1 = CAST('2004-01-04' AS DATE);
+
        
+
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Functions and Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0047.html b/docs/dws/tool/dws_16_0047.html
new file mode 100644
index 00000000..219464dd
--- /dev/null
+++ b/docs/dws/tool/dws_16_0047.html
@@ -0,0 +1,186 @@
+
+
+
        Comparison and List Operators
        
+
         
        The comparison operators LT, LE, GT, GE, EQ, and NE must not be used as TABLE alias or COLUMN alias.
        
+
        
+
        The following comparison and list operators are supported:
        
+
        ^= and GT
        Input: Comparison operations (^= and GT)
        1
+2
+3
+4
        SELECT t1.c1, t2.c2 
+  FROM tab1 t1, tab2 t2 
+ WHERE t1.c3 ^= t1.c3
+   AND t2.c4 GT 100;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
+4
        SELECT t1.c1, t2.c2 
+  FROM tab1 t1, tab2 t2 
+ WHERE t1.c3 <> t1.c3
+   AND t2.c4 > 100;
+
        
+
+
        
+
        
+
        EQ and NE
        Input: Comparison operations (EQ and NE)
        1
+2
+3
+4
        SELECT t1.c1, t2.c2 
+  FROM tab1 t1 INNER JOIN tab2 t2 
+    ON t1.c2 EQ t2.c2
+ WHERE t1.c6 NE 1000;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
         SELECT t1.c1, t2.c2 
+  FROM tab1 t1 INNER JOIN tab2 t2 
+    ON t1.c2 = t2.c2
+ WHERE
+        t1.c6 <> 1000;
+
        
+
+
        
+
        
+
        LE and GE
        Input: Comparison operations (LE and GE)
        1
+2
+3
+4
        SELECT t1.c1, t2.c2 
+  FROM tab1 t1, tab2 t2 
+ WHERE t1.c3 LE 200
+   AND t2.c4 GE 100;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
+4
         SELECT t1.c1, t2.c2 
+   FROM tab1 t1, tab2 t2 
+  WHERE t1.c3 <= 200
+    AND t2.c4 >= 100;
+
        
+
+
        
+
        
+
        NOT= and LT
        Input: Comparison operations (NOT= and LT)
        1
+2
+3
+4
        SELECT t1.c1, t2.c2 
+  FROM tab1 t1, tab2 t2 
+ WHERE t1.c3 NOT= t1.c3
+   AND t2.c4 LT 100;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
+4
        SELECT t1.c1, t2.c2 
+  FROM tab1 t1, tab2 t2 
+ WHERE t1.c3 <> t1.c3
+   AND t2.c4 < 100;
+
        
+
+
        
+
        
+
        IN and NOT IN
        For details, see IN and NOT IN Conversion.
        
+
        Input: IN and NOT IN
        1
+2
+3
         SELECT c1, c2
+   FROM tab1
+  WHERE c1 IN 'XY';
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
        SELECT c1, c2
+  FROM tab1
+ WHERE c1 = 'XY';
+
        
+
+
        
+
         
        GaussDB A and GaussDB(DWS) support the IN and NOT IN operators, except in special scenarios.
        
+
        
+
        
+
        IS NOT IN
        Input: IS NOT IN
        1
+2
+3
        SELECT c1, c2
+  FROM tab1
+ WHERE c1 IS NOT IN (subquery);
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
        SELECT c1, c2
+  FROM tab1
+ WHERE c1 NOT IN (subquery);
+
        
+
+
        
+
        
+
        LIKE ALL/NOT LIKE ALL
        Input: LIKE ALL / NOT LIKE ALL
        1
+2
+3
        SELECT c1, c2
+  FROM tab1
+ WHERE c3 NOT LIKE ALL ('%STR1%', '%STR2%', '%STR3%');
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
        SELECT c1, c2
+  FROM tab1
+ WHERE c3 NOT LIKE ALL (ARRAY[ '%STR1%', '%STR2%', '%STR3%' ]);
+
        
+
+
        
+
        
+
        LIKE ANY/NOT LIKE ANY
        Input: LIKE ANY / NOT LIKE ANY
        1
+2
+3
        SELECT c1, c2
+  FROM tab1
+ WHERE c3 LIKE ANY ('STR1%', 'STR2%', 'STR3%');
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
+3
        SELECT c1, c2
+  FROM tab1
+ WHERE c3 LIKE ANY (ARRAY[ 'STR1%', 'STR2%', 'STR3%' ]);
+
        
+
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Functions and Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0048.html b/docs/dws/tool/dws_16_0048.html
new file mode 100644
index 00000000..ea2e7f5a
--- /dev/null
+++ b/docs/dws/tool/dws_16_0048.html
@@ -0,0 +1,25 @@
+
+
+
        Table Operators
        
+
        The functions that can be called in the FROM clause of a query are from the table operator.
        
+
        Input: Table operator with RETURNS
        1
+2
        SELECT * 
+  FROM TABLE( sales_retrieve (9005) RETURNS ( store INTEGER, item CLOB, quantity BYTEINT) ) AS ret;
+
        
+
+
        
+
        
+
        Output
        
+
        1
+2
        SELECT *
+  FROM sales_retrieve(9005) AS ret (store, item, quantity);
+
        
+
+
        
+
        
+
        
+
        
+
        Parent topic: Functions and Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0049.html b/docs/dws/tool/dws_16_0049.html
new file mode 100644
index 00000000..3c019576
--- /dev/null
+++ b/docs/dws/tool/dws_16_0049.html
@@ -0,0 +1,24 @@
+
+
+
        Query Migration Operators
        
+
        
+
        
+
+
diff --git a/docs/dws/tool/dws_16_0051.html b/docs/dws/tool/dws_16_0051.html
new file mode 100644
index 00000000..7f8b4702
--- /dev/null
+++ b/docs/dws/tool/dws_16_0051.html
@@ -0,0 +1,242 @@
+
+
+
        QUALIFY
        
+
        In general, the QUALIFY clause is accompanied by analytic functions (window functions) such as CSUM(), MDIFF(), ROW_NUMBER() and RANK(). This is addressed using sub-query that contains the window functions specified in the QUALIFY clause. Migration tools support QUALIFY with MDIFF(), RANK() and ROW_NUMBER(). QUALIFY is a Teradata extension and not an ANSI standard syntax. It is executed after the WHERE and GROUP BY clauses. QUALIFY must start in new line.
        
+
         
        Migration tools support column name and/or expressions in the ORDER BY clause only if the column name and/or expression is explicitly included in the SELECT statement as well.
        
+
        
+
        Input: QUALIFY
        
+
        1
+2
+3
+4
+5
+6
        SELECT
+        CUSTOMER_ID
+       ,CUSTOMER_NAME
+  FROM
+       CUSTOMER_T QUALIFY row_number( ) Over( partition BY CUSTOMER_ID ORDER BY POSTAL_CODE DESC ) = 1
+;
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
        SELECT
+          CUSTOMER_ID
+          ,CUSTOMER_NAME
+     FROM
+          (
+               SELECT
+                         CUSTOMER_ID
+                         ,CUSTOMER_NAME
+                         ,row_number( ) Over( partition BY CUSTOMER_ID ORDER BY POSTAL_CODE DESC ) AS ROW_NUM1
+                    FROM
+                         CUSTOMER_T
+          ) Q1
+     WHERE
+          Q1.ROW_NUM1 = 1
+; 
+
        
+
+
        
+
        Input: QUALIFY with MDIFF and RANK
        
+
        1
+2
+3
+4
+5
+6
+7
+8
+9
        SELECT
+           material_name
+          ,unit_of_measure * standard_cost AS tot_cost
+     FROM
+          raw_material_t m LEFT JOIN supplies_t s
+               ON s.material_id = m.material_id 
+          QUALIFY rank ( ) over( ORDER BY tot_cost DESC ) IN '5'
+                  OR mdiff( tot_cost ,3 ,material_name ) IS NULL
+;
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
        SELECT
+          material_name
+          ,tot_cost
+     FROM
+          (
+               SELECT
+                         material_name
+                         ,unit_of_measure * standard_cost AS tot_cost
+                         ,rank ( ) over( ORDER BY unit_of_measure * standard_cost DESC ) AS ROW_NUM1
+                         ,unit_of_measure * standard_cost - (LAG( unit_of_measure * standard_cost ,3 ,NULL ) over( ORDER BY material_name )) AS ROW_NUM2
+                    FROM
+                         raw_material_t m LEFT JOIN supplies_t s
+                              ON s.material_id = m.material_id
+          ) Q1
+     WHERE
+          Q1.ROW_NUM1 = '5'
+          OR Q1.ROW_NUM2 IS NULL
+;
+
        
+
+
        
+
        Input: QUALIFY with ORDER BY having columns that do not exist in the SELECT list
        
+
        1
+2
+3
+4
+5
+6
        SELECT Postal_Code
+   FROM db_pvfc9_std.Customer_t t1
+   GROUP BY Customer_Name ,Postal_Code
+   QUALIFY ---comments
+ (  Rank ( CHAR(Customer_Address) DESC  )  ) = 1
+  ORDER BY t1.Customer_Name;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
+6
+7
+8
        SELECT Postal_Code FROM
+           ( SELECT Customer_Name, Postal_Code
+    , Rank () over( PARTITION BY Customer_Name, Postal_Code ORDER BY LENGTH(Customer_Address) DESC ) AS Rank_col
+               FROM db_pvfc9_std.Customer_t t1
+           ) Q1
+      WHERE /*comments*/
+    Q1.Rank_col = 1
+  ORDER BY Q1.Customer_Name;
+
        
+
+
        
+
        Input: QUALIFY with COLUMN ALIAS - the corresponding column expression should not be added again in SELECT list.
        
+
        1
+2
+3
+4
+5
        SELECT material_name, unit_of_measure * standard_cost as tot_cost,
+        RANK() over(order by tot_cost desc) vendor_cnt
+ FROM raw_material_t m left join supplies_t s
+ ON s.material_id = m.material_id
+ QUALIFY vendor_cnt < 5 or MDIFF(tot_cost, 3, material_name) IS NULL;
+
        
+
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
        SELECT material_name, tot_cost, vendor_cnt
+   FROM  ( SELECT material_name
+                       , unit_of_measure * standard_cost AS tot_cost
+                      , rank () over (ORDER BY tot_cost DESC) vendor_cnt
+                      , tot_cost - ( LAG(tot_cost ,3 ,NULL) over (ORDER BY material_name) ) AS anltfn
+               FROM raw_material_t m LEFT JOIN supplies_t s
+                  ON s.material_id = m.material_id
+           ) Q1
+      WHERE  Q1.vendor_cnt < 5 OR Q1.anltfn IS NULL
+ ;
+
        
+
+
        
+
        TITLE with QUALIFY
        Input
        
+
        
+
        REPLACE VIEW ${STG_VIEW}.LP06_BMCLIINFP${v_Table_Suffix_Inc}
+(
+  CLICLINBR
+, CLICHNNAM
+, CLICHNSHO
+, CLICLIMNE
+, CLIBNKCOD
+)
+AS
+LOCKING ${STG_DATA}.LP06_BMCLIINFP${v_Table_Suffix_Inc} FOR ACCESS
+SELECT
+  CLICLINBR (title '    VARCHAR(20)')
+, CLICHNNAM (title '        VARCHAR(200)')
+, CLICHNSHO (title '        VARCHAR(20)')
+, CLICLIMNE (title '      VARCHAR(10)')
+, CLIBNKCOD (title '       VARCHAR(11)')
+FROM
+  ${STG_DATA}.LP06_BMCLIINFP${v_Table_Suffix_Inc} s1
+QUALIFY
+    ROW_NUMBER() OVER(PARTITION BY  CLICLINBR ORDER BY CLICLINBR  ) = 1
+;
        
+
        Output
        
+
        CREATE OR REPLACE VIEW ${STG_VIEW}.LP06_BMCLIINFP${v_Table_Suffix_Inc}
+(
+  CLICLINBR
+, CLICHNNAM
+, CLICHNSHO
+, CLICLIMNE
+, CLIBNKCOD
+)
+AS
+/* LOCKING ${STG_DATA}.LP06_BMCLIINFP${v_Table_Suffix_Inc} FOR ACCESS */
+SELECT CLICLINBR
+        , CLICHNNAM
+       , CLICHNSHO
+       , CLICLIMNE
+      , CLIBNKCOD
+ FROM (
+           SELECT
+                          CLICLINBR /* (title '    VARCHAR(20)') */
+                        , CLICHNNAM /* (title '        VARCHAR(200)') */
+                       , CLICHNSHO /* (title '        VARCHAR(20)') */
+                       , CLICLIMNE /* (title '      VARCHAR(10)') */
+                       , CLIBNKCOD /* (title '       VARCHAR(11)') */
+                       , ROW_NUMBER() OVER(PARTITION BY  CLICLINBR ORDER BY CLICLINBR  ) AS ROWNUM1
+FROM
+  ${STG_DATA}.LP06_BMCLIINFP${v_Table_Suffix_Inc} s1 ) Q1
+WHERE Q1.ROWNUM1 = 1
+;
        
+
        
+
        
+
        
+
        Parent topic: Query Migration Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0052.html b/docs/dws/tool/dws_16_0052.html
new file mode 100644
index 00000000..fdcee52c
--- /dev/null
+++ b/docs/dws/tool/dws_16_0052.html
@@ -0,0 +1,103 @@
+
+
+
        ALIAS
        
+
        ALIAS is supported by all databases. In Teradata, an ALIAS can be referred in SELECT and WHERE clauses of the same statement where the alias is defined. Since ALIAS is not supported in SELECT and WHERE clauses in the target, it is replaced by the defined value/expression.
        
+
         
        The comparison operators LT, LE, GT, GE, EQ, and NE must not be used as TABLE alias or COLUMN alias.
        
+
        The tool supports column ALIAS. If the ALIAS is the same as the column name, the ALIAS is specified only for that column and not for other columns in the table. In the following example, the column name DATA_DT conflicts with the alias DATA_DT, which is not supported by the tool.
        
+
        1
        SELECT DATA_DT,DATA_INT AS DATA_DT FROM KK WHERE DATA_DT=DATE;
+
        
+
+
        
+
        
+
        Input: ALIAS
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
        SELECT
+          expression1 (
+               TITLE 'Expression 1'
+          ) AS alias1
+          ,CASE
+               WHEN alias1 + Cx >= z
+               THEN 1
+               ELSE 0
+          END AS alias2
+     FROM
+          tab1
+     WHERE
+          alias1 = y
+;
+
        
+
+
        
+
        Output: tdMigrateALIAS = FALSE
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        SELECT
+          expression1 AS alias1
+          ,CASE
+               WHEN alias1 + Cx >= z
+               THEN 1
+               ELSE 0
+          END AS alias2
+     FROM
+          tab1
+     WHERE
+          alias1 = y
+;
+
        
+
+
        
+
        Output: tdMigrateALIAS = TRUE
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
        SELECT
+          expression1 AS alias1
+          ,CASE
+               WHEN expression1 + Cx >= z
+               THEN 1
+               ELSE 0
+          END AS alias2
+     FROM
+          tab1
+     WHERE
+          expression1 = y
+;
+
        
+
+
        
+
        
+
        
+
        
+
        Parent topic: Query Migration Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0053.html b/docs/dws/tool/dws_16_0053.html
new file mode 100644
index 00000000..1dc6f930
--- /dev/null
+++ b/docs/dws/tool/dws_16_0053.html
@@ -0,0 +1,220 @@
+
+
+
        FORMAT and CAST
        
+
        In Teradata, the FORMAT keyword is used for formatting a column/expression. For example, FORMAT '9(n)' and 'z(n)' are addressed using LPAD with 0 and space (' ') respectively.
        
+
        Data typing is done using CAST or direct data type [like (expression1)(CHAR(n))]. This feature is addressed using CAST. For details, see Type Casting and Formatting.
        
+
        Input: FORMAT with CAST
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
        SELECT
+          CAST(TRIM( Agt_Num ) AS DECIMAL( 5 ,0 ) FORMAT '9(5)' )
+     FROM
+          C03_AGENT_BOND
+;
+
+SELECT
+          CAST(CAST( Agt_Num AS INT FORMAT 'Z(17)' ) AS CHAR( 5 ) )
+     FROM         
+          C03_AGENT_BOND
+;
+
+SELECT
+          CHAR(CAST( CAST( CND_VLU AS DECIMAL( 17 ,0 ) FORMAT 'Z(17)' ) AS VARCHAR( 17 ) ) )
+     FROM
+          C03_AGENT_BOND
+;
+
        
+
+
        
+
        
+
        Output
        
+
        SELECT
+          LPAD( CAST( TRIM( Agt_Num ) AS DECIMAL( 5 ,0 ) ) ,5 ,'0' ) AS Agt_Num
+     FROM
+          C03_AGENT_BOND
+;
+SELECT
+CAST(CAST( Agt_Num AS INT FORMAT 'Z(17)' ) AS CHAR( 5 ) )
+FROM
+C03_AGENT_BOND
+;
+
+SELECT
+          LENGTH( CAST( LPAD( CAST( CND_VLU AS DECIMAL( 17 ,0 ) ) ,17 ,' ' ) AS VARCHAR( 17 ) ) ) AS CND_VLU
+     FROM
+          C03_AGENT_BOND
+;
        
+
        Input - FORMAT 'Z(n)9'
        
+
        1
+2
+3
+4
+5
+6
        SELECT
+          standard_price (FORMAT 'Z(5)9') (CHAR( 6 ))
+          ,max_price (FORMAT 'ZZZZZ9') (CHAR( 6 ))
+     FROM
+          product_t
+; 
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
+6
        SELECT
+          CAST( TO_CHAR( standard_price ,'999990' ) AS CHAR( 6 ) ) AS standard_price
+          ,CAST( TO_CHAR( max_price ,'999990' ) AS CHAR( 6 ) ) AS max_price
+     FROM
+          product_t
+; 
+
        
+
+
        
+
        Input - FORMAT 'z(m)9.9(n)'
        
+
        1
+2
+3
+4
+5
        SELECT
+          standard_price (FORMAT 'Z(6)9.9(2)') (CHAR( 6 ))
+     FROM
+          product_t
+;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
        SELECT
+          CAST( TO_CHAR( standard_price ,'9999990.00' ) AS CHAR( 6 ) ) AS standard_price
+     FROM
+          product_t
+;
+
        
+
+
        
+
        Input - CAST AS INTEGER
        
+
        1
+2
+3
+4
+5
        SELECT
+          CAST( standard_price AS INTEGER )
+     FROM
+          product_t
+;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
        SELECT
+         (standard_price)
+     FROM
+          product_t
+;
+
        
+
+
        
+
        Input - CAST AS INTEGER FORMAT
        
+
        1
+2
+3
+4
+5
+6
+7
        SELECT
+          CAST( price11 AS INTEGER FORMAT 'Z(4)9' ) (
+               CHAR( 10 )
+          )
+     FROM
+          product_t
+;
+
        
+
+
        
+
        Output
        
+
        1
+2
+3
+4
+5
        SELECT
+          CAST( TO_CHAR(  ( price11 ) ,'99990' ) AS CHAR( 10 ) ) AS price11
+     FROM
+          product_t
+;
+
        
+
+
        
+
         
        The following Gauss function is added to convert to integer:
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
        CREATE OR REPLACE FUNCTION 
+/*  This function is used to support "CAST AS INTEGER" of Teradata.
+    It should be created in the "mig_td_ext" schema.
+*/
+     ( i_param                            TEXT )
+RETURN INTEGER
+AS
+  v_castasint    INTEGER;
+BEGIN
+
+   v_castasint := CASE WHEN i_param IS NULL 
+                                                THEN NULL         -- if NULL value is provided as input
+                                                                WHEN TRIM(i_param) IS NULL 
+                                                                                THEN 0                  -- if empty string with one or more spaces is provided 
+                                                                ELSE TRUNC(CAST(i_param AS NUMBER))            -- if any numeric value is provided
+                                END;
+
+RETURN v_castasint;
+END;
+
        
+
+
        
+
        
+
        
+
        
+
        
+
        Parent topic: Query Migration Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0054.html b/docs/dws/tool/dws_16_0054.html
new file mode 100644
index 00000000..ba553864
--- /dev/null
+++ b/docs/dws/tool/dws_16_0054.html
@@ -0,0 +1,138 @@
+
+
+
        Short Keys Migration
        
+
        Table 1 lists the abbreviation keywords supported by Teradata and the corresponding syntax in GaussDB A and GaussDB(DWS).
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 List of short keys
        Teradata Short Key
        
+
        GaussDB A and GaussDB(DWS) Syntax
        
+
        SEL
        
+
        SELECT
        
+
        INS
        
+
        INSERT
        
+
        UPD
        
+
        UPDATE
        
+
        DEL
        
+
        DELETE
        
+
        CT
        
+
        CREATE TABLE
        
+
        CV
        
+
        CREATE VIEW
        
+
        BT
        
+
        START TRANSACTION
        
+
        ET
        
+
        COMMIT
        
+
        
+
        
+
        Input - BT
        
+
        BT;
+--              
+delete from ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL 
+where DW_Job_Seq = ${v_Group_No};
+
+.if ERRORCODE <> 0 then .quit 12;
+
+--     
+insert into ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL 
+(
+   Cust_Id
+  ,Cust_UID
+  ,DW_Upd_Dt
+  ,DW_Upd_Tm
+  ,DW_Job_Seq
+  ,DW_Etl_Dt
+)
+select
+   a.Cust_Id
+  ,a.Cust_UID
+  ,current_date as Dw_Upd_Dt
+  ,current_time(0) as DW_Upd_Tm
+  ,cast(${v_Group_No} as byteint) as DW_Job_Seq
+  ,cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_Etl_Dt
+from ${BRTL_VCOR}.BRTL_CS_CUST_CID_UID_REL_S a
+where a.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd');
+
+.if ERRORCODE <> 0 then .quit 12;
+
+ET;cd ..
        
+
        Output
        
+
        BEGIN
+--    
+   BEGIN          
+      delete from ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL  
+       where DW_Job_Seq = ${v_Group_No};
+         lv_mig_errorcode = 0;
+   EXCEPTION
+      WHEN OTHERS THEN
+         lv_mig_errorcode = -1;
+   END;
+
+   IF lv_mig_errorcode <> 0 THEN
+        RAISE EXCEPTION '12';
+   END IF;
+
+--     
+   BEGIN
+        insert into ${BRTL_DCOR}.BRTL_CS_CUST_CID_UID_REL 
+        (
+          Cust_Id
+         ,Cust_UID
+         ,DW_Upd_Dt
+         ,DW_Upd_Tm
+         ,DW_Job_Seq
+         ,DW_Etl_Dt
+       )
+      select
+          a.Cust_Id
+         ,a.Cust_UID
+         ,current_date as Dw_Upd_Dt
+         ,current_time(0) as DW_Upd_Tm
+         ,cast(${v_Group_No} as byteint) as DW_Job_Seq
+         ,cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd') as DW_Etl_Dt
+       from ${BRTL_VCOR}.BRTL_CS_CUST_CID_UID_REL_S a
+     where a.DW_Snsh_Dt = cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd');
+   EXCEPTION
+      WHEN OTHERS THEN
+         lv_mig_errorcode = -1;
+   END;
+
+   IF lv_mig_errorcode <> 0 THEN
+        RAISE EXCEPTION '12';
+   END IF;
+
+END;
        
+
        
+
        
+
        
+
        Parent topic: Query Migration Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_16_0055.html b/docs/dws/tool/dws_16_0055.html
new file mode 100644
index 00000000..fbae38f0
--- /dev/null
+++ b/docs/dws/tool/dws_16_0055.html
@@ -0,0 +1,305 @@
+
+
+
        Object Names Starting with $
        
+
        This section describes the migration of object names starting with $.
        
+
        The migration behavior for object names starting with $ is explained in the following table. Use the tdMigrateDollar configuration parameter to configure the behavior.
        
+
        For details, see IN and NOT IN Conversion.
        
+
+
        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
        Table 1 Migration of object names starting with $
        tdMigrateDollar Setting
        
+
        Object Name
        
+
        Migrated To
        
+
        true
        
+
        $V_SQL
        
+
        Static object name starting with $
        
+
        "$V_SQL"
        
+
        true
        
+
        ${V_SQL}
        
+
        Dynamic object name starting with $
        
+
        ${V_SQL}
        
+
        No change: Dynamic object names not supported
        
+
        false
        
+
        $V_SQL
        
+
        Static object name starting with $
        
+
        $V_SQL
        
+
        No change: Configuration parameter is set to false.
        
+
        false
        
+
        ${V_SQL}
        
+
        Dynamic object name starting with $
        
+
        ${V_SQL}
        
+
        No change: Configuration parameter is set to false.
        
+
        
+
        
+
         
        Any variable starting with $ is considered as a Value. The tool will migrate this by adding ARRAY.
        
+
        
+
        Input - OBJECT STARTING WITH $
        1
        SELECT $C1 from p11 where $C1 NOT LIKE ANY ($sql1);
+
        
+
+
        
+
        
+
        Output (tdMigrateDollar to TRUE)
        
+
        1
+2
+3
+4
+5
+6
+7
+8
+9
        SELECT
+        "$C1"
+FROM
+        p11
+WHERE
+        "$C1" NOT LIKE ANY (
+        ARRAY[ "$sql1" ]
+        )
+;
+
        
+
+
        
+
        Output (tdMigrateDollar to FALSE)
        
+
        1
+2
+3
+4
+5
+6
+7
+8
+9
        SELECT
+        $C1
+FROM
+        p11
+WHERE
+        $C1 NOT LIKE ANY (
+        ARRAY[ $sql1 ]
+        )
+;
+
        
+
+
        
+
        Input - Value starting with $ in LIKEALL/LIKE ANY
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
        SELECT * FROM T1
+WHERE T1.Event_Dt>=ADD_MONTHS(CAST('${OUT_DATE}' AS DATE FORMAT 'YYYYMMDD')+1,(-1)*CAST(T7.Tm_Range_Month AS INTEGER)) 
+   AND T1.Event_Dt<=CAST('${OUT_DATE}' AS DATE FORMAT 'YYYYMMDD')
+   AND T1.Cntpty_Acct_Name NOT LIKE ALL ( SELECT Tx_Cntpty_Name_Key FROM TEMP_NAME )
+   AND T1.Cntpty_Acct_Name NOT LIKE ANY ( SELECT Tx_Cntpty_Name_Key FROM TEMP_NAME )
+   AND T1.Cntpty_Acct_Name LIKE ALL ( SELECT Tx_Cntpty_Name_Key FROM TEMP_NAME )
+   AND T1.Cntpty_Acct_Name LIKE ANY ( SELECT Tx_Cntpty_Name_Key FROM TEMP_NAME )
+   AND T1.Col1 NOT LIKE ANY ($sql1)
+   AND T1.Col1 NOT LIKE ALL ($sql1)
+   AND T1.Col1 LIKE ANY ($sql1)
+   AND T1.Col1 LIKE ALL ($sql1);
+
        
+
+
        
+
        
+
        Output
        
+
         1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34
+35
+36
+37
+38
+39
+40
+41
+42
+43
+44
        SELECT
+          *
+     FROM
+          T1
+     WHERE
+          T1.Event_Dt >= ADD_MONTHS (CAST( '${OUT_DATE}' AS DATE ) + 1 ,(- 1 ) * CAST( T7.Tm_Range_Month AS INTEGER ))
+          AND T1.Event_Dt <= CAST( '${OUT_DATE}' AS DATE )
+          AND T1.Cntpty_Acct_Name NOT LIKE ALL (
+               SELECT
+                         Tx_Cntpty_Name_Key
+                    FROM
+                         TEMP_NAME
+          )
+          AND T1.Cntpty_Acct_Name NOT LIKE ANY (
+               SELECT
+                         Tx_Cntpty_Name_Key
+                    FROM
+                         TEMP_NAME
+          )
+          AND T1.Cntpty_Acct_Name LIKE ALL (
+               SELECT
+                         Tx_Cntpty_Name_Key
+                    FROM
+                         TEMP_NAME
+          )
+          AND T1.Cntpty_Acct_Name LIKE ANY (
+               SELECT
+                         Tx_Cntpty_Name_Key
+                    FROM
+                         TEMP_NAME
+          )
+          AND T1.Col1 NOT LIKE ANY (
+               ARRAY[ "$sql1" ]
+          )
+          AND T1.Col1 NOT LIKE ALL (
+               ARRAY[ "$sql1" ]
+          )
+          AND T1.Col1 LIKE ANY (
+               ARRAY[ "$sql1" ]
+          )
+          AND T1.Col1 LIKE ALL (
+               ARRAY[ "$sql1" ]
+          )
+;
+
        
+
+
        
+
        QUALIFY, CASE, and ORDER BY
        Input
        
+
        select 
+   a.Cust_UID as Cust_UID          /*   UID */
+  ,a.Rtl_Usr_Id as Ini_CM          /*        */
+  ,a.Cntr_Aprv_Dt as Aprv_Pass_Tm          /*        */
+  ,a.Blg_Org_Id as CM_BRN_Nbr          /*         */
+  ,a.Mng_Chg_Typ_Cd  as MNG_CHG_TYP_CD          /*          */
+  ,case when a.Blg_Org_Id = b.BRN_Org_Id and a.Mng_Chg_Typ_Cd= 'PMD' and a.Pst_Id in ('PB0101','PB0104') then 'Y' ----        ,        
+       when a.Blg_Org_Id = b.BRN_Org_Id and a.Mng_Chg_Typ_Cd= 'DEVPMD' and a.Pst_Id ='PB0106'  then 'Y' ----            
+       when a.Blg_Org_Id = b.BRN_Org_Id and a.Mng_Chg_Typ_Cd= 'DMD' and a.Pst_Id in ('PB0201','PB0204') then 'Y' ----        ,        
+      when a.Blg_Org_Id = b.BRN_Org_Id and a.Mng_Chg_Typ_Cd= 'DEVDMD' and a.Pst_Id ='PB0109'  then 'Y' ----            ,
+       else ''
+end  as Pst_Flg          /*      */
+  ,a.Pst_Id as Pst_Id          /*      */
+  ,a.BBK_Org_Id  as BBK_Org_Id          /*        */
+from VT_CUID_MND_NMN_CHG_INF as a          /* VT_         */
+LEFT OUTER JOIN ${BRTL_VCOR}.BRTL_EM_USR_PST_REL_INF_S as b          /* EM_           */
+  on  a.Rtl_Usr_Id = b.Rtl_Usr_Id          
+  AND a.Blg_Org_Id  = b.BRN_Org_Id           
+  AND a.Pst_Id = b.Pst_Id          
+  AND b.Sys_Id = 'privatebanking'           
+  AND b.pst_sts IN ('1','0','-2') /*     1   -2   0  */          
+  AND b.DW_Snsh_Dt =  cast('${v_Trx_Dt}' as date format 'yyyy-mm-dd')          
+qualify   row_number() over(partition by a.Cust_UID,a.bbk_org_id order by 
+case when ( a.Mng_Chg_Typ_Cd= 'PMD'    and   a.Pst_Id in ('PB0101','PB0104')) or ( a.Mng_Chg_Typ_Cd= 'DEVPMD'    and   a.Pst_Id ='PB0106')   
+then 0 when  (a.Mng_Chg_Typ_Cd= 'DMD' and a.Pst_Id in ('PB0201','PB0204')) or    (a.Mng_Chg_Typ_Cd= 'DEVDMD' and a.Pst_Id ='PB0109 ')   then 0 else 1 end  asc )  = 1         
+;
        
+
        Output
        
+
        
+
         SELECT
+                     Cust_UID AS Cust_UID /*   UID */
+                     ,Ini_CM /*        */
+                     ,Aprv_Pass_Tm /*        */
+                     ,CM_BRN_Nbr /*         */
+                     ,MNG_CHG_TYP_CD /*          */
+                     ,Pst_Flg /*      */
+                     ,Pst_Id AS Pst_Id /*      */
+                     ,BBK_Org_Id AS BBK_Org_Id /*        */
+                FROM
+                     ( SELECT
+                          a.Cust_UID AS Cust_UID /*   UID */
+                          ,a.Rtl_Usr_Id AS Ini_CM /*        */
+                          ,a.Cntr_Aprv_Dt AS Aprv_Pass_Tm /*        */
+                          ,a.Blg_Org_Id AS CM_BRN_Nbr /*         */
+                          ,a.Mng_Chg_Typ_Cd AS MNG_CHG_TYP_CD /*          */
+                          ,CASE WHEN a.Blg_Org_Id = b.BRN_Org_Id AND a.Mng_Chg_Typ_Cd = 'PMD' AND a.Pst_Id IN ( 'PB0101' ,'PB0104' )
+                                    THEN 'Y' /*         , */
+                               WHEN a.Blg_Org_Id = b.BRN_Org_Id AND a.Mng_Chg_Typ_Cd = 'DEVPMD' AND a.Pst_Id = 'PB0106'
+                                    THEN 'Y' /*  */
+                               WHEN a.Blg_Org_Id = b.BRN_Org_Id AND a.Mng_Chg_Typ_Cd = 'DMD' AND a.Pst_Id IN ( 'PB0201' ,'PB0204' )
+                                    THEN 'Y' /*         , */
+                               WHEN a.Blg_Org_Id = b.BRN_Org_Id AND a.Mng_Chg_Typ_Cd = 'DEVDMD' AND a.Pst_Id = 'PB0109'
+                                    THEN 'Y' /*             , */
+                          ELSE
+                               ''
+                          END AS Pst_Flg /*      */
+                          ,a.Pst_Id AS Pst_Id /*      */
+                          ,a.BBK_Org_Id AS BBK_Org_Id /*        */
+                          ,row_number( ) over( partition BY a.Cust_UID
+                          ,a.bbk_org_id
+                     ORDER BY
+                          CASE WHEN( a.Mng_Chg_Typ_Cd = 'PMD' AND Q1.Pst_Id IN ( 'PB0101' ,'PB0104' ) ) OR( Q1.Mng_Chg_Typ_Cd = 'DEVPMD' AND a.Pst_Id = 'PB0106' )
+                                    THEN 0
+                               WHEN( a.Mng_Chg_Typ_Cd = 'DMD' AND Q1.Pst_Id IN ( 'PB0201' ,'PB0204' ) ) OR( Q1.Mng_Chg_Typ_Cd = 'DEVDMD' AND a.Pst_Id = 'PB0109 ' )
+                                    THEN 0
+                          ELSE
+                               1
+                          END ASC ) AS ROW_NUM1
+                     FROM
+                          VT_CUID_MND_NMN_CHG_INF AS a /* VT_         */
+                          LEFT OUTER JOIN BRTL_VCOR.BRTL_EM_USR_PST_REL_INF_S AS b /* EM_           */
+                               ON a.Rtl_Usr_Id = b.Rtl_Usr_Id
+                          AND a.Blg_Org_Id = b.BRN_Org_Id
+                          AND a.Pst_Id = b.Pst_Id
+                          AND b.Sys_Id = 'privatebanking'
+                          AND b.pst_sts IN ( '1' ,'0' ,'-2' ) /*     1   -2   0  */
+                          AND b.DW_Snsh_Dt = CAST( lv_mig_v_Trx_Dt AS DATE ) ) Q1
+                     WHERE
+                          Q1.ROW_NUM1 = 1 ;
        
+
        
+
        
+
        
+
        
+
        Parent topic: Query Migration Operators
        
+
        
+
        
+
diff --git a/docs/dws/tool/dws_mt_0091.html b/docs/dws/tool/dws_16_0056.html
similarity index 59%
rename from docs/dws/tool/dws_mt_0091.html
rename to docs/dws/tool/dws_16_0056.html
index a572864c..b0d5d57e 100644
--- a/docs/dws/tool/dws_mt_0091.html
+++ b/docs/dws/tool/dws_16_0056.html
@@ -1,13 +1,14 @@
-
+
 
 
        Query Optimization Operators
        
-
        This section describes the syntax for migrating Teradata query optimization operators. The migration syntax determines how the keywords and features are migrated.
        
-
        Use the inToExists parameter to configure the migration from IN orNOT IN to EXISTS or NOT EXISTS.
        
-
        This parameter defaults to FALSE. To enable the query optimization feature, this parameter must be set to TRUE.
        
-
        IN and NOT IN Conversion
        When being converted to GaussDB(DWS) SQL queries, Teradata queries containing the IN and NOT IN operators have been optimized, and IN and NOT IN have been converted to EXISTS and NOT EXISTS, respectively. The IN and NOT IN operators support single or multiple columns. DSC will migrate the IN or NOT IN statement only when it exists in the WHERE or ON clause. The following example shows the conversion from IN to EXISTS, which is also applicable to the conversion from  NOT IN to NOT EXISTS.
        
-
        Simple conversion from IN to EXISTS
        
-
        In the following example, the keyword IN is provided in the input file. During the migration, DSC replaces IN with EXISTS  to optimize query performance.
        
-