ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Unable to create table LISA_TEMP_TABLE1__ when Upgrading from DevTest 10.1.0 to 10.5.0

book

Article ID: 186373

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

This is a fresh install of DevTest 10.5 on Windows 2016, with local SQL 2016.

The problem is the following: Customer doesn't want to provide dbo authority to "our" db users. When we run the 10.1 installation we created the DBs manually, then we imported the DDLs provided with the product to create the schema, we created users with datareader and datawriter permissions, we configured .properties files and everything worked as expected.

Tried the same with release 10.5, so I created 3 DBs (iamdb, lisadb and dradisdb), 3 users (iamusr, lisausr and dradisusr) and these three users have datareader and datawriter permissions on "their" databases.

Then imported the DDLs from sa user (one DDL for IAMDB, one for DRADISDB and two for LISADB).

Configured the .properties files and:


1) Started IAM service ==> OK

2) Started Enterprise Dashboard Service ==> Ok

3) Started Registry service ==> IT FAILS.


In a nutshell Registry service tries to create a table (LISA_TEMP_TABLE1__) but obviously it fails.

On local machine tried adding the ddladmin authority to lisausr (not to the other users) and then it works, if user has ddladmin authority there is no need to import the DDLs.

 

Cause

Schema changes from10.1.0 to 10.5.0

Environment

Release : 10.5

Component : CA Service Virtualization

Resolution

There were some schema changes in 10.1 to 10.5.

If an upgrade installation had been done there would have been no issue.

If the current version of DevTest is different from the value inside [PREF_LISA_VERSION] it processes few extra steps to validate if an upgrade can be done.

And it tried checking checkIfAllDatabasesAreWritable, this only happens if the current version of Devtest and PREF_LISA_VERSION are different.

We validated you can manually update the value of LISA_VERSION as '10.5.0' in [PREF_LISA_VERSION].