DSXchange

I fixed it by addjusting the time out setting on the job performance tab of the job properties.
Thanx for your time
Jim

I am having to run a query in an ODBC connection to get the data that I need, but i keep geting the error "ODBC time out expired" Where would I go to increase the time limit?
Jim

Try reformatting so that your statement reads oconv(iconv(Input.Update_Date, "D-ymd[4,2,2]"), "D4-YMD[4,2,2]") : Oconv("00:00:00","MTS") replacing the / with -. This seems to have fixed it... oconv(iconv(Input.Update_Date, "D-ymd[4,2,2]"), "D/M...

ogmios wrote:Which kind of database stage generates the error? There are huge differences between the different kind of stages.

Ogmios

Not sure what u are asking but I have three stages in the job a Sequencial a transformer and an ODBC. Im guessing that the error is originating at teh ODBC stage
Jim

I have a sequenctial file that has a date field in it. In my transform I use the following code oconv(iconv(Input.Update_Date, "D-ymd[4,2,2]"), "D/MDY[2,2,4]") this outputs correctly. I am tring ot load to a colum of the data type DateTime. I get the following error JOCDEVLoadToS...

A poster replying to a diff post just gave me the solution: 3) No , the usual advise is to preload your lookup data to a hash file and do the lookups from there. Since I don't like hash files that much, I usually move the "lookup table" to the database where the main query is executing in ...

I have a need to do some fairly simple SQL code in a transformer. This is the bit of code that im confused at: FROM [DM_JOC_AGGR_YR_MTH_TBL] f, [REF_JOC_VARIABLES_LU_TBL] v WHERE f.direction_id = v.direction_id and VDATE_MONTH_ID > v.Rolling_12_Cutoff and the bit that gets me si the > rolling_12_cut...

anupam wrote:Infact we have also upgraded to version 7 for testing, Just wanted to know the Performance Analysis of Version 7

I dont realy see much improvment in performance...I do see alot of improvment in usability of the tool. so in a sence that does help performance, its faster to create jobs now.
Jim

Unfortunatly no one has any idea whats going on here and I have run out of time. I am reverting to the old job with collectors and partitioners. We have just upgraded to vers 7 so I am hopeing that that will help keep this job running smothly. Thanx for all of you guys imput. Jim Jim, In my opinion...

Unfortunatly no one has any idea whats going on here and I have run out of time. I am reverting to the old job with collectors and partitioners. We have just upgraded to vers 7 so I am hopeing that that will help keep this job running smothly. Thanx for all of you guys imput.
Jim

Just to close this post...I successfully upgreaded to version 7 in about an hour and a half with no problems.
Jim

this is what is confusing me about your theries....... Jim Your issue has been open for weeks. In the meantime, I've answered about 100 posts and done some work myself. My theories are meant to guide you in what to look for in your design. Some other time you will have characters in your data that ...

You have an entry line in the file is what you are saying. You have an extra carriage return/line feed somewhere. Either the data has it embedded in it, or the concatenation is somehow introducing it. You can configure the sequential stage to throw away incomplete rows, or you can configure the seq...

NOOO! You probably have omit last newline checked in the sequential stage definition! Just uncheck it. If you have two files, with no last newline delimiter, and concatenate, then the first/last row where the files meet becomes one huge line. Omitting the last newline should be a rarely used option...

I rewrote my stage variable and it is doing what I want it to do. Thanx for clearing up what a job paramiter is capable of.
Jim