| Author |
Message |
    
Minneapolis
Kurra Bewarse
Username: Minneapolis
Post Number: 943
Registered: 04-2005
Posted From: 156.98.20.1
| | Posted on Tuesday, January 02, 2007 - 3:40 pm: |    |
Nayakudu mama dhanitho thippalu inni anni kaadhu. Adhi inthavaraku avvaledhu. Oka vela kasepu dhani midha work cheddhamani start chesthe time antha waste avutundhi with out any results. Ivvala ayithe mottham time waste dhani midhane.
I am right now at a stage where i can read the complete timestamp from Sybase source with Informatica but not able to load into DB2 target mama. Sybase nundi read chesetappude milliseconds part ni seperate chesi string ga read chesthunna, dhani mundhala date part ni matram asusual date/time ga read chesthunna..taruvaatha dheenni string ga chesthunna..
ee date/time string ni milliseconds string ni concat chesthunna. I m making sure that this final string looks exactly like DB2 timestamp value of 26bytes but its a string. Debug chesi chusthunte final target varaku correct ga DB2 timestamp lagane all bytes inlcuding millisecond read cehsthundhi kaani final target loki nulls velthunnayi.
So thru informatica we cant send a field thats in string format to a timestamp field in DB2 ani telisindhi. Ippudu emi cheyyalo artham ayyi savadam ledhu. Neekemayina idea vundhaa like post SQL gani, leka data elago alaa laod chesi taruvatha aa field data type ni marchadam kaani.
Torture enti ante ma team lo Informatica professional services vadu vunnadu kaani vadini adigithe ticket open chestha, kaani i cant guarantee an answer soon ani antaadu.we r bad at supporting milliseoncds ani sollu chebuthunnadu.. |
Nayakudu
Vooriki Bewarse
Username: Nayakudu
Post Number: 5072
Registered: 05-2005
Posted From: 129.188.69.161
| | Posted on Tuesday, January 02, 2007 - 1:44 pm: | |
MPLS mama emayyindi work ayyindaa ledaa?? |
Infinity
Vooriki Bewarse
Username: Infinity
Post Number: 5282
Registered: 04-2005
Posted From: 69.115.252.248
| | Posted on Wednesday, December 27, 2006 - 6:31 pm: | |
cast the data type to timestamp (6) and extract milliseconds from the new field into whichever variable u want. |
2006
Kurra Bewarse
Username: 2006
Post Number: 817
Registered: 05-2006
Posted From: 136.182.158.137
| | Posted on Wednesday, December 27, 2006 - 5:38 pm: | |
Minneapolis mama,
ippudu source qualifier lo aa port data type ni change cheyyandi -- change it to varchar2(26) whatever you want it to... and subsequently define the data type of ths particular port as varchar2(23) through out the mapping... and finall join it to column in target table..
RAMOJI - the demolished man who defied the dictator GOSI - the to be first mayor of andhra capital after separation
|
Beer
Bewarse
Username: Beer
Post Number: 1894
Registered: 09-2006
Posted From: 208.204.155.241
| | Posted on Wednesday, December 27, 2006 - 4:20 pm: | |
2006 ee lokam lo neeku teliyani software languages, tools antoo vundavemo kada 
Beauty lies in the eye of the beer holder  |
Minneapolis
Kurra Bewarse
Username: Minneapolis
Post Number: 942
Registered: 04-2005
Posted From: 156.98.20.1
| | Posted on Wednesday, December 27, 2006 - 3:57 pm: | |
2006 mama convert function work avutundhi kaani ey field ni return cheyyalo source qualifier lo nundi bhayataki teliyadam eldhu.
select convert( char(26), knfd_nonfilr_inc_dat.run_dtm_test, 109)
from knfd_nonfilr_inc_dat
ilaa icchanu select stmt lo.
Ikkada 26 ani isthe 26characters testudhi plus 109 sybase style anta is bringing the date format properly with milli seconds. database midha work avutundhi.
for example na source lo 14 fields vunnayi. source qualifier lo kooda 14 vunchi aa run_dtm_test ane field length 19 vunchesi dhaanine return cheyyala?
Alaa chesthe mapping run avutundhi kaani asusual truncate chesi dobbutundhi. Kakapothe idhe SQL override ni databse midha test chesaanu work avutundhi. so ippudu source qualifier lo ee field ni ports tab lo edho manage cheyyali anukunta..can u tell how to go further from here as source qualifier lo oka kottha port add chesi with out having connection from source dhanni return chesthunte session fail avutundhi. |
2006
Kurra Bewarse
Username: 2006
Post Number: 802
Registered: 05-2006
Posted From: 129.188.69.161
| | Posted on Wednesday, December 27, 2006 - 1:07 pm: | |
i give the date field a name "dt_test"
mama source qualifier ni overwrite chesthey to convert dt_test to character, you can change the default data type of dt_test to varchar2(23) in source qualifier
ok
RAMOJI - the demolished man who defied the dictator GOSI - the to be first mayor of andhra capital after separation
|
Minneapolis
Kurra Bewarse
Username: Minneapolis
Post Number: 941
Registered: 04-2005
Posted From: 156.98.20.1
| | Posted on Wednesday, December 27, 2006 - 1:04 pm: | |
2006 mama let me try that as i m thinking it should work. SQL Override lo in the select stmt lo to_char(timestamp) ani isthanu sare. kaani this timestamp field whenever it is coming into the source qualifier its becoming 19bytes since source is a table and its defined as date/time there. so anyway let me try it. |
2006
Kurra Bewarse
Username: 2006
Post Number: 801
Registered: 05-2006
Posted From: 129.188.69.161
| | Posted on Wednesday, December 27, 2006 - 1:02 pm: | |
i think there is a function "convert" to convert the dates to char type in sybase
RAMOJI - the demolished man who defied the dictator GOSI - the to be first mayor of andhra capital after separation
|
2006
Kurra Bewarse
Username: 2006
Post Number: 800
Registered: 05-2006
Posted From: 136.182.158.153
| | Posted on Wednesday, December 27, 2006 - 12:56 pm: | |
mama, data type of a column in source qualifier should be same as defined in database...
what you can do is overwrite the source qualifier SQL and convert this date field to character using to_char() function available in sybase.. in such scenario, you can change the data type in source qualifier to varchar(23)
RAMOJI - the demolished man who defied the dictator GOSI - the to be first mayor of andhra capital after separation
|
2006
Kurra Bewarse
Username: 2006
Post Number: 799
Registered: 05-2006
Posted From: 129.188.69.161
| | Posted on Wednesday, December 27, 2006 - 12:52 pm: | |
mama try to read the date field as character
RAMOJI - the demolished man who defied the dictator GOSI - the to be first mayor of andhra capital after separation
|
Onlynbk
Bewarse ke Bewarse!
Username: Onlynbk
Post Number: 16096
Registered: 03-2004
Posted From: 221.134.28.127
| | Posted on Wednesday, December 27, 2006 - 12:52 pm: | |
idhe edho complex problem la undhi
maku antha idea ledhu
dont know about this timestamp
diniki emi transformations use chestaru
balayya ki anyayam cheisna vallu sala sala kage nune lo padi madi masi ayi potaru |
Minneapolis
Kurra Bewarse
Username: Minneapolis
Post Number: 940
Registered: 04-2005
Posted From: 156.98.20.1
| | Posted on Wednesday, December 27, 2006 - 12:50 pm: | |
Sure mama ikkade vuntaa..Throw me any ideas how to handle this part if u know by any chance.. |
2006
Kurra Bewarse
Username: 2006
Post Number: 798
Registered: 05-2006
Posted From: 136.182.158.153
| | Posted on Wednesday, December 27, 2006 - 12:45 pm: | |
hold on for 2 mins.. i will get back to you
RAMOJI - the demolished man who defied the dictator GOSI - the to be first mayor of andhra capital after separation
|
Minneapolis
Kurra Bewarse
Username: Minneapolis
Post Number: 939
Registered: 04-2005
Posted From: 156.98.20.1
| | Posted on Wednesday, December 27, 2006 - 12:43 pm: | |
Guys can anyone tell me how to capture the milliseconds part of the timestamp field when you process it through informatica. Though i have timestamp values for a field which is 23bytes in the source, Informatica is truncating them to seconds place and sending to the target as 19bytes.
My source is sybase which has 23bytes for the timestamp field that has milli seconds in the values. The target which is DB2 can hold the milli seconds too since the field length is 26bytes. Etocchi problem anthaa Informatica thone since its truncating the field length to 19bytes by default.
Naa kharma koddhi ee timestamp field midha source and target lo unique index define chesaaru and for some records its being unique only if u consider the milli seonds part of that timestamp field. I mean to say only if i consider the milliseconds part only the record is being unique. So when i tried to load its loading only some of them and others r being deleted since DB2 doesnt allow duplicates ( as there will duplicates if u consider only till seconds ).
My attempt: I tried to change the field type to varchar(23) in the source qualifier and its making the mapping as invalid.
Any one has any suggestions on this one.. |
