Wednesday, March 14, 2018

OID users not propagating to EBS

   A customer complained of user sync not working between OID and EBS. Anyone who knows IDM will check dip first . In this case customer was on OID 11.1.1.7 and OAM 11.1.2.2 . When we logged in to em and clicked dip application, we were unable to access it. Then we checked ods managed server logs and hit on the issue.

<Mar 10, 2018 12:53:23 PM GMT> <Warning> <EJB> <BEA-010212> <The EJB 'UpdateJob(Application: DIP#11.1.1.2.0, EJBComponent: dipejb.jar)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: remote[updateChangesForPre1012(long,long), updateChangesForPost1012(long,long), setUpdateChangeNumber(long), updateChangesForSync(long,long)]  local[updateChangesForPre1012(long,long), updateChangesForPost1012(long,long), setUpdateChangeNumber(long), updateChangesForSync(long,long)]  >
<Mar 10, 2018 12:53:23 PM GMT> <Warning> <EJB> <BEA-010212> <The EJB 'DIPScheduler(Application: DIP#11.1.1.2.0, EJBComponent: dipejb.jar)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: remote[startConfigset(), stopConfigSet()]  local[startConfigset(), stopConfigSet()]  >
<Mar 10, 2018 12:53:23 PM GMT> <Warning> <EJB> <BEA-010212> <The EJB 'DIPProv(Application: DIP#11.1.1.2.0, EJBComponent: dipejb.jar)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: remote[hasMoreChanges(), closeConnections(), initialize(java.lang.String,java.lang.String), updateStatus(boolean), doOneIteration()]  local[hasMoreChanges(), closeConnections(), initialize(java.lang.String,java.lang.String), updateStatus(boolean), doOneIteration()]  >
APPLICATION CODE GOT A NEW CONFIG OBJECT: oracle.idm.integration.dipconfig.jaxb.DIPConfig@28f772e0
Refresh Interval Current:0
<Mar 10, 2018 12:53:32 PM GMT> <Warning> <oracle.dip> <BEA-000000> <obtaining LDAP connection failed in attempt number :1 -  Retrying>
<Mar 10, 2018 12:53:32 PM GMT> <Warning> <oracle.dip> <BEA-000000> <obtaining LDAP connection failed in attempt number :2 -  Retrying>
<Mar 10, 2018 12:53:32 PM GMT> <Warning> <oracle.dip> <BEA-000000> <obtaining LDAP connection failed in attempt number :3 -  Retrying>
<Mar 10, 2018 12:53:32 PM GMT> <Error> <oracle.dip> <BEA-000000> <maximum LDAP connection retry count reached>
<Mar 10, 2018 12:53:32 PM GMT> <Error> <oracle.dip> <BEA-000000> <Connection to LDAP server failed - Check configuration of DIP server.>
<Mar 10, 2018 12:53:32 PM GMT> <Error> <oracle.dip> <BEA-000000> <Directory Integration Platform is not able to get the context with the given details : OID host: oidardsprd.oracleoutsourcing.com Port: 10038 SSL mode:1.>
<Mar 10, 2018 12:53:32 PM GMT> <Error> <oracle.dip> <DIP-10013> <Exception>
<Mar 10, 2018 12:53:34 PM GMT> <Warning> <oracle.adfinternal.view.faces.partition.FeatureUtils> <ADF_FACES-30130> <Ignoring feature-dependency on feature "AdfDvtCommon".  No such feature exists.>
Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.
Started: ADF Library non-ADFJspResourceProvider post-deployment
Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 58

Solution: Well, check on em , unable to access is a issue. Other check is dipstatus.

set Oracle_Home to idm home.
cd $ORACLE_HOME/bin
-bash-4.1$ ./dipStatus -h xyz.oracle.com -p 10023 -D weblogic
[Weblogic user password]
Connection parameters initialized.
Connecting at xyz.oracle.com:10023, with userid "weblogic"..
Connected successfully.

ODIP Application is down at this host and port.
-bash-4.1$

So, start your ODS managed server , it should fix the issue.Maybe ODS was started prior to starting OID services i think.

No comments:

Post a Comment