Page 1 of 1
Qualitystage job getting aborted with qsavop error
Posted: Thu Dec 04, 2014 10:02 am
by arvind_ds
Hello Experts,
One of the quality stage job containing Address verification stage is getting aborted with below error.
main_program: PATH search failure: [sil/step_il.C:1329]
main_program: Could not locate operator definition, wrapper, or Unix command for "qsavop"; please check that all needed libraries are preloaded, and check the PATH for the wrappers [sil/step_il.C:622]
main_program: Operator qsavop does not exist in the registry. [api/opreg.C:259]
main_program: Creation of a step finished with status = FAILED. [osh.C:977]
Any help on the resolution of the above issue is much appreciated. Many thanks.
Posted: Thu Dec 04, 2014 12:05 pm
by priyadarshikunal
Did you check if the PATH and LD_LIBRARY_PATH variables is set correctly?
Posted: Thu Dec 04, 2014 1:43 pm
by ray.wurlod
PATH in particular, as specified in the error message itself.
Posted: Thu Dec 04, 2014 6:48 pm
by qt_ky
Did it just break recently? Is it a new setup that's never worked yet? Is it working on another server?
Posted: Fri Dec 05, 2014 2:42 am
by arvind_ds
PATH & LD_LIBRARY_PATH, both are setup correctly. The job in question here, worked fine earlier in the same environment around 6 months back. We did not make any specific changes in the environment, so just wondering why the job is failing when it is executed after a gap of 6 months. Its happening in DEV environment, we have not moved it to higher environments yet.
>. ./dsenv
> echo $PATH
/var/lsf/9.1/linux2.6-glibc2.3-x86_64/etc:/var/lsf/9.1/linux2.6-glibc2.3-x86_64/bin:/opt/IBM/InformationServer/Server/PXEngine/grid_enabled.4.3.3:/opt/IBM/InformationServer/ASBNode/apps/jre/bin:/opt/IBM/InformationServer/Server/PXEngine/grid_enabled.4.3.3:/opt/IBM/InformationServer/ASBNode/apps/jre/bin:/opt/IBM/InformationServer/Server/PXEngine/grid_enabled.4.3.3:/opt/IBM/InformationServer/ASBNode/apps/jre/bin:/opt/teradata/client/14.00/tbuild/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/opt/quest/bin:/opt/IBM/InformationServer/Server/DSEngine:/opt/IBM/InformationServer/Server/DSEngine/bin:/opt/IBM/InformationServer/Server/PXEngine/bin:/opt/IBM/InformationServer/Server/DSEngine/../../ASBNode/bin:/opt/IBM/loadl/bin::/opt/IBM/InformationServer/Server/DSEngine/../../Clients/istools/cli:.:/opt/teradata/client/14.00/bin:/opt/ibm/db2/V10.1/bin:/db2/db2inst1/sqllib/bin::/opt/ibm/db2/V10.1/lib:/db2/db2inst1/sqllib/adm:/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/var/opt/oracle/app/product/11.2.0/client_1/bin:/var/opt/oracle/app/product/11.2.0/client_1/nls/data:/opt/mqm/bin:/opt/IBM/SAPHANA:.:/opt/IBM/DS_FUNCTIONS:/opt/IBM/DS_QS_LIBS:/opt/IBM/home/lsfadm/9.1/linux2.6-glibc2.3-x86_64/bin:/opt/IBM/InformationServer/Server/DSEngine:/opt/IBM/InformationServer/Server/DSEngine/bin:/opt/IBM/InformationServer/Server/PXEngine/bin:/opt/IBM/InformationServer/Server/DSEngine/../../ASBNode/bin:/opt/IBM/loadl/bin::/opt/IBM/InformationServer/Server/DSEngine/../../Clients/istools/cli:.:/opt/teradata/client/14.00/bin:/opt/ibm/db2/V10.1/bin:/db2/db2inst1/sqllib/bin::/opt/ibm/db2/V10.1/lib:/db2/db2inst1/sqllib/adm:/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/var/opt/oracle/app/product/11.2.0/client_1/bin:/var/opt/oracle/app/product/11.2.0/client_1/nls/data:/opt/mqm/bin:/opt/IBM/SAPHANA:.:/opt/IBM/DS_FUNCTIONS:/opt/IBM/DS_QS_LIBS:/opt/IBM/home/lsfadm/9.1/linux2.6-glibc2.3-x86_64/bin:/opt/IBM/InformationServer/Server/DSEngine:/opt/IBM/InformationServer/Server/DSEngine/bin:/opt/IBM/InformationServer/Server/PXEngine/bin:/opt/IBM/InformationServer/Server/DSEngine/../../ASBNode/bin:/opt/IBM/loadl/bin::/opt/IBM/InformationServer/Server/DSEngine/../../Clients/istools/cli:.:/opt/teradata/client/14.00/bin:/opt/ibm/db2/V10.1/bin:/db2/db2inst1/sqllib/bin::/opt/ibm/db2/V10.1/lib:/db2/db2inst1/sqllib/adm:/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/var/opt/oracle/app/product/11.2.0/client_1/bin:/var/opt/oracle/app/product/11.2.0/client_1/nls/data:/opt/mqm/bin:/opt/IBM/SAPHANA:.:/opt/IBM/DS_FUNCTIONS:/opt/IBM/DS_QS_LIBS:/opt/IBM/home/lsfadm/9.1/linux2.6-glibc2.3-x86_64/bin
> echo $LD_LIBRARY_PATH
/opt/IBM/InformationServer/Server/branded_odbc/lib:/opt/IBM/InformationServer/Server/DSComponents/lib:/opt/IBM/InformationServer/Server/DSComponents/bin:/opt/IBM/InformationServer/Server/DSEngine/lib:/opt/IBM/InformationServer/Server/DSEngine/uvdlls:/opt/IBM/InformationServer/Server/PXEngine/lib:/opt/IBM/InformationServer/ASBNode/apps/jre/bin:/opt/IBM/InformationServer/ASBNode/apps/jre/bin/classic:/opt/IBM/InformationServer/ASBNode/lib/cpp:/opt/IBM/InformationServer/ASBNode/apps/proxy/cpp/linux-all-x86_64:/opt/IBM/InformationServer/Server/branded_odbc/lib:/opt/IBM/InformationServer/Server/DSComponents/lib:/opt/IBM/InformationServer/Server/DSComponents/bin:/opt/IBM/InformationServer/Server/DSEngine/lib:/opt/IBM/InformationServer/Server/DSEngine/uvdlls:/opt/IBM/InformationServer/Server/PXEngine/lib:/opt/IBM/InformationServer/ASBNode/apps/jre/bin:/opt/IBM/InformationServer/ASBNode/apps/jre/bin/classic:/opt/IBM/InformationServer/ASBNode/lib/cpp:/opt/IBM/InformationServer/ASBNode/apps/proxy/cpp/linux-all-x86_64:/var/lsf/9.1/linux2.6-glibc2.3-x86_64/lib:/opt/IBM/InformationServer/Server/branded_odbc/lib:/opt/IBM/InformationServer/Server/DSComponents/lib:/opt/IBM/InformationServer/Server/DSComponents/bin:/opt/IBM/InformationServer/Server/DSEngine/lib:/opt/IBM/InformationServer/Server/DSEngine/uvdlls:/opt/IBM/InformationServer/Server/PXEngine/lib:/opt/IBM/InformationServer/ASBNode/apps/jre/bin:/opt/IBM/InformationServer/ASBNode/apps/jre/bin/classic:/opt/IBM/InformationServer/ASBNode/lib/cpp:/opt/IBM/InformationServer/ASBNode/apps/proxy/cpp/linux-all-x86_64:/opt/teradata/client/14.00/lib:/opt/teradata/client/14.00/tbuild/lib:/usr/lib:/opt/teradata/client/14.00/lib64:/opt/teradata/client/14.00/tbuild/lib64::/opt/ibm/db2/V10.1/lib64:/opt/ibm/db2/V10.1/lib32:/db2/db2inst1/sqllib/lib:/home/db2inst1/sqllib/lib:/opt/IBM/InformationServer/Server/branded_odbc/lib::/var/opt/oracle/app/product/11.2.0/client_1:/var/opt/oracle/app/product/11.2.0/client_1/lib:/var/opt/oracle/app/product/11.2.0/client_1/network/lib:/var/opt/oracle/app/product/11.2.0/client_1/nls/data::/opt/mqm/lib64:/opt/IBM/SAPHANA:.:/opt/IBM/DS_FUNCTIONS:/opt/IBM/DS_QS_LIBS:/opt/teradata/client/14.00/lib64:/opt/teradata/client/14.00/tbuild/lib64::/opt/ibm/db2/V10.1/lib64:/opt/ibm/db2/V10.1/lib32:/db2/db2inst1/sqllib/lib:/home/db2inst1/sqllib/lib:/opt/IBM/InformationServer/Server/branded_odbc/lib::/var/opt/oracle/app/product/11.2.0/client_1:/var/opt/oracle/app/product/11.2.0/client_1/lib:/var/opt/oracle/app/product/11.2.0/client_1/network/lib:/var/opt/oracle/app/product/11.2.0/client_1/nls/data::/opt/mqm/lib64:/opt/IBM/SAPHANA:.:/opt/IBM/DS_FUNCTIONS:/opt/IBM/DS_QS_LIBS:/opt/teradata/client/14.00/lib64:/opt/teradata/client/14.00/tbuild/lib64::/opt/ibm/db2/V10.1/lib64:/opt/ibm/db2/V10.1/lib32:/db2/db2inst1/sqllib/lib:/home/db2inst1/sqllib/lib:/opt/IBM/InformationServer/Server/branded_odbc/lib::/var/opt/oracle/app/product/11.2.0/client_1:/var/opt/oracle/app/product/11.2.0/client_1/lib:/var/opt/oracle/app/product/11.2.0/client_1/network/lib:/var/opt/oracle/app/product/11.2.0/client_1/nls/data::/opt/mqm/lib64:/opt/IBM/SAPHANA:.:/opt/IBM/DS_FUNCTIONS:/opt/IBM/DS_QS_LIBS
Posted: Fri Dec 05, 2014 6:25 am
by qt_ky
There were significant AVI module changes between Q2 and Q3.
The interface changed, I think on client and server (definitely on server side).
There was a Q3 update package (*.ispkg file) to apply.
Of course the reference data changed, and it also appears
that the its file format changed as well.
I would guess that something got missed and may be out of sync.
Make sure the update package is applied everywhere it needs to be.