Internal Error: (nP==nC): sc/sc.C: 3858

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
Telenet
Premium Member
Premium Member
Posts: 14
Joined: Fri Nov 24, 2006 6:18 am
Location: Telenet

Internal Error: (nP==nC): sc/sc.C: 3858

Post by Telenet »

Anyone ever seen this error ? Has this something to do with the internal buffering ?


main_program: Internal Error: (nP==nC): sc/sc.C: 3858
Traceback: [6] APT_FatalPath::pureAssertion(0xff13219c, 0xffbeca30, 0xffbeca4c, 0xf12, 0xfed76488, 0xfed76480), at 0xff06c914
[7] APT_SC::IPC_DataSet::computeStraightThroughOptimization(0xfed763ec, 0x1, 0x2, 0x5ccad0, 0xfed6fdc0, 0xfed761e0), at 0xfea222ec
[8] APT_IR::Score::compose(0x35, 0xfed6fd5c, 0xfedb9380, 0x25, 0x18, 0x5b0e18), at 0xfe9ff52c
[9] APT_ScoreComposer::compose(0x5b0dd8, 0x1f3af4, 0xfedefb64, 0x1f3af4, 0x1f3af4, 0x5b0dd8), at 0xfea2c3c0
[10] APT_ScoreComposer::compose(0x124be8, 0xfee0ec34, 0xffbed274, 0xfedefb64, 0xfedfe890, 0xfedb9380), at 0xfea2c2e8
[11] APT_StepRep::check(0x0, 0xfedeec4c, 0x0, 0x0, 0x0, 0x14fbe0), at 0xfe762c0c
[12] APT_Step::check(0x124be8, 0xfedb9380, 0x124be8, 0xffbed4f8, 0xffbed4f8, 0xffbed4f8), at 0xfe7575cc
[13] APT_OSL::createAndCheckStep(0x150ec0, 0xffbee740, 0xff36bba0, 0x150ec0, 0x32bac, 0xffbed584), at 0xff23eb08
[14] APT_ORCHESTRATE_main(0xa2b58, 0x0, 0x150ec0, 0xff131b70, 0x44dc8, 0x1), at 0x209a8
[15] APT_PMconductorMain(0xffbeed58, 0x47e08, 0xfedfa60c, 0xff233c6c, 0xff233c6c, 0xffbeedac), at 0xfe9afe9c
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Looks like an 'assert error' to me, one of those 'This must be true' checks that abort if not true. You'll need to take this to your official Support provider, I would think.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Telenet
Premium Member
Premium Member
Posts: 14
Joined: Fri Nov 24, 2006 6:18 am
Location: Telenet

Post by Telenet »

It seems that this error is due to the buffer strategy used. This error pops-up when we force buffering on a poorly designed (the partitioning is not well looked after) parallel job. I have the impression that the partitionning is preserved when you go for "force buffering" and the partitionning is "revisited" if you go for "automatic buffering"
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Hmmm... regardless, I don't believe one should be able to generate any kind of an assert error, that would normally indicate a code problem.
-craig

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