IMAM error CDIMR4650E occurs when try to create new import area

-

Problem(Abstract)

While trying to create a new import area using InfoSphere Metadata Asset Manager (IMAM) console, user gets error: 

[CDIMR4650E] Failed to retrieve the value of the 'allowShareHistoryDeletion' property.

followed by exception string that shows a password failure.

Symptom

Additional errors shown at failure time may include: 
com.ibm.iis.xmeta.client.exception.ServiceException: Error initializing repository
or
com.ibm.iis.xmeta.client.exception.ServiceException: Error calling client method getAllBridgeServers 

Caused by:
[IBM][Oracle JDBC Driver][Oracle]ORA-01017: invalid username/password; logon denied
DSRA0010E: SQL State = 28000, Eror Code = 1,017


Cause

Information Server has two repository userids, xmeta and xmetasr. The xmetasr userid is used to access staging area schema in our metadata repository. It is possible for users to still be able to login if xmeta password remains valid, but functions which need access to staging area of repository need to access xmetasr schema and thus will fail if the xmetasr password has expired.

Resolving the problem

Run AppServerAdmin script with -dbs option to change the xmetasr credentials: (as opposed to the -db option used to change xmeta credentials). 



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