ORA-01017: Invalid Username/password After Changing Config & Atomic Schema Password in OFSAA 8.0.x
(Doc ID 2470878.1)
Last updated on FEBRUARY 16, 2023
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.5 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Symptoms
For Oracle Financial Services Analytical Applications (OFSAA) 8.0.x, after changing the atomic password in the user interface and config passwords as described in <Document 1246774.1> "How to Change the OFSAA Config and Atomic Schema User Passwords in OFSAA", when starting the FICServer process, the error below appears in the SMSService.log from $FIC_APP_HOME/common/FICServer/logs:
[UMMLOG] Nov 2,18 14:48:29 : [DACDATABASEGATEWAY][BIND VARIABLES DDL Query for debug] : [ select METADATA_KEY ,LOCALE_DESCRIPTION from REV_LOCALE_HIER where VERSION_NO = 0 and METADATA_KEY like 'HPFTRL:%:ND' and upper(METADATA_LOCALE) = 'EN_US'] On URL: <jdbc connect string> Driver: oracle.jdbc.driver.OracleDriver Metadata Required : false
[UMMLOG] Nov 2,18 14:48:29 : [DACCONNECTIONPROVIDER]Connection Type getting used ->
[UMMLOG] Nov 2,18 14:48:29 : [DACCONNECTIONPROVIDER]Apache Connection
[UMMLOG] Nov 2,18 14:48:30 : [DACCONNECTIONPROVIDER]Error getting connection from pool : java.sql.SQLException: Cannot create PoolableConnectionFactory (ORA-01017: invalid username/password; logon denied
)
[UMMLOG] Nov 2,18 14:48:30 : [DACCONNECTIONPROVIDER]
java.sql.SQLException: Cannot create PoolableConnectionFactory (ORA-01017: invalid username/password; logon denied
)
at org.apache.commons.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:2294)
at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:2039)
at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:1533)
at com.iflex.fic.ficserver.services.DAC.DACConnectionProvider.getAPACHEConnection(DACConnectionProvider.java:182)
at com.iflex.fic.ficserver.services.DAC.DACConnectionProvider.getConnection(DACConnectionProvider.java:131)
at com.iflex.fic.ficserver.services.DAC.DACDatabaseGateway.executePSQuery(DACDatabaseGateway.java:1714)
at com.iflex.fic.ficserver.services.sms.SMSDACGateway.innerPSExecuteQuery(SMSDACGateway.java:805)
at com.iflex.fic.ficserver.services.sms.SMSDACGateway.innerPSExecuteQuery(SMSDACGateway.java:721)
at com.iflex.fic.ficserver.services.sms.SMSDACGateway.executePSQuery(SMSDACGateway.java:470)
at com.iflex.fic.ficserver.services.sms.SMSServiceProvider.handleRequest(SMSServiceProvider.java:638)
at com.iflex.fic.newservice.ServiceProxy.invokeService(ServiceProxy.java:184)
at com.iflex.fic.newservice.NewServiceMaster.provideService(NewServiceMaster.java:211)
etc.
The error occurs in the log after starting the FICServer process. Eventually, the atomic schema user account is locked after too many failed login attempts and you get the error "ORA-28000: the account is locked".
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 |
Cause |
Solution |
References |