Art of BI: MDS or BIPLATFORM Schema Password Change Considerations

As you know the OBI 11g installation requires that the Repository Creation Utility (RCU) be run in advance to create a metadata repository for information used by OBI.  During the installation of the RCU and the creation of the database users/schemas a password (or multiple depending on your install configuration) is created for the MDS and BIPLATFORM schemas.

Perhaps unknown by most, this password(s) ultimately becomes coveted by the OBI 11g system.  What if one needs to change the initial passwords for one or both of these schemas?  How would a password change or expiration of that user/schema password impact the OBI 11g system?

Let’s just say that this whole concept of using a metadata schema to support an application is not a novel one. However, because this concept is new to those who love and have made their bacon working with OBI this may seem cumbersome.  Although we had all better just get used to it.  It’s going to be around for a while according to the Oracle roadmap for BI.

A need to change the password for either schema or if the password just happens to expire (default expiration is set of Oracle RDBMS 11g) can beget some unexpected results.  There real question becomes what will happen to my OBI 11g system? and then of course where do I go to reset the password aside form the RDBMS itself so that OBI 11g picks it up and behaves itself? Fortunately the resolution/process is straightforward.

Can the MDS or BIPLATFORM schema password be reset?

Yes, of course it can. After all it is just a user/schema in your RDBMS.  It may even get locked due to the password expiration default setting of the Oracle RDBMS 11g database if using that version.  But once you change this for any reason that is where the fun begins.  The password can be changed using the basic Oracle PL/SQL syntax for updating a user account identified by…yada yada yada.  But once this is done it actually causes issues with the WLS and OBI system’s ability to connect to those schemas.  I’m guessing some encryption had taking place during the installation and it gets disrupted or something like that.  Either way both the MDS schema required by Fusion Middleware Control (EM) and the BIPLATFORM schema that controls the OBI Agents, etc. gets hosed.

Impact of MDS or BIPLATFORM password reset

If one needs to adjust the password for these schemas or the password expires two things will happen.  First, the WebLogic Server (WLS) will startup but it will not start up properly. Viewing the start up logs one will notice an error stating that there is an invalid username/password as such the WLS cannot properly connect to the database.  This is the main culprit and should be rectified first (more on this below).  The second issue one will notice is a functional one that will show itself clearly in the OBI 11g fusion control enterprise manager (EM).  This has to do with the BI Scheduler service component.  One will notice that this will not start properly.  As a matter of fact it just won’t start.  In fact, it will may have an impact on other components such as the “Restart All” will not complete, etc.

The impact is clear and that nothing will work properly.


How-to Fix / Update the MDS schema password for OBI 11g?

Great question.  Here are the steps:

  1. Login to the Fusion Middleware Control (EM)
  2. Expand WebLogic Domain > bifoundation_domain
  3. Under the bifoundation_domain, expand the WebLogic Domain dropdown and select JDBC Data Sources
  4. Select mds-owsm from the list and click Edit
  5. Under the connection properties tab change the password and click the Apply button (upper right of form)
  6. Restart OBI Services

How-to Fix / Upate the BIPLATFORM schema password for OBI the 11g Scheduler?

Another good one friend.  Here are the steps:

  1. Login to the Fusion Middleware Control (EM)
  2. Expand Business Intelligence > coreapplication
  3. Click on the Deployment tab
  4. Click on the Scheduler tab
  5. Click the Lock & Edit Configuration button
  6. Once the option to edit the scheduler metadata becomes available enter the new password for the schema/user[simage=500,400,y,center]
  7. Click Apply
  8. Click Activate Changes
  9. Just restart the scheduler. Or, bounce OBI Services just to be ready and steady if so desired.

Other Possible OBI 11g Symptoms from this or similar password expiration/change

  • SampleApp MapViewer obiee_navteq schema will cause maps to not render
  • May impact Action Framework to some degree
  • Will impact Real-Time Decisions (RTD) if installed


Clearly dealing with security constraints in OBI 11g becomes a new factor of your designated OBI Administrator. It is an extra task that I am sure one could do without.  However, this blog showed a quick approach to getting the core OBI 11g system back up and running in case this is a situation one gets placed into.  There are several other areas that require updating the password for in case the DB user password is changed at any point in time.  I left this post for the core pieces so that your EM capacity tab shows nothing but green up arrows.  I hope you found it useful.

Contact Us
Christian Screen
Christian is an innovator in analytics and data warehousing design, best practices, and delivery. With more than fifteenyears of decision support and data warehousing with key experiences at Office Depot HQ, Sierra-Cedar, and Capgemini, he oversees the Oracle Analytics Practice which includes the technical development and delivery of Oracle BI collaboration software, data warehouse solutions, Oracle BI/EPM projects, and packaged analytics solutions at Datavail.

Leave a Reply

Your email address will not be published.
Required fields are marked (*).

20 thoughts on “Art of BI: MDS or BIPLATFORM Schema Password Change Considerations”
    1. Mohamed,
      You should be able to to see the steps and a few screenshots. Not every step doesn’t have a screenshot in the post only a handful.


  1. Hi,
    Can you guide me how to change the password , when presentation service and scheduler is down.?

    I already made change from weblogin console.

    but when i try to start presentation service, “dev_biplatform”schema gets locked.


    1. If dev_biplatform is locked you need to unlock that via pl/sql using sqlplus, toad, sqldeveloper or the like.

      1. Yes thats take care. But matter is , while opmn is started from some where wrong password is send to the db and accouts gets locked.nSince console laos not comign up I cant change from midle tire logins.nnSo am looking if any option to change in any middle tire file from backend.n

      2. Hi Knpn,
        Did you find a solution? I am having the same problem. The database account is resolved but I keep locking it when I go into WebLogic.

      3. I think he describes the solution up above. The scenario plays out like this… you change the data source in /console, and the schema password in the database. But after a restart, the obisch1 is locked.
        From /em, go to the Deployment tab of the coreapplication and change the xxx_BIPLATFORM password there. And make sure to unlock the database account, if locked, before restarting the opmnctl service.

      4. Yes thats take care. But matter is , while opmn is started from some where wrong password is send to the db and accouts gets locked.nSince console laos not comign up I cant change from midle tire logins.nnSo am looking if any option to change in any middle tire file from backend.n

  2. You say “There are several other areas that require updating the password for in case the DB user password is changed at any point in time.” Any pointers on finding the other areas? I am a new OBI Admin… Thanks!

    1. Tropical,

      Yes, the other places to check are any of the JDBC connections that are created via the WebLogic Server Admin Console. Open the WLS Admin Console and from the left menu Select Services > Data Sources. You my need to Lock & Edit to make the appropriate changes but each of the JDBC data source listed will need to be assessed in order to ensure that all connections for all OBIEE components are being made successfully.

  3. Is it possible to script these password changes using WLST? I’m going to need to do this routinely and would prefer to automate it.


    1. Jerry
      You can definitely script this operation. You can use wlst to do both operations. I’ll see if I can post some code later this week.

      1. That would be great. This must be well hidden. I searched through the MBeans and couldn’t find one for these passwords. I found the MDS jdbc connection info, but it didn’t include the password. I couldn’t find the BIPLATFORM jdbc info at all.

        I found the MBean that represents the LDAP schema definitions for the Active Directory LDAP Authentication provider. This includes the password for connecting to AD, so I think changing that can be scripted with WLST.



  4. Hi,

    I hope you can help me with this… In the JDBC Data Sources (EM), I cannot select and edit the mds-owsm. I think the problem is everytime I try to select the mds-owsm the page refreshes.

    Thank you very much.


  5. Hi,

    am getting this error msg :
    “Error occurred while updating the JDBC data source “mds-owsm”.
    The domain configuration has been locked by another administration tool or
    user. Retry after making sure that the lock is released. In most cases, you.”
    even after unlocking the ” Dev_Biplatform and DEV_MDS ” users at db level, after doing this BIScheduler is up but still not able login analytics page.

    1. So, since you cleared the lock it appears that the password update was successful, correct? However, what error message are you getting now that is preventing the login to the OBI portal?

    1. Andrew,
      There are no issues with using different passwords for the two OBIEE 11g RCU Schemas.
      Your #2, about the same password or all schemas, the link mentions issues during the installation. It says nothing about after the installation and then you change or modify the passwords post-installation. I don’t believe that the pros at Oracle would have some referring logic that would store the passwords inside the schemas and make some later reference to a changed password that should only reside at the database level. So for that reason I’m going to say that you should be good. Either check the box and use the same password or uncheck the box and use different passwords at installation. I now for a fact that changing the passwords of either schema post-installation does not cause any problems. But as stated in the post or elsewhere in the blog you have some other areas of Oracle BI where you’ll need to reconfigure with the updated passwords.