Registry Service using the wrong schema tables when VSE starts.

Document ID : KB000094946
Last Modified Date : 07/05/2018
Show Technical Document Details
Issue:
I am getting one error in the registry when I start the vse, not sure what it is at this point. Everything seems to startup ok and work. The development registry database has a multiple schemas in it for each environment and the error seems to be pointing to the first one I built. Not sure why it is in the other environments. I am hoping it goes away when I upgrade the environment that has the ca_reg schema. Let me know if you have any thoughts. Here is the setup I have. Env 0 has ca_reg for its schema. careg database. Env1 has ca_reg1 for its schema. careg database. Etc…. The error in environment 5,6 …. Is : 2018-01-17 20:57:40,469Z (14:57) [Thread-15] ERROR org.springframework.boot.SpringApplication - Application startup failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManagerPostProcessor': Initialization of bean failed; nested exception is o rg.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting be an property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing column: case_type in CA_REG.LISA_MANUAL_CASE at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) at ......
Environment:
DevTest 10.2.4
Cause:
Its not an issue with DevTest - this is just how Oracle works. You are not having a problem in 9 because the Oracle user being used points to the 9 schema by default. When you add a second schema in Oracle, you need to do some configuration in Java to get it to not use the user default schema. Your DBA should know how to do this.
Resolution:
Until the Java configuration can be done, do this:

Error resolved by adding this property to the site.properties file and restarting the Registry: 

hibernate.default_schema=ca_reg5a 

This is an Oracle property. The default schema property is used when you create multiple schemas within a single database.