Multiload JOb Hangs at near completion of Records

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
reddy.cba
Premium Member
Premium Member
Posts: 27
Joined: Wed Jan 31, 2007 3:32 am
Location: sydney

Multiload JOb Hangs at near completion of Records

Post by reddy.cba »

HI All,
I am running a Multiload JOb in D/S Parallel edition,
Input File is a Huge dataset contaning more than 12 million records, and i am writing this to Teradata using Multiload option.

After nearly writing 12 million records the job does not do anything... It still hangs up..

can any one tell me why its happening, or do i need to add any parameters if the Input file is too big to load.

Thanks In Advance
Vamshi

Money has not created Man, Man has created Money.....SO dont die for Money...
hamzaqk
Participant
Posts: 249
Joined: Tue Apr 17, 2007 5:50 am
Location: islamabad

Post by hamzaqk »

not alot of information to come to any conclusions... have tried running the multiload script manually ?

mload < abc.mld ?

Does it run ok ?

It seems more like a network issue to me than an issue pertaining to ML. try running the job at a different time of the day.

Teradata Certified Master V2R5
reddy.cba
Premium Member
Premium Member
Posts: 27
Joined: Wed Jan 31, 2007 3:32 am
Location: sydney

Post by reddy.cba »

I havnt tried running it, But will try again...
Just in case i need to add any parameters if i am reading data frm a big dataset and writing into teradata, ?
Are there any parameters i need to add to run the job smoothly...

The same job was running fine when i ran with less than 100 records...
I assume nothing wrong with the job design its just the volume ....
may be i need to add some parameters to the job?

Thanks In Advance
Vamshi
reddy.cba
Premium Member
Premium Member
Posts: 27
Joined: Wed Jan 31, 2007 3:32 am
Location: sydney

Post by reddy.cba »

FOund the problem...
Prmiamry Index was created on wrong column and as a result... The job took ages to finish....

After changing the primary index column..it worked...
If any of you face any problem like this..check DDL for the Target DB and also check for the Indexing....

Many thanks to all
Vamshi
Post Reply