DSXchange

IBM's response There is issue with Jobmon if the number of records crosses some limit. To avoid that, please set the following: APT_MONITOR_SIZE=100000 or more APT_DISABLE_COMBINATION=true One of the parameters that was set when the problem was resolved was, APT_NO_JOBMON to True, this would also wo...

John Smith wrote:Can you try this - change the name of the dataset in your job and rerun?

Yes, that didnt work either. Getting the same exception.

Are you accessing a Data Set that was created with a different configuration file (and therefore with a different number of partitions)? Thank you for replying Ray - We are having this issue with multiple jobs - one for a RTI job that aborts with this error as soon as it is enabled and the other fo...

We have the following set up. Our online application is bound with Datastage RTI jobs through Text over JMS bindings. Each RTI job has its own input/output destinations and corresponding MDBs deployed in WebSphere. Recently we started getting the following error causing it to abort: ********** main_...

Hi Keshav,

Do you have the patch details? Specific version#s?

Thanks

We are facing issues with a couple of jobs throwing "Fatal Error: The input interface does not contain component "sortRec". Is it related to applying patches while installing DS server??? Also it is purely server related since the same job works in other environments without issues(I ...

I am also facin this issue.
Please suggest your valuable comment on this.

I am also facin this issue.
Please suggest your valuable comment on this.

Hi all, We have been suffering from poor performance of several queries against DB2 UDB invoked by DataStage. We are using DataStage 7.5.1.A and use the ODBC Stage to access DB2 through the Data Direct driver. We have a DB2 solution to use the REOPT(ALWAYS) funtion for these queries. From a pure DB2...

Ok...good luck. One question, based on your notes...it sounds like this particular Operation has two Jobs attached? (ie.. Job B on Server "X" and also on Server "Y")? That's a great failover and load balancing scenario, but is more complicated for debugging. Ernie Yes, we have a...

Well, something changed. I'd probably try things such as "stopping" (at the WAS console) one jar or the other, and see if the pattern still occurs, or if Job B continues to fail if it is the only job that has a working MDB, and/or if it is the only job that is "enabled". Also, r...

Yes... it is a very weird problem. These jobs each have separate services/operations and MDBs.

Yes, I am pretty sure the WAS error was a consequence of the DS abort. The problem here is the listener port corresponding to jobA went down and the instance # matches with jobB. The aborting instances of jobB do not perform any work when it aborts. It aborts due to the following errors: main_progra...

Thank you for responding. Is it a new application (mdb jar), or one that was just recently deployed? Just guessing at the moment, but some generic searches on the "non-application exception" in WAS always seem to come up with EAR or JAR configuration/installation ssues..... Does this one a...

We have the following set up. Our online application is bound with Datastage RTI jobs through Text over JMS bindings. Each RTI job has its own input/output destinations and corresponding MDBs deployed in WebSphere. Recently we had the following issue - Listener port (in WebSphere) corresponding to t...