If you look at the output, you will see one schema defined with "sql_source" like this:
sql_source 706 2000 VARCHAR
and in the other location, like this:
sql_source 690 2147483647 text
Clearly, something is wrong somewhere.
You will need to open an incident with the GSC (global support center) and have them help you research the issue.
I will also note that you are using the SQLServer ODBC driver, and not an ODBC driver that is certified with TPT. Since we only certify with the ODBC drivers provided by Progress DataDirect, you should download an evaluation copy of that driver and try out the test. If you still get the same issue, then contact the GSC. If the problem goes away, there must be something about the SQLServer driver that was erroneous.
The GSC might only assist if you are using supported 3rd party products.
--SteveF
Hi
I’m using TPT Wizard and using TPT Load operator(Fastload) to generate scripts. It’s working fine for most of the tables but it’s throwing above error for couple of tables. At the same time If I use OLD Load and generate Multiload script, It works for all the tables.
TPT Load Script
When I execute this script It gives Following Error. I've also attached Log file below.
Detail log file
It shows one Warning: possible size violation for column: 'sql_source' -----as this column data type is 'text' in source table and it's assaigned Varchar(2000) as per the target table.
- This type of warning is present in other successful jobs log files as well.
- All the other Warnings(TMSM failed to initialize, Warning: Message received from ODBC driver: ... etc) are present in all the successful jobs log files as well, so please Ignore it.
I've tried to search above error but couldn't find any information.
I'll appreciate the help from forum members to solve this problem.
HS