DSXchange

So what about ODBC? Is this a known issue? I mean is ODBC incompatible with BigInt in parallel jobs?

Is this software inbuilt or I have to use third party?
Does your reply imply that there indeed is a problem with ODBC and BigInt and further that I cant use it?

I am not sure whether it is a bug or I am doing something funny but this is what I am facing: I want to fetch a rows from DB2 table to flat file. There is a field in this table with datatype BigInt and length as 19. I created a parallel job whose structure is ODBC Stage --------------> Seq File I go...

I removed duplicates from the left table which had 216 records...Now the output of join is as expected i.e equal to number of records in left table. But it still is a puzzle that when there were 216 records why the output had 1896 records. Say even if there are duplicates you should get only those n...

I tried hash as well as round robin..Both are yielding same result. I have also set disable sort insertion as true. The join stage is perfroming the sort

I am using Join stage. there are two inputs to the join stage. Both inputs are ODBC stages. Both have a simple select statement with order by. All the primary keys have been added to join stage. There are no duplicates in the right table. In the left table there are duplicates but total number of ro...

Two things I left out to mention: The right table which has 5 million records has no duplicates for the key combination which I mentioned in the join. Secondly, I fired the same inner join query in db2 which returned exactly 216 records. So when we do a inner join on these tables via a SQL query you...

I am performing an inner join of two tables. The left table contains only 216 records while the right table contains 5 million records. However, I am getting output as 1896 records in the output. We should ideally get only 216 records because thats what is there in the left table. Why is this happen...

I had no other option, I had to get the job up and running. Recompiling was the only option. But in my query in above post, I have mentioned the error when the job was reset? Does that help? That you are wrong when you assert that nothing had changed. By recompiling you've destroyed all the evidence...

Anyone any opinion on this?

Nothing has changed in the system per se. In the previous successful run of the job there was a info log entry in the Director with the heading "Environment variable settings:" The body contained many paths and all other information. In the failed run also the entry was there but when I ex...

We have a server job which has been running for some time without any problems The jobs has a ODBC stage a hash file stage and after lookup the data is written to sequential file. Today the job failed with the following error Abnormal termination of stage Hash File Stage.IDENT1 detected I reset the ...

The whole project had to be exported and then reimported back. Luckily we lost no jobs in the process.

What caused this no one knows still?

Then you need to ascertain what changed yesterday. If not the job iteself, then what in the job's environment? Obviously, something did - the hard part can be figuring out what. Ah... so it's only advice worth putting effort into when it comes from Ray, eh? :? :lol: Hey Chulett, it is not like that...

We have a server job which runs daily. Normally it takes approx 7 minutes to complete. But the yesterdays run of this job is still in running state. No warnings whatsoever. We are not accessing any Databases. Only seq files and hash files. All the files required are in place and have the proper rig...