oif JNDI conftmpdatastore password expired JDBC error

 error

 <Warning> <JDBC> <oifserver> <Thread-34> <<anonymous>> <> <0000LQpE4yX8hoWzLwmJOA1NivGU000003> <1471920629058> <BEA-0011
29> <Received exception while creating connection for pool "conftmpdatastore": ORA-28001: the password has expired

 <Info> <JDBC> <oifserver>  <Thread-34> <<anonymous>> <> <0000LQpE4yX8hoWzLwmJOA1NivGU000003> <1471920629060> <BEA-001156>
 <Stack trace associated with message 001129 follows:

java.sql.SQLException: ORA-28001: the password has expired

        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
        at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:689)
        at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:452)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
        at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:384)
        at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:811)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411)
        at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:678)
        at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:238)
        at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:34)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:567)
        at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:357)
        at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:239)
        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)
        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1227)
        at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:451)
        at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:343)
        at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:330)
        at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:469)
        at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:363)
        at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:125)
        at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:454)
        at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:538)
        at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:498)
        at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:491)
        at oracle.security.fed.model.util.rdbms.RDBMSConnectionManager.getConnection(RDBMSConnectionManager.java:210)
        at oracle.security.fed.util.config.RDBMSConfiguration.getValue(RDBMSConfiguration.java:97)
        at oracle.security.fed.util.config.RDBMSConfiguration.getVersion(RDBMSConfiguration.java:85)


solution:

1.   log into database as power user (sysdba) and find which password is expired by running following command.

select username, account_status, lock_date from dba_usersl


check if any account have account_status as EXPIRED.

you will see one of the account with EXPIRED status.


2. run following command as sysdba to change the password.

alter user "name of the user" identified by "password of the user"


optional:
if you want to have this password never expired, run following command

1. find default profile of the user

select username,profile from dba_users;

2. alter profile "name of the profile" limit PASSWORD_LIFE_TIME UNLIMITED;

find witch file contains JAVA_HOME path

find . -type f -name "*.sh" -exec grep -il JAVA_HOME {} \;

Weblogic, SOA, Oracle BI WSM Policy Manager, Oracle WebCenter, EM version information file

you can find version information of Weblogic, SOA, Oracle BI WSM Policy Manager, Oracle WebCenter, EM  at below file


• $MW_HOME/user_projects/domains/domain/init-info/domain-info.xml

for weblogic version you can also look into

• $MW_HOME/wlserver_10.3/.product.properties

sample url to create IDP initiated url request

fill the request and create IDP initiated url

 http://host:port/fed/idp/initiatesso?providerid=http%3A%2F%2Fsp.com&returnurl=ProtectedAppURL

OIF EMAGENT error Startup of UPLOAD MANAGER failure (00722)

emagent.log
===========
  Thread-1 Starting Agent 10.2.0.5.0 from /opt/oracle/Middleware2/Oracle_IDM1 (00701)
  Thread-1 <Agent Startup> : Startup of UPLOAD MANAGER failure (00722)




emagentfetchlet.log
================
  [nmefmgr_getJNIFetchlet] WARN emd.fetchlets getMetric.387 - oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
oracle.sysman.emSDK.emd.fetchlet.FetchletException: oracle.sysman.emSDK.emd.fetchlet.FetchletException: java.io.IOException: Unhandled exception in lookup
at oracle.sysman.emd.fetchlets.JMX.JMXFetchletWrapperBase.getMetric(JMXFetchletWrapperBase.java:96)
at oracle.sysman.emd.fetchlets.FetchletWrapper.getMetric(FetchletWrapper.java:382)




emagent.trc
=========
Thread-1 WARN upload: Upload manager has no Failure script: disabled
Thread-1 WARN main: failed to start upload manager, disabled


Solution:
your EMAGENT password is not correct. you can update EMAGENT password thru EM console by following.


1. Login to EM console
2. Navigate to Farm-->Agent-Monitored Targets
3. Click Configure for OIF.
4. Update "WebLogic Monitoring Password" with existing password.
5. Restart the OIF and EMAGENT services.

OIF, updating EMAGENT password thru EM console

1. Login to EM console
2. Navigate to Farm-->Agent-Monitored Targets
3. Click Configure for OIF.
4. Update "WebLogic Monitoring Password" with existing password.
5. Restart the OIF and EMAGENT services.

OIF metadata configuration file cot.xml

$DOMAIN_HOME/config/fmwconfig/servers/<OIF_SERVER_NAME>/applications/OIF_11.1.1.2.0/configuration/*.xml files (the federated partner data is stored in the cot.xml file) prior to loading the new metadata


when you are planning to upload medata and want to have backup of existing metadata you can either backup cot.xml or i prefer to backup whole "config" directory.