Details
-
Type:
Bug
-
Status: CLOSED
-
Priority:
Minor
-
Resolution: Non-Issue
-
Affects Version/s: 2.7.2
-
Fix Version/s: 2.7.3 [tentative]
-
Component/s: Entity Broker
-
Labels:None
-
Environment:Demo version of 2.7.2
-
CLE Team Issue:Yes
Description
On startup of demo version of 2.7.2 in catalina.out the following information is logged. This may well be associated with a valid state for the inmemory DB, but is confusing for a system administrator. Please review.
INFO: [GenericDao] Could not execute first DDL line, skipping the rest: StatementCallback; bad SQL grammar [CREATE TABLE ENTITY_PROPERTIES ( id BIGINT NOT NULL IDENTITY, entityRef VARCHAR(255) NOT NULL, entityPrefix VARCHAR(255) NOT NULL, propertyName VARCHAR(255) NOT NULL, propertyValue LONGVARCHAR NOT NULL)]; nested exception is java.sql.SQLException: Table already exists: ENTITY_PROPERTIES in statement [CREATE TABLE ENTITY_PROPERTIES]:java.sql.SQLException: Table already exists: ENTITY_PROPERTIES in statement [CREATE TABLE ENTITY_PROPERTIES]
INFO: [GenericDao] Could not execute first DDL line, skipping the rest: StatementCallback; bad SQL grammar [CREATE TABLE ENTITY_TAG_APPLICATIONS ( id BIGINT NOT NULL IDENTITY, entityRef VARCHAR(255) NOT NULL, entityPrefix VARCHAR(255) NOT NULL, tag VARCHAR(255) NOT NULL)]; nested exception is java.sql.SQLException: Table already exists: ENTITY_TAG_APPLICATIONS in statement [CREATE TABLE ENTITY_TAG_APPLICATIONS]:java.sql.SQLException: Table already exists: ENTITY_TAG_APPLICATIONS in statement [CREATE TABLE ENTITY_TAG_APPLICATIONS]