Post Oracle DB upgrade to Oracle 19c, Identity Manager env not getting started

Products

• CA Identity Suite
• CA Identity Manager

Issue/Introduction

Upgraded the Oracle DB from 12c to 19c. After upgrade we have started the CA Identity Manager and getting the below error. 

 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.ra.deployment."iam_im.ear#workflow.rar": org.jboss.msc.service.StartException in service jboss.ra.deployment."iam_im.ear#workflow.rar": JBAS010446: Failed to start RA deployment [iam_im.ear#workflow.rar]

2022-03-19 03:59:28,907 ERROR [ims.tmt.CreateDatabaseSchema] (MSC service thread 1-15) The datasource configuration of Archive is invalid.: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/iam/im/jdbc/jdbc/archive
2022-03-19 03:59:28,909 ERROR [ims.Main] (MSC service thread 1-15) The IAM FW Startup was not successful
2022-03-19 03:59:28,909 ERROR [ims.Main] (MSC service thread 1-15) java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/iam/im/jdbc/jdbc/archive

2022-03-19 03:19:06,502 ERROR [ims.tmt.CreateDatabaseSchema] (MSC service thread                                                                              1-9) The datasource configuration of Archive is invalid.: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/iam/im/jdbc/jdbc/archive
2022-03-19 03:19:06,505 ERROR [ims.Main] (MSC service thread 1-9) The IAM FW Startup was not successful
2022-03-19 03:19:06,505 ERROR [ims.Main] (MSC service thread 1-9) java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/iam/im/jdbc/jdbc/archive
        at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDa                                                                             taSource.java:154)

2022-03-19 03:19:06,506 INFO  [ims.Main] (MSC service thread 1-9) ---- CA IAM Se                                                                             rver shutdown Initiated. ----
2022-03-19 03:19:06,513 WARN  [ims.tmt.events] (MSC service thread 1-9) Attempti                                                                             ng to shutdown long running events if any.
2022-03-19 03:19:07,169 ERROR [org.jboss.msc.service.fail] (MSC service thread 1                                                                             -9) MSC000001: Failed to start service jboss.undertow.deployment.default-server.                                                                             default-host./iam/im: org.jboss.msc.service.StartException in service jboss.unde                                                                             rtow.deployment.default-server.default-host./iam/im: Failed to start service
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceCont                                                                             rollerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

Environment

Release : 14.3

Component : Identity Manager

Cause

Reviewing IM server.log identified the Oracle error ORA-01017: invalid username/password; logon denied

For some reason the lowercase passwords being used in Oracle 12c were converted to upper case during the upgrade to Oracle 19

Resolution

There is an error "Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied" in IM server.log after upgrade to Oracle 19c.

Tested in Identity Suite console and SQL Developer and edited the Database Connection and got same error ORA-01017: invalid username/password; logon denied

Tested with same password but converting all lowercase characters to uppercase and test connection worked fine.

Putting the passwords converted from lowercase to uppercase in Identity Suite Console Edit Database and IM started Successfully.

Advised to check with DBA why the lower case passwords were converted to uppercase with Oracle 19 Upgrade. This is not a Identity Suite problem but a new behavior with Oracle DB after the DB upgrade.