Document toolboxDocument toolbox

Workbench operations return ‘Could not find specified assets’

Symptom

Running compliance or Git Commit in MettleCI Workbench returns a Could not find specified assets error, despite the user specifying the name of a valid Asset within the selected Project.

Diagnosis

From a shell on the DataStage Engine hosting the MettleCI Workbench Service execute an istool command to perform an export of your selected asset using the same user account used to execute MettleCI Workbench (typically mciworkb).

For example…

/opt/IBM/InformationServer/Clients/istools/cli/istool.sh export -domain myhost.myorganization.com:9443 -username myusername -password mypassword -archive "/tmp/myexport.isx" -datastage ' -base="myhost.myorganization.com/myproject" "/myjob." '

If you observe that the export file has not been created, despite the istool export command running with no error message, it’s likely you have found the reason for the Workbench error.

Cause

MettleCI uses DataStage’s native export capabilities to extract the required asset(s) from the repository tier. Without a working istool - and hence access to the DataStage assets - MettleCI cannot successfully complete the requested operation.

Solution

See IBM’s technote on this topic which describes the problem and its solution: https://www.ibm.com/support/pages/infosphere-information-server-manager-and-istool-command-may-encounter-errors-after-applying-jr55455 . Note that JR55455 might have been applied to your Information Server system as a by-product of installing an Information Server fix pack or service pack.

© 2015-2024 Data Migrators Pty Ltd.