Error deleting datasets
Moderators: chulett, rschirm, roy
Error deleting datasets
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].
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].
Last edited by kumar11 on Tue Sep 20, 2016 2:41 pm, edited 2 times in total.
It looks like you have not sourced the "dsenv" file, or that the path to the orchadmin command is not part of your $PATH.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Thanks ArndW
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.
/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.
Actually:
Code: Select all
. ./dsenv
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
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.
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.
You can also delete datasets by invoking Data Set Management utility in either DataStage Designer or Director client.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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*
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*