One of our jobs aborted in production while direct loading the data from one oracle table(source) to another Oracle table(target) with no transformtion,this job used to run succefully till previous run.
When we tried to veiw data in Source it thro' following info
##I IIS-DSEE-TFCN-00001 11:23:34(000) <main_program>
IBM WebSphere DataStage Enterprise Edition 8.0.1.4458
Copyright (c) 2001, 2005-2007 IBM Corporation. All rights reserved
##I IIS-DSEE-TOSH-00002 11:23:34(001) <main_program> orchgeneral: loaded
##I IIS-DSEE-TOSH-00002 11:23:34(002) <main_program> orchsort: loaded
##I IIS-DSEE-TOSH-00002 11:23:34(003) <main_program> orchstats: loaded
##W IIS-DSEE-TOSH-00049 11:23:34(004) <main_program> Parameter specified but not used in flow: SOURCE_USER
##W IIS-DSEE-TOSH-00049 11:23:34(005) <main_program> Parameter specified but not used in flow: SOURCE_PWD
##W IIS-DSEE-TOSH-00049 11:23:34(006) <main_program> Parameter specified but not used in flow: SOURCE_TNS
##W IIS-DSEE-TOSH-00049 11:23:34(007) <main_program> Parameter specified but not used in flow: TARGET_USER
##W IIS-DSEE-TOSH-00049 11:23:34(008) <main_program> Parameter specified but not used in flow: TARGET_PWD
##W IIS-DSEE-TOSH-00049 11:23:34(009) <main_program> Parameter specified but not used in flow: TARGET_TNS
##W IIS-DSEE-TOSH-00049 11:23:34(010) <main_program> Parameter specified but not used in flow: _APT_ORACLE_PRESERVE_BLANKS
##W IIS-DSEE-TOSH-00049 11:23:34(011) <main_program> Parameter specified but not used in flow: DSProjectMapName
##I IIS-DSEE-TFSC-00001 11:23:57(005) <main_program> APT configuration file: D:/IBM/InformationServer/Server/Configurations/OneServer3Nodes.apt
##W IIS-DSEE-TOSH-00306 11:23:57(006) <oraE_src_MSF000_DC0001> Ignoring combining directive applied to a non-combinable operator
>##E IIS-DSEE-TFOR-00089 11:23:59(000) <_ABORT_IDENT_,0> The runLocally() of the operator failed.
##I IIS-DSEE-TFOR-00163 11:23:59(001) <_ABORT_IDENT_,0> Input 0 consumed 0 records.
>##E IIS-DSEE-TFOR-00089 11:23:59(002) <APT_CombinedOperatorController,0> The runLocally() of the operator failed.
##I IIS-DSEE-USBP-00001 11:23:59(000) <APT_CombinedOperatorController,0> called postFinalRunLocally
>##E IIS-DSEE-TFPM-00040 11:23:59(003) <APT_CombinedOperatorController,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
>##E IIS-DSEE-TFSC-00011 11:24:05(000) <main_program> Step execution finished with status = FAILED.
##I IIS-DSEE-TCOS-00026 11:24:05(001) <main_program> Startup time, 0:29; production run time, 0:01.
View Data runs its own osh script (you can choose to look at it in one of the dialog screens). This script has hit some in-built row limit. Try limiting View Data to only a few rows, then increase it gradually.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
This post is very old now, but as none of the others inquiring about the "VIEWDATA ROW LIMITER HIT" issue, I am attaching something that will possibly help others in future. It helped me today after a smart colleague pointed it out.
It is possibly just as simple to commit the data in your source table from DB end (i.e. TOAD or SQLDeveloper).
I had the same issue of the "job worked until recently and I changed nothing in the meantime!", and was convinced that it had to do with the DataStage as the same SQL query ran just fine from TOAD. This, regardless of changing the table values in the meantime.
So, just commit and see if it helps...
Actually i am getting the warning after job execution and not while viewing the data in oracle stage
Also i am executing a select query whithout any constraints on a specific oracle table.
I executed the select query in oracle and then executed COMMit;
But no chng
It's an unspoken rule and common courtesy to start your own post when you have an issue. That way we know your version of the product, your operating system, you can mark it Resolved when your questions have been answered and you can post the gory details of your problem rather coming into a similar thread and simply saying you "have the same problem". No, you don't. Get the point?
And while "the Moderator" may have said to search for an existing post rather than blindly creating a new one, the goal of said search is to see if the question you are planning on asking has already been asked and answered, so you get your answer right away. The goal is not to find a thread to hi-jack.
-craig
"You can never have too many knives" -- Logan Nine Fingers