I have a BASIC transformer and one i/p file and o/p file in a parallel job...getting the following error...very surprising...I have no clue what is happening!!!
I don't really like what you're doing. Principally, what is @ID doing, and how is it actually specified in the expression in the BASIC Transformer?
You really shouldn't, however, be querying the repository tables in this way for every row processed - you can end up with a deadlock situation if DataStage is also trying to update the repository table.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Full Text. BASIC_Transformer_34,0: Operator terminated abnormally:
runLocally did not return APT_StatusOk
Does this indicate anything to you....It is a basic transformer in a parallel job...Parallel transformer works fine.
Thanks,
Ashwin
ray.wurlod wrote:I don't really like what you're doing. Principally, what is @ID doing, and how is it actually specified in the expression in the BASIC Transformer?
You really shouldn't, however, be querying the repository tables in this way for every row processed - you can end up with a deadlock situation if DataStage is also trying to update the repository table.
@ID
FIELD ( TRANS ( RT_LOG109 , //JOB.STARTED.NO , 1 , X ) , ( char ( 252 ) ) , 1 )
as an (the?) expression in the BASIC Transformer.
So can you advise what you ARE doing in the BASIC Transformer stage that is failing to execute? The operator that it has generated has failed to run successfully, as you can see in the log, but there is no guidance from you as to what it is trying to do (and therefore why it might be failing).
Right now, you've given us "my car doesn't work, can you fix it?".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I am not doing anything in the transformer. I am just mapping i/p cols and o/p cols...I think the real problem (I dont know what it is...hence this query) is not evident in the log.
OK. If the problem is with a BASIC Transformer stage (as per your subject), then you ARE hitting it every row. But, of course, you're not even getting to process row #1.
Yet the log file is telling us that the runLocally() function associated with the operator generated by compiling the BASIC Transformer stage has something about it that caused it to fail, or that the operator itself has something about it.
If all you're doing is mapping input to output columns, why aren't you using a Transformer stage (rather than a BASIC Transformer stage)?
Do you get this problem with every job that contains a BASIC Transformer stage, or only the one job? If more than one, can you discern anything else that might be a pattern? What happens, for example, if you specify a one-node configuration?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I get this problem with every job that contains a BASIC Transformer stage....I havent tried the node configuration though...I tried to change sequential/parallel option in BASIC tx but still got the same error.
Anyway we will be moving to a different env from now.....will check out this situation there.
I've just gone through the process of removing all BASIC transformers from my parallel job. Everything was working fine, until i started integrating the PX jobs with Job sequeneces then i started recieving MUTEX errors, i followed the advise on this board and switched over to Parallel Transformer to resolve the issue.
You might want to consider migrating away from BASIC transformers to avoid unexpected issues further down the line.