APT_BadAlloc: Heap allocation failed

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
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

APT_BadAlloc: Heap allocation failed

Post by kanasai167 »

My job flow is like this :
DB2Connector --> Sort --> Transformer --> Filter --> DB2Connector

My source data is around 10m records with 8 columns , final output data is around 1m records with 80 columns. My development server is win2008 r2 with 32g ram.
And i got the error at the transformer when i run the job.
I see one of the solution is adding the number of node , where can i set this? Thank you.

Below is my job log :
Transformer_1,0: Caught exception from runLocally(): APT_BadAlloc: Heap allocation failed..
Transformer_1,0: Failure during execution of operator logic.
Transformer_1,0: Input 0 consumed 42274 records.
Transformer_1,0: Output 0 produced 42263 records.
Transformer_1,0: Fatal Error: Caught unknown exception in player process: terminating.
node_node1: Player 3 terminated unexpectedly.
Transformer_1,0: Failure during execution of operator logic.
Transformer_1,0: Input 0 consumed 42800 records.
Transformer_1,0: Output 0 produced 42799 records.
Transformer_1,0: Fatal Error: Unable to allocate communication resources
node_node2: Player 2 terminated unexpectedly.
main_program: APT_PMsectionLeader(2, node2), player 2 - Unexpected exit status 1.
Sort_2,1: Failure during execution of operator logic.
Sort_2,1: Input 0 consumed 4971675 records.
Sort_2,1: Output 0 produced 21824 records.
Sort_2,1: Fatal Error: Unable to allocate communication resources
node_node2: Player 1 terminated unexpectedly.
main_program: APT_PMsectionLeader(2, node2), player 1 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 3 - Unexpected exit status 1.
DB2_Connector_0,0: sendWriteSignal() failed on node MSDFA230 ds = 0 conspart = 1 Broken pipe
DB2_Connector_0,0: Could not send close message (shared memory)
Sort_2,0: Failure during execution of operator logic.
Sort_2,0: Input 0 consumed 4971566 records.
Sort_2,0: Output 0 produced 21824 records.
Sort_2,0: Fatal Error: Unable to allocate communication resources
node_node1: Player 2 terminated unexpectedly.
main_program: APT_PMsectionLeader(1, node1), player 2 - Unexpected exit status 1.
main_program: Step execution finished with status = FAILED.
main_program: Startup time, 0:15; production run time, 2:02.
Job TESTING_OTHDATA aborted.



Environment variable settings:
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Windows\system32\config\systemprofile\AppData\Roaming
APT_COMPILEOPT=-W/TP -W/EHa -DAPT_USE_ANSI_IOSTREAMS -c -W/Zc:wchar_t-
APT_COMPILER=cxx
APT_CONFIG_FILE=C:/IBM/InformationServer/Server/Configurations/default.apt
APT_DISABLE_COMBINATION=1
APT_ERROR_CONFIGURATION=severity, !vseverity, !jobid, moduleid, errorIndex, timestamp, !ipaddr, !nodeplayer, !nodename, opid, message
APT_LINKER=cxx
APT_LINKOPT=-s -W/dll -W/base:0x50000000 -W/Zc:wchar_t-
APT_MONITOR_MINTIME=10
APT_NO_ONE_NODE_COMBINING_OPTIMIZATION=1
APT_OPERATOR_REGISTRY_PATH=C:\IBM\InformationServer\Server\Projects\dstage1\buildop
APT_ORCHHOME=C:/IBM/InformationServer/Server/PXEngine
APT_STRING_PADCHAR=0x20
APT_USE_CRLF=1
BELL=^G
CLASSPATH=C:\Program Files (x86)\IBM\WSClassic95\JDBC/cacjdbc21.jar;.;C:\IBM\SQLLIB\java\db2java.zip;C:\IBM\SQLLIB\java\db2jcc.jar;C:\IBM\SQLLIB\java\sqlj.zip;C:\IBM\SQLLIB\java\db2jcc_license_cu.jar;C:\IBM\SQLLIB\bin;C:\IBM\SQLLIB\java\common.jar
COMPUTERNAME=MSDFA230
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramFiles=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
ComSpec=C:\Windows\system32\cmd.exe
DB2INSTANCE=DB2
DISCOVERY_GERONIMO_HOME=C:\Program Files (x86)\IBM\InfoSphere\Discovery\Discovery Server
DISCOVERY_HOME=C:\Program Files (x86)\IBM\InfoSphere\Discovery
DISCOVERY_JAVA_HOME=C:\Program Files (x86)\IBM\InfoSphere\Discovery\Java60\jre
DISCOVERY_SERVER_START=C:\Program Files (x86)\IBM\InfoSphere\Discovery\Discovery Server\bin\run-Discovery.bat
DISCOVERY_SERVER_STOP=C:\Program Files (x86)\IBM\InfoSphere\Discovery\Discovery Server\bin\shutdown-Discovery.bat
DISPLAY=:0.0
DS_ENABLE_RESERVED_CHAR_CONVERT=0
DS_OPERATOR_BUILDOP_DIR=buildop
DS_OPERATOR_WRAPPED_DIR=wrapped
DS_TDM_PIPE_OPEN_TIMEOUT=720
DS_TDM_TRACE_SUBROUTINE_CALLS=0
DS_USERNO=-10956
DSIPC_OPEN_TIMEOUT=30
FLAVOR=-1
FP_NO_HOST_CHECK=NO
INCLUDE=C:\IBM\SQLLIB\INCLUDE;C:\IBM\SQLLIB\LIB;C:\Program Files\Microsoft SDKs\Windows\v7.1\Lib
ISUSER=SNYAP
LIB=C:\Program Files\Microsoft SDKs\Windows\v7.1\Lib;C:\IBM\SQLLIB\LIB
LOCALAPPDATA=C:\Windows\system32\config\systemprofile\AppData\Local
MAN_CHM_INDEX=C:/PROGRA~2/MKSTOO~1/etc/chm/tkutil.idx;C:/PROGRA~2/MKSTOO~1/etc/chm/tkapi.idx;C:/PROGRA~2/MKSTOO~1/etc/chm/tcltk.idx;C:/PROGRA~2/MKSTOO~1/etc/chm/tkcurses.idx
MAN_HTM_PATHS=C:/PROGRA~2/MKSTOO~1/etc/htm/perl;C:/PROGRA~2/MKSTOO~1/etc/htm/perl/pod;C:/PROGRA~2/MKSTOO~1/etc/htm/perl/ext;C:/PROGRA~2/MKSTOO~1/etc/htm/perl/lib
MAN_TXT_INDEX=C:/PROGRA~2/MKSTOO~1/etc/tkutil.idx;C:/PROGRA~2/MKSTOO~1/etc/tkapi.idx;C:/PROGRA~2/MKSTOO~1/etc/tcltk.idx;C:/PROGRA~2/MKSTOO~1/etc/tkcurses.idx
NUMBER_OF_PROCESSORS=4
NUTCROOT=C:\PROGRA~2\MKSTOO~1
OS=Windows_NT
OSH_STDOUT_MSG=1
PATH=C:\IBM\InformationServer\Server\PXEngine\bin;C:\IBM\InformationServer\Server\PXEngine\osh_wrappers;C:\IBM\InformationServer\Server\PXEngine\user_osh_wrappers;C:\IBM\InformationServer\Server\PXEngine\user_osh_wrappers;C:\IBM\InformationServer\Server\DSComponents\bin;C:\IBM\InformationServer\Server\DSParallel;C:\IBM\InformationServer\Server\Projects\dstage1\RT_BP401.O;C:\IBM\InformationServer\Server\DSEngine\bin;C:\IBM\InformationServer\Server\Projects\dstage1\buildop;C:\IBM\InformationServer\Server\Projects\dstage1\wrapped;C:\Program Files (x86)\IBM\WSClassic95\ODBC\lib;C:\Program Files (x86)\IBM\WSClassic95\ODBC\bin;C:\Program Files (x86)\MKS Toolkit\mksnt;C:\PROGRA~2\MKSTOO~1\bin64;C:\PROGRA~2\MKSTOO~1\bin;C:\PROGRA~2\MKSTOO~1\bin\X11;C:\PROGRA~2\MKSTOO~1\mksnt;C:\IBM\InformationServer\ASBNode\apps\jre\bin\classic;C:\IBM\InformationServer\ASBNode\lib\cpp;C:\IBM\InformationServer\ASBNode\apps\proxy\cpp\vc60\MT_dll\bin;D:\app\Administrator\product\11.2.0\client_1;C:\Windows\system32;C:\Windows;C:\Windows\system32\wbem;C:\Windows\system32\windowspowershell\v1.0\;c:\program files\ibm\gsk8\lib64;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Windows/SysWOW64;C:\IBM\SQLLIB\BIN;C:\IBM\SQLLIB\FUNCTION;C:\IBM\SQLLIB\SAMPLES\REPL;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.sh;.ksh;.csh;.sed;.awk;.pl
PIDTOK=12156
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_ARCHITEW6432=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 44 Stepping 2, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2c02
ProgramData=C:\ProgramData
ProgramFiles(x86)=C:\Program Files (x86)
ProgramFiles=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
PWD=C:\IBM\InformationServer\Server\Projects\dstage1
PX_DBCONNECTHOME=C:/IBM/InformationServer/Server/DSComponents
ROOTDIR=C:/PROGRA~2/MKSTOO~1
SHELL=C:/PROGRA~2/MKSTOO~1/mksnt/sh.exe
SYS_ID=ABC
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Windows\TEMP
TERM=console
TERMCAP=C:\PROGRA~2\MKSTOO~1\etc\termcap
TERMINFO=C:\PROGRA~2\MKSTOO~1\usr\lib\terminfo
TMP=C:\Windows\TEMP
UNIVERSE_CONTROLLING_TERM=1
UNIVERSE_PARENT_PROCESS=12156
USER=MSDFA230\DFIC_a
USERDOMAIN=BSN
USERNAME=MSDFA230$
USERPROFILE=C:\Windows\system32\config\systemprofile
VS100COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\
VS90COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Tools\
WHO=dstage1
windir=C:\Windows
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log
arvind_ds
Participant
Posts: 428
Joined: Thu Aug 16, 2007 11:38 pm
Location: Manali

Post by arvind_ds »

Try to increase the max heap sixe in WAS & proxy.xml file and then test again.

HTH
Arvind
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

in WAS... , is it the Administrative Console under the IBM WebSphere?

I able to login , but i can't find where to set the heap size.

By the way , i found some guide on changing the heap size in registry , not sure if this is the right one , need some advice first before i change this.

To change the heap size
Go to registry editor and change the non interactive desktop heap size.
Go to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Session Manager > SubSystems.
Click on windows on the right pane.
Now edit the ShareSection parameter in the value box
Change the last value from 512 to 1024.



my current SharedSection=1024,20480,768

Thanks
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

i already change the max heap size in administrative console and also the proxy.xml
But the heap size error still there...
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

It's not a WAS issue.

9 times out of 10 I see jobs failing because of NLS or bad character set selections. Look there first.

A) Talk to the DBA and get the correct character set for the data.
B) convert your job to use that character set. In the stages and as a job default.
C) Remove all job warning messages. (Null exception handler, etc..)
D) recompile / reexecute.
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Post by SURA »

Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Post Reply