Error while running job

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
atulgoel
Participant
Posts: 84
Joined: Tue Feb 03, 2009 1:09 am
Location: Bangalore, India

Error while running job

Post by atulgoel »

Hi,

I am getting the below error while running the job. Upto yesterday, I was able to run the job, but today suddenly, I am getting the below error:


main_program: Internal Error: (d->nPartitions()== nPartitions_): datamgr/segment.C: 288
Traceback: [6] APT_FatalPath::pureAssertion(0xffffffff7ec8c491, 0xffffffff7ec8c4b1, 0x120, 0x3669, 0x1ea2b4, 0xf), at 0xffffffff7dd803fc
[7] APT_DMSegment::setPartitionDescriptor(0x1002b4ad0, 0xffffffff7fffa7d8, 0xe400, 0xffffffff7ec8c47f, 0xffffffff7edf4b40, 0xffffffff7edf4b40), at 0xffffffff7e55728c
[8] APT_DMDescriptor::setPartitionDescriptor(0xffffffff7fffa7d8, 0xffffffff7fffa9c0, 0x40000, 0x1, 0xffffffff7ee88a01, 0x0), at 0xffffffff7e521d78
[9] APT_DMFileDataSet::readDescriptor(0xffffffff7fffadf0, 0xffffffff7fffa7d8, 0x2, 0xffffffff7fffa9c0, 0xffffffff7fffa668, 0xffffffff7fffa630), at 0xffffffff7e54296c
[10] APT_DMFileDataSet::describe(0xffffffff7fffb0a4, 0x100748930, 0xffffffff7fffb0a8, 0x1, 0xffffffff7fffadf8, 0xffffffff7fffb120), at 0xffffffff7e53dd70
[11] APT_DataSetRep::setFileMode(0x10073a4b0, 0xffffffff7fffbd78, 0xffffffff7fffb0a8, 0xffffffff7fffb1e8, 0xffffffff7fffb218, 0x100748930), at 0xffffffff7e3c699c
[12] APT_DataSet::APT_DataSet(0x10070e890, 0xffffffff7fffbd78, 0x1, 0x1, 0x10062c338, 0x0), at 0xffffffff7e3bc8dc
[13] APT_OSL_SIL_DataEntity::instantiateAndInitializeDataSet(0x10062c1b8, 0x1, 0xffffffff7fffc140, 0x100627f78, 0x1, 0x800), at 0xffffffff7f2ceb18
[14] APT_OSL_SIL_StepSpec::instantiateAndInitializeStep(0x1800, 0xffffffff7f48eec0, 0x2000, 0x100133030, 0x0, 0x4240), at 0xffffffff7f298a90
[15] APT_OSL::createAndCheckStep(0x1002cddf0, 0xffffffff7fffdd48, 0x1b0, 0xffffffff7fffc330, 0xffffffff7fffc380, 0x100126500), at 0xffffffff7f22d2e4
[16] APT_ORCHESTRATE_main(0x100227f90, 0xffffffff7fffde50, 0xffffffff7fffd578, 0xffffffff7fffde28, 0xffffffff7fffdac8, 0xffffffff7fffddb0), at 0x100011bd4
[17] APT_PMconductorMain(0x1a5d0, 0xffffffff7fffe6b8, 0xffffffff7fffe6e0, 0x1, 0xffffffff7edf4b40, 0x1600000000), at 0xffffffff7e727aac
[18] APT_SharedMain(0x11, 0xffffffff7fffedc0, 0xffffffff7fffec08, 0x8, 0xffffffff7fffebe0, 0xffffffff7edf4b40), at 0xffffffff7e75cdc4
detaching from process 15779


Anyone has any idea on this?

Thanks
Atul
atulgoel
Participant
Posts: 84
Joined: Tue Feb 03, 2009 1:09 am
Location: Bangalore, India

Post by atulgoel »

Hi All,

I found the solution myself. Delete the datasets that you are creation in the job and create them again or either change the datasets name. After this, the job will ran fine.

THanks
Atul
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Yah, looks like they were corrupted... guessing you may have run out of space.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply