Troubleshooting

Error occurred while formatting! Returning unformatted SQL: select count(* from table_temp;

Cause: This could be due to inconsistency in the number of opening and closing parentheses in the input file.

Solution: Ensure each opening parenthesis has a corresponding closing parenthesis.

ERROR QueryConversionUtility:249 Query is not converted as it contains unsupported keyword: LAST

Cause: Input query file contains an unsupported keyword.

Solution: Ensure no unsupported keywords are present in the scripts to be migrated.

For details, see Supported Keywords and Features.

Disk is almost full. Please clear the space and re-run the tool.

Cause: Insufficient space on the disk.

Solution: Free space from the disk and retry the operation.

Please enter valid input parameters, Kindly refer the user manual to execute.

Cause: The possible cause could be:

1. No valid parameters are specified.
2. The short keys are in lower case.

Solutions:

1. Provide all mandatory parameters when performing migration.
2. Ensure all short keys are in upper case.

For details, see Database Schema Conversion.

No SQL files found in input folder. Hence stopping migration.

Cause: No valid SQL files are present in the input folder during the migration process.

Solution: Ensure SQL files to be migrated are present in the input folder.

For details, see Migration Process.

Migration Application failed to start :

Currently we are not supporting this Database : <database-name>

Cause: Incorrect database name mentioned in the source database parameter.

Solution: Use only Teradata or Oracle as values to the source database parameter.

For details, see Database Schema Conversion.

Output folder is not set. Please enter an output folder and refer the user manual for syntax.

Cause: The output folder path is not specified.

Solution: Specify a valid path for the output folder parameter.

For details, see Database Schema Conversion.

ascii "****" does not map to charset

Cause: DSC cannot detect the encoding format of the file input, and the character set configured in the system does not match that of the file input. As a result, an alarm is reported.

Solution: Set encodingFormat to the actual encoding format and try again.

Example:

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 ************************