DSXchange

Hi,
when trying to delete the datasets on the box getting the below error:

/opt/IBM/InformationServer/Server/PXEngine> in/orchadmin delete /mi/dev1/datastage/stage/xxxxx.ds <
Could not load program /opt/IBM/InformationServer/Server/PXEngine/bin/orchadmin:
Symbol resolution failed for /opt/IBM/InformationServer/Server/PXEngine/lib/liborchcoreaix64.so because:
Symbol __dl__Q2_6icu_507UMemoryFPv (number 160) is not exported from dependent
module /opt/IBM/TWA/TWS/bin/libicuuc.a[libicuuc.so].
Symbol u_errorName_50 (number 161) is not exported from dependent
module /opt/IBM/TWA/TWS/bin/libicuuc.a[libicuuc.so].
Symbol u_setDataDirectory_50 (number 162) is not exported from dependent
module /opt/IBM/TWA/TWS/bin/libicuuc.a[libicuuc.so].
Symbol u_strlen_50 (number 163) is not exported from dependent
module /opt/IBM/TWA/TWS/bin/libicuuc.a[libicuuc.so].

It looks like you have not sourced the "dsenv" file, or that the path to the orchadmin command is not part of your $PATH.

Tried sourcing dsenv and updating the $PATH. but still the below error persists.

/opt/IBM/InformationServer/Server/PXEngine/bin/orchadmin delete /mi/dev1/datastage/xxxxxx.ds
Could not load program /opt/IBM/InformationServer/Server/PXEngine/bin/orchadmin:
Dependent module liborchgeneralaix64.so could not be loaded.
Could not load module liborchgeneralaix64.so.

Just for grins, can you confirm for us what your understanding of "sourcing dsenv" means?

./dsenv

Actually:

Thanks Chulett!!
now it gives a different error.

$ . ./dsenv
$ /opt/IBM/InformationServer/Server/PXEngine/bin/orchadmin delete /mi/dev1/datastage/stage/xxxxx.ds
##E IIS-DSEE-TFPA-00021 $APT_CONFIG_FILE was not set, and config.apt was not found in the working directory or in $APT_ORCHHOME/etc.
##F IIS-DSEE-TFCF-00009 Fatal Error: Cannot continue without a configuration file.

This technote will help you.

You can also delete datasets by invoking Data Set Management utility in either DataStage Designer or Director client.

I changed your initial post's subject to something more problem specific, not sure why you felt the need to edit it and change it back to something so... generic.

Both APT_CONFIG_FILE and APT_ORCHHOME need to be set. Verify that they are set in your dsenv script and that you are correctly sourcing that script.

Thanks All !!!

Able to resolve the issue after adding the APT_CONFIG_FILE and APT_ORCHHOME in dsenv file.

If your environment is hosting multiple projects, you should not set APT_CONFIG_FILE in dsenv. maybe make a wrapper script for that project so as to target a specific config file.

On a delete, it really doesn't matter that a config file be of that project, any VALID config file will do since the delete process will use the imbedded apt file in the descriptor.

But... I would still avoid putting a default APT in the dsenv.

*drops two cents*