Skip to content
June 1, 2013 / Tiago Epifânio

OBIEE: MDS or BIPLATFORM password invalid

I recently had this problem with a development server. I had to restart the BI services and they just wouldn’t come back to life. HNMCNTHMVWVF

Looking at the Log files in the Enterprise Manager I found this error message:

oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load MDS configuration document    
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "MAR_TargetRepos" is invalid.    
MDS-01376: Unable to get database connection from data source "mds-owsm" configured with JNDI name "jdbc/mds/owsm".     
weblogic.common.resourcepool.ResourceDeadException: 0:
 Could not connect to 'oracle.jdbc.OracleDriver'.

 The returned message is: ORA-01017: invalid username/password; logon denied

 It is likely that the login or password is not valid.
 It is also possible that something else is invalid in
 the configuration or that the database is not available.

at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:733)
at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:204)
at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)
at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:77)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:283)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.StartOperation.createAndPrepareContainer(StartOperation.java:85)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doPrepare(StartOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document    
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "MAR_TargetRepos" is invalid.    
MDS-01376: Unable to get database connection from data source "mds-owsm" configured with JNDI name "jdbc/mds/owsm".     
weblogic.common.resourcepool.ResourceDeadException: 0:
 Could not connect to 'oracle.jdbc.OracleDriver'.

 The returned message is: ORA-01017: invalid username/password; logon denied

 It is likely that the login or password is not valid.
 It is also possible that something else is invalid in
 the configuration or that the database is not available.

at oracle.mds.config.PConfig.loadFromBean(PConfig.java:959)
at oracle.mds.config.PConfig.(PConfig.java:758)
at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:787)
at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:848)
at oracle.mds.config.MDSConfig.(MDSConfig.java:491)
at oracle.mds.config.MDSConfig.(MDSConfig.java:438)
at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:516)
... 29 more
Caused by: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "MAR_TargetRepos" is invalid.    
MDS-01376: Unable to get database connection from data source "mds-owsm" configured with JNDI name "jdbc/mds/owsm".     
weblogic.common.resourcepool.ResourceDeadException: 0:
 Could not connect to 'oracle.jdbc.OracleDriver'.

 The returned message is: ORA-01017: invalid username/password; logon denied

 It is likely that the login or password is not valid.
 It is also possible that something else is invalid in
 the configuration or that the database is not available.

at oracle.mds.config.PConfig.loadFromBean(PConfig.java:953)
... 35 more

So the relevant part here was “ORA-01017: invalid username/password; logon denied”. This error meant that the server couldn’t log in to my MDS database schema (that’s one of the schemas you create when running the RCU as part of your OBIEE installation).

I ran the following query in my database (logged on with SYS account):

select * from dba_users where ACCOUNT_STATUS LIKE '%EXPIRED%' OR ACCOUNT_STATUS LIKE '%LOCK%' order by username;

It turned out that the schemas that the RCU created were setup to expire after six months after creation.

So, first step is to reset the password like this:

ALTER USER DEV_BIPLATFORM IDENTIFIED BY (yourpassword);
ALTER USER DEV_MDS IDENTIFIED BY (yourpassword);

DEV_BIPLATFORM and DEV_MDS are the names of my schemas. Just change the above SQL to you needs.

After that your schemas are still locked, so you need to unlock them:

ALTER USER DEV_BIPLATFORM ACCOUNT UNLOCK;
ALTER USER DEV_MDS ACCOUNT UNLOCK;

Finally, if you want your accounts to never expire ever again (that’s ok for a development server, I guess), you might want to execute the following SQL:

alter profile DEFAULT limit password_life_time UNLIMITED;

If your passwords are exactly the same as they were before they expired, you can restart your services at this point.

But if you changed your password (like I did) you have to update the data sources in your server. To do that you have to login to your Fusion Middleware Control (enterprise manager) and:

To set the MDS password:

  1. On the menu on the left, expand “WebLogic Domain”;
  2. Right-click “bifoundation_domain;
  3. On the pop-up menu select “JDBC Data Sources;
  4. Click “mds-owsm”;
  5. Select the “Connection Pool” tab;
  6. Set the password and hit “Apply”;

 To set the BIPLATFORM password:

  1. Expand “Business intelligence” menu on the left;
  2. Click the “Deployment” tab;
  3. Click the “Scheduler” tab under deployment;
  4. Click “Lock and Edit Configuration” button;
  5. Set the password and hit “Apply”;
  6. Click the “Activate Changes” button;

After all these operations, restart your OBI services. Hopefully they will start. If they don’t start, I suggest you restart your server.

Hope this helps.

Advertisements

4 Comments

Leave a Comment
  1. mach / Jul 25 2013 3:05 pm

    Hi, Really nice information, and let me tell you, your website gives the best and the most interesting information. This is just the kind of information that i had been looking for,and i would regularly watch out for the new post, once again hats off to you! Thanks a lot once again.

  2. Omar Saad / Apr 26 2014 11:22 pm

    i have same problem and i try this solution but in the end step when i pres apply this msg appear

    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 (or the other user) can unlock the domain configuration using the Change Center in the WebLogic Administration Console for this domain.

  3. Michel / Mar 31 2016 8:20 am

    Hello!
    I have the same problem: DEV_MDS and DEV_BIPLATFORM are locked, but at the same time weblogic are down, so I can’t change password via em. What can I do to fix?

    • Rodrigo Chiolas / Mar 31 2016 9:23 am

      Hi,

      If your weblogic is down probably you have another problem, try to understand why it is down. Check the logs 😉

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: