OID 12c - "ORA-01017: invalid username/password;" after ODS Password Change on Windows with OIDPASSWD
(Doc ID 2950212.1)
Last updated on MAY 24, 2023
Applies to:
Oracle Internet Directory - Version 12.2.1.4.0 and laterMicrosoft Windows x64 (64-bit)
Symptoms
OID instance fails to start after changing ODS Schema Password on Windows with "oidpasswd".
- Change ODS password with the command: oidpasswd connect=oiddb change_oiddb_pwd=true
- The Admin Server will take a very long time to start and multiple errors can be seen in AdminServer.log, including "java.io.IOException: ORA-01017: invalid username/password; logon denied"
- OID instance will fail to start and a generic error message will be seen in NodeManager.log: "Server start command for OID server 'oid1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]"
- Checking with SQLPlus, the ODS account will be locked in the Database
- oidmon-0000.log will present "ORA-28000,ORA-28000: The account is locked." and "Unable to connect to database, will retry again after 10 sec" error messages
AdminServer.log
[DATE] [AdminServer] [WARNING] [J2EE JMX-46252][oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean] [tid:[STANDBY].ExecuteThread: '4' for queue: 'weblogic.kernel.Default(self-tuning)'] [userId: ] [ecid:[ECID]] [partition-name: DOMAIN][tenant-name: GLOBAL] Error during preRegister for MBeanoracle.oid.mbeans:type=OIDInstance,name=oid1[[java.io.IOException: ORA-01017: invalid username/password; logon denied
at oracle.oid.mbeans.OIDProxy.load(OIDProxy.java:1879)
at oracle.oid.mbeans.OIDProxy.preRegister(OIDProxy.java:2117)
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean$1.run(OracleStandardEmitterMBean.java:567)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doPreReg
NodeManager.log
<[DATE]> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<[DATE]> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation:weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>Successfully Connected to Node Manager.Starting server oid1 ...
This Exception occurred at [DATE].weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Server start command for OID server 'oid1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'oid1' log for detailed information.].Please check Node Manager log for details.
Error: Error occurred while performing nmStart : Error Starting server oid1 :Received error message from Node Manager Server: [Server start command for OID server 'oid1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'oid1' log for detailed information.]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :
oidmon-0000.log
[DATE] [OID] [NOTIFICATION:16] [] [OIDMON] [HOST_NAME] [pid: 5288] [tid: 0] Guardian: [gsdsiConnect] ORA-28000,ORA-28000: The account is locked.
[DATE] [OID] [NOTIFICATION:16] [] [OIDMON] [HOST_NAME] [pid: 5288] [tid: 0] Guardian: [oidmon]: Unable to connect to database, will retry again after 10 sec
[DATE] [OID] [NOTIFICATION:16] [] [OIDMON] [HOST_NAME] [pid: 5288] [tid: 0] Guardian: Error connecting database. -1
[DATE] [OID] [NOTIFICATION:16] [] [OIDMON] [HOST_NAME] [pid: 5288] [tid: 0] Guardian: Error : Guardian Process terminated
Changes
Just changed ODS password using oidpasswd.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |