DSXchange

Folks, I have the following requirement from customer --------------------------------- If the incoming data feed from the source systems contain records which have invalid format of data, then the attributes will be rejected and the record will be sent to the Landing table. ------------------------...

Hi, I am using a OCI Stage and selected for Load SQL from a file at run time and kept that SQL query in a file at the server whose path also I have mentioned. But while running the job I am getting the error: Oracle_OCI_0: ORA-24334: no descriptor for this position. Though from Director it is showin...

Ascential DataStage version 7.5.1A Yes ... Thanks Ray, I remember you are quite helpful, even an year back. But, precisely, what I am asking is, Does the product Ascential Datastage 7.5.1.A still exist for buying or downloading ? Or, has it been named IBM Websphere Datastage? In the later case, whi...

Hi,

I last worked on Ascential Datastage almost an year back. The version I was using was 7.5.1.A . What is the name and version of the product that I can use now to do the same things that we did earlier. Can I import my jobs from my earlier work to the Webspere Datastage ?

cheers
Soham

Hi,

Just to update it is a server job. It was working pretty fine in the Dev. But isnt working after moving to Prod. When it is writing to a oci, it's working fine. But cannot read from a OCI and throws the error OCI_INVALID_HANDLE.

thanks
soham

Thanks ray ...i would rather close ths thread here. This "multithreading" seems to be creating confusion. I will carry on with the other post

thanks
Soham

Yes, oracle client config seems to be the issue but cannot figure out what exactly might have gone wrong ? The oracle home and stuffs looks fine. Any further clues pal ??

thanks
Soham

Hi,

I am able to insert a into a oracle table, using a datastage job. But Job is not working when reading from table to a sequence file or another table. I could see using toad it is retrieving data from oracle but not able to write to the output system.

Thanks in advance
Soham

Hi, This one is a separate problem. Nothing to do with UTF8. I was not able to see the fatal error and the job aborted without throwing any error. Now i can see the error after changing NLS to UTF8. Now that I can see the error, the errors says OCI_INVALID_HANDLE. This is happening whenever i ttry t...

thanx ppl..the error started coming on changing the NLS settings. I changed it to UTF8. The error is that it cannot read from the OCI stages. Everything was running fine in DEV. When we migrated to PROD, all the jobs that read from a OCI started giving errors. The error is OCI_INVALID_HANDLE. The on...

Hi guys, I cannot read from any OCI stages. In the DEV, everything was running fine. When I migrated to prod, all the jobs that reads from the OCI are failing. The ones that are writing to OCI runs fine. One common error everywhere is OCI_INVALID_HANDLE. The ORACLE_HOME settings also look fine. Any ...

Hi ppl, I have a strange problem here. I have a job which aborts, but it does not throw any fatal error. When i look into the job log, everything runs fine, suddenly it gives "Attempting to cleanup after ABORT raised in ......". It usually gives this after a fatal error. But here we donot ...

I exported the jobs that i created in unix and imported them in windoze. Wondering where in the job there might be a hard reference to unix library files. Yes, i compiled the jobs before running them in windows. When i exported them a dsx file was created which i guess is a source file rather than a...

Also, Can you please tell me what are these ".so" files ? Should they be present in both windows and unix installation. I am moving from unix to windows installation. Can that be an issue ?? If so, what should be the right approach to get rid of the error

thanks

Hello ppl, I am getting the following error when I try to run any job with stored proc stage. Did anyone ever come across such an error. Any clues why it might be happening ? ds_loadlibrary: Win32 error in LoadLibrary of dsstp.so The development was done in datastage 7.5.1.A and subsequently moved t...