BIApps Version 11.1.1.7.160719 - ODI repository Password Change

Mahesh25

Hi All,

We are using BIApps Version 11.1.1.7.160719, which comes with ODI.

Currently we want to Change password of ODI repository Schema from Database .

I wanted to know where all i need to change the updated password ?

I Know for for sure I would need to change it in ODI connection in Topology, but I am not sure about other places.

I tried to find out for the same but could not get any documentation of link.

As we can generate Load plans from BIACM, we should have connection details there, but not able to find the same.

Any help regarding this would be appreciated.

Thanks,

Mahesh

Charles M

Hi Mahesh,

You will certainly need to make changes from the WebLogic Admin Console. For example, find your data sources for the ODI repository(ies) [Home >bifoundation_domain >Summary of JDBC Data Sources > odiMasterRepository | Home >bifoundation_domain >Summary of JDBC Data Sources >odiWorkRepository]. Locate the 'Connection Pool' tab, under 'Configuration'. You can change them there (don't forget to "lock & edit" before making the changes).

Also, you need to make the change(s) within the database itself prior to doing the above and enusre the OBI services are down (e.g. opmnctl stopall). Possibly, you may need to bring the ODI manged server down as well ... not sure about that off-hand.

ALTER USER {repo_user} IDENTIFIED BY {yourpassword};

There are some notes related to this, but contain additional steps for other accounts/tasks. For example, OBIA 11g: How to change the system account passwords in BI Applications (Doc ID 2264922.1), OBIA 11g: How to Change BI Applications System Account Passwords (Doc ID 1613764.1).

How To Update OBIEE 11g Configuration When The Repository (RCU) Schemas Have Changed (Doc ID 1307835.1) <<< Illustrations for the WebLogic steps. Keep in mind these are for another account ...

Let me know how it goes. If something becomes locked after you change the DB account, it will find its way to one of the logs. Do this in your Dev instance first.

Regards,

Charles