DSXchange

Hi all, My parallel Job name is : QS_Sample_InvestigateJob_New Project name : satyam Compilation is successful. When i execute the job, its throwing the below error.. Error setting up internal communications (fifo //./pipe/satyam-RT_SC58-QS_Sample_InvestigateJob_New.. This is not just for this job. ...

Looks like you are attempting to compile the Job which is calling the routine too.. Try to write out the list of jobs compiled into a file or into Datastage Log (as information)... (By writing a statement at the start and end of the Loop to log the information such as "Compilation started for J...

How are you restarting your service ? From telnet window ??

Check if the connections are dying as soon as the Telnet session expires.

Try to start service as a background process (using '&' )

Due to diskspace constraints on our UNIX box, we are needed to move the Datastage projects from the path /ascential/datastage/Projects/ProjectName to /san/datastage/Projects/ProjectName One way of doing this is to create a New Project, Export the Old Project and Import into the New Project. Consider...

Did you set the NLS_LANG ?

Try to put in a "where" condition to limit the number of rows and see if the error still appears.

Try to put in a "where" condition to limit the number of rows and see if the error still appears.

Are the tunables (Read /Write cache size for Hashed file stage & Active-Active link Performance settings) The same for both the projects ?

change capture would help

Hi, After installed the XML patch we got the following warnings could you please guide us to resolve this problem. Xml_Currency,0: Warning: New_SOA.Webs_Currency: ASCL-DSJNI-00001`:`TJStage::initialize: initializing Transformer for Java stage; resource path not found Webs_Currency,0: Warning: New_SO...

Dear All,

Could you please anybody help me on this issue.

Thanks & Regards
Rao

We are unable to connect to the web service client..and the following errors are getting...any help in this is appreciated. main_program: Failed to initialize job monitoring. Monitor information will not be generated. Xml_Currency,0: Error: The name '{0}' is not a valid NCName. expression = '/:operJ...

Thank's a lot Ray for your kind information.

Warm Regards,
Raja.

Hi We have migrated datastage jobs from Test to Prod Environments (using Datastage Export and Import). However there is a requirement to verify that all the components have been successfully ported to new environment. We have tried 2 approaches, but both of them have been denied by the testing group...

If you have executed the datastage job from your id, you should be able to log on to unix with the same login id and kill the phantom.

Try to see if you can clean up resources from Datastage Director for that job.