DSXchange

Greetings,

When I trigger the dsjob executable from the Command Line I get this Error Message "Segmentation Fault(coredump)".

Please let me know where the problem lies and how can I rectify this ???.

Thanks in Advance.

Badhri ...

Badhrinath Krishnamoorthy
www.cognizant.com

Greetings,

This is Badhri again regarding the "Segmentation Fault(coredump)" issue i face when triggering the dsjob from the command line. Kindly let me know your thoughts in this.

The DS is installed in Sun Solaris 2.8

Thanks,
Badhri ...

Badhrinath Krishnamoorthy
www.cognizant.com

Badhri,

Please supply more information as to the nature of your problem.

A couple of basic questions to get things started are:
- Can you run any jobs successfully from Director?
- Are these the jobs that give the coredump?
- Is your command line environment set up correctly? I think there's a "dsenv " script in the DSEngine directory that you can run that may help (". ./dsenv").


I can think of several other questions, depending on how you answer these.

Good Luck,
Tony

Hi Tony,

Thanks for looking into this.

I don't have any issues running the jobs from the Datastage Director. The problem is when I try to run the dsjob command in the command line to get some Metadata info. For Example,

dsjob -server 10.10.22.70 -user -password -jobinfo edw_601 StageA

Let me know incase need any more info.

Thanks,
Badhri ...

Badhrinath Krishnamoorthy
www.cognizant.com

Badhri,

I am by no means an expert at this, so be patient.

You didn't answer my question about setting up your environment. Did you look into this? I know there are some environment variables that need to be set up correctly and, as I mentioned, there is a script file in the ../DSEngine directory called "dsenv". You can execute it by cd'ing to the ../DSEngine directory and running ". ./dsenv" before trying to run dsjob.

Hope this helps,
Tony

Greetings,

My dsenv file seems to be fine and I also executed the same once but no luck. Is there anything paricular in dsenv tha6 should be taken care ?.

But the issue is that the "dsjob" executable works fine in my development box and not in my Production and all the paramters in dsenv in both the boxes are alike.

Thanks,
Badhri ...

Badhrinath Krishnamoorthy
www.cognizant.com

Could be that your environment isn't the same on your production box as on the development box. I would look at where your datastage directories are in the path and shared library environment variables. I suspect you'll find something wrong there.

Is this a Unix box?

tony

Try including the -run option in your dsjob command.

Enter dsjob with no command line options to get the top-level syntax.
Enter dsjob -run but with no other command line options to get the run-level syntax.

Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518