DSXchange

HI All,

Thanks for your suggestions. I will look into these and get back to you.

I am facing this problem in Server Jobs Datastage 5.2.

Sorry for mentioning Server Datastage 7

Regards
Sreenivasulu

HI All, The Datastage server is running slow because of a particular design. Earlier we had a non-multi instance datastage job calling a multinstance job. Now we changed the application design to multi-instance datastage job calling another multi-instance job. This causes the number of dsapi in the ...

Hints work. I have used no_merge hint using user-defined sql

Regards
Sreenivasulu

I also found a similar problem in nested sequence restartability.

Would try to get info from Datastage product support guys.

Regards
Sreenivasulu

Great going...

Hi, We are getting following error in production. Can any one help in identifying the problem, Program "*DataStage*DSR_LOADSTRING": Line 114, WARNING: Internal file corruption detected during file open! File must be repaired, possible truncation. hsize: 2048 bsize: 2048 fsize: 5877529 Prog...

I believe all dsx files can be viewed as txt file where an automated find/replace could work.

Regards
Sreenivasulu

HI

You can keep the sql as it is "SELECT * FROM PGM WHERE PGM.PGM_S_ID=:1 " but uncheck the checkbox for "Pre 4.2 user-defined sql". Then compile. By default this checkbox gets checked.

I tried this way once.

Regards
Sreenivasulu

HI,

Put "Set AutoCommit On" before the sql statement. This would help in applying for the current session.

Regards
Sreeni

HI All,

I am about to buy a machine with Windows NT on AMD since this would be cheaper that a windows NT on Intel.

Would i face any issues in datastage installtion with the AMD processor ?

Regards
Sreeni

Installation of Datastage 7 in Windows XP is not working. The client
is also not getting installed. Any workaround.

Hi Akhlin

Can you tell the full form of DRS stage which you are referring to ?
I was answering based on the assumption that you were using OCI stage for lookup

Regards
Sreeni

HI Chullet,

Actually i fixed one such issue which gave a error "illegal name/variable"
and i did this. It worked wonders

Regards
Sreeni

In the lookup stage. Uncheck "Pre 4.2 User defined Sql" and compile.
By default this gets checked hence you have to uncheck deliberately.

Regards
Sreeni

Plus you need to put the COMMIT if the transaction paramters are not set

Regards
Sreeni