Table 'User' exist Error received when starting Tomcat during ARD Hub implementation

Products

• CA Agile Requirements Designer

Issue/Introduction

We're in the process of implementing a new ARD hub server and are receiving errors when starting Tomcat. Keycloak is running and no issues reported during the startup. 

2022-06-03 16:09:57.545  INFO [flow-storage,,] 2620 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'hibernateConfiguration' of type [org.hibernate.cfg.Configuration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-06-03 16:09:57.560  INFO [flow-storage,,] 2620 --- [           main] ardflowstorage.DataConfiguration         : Database settings:
2022-06-03 16:09:57.560  INFO [flow-storage,,] 2620 --- [           main] ardflowstorage.DataConfiguration         :   dbType :: mysql
2022-06-03 16:09:57.560  INFO [flow-storage,,] 2620 --- [           main] ardflowstorage.DataConfiguration         :   url    :: jdbc:mysql://sd-dbc9-e3b1.nam.nsroot.net:3306/mysql?useUnicode=true&characterEncoding=utf-8&createDatabaseIfNotExist=true&user=root&useSSL=false
2022-06-03 16:09:57.576  INFO [flow-storage,,] 2620 --- [           main] ardflowstorage.DataConfiguration         :   user   :: root
2022-06-03 16:09:57.576  INFO [flow-storage,,] 2620 --- [           main] ardflowstorage.DataConfiguration         :   schema :: mysql
2022-06-03 16:09:57.592  INFO [flow-storage,,] 2620 --- [           main] ardflowstorage.dal.DataSourceFactory     : Basic data source properties: {logAbandoned=true, maxWaitMillis=30000, password=****, minIdle=2, maxTotal=50, driverClassName=org.mariadb.jdbc.Driver, removeAbandonedTimeout=3600, defaultTransactionIsolation=2, removeAbandonedOnBorrow=true, url=jdbc:mysql://sd-dbc9-e3b1.nam.nsroot.net:3306/mysql?useUnicode=true&characterEncoding=utf-8&createDatabaseIfNotExist=true&user=root&useSSL=false, username=root}
2022-06-03 16:09:57.654  INFO [flow-storage,,] 2620 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'dataSource' of type [org.apache.commons.dbcp2.BasicDataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-06-03 16:09:57.795  INFO [flow-storage,,] 2620 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-06-03 16:09:57.810  INFO [flow-storage,,] 2620 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceInitializerInvoker' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceInitializerInvoker] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-06-03 16:10:06.451  INFO [flow-storage,,] 2620 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean '(inner bean)#5da6b3d3' of type [org.springframework.beans.factory.config.PropertiesFactoryBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-ts the failed migration may still be required.
2022-06-03 16:10:23.952  INFO [flow-storage,,] 2620 --- [           main] ardflowstorage.dal.TenantSchemaDao       : Starting Flyway migration
2022-06-03 16:10:24.280  INFO [flow-storage,,] 2620 --- [           main] o.f.core.internal.command.DbValidate     : Successfully validated 28 migrations (execution time 00:00.253s)
2022-06-03 16:10:24.311  INFO [flow-storage,,] 2620 --- [           main] o.f.core.internal.command.DbMigrate      : Current version of schema `mysql`: 0.1.0.202
2022-06-03 16:10:24.342  INFO [flow-storage,,] 2620 --- [           main] o.f.core.internal.command.DbMigrate      : Migrating schema `mysql` to version 0.1.0.400 - Create Initial Tables With Subflow External Links
2022-06-03 16:10:24.358 ERROR [flow-storage,,] 2620 --- [           main] o.f.core.internal.command.DbMigrate      : Migration of schema `mysql` to version 0.1.0.400 - Create Initial Tables With Subflow External Links failed! Please restore backups and roll back database and code!
2022-06-03 16:10:24.405 ERROR [flow-storage,,] 2620 --- [           main] ardflowstorage.dal.TenantSchemaDao       : Flyway migration failed.
org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateSqlException:

Migration V0_1_0_400__Create_Initial_Tables_With_Subflow_External_Links.sql failed

----------------------------------------------------------------------------------

SQL State  : 42S01
Error Code : 1050
Message    : (conn=48) Table 'user' already exists

Location   : ardflowstorage/sql/tenant/mysql/V0_1_0_400__Create_Initial_Tables_With_Subflow_External_Links.sql (C:\Program Files\Apache\Tomcat 9.0\webapps\ard#flow-storage\WEB-INF\classes\ardflowstorage\sql\tenant\mysql\V0_1_0_400__Create_Initial_Tables_With_Subflow_External_Links.sql)

Line       : 7

Statement  : CREATE TABLE User (
        `id` nvarchar(255) NOT NULL,
        `login` nvarchar(50) NULL,
        `name` nvarchar(50) NULL,
        `surname` nvarchar(50) NULL,
        `email` nvarchar(50) NULL,
        CONSTRAINT PK_User PRIMARY KEY(`id` ASC)
)

 

Environment

Release : 3.2.5

Component: ARD
Agile Requirements designer

Cause

This issue is caused because the schema name is not configured in settings.properties file (path: .ard/conf/settings.properties).

It should be "ARDFlowStorage" or the user can give any other custom names

 

Resolution

 Schema name is not configured in settings.properties file (path: .ard/conf/settings.properties).  Once the schema name was added, it resolved the issue. 

settings.properties file