search cancel

Registry Service not able to start - Failed statement: CREATE TABLE LISA_TEMP_TABLE1


Article ID: 213155


Updated On:


Service Virtualization



Our DBA created  DEVTEST Tables for IAM , ED , Registry and CAI  using the DDL from DevTest/Database folder with DBA privileges.  Once the tables are created , we created a user - APPUser in Oracle, that has less privileges to start all the DevTest components.  

IAM and ED  starts fine.  

 While starting Registry service, its giving the error message. 

The error message
2021-04-12 20:46:02,108Z (16:46) [main] ERROR System.err                     - [DevTest AGENT:][ERROR][9328][21][main][Apr 12, 2021 4:46:02 PM] !!!!!!!! Database user permission check failed !!!!!!!!
2021-04-12 20:46:03,277Z (16:46) [main] ERROR System.err                     - [DevTest AGENT:][ERROR][9328][21][main][Apr 12, 2021 4:46:03 PM] Please ensure the user has privileges to create/alter/drop table, view and index and manipulate data.
2021-04-12 20:46:04,301Z (16:46) [main] ERROR System.err                     - [DevTest AGENT:][ERROR][9328][21][main][Apr 12, 2021 4:46:04 PM] Failed statement: CREATE TABLE LISA_TEMP_TABLE1__ (COL1 varchar(10) not null, COL2 varchar(10))  Error: ORA-01031: insufficient privileges
2021-04-12 20:46:05,337Z (16:46) [main] ERROR com.itko.lisa.utils.db.safeguard.DatabaseSafeGuard - DDLs cannot be executed in this module REPORTING database user does not have sufficient permissions.
2021-04-12 20:46:05,337Z (16:46) [main] ERROR com.itko.lisa.coordinator.TestRegistryImpl - Database initialization is not possible in module REPORTING. Not enough db permissions to execute DDL statements.
com.itko.lisa.exception.UpgradeException: Database initialization is not possible in module REPORTING. Not enough db permissions to execute DDL statements.
        at com.itko.lisa.utils.db.safeguard.DatabaseSafeGuard.checkIfAllDatabasesAreWritable(
        at com.itko.lisa.utils.db.safeguard.DatabaseSafeGuard.checkIfMigrationIsPossible(
        at com.itko.lisa.utils.db.safeguard.DatabaseSafeGuard.checkIfDatabaseCanBeChanged(
        at com.itko.lisa.coordinator.TestRegistryImpl.main(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
        at com.exe4j.runtime.WinLauncher$ Source)


 This is critical and impacting our onboarding for perf testing.




Release : 10.6

Component : CA Service Virtualization


BAsed on what we found in the latest log file , it could be seen that we are  trying to setup agent schema " Creating Pathfinder Schema"


For DB users with less priviledges, Make sure you set the property lisa.database.migration.safeguards to false in It is true by default. It is important to ensure that the db user has dba level privileges during the upgrade.

1. in add : 



2. for the error you are seeing, its trying to create the Agent tables. 

Changed  rules.xml  to skip setting up the Broket/Agent tables.

Solution to skip setting AGENT/Broker tables:


Edit rules.xml file in LISA_HOME folder. Add the XML elements in bold. Make sure you add the property separately under agent, broker and console sections as shown below. Save the file and restart registry. 


<?xml version="1.0" encoding="UTF-8"?><rules>
   <agent guid="-2032180703" name="DEFAULT">
      <property comment="Enable querying of the JMX counters via the agent" key="lisa.agent.jmx.enabled" value="true"/>
      <property comment="Persistence" key="PERSISTENCE_DISABLED" value="true"/>
   <!--************ Broker *************-->
      <property comment="The logging level of the root category" key="lisa.log.level" value="dev"/>
      <property comment="Persistence" key="PERSISTENCE_DISABLED" value="true"/>
   <!--************ Console ************-->
      <property comment="Broker url when run in embedded mode (i.e. in LW)" key="" value="tcp://localhost:2009?daemon=true"/>
      <property comment="Persistence" key="PERSISTENCE_DISABLED" value="true"/>

3.  Also , make sure the connection pool size is  at a higher number, and you don't get starvation on connection pools.