Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Print Bookmark Alert me when this article is updated


ERROR:"Found non-empty schema 'PIM_SUPPLIER' without metadata table! Use init() first to initialize the metadata table" while starting PIM Supplier portal
Problem Description
The Product Information Management (PIM) Supplier portal fails to start with the following error messages:

Caused by: com.googlecode.flyway.core.api.FlywayException: Found non-empty schema 'PIM_SUPPLIER' without metadata table! Use init() first to initialize the metadata table.
at com.googlecode.flyway.core.Flyway$1.execute( ~[flyway-core-2.0.3.jar:na]
at com.googlecode.flyway.core.Flyway$1.execute( ~[flyway-core-2.0.3.jar:na]
at com.googlecode.flyway.core.Flyway.execute( ~[flyway-core-2.0.3.jar:na]
at com.googlecode.flyway.core.Flyway.migrate( ~[flyway-core-2.0.3.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_201]
at sun.reflect.NativeMethodAccessorImpl.invoke( ~[na:1.8.0_201]
at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[na:1.8.0_201]
at java.lang.reflect.Method.invoke( ~[na:1.8.0_201]
at ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
at ~[spring-beans-4.3.10.RELEASE.jar:4.3.10.RELEASE]
... 87 common frames omitted
04/02 15:45:36.960 [localhost-startStop-1] [] INFO c.h.h.s.f.ApplicationLoadedContextListener - PIM Supplier Portal started.
04/02 15:45:36.965 [localhost-startStop-1] [] INFO c.h.h.s.f.ApplicationLoadedContextListener - PIM Supplier Portal shut down.
This issue occurs when the correct schema is not used. Supplier portal comes with its own schema which needs to be created at the time of installation of the supplier portal. In case you link the schema created as a part of PIM core, you face metadata issues. Both the schemas serve different purposes. 
As per the guidelines, the schema needs to be created using the script provided with the supplier portal installer. Provide the same schema name in the of supplier portal.

Create a new schema using that script to resolve this issue.
More Information
Applies To
Product: Product 360 (Media Manager)
Problem Type: Configuration
User Type: Administrator
Project Phase: Configure
Product Version:
Operating System:
Other Software:

Last Modified Date:5/17/2019 4:27 AMID:575329
People who viewed this also viewed


Did this KB document help you?

What can we do to improve this information (2000 or fewer characters)