Internal Error in main_program

[bdstage]

Hello all,

I have a job which is giving a strange error while I am trying to validate and execute.

The exact error message is:

Code: Select all

main_program: Internal Error: (APT_SC::downcast(pConsumer())->kind() == APT_Operator::eParallel): sc/sc.C: 3984 
Traceback:   [6] APT_FatalPath::pureAssertion(0xfedf549c, 0xfedf54dd, 0xf90, 0xc00, 0xff1acad4, 0x8), at 0xff0e6918 
  [7] APT_SC::IPC_DataSet::computeStraightThroughOptimization(0xf76a40, 0x10c11f8, 0xf7c930, 0xfedf5454, 0xf76a6c, 0x2), at 0xfeaa2acc 
  [8] APT_IR::Score::compose(0x577ca0, 0x0, 0x4, 0x1, 0xfedeffab, 0x577cb4), at 0xfea7ff34 
  [9] APT_ScoreComposer::compose(0x36b628, 0x262ca4, 0xfee70888, 0xff1ba020, 0x5d298, 0xfedf8729), at 0xfeaa9f70 
  [10] APT_ScoreComposer::compose(0x36b628, 0x262ca4, 0xfedf86f9, 0xfee30abc, 0x230c, 0xfee83258), at 0xfeaa9ed0 
  [11] APT_StepRep::check(0x262c98, 0x1, 0xffbfd020, 0x0, 0xfee6f124, 0x0), at 0xfe7bbeec 
  [12] APT_Step::check(0x36b628, 0xffbfd1b8, 0xffbfd180, 0xffbfd180, 0xffbfd0fc, 0xfee30abc), at 0xfe7b11dc 
  [13] APT_OSL::createAndCheckStep(0x2b9858, 0xffbfe26c, 0xd4, 0x9, 0xffbfd19c, 0xffbfd1b8), at 0xff222908 
  [14] APT_ORCHESTRATE_main(0x2bf50, 0xffbfdd38, 0xffbfe2fc, 0xffbfe0d0, 0xffbfe2a8, 0xffbfe2c4), at 0x1f954 
  [15] APT_PMconductorMain(0x0, 0xcc00, 0xff1b50c4, 0xfee30abc, 0xffbfe8b4, 0xffbfe8d0), at 0xfea1edec 
  [16] APT_SharedMain(0xc, 0xffbfebc4, 0x17378, 0xc, 0x1, 0x17000), at 0xfea52038 
detaching from process 28875

All I am doing in the job is doing some lookups through Data sets and removing the duplicates through Remove Duplicates stage and loading into an Oracle table.

I have no clue about it. I tried restarting DataStage services. But there is no use.

Thanks in advance for the replies!!

[bdstage]

The job is running fine if it is using a single node configuration file.

We are having problems only when we are using a 2 node configuration file.

IBM Support guy told me to add APT_DISABLE_STRAIGHT_THROUGH_OPTIMIZATION as an environment variable with a vaue of 1. It solved the error message that is present in the post. But it is giving a few more errors.

Here are the error messages:

Code: Select all

buffer(1),0: Failure during execution of operator logic. [api/operator_rep.C:376]
buffer(0),1: Failure during execution of operator logic. [api/operator_rep.C:376]
buffer(1),1: Failure during execution of operator logic. [api/operator_rep.C:376]
buffer(2),1: Failure during execution of operator logic. [api/operator_rep.C:376]
buffer(3),1: Failure during execution of operator logic. [api/operator_rep.C:376]
buffer(3),0: Failure during execution of operator logic. [api/operator_rep.C:376]
buffer(0),0: Failure during execution of operator logic. [api/operator_rep.C:376]
buffer(2),0: Failure during execution of operator logic. [api/operator_rep.C:376]

buffer(0),0: Internal Error: (outDS->isStraightThrough()): iomgr/bufferop.C: 1907 
Traceback:   [6] APT_FatalPath::pureAssertion(0xfedded4b, 0xfedded66, 0x773, 0xfe9aabb8, 0xff1acad4, 0x24), at 0xff0e6918 
  [7] APT_BufferOperator::addAllSockets(0xc672d8, 0x80, 0x451e90, 0xfee30abc, 0xfee8250c, 0xfedded14), at 0xfe9a8d84 
  [8] APT_BufferOperator::runLocally(0xc672d8, 0xa, 0xfe9a8dec, 0xfee7b894, 0xc6a638, 0x0), at 0xfe9a8e04 
  [9] APT_OperatorRep::run(0xc675e8, 0xc67630, 0xc672d8, 0xc6a638, 0x18400, 0xffbfc7ac), at 0xfe746680 
  [10] APT_SC::Operator::runLocally(0x12f5a0, 0x0, 0x1, 0x0, 0xfea86dc0, 0x12f5ec), at 0xfea960a0 
  [11] APT_ProcessManager::executePlayer(0x16639c, 0x210167be, 0x4, 0xfee816fc, 0xffbfcbd8, 0xffbfcbf4), at 0xfea5a610 
  [12] executeStep(0xc29d0, 0x4, 0xfee80588, 0xfee30abc, 0xffbfcf98, 0x15094c), at 0xfea57830 
  [13] APT_PMcontrolServiceTableClass::dispatch(0x9aa28, 0xc29d0, 0xfea57570, 0xbf508, 0xf0, 0x1e), at 0xfea23a5c 
  [14] APT_PMMessagePort::dispatch(0xbed60, 0xc29d0, 0xd274, 0xfee7e780, 0x0, 0xc29d0), at 0xfea2c5e0 
  [15] APT_PMMessagePort::poll(0xd000, 0x1, 0x4, 0x1, 0xfee30abc, 0x440190), at 0xfea2df34 
  [16] APT_PMdispatchLoop(0x1, 0xfee7e340, 0x1, 0xfee30abc, 0xd090, 0xd000), at 0xfea2460c 
  [17] APT_ProcessManager::playerMain(0x2, 0xfee7fbbc, 0xfee7fbb8, 0xfee7fbc0, 0xfee7fbb0, 0xfee30abc), at 0xfea56df0 
  [18] APT_PMPlayer::APT_PMPlayer(0x104cd8, 0x3, 0xfea56bd4, 0x19800, 0xfedebd79, 0x0), at 0xfea433ac 
  [19] startPlayerSvc(0xc29d0, 0xfee30abc, 0x1f, 0x1a, 0x230c, 0x104cd8), at 0xfea57350 
  [20] APT_PMcontrolServiceTableClass::dispatch(0x9aa28, 0xc29d0, 0xfea5722c, 0xbf508, 0xe0, 0x1c), at 0xfea23a5c 
  [21] APT_PMMessagePort::dispatch(0xbed08, 0xc29d0, 0xd274, 0xfee7e780, 0x0, 0xc29d0), at 0xfea2c5e0 
  [22] APT_PMMessagePort::poll(0xd000, 0x1, 0x4, 0x1, 0xfee30abc, 0x9aa48), at 0xfea2df34 
  [23] APT_PMdispatchLoop(0x1, 0xfee7e340, 0x1, 0xfee30abc, 0xd090, 0xd000), at 0xfea2460c 
  [24] APT_PMsectionLeaderMain(0xbed08, 0x17000, 0xfee30abc, 0xfeded994, 0xffbfe6f4, 0xffbfe838), at 0xfea5c1a8 
  [25] APT_SharedMain(0xa, 0xffbfeb5c, 0x17378, 0x7fc00, 0x3e, 0x17000), at 0xfea520d0 

Once I get to know the solution from IBM Support, I will post it here.

Thanks!!

[singhald]

Could you please tell us how did you resolve this issue

[chulett]

They haven't posted here in five years. Best if you start your own post and explain to us the issue that you are having.