Error starting Hybris 1905 on unitialized MySQL 5.7 schema

[Former Member]

OS: Linux Hybris recipe: b2c_acc_plus

Config as follows:

 db.driver=com.mysql.jdbc.Driver
 db.url=jdbc:mysql://hostname/hybrisdb?useConfigs=maxPerformance&characterEncoding=utf8&useSSL=false
 db.username=hybrisdba
 db.password=password
 db.tableprefix=
 mysql.optional.tabledefs=CHARSET=utf8 COLLATE=utf8_bin
 mysql.tabletype=InnoDB
 mysql.allow.fractional.seconds=true
 db.customsessionsql=SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED

Stack runs to Orbeon Forms message, then Hybris generates the error:

ERROR [hybrisHTTP29] [10.100.16.61] [DBPersistenceManager] typePK or Code was NULL in getPersistenceInfoInternal() INFO | jvm 1 | main | 2019/06/21 13:12:22.583 | Jun 21, 2019 1:12:22 PM org.apache.catalina.core.StandardWrapperValve invoke INFO | jvm 1 | main | 2019/06/21 13:12:22.583 | SEVERE: Servlet.service() for servlet [DispatcherServlet] in context with path [/yacceleratorstorefront] threw exception [Error while processing internal filterchain. Exception occurred at chain position: 7 of 20. Current filter: ‘de.hybris.platform.yacceleratorstorefront.filters.cms.CMSSiteFilter@205e7824’!; nested exception is de.hybris.platform.jalo.JaloSystemException: Table hybrisdb.composedtypes’ doesn’t exist[HY--1]]

Another 1905 instance is running correctly against MySQL 5.6.

[arvind-kumar_avinash]

Hi - can you please use just the following configuration and let me know if it works?

 db.driver=com.mysql.jdbc.Driver
 db.url=jdbc:mysql://hostname/hybrisdb?useUnicode=true&useFastDateParsing=false&zeroDateTimeBehavior=convertToNull&autoReconnect=true&characterEncoding=UTF-8&characterSetResults=UTF-8
 db.username=hybrisdba
 db.password=password
 mysql.optional.tabledefs=CHARSET=utf8 COLLATE=utf8_bin
 mysql.tabletype=InnoDB

If the above settings do not work, please downgrade/upgrade the MySQL driver and try again.

[former_member786386]

Hi,

We have the same issue but with ootb hsqldb. What was your solution for fixing this in the end?

Thanks !

[andreea_libotean]

Hi

I have the same issue using MySQL 5.7.18.

Did you manage to solve the issue ?

Thank you !

[Former Member]

It could be a driver issue