Page 1 of 1

Datastage strange behaviour

Posted: Fri Jan 15, 2010 3:18 am
by arnie_nits
Hi,

I am facing a strange problem.

The source stages doesnot open. When I double click on the databasestages the nothing happens. And then when I close the job,it ask "Do you want to save". Then when I close Datastage I get an error like:

The instruction at "0x6c3ebd5c" reference memory at "0x01c041d4". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

Please suggest.

Regards,
Arnie.

Posted: Fri Jan 15, 2010 3:27 am
by Sainath.Srinivasan
Did you have the job / object open for quite some time ?

Is your DataStage server down ?

Was there any network issues ?

Did you have quite loads of programs open at same time ?

Posted: Fri Jan 15, 2010 3:36 am
by arnie_nits
1. No I restart the system often.

2. No . From another system I was able to open the source stages of same jobs.

3. No network issue.

4. I checked that. With no programs open I was getting the issue.

Also I re-installed DS. Still the same problem.

I use DRS staged in server and there I get the problem.
I am not getting the problem in ODBC stage in parallel.

I am able to open the target stages. The problem is with only the source stages.

Regards,
Arnie.

Posted: Fri Jan 15, 2010 4:41 am
by ArndW
Often this type of problem can occur from incorrect DLLs in the DataStage client software and a re-installation can solve the problem. In many installations software updates are automatically applied and they can, occasionally, overwrite libraries with older/newer versions than what DataStage expects and thus causes issues.

Posted: Fri Jan 15, 2010 5:46 am
by arnie_nits
I have re-installed DS twice now. Still the same problem.

Regards,
Arnie

Posted: Fri Jan 15, 2010 6:10 am
by arnie_nits
I have re-installed DS twice now. Still the same problem.

Regards,
Arnie

Re: Datastage strange behaviour

Posted: Fri Jan 15, 2010 6:47 am
by J.Calvo
Any Java Update recently? In some versions this problem appears with java updates , the solution is uninstall java update or apply some patches.
arnie_nits wrote:Hi,

I am facing a strange problem.

The source stages doesnot open. When I double click on the databasestages the nothing happens. And then when I close the job,it ask "Do you want to save". Then when I close Datastage I get an error like:

The instruction at "0x6c3ebd5c" reference memory at "0x01c041d4". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

Please suggest.

Regards,
Arnie.

Posted: Fri Jan 15, 2010 10:53 am
by arnie_nits
Well no Java..but do have .Net installed. Is that the problem??

Regards,
Arnie

Posted: Fri Jan 15, 2010 11:11 am
by chulett
Hard to say but I doubt it. You need .Net for the client and multiple versions don't conflict with each other, from what I've read.

Posted: Wed Jan 20, 2010 10:03 am
by arnie_nits
I tried a lot by re-installing many times.

Someone please suggest. Hasn't anyone faced this problem before?


Thanks and regards,
Arnie.

Posted: Wed Jan 20, 2010 11:00 am
by chulett
Nope. Somewhat similar issues but not that one.

Is this problem specific to you / your PC or do others have the same issue with the same stages? Assuming the former, I would recommend you reinstall the DataStage client one more time, this time with 'extreme prejudice' as they say:

1. Uninstall the software.
2. Remove every last trace of the Ascential directories from your drive.
3. Use "regedit" to find and nuke every mention of "Ascential" from the registry.
4. Reboot.
5. Re-install the client.

I would guess you didn't do it this way before, hence the suggestion and its done the trick for many peoples. And if you've never used "regedit" or aren't that familiar with the Windows Registry, get some help from someone who is. Improper usage of it could end you up with a PC that no workie no more. :wink:

Posted: Thu Jan 21, 2010 10:34 am
by Abhijeet1980
Kindly refer the DataStage documentation before installation of the clients.

Also, check for the correct version (patches for Windows). As suggested by our colleague, make sure that your registry entries are removed before the installation.

That should take care of the problem.

Many regards,
Abhijit Gaikwad