After attempting to log into OID after starting up the server and services, I notice that I was unable to log into the OID domain using any credentials.
When navigating through to the opmnctl directory attempting to startall and stopall, I was receiving the following error:
[oracle@localhost bin]$ ./opmnctl stopall
opmnctl stopall: stopping opmn and all managed processes...
Error
-- Process (index=1,uid=653676181,pid=3955)
time out while waiting for a managed process to start
Log:
/home/oracle/Oracle/Middleware/asinst_2/diagnostics/logs/OID/oid2/console~OID~1.log
When I run the status command, I notice that oidldapd process status was down against the oid component [oracle@localhost bin]$ ./opmnctl status
Processes in Instance: asinst_2
---------------------------------+--------------------+---------+---------
ias-component | process-type | pid | status
---------------------------------+--------------------+---------+---------
ohs1 | OHS | 3532 | Alive
ovd1 | OVD | 3531 | Alive
oid2 | oidldapd | N/A | Down
oid2 | oidldapd | N/A | Down
oid2 | oidmon | N/A | Down
EMAGENT | EMAGENT | 3530 | Alive
After deciding to review the oidmon-0000.log, located within the /home/oracle/Oracle/Middleware/asinst_2/diagnostics/logs/OID/oid2/ directory, I noticed the error ORA-28002, ORA-28002: the password will expire within 7 days.
[host: localhost.localdomain] [pid: 6563] [tid: 0] Guardian: Connecting to database, connect string is oiddb
[host: localhost.localdomain] [pid: 6563] [tid: 0] Guardian: [gsdsiConnect] ORA-28002, ORA-28002: the password will expire within 7 days
[host: localhost.localdomain] [pid: 6563] [tid: 0] Guardian: [oidmon]: Unable to connect to database, will retry again after 10 sec

Log into SQLPLUS and located the username of the ODS service...
SQL> select username from dba_users;
USERNAME
------------------------------
ODSSM
ODS
SCOTT
ORACLE_OCM
BI
...

I then decided to review this user within SQL developer...
Select * from dba_users where username = 'ODS';
After noticing that infact the user password has expired, as apposed to what was stated within the logs. I altered the user by changing the password (in my case, my password was Password1)
alter user ods identified by Password1
Then commit...commit;
I ran the select query again and then noticed the Account status had changed to OPEN (yay!)

I then ran the opmnctl stopall, then opmnctl startall and notied the oid2 component status has changed to Down to Alive (yay again!)
[oracle@localhost bin]$ ./opmnctl stopall
opmnctl stopall: stopping opmn and all managed processes...
[oracle@localhost bin]$ ./opmnctl startall
opmnctl startall: starting opmn and all managed processes...
[oracle@localhost bin]$ ./opmnctl status
Processes in Instance: asinst_2
---------------------------------+--------------------+---------+---------
ias-component | process-type | pid | status
---------------------------------+--------------------+---------+---------
ohs1 | OHS | 9541 | Alive
ovd1 | OVD | 9540 | Alive
oid2 | oidldapd | 9637 | Alive
oid2 | oidldapd | 9623 | Alive
oid2 | oidmon | 9543 | Alive
EMAGENT | EMAGENT | 9539 | Alive
When I restarted the weblogic server, I was then able to log into OID through the ODSM gui.
About the author

Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...

NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...

For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...

In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
