Informix DB Connect Issue

senthilt1 · Post by **senthilt1** » Thu Jan 29, 2009 2:33 am

HI,

I tried to connect the informix database through parallel jobs,

When i view/run the job it gives the below error

##I TUTL 000031 16:33:37(001) <main_program> The open files limit is 4096; raising to 8192.
##I TOSH 000002 16:33:37(002) <main_program> orchgeneral: loaded
##I TOSH 000002 16:33:37(003) <main_program> orchsort: loaded
##I TOSH 000002 16:33:37(004) <main_program> orchstats: loaded
##I TFSC 000001 16:33:37(005) <main_program> APT configuration file: /ascential/dsadm/Ascential/DataStage/Configurations/default.apt
##W TCOS 000049 16:33:40(000) <main_program> Parameter specified but not used in flow: _APT_CONFIG_FILE
##W TCOS 000049 16:33:40(001) <main_program> Parameter specified but not used in flow: DSProjectMapName
>##E TOSH 000205 16:33:41(000) <main_program> PATH search failure:
>##E TOSH 000000 16:33:41(001) <main_program> Could not locate operator definition, wrapper, or Unix command for "infxread"; please check that all needed libraries are preloaded, and check the PATH for the wrappers
##W TOSH 000004 16:33:41(002) <main_program> Operator infxread does not exist in the registry.
>##E TCOS 000029 16:33:41(003) <main_program> Creation of step finished with status = FAILED

Please let me know what needs to be done on this..

Thanks,
senthil Kumar P

ray.wurlod · Post by **ray.wurlod** » Thu Jan 29, 2009 3:18 am

Start by correcting anything with a ##E token.

Also ensure that your APT_CONFIG_FILE environment variable contains the pathname of a valid configuration file (use the Configurations editor to check the file's validity).

senthilt1 · Post by **senthilt1** » Thu Jan 29, 2009 3:47 am

Thanks Ray,

The configuratuion file used is the default one which is working fine for the job having file to file load. But the same is not working for connecting the Informix DB.

Apart from config file is there anything that we have look at for the Informix connection...

Thanks,

Senthil Kumar P

ray.wurlod · Post by **ray.wurlod** » Thu Jan 29, 2009 3:09 pm

Any DB2 client executable whose directory needs to be in PATH or LD_LIBRARY_PATH and isn't.

Verify that all required DB2-related information - especially environment variables - are being correctly set in the dsenv script.