Projects in InformationAnalyser are not showing in DQEC

-
​

Problem

Projects in InformationAnalyser are not showing in DQEC and also the exception are not showing.

Resolving the problem

Rebuilding the index

Follow the steps listed below to rebuild exception set index by using the reindex REST API method for the InfoSphere Data Quality Exception Console:

1. Close all browser instances.

2. Open a new browser.

3. Enter the URL that corresponds tor the eindex REST API method for the InfoSphere Data Quality Exception Console in the following format:

https://<server>:<port>/ibm/iis/dqec/rest/reindex.

For example. if the server is local ("localhost") and the port is 9443, then the "reindex" URL will be:

https://localhost:9443/ibm/iis/dqec/rest/reindex

4. Enter your user credentials for a user that has the Exception Management Administrator role.

Note: If the user doesn't have the proper role, the following error message is displayed:

"The user was not authorized to perform the requested operation."

4) When the re-indexing is finished, the following message is displayed:

"Successfully re-indexed all exception sets."

5) Close the browser to log out.

Clearing the index data

If the re-index fails to complete, follow these steps to clear the index data:

1. Shutdown InfoSphere Information Server.

2. Manually clear the index by deleting all files and folders in the index "data" folder,

Note: The index data folder is different from the data folder. Be sure to delete only the files and subfolders in the index data folder:

WebSphere Application Server Liberty profile:

<install folder>\ASBServer\bin\EMC\emc_solr\emc\data

3) Restart IBM InfoSphere Information Server.

4) Repeat the steps to rebuild the index.







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