DSXchange

Thank you for responding.

Since we are using CDC and it connects using only odbc driver we have no other option.
As a final option I will open a Case with IBM. Will keep you all posted.

Thanks for responding.

We are using odbc.ini to connect to oracle . Since CDC uses only odbc driver.

I think its time to contact official support.

Two questions: (Information Server 9.1.2 on AIX) 1) Does Oracle ODBC driver have an alternative server mechanism? We have two Oracle databases and (A and B) and we want to connect to Oracle database B when Oracle database A fails, using ODBC driver. 2) Does CDC transaction stage uses only ODBC drive...

So we have QSAVI DB files placed on all compute nodes with 777 .
gave 777 -R to QSAVI in DSComponent directory .
Ran job with APT_GRID_ENABLE=NO job log has same warning messages , Ran job with APT_GRID_ENABLE=YES job log has same warning messages.

opened a service ticket . support said its not worth involving engineering on this warning message .
it is seen on all machines where AVI is installed in GRID environment.
so suggested to suppress the warning message .

I have changed few permissions on lib's and it worked.
however I get Resource bundle correspoding to message key DSEE-AVIF not found. check that DSHOME or APT_RESPATH is set .

DSXImportservice.sh script is import dsjobs .
but this script is importing env var along with the job and assigning $PROJDEF value to them.

how to get right of it .Is there any flag that I can use in the syntax ?

did any one setup AVI on Grid environment ?

We have installed AVI ,it is working fine in non grid but fails wen grid is enabled.

can I run UpdateSignerCerts.sh|bat command and give -auth file option.
As I dont want to share password to sysadmin team.

is this connector failure have to do with kernel limits ?

I am seeing these files on compute nodes (server2)also ..
where my scratch disk is located . ..

And my engine is located on conductor node server 1.

I have tried with a job having a connector stage and by killing the job in the middle of execution but could not generate these files .

these logs have info about hostname , ports ,dsd.run and connections established and wait state So basically it has lot of information about the server. After lot of research I figured when a datastage job is initiated and failed abruptly then these logs are generated. If you have more info pls share.

In my DataStage environment under /tmp is px.connect.fail#### files I see them on few of my remote servers where datastage scratch disk is mounted (nfs) . I am assuming some connection fail while accessing scratch disk and this is generating these logs.. Did any one see such files in your servers ? ...

I still dont have access to those logs . I will post here once I take a look.

in user history may be I should be able to try that .

I will keep you posted.
Thanks .