COMMIT PROBLEM IN JOB
Moderators: chulett, rschirm, roy
ORACLE 9Iprabu wrote:What is the db you use[try merge statement if you do], hanging issues cannot be answered without tracing your design
Design is
I have source and we do lookups on couple of table and look up the same Target table If the record is a alredy exists then We update the table and if new record we send this next Trnsform and Get the Seq# from ORACLE sequncer and insert the record into target table and HASHED file Commit on Both Update and Insert is 5000 Hope this will help you
ram1899
Thank youchulett wrote:If you are using two database stages for your Insert and Update links, switch the job to use a single stage for both links. This will keep all work in a single transaction and generally avoids all that pesky 'hanging'.
In this case what TRANSACTION SIZE is best option
ram1899
That's your call. We generally stick with 0 to get an all-or-nothing load. You need to decide what's appropriate for what you are doing and how you are handling restarts after failure. If you do use something other than 0, make sure it's a multiple of the Array Size.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote:That's your call. We generally stick with 0 to get an all-or-nothing load. You need to decide what's appropriate for what you are doing and how you are handling restarts after failure. If you do use something other than 0, make sure it's a multiple of the Array Size.
Thanks A TON Craig Appreciate I will do this change on the same Job and update you how it goes
Thanks again
ram1899
One more Quick Question what if the Links to Target table are coming from two diffrent Transform stages ???chulett wrote:That's your call. We generally stick with 0 to get an all-or-nothing load. You need to decide what's appropriate for what you are doing and how you are handling restarts after failure. If you do use something other than 0, make sure it's a multiple of the Array Size.
ram1899
Thank youchulett wrote:Doesn't matter. All you lose in that case is the ability to do what's called Transaction Grouping, nothing you need to worry about for this it seems.
This Jobs are designed by Some one and all left to diffrent project in same company and I have to Rock and roll on this Jobs from the day one day and night. No Error Handling No Restart capability. There is no time to think of how best solution I can give.
ram1899
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Ray is right. Its better to plan and rethink the design before implementing it. "Failing to plan is planning to fail". Especially if you are tweaking someone else's jobs. Make sure you have good amount of comments to avoid any confusion by future developers.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
This site is full of patterns and best practices. You can even check out Vincent's blogs. Kims has some tips on his home page. Search is the key. And if you have time, you can even prepare a white paper or build sample templates and share it with us ![Razz :P](./images/smilies/icon_razz.gif)
![Razz :P](./images/smilies/icon_razz.gif)
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.