Exception during pool initialization.","level":"ERROR","stackTrace":"java.sql.SQLException: ORA-01017: invalid username/password; logon denied oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)

Liquibase Development
1

Hi All,
Need your advice in identifying the cause for the below stated issue.
While trying to connect to GOS (Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 ), the build is failing with the below error:
“podName”:“-staging-”,“env”:“test”,“message”:“Staging_***_DATASOURCE - Exception during pool initialization.”,“level”:“ERROR”,“stackTrace”:"\tjava.sql.SQLException: ORA-01017: invalid username/password; logon denied\n\n\t\tat oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)\n\t\tat

Is there any step/role missing in *** or *** Account onboarding ?
Steps done for the creation of *** Account , staging_*** :

  1. Created App-to-App Account for FID :
    Account Owner

Account Name
staging_***
2. Onboarded staging_*** to *** with app name as staging-liquibase (namespace is -staging-liquibase-test)
3. Granted access for staging to Staging *** UAT DB
4. Granted the below roles to this user in the *** UAT DB:
***_EXC_ETL
***_EV1_ETL
***_SEL_ETL
***_APPLICATION_SCHEMA_ROLE
***_DML_ETL
CONNECT
***_DBAPPUSER

My pom.xml has:
4.0.0
com..
-staging-liquibase
${revision}
jar
-staging-liquibase

true 8 0.0.0-SNAPSHOT 0.8.6 org.liquibase liquibase-core 4.8.0 com.h2database h2 2.1.210 org.liquibase liquibase-maven-plugin 4.8.0
2

You getting error: “ORA-01017: invalid username/password; logon denied”

Which indicates that either your username or password is invalid. This error has nothing to do with roles or privileges.

I suggest attempting to connect to your database via sql-developer or sqlplus to make sure you have the correct username/password, then make sure that is configured in your liquibase properties.

4 
ORA-01031: insufficient privileges [Failed SQL: (1031) CREATE TABLE ***STG_DBO.DATABASECHANGELOGLOCK

You don’t indicate what user you are attempting to connect with, but with those privileges you can only create that table if you login as ***STG_DBO. The CREATE TABLE privilege only allows you to create a table in your own schema. Otherwise you need CREATE ANY TABLE to create a table in another user’s schema.

and those