If Height Were A Power Law “… the median height would be two feet tall (a hundred men shorter than two feet, and a hundred taller)…” If Height Were A Power Law “ If the average height of two hundred men was five foot ten the most frequent (or modal) height would be held by dozens of men who were each only a foot tall …” New DB2 9.5 Monitoring Features Types of Information Statistics Counters High watermarks Histograms Activities Types of Presentation Table functions Event monitors Hope this info will help you to guide me to resolve the issues.īut when i do History load (without lookup).DB2 9.5 Monitoring Performance Tuning and Problem DeterminationĪgenda What I’m going to talk about Monitoring features new to DB2 9.5 Measuring against SLAs so that the system can be tuned to achieve them Using new monitoring features for problem determination What I’m not going to talk about Monitoring features that existed prior to DB2 9.5 Tuning individual queries, bufferpool hit ratios, etc. So in the incrmental load am using Lookup dataflow with Sql server tables which has Datetime2.Note: we tried all the possible datetime datatypes'Īnyway.we i map the columns in the lookuk.Ĭannot map the input column ,'START_TRAN_ID(DB2)' TO look up column'StartTranID(Sql server) 'because the data type do not match When i preview the query in OLEDB Source of DB2.The START_TRAN_ID has data in following format
We are pulling data from DB2 Database to our Staging Area(Staging database is SQL SERVER 2008-We have complete control over Sql server 2008)ġ) Am using OLE DB Source to query the DB2 Database.Ģ)Am doing incremntal load so i have to use lookup to compare StartTranID Column (We used Datetime,Datetime2.)of stage area with START_TRAN_ID Column of DB2 (which we dont know the schema) corresponding table columns to get the modified records We are pulling data from DB2 Database (We have permission only to SELECT Statement on DB2 database.So no way we can get the datatype or schema) I am not saying that this is the case in your situation, but it is something that I have experienced in the past. These connection managers seem to be really finicky and will blame the dates for most problems in the pipe. It is some other binary column above which the connection manager can not properly handle. NOTE: In my experience, most of the time that I encounter a truncation error for dates coming from DB2 it is not really an error with the date column. In either case, you have to check for early dates and correct them as DB2 allows timestamp dates all the way down to 00010101 whereas the earliest for SQL is 17530101. I have had luck with the Microsoft Ole DB Provider for DB2 (Download for Enterprise Edition Only) not having this problem And I am pretty sure that I have had similar luck with the IBM provided Ole DB provider. Depending on which connection manager you are using that MIGHT be the right solution for dealing with truncations.
0 kommentar(er)
