Hi Guys,
i am facing very strange thing in version 8.1, when i import metadata using ODBC connection from SQL server 2008 i am unable to view data on a single field which is define as "LongNvarchar". i tried to change this field to other datatype but its complaining about "Datatype not supported"
see the error below:
##I IIS-DSEE-TFCN-00006 19:51:17(001) <main_program> conductor uname: -s=Windows_NT; -r=2; -v=5; -n=IBMPOC; -m=Pentium
##I IIS-DSEE-TOSH-00002 19:51:17(002) <main_program> orchgeneral: loaded
##I IIS-DSEE-TOSH-00002 19:51:17(003) <main_program> orchsort: loaded
##I IIS-DSEE-TOSH-00002 19:51:17(004) <main_program> orchstats: loaded
##W IIS-DSEE-TOSH-00049 19:51:18(000) <main_program> Parameter specified but not used in flow: DSProjectMapName
##I IIS-DSEE-TDOD-00080 19:51:18(001) <Barloworld_SQL> Process meta data not available in database
>##E IIS-DSEE-TDOD-00001 19:51:18(002) <main_program> Datatype Not Supported
>##E IIS-DSEE-TOPK-00007 19:51:18(007) <_PEEK_IDENT_> Input dataset does not have field: "LocationID".
>##E IIS-DSEE-TOPK-00007 19:51:18(008) <_PEEK_IDENT_> Input dataset does not have field: "ScenarioID".
>##E IIS-DSEE-TOPK-00007 19:51:18(009) <_PEEK_IDENT_> Input dataset does not have field: "CurrencyID".
>##E IIS-DSEE-TOPK-00007 19:51:18(010) <_PEEK_IDENT_> Input dataset does not have field: "LocationCode".
>##E IIS-DSEE-TOPK-00007 19:51:18(011) <_PEEK_IDENT_> Input dataset does not have field: "MaxForecastError".
>##E IIS-DSEE-TOPK-00007 19:51:18(012) <_PEEK_IDENT_> Input dataset does not have field: "RegionID".
>##E IIS-DSEE-TOPK-00007 19:51:18(013) <_PEEK_IDENT_> Input dataset does not have field: "LocationDescription".
>##E IIS-DSEE-TFSR-00019 19:51:18(015) <main_program> Could not check all operators because of previous error(s)
##W IIS-DSEE-TFIP-00093 19:51:18(016) <Barloworld_SQL> When checking operator: The modify operator has a binding for the non-existent output field "LocationID".
##W IIS-DSEE-TFIP-00093 19:51:18(017) <Barloworld_SQL> When checking operator: The modify operator has a binding for the non-existent output field "ScenarioID".
##W IIS-DSEE-TFIP-00093 19:51:18(018) <Barloworld_SQL> When checking operator: The modify operator has a binding for the non-existent output field "CurrencyID".
##W IIS-DSEE-TFIP-00093 19:51:18(019) <Barloworld_SQL> When checking operator: The modify operator has a binding for the non-existent output field "LocationCode".
##W IIS-DSEE-TFIP-00093 19:51:18(020) <Barloworld_SQL> When checking operator: The modify operator has a binding for the non-existent output field "MaxForecastError".
##W IIS-DSEE-TFIP-00093 19:51:18(021) <Barloworld_SQL> When checking operator: The modify operator has a binding for the non-existent output field "RegionID".
##W IIS-DSEE-TFIP-00093 19:51:18(022) <Barloworld_SQL> When checking operator: The modify operator has a binding for the non-existent output field "LocationDescription".
>##E IIS-DSEE-TCOS-00029 19:51:18(023) <main_program> Creation of a step finished with status = FAILED.
>
Datatype LongNvarchar not working
Moderators: chulett, rschirm, roy
Datatype LongNvarchar not working
-------------------------
https://www.ssa.co.za
https://www.ssa.co.za
Re: Datatype LongNvarchar not working
"LongNvarchar"
-------------------------
https://www.ssa.co.za
https://www.ssa.co.za
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
There is no data type LongNvarchar is available in sql server. :D
I believe it might be text/xml/varchar(max)/Binary data type.
while importing this field into DS it will convert into LongNvarchar. let it be as it is then load this metadata using odbc connector stage and change the array size =1 . iIt will resolve your problems
I believe it might be text/xml/varchar(max)/Binary data type.
while importing this field into DS it will convert into LongNvarchar. let it be as it is then load this metadata using odbc connector stage and change the array size =1 . iIt will resolve your problems