dsjob: error while loading shared libraries: libvmdsapi.so: cannot open shared object file: No such file or directory

-

If you try to run the dsjob command you will get something like this: 

$ dsjob
dsjob: error while loading shared libraries: libvmdsapi.so: cannot open shared object file: No such file or directory

Presuming that you have selected the default path names during the installation of your server, the following will setup the environment: 



$ export DSHOME=/opt/IBM/InformationServer/Server/DSEngine
$ export PATH=$PATH:$DSHOME/bin:/opt/IBM/InformationServer/Server/PXEngine/bin
$ export APT_CONFIG_FILE=/opt/IBM/InformationServer/Server/Configurations/default.apt
$ . /$DSHOME/dsenv

You could even include the above into the  ~/.bashrc file so they are executed automatically





Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more