Page 1 of 1

error : Internal Error: (size <= blocksize_): iomgr/ioco

Posted: Mon Oct 13, 2014 4:50 am
by ulab
HI,

am getting this issue from the past 3 days in the production, any suggestions/help is appriciated.

LKP_PPREF_ACT_OPT_ID,2: Internal Error: (size <= blocksize_): iomgr/iocomm.C: 1902
Traceback: assert.APT_FatalPath::pureAssertion(const char*,const char*,int)(??, ??, ??) at 0x90000000ab41b88 APT_Communicator::shmemAllocBuffer(int)(??, ??) at 0x90000000b2fbb48 APT_IOBlkCtl::APT_IOBlkCtl(int,int,int,APT_Communicator*)(??, ??, ??, ??, ??) at 0x90000000b2e6a84 APT_IOPort::alloc(int)(??, ??) at 0x90000000b2ef650 APT_DMFileIOPartition::newBlock(APT_DMStatus&,bool&,APT_IODir,unsigned int&,const unsigned char*,unsigned int,int*,APT_DMInputCursor::ReadingMode,int)(??, ??, ??, ??, ??, ??, ??, ??) at 0x90000000b2d5e88 APT_DMBlockedPartition::getOutputRecord_block(unsigned int,void**,int&,int&)(??, ??, ??, ??, ??, ??) at 0x90000000b2d4158 APT_DataSetRep::prepareForRun(APT_DataSet::Direction,APT_ErrorLog&)(??, ??, ??) at 0x90000000ad73520
APT_OperatorRep::prepareForRun()(??) at 0x90000000adc1dd0
APT_OperatorRep::run()(??) at 0x90000000adc0738
APT_OperatorSC::runLocally()(??) at 0x90000000affce24 APT_SC::Operator::runLocally(unsigned int)(??, ??) at 0x90000000b2294d4
APT_IR::Process::runLocally()(??) at 0x90000000b38ac24
APT_ProcessManager::executePlayer(APT_ScoreProcess*)(??) at 0x90000000b33ebfc rtpexecutil.executeStep(const APT_PMMessageHeader*)(??) at 0x90000000b32dc04 APT_PMcontrolServiceTableClass::dispatch(const APT_PMMessageHeader*) const(??, ??) at 0x90000000b01c0b4
APT_PMMessagePort::dispatch()(??) at 0x90000000b023258 APT_PMMessagePort::poll(double,unsigned int)(??, ??) at 0x90000000b025178
APT_PMdispatchLoop()() at 0x90000000b01fc38
APT_ProcessManager::playerMain(void*)(??) at 0x90000000b32cd80 APT_PMPlayer::APT_PMPlayer(void(*)(void*),void*)(??, ??, ??) at 0x90000000b00f57cLearn more...

Posted: Mon Oct 13, 2014 5:08 am
by ulab
some more info on this,

I deleted all the old files from the project/&PH& folder as per a technote but still no use,

NOTE: this job completed fine once before this abort, but before that it got failed, since 3 days couple of times it executed fine after changing the values APT_Max_Transport_block and APT_Min_Transport_block values.

any inputs on this issue is appriciated,

thanks.

Posted: Mon Oct 13, 2014 6:45 am
by qt_ky
What changed?

Posted: Mon Oct 13, 2014 3:22 pm
by ray.wurlod
Have you changed the memory offsets used by DataStage engine?