Skip to Content
Former Member
Jul 24, 2017 at 08:04 PM

Why is Hybris looking for TYPESYSTEMNAME in sql update statement at Startup?


We are seeing an error in the startup of Hybris after building the new version code (v6.3.0.4) and startup for the first time. We are upgrading from v5.0.4.7 on Oracle 11g. Certain columns and other associated tables do not seem to exist in v5.0 and would expect that Hybris should stnd allow an Update System to occur to create these new tables and columns. Problem is that we can not start system to do an UpdateSystem (from hac or from cmd line)

It appears to be looking for the column 'TYPESYSTEMNAME' in the ydeployments table.

INFO | jvm 1 | main | 2017/07/24 10:58:31.389 | Jul 24, 2017 10:58:31 AM org.apache.catalina.core.StandardContext listenerStart INFO | jvm 1 | main | 2017/07/24 10:58:31.389 | SEVERE: Exception sending context initialized event to listener instance of class de.hybris.platform.spring.HybrisContextLoaderListener INFO | jvm 1 | main | 2017/07/24 10:58:31.389 | org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [update ydeployments set propstableName ='typesystemprops' where propstablename NOT LIKE '%typesystemprops%' AND name IN ('ComposedType', 'AtomicType', 'CollectionType', 'MapType', 'AttributeDescriptor', 'EnumerationValue') AND typesystemname='DEFAULT']; nested exception is java.sql.SQLSyntaxErrorException: ORA-00904: "TYPESYSTEMNAME": invalid identifier

Any ideas on allowing hybris to startup in order to get to the UpdateSystem?