故障处理
本章介绍使用DSC时可能遇到的问题，并提供故障处理步骤。
下表列举了常见故障的问题现象、原因、解决方案。
问题现象 |
原因及解决方案 |
|---|---|
Error occurred while formatting! Returning unformatted SQL: SELECT count(*) FROM table_temp; |
原因：可能原因为输出文件中左右括号数量不一致。 解决方案：确保文件中所有左右括号匹配。 |
ERROR QueryConversionUtility:249 Query is not converted as it contains unsupported keyword: LAST |
原因：输入的查询文件包含一个不支持的关键词。 解决方案：确保要迁移的脚本中不含有不支持的关键词。 |
Disk is almost full. Please clear the space and re-run the tool. |
原因：磁盘空间不足。 解决方案：从磁盘中释放空间然后重试。 |
Please enter valid input parameters, Kindly refer the user manual to execute. |
原因：可能原因为：
解决方案：
|
No SQL files found in input folder. Hence stopping migration. |
原因：迁移过程中输入的文件夹中不存在有效SQL文件。 解决方案：确保要迁移的SQL文件存在输入的文件夹中。 有关详情，请参见迁移流程。 |
Migration Application failed to start : Currently we are not supporting this Database : <database-name> |
原因：源数据库参数中提到的数据库名称不正确。 解决方案：DSC仅支持Teradata或Oracle作为源数据库参数的值。 |
Output folder is not set. Please enter an output folder and refer the user manual for syntax. |
原因：未指定输出文件夹路径。 解决方案：指定输出文件夹参数的有效路径。 |
java.lang.OutOfMemoryError: GC overhead limit exceeded. |
原因：在迁移操作期间，如果内存使用超过设置的值，DSC将有该错误提示并退出。 解决方案：可通过更改application.properties配置文件中的initialJVMMemory和maxJVMMemory 的值，以分配更多内存。 |
ascii “****” does not map to charset |
原因：DSC无法检测输入文件的编码格式，且系统区域设置的字符集与输入文件的字符集不匹配。于是，系统上报告警。 解决方案：将encodingFormat参数设为实际编码值，并再次执行。 示例： testmigration@BLR1000026522:~/18.1_RETEST/DSC/scripts/teradata> perl sqlTDtoGS.pl -i ../../PERL -o ../../PERL_OUT/ -m /home/testmigration/18.1_FORMAT_RETEST/sep6thpackage/DSC Extracting SQL contents from perl files started ascii "\xFF" does not map to Unicode at core/teradatacore.pm line 1270. ascii "\xFE" does not map to Unicode at core/teradatacore.pm line 1270. ascii "\xFE" does not map to Unicode at core/teradatacore.pm line 1270. ascii "\xFF" does not map to Unicode at core/teradatacore.pm line 1270. Extracting SQL contents from perl files completed ********************** 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 ************************ |
错误码
错误码 |
错误信息 |
|---|---|
Teradata |
|
DSC_ERR_003_001 |
Query/statement is not supported since the Teradata view "dbc.indices" is supported only for the indextype P and Q. |
DSC_ERR_003_002 |
Error in Bteq processing. Something went wrong while processing the BTEQ commands. |
DSC_ERR_003_003 |
Query/statement is not supported in ddl DSC. Please check the same and refer user manual for the supported feature list. |
DSC_ERR_003_004 |
Unsupported format decimal format like ZZZ99Z, ZZZ.ZZ9. |
DSC_ERR_003_005 |
The tool does not support the "IN/NOT IN to EXISTS/NOT EXISTS conversion" for the query in which its outer query refers multiple tables and the column(s) specified with IN / NOT IN operator do not have table reference. |
DSC_ERR_003_006 |
The tool does not support the query in which its outer query refers multiple tables and the column(s) specified with IN / NOT IN operator do not have table reference. |
DSC_ERR_003_007 |
Primary Index without column is not supported. |
DSC_ERR_003_008 |
TeradataQuerySplitter config file contains list is not supported. |
DSC_ERR_003_009 |
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. |
DSC_ERR_003_010 |
Gauss does not have an equivalent syntax for CHARACTER SET & CASE SPECIFIC option in column-level. Please enable the config_param tdMigrateCharsetCase to comment the CHARACTER SET & CASE SPECIFIC option syntax in the statement. |
DSC_ERR_003_011 |
Gauss does not have equivalent syntax for LOCK option in CREATE VIEW and INSERT statement. You can rewrite this statement or set the configuration parameter tdMigrateLOCKOption to TRUE to comment the LOCK syntax in this statement. |
DSC_ERR_003_012 |
Invalid width (Number of rows) parameter in MDIFF function. |
DSC_ERR_003_013 |
First 2 parameters should be present in MDIFF function. |
DSC_ERR_003_014 |
Query/statement is not supported as ORDER BY clause is not present in TOP WITH TIES. Please check the same and refer user manual. |
DSC_ERR_003_015 |
Column mismatch for the TITLE conversion. |
DSC_ERR_003_016 |
Query/statement is not supported as same Table alias is addressed in both inner and outer query. Please check the same and refer user manual for the supported feature list. |
DSC_ERR_003_017 |
Sub query list does not have columns. |
DSC_ERR_003_018 |
Number of expressions specified in the outer query does not match with inner query. |
DSC_ERR_003_019 |
Error while loading the .RUN FILE from given location. |
DSC_ERR_003_020 |
Unable to delete the file, file not found. |
DSC_ERR_003_021 |
Unable to delete the file, failed with IOEXception. |
DSC_ERR_003_022 |
Please specify the value for enviroment_file_path parameter in features-teradata.properties. |
Application |
|
DSC_ERR_004_001 |
Application has timed out, exceeded the hours specified in the config file. Please configure the Timeout parameter in the application.properties to higher value. |
DSC_ERR_004_002 |
Error while loading the property files from config directory. |
DSC_ERR_004_003 |
Error while loading the property files from config directory, directory is not readable. |
DSC_ERR_004_004 |
Error while loading the property file. |
DSC_ERR_004_005 |
Unable to load the JSON file. |
DSC_ERR_004_006 |
DSC tool does not support this Conversion type provided. |
DSC_ERR_004_007 |
Error occurred while framing output replacement query. |
DSC_ERR_004_008 |
Invalid index value while parsing the script. |
DSC_ERR_004_009 |
Error in conversion process, unable to convert the script. |
DSC_ERR_004_010 |
No SQL files found in the input directory with the extension specified in the fileExtension property in application.properties. |
DSC_ERR_004_011 |
The query length parameter (MaxSqlLen) value is not valid. |
DSC_ERR_004_012 |
Since the input folder has write privileges to Group and/or Others, process is stopped due to security reason. |
DSC_ERR_004_013 |
Since the output directory has write privileges to Group and/or Others, process is stopped due to security reason. |
DSC_ERR_004_014 |
Disk is almost full. Please clear the space and re-run the tool. |
DSC_ERR_004_015 |
DSC has been cancelled as configured by the user. |
DSC_ERR_004_016 |
Error occurred while formatting the sql scripts. |
DSC_ERR_004_017 |
Invalid index specified for fetching the element from list while formatting the scripts |
DSC_ERR_004_018 |
Error occurred while converting from string to integer. |
DSC_ERR_004_019 |
Input File is modified while DSC is in progress. |
DSC_ERR_004_020 |
Process is null, unable to read encoding format. |
DSC_ERR_004_021 |
Target File does not have write permissions. |
DSC_ERR_004_022 |
The target directory does not have write privileges to Group and/or Others, process is stopped due to security reason. |
DSC_ERR_004_023 |
PL/SQL object contains incorrect DDL/Query. Please check the script for the query position specified in the log. |
DSC_ERR_004_024 |
PreQueryValidation failed due to bracket mismatch or invalid terminator. |
DSC_ERR_004_025 |
Conversion task name is not valid. |
DSC_ERR_004_026 |
Database entered by the user is not supported by the DSC tool. |
DSC_ERR_004_027 |
Gauss db password should not be empty. |
DSC_ERR_004_028 |
Gauss db password should not be empty. |
DSC_ERR_004_029 |
Target db entered in the Gaussdb.properties is not valid. |
DSC_ERR_004_030 |
User name entered in the Gaussdb.properties is empty. |
DSC_ERR_004_031 |
Port entered in the Gaussdb.properties is not valid. |
DSC_ERR_004_032 |
IP entered in the Gaussdb.properties is not valid. |
DSC_ERR_004_033 |
Database name entered in the Gaussdb.properties is empty. |
DSC_ERR_004_034 |
DSC Application failed to start. |
DSC_ERR_004_035 |
Since the Enviroment variable path has write privileges to Group and/or Others, process is stopped due to security reason. |
DSC_ERR_004_036 |
Error while loading Enviroment parameter File. |
DSC_ERR_004_037 |
Invalid input (empty/space/string value) for the parameter NoOfThreads in application.properties. Hence taking the default processes. |
DSC_ERR_004_038 |
Input for the parameter NoOfThreads in application.properties is less than 1. Hence taking the default processes. |
DSC_ERR_004_039 |
Error in processing the DDL query. |
DSC_ERR_004_040 |
Error in processing the PL/SQL query. |
DSC_ERR_004_041 |
Error in post processing the query. |
DSC_ERR_004_042 |
Invalid application timeout value, default to 4 hours. |
DSC_ERR_004_043 |
Error in writing the output file. |
DSC_ERR_004_044 |
Error in reading the input file. |
DSC_ERR_004_045 |
No valid files found in the input directory for migration. |
DSC_ERR_004_046 |
Query is not converted as it contains unsupported keyword. |
DSC_ERR_004_047 |
Error while reading the property. |
DSC_ERR_004_048 |
PreQueryValidation failed due to query exceeds maximum length (MaxSqlLen config parameter). |
DSC_ERR_004_049 |
Thread count entered in the Gaussdb.properties is not valid. |
Wrapper |
|
DSC_ERR_005_003 |
Reading file Failed with error: File not found Exception. |
DSC_ERR_005_004 |
Reading file Failed with error: IOException. |
DSC_ERR_005_005 |
Root privileged users are not allowed to execute the DSC tool. |
DSC_ERR_005_006 |
Error while getting the id of os user used to execute the DSC tool. |
DSC_ERR_005_007 |
Arguments specified is not valid, please check the user manual for the command line arguments. |
DSC_ERR_005_008 |
File name is not specified for reading the encoding type. |
DSC_ERR_005_009 |
Invalid argument specified for the encoding parameter. |
DSC_ERR_005_010 |
Source database is not set. Please enter a valid source db and refer the user manual for syntax. |
DSC_ERR_005_011 |
Commandline database specified for source to target is not supported by the DSC tool. |
DSC_ERR_005_012 |
Error in loading config file with IOException. |
DSC_ERR_005_013 |
Initial JVM memory is greater than maximum JVM memory. |
DSC_ERR_005_014 |
Invalid value specified for configValue. |
DSC_ERR_005_015 |
Invalid source database specified for source-db option. |
DSC_ERR_005_016 |
Invalid target database specified for target-db option. |
DSC_ERR_005_017 |
Invalid conversion type specified for dsc-type option. |
DSC_ERR_005_018 |
Invalid application language specified for application-lang option. |
DSC_ERR_005_019 |
Conversion-type should be DDL for application-lang type as perl. |
DSC_ERR_005_020 |
Source-db should be teradata for application-lang type as perl. |
DSC_ERR_005_021 |
Please use "-VN [V1R7 | V1R8_330]" or "--version-number [V1R7 | V1R8_330]" to specify the kernel version which can be either V1R7 or V1R8_330. |
DSC_ERR_005_022 |
Input directory does not exist. |
DSC_ERR_005_023 |
Getting path for input directory failed with IOException. |
DSC_ERR_005_024 |
Getting path for output directory failed with IOException. |
DSC_ERR_005_025 |
Setting file permission for output directory failed with IOException. |
DSC_ERR_005_026 |
Creating output directory failed. |
DSC_ERR_005_027 |
Setting file permissions for log directory/file failed with FileException. |
DSC_ERR_005_028 |
Error while connecting to GaussDB, Failed with error. |
DSC_ERR_005_029 |
Error occurred due to file permission while creating or executing the file. |
DSC_ERR_005_030 |
No arguments specified in the commandline. |
DSC_ERR_005_031 |
Error occurred in creating output directory. |
