Exception Sets are not displayed in the Data Quality Exception Console

-

Technote (troubleshooting)


Problem(Abstract)

Exception Sets are not displayed in the Data Quality Exception Console.

Cause

The IBM InfoSphere Information Server Suite Installer did not set the required configuration key that references the index location.

Diagnosing the problem

Server logs contain error messages or stack traces that indicate initialization failures while loading configuration data.

Resolving the problem

Follow the steps listed below to set the required configuration key.

1. Enter the iisAdmin command to set the key and value:

Unix

<IS installation dir>/ASBServer/bin/iisAdmin.sh -set -key com.ibm.iis.emc.search.index.home -value <IS installation dir>/ASBServer/bin/EMC/emc_solr

Windows (Only required when not installed in C:\IBM\InformationServer)

<IS installation dir>\ASBServer\bin\iisAdmin.bat -set -key com.ibm.iis.emc.search.index.home -value <IS installation dir>\ASBServer\bin\EMC\emc_solr

2. Restart the application server.

3. Rebuild the exception set index. See How to rebulid the exception set index.

Related information

How to rebuild the exception set index

Product Alias/Synonym

DQEC







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