After upgrading database for IAM getting error

Products

• CA Cloud Test Mobile
• CA Application Test

Issue/Introduction

We have upgraded to 10.5 version, but while starting components we need some help as IAM component is introduced recently.

Installation is  but we need to start the components, while starting IAM component we got below error.

Error log 1

Config server url not provided. Using properties from install location

Error Log 2

14:29:04,894 ERROR [org.keycloak.connections.jpa.updater.liquibase.conn.DefaultLiquibaseConnectionProvider] (ServerService Thread Pool -- 48) Change Set META-INF/jpa-changelog-2.1.0.xml::2.1.0::[email protected] failed.  Error: ORA-00955: name is already used by an existing object
 [Failed SQL: CREATE TABLE AST_CA_DASHBOARD.BROKER_LINK (IDENTITY_PROVIDER VARCHAR2(255) NOT NULL, STORAGE_PROVIDER_ID VARCHAR2(255), REALM_ID VARCHAR2(36) NOT NULL, BROKER_USER_ID VARCHAR2(255), BROKER_USERNAME VARCHAR2(255), TOKEN CLOB, USER_ID VARCHAR2(255) NOT NULL)]: liquibase.exception.DatabaseException: ORA-00955: name is already used by an existing object
 [Failed SQL: CREATE TABLE AST_CA_DASHBOARD.BROKER_LINK (IDENTITY_PROVIDER VARCHAR2(255) NOT NULL, STORAGE_PROVIDER_ID VARCHAR2(255), REALM_ID VARCHAR2(36) NOT NULL, BROKER_USER_ID VARCHAR2(255), BROKER_USERNAME VARCHAR2(255), TOKEN CLOB, USER_ID VARCHAR2(255) NOT NULL)]

Caused by: liquibase.exception.MigrationFailedException: Migration failed for change set META-INF/jpa-changelog-2.1.0.xml::2.1.0::[email protected]:
     Reason: liquibase.exception.DatabaseException: ORA-00955: name is already used by an existing object
 [Failed SQL: CREATE TABLE AST_CA_DASHBOARD.BROKER_LINK (IDENTITY_PROVIDER VARCHAR2(255) NOT NULL, STORAGE_PROVIDER_ID VARCHAR2(255), REALM_ID VARCHAR2(36) NOT NULL, BROKER_USER_ID VARCHAR2(255), BROKER_USERNAME VARCHAR2(255), TOKEN CLOB, USER_ID VARCHAR2(255) NOT NULL)]
        at liquibase.changelog.ChangeSet.execute(ChangeSet.java:584)

Environment

Release : 10.5

Component : CA Service Virtualization

Resolution

You are pointing both IAM and Registry to same database.

    As your old registry database has table name broker_link, IAM is throwing an error while creating database. So, we reverted IAM database to Embeded databse to resolve this issue. 

   For long run, create a separate database schema for IAM and configure database details.