Hi all,
Currently using DataStage Version 8.1, a parallel job is extracting data from Oracle table using Dynamic RDBMS stage. The table contains one column, which has been defined as varchar in the stage metadata with no length defined.
I can successfully "view data" from within the stage, but when I run the job, it fails with the SIGSEGV error as below -
Dynamic_RDBMS_6,0: Operator terminated abnormally: received signal SIGSEGV
The same job runs successfully in DataStage version 8.0.1.
However, if I define the length of the column (say 255) in the stage metadata (version 8.1), the job runs successfully. Could anyone please explain the reason for this behaviour and if the job can be run without defining the varchar length?
Thanks in advance!
Dynamic RDBMS (Oracle) - Varchar Issue
Moderators: chulett, rschirm, roy
Dynamic RDBMS (Oracle) - Varchar Issue
Nitin Mediratta
Think Different!
Think Different!
That's an obvious question. Answer is that we are moving from 8.0 to 8.1 and the golden rule is, not to change any code. Of course, if there is no other solution, then this approach will have to be followed.chulett wrote:Why not just set an appropriate length and move on? ...
I was hoping if anyone encountered the same problem on 8.1 and knows of a solution. But if I do not find any solution, then might contact support.
Nitin Mediratta
Think Different!
Think Different!