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)

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 ), jules build is failing with the below error:
“podName”:“fccs-staging-liquibase-t9hxx”,“env”:“test”,“message”:“Staging_UAT_GOS_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 FID or Functional Account onboarding ?
Steps done for the creation of Functional Account , staging_gos_ku :

  1. Created Sophia App-to-App Account for FID :
    Account Owner
    A015135
    Account Name
    staging_gos_ku
  2. Onboarded staging_gos_ku to GAIA with app name as staging-liquibase (namespace is 85030d109670-staging-liquibase-test)
  3. Granted access for staging_gos_ku to Staging GOS UAT DB
  4. Granted the below roles to this user in the GOS UAT DB:
    BRGSTG_EXC_ETL
    BRGSTG_EV1_ETL
    BRGSTG_SEL_ETL
    JPMC_APPLICATION_SCHEMA_ROLE
    BRGSTG_DML_ETL
    CONNECT
    JPMC_DBAPPUSER

My pom.xml has:
4.0.0
com.jpmorgan.fccs
fccs-staging-liquibase
${revision}
jar
fccs-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

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.

This is a kerberos authenticated user, (passwordless user), and is meant to be used only through Jules pipeline.Hence can’t test it manually thru sqldeveloper.
Anyways, the issue has been resolved by mapping the user to the correct schema.
But now , I’m facing another issue of insufficient privileges while creating the CHANGELOGLOCK table in my schema.
“Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘liquibase’ defined in class path resource [org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration$LiquibaseConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.LockException: liquibase.exception.DatabaseException: ORA-01031: insufficient privileges [Failed SQL: (1031) CREATE TABLE BRGSTG_DBO.DATABASECHANGELOGLOCK (ID INTEGER NOT NULL, LOCKED NUMBER(1) NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR2(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))]”,“level”:“WARN”}
The user is assigned to a role which has the below privileges in addition to CREATE SESSION and SET CONTAINER privileges :

  1. EXEMPT REDACTION POLICY
  2. CREATE ANY CONTEXT
  3. CREATE TABLE
  4. EXEMPT ACCESS POLICY
  5. CREATE VIEW
  6. ADMINISTER DATABASE TRIGGER
  7. FLASHBACK ARCHIVE ADMINISTER
  8. CHANGE NOTIFICATION
  9. CREATE DIMENSION
  10. CREATE TABLE
  11. CREATE CUBE BUILD PROCESS
  12. CREATE MEASURE FOLDER
  13. CREATE EVALUATION CONTEXT
  14. CREATE TYPE
  15. ADMINISTER SQL TUNING SET
  16. ADVISOR
  17. CREATE RULE
  18. CREATE OPERATOR
  19. CREATE VIEW
  20. CREATE PUBLIC SYNONYM
  21. CREATE INDEXTYPE
  22. FORCE TRANSACTION
  23. CREATE ROLE
  24. CREATE CLUSTER
  25. CREATE CUBE
  26. RESUMABLE
  27. CREATE PROCEDURE
  28. CREATE SESSION
  29. CREATE ANY EDITION
  30. CREATE RULE SET
  31. CREATE MATERIALIZED VIEW
  32. CREATE SEQUENCE
  33. FLASHBACK ARCHIVE ADMINISTER
  34. CREATE CUBE DIMENSION
  35. CREATE MINING MODEL
  36. CHANGE NOTIFICATION
  37. DEBUG CONNECT SESSION
  38. CREATE TRIGGER
  39. CREATE SYNONYM
ORA-01031: insufficient privileges [Failed SQL: (1031) CREATE TABLE BRGSTG_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 BRGSTG_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