DSXchange

LOL @ Chulette I too have not been able to get a definitive answer to this 64/32 bit story but just so you know We have another server that was upgraded to AIX 6.1 / DS 8.1. It had the oracle 10G 32 bit client which did not work but as soon as we upgraded to oracle 10G 64 bit client things started w...

Chulett :

AIX 6.1 and DS 8.1 are supposed to be 64 bit. Are they not ? Are you saying that our sys admin might have upgraded our DS 7.5.1 to a 32 bit version of DS 8.1 ?

No. Oracle is on a different machine. I can tnsping from the datastage machine to oracle machine and I can also connect to oracle with sqlplus. I used the command below to confirm that we are using 64 bit client. dump -ah -X64 /app/product/oracle/DBBASE/11.2/lib/libclntsh.so Also, ODBC stage can vie...

Our old server configuration was this - Aix 5.3 Datastage 7.5.1 using Oracle 10G 32 bit client to connect to oracle 10G database. We just did an In-place upgrade to the below server configuration - AIX 6.1 Datastage 8.1 using oracle 11G 64 bit client to connect to oracle 11G database. After the upgr...

DataStage Designer appear to hang when it tries to display a stage using invalid screen coordinates. This will happen every time you try to open a particular kind of stage. The solution is to remove the saved screen coordinates from the Windows Registry. Close the Designer. Use regedit to delete thi...

We are getting a weird error in one of our parallel jobs. This is our setup AIX 5.3 Datastage 7.5 using oracle 10G or 11G client connecting to Oracle 11G database under 11G RAC. The job has a native oracle stage which is using the TABLE read method to read from a table (say TAB1). We are using the P...

I got it working. Datastage 7.5 using Oracle 11G client connecting to Oracle 11G database on 11G RAC on AIX 5.3 The slew of errors i was getting earlier (see my message above) was simply because the DBAs installed a 64 bit version of the oracle 11G client. We replaced it with the 32 bit version and ...

We tried with this setup first - Datastage 7.5 EE using Oracle 10G client to connect to Oracle 11G database under 11G RAC While we were able to connect and while it seemed to work fine for most part, one of our jobs aborted with this error - "Could not determine version of Oracle for which to p...

I started getting exactly these kind of compilation error messages in one of my parallel jobs after we migrated our 7.5 jobs to our 8.1 installation. Error when checking composite operator: Converting ustring to string using codepage ISO-8859-1. The only difference is that when our sys admins instal...

OK, I resolved....The OS was AIX 6.1 (64.bit) and IS 8.1 and XLC 10.1 so the 10.1 XLC plus adding the -q64 in this environemnt solved the issue. Thanks Could you please give me the details of the environmental variables. We were facing the same issue in the same environment as you have resolved on ...

Sorry - this is resolved. Pardon my stupidity.

We discovered that since you can have only one EXCEPTION HANDLER stage in one SEQUENCE job, when the job is open exception handler in the pallete will be grayed out.

We have a fresh datastage 8.1 installation with fixpack 8.1 In the SEQUENCE pallate everything else is available but EXCEPTION_HANDLER is grayed out. Any idea why ? Please note that a sequence that we migrated from 7.5 which has an exception handler in it compiles just fine. It's just that the stage...

ray.wurlod wrote:Use 191 (not Alt-191), ideally when importing the table definition from the Sequential File. ...

Thanks, this is working

Hi,

How to use extended ascii char 191 (┐) as a delimiter in sequential file stage.

I was trying to type ALT+191 as a delimiter but it is coming out as + which is not right.

Could someone share your thoughts on using this delimiter in parallel job.

Thanks

we are using change capture to find the new/update and deleted records. After the first run, it gave x number of records for insert and y number of records for update. We ran the update job which updates the records and load job which loads the new records. When we try to run the change capture job ...