DSXchange

Version 7 is different from 7.5, 7.5 has three properties like Upsert, Load. If we specify the method as upsert and Auto-Generated SQL, It will produce query for Insert as well as Upsert. Alternative solution is make Custom SQL and write Insert queries alone.

Anyways good work kumar. Keep going.

Is any transformation logic built in at transformer stage? if not as suggested use Oracle Bulk Loader. Can we get entire job design information to analyze the problem.

If he is doing Insert alone, no need to have the update query.So i asked him to write user defined sql for insertion alone and not to have update statements.

No need to be sorry for that kumar. Alternative solutions are always welcome. We felt good that if we have that option and will be useful in one way or other.

You can create any number of files as you want. There is no limitation. Could you please tell us your requirement.

Thanks Punardeep, but here issue is different. I am able to execute same SP which runs for more than 30 minutes through Shell Script or from a Job Sequnce by Calling the scripts which calls SP but not directly from ODBC.

Could you please give us the Parameter details (Name, Type, Initial value if any) and the value of the parameter. Will be easy for us to analyze the issue.

I searched it but couldn't find what is required. Anyways thanks for your responses.

Thanks for that Kumar. We know that, Chulett and Myself thinking it will be good we have that option and you started with giving alternative solution which dragged into explaining all the scenario, We know that we can use shell script to call Job Sequence / Job.

Excatly. But it should be applicable to all. In some of the posts people who are pointing now did the same thing and it happened recently. Kumar you mentioned in some of the post saying Wait for OP or something like OP. People like us don't understand that and by seeing this they will think they can...

I didn't say that job/sequence needs to start from the point where it failed. It can start from the beginning again, no issues for me. Issue is with job warning setup.

It's leading to somewhere i guess. I wanted not to fail Job Seqeunce and wanted to restart only the failed job. Hope it is clear to you now.

Exactly. Not sure whether you understood correctly or not. The issue here not with job sequence. It's all with job. To make it clear. I have Jobs J 1, J 2, J 3...J 20 Job Sequence S 1 Now S 1 Calls J 1, J 2 sequentially and waits for completion of both J 1 and J 2. then J 3, J 4...J 20 called parall...

DSGuru solution is really a good one, I started writing my previous message as your reply to kumar_s Posted: Sun Mar 11, 2007 7:05 pm -------------------------------------------------------------------------------- Even if database is very fine tuned and has high band width, its not worth hitting th...