Teradata connector jobs that are migrated from the Teradata Enterprise stage might fail with RDBMS code 3798:DK®
While migrating the Datastage Job from Enterprise stages to Connector stages, Using Information server connector migration tool. We might get the following error. Find the details of the problem along with solution for the same.DK®
Details Of Error :DK®
When you migrate a job with the Teradata Enterprise stage to use the
Teradata Connector stage, the connector migration tool sets the Teradata
connector Client character set property to UTF8 by default. The
connector migration tool sets the Client character set property to UTF8
because the Teradata Enterprise stage does not have a user-defined
client character set property. Instead, the stage sets the client
character set at runtime.DK®
Some jobs that were migrated might fail if the lengths of the character columns in the migrated job are not large enough to handle UTF8, which is a multibyte character set. Consider the scenario where the job with the Teradata Enterprise stage used the LATIN1252_0A character set with a Varchar column of length equal to 10. The migrated job uses UTF8 as the client character set and also contains a Varchar column with length equal to 10. An input row that was stored in 10 bytes in the LATIN1252_0A character set might require up to four times as many bytes in the UTF8 character set. Therefore, to store the same data, the Varchar column of the migrated job needs to be 40 bytes. If the lengths that are defined for the character columns on the Columns tab of the link are not large enough for this expansion, the job might fail with Teradata RDBMS code 3798: A column or character expression is larger than the max size.DK®
Error Code :DK®
Migrated Teradata enterprise jobs fail with Teradata RDBMS code 3798: A
column or character expression is larger than the max size.
Reason Of the Error :DK®
The Teradata Enterprise stage and Teradata Connector stage set the Client character set
property differently. The Teradata Enterprise stage sets the character
set based on the value of the NLSMap in the job and uses the mapping
that is defined in the tera_cs.txt file, which is located in the $APT_ORCHHOME/etc directory. The Teradata Connector stage uses the value that you set for the Client character set property.DK®
Solution Of the problem :DK®
In the Teradata Connector stage, set the Client character set
property to the same character set that was used in the Teradata
Enterprise stage job.DK®
The character set that was used by the Teradata
Enterprise stage is determined based on the NLSMap value of the migrated
job and the mapping that is defined in the tera_cs.txt file, which is located in the $APT_ORCHHOME/etc directory. You can use the connector migration tool to update a connector property for a batch of jobs.DK®
Alternatively, you can increase the lengths of
the character columns in the design schema of the job that has the
Teradata Connector stage.DK®
No comments:
Post a Comment