Archives of the TeradataForum
Message Posted: Sat, 01 Nov 2003 @ 15:26:31 GMT
Does anyone recognize a root cause here?: Windows server (Adv W2K) install of Multiload halts with unidentified character set error:
"UTY8400 Error determining default character set name, code = 224" Default settings aren't getting picked up; the only workaround that is effective to code -c ASCII on the Mload command line. BteqWIN works on the same W2K server.
I have duplicated this same behavior with an mload install to my desktop.
I suspect something is wrong with my Multiload installs. :-(
Teradata Multiload dependencies: CLIv2, Data Connector, Named Pipes.
Using TTU7.0 Multiload to Teradata R5 on MP-RAS.
Setting characters set for a Network attached client (priority per documentation):
1. Uses the character set specified in the utility program (This works when we specify -c ASCII in the mload command line).
2. Uses the default as defined in clispb.dat file (Adding a charset in this file hasn't made any difference and has never been required before).
3. As defined in DBC.HostsInfo (No entries in DBC.HostsInfo).
4. Default is ASCII. (Our Multiload isn't getting this default). MISC: Mload for Windows install doesn't update the path and/or otherwise resists install to non-C: drive.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|